09-11-2021 06:20
09-11-2021 06:20
I created a custom clock face for my ionic a few years back. Ported it to the Sense. It was working fine until a few months ago when my battery started draining rapidly. I had to have the Sense replaced & just got it back and the same problem is happening. It accesses steps and heart rate and battery percentage. It seems to make the watch less and less responsive, almost like my clock face code isn't relinquishing control or maybe is getting run multiple times or isn't releasing or freeing something. I think it is also interfering with synching. I recompiled it with sdk 6.0 and that only seemed to make things worse. It was using about 10% or more an hour.
I've removed my side loaded clock face and now the battery consumption is back to minimal.
Does anyone have any ideas on how I can resolve this or coding suggestions which could help me stop killing the battery. Could anyone share solid concepts about how to preserve the battery from a coding perspective?
Many thanks in advance.
-Chuck
09-11-2021 06:35
09-11-2021 06:35
This is most likely neither a watch or clock face problem.
There is a known issue with the Fitbit App that drains the battery quickly.
You can try turning off the phone's Bluetooth, Shutdown the watch, wait 10 seconds and place on the charger to restart it and fully charge it.
Then note the battery draining, in all probability it will be fine but if not it could be your watch face, though as it was working fine it will still be fine.
Here is a link that you can try to improve your battery life, though probably it will not make as much difference, once the phone is disconnected.