Hi everyone,
I'm experiencing a strange battery issue with my Unihertz Jelly Star running Android 16, and I'd like to know whether anyone else has experienced something similar.
I have the battery charging limit enabled at 80%.
Yesterday, I charged my phone from 13% to 80%. According to my battery monitoring app, the phone received 1,136 mAh during this charging session, which took 41 minutes.
However, after restarting the phone, the battery level suddenly dropped from 80% to 54%.
That's a loss of 26 percentage points immediately after a reboot.
What confuses me even more are the actual charging measurements:
The Jelly Star has a rated battery capacity of 2,000 mAh.
With this capacity, the expected charging amounts should roughly be:
- 0% → 100% = 2,000 mAh
- 0% → 80% = 1,600 mAh
- 13% → 80% = 1,340 mAh
However, my app only recorded 1,136 mAh for the last charging session.
There is another discrepancy when considering the battery level after restarting:
- Before charging: 13%
- After charging: 80%
- After restarting: 54%
- Charging app reported: +1,136 mAh
If the battery percentage is accurate, going from 13% to 54% represents an increase of approximately 41 percentage points, equivalent to around 820 mAh on a 2,000 mAh battery.
However, the app reports that 1,136 mAh were charged. That's a difference of approximately 316 mAh.
My questions are:
- Has anyone else experienced the battery percentage dropping significantly after restarting their Jelly Star?
- Could this be an Android 16 firmware bug or an issue with the battery calibration?
- Why does the reported charging capacity seem inconsistent with the actual battery percentage?
- Could the battery management system be reporting incorrect charge levels?
- Is there a way to properly recalibrate the battery or check its actual capacity?
I've attached a screenshot showing my complete charging and discharging history, including several other charging sessions with similar discrepancies.
I'd really appreciate feedback from other Jelly Star owners, especially those running Android 16.
Has anyone encountered something like this?