Wow, that is a lot of instructions when what you need to know is the state of charge.
All of this is because you can’t rely on the new System.batteryCharge() call that was added after deviceOS@1.5.0? And the reason it does not work is because you are checking the charge level after coming out of sleep?
I am just wondering if we should be pressing for the System call to be fixed rather than adding management of the fuel gauge to our code.
BTW, I have been using this approach for a few days and it does seem to fix the issue of incorrect battery charge readings after sleep.
Thanks,
Chip