-
Update: Later today I repeated the charging process, ignored both the „fully charged“ message and the beeps every few seconds, left the room. After an hour or two I came back and the battery was at 100% 😀
Is there an option to switch off the beeps?
I’m using the latest firmware. Should I make a factory reset anyway?
Thanks, Peter -
I´m using the Kickstarter version of the Bangle 2. Since a few months I have problems to fully charge the Bangle 2 battery: The charging process stoped after an hour or so with the "fully charged" message and initially showed 80%. Over time the final charging percentage was decreasing and today it already stoped at 60% or so. Last time I had calibrated the percentage measurement, but without effect.
What can I do else?
Thanks, Peter -
I think, it´s very good idea to provide a backup/restore functionality in the IDE or in the app loader, which could restore all apps and all settings after a total crash of the watch.
Why do I think, that this a good idea: Yesterday my Bangle2 was stuck, error message "Storage corrupted", then booted with a default set of apps, my apps all gone, all settings back to default. I had to repeat the app installation and settings process for all my apps and than upload my modified source code - tedious task! It would have been much easier to restore the last backup.
-
@Nicoboss: I think you are right: It simply was the quiet mode scheduler sign :-)
Thank you both! -
-
-
-
-
-
I tested the GPS Recorder app at my Bangle and I got two problems:
I tested tracking my regular Nordic Walking round course, which runs about one hour.
Afterwards, when I download a gpx file from the watch and showed the track in Google Maps, I only saw a part of the walking track: After a few minutes the Bangle started writing coordinates., but after about 40 minutes the track ends abruptly (I double checked with an file editor). This behavior is reproducible.
My second issue is, that kml import to Google Maps is not always working: In the second test run Google Maps produced a vertical line at my meridian instead of the expected track, although in the editor the kml file looked good to me. I then tried gpx format download instead of kml and this worked partly as described above.
Any idea how to fix these?
I switched off the beep - thank you!