Howdy, everyone!
I have a problem with my G935F: the battery percentage stays stuck while the device is on, it gets updated on reboot but then won't change. If I connect the phone to the charger the icon in the status bar reflects that but the charge level still won't update until the next reboot.
Battery life is great and charging while the phone is off shows the correct percentage throughout, which makes me believe this is not a problem with the battery.
The phone is rooted and I'm on stock 6.0.1. I've already tried multiple full wipes and flashing several versions of the stock rom (including Nougat) but the problem persists. I've also tried clearing the cache and the dalvik cache to no avail.
Do you have any ideas about what the problem might be or what steps I may take to try and fix it? I'd like to rule out all possibilities before dishing out €50 to have the battery replaced!
Maybe you have an app that's interfering with the reported battery level. Does the battery indicator update properly when you boot the phone into safe mode?
Unfortunately, no.
No ideas?
Unfortunately the battery level is still incorrect even when the phone is booted in Safe Mode. However it is correct when the phone is charged while turned off and the battery life is normal, which makes me believe it's not a hardware problem...
Hey guys sorry to bump old thread , but found this thread and its good to not always make new threads Well, i also suffer some heating issues but recently my battery percentage stuck at 82% while i was charging with hotspot active , i dont know why it got stuck , but when i replugged the jack in usb port , it continues but after sometime stucks again at 84% , i cleared cache partition but its still the same. But if i turn off the phone and charge, it will proceed to 100% , so the only changes that i made in system are enabling developer options and installing nova launcher and xwidgets app , phone is not rooted and completely stock. Any hints guys ?
Related
One day i was found that my magic isn't charged fully - charging level is stuck at same % (say 66%) although charger was plugged in during all the night.
Beginning from this moment the phone doesn't detect battery level correctly and don't charging up to 100% nor when it is on nor when it is off. For example it can show me one value but after reboot shows differently another value (for example was 46% but after rebooting is 8%, or in some cases battery level can be even more, than before i performing reboot - say was 22% but after rebooting is 78%).
I'd tried wipe, erase system partition and re-flash rom, flash another roms - all without any luck. So i decided that my battery is died. But when i got a brand new battery (from another just bought magic), i got the same issue as in case of my battery. Also another magic works perfect with my battery.
It appears that problem in the phone itself? Anybody got the same issue?
intruders said:
One day i was found that my magic isn't charged fully - charging level is stuck at same % (say 66%) although charger was plugged in during all the night.
Beginning from this moment the phone doesn't detect battery level correctly and don't charging up to 100% nor when it is on nor when it is off. For example it can show me one value but after reboot shows differently another value (for example was 46% but after rebooting is 8%, or in some cases battery level can be even more, than before i performing reboot - say was 22% but after rebooting is 78%).
I'd tried wipe, erase system partition and re-flash rom, flash another roms - all without any luck. So i decided that my battery is died. But when i got a brand new battery (from another just bought magic), i got the same issue as in case of my battery. Also another magic works perfect with my battery.
It appears that problem in the phone itself? Anybody got the same issue?
Click to expand...
Click to collapse
Me too....
did you try wiping battery stats (from recovery)?
I'm not sure if this is supposed to done from a full or empty battery though
adavis159 said:
did you try wiping battery stats (from recovery)?
I'm not sure if this is supposed to done from a full or empty battery though
Click to expand...
Click to collapse
That is what i waa going to say, but I'm sure it doesnt matter what level your battery is when you do this aslong as it doesnt die during the process. Anyways you could have a faulty phone reading the levels wrong if changing roms and doing this doesnt work.
luminiz said:
Me too....
Click to expand...
Click to collapse
I found several similar cases on this forum but no one answer that actually explain what and why it happens.
In my case i got this issue after performing battery calibration procedure. Maybe is just coincidence, i don't know.
adavis159 said:
did you try wiping battery stats (from recovery)?
Click to expand...
Click to collapse
Yep, of course i tried do this from recovery and manually deleting battery stats file - both with no luck. Also during rom flashing battery stats also was erased.
Tried un-root my phone by flashing Android 1.5 from MT3G - issue isn't disappear. After a week maximum detected battery level is falling down and i can't get even 40% of charge. Now, two weeks later, maximum charging level is only few %. Damn it
Hey I was wondering if anyone running any GB ROMs experience huge battery level drops when/if they experience a random reboot or reboot manually (sometimes). My battery will appear to be doing great until the phone is rebooted and then the indicator drops to the bottom...the interesting part is the indicator will always boot to the same level (30%) no matter what level I was at b4 the reboot. I've experience this with both hurricane and stockyish ROMs. I tried resetting battery stats and that ddnt help...
bazidl said:
Hey I was wondering if anyone running any GB ROMs experience huge battery level drops when/if they experience a random reboot or reboot manually (sometimes). My battery will appear to be doing great until the phone is rebooted and then the indicator drops to the bottom...the interesting part is the indicator will always boot to the same level (30%) no matter what level I was at b4 the reboot. I've experience this with both hurricane and stockyish ROMs. I tried resetting battery stats and that ddnt help...
Click to expand...
Click to collapse
That is a bug in CWM and battery level reporting. You can get your battery level back by either rebooting with a charger on or pull the battery out for 5 minutes and reboot.
Worked! Thanks!
i didnt think that it was a CWM problem... b/c i have noticed that since when i first got my epic on release day..
same thing just happened to me but im still on SFR Froyo so i dont think its a GB Rom, but i did the put the charger in and rebooted.... worked great thanks!
Glad I could help. Didn't realize some people saw this on stock. So it may be a reporting issue or momentary voltage drop. Either way at least we can work around it.
Sent from my SPH-D700 using XDA App
Yesterday, I switched on the System UI Tuner, specifically the "Show embedded battery percentage" feature. Today, I was on a phone call for about 30 minutes (with screen on) and was not charging at all. Battery level should have been lower than 100% but remained 100%. Rebooted the phone and the battery level is still at 100%.
Anybody else experienced this and/or has a remedy for it?
did you actually check your battery stats? has it moved from 100%? hav you tried turning it off again? there's not enough information here!
640k said:
did you actually check your battery stats? has it moved from 100%? hav you tried turning it off again? there's not enough information here!
Click to expand...
Click to collapse
The battery stats did not have any information for more than an hour. I turned of the battery percentage feature and the indicator went back to normal.
You sure you didn't turn on Demo mode by accident? System UI tuner allows you to turn on demo mode which will make the battery percent stay on 100%. Try toggling it on and off.
XavierD8188 said:
You sure you didn't turn on Demo mode by accident? System UI tuner allows you to turn on demo mode which will make the battery percent stay on 100%. Try toggling it on and off.
Click to expand...
Click to collapse
Confirmed it's been disabled. I've never activated it.
Same issue
hey there.
I have the same issue right now. I just got my 6p yesterday and I have no modification installed at all, although i did unlock.
My battery is showing 100% with no individual battery use breakdowns, and I have rebooted twice and still 100%.
Did you solve your issue at all?
I may do a factory reset and see if that helps.
Have the same issue. It started this afternoon.
I had the same problem . I fixed it by going into recovery (stock), wipe my cache partition, and reboot.
I fixed mine also, went into TWRP wiped Delvik Cache and Cache.
dslreports said:
I had the same problem . I fixed it by going into recovery (stock), wipe my cache partition, and reboot.
Click to expand...
Click to collapse
that didn't work for me.
hal
fixed
I did the same thing, wiped the cache and a reboot and has seemed okay since. bizarre.
This just happened to me this morning. Was just playing games on my phone for about an hour, then noticed phone still showing 100%. Anyone figure out a sure way to fix this? Tried rebooting.
Hey everyone. So I bought a second hand note 4 recently and have been having battery problems.
I did a full wipe install of CM13 and the battery dropped to 0% at random times and I had to plug it in the charger for the phone to even boot as it would just restart as soon as it turned on. Anyway, i thought this is probably due to faulty battery. I purchased another one and now this one doesn't reboot at random times but seems like the phone keeps reading the battery percentage wrong, sometimes it doesn't charge over certain percent, just gets stuck at 77% or 63% or any percentage really. If I remove the battery and plug it back in, it shows a completely different percentage everytime. I have tried wiping battery stats, do a full discharge/charge, nothing seems to help. Battery drains fairly fast too, once I manage to get it to 100% it shows that expected time is like 2-3hrs if screen on. Thanks!
idoluvizsick said:
Hey everyone. So I bought a second hand note 4 recently and have been having battery problems.
I did a full wipe install of CM13 and the battery dropped to 0% at random times and I had to plug it in the charger for the phone to even boot as it would just restart as soon as it turned on. Anyway, i thought this is probably due to faulty battery. I purchased another one and now this one doesn't reboot at random times but seems like the phone keeps reading the battery percentage wrong, sometimes it doesn't charge over certain percent, just gets stuck at 77% or 63% or any percentage really. If I remove the battery and plug it back in, it shows a completely different percentage everytime. I have tried wiping battery stats, do a full discharge/charge, nothing seems to help. Battery drains fairly fast too, once I manage to get it to 100% it shows that expected time is like 2-3hrs if screen on. Thanks!
Click to expand...
Click to collapse
battery displaying different percentage after u remove it and put it back in is normal i have 3 note4s all do the same (up to 10 percentage change, it either increases or decreases) but the other issues like getting stuck on a certain percentage are not normal make sure u have the genuine battery and try stock rom.
yeah, i tried stock and the same thing really. such a random issue. I just noticed that battery charges once I turn the screen on and use it , so it only gets stuck on random percent only with screen off.
idoluvizsick said:
yeah, i tried stock and the same thing really. such a random issue. I just noticed that battery charges once I turn the screen on and use it , so it only gets stuck on random percent only with screen off.
Click to expand...
Click to collapse
U can try recalibraring the battery....
Bishal 00 said:
U can try recalibraring the battery....
Click to expand...
Click to collapse
yeah, i said I wiped battery stats, which is basically recalibration
once the battery is charged to 100% it also drops first 10-20% really fast and then it gets better but still I only get around 2hrs screen time
idoluvizsick said:
yeah, i said I wiped battery stats, which is basically recalibration
Click to expand...
Click to collapse
Oops my bad..Didn't read your whole post...
the only way to fix this replace your battery by new one
i tried all options (Format ROM - Wipe battery status - Getting back to stock ROM - Unroot - re Celebrate apps - Changing recovery-Removing battery from device for while sleeping - charge without fast charge - charge via USB)
i asked myself after that all of this headache doesn't worth 20$, i replaced the battery with new one and its working fine now
A0_o said:
the only way to fix this replace your battery by new one
i tried all options (Format ROM - Wipe battery status - Getting back to stock ROM - Unroot - re Celebrate apps - Changing recovery-Removing battery from device for while sleeping - charge without fast charge - charge via USB)
i asked myself after that all of this headache doesn't worth 20$, i replaced the battery with new one and its working fine now
Click to expand...
Click to collapse
yeah, i replaced battery as well but it's still the same issue. old one at least charged fully but would randomly reboot on me, the new one doesn't reboot but drains extra fast and doesn't always charge fully. can't believe both batteries are faulty
I am sorry for summoning this old post but did you find any solution to your problem? I have exactly the same experience with my note 4.
Thanks!
Is there a solution for this problem?
Power down and then out-and-in same battery and my stuck-at78%... was 100% when started.
if you having problems with auto restarting.... download the app " WAKE LOCK" and put it on Partial Wake Lock setting... your restarts will be a thing of the past.
It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry ?. What do you guys think of that issue? anyone else had the same problem?
Hrmmm... Try disabling battery saver all together. A similar situation I had with my Pixel XL. Good luck. I miss my 6P!...:crying:
nagoo1 said:
It's my brother's phone. out if nowhere, it started bootlooping.
Click to expand...
Click to collapse
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
v12xke said:
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
Click to expand...
Click to collapse
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
nagoo1 said:
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
Click to expand...
Click to collapse
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
v12xke said:
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
Click to expand...
Click to collapse
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
nagoo1 said:
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
Click to expand...
Click to collapse
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
v12xke said:
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
Click to expand...
Click to collapse
I tried formatting, got no errors, and the same freakin boot-loop. The thing is we bought this phone from USA and the warranty expired 3 weeks ago :s .. anyways, if you have any other ideas plz suggest
Thanks
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
v12xke said:
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
Click to expand...
Click to collapse
Thanks for replying. I'd like to try your method but I don't think it's gonna work for me as the phone starts bootlooping after the 10% mark and the app wouldn't stop it from doing that. I also think that battery health is OK because if I keep charging it up to a 100% while off then try to boot it, it keeps bootlooping for about 5 hours until it reaches 10% then boots normally.
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
I tend to believe that it's a ram issue as I've seen this before in other phones, PCs and Laptops, but what does any thing have to do with this 10% battery??????
nagoo1 said:
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
Click to expand...
Click to collapse
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
rchtk said:
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
Click to expand...
Click to collapse
Never done this before, I'll look it up and try to get it. I think I saw an option in twrp to copy logs.
nagoo1 said:
It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry . What do you guys think of that issue? anyone else had the same problem?
Click to expand...
Click to collapse
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
anikadam said:
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
Click to expand...
Click to collapse
Seems to be the same issue. I hope we both can find a solution for this.
Here are two dmesg.log I got from TWRP, I got one below 10% and one above 10% (bootlooping). I really don't know what to do with these, so we'll need some experience here
Edit: too much characters for the post, I'll attach them instead
I hope this is actually what you guys are looking for.
View attachment 4089615
View attachment 4089616
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
jhs39 said:
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
Click to expand...
Click to collapse
Yeah I think it's a HW failure too, but what makes it work without any issues under 10%? keep in mind that sometimes I leave it bootloop for hours before it reaches 10% and boots-up, which means the device is hot. Also, if i leave it to cool down with airplane mode for a while, it keeps working. I even tried playing asphalt till the phone reached 0% and shut down. It has nothing to do with heat i think, which means its not connection issue like we used to see in graphics cards before.
I just wanna know what gets triggered under 10% that makes the phone work normally? it's not battery saving mode cause i've tried it, but I'm pretty sure something changes at exactly 10% that makes it work.
I don't have a service center that I can trust over here, I called them and they told me they will try flashing the SW (not free of-course) and that if ti's not SW then they will change the main board for almost the same price as a new phone :laugh:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
I knew it wouldn't work, but I had to try
I found a thread over here that fixes bootloop for a certain situation, i knew it wouldn't work but i tried it anyways.
https://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Following the guide I have to Restore a backup through TWRP, It further proved that It's a HW issue when it kept freezing and rebooting when trying to restore. I left the battery drain till it reached 10% then tried to restore again and it worked and booted up, but again when I tried to charge beyond 10% it bootlooped :crying:
jhs39 said:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
Click to expand...
Click to collapse
Nice Idea, but I don't know which kernel manager to use with franco & what settings would be best for limiting cpu. if there's a topic about that please point it to me or give me ur thoughts