I did a search and looked through the threads, some were similar but none were exactly like mine... which has me worried. also google didn't help... which has me worried
My battery charges, and discharges ( i think) normally. I don't see any problem with the actual usage. But, the battery indicator only updates when it is plugged in or unplugged, or i restart it. while it's running it doesn't update, so i have to guess at the level of battery.
I just bought a "re-certified" one from newegg. it did the latest ICS OTA update immediately after turning it on. It had this problem on stock OTA, but i have since rooted it with ViperMOD (still stock ROM), and the issue is still there.
I have read about battery calibration, deleting battery stats, etc - would these be applicable? how do I actually go about doing it?
Thanks for any info!
I would backup all my data (Using Titanium Backup), backup your ROM then either flash to something new or delete all your data. Obviously you can restore everything once your done but just to see if this is a software or hardware issue.
Have you tried any other battery widget? Does it update in settings -> about tablet -> status and/or settings -> battery?
If not, you should try reflashing like mike suggested.
I have tried "Beautiful Widgets" battery widget, as well as stats - and they all show the same level.
ty, will do. do you have a recommendation for rom? stock like with stability and battery life? no dock...
Android Revolution HD look ok?
thanks again
yeah didn't help. i did a wipe from within CWM, and installed Android Revolution.
Is there anything i can do to wipe to wipe it further, safely? before i go through the process of trying to RMA it.
I am fully charging it and then will reset the battery stats and discharge it, as that's said to be good anyway once in awhile and i don't have anything better to do...
if it comes down to it, how might i unroot before sending this back? i have the image from before flashing, but that was after rooting and installing CWM.
Deleting battery stats won't improve your battery life. It's a MYTH.
http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
The correct way to calibrate your battery is to discharge it 2-3 times after flashing a new rom/kernel.
Related
Okay, so for a while I was among those fortunate to have their Batteru Usage Stats not force close. For those not sure what I'm talking about, it's under Settings -> Battery Manager then touching the "battery indicator".
Well as of recent I started to get force closes like others, and decided to charge up the battery 100% and wipe my battery stats using Koush's bootstrap.
Upon rebooting my force close issues are gone (for now). Now I don't know for sure if this was a fluke or what, and I'm not sure how many ways one can wipe their battery stats but if you are getting force closes then give it a try.
Anyways, hope it helps.
What do you exactly mean by "wipe my battery stats" ??
InfamousDX said:
What do you exactly mean by "wipe my battery stats" ??
Click to expand...
Click to collapse
I can only vouch for Koush's bootstrap recovery, which has an option to wipe battery stats.
That being said the problem came back, so it may just be a temporary fix.
Sent from my DROIDX using XDA App
Okay, another update to this thread:
After the force close in battery usage statistics came back I let it go for a while. Just today after a complete recharge I went back into recovery and wiped stats again. Upon rebooting I was able to see my usage statistics again without force closing.
Well, I plugged the phone into the PC to transfer a blackbar theme to my SD card, and after that hastily opened droid x bootstrap and rebooted back to koush's recovery to flash it.
After flashing it successfully, and upon rebooting I now get my force close again.
Sooooo.....
Now to figure out if my hasty boot to recovery (it was doing the preparing SD card thing when I had the app boot to recovery) is what's causing this or the actual flashing of the blackbar mod (for whatever reason) is the culprit.
Of course all this was done with an "I wonder...." approach so I'm going to try and narrow it down when I get a chance.
I am not sure if there is a clear "flash this or mod that" root to the problem.
I have had this problem and it persists from full sbf's, different roms etc...
It comes and goes as it pleases even when I do nothing different to my system, so I think it is more of a base kernel issue with 2.2.
Hopefully this will be fixed in 2.3 (if we get it etc..) but until then I just live with it working/not working as its mood dictates.
Just my opinion
D.
Hi all,
Nasty problem with my 1 month old Motorola Defy+ (MB526)
Last weekend I installed ICS9 from Quarx (20120318 build). I did this using 2ndinit CWM. Made an android backup of my stock setup, I did this over my stock SBF 4.5.1.-134_DFP-74. Used the gapps.zip and battery fix.
The system worked pretty well, but time by time it was unstable. When turned off, it had lots of difficulty to boot up again, lots of reboots and 2-3 battery pulls.
I was planning to flash another ROM when I had the time. Yesterday it worked well, started fully loaded, used it as MP3 for long time, when I went to sleep it was 48% (the accu).
This morning, I stepped in car and phone turned out to be dead. Connected it to my car charger, and it came back to life. However, immediate reboot etc. So I decided to (while driving) put back my stock nandroid backup.
It all turned out well. Stock ROM booted but gave the notice (translation from dutch): "Battery of your device is invalid and cannot be charged. Replace the battery with a battery from your Motorola"
hmm, tried it with my USB cable at the office, and now at home again with the normal charger..
What happened? Any ideas on how to solve this?
The complication is that now my device is rooted and has 2ndinit starter, warranty is more difficult.
Solution: red lens battery fix
I’m not sure it’s exactly the same issue, but my Defy+ totally refuses to charge with Quarx CM9 build 20120318 + CM9 kernel from [1].
Unfortunately I noticed only once the battery was dead empty.
I couldn’t even get it to boot with the USB charger pluged in, and the only way I could get it to boot again was to charge my battery pack in friend’s Defy.
Then I applied the « Battery fix for red lens » provided here [1] which kind of fixed the problem. Now the battery charges again, but it won’t charge over 80/85%.
I had done a « Clean battery stats » from the boot menu after installing CM9 before this whole story, so I don’t know if it had any effect.
If anyone knows better please let me know!
The instability you noticed may be due to the Android debug bug… in CM9 builds. You have to leave Android USB debug (from System params->Debug features, translated from french on, otherwise it will lag like hell most of the time and drain the battery due to the init process eating up the CPU.
[1] http://forum.xda-developers.com/showthread.php?t=1432100
Hi, I installed the battery fix immediatly after flashing the Quarx ROM, so that should not be the problem.
In the meanwhile I have been trying some things with the battery calibration software. That one flawlessy sees that my battery is 100% charged (i did that using the mcguyver method). But, resetting the calibration file on the phone won't help.
In the meantime I have been able to delete all traces (2ndinit boot, titanium backup and unrooted my phone) so I am considering to RMA the phone, no matter the fact how long that is going to take..
Unless, someone here has a last excellent advice..
fokkeh said:
...the mcguyver method...
Click to expand...
Click to collapse
Great! You have just fried your battery (like a few others who tried going McGyver). Get a new battery now and don't use the McGyver method again
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
fokkeh said:
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
Click to expand...
Click to collapse
Well now that your phone is alive, then go to stock and reclaim warranty! Do RMA.!
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
fokkeh said:
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
Click to expand...
Click to collapse
I understand that bro!! Even my phone was away for couple of weeks recently! Just pray they don't flash the latest SBF(BL7_ as they did in mine!
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Puckying said:
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Click to expand...
Click to collapse
Hi, this morning everything changed again, I decided to give it one more try with the latest Quarx CM9 nightly (20120330), wiped data, flashed nightly.zip, gapps and kernel but waited with the battery. After that I wiped cache, dalvik and battery stats.
Reboot and battery seems alive? very strange. But I don't want the kind of buggy CM9 builds anymore, so decided to put back my 2 hours old nandroid backup, using Restore.
Strangly, battery problem was back again. ****! Than just for fun I did data/cache/dalvik/battery stats wipe on stock, and that did not help either.
Now I am back on CM9 again, but thats running O.K. (battery is working!) but not stable enough for me. CM7 (cannot remember which build) gave the problem as well.
With the latter in mind I think (and thus agree with you) flashing a fresh SBF will probably solve the problem, but I am not 100% sure. I want to be able to put back my stock setup for possible RMA. My stock is 4.5.1.-134_DFP-74 and I cannot find that one on internet. And I cannot put it back to stock otherwise right?
The one Pranks gave you in your post (4.5.1-134_DFP-1321) is that a deblurred one? Because when I put a new one, I would like it to be a deblurred. I hate all the bloatware.
I have no idea, but I think he said it was from his own defy so I am guessing it the complete original blurred thing.
---------- Post added at 01:57 PM ---------- Previous post was at 01:31 PM ----------
I redid the cm9 flashing too and now at least it is telling me the battery is charging. But it stays stuck at a big battery icon and a red led is on.
Will see if it goes past that screen with a bit more juice.
---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------
Yessss, it started up!
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
fokkeh said:
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
Click to expand...
Click to collapse
Cardiotrainer however for me is one of the most imp app!!
Hi
I am using this rom over the last few days and really like it. Users are reporting great battery life but I am seeing the opposite. My batty has dropped to 38% in about 2 hours from a full charge.
Can anyone suggest what could be the cause?
Thanks
Did you do a clean flash? When not do a full wipe and then flash it. And on the second thought i could be your kernel settings... Maybe you overlocked your device or the false cpu govenour?
It is hard to say what may be causing the drain. Only thing I can suggest is to do a full wipe (factory reset, wipe cache, wipe davlik and wipe system) and don't put anything on it (don't restore any apps or from TB) and see how it runs. If you don't experience any battery drain start off by installing your apps back on.
Unfortunately, it will be a slow process till you find the issue.
Or maybe it could be an app... I use Wakelock Detector for this (Can't provide link, sorry).
Thanks for the replies.
I did a full wipe before installing this ROM. I also tried factory resetting and installing the rom again. I haven't tweaked any kernel settings but left everything default.
Hi all,
I unlocked my bootloader and flashed twrp on my G5 plus. Before I unlocked my bootloader I had amazing battery life. 8 hours and 15 minutes of sot at the most. Now I'm getting terrible battery life. I can't even last half a day. Does the phone understand how you use it and optimize the Snapdragon 625 or is it something else.
Edit: It also drains battery on standby
You have an app that is not allowing the phone to sleep... Install GSAM or other similar battery usage monitoring app and see what the offender is.
What about the general battery drain. Before I flashed twrp and unlocked my bootloader I used to be able to make it from 6 a.m to 8 p.m. Today is my first day using my phone after unlocking my bootloader and flashing TWRP. After I set up my phone again (the bootloader erased all my data) I set up my phone and charged it over night. By this time of the day I should be at around 70% but I am at 49%. How do I fix this battery drain issue.
It drains 1% every minute to minute and a half.
I'm planning to revert back to stock. How do I relock my bootloader and remove twrp. Can someone please provide instructions and the links for the files to be download
Unlocking, installing TWRP, and rooting are NOT the cause of your battery drain... you should determine that first.
"Relocking" and returning to pure stock can be easy, or difficult, depending on your software version. If you were on the latest stock version then you will have to wait, because to relock the bootloader you must have a complete, digitally signed, factory firmware image that is flashed via fastboot... the process is well documented, but you cannot downgrade to do it, you must flash the same or a newer version than what is installed in your device currently.
See the problem yet? Yup, exactly... we don't have a full factory image of the latest version. We might get one tomorrow, might get one in 3 months, a year, or never, we don't know as all of them are leaks because Moto does not officially support that level of user self-repair on non-developer models.
So we go back to what I said at the beginning... Unlocking, installing TWRP, and rooting are NOT the cause of your battery drain... Work on that first, what have you tried?
Have you installed GSAM and looked at the monitors to see exactly WHAT is draining battery? Have you wiped the cache partition(s) in TWRP? Have you done a full factory reset?
You have decided to root... unfortunately this is not a Nexus device, you can't just stick your toe in and if the water is too cold you have can pull it out and forget going in the pool, for better or worse, now you have to jump in and just get used to it.
I got gsam and I fully recharged my battery with the included wall adapter. I'm getting slightly better battery life but I'll see what app is the culprit after a full days use tommorow
I was at 92% and now I'm suddenly at 89%. Did it really drain 3% or is my battery not calibrated
DarthMaul14 said:
I was at 92% and now I'm suddenly at 89%. Did it really drain 3% or is my battery not calibrated
Click to expand...
Click to collapse
Let it go to at least 70% or lower, then post a screenshot of GSAM
Did you do the cache wipes?
And "battery calibration" isn't a thing anymore, it's automatic every charge cycle.
I'm not rooted so I have to enable the extra stats thing through adb when I get home. Is it clearing the cache?
Sorry I'm kind to new to this but what are cache wipes
DarthMaul14 said:
I'm not rooted so I have to enable the extra stats thing through adb when I get home. Is it clearing the cache?
Sorry I'm kind to new to this but what are cache wipes
Click to expand...
Click to collapse
Wait... You are not rooted, all you did was unlock and flash TWRP and nothing else?
Ok, power off and start TWRP, go to Wipes and Advanced, tick Cache and Dalvik Cache (verify nothing else is selected), and swipe to confirm and perform the action. Press Home - Reboot - System and let it reboot, if prompted about no SuperSU or Root, DON'T DO IT! Skip, ignore, not now, or whatever so it doesn't do anything but reboot. It will take more time than a normal reboot, so he patient. This does not harm your data or files in any way.
Ok I tried it. It surprisingly took under a minute.
I'll see if that makes a difference. Thanks
I tried to root but it didn't work. I first tried super su. I flashed it by twrp and it was successful. But when I went to twrp and I opened super su I could see the root check app in the background but super su kept on telling me that the super su binary wasn't installed. So I had root access but I had no control over it. Even cpu z told me that I was rooted. So I decided to uninstall super su and I re flashed it but the same thing happened again. One of my friends the told me to try out Magisk(apparently you could hide you have root access from apps). I tried to flash Magisk for the first time but it give me two errors while flashing it. When I opened the app it asked me to get the Magisk manager but for some reason they removed the Magisk manager from the play store. I did the same thing again but this time I got the apk for Magisk Manager 14.0 from apk mirror and it didn't work for me. So I uninstalled Magisk. So then I went to Snapchat and it didn't let me login because apparently Snapchat doesn't let rooted users use it. So then I decided to do a factory reset yesterday. (Before all this my battery life was normal about my usual 7 hours of sot). Then yesterday evening I noticed that it was draining a lot of battery. So someone said there was a fix only for the standby mode using minimal adb which basically forces the device to doze. So I have force dozed enabled and my standby battery life is really good. I slept with 62% and I woke up this morning with 62%(so that made a huge difference). I just cleared the dalvik cache and normal cache towards twrp and it seems like it's really helping. I'll change it fully again and hopefully things get better.
Clearing the cache and dalvik cache didn't help me
Did you try just installing the SuperSU app from the Play Store?
Is this really real?
Sent from my Moto G (5) Plus using Tapatalk
mindmajick said:
Is this really real?
Click to expand...
Click to collapse
What are you asking about?
Yes it is. I'm giving an overview of what I did in case if I did something wrong while flashing super su. I found what's draining the battery. It's the cell standby
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
I always wipe cache/dalvik when dirty flashing my rom updates and never had that problem.
I'm guessing you have a bad battery, otherwise it wouldn't have behaved as you described. If you're lucky it's just a glitch - try a few charge cycles :fingers-crossed:
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
lewmur said:
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
Click to expand...
Click to collapse
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
ShadNuke said:
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
Click to expand...
Click to collapse
Rule of thumb, flash stock ROMs via odin and custom ROMs via TWRP. My choice would be a custom ROM and then BACKUP!!!:laugh:
edit: If you rooted the device a long time ago, that means you haven't been getting any updates. You may well be clear back on Android 6 while the latest custom ROMs are 10 and the latest stock is 8.1. You can get the latest stock with Frija, which is a free download.
I'll have to take a look on my SD card, I recall using Titanium backup, so I'll have to check. Do you have any recommendations? Warranty is gone, so I'll likely install a new ROM, I usually do once it's up anyway
I only browse Reddit, Facebook, a couple other social media apps and I'll play the odd game.