(Please see post #4 as the issue has evolved)
I recently updated my husband's HD from CM 11 to CM 12.1 (the one build in @amaces obsolete folder). This restored some functionality to a few apps that had "moved on" beyond KitKat and preserved the HMDI functionality. Everything else is essentially the same. Except.
Too often on starting the tablet up in the morning it shows about the same battery level as at shutdown the prior evening (maybe 50-ish) and then in a matter of minutes nosedives to 1%. You can see the behavior on the power usage graphic in Settings and it's pretty shocking. There's a vertical line for when it booted up and then *bam*, it drops to essentially nothing. If the tablet is plugged in for just a moment, the battery level returns to normal and everything is fine. It can be disconnected from the power supply and behaves normally the rest of the day.
So this is annoying (moreso because I need to hear about it every time it happens
). I've read the entire (unofficial) CM 12 thread. This issue comes up once or twice and seems to be "resolved" by "calibrating" the battery either with an app from the PlayStore or without. The app seems to just delete a file that would be overwritten at boot anyway from what else I have read on the subject, but the main idea is to drain the battery to an actual 1%, shut down and charge (the tablet remains "off" although the screen is on) until you've got 100% (which has to be judged by the green LED since the tablet is off).
I tried this (with the app), beginning by wiping cache and dalvik cache. It seemed to work for awhile. Then I foolishly suggested doing a backup. I did this with the emmc TWRP and everything seemed to go well except the battery indicator issue started up again...
So we did the battery thing again.... And it was just fine until this morning (not what you want to hear as you sit down to breakfast).
Clearly one could live with this if you always have the charger close at hand, but it's pretty lame. The tablet behaves beautifully in all other respects. I don't think it's a hardware issue as it started right after flashing the new ROM.
One person in the CM 12 thread actually praised the ROM as eliminating this issue which he had from CM 11!
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough. If I reflash the ROM do I have to reflash GApps also?
Suggestions? I'm really at a loss here.
I recently updated my husband's HD from CM 11 to CM 12.1 (the one build in @amaces obsolete folder). This restored some functionality to a few apps that had "moved on" beyond KitKat and preserved the HMDI functionality. Everything else is essentially the same. Except.
Too often on starting the tablet up in the morning it shows about the same battery level as at shutdown the prior evening (maybe 50-ish) and then in a matter of minutes nosedives to 1%. You can see the behavior on the power usage graphic in Settings and it's pretty shocking. There's a vertical line for when it booted up and then *bam*, it drops to essentially nothing. If the tablet is plugged in for just a moment, the battery level returns to normal and everything is fine. It can be disconnected from the power supply and behaves normally the rest of the day.
So this is annoying (moreso because I need to hear about it every time it happens
I tried this (with the app), beginning by wiping cache and dalvik cache. It seemed to work for awhile. Then I foolishly suggested doing a backup. I did this with the emmc TWRP and everything seemed to go well except the battery indicator issue started up again...
So we did the battery thing again.... And it was just fine until this morning (not what you want to hear as you sit down to breakfast).
Clearly one could live with this if you always have the charger close at hand, but it's pretty lame. The tablet behaves beautifully in all other respects. I don't think it's a hardware issue as it started right after flashing the new ROM.
One person in the CM 12 thread actually praised the ROM as eliminating this issue which he had from CM 11!
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough. If I reflash the ROM do I have to reflash GApps also?
Suggestions? I'm really at a loss here.
Last edited: