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.
Related
Yesterday I decided to install the UKB 2.1 patch but didn't like the fact that the accurate battery percentage was super imposed on the battery, which I had flashed a patch to remove while on 2.0. I then tried to reinstall that patch which was intended for 2.0 and began having force close vibrates on startup to the point that it wouldn't completely boot up. I then booted to recovery, wiped data, cache and dalvik, then did a Nand restore of the backup I had done prior to installing 2.1. Everything seemed fine until I tried to access TSM Parts from the settings menu. It force closes every time without opening. Now I'm at a loss, should I wipe and Odin back to scratch and redo everything or is there a simpler fix?
Sent from my SCH-I500 using XDA App
I don't know enough to provide a technical explanation, but it has been my experience that flashing anything made for UKB 2.0 onto a UKB 2.1 install will cause problems. That said, have you tried fixing permissions in recovery? Moreover, which particular recovery are you using? You may ultimately need to do the ol' Odin Start-From-Scratch, but let's make sure all the bases are covered first. Boot into recovery, select the "Advanced" menu, and then select the "Fix Permissions" command. It should take a few seconds at the very least; if it finishes instantly, the command did not work and you may simply need to Odin in a different recovery and try again. If it obviously did some amount of work, do a full reboot and see if the FC issue is resolved. Let me know how the first try goes and we'll go from there.
The radio is ED05
The kernel is the one that came with it.
However the phone randomly reboots when I am talking on the phone and sometimes when I answer the phone (happened once) it kept ringing on my end but I could still here the person on the other end.
Also the battery is constantly draining fast.
I can get through most of the work day, but it will be about 20%
I've fully charged it and let it run dead.
I rooted and used the MIUI Rom on my wife's and mine fascinate.
Any suggestions?
Did you mean 1.9.16. If so that version had the same kind of bugs and ran odd on my phone too while it ran fine on a friends phone. Don't know why it runs so differently on phones but try the latest 10.28.1.1. It has been running the best out of any one the last month for me. You can find it on miui.us in the fascinate forum. The original port had a broken flash on the camera and weblexa fixed in the 10.28.1.1 version. I've been on it all week no reboots or phantom rings yet.
Do I just boot to recovery and wipe Dalvik Cache and Wipe Cache Partition and install zip from SDCard?
Would you advise to delete battery stats?
Yes just boot to recovery through the power menu. The recovery associated with the 3 button method doesn't work you have to use the one you boot into from the power menu. For best results wipe data/ factory reset too. Sometimes if you just wipe the caches it will act funny. You can wipe battery stats too if you want. I don't do it every time but if it seems it's reading wrong I will go back and clear it later. Since it seems it drains fast you may want to clear the battery stats. I get about 17hrs out of mine with moderate use.
I think I downloaded 10.28.1.0. from the website miui.us. I will download the one from the forum and go from there.
Good luck hope it works well for you. It's a great rom on this phone.
Sent from my SCH-I500 using Tapatalk
MIUI + Fascinate + this forum = lolwatwhichthreadagain
I installed the new update 10.28.1.0 and it seems to work pretty well.
I have a few issues however. I cannot install new programs from the Android Market, it says there is no room available, when there is, and the File Explorer crashes all the time now.
My phone has an odd problem, it seems the battery won't charge above about 66%. I charge it for hours on an outlet charger, and it still won't charge above that. I only started noticing it after my phone started doing two bootloops everytime it reboots, which is slightly annoying, but hasn't really affected anything else. I've also noticed an increased amount of lag in the software, not much, but it's starting to get slowed. Could my number of apps have anything to do with this? TiBu says I have 195 user apps, and the standard amount of system apps. I'm currently running CM7 Build #139. I not only want to know what's wrong and how to fix it, but why it's acting up, although that would be my secondary objective.
Try wiping batterystats.bin; you can do it through a root file explorer under system or boot into clockwork recovery and do it under advanced options. You also may want to wipe cache while you're in recovery.
MissionImprobable said:
Try wiping batterystats.bin; you can do it through a root file explorer under system or boot into clockwork recovery and do it under advanced options. You also may want to wipe cache while you're in recovery.
Click to expand...
Click to collapse
Don't I have to let my battery discharge, or is it just wiping it?
Just go ahead and do it as is. If that corrects the problem you'll want to get it fully charged, wipe batterystats again, run the phone all the way down til it powers off, then fully charge again without interruption.
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.