Hi everyone, I'm recently owner of a Galaxy Nexus...and I'm having some troubles with battery/usb, and battery status...I've already look at the threads about usb problems...but, what I didn't found is this:
My battery history is not right...It didn't show me the apps consumption...or it shows it, but like freezed in time...The time of use its freezed too...It acts really strange. I did factory reset...but nothing...I'm totally stock.
Any idea?
Besides, when I plug the charger, it takes about 30 sec to show the bolt icon on notification's battery icon.
The Battery/App Stats aren't displayed in real-time, you would have to manually refresh them to see the updated data.
Are you using an official Samsung battery?
It could be the charger you are using, I've actually been able to drain my battery when it's plugged into a live charger. Anything below 1 Amp output seems to delay the charging process significantly.
Liskrig said:
The Battery/App Stats aren't displayed in real-time, you would have to manually refresh them to see the updated data.
Are you using an official Samsung battery?
It could be the charger you are using, I've actually been able to drain my battery when it's plugged into a live charger. Anything below 1 Amp output seems to delay the charging process significantly.
Click to expand...
Click to collapse
Yes, official battery and charger...I press on refresh but nothing happens...so I've tried to plug/unplug severaltimes..sometimes at PC's usb, and the history did reset...but when I think its working, I press on refresh and nothing....It keeps showing 3 secs of battery usage for example
I would suggest rooting (if you're not already) and attempting to wipe the battery stats manually. There could be something stuck in that file that is preventing it from updating when required to.
With a root file explorer, go to Data/System and remove "batterystats".
Other than that, I'm stumped. I've flashed hundreds of ROMs, and wiped my phone hundreds more times and I've never come across this issue. I'm using the Toro variant but I doubt that has anything to do with it.
Let me know if that worked though, I'll keep looking around for a solution.
Liskrig said:
I would suggest rooting (if you're not already) and attempting to wipe the battery stats manually. There could be something stuck in that file that is preventing it from updating when required to.
With a root file explorer, go to Data/System and remove "batterystats".
Other than that, I'm stumped. I've flashed hundreds of ROMs, and wiped my phone hundreds more times and I've never come across this issue. I'm using the Toro variant but I doubt that has anything to do with it.
Let me know if that worked though, I'll keep looking around for a solution.
Click to expand...
Click to collapse
@Liskrig thanks for your help...I finally change it for another nexus, this one works properly. :highfive:.
I think it was all related to micro usb issues...
Related
I started with 80% on Windows Mobile, launched Android, and slept with it sleeping on Android.
I had it under my pillow and I did notice that the phone was hot whenever I picked it up (After an hourish)
In the morning when I wake up the phone is dead.
Any explanation? The phone's backlight was fully off and the phone was locked. Normally on Windows Mobile 80% battery can last me two full days before I need to charge again.
I thought the full sleep was completed on the Android?
Also it shows that it's charging even after I unplug it? I'm using the latest Android on Launcherpro
o my gosh do some effing research first!!!!!! that answer is in the android build thread.
but to answer your questions....
full sleep is working its just that they still havent got the battery voltage or something like that working right so it still drains and its hot cause the drivers still arent working right in some things.
but all of this is from the top of my head so im pretty sure that im wrong with one of those but just go to the build thread use the SEARCH button..
and have fun with your android
Do you know how hard it is to find anything in that thread... It's like finding a needle in a haystack.
Okay so I just booted it without my charger plugged in and it shows that it is charging? But no LED.
I open Battery Indicator and it says "Charging from 32%" and it stays there... Never changes.
Now then if I plug in my charger... nothing changes. No LED even. Just "Charging from 32%" as before... Really weird.
andershizzle said:
Okay so I just booted it without my charger plugged in and it shows that it is charging? But no LED.
I open Battery Indicator and it says "Charging from 32%" and it stays there... Never changes.
Now then if I plug in my charger... nothing changes. No LED even. Just "Charging from 32%" as before... Really weird.
Click to expand...
Click to collapse
There are many posts concerning the current battery issues with the Rhodium. I suggest reading them. There's even a sort of fix if you don't mind losing wifi.
roofuskit said:
There are many posts concerning the current battery issues with the Rhodium. I suggest reading them. There's even a sort of fix if you don't mind losing wifi.
Click to expand...
Click to collapse
Actually you don't lose WiFi anymore.
I used that battery fix but I'm still having this same issue... It says I'm charging even if I'm not.
I think my phone didn't enter deep sleep mode... for one of two reasons... I had windows live messenger running.. or it thought it was charging, and it doesn't sleep while it charges? Dunno.
Maybe I'll re-install it all..
I fixed my issue. I figure it had something to do with the update utility in WinMo. I re-installed Android and added only the zimage from the Battery fix and ran that, and everything works. The first time I had updated the Android using the utility first. All good now. Weird stuff.
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Checkout this thread to see if the gsiff_daemon is your problem. tl;dr when the system is hot and tearing through the battery, go to system settings -> Developer options -> and check Show CPU usage. If gsiff_daemon is the top or second highest on the list, then that is your problem. To solve it for the moment, use system tuner, or something else, to kill gsiff_daemon. There is no permanent cure at the moment, other than to delete gsiff_daemon. Both of those fixes require root, the non-root fix is to reboot.
If gsiff_daemon is not on the list, then something else is the problem, but Show CPU Usage should give you an idea of what system process is running hard.
Samsung Push problem
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
dansushi said:
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
Click to expand...
Click to collapse
Interesting, I installed "micro cpu monitor" shows thin line at top of screen showing both cores.
I haven't had this happen for some time now but after playing with google play and maps downloading offline maps etc I noticed my 2nd core pegged out.
Having seen this in the past & ignoring it I now realize that majorly drains the battery as well as it getting warm.
A simple reboot seems to be the only thing that fixes it. Clearing ram and closing recent screens dies nothing to clear the "cpu jam".
If left alone, it always shows the culprit as "android system"
As to what part of "android system" I don't know.
But until we figure this out for good, that little micro cpu monitor. App is sweet for peace of mind to know all is well or whether a reboot is needed. For what it's worth, I also noticed that after the event, that my auto rotate to landscape was mysteriously unchecked?
If it jams again, I'll have to see if it gets unchecked again, unknown if there is a relation.
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
That happened to me too. But for me, flashing another rom fixed it.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Swaggernaut said:
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No there is a cwm flashable fix floating around here for that
Galaxy SIII via XDA premium
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Contact sync?
i noticed this today and while troubleshooting, noticed contact sync from google says "sync is currently experiencing problems..." maybe?
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
I read the thread about gsiff_daemon culprit. I had it listed as a possible battery drain culprit. The thread says the issue may happen after a hot reboot...which I did have. Killing gsiff_daemon was not immediately effective. I renamed the file so it wouldn't get used...like the thread recommended. I had to reboot to get normal battery drain back and have yet to see the issue again. But i wont know for some time...or maybe when/if i get a hot reboot...which is really rare. Do yourself a favor, and buy better battery stats. Its a must have tool...and it's not expensive.
I wonder if this problem has been solved with latest lj7 jellybean from sprint
Sent from my SPH-L710 using xda app-developers app
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
eatonjb said:
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
Click to expand...
Click to collapse
My experience with froyo/gb/ics is that things have been getting progressively better over the years. But with each so called UPGRADE of an OS or even APPS, we often have to deal with bugs or incompatibilities. I am eager to upgrade to a stock based JB soon, but wisdom says, for 20 things improved, there will be 5 things broken....or hurting in some way. Early adopters suffer the most as usually these issues get ironed out...most of them.
BUT...these stuck drains...wake locks etc., it seems they will happen when they do no matter how many issues get fixed. Over the years, I've had random standby drains caused by Maps/Nav. Maybe it's ok for months, then after a particular update, it's back...and unpredictable. The YES...a reboot, just like with a PC, is a quick short term workaround.
Finally, with the App CURRENT WIDGET, there is a provision to watch for high drain in standby. It watches MilliAmp (ma) readings over time..to determine if you have a rogue drain. That's different than monitoring the CPU. (Some drains do not cause much CPU activity) BUT UNFORTUNATELY, that app won't work with our S3's because of a lack of hardware support. Works great with HTC and many others. It's a bummer because I used to use it and have my HD2 reboot if a 15min consecutive high drain was recorded in standby....thereby saving the battery and usually killing the bug.
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
ScottC said:
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
Click to expand...
Click to collapse
I had this problem numerous times before. If it is Android System that is taking up battery, then its most probably a bad kernel. Your nandroid backup probably was bad. (it sucks, i know). Redownload the stock rom, flash it in odin, before starting up reboot in recovery and factory reset, then start it up. Your problem should be resolved. dont restore any apps and start fresh. Like I said it sucks but what can you do?
Hey ScottC,
Definitely doesn't sound normal. At the end of the day, I'm sitting around 10% lost to android system, 15% tops (of course this can vary on what you use and how you use it, but if your battery dies in 5 hours, certainly something is wrong). It's possible that in the process of nandroiding back, something messed up. I'd recommend a complete wipe (factory reset, wipe dalvik, etc), then test it out for a day or two. If the issue persists, you will likely want to Odin back to stock. If it still persists (highly unlikely), I'd call in for an exchange. Best of luck to you, and please let us know the results!
Thanks for the tips - to clarify, it was doing this before I ever nandroided back - but I have a feeling wiping might be the best bet (or trying out a better JB leak).
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
I have the same issue. My phone was 100 percent and I've been sitting here watching the Texans game and I'm getting the worst battery life today that I have in my week or so of owning this phone. My phone is bone stock.
Sent from my SGH-T999 using xda premium
I have the same issue
ibous said:
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Add another one to the list for this problem. I've had my phone since Sept. 27th (so 3 weeks?) and up until about 4 days ago it was great. Great battery life, even with all the bells and whistles turned on, and several apps that update constantly. For some reason a few days ago it started to battery drain HARD, downing to 25% of the battery life in less than 6 hours. That's with the phone sitting idle, not touching it, on wi-fi (not 4G) with excellent signal. Last night I plugged the phone in at 10% battery, did some chores, and returned some 3 hours later to find the battery at 5%. It drained while it was plugged in!
The battery drain issue seemed to start after the phone decided to have a certain level of diffuculty finding a 4G signal. I had to reboot the phone to get it to connect to the network. After that, the Android System will take anywhere from 55% to 76% of the battery drain.
I have shut off numerous programs, disabled the Samsung apps that were said to possibly be a problem, and looked for the gsiff_daemon in the CPU list (my top process is "com.android.systemui"). I searched com.android.systemui to see if I could find a fix, and all I'm really seeing is "flash a new ROM" or "Your kernal is bad, reset or reflash it." I'm running a 100% stock phone, and actually had no intention of rooting or flashing this phone yet, and I didn't want to have to factory default it. It's starting to look like that's my only option. Someone said that this bug seems to crop up out of pure chance and I think they may be right. My husband has the identical phone, bought, charged and activated the same day, and he doesn't have this problem. He's still getting the incredible battery life that I used to get.
So what's the skinny? Is my only option on this a factory reset? I've seen threads referrring to a thread dedicated to this topic, yet no links. If there's more info to be found, I'd love to read it.
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
lazarat said:
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
Click to expand...
Click to collapse
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
I believe this is the thread you were told about.
http://forum.xda-developers.com/showthread.php?t=1755180
When you checked cpu use, how did you check it? There's an option in Dev Options to Show CPU Usage and you can see real time what's running. Just fyi in case you did it differently.
Sent from my SGH-T999 using xda app-developers app
Thanks for the Link, Doc! It's much appreciated. As far as checking the CPU, I used the option under the Dev Options menu and watched it bounce about. Many different programs would take top spot, but when the phone was idling it was always com.android.systemui at the top. When it wasn't top, it was never far below.
Have you tried booting into recovery and wiping dalvik cache?
If it comes to it, before factory resetting since you want to avoid that, download the official stock FW and flash with Odin. I'm pretty sure it will keep your data and apps intact. Backup data first in case I'm remembering wrong. If that doesn't do it then factory reset may be your final option.
Check settings > Battery, and open Android System (I'm betting its at the top). This may give you a better idea of what the root cause could be, maybe...
Sent from my SGH-T999 using xda app-developers app
CorbieMessenger said:
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
Click to expand...
Click to collapse
You are not the op of this thread so i cannot comment about your problems. The first posts regard rooted devices running jb leaked roms and in the jb leaked roms threads all people talk about is android system taking a high percentage of the battery usage. So one must be really blind not to notice what is the problem and fix if there is any. There is no fix and it is kernel issue. Thats the reason why it is called leak and not official release. U can post some screenshots of ur battery usage and firmware version you are running if u want people to help u since u claim u r all stock and still android system usage is high 76%.
Doc-
I tried booting into recovery, but since I'm not a rooted user I can't clear the delvick cache. Somehow in the process of attempting booting into recovery I managed to lose my set wallpaper and most of my homescreen widgets, though the rest of my data and programs seem perfectly intact (accidentally went into a safe mode option). I did clear the cache partition in recovery, and tried another trick someone listed of pulling the battery and holding down the power key (I'll try anything at this point) and oddly it seems to be behaving better so far. Sitting on my desk it didn't discharge at all, and having just put all my widgets back it's only drained a few points. The screen is now the big spender at 39% with Cell Standby next at 12% (previously is was Android System being the hog at 50-70%). I have no idea which of the things I did actually did anything, but I think this just saved my tail.
I'm going to charge the phone normally tonight and leave it loose all day tomorrow like I usually do, and see what happens. If it starts battery draining again, I'm going to try flashing with Odin. Here's hoping I'm one of the few lucky ones where the problem simply "goes away".
Thanks again for your help!
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
I know that this sounds pretty simple and you may have already tried this, but it always works like a charm for me. Try draining the battery ALL the way down until it automatically shuts off. Then keep turning it on until it won't even turn on our vibrate anymore. Plug it in and turn it on. Leave it plugged in until it's at 100% again, I do this overnight so there's no usage other than standby. Hopefully this will get your battery back in shape. Good luck!
DocHoliday77 said:
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sometimes I wonder how I got into Safe mode.
forum.xda-developers.com/showthread.php?t=1821557
Well, It behaved for about an hour, then it started the massive drain again. Sadly I just backed a few things up and then factory defaulted it. We're leaving on a trip tomorrow, and I need it to not be a power-sucking brick. Oddly, everything that my CPU report was showing was identical to my husban'd phone, which has no issues with battery life. The Gsiff daemon never once showed up.
As far as safe mode, I held down the volume down button while I powered up the phone. It went into safe mode. Don't know if it'll work for y'all, or if it was just a fluke on my part. :>
Thank everyone for your help in trying to troubleshoot this. One of these days I'd love to have an electronic device that just worked without me having to poke around in it's guts. ;>
If its still acting up after the factory reset, your best bet is to flash the stock FW with Odin. If the factory reset didn't wipe your internal sdcard, you may need to to wipe it in recovery by using format data as well. (Factory reset should do this anyway as long as you're on stock recovery)
I've seen on some jb leaks where this would significantly help. I know your not using jb but its worth mentioning anyway.
Good luck!
Sent from my SGH-T999 using xda app-developers app
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
louballs said:
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
Click to expand...
Click to collapse
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
HTCDreamOn said:
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
Click to expand...
Click to collapse
Thanks for the tip. I had already deleted the battery stats bin file from the system and rebooted and received the same results (assume thats what your fix does). I've also reinstalled the rom and had no issues. Ive done searches and found that SEVERAL other people with the G2 had this issue. Kind of surprised it hasnt yet been addressed on this forum. Back in 2011 Tmobile was asking for people to volunteer some info in order to fix it. Apparently nothing was ever done and when i call in (several times), no one seems to know what im talking about even when i point them in the direction of their own forums. I'm really at a loss and don't feel like paying out the a$$ for a new phone when I know this is not something I did.
A long time ago for an unexplained reason my phone froze at 17%. It hold more power then that, but Android is frozen at that number. When the device is off and I first plug it in then it only shows 17%.
It's been like this for a year. I've done various things, like factory reset. Tried draining and fully charging battery many times. No luck. I was told I should get the battery replaced. I may still do that.
I just recently installed twms. I noticed it actually has the proper battery %. What is making twms check different then Android?
I have the last version of Android for pixel 3 xl. My phone is rooted but I don't have any mods installed. Is there something I can do to have Android read the battery the same way that twms does? Would a new kernel fix this? Please point me in the right direction?
I do not know what Twms is but it seems something wrong with rom itself. Did you tried wiping everything and clean flash stock rom ? Maybe some files gets corrupted.
Also can you try any battery app that report battery voltage ? If it is reported correctly at least you can say battery is ok..
icanrule said:
A long time ago for an unexplained reason my phone froze at 17%. It hold more power then that, but Android is frozen at that number. When the device is off and I first plug it in then it only shows 17%.
It's been like this for a year. I've done various things, like factory reset. Tried draining and fully charging battery many times. No luck. I was told I should get the battery replaced. I may still do that.
I just recently installed twms. I noticed it actually has the proper battery %. What is making twms check different then Android?
I have the last version of Android for pixel 3 xl. My phone is rooted but I don't have any mods installed. Is there something I can do to have Android read the battery the same way that twms does? Would a new kernel fix this? Please point me in the right direction?
Click to expand...
Click to collapse
I am having the same problem as you, only in my case I am stuck at 1% when I restart in TWRP if it shows me the correct percentage, I have tried with different roms (custom - stock) and different kernels I still have the same problem.
I have noticed that when accessing the root of the system (any rom) in the address or path "sys/class/power_supply/battery" and I open the "battery" file with a text editor there if I see the real value of the load of my battery
I have been meaning to post an update to this thread. I found a workable solution for me with tasker. You can download it for free at (https://taskernet.com/shares/?user=...GsgjEQmPWd4nGTxTaKorB2&id=Project:BatteryInfo)