Database Users

For Those with Battery Usage Stats FC'ing

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.

Successfully installed MIUI-109160 but issues

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.

moto g5 plus is draining battery fast

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

Weird State, Freezing, Rebooting, Need Help

My Zte axon 7 for last few days has been mostly stuck on a red led for until the battery dies then I plug it in and it boots normal and functions good for 20 mins until it freezes with a red led and I have to do it all over again. I was in TWRP running linage os and it still froze in TWRP which I was suprised. Has anyone else had this issue because I'm not finding much on the internet for it.

sonic1337 said:
My Zte axon 7 for last few days has been mostly stuck on a red led for until the battery dies then I plug it in and it boots normal and functions good for 20 mins until it freezes with a red led and I have to do it all over again. I was in TWRP running linage os and it still froze in TWRP which I was suprised. Has anyone else had this issue because I'm not finding much on the internet for it.
Click to expand...
Click to collapse
yes,me.Also on 10% phone shut down,then i try to turn it on and it says i need to charge my battery,i ignore it.Then i try to boot in TWRP and that works.
Also vendor partition issues,other time on boot its gone,other time in reboot its back
calibration issues also here that i noticed,what more users have but not aware about

Have you found a work around for this to prevent it from happening or to make it work longer. I do not know what causes it. I hesitate to format cause I got some pictures. But I will if it comes to it.

sonic1337 said:
Have you found a work around for this to prevent it from happening or to make it work longer. I do not know what causes it. I hesitate to format cause I got some pictures. But I will if it comes to it.
Click to expand...
Click to collapse
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded

Predatorhaze said:
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded
Click to expand...
Click to collapse
I will try doing this, unfortantly luck isn't on my side for this. In short I did this process 1 year ago forgetting how to do it, as well as I am now on windows 8.1 (previous Wind 7) and the drivers are very hard to get working as when the phone previously worked it would be hard to get it to detect the phpne using Usb 2.0. Just send me a tut on how to flash Lastest version of TWRP and ill do it. Also how do I clear the Vendor partions? I mainly had the intention to set this phpne up once and never come back to all this so thats why I have nothing ready for this.

Also what if it freezes while i'm usimg TWRP? I had that happen to me before

Predatorhaze said:
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded
Click to expand...
Click to collapse
Is this the method you used to fix it?

sonic1337 said:
Is this the method you used to fix it?
Click to expand...
Click to collapse
yes,and then reverted back to los 14.
I have same problems now again,with the rebooting,power loss,fake 0 battery capacity.
i dont know what the cause is,but for me it happen only with vendor partition installed with los15 bootstack etc
im trying to fix it again

Predatorhaze said:
yes,and then reverted back to los 14.
I have same problems now again,with the rebooting,power loss,fake 0 battery capacity.
i dont know what the cause is,but for me it happen only with vendor partition installed with los15 bootstack etc
im trying to fix it again
Click to expand...
Click to collapse
Ok what i'm going to do is erase the entire device, flash TWRP then the default Rom and see if it still happens.

sonic1337 said:
Ok what i'm going to do is erase the entire device, flash TWRP then the default Rom and see if it still happens.
Click to expand...
Click to collapse
u mean stock rom? what i did was ersing everything,also the vendor partition.I rebooted sometimes in twrp to make sure everything is gone and all partitions are on default size.And im glad i did this because the vendor partition showed up again after some reboot in twrp.
Then i installed everything for los14.1 (bootstack and modem) and flashed nuclearom (all default).Ive run some cycles on that and my problems were all solved.Battery calibration was also normal and good

Same issue, more details, with year old B32 system
Just want to add, having same issue. When phone is unplugged, battery starts draining quickly, in fifteen minutes reaching 70%. IF it reaches that far. Usually, battery just jumps from any % to 0! and shuts off, even from 100% charge sometimes, and can't restart phone until I plug it in. When plugged in, it shows wherever it shut down, for example if it shut down at 76% on charging it shows 76%.
Looking at posts above, I wiped everything, including data and media, did a complete reflash to B32 stock image by DrakenFX that I did literally a year ago. STILL same issue remains, battery starts discharging very quickly, then from 95% skips to 0! and shuts off.
Hope this is helpful to anyone dealing with this issue.

vereshchagin said:
Just want to add, having same issue. When phone is unplugged, battery starts draining quickly, in fifteen minutes reaching 70%. IF it reaches that far. Usually, battery just jumps from any % to 0! and shuts off, even from 100% charge sometimes, and can't restart phone until I plug it in. When plugged in, it shows wherever it shut down, for example if it shut down at 76% on charging it shows 76%.
Looking at posts above, I wiped everything, including data and media, did a complete reflash to B32 stock image by DrakenFX that I did literally a year ago. STILL same issue remains, battery starts discharging very quickly, then from 95% skips to 0! and shuts off.
Hope this is helpful to anyone dealing with this issue.
Click to expand...
Click to collapse
that must be your battery. Install Ampere, and disconnect the phone while it is at 100%. See how much voltage it reports. If it says it's at ~95% and has less than 4.3V then it's definitely just a very bad battery with high internal resistance, this causes it to drop voltage easily once a load is applied, and the phone detects the low voltage and shuts off to prevent bad stuff from happening
Does the phone look like it's warped somewhere? Your battery might be bloating

Cleared my cache and Dalvik and my battery life went down the toilet!

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.