Is it safe to test apps on the device while developing?

Former Member over 8 years ago

I'm starting to develop apps/widget/watchfaces, and I just found myself with a useless, bricked Fenix Chronos. Now, it may have been a defective unit, but I wanted to know if, in your experience, it was safe to test apps on the device.

The term you find in the documentation is "Side Loading an App". For example, if I compile with Eclipse a new app, and copy/paste the executable into the GARMIN/APPS directory, is it safe? will this cause any issues?

Bottom line, if it's dangerous I may get a less costly device (not the 1.500$ chronos) for development.

Thanks.

HermoT over 8 years ago

100% safe.

Apps are sandboxed and cannot brick any device as far as I am aware.

In 2 years never had a sideloaded app bricking any of my various devices.

Former Member over 8 years ago

gary fieldgate

100% safe.

Apps are sandboxed and cannot brick any device as far as I am aware.

In 2 years never had a sideloaded app bricking any of my various devices.

So, just to be sure: manually copy/pasting the compiled executable from eclipse to the GARMIN/APPS folder should not break the device in any way, right? What about uninstalling one of these via the Garmin Connect mobile app?

HermoT over 8 years ago

So, just to be sure: manually copy/pasting the compiled executable from eclipse to the GARMIN/APPS folder should not break the device in any way, right? What about uninstalling one of these via the Garmin Connect mobile app?

Correct. Fear not. :D
You can uninstall from the app without issues.

Former Member over 8 years ago

Correct. Fear not. :D
You can uninstall from the app without issues.

I was asking this because the watch seems to give access to the firmware files when connecting via USB, that's all.

jim_m_58 over 8 years ago

I tend to use the "build for device wizard" in eclipse instead of copy/paste, as you have a bit more control and can build a release or debug version of the .prg, as well as selecting the correct target device. Using the wrong target can mean that the bitmaps may be in odd colors, or the layout might not match the screen, but that's about it.

Former Member over 8 years ago

I tend to use the "build for device wizard" in eclipse instead of copy/paste, as you have a bit more control and can build a release or debug version of the .prg, as well as selecting the correct target device. Using the wrong target can mean that the bitmaps may be in odd colors, or the layout might not match the screen, but that's about it.

I used the wizard, but the build destination was not the device folder but a local folder. I still copy/pasted the only generated file, the .prg file.

jim_m_58 over 8 years ago

I was asking this because the watch seems to give access to the firmware files when connecting via USB, that's all.

Actually, it really doesn't. When there's new firmware (GUPDATE.*), part of the install involves checking it for validity, and when it's installed (or shown to be invalid), it's removed from the mass storage space.

Former Member over 8 years ago

Actually, it really doesn't. When there's new firmware (GUPDATE.*), part of the install involves checking it for validity, and when it's installed (or shown to be invalid), it's removed from the mass storage space.

So, out of curiosity, if I connected the watch via USB and deleted all the files, would it still work?

jim_m_58 over 8 years ago

I wouldn't try it, but in theory, that could be the case.

travis.vitek over 8 years ago

if I compile with Eclipse a new app, and copy/paste the executable into the GARMIN/APPS directory, is it safe? will this cause any issues?

Yes, I'm with HermoT and jim_m_58. This is very safe. I've been doing it for two years now and it hasn't been a problem.

So, out of curiosity, if I connected the watch via USB and deleted all the files, would it still work?

I wouldn't consider this to be a great idea. That said, I'm fairly certain that the data on the accessible file system does not include anything necessary to the functioning of the operating system. You should be able to move all of the files off of the file system and still get a bootable device.

Travis