-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Charge cap not working. #340
Comments
I've observed the same having flashed firmware again and again, my 80% cap is usually exceeded. Perhaps due to the device getting power in the interval of updating and in that time it's not checking the cap? Not sure. Doesn't seem to ever be a problem during normal operation though. |
It's not exactly clear how it works (not that I've tried with all my might to find out), but from what I saw even when charge is suppressed (method that charge cap uses, aswell as some apps like subghz as they need a stable power line without fluctuations that charging causes) it's not discharging like you'd expect... unplugged it shows charge of -6ma or whatever, charging shows +whatever ma, and plugged with charge suppressed it shows charge 0ma... almost like it is charging but only enough to offset the amount it's drawing. That might explain why, it's "suppressed" but a very tiny amount is still being accumulated over time? If so, no clue if it would be a software or hardware thing. And then again, not even sure if this is what's actually happening, maybe that 0ma is just a problem in display but it's actually discharging, I don't know. |
It's not just charging just during reboots; it's also charging when I get files through qFlipper and download or update apps |
Well yes, but we count those as 'normal operation' and the cap should be working correctly for them, right? |
Describe the bug.
I have my flipper's charge cap set to 95 percent, and while updating it charged to 98 percent!
Reproduction
Target
Firmware, Hardware
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: