Since Lenovo P2 is one big power source I have found out that I rarely have to charge the battery to 100%. Often I find 80% sufficient, but if you only charge to this level battery stats won't reset. I think the lowest you can charge while battery stats still resets is 90%. I have tried the adb shell dumpsys batterystats --reset without success (rooted with Magisk). Magisk have previously had problems so it could be a reason. It could also be due to the stock rom/kernel not supporting this.
My question is simply: Has anyone successfully resetted battery stats with the dumpsys command? (which I believe is the only way doing it manually)
Related
I've i9195 with stock battery and rom, all was normal. Then I replaced it with double sized battery+new back cover. Not a microUSB batterycase. After many cycles and weeks of use it still didn't calibrated to new capacity. Fully charged battery lasts about a day and phone shuts down. If I switch it back ON after couple of minutes - I see 50% charged and can use phone another day.After second 'full discharge' I'll have about 15% more. All techniques for 'calibrating' battery with deleting batterystats doesn't work. Charge, off, remove bat, wait, place it back - either. /sys/class/power_supply/battery/uevent have string POWER_SUPPLY_ENERGY_FULL=1940000000 and it is always the same. So phone simply downcount from this level and tells that charge is 0% while voltage is about 3.7v. Interesting that "energy_full" file has number of 3880000000 but it seems that it's not used in calculations.
After all I installed CWM, root, cyanogenmod 11 and used it for about a week. SAME problems, except that "energy_full" is 1940000000.
I want to solve this very much, I can program or recompile kernel, if needed. It's pm8921 charger ic there. Maybe this number was programmed in it in factory mode or smth. Maybe threis a way to correct it. Thanks in advance.
Same here with stock-rom, CyanogenMod and MoKee's rom.
I think the only way will be to recompile the used kernel with the correct value of 3880000000 instead of 1940000000 in file "drivers/power/pm8921-bms.c" in kernel sources (function "calculate_fcc_uah", part "scalefactor". Scalefactor has to be change into scalefactor *= 2.
Huge work for a little problem...
Instead of making any advanced config, have you tried this little app (needs root privileges)?
https://play.google.com/store/apps/details?id=com.nema.batterycalibration
After migrating to CM11 my battery was draining very fast. I used this app and it apparently fixed a part of the issue (battery still drains fast, but not as fast as before).
Quick question regarding the battery. Is there anyway to actually check the usage time in hours and minutes on this? When I look at the battery info all I get is the graph with % left and approx time left. Id like to be able to know the exact battery life Im getting if its possible? Want to avoid a third party battery app if thats possible. Thanks everyone.
execute below command in terminal emulator -
su
dumpsys batterystats
For some reason my phone is one of the lucky few which has a persistent wakelock problem. fusb301_otg_wl which is 100% all the time and prevents the phone from getting into sleep/idle followed by 6a00000.ssusb
These wakelocks appeared after updating from OOS 3.2.8 to newer versions. I've tried many roms, kernels, cleaned my usb/charge port, tried differtent cables and chargers but no luck so far. When flashing new roms/kernels the wakelock is away for a few hours but somehow the wakelock always finds a way to get persistent again and stays at 100%
I discovered that there are three ways to remove/hide the wakelock
1. just stick something random in the usb port and the wakelock is gone. For example only this thing with nothing attached to it.
2. use this script to edit a file on startup
#!/system/bin/sh
chmod u+rwx /sys/module/dwc3_msm/parameters/disable_host_mode
echo Y > /sys/module/dwc3_msm/parameters/disable_host_mode
3. Flash stock OOS 3.2.8.
Fix 1 and 2 are minor fixes for a bigger problem. The battery drain is a little less then with the wakelock but I still have a drain between 5 and 10% a hour when my phone is doing nothing.
So my question is if someone knows whats causes the wakelock to appear. Did someone succesfully repaired his phone to prevent this wakelock? Did a new usb port helped? And maybe someone knows what have been changed after OOS 3.2.8 so maybe a new kernel can be written
Hello guys, my HTC 10 (Verizon) is suffering from massive ideal battery drain. I leave it at 97% before going to sleep and when I wake up (after 6hrs) it's either below 30% or has shut down.
I'm on stock Oreo 8.0, no root. Version 3.18.605.13. I tried factory resetting it twice both from the reset option in settings and also from recovery, cleared cache partition from recovery as well but to no avail.
Also using greenify with aggressive doze on, doesn't help much. The battery runs okay as long as I'm using it, it goes nuts when the phone is placed on the table with the screen turned off.
Also I installed gsam battery monitor with adb and found kernalos to be draining the most battery. Then I installed BetterBatteryStats with adb and I'm posting screenshots of the results below.
hi, has anyone experienced the battery drain when the phone is idle?
last night i've left the phone on 20-22% battery and when i woke up - the phone was turned off because the battery reached 0%...
when it charged - the idle battery consumption was off the wall...
device is about a month and a half old...
i'm using stock MIUI (latest, EU), not rooted
phone is slightly debloated via adb fastboot tool...
phone doesn't use 5G network at home or ever, mobile data is turned off when i'm home
i just can't figure out what is happening...
thanks in advance
Debloated too much I think. Have the same issue when I have Samsung Phone and used adb debloater
not sure about that...
i didn't touch any crucial Xiaomi apps, just recommended ones and never had any bebloat battery drain issues on any device which was debloated or even rooted
update:
last night i left the device with 38% battery, just to see what would happen
in the morning, 8 hours after - it still had 35% charge strange...
note: in the meantime, i adjusted some apps not to work in the background if not needed and uninstalled (almost) never used Google Lens (which i've installed few days ago to try something)
didn't touch any battery settings for common social and messaging apps that i use (Facebook, fb messenger, google messages)
so, maybe the culprit was either google lens or some of those adjusted apps - or the device doesn't read the battery well when under 30%... i'll see what will happen in the next few days...
@60nine Settings > Battery > Battery Use (check "Daily battery usage chart")
Look there if you see any app that has consumed much battery.
you seriously think that i don't already know how to check this? (how do you think i've found that the idle was draining the battery?
no suspicious apps there, idle battery consumption was at the top...
Sorry, I overlooked that you have already wrote it is the idle drain and not a specific app
no problem