Related
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
I take care to exit unused applications, etc, but this still occurs. In fact, I have tried rebooting to ensure nothing is left running in the background. Oddly, it occurs EVEN WHEN PLUGGED INTO THE CAR OR USB outlet... Most often this occurs when I'm using the device for navigation, so GPS, and DATA will be on. The notice has also popped up during other applications. It has happened when using LTE but also when LTE is disabled.
Is this something that everyone is experiencing? If you are, can you please post your Service provider, your SPECS, any mods, or if you have made any progress in stopping it. Lets see if we can track this down.
Mad Medik said:
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
Click to expand...
Click to collapse
That's strange. I've never seen a message like that. It doesn't sound like something native to Android / Sense, do you have any battery monitoring / power control apps installed that could be giving this message? How long does your phone last on a charge if you don't plug it in?
I've seen that error before. I wasn't using the USB cable and charger that came with my phone and that cable was damaged in the USB socket. Have you tried other plugs?
Sent from my HTC Raider X710e using XDA App
The reason you are probably seeing that on car or USB charger is due to then not proving the right amount of power. If you have the screen brightness set high and using navigation it uses quite a bit of power. Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Sent from my GT-I9000 using xda premium
Ive had that happen once when I was playing a really graphics intense game. I was over at a friends house and had it plugged into his computer to charge and was showing him how much better a game looked on my phone than his and it did that. I was using the 3 usb ports on the front of his tower, and he also had his phone and a headset plugged in that front hub as well, and since that hub is powered by one connection on the motherboard I just figured the 3 devices (mainly the 2 phones) were just drawing too much power at the time.
I have had it happen when I was playing a graphics intensive game while plugged into USB on my computer, but never when plugged into AC or car charger.
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
I would find someone with a vivid and try on it, maybe the battery is dead.
Sent from my HTC Vivid via Tapatalk
Mad Medik said:
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
Click to expand...
Click to collapse
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
rquiett said:
Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Click to expand...
Click to collapse
It looks like this is bang on. Apparantly computer USB ports for USB 1, 1.1 are minimum 200 mA with 500 mA recommended. Not sure about USB 2.0. Interestingly there is a proposal for USB 3.0 to allow for 20 Amps or more so you could easily power a laptop and other devices through a USB connection.
The HTC Holiday draws something more than 500 mA and presumably a max of 1 Amp as this is what the included HTC wall charger is rated for.
Anyhow, I guess I will have to pick up a new car charger, because the USB port in my car only pushes 500 mA max, and same for my current car charger.
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
jebise101 said:
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
Click to expand...
Click to collapse
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Mad Medik said:
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Click to expand...
Click to collapse
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Pirateghost said:
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
Click to expand...
Click to collapse
jebise101 said:
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Click to expand...
Click to collapse
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Mad Medik said:
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Click to expand...
Click to collapse
once you have done your recovery you dont need to do it again until you update the recovery with a newer version. its a one time thing, unless you relock stock RUU the device.
the ph39img.zip was configured for at&t vivid. you would probably need to modify it for any other holiday device.
if you are restoring from a backup, did you make sure and flash your boot.img from your backup first? otherwise you will be stuck at that HTC screen for a lot longer....just boot into HBOOT and flash the stock boot.img
I have not really seen my answer on here so excuse me if I am asking repeated ?tions
My battery is NOT holding a charge, so i went to the mobile store and they tell me that the battery is not designed to last more than a year blah blah blah so i bought a new one since this one drained super fast anyway when using the GPS
So i get a new extended life MASSIVE battery and now it wont charge either. It worked fine for about a week, and now its just yellow exclamation point city.
I cannot get the phone to stay on, I have tried multiple charging leads, used the wall, used the computer port, nothing.
So I guess my only option is to mail it to Samsung as maybe it is the usb port itself?
I only think this as last night when I plugged in before bed it made the connection/disconnection sound like 4-5 times as if to say the plug is not in.
But with that said, even when i would plug in and see that it reads the charge is being accepted, I still get nothing hours later.
So if Samsung gets it, will they go into my phone and see the custom rom and tell me to have a nice day as my warranty is now voided for tampering with the original firmware?
Because clearly I have no way to flash it back to stock since the battery will not charge at all.
Entertaining suggestions
Thanks
You do have a way to flash stock, charge the battery externally/put a new battery and unroot and flash stock. Yes if you send it to Samsung they may notice a root so better to get the original firmware in place. I guess the internal charging circuit is flawed but then it shouldn't have charged the new battery at all, not even for a week.
Varad297 said:
You do have a way to flash stock, charge the battery externally/put a new battery and unroot and flash stock. Yes if you send it to Samsung they may notice a root so better to get the original firmware in place. I guess the internal charging circuit is flawed but then it shouldn't have charged the new battery at all, not even for a week.
Click to expand...
Click to collapse
And how do i charge the battery externally, you left that bit out.
Using some other N7000! Look, I'm just suggesting u, maybe there are other ways to charge externally.
I just took it to the phone shop in the mall and the battery is fully charged, just the phone is not excepting it for some reason.
So the phone is screwed up for sure.
Not sure what to do since I cannot get it to turn on to put it back to stock rom
Send it to Samsung, the circuit must be damaged. Hardware problem, you may get away with a root.
Varad297 said:
Send it to Samsung, the circuit must be damaged. Hardware problem, you may get away with a root.
Click to expand...
Click to collapse
I have not touched my phone since I put the custom rom on there about a year ago.
Problem is I have no pc anymore, i only have my mac, is there a way currently to flash the stock rom without needing a pc?
johseph said:
I have not touched my phone since I put the custom rom on there about a year ago.
Problem is I have no pc anymore, i only have my mac, is there a way currently to flash the stock rom without needing a pc?
Click to expand...
Click to collapse
only other way is using mobile odin but phone need to be in working state for that. Try the last option for the service center if it is not even starting they would not be able to check which rom you have and if the motherboard is replaced (just assuming) then there is nothing to be worried about.
treacherous_hawk said:
only other way is using mobile odin but phone need to be in working state for that. Try the last option for the service center if it is not even starting they would not be able to check which rom you have and if the motherboard is replaced (just assuming) then there is nothing to be worried about.
Click to expand...
Click to collapse
Well i took the battery to the shop and they said it was fully charged so its the phone
But now the aftermarket (extended life) actually took a charge when I got home, the phone read 100%, so i turned it on and it said 53% and charging, hmmmm
SO i removed betterbattery app and restarted the phone, then it said low battery again.
So its taking a charge but not holding it now.
I dont remember how to use the Odin since I did the rom flash and so on a year ago and have not touched my phone since I did the root and all of that so I dont remember how lol.
Plus I have only my macbook now and no pc
#weak
Use Mobile ODIN Pro, available on Google Play.
do hit thanks if i help!
Varad297 said:
Use Mobile ODIN Pro, available on Google Play.
do hit thanks if i help!
Click to expand...
Click to collapse
Already have that on my phone, when i go to it, it reads that nothing is on my phone?
You can put a stock firmware in your phone and then flash it. Refer to http://forum.xda-developers.com/showthread.php?t=1347899
Basically when I was heading home from school, my battery was on 56%. 5 mins later, it shut down. Managed to catch a glimpse of the battery percentage and it was on 0%. So I thought to myself, maybe I need to calibrate my battery again. So while heading home, I made sure to drain my battery completely by turning the device on as many times as possible (it would turn on and immediately turn off because it has 0%). Finally at home, I fully charged the phone without turning it on. Once 100%, I turned it on and everything was fine. Battery dropped to 50% after a heavy usage (surfing YouTube, Instagram, Facebook, XDA and reddit) for about 3-4 hours. Was chatting with my friends on WhatsApp (The battery still on ~50%) and my phone shut down. Saw it on 0%. Now it's charging as we speak.
This happened when I updated to Lollipop. Not sure if it's Lollipop, my method of rooting the device or this mod that's causing it. I think it's not Lollipop. It was fine the first few days using it without any root or mods installed.
Note: The way I rooted my device is by flashing a 4.4.4 kernel with recovery, flash SuperSU, reflash 5.0 kernel. Installed dual recovery by @[NUT] and then flashing SuperSU again in the recovery.
Another issue is my phone keeps on jumping in and out of charging. Here's a video I took. It only happens when charging using a PC or Sony's wall plug that came with the phone. Other wall plug seems to work just fine.
LeParkour012 said:
Basically when I was heading home from school, my battery was on 56%. 5 mins later, it shut down. Managed to catch a glimpse of the battery percentage and it was on 0%. So I thought to myself, maybe I need to calibrate my battery again. So while heading home, I made sure to drain my battery completely by turning the device on as many times as possible (it would turn on and immediately turn off because it has 0%). Finally at home, I fully charged the phone without turning it on. Once 100%, I turned it on and everything was fine. Battery dropped to 50% after a heavy usage (surfing YouTube, Instagram, Facebook, XDA and reddit) for about 3-4 hours. Was chatting with my friends on WhatsApp (The battery still on ~50%) and my phone shut down. Saw it on 0%. Now it's charging as we speak.
This happened when I updated to Lollipop. Not sure if it's Lollipop, my method of rooting the device or this mod that's causing it. I think it's not Lollipop. It was fine the first few days using it without any root or mods installed.
Note: The way I rooted my device is by flashing a 4.4.4 kernel with recovery, flash SuperSU, reflash 5.0 kernel. Installed dual recovery by @[NUT] and then flashing SuperSU again in the recovery.
Another issue is my phone keeps on jumping in and out of charging. Here's a video I took. It only happens when charging using a PC or Sony's wall plug that came with the phone. Other wall plug seems to work just fine.
Click to expand...
Click to collapse
Regarding the first part, happens to me something very similar from KK 4.4.4 and 5.0.2 LP, continuing the problem, I have tried several ways to repair it without success. It may be necessary to replace the battery.
Regarding: Another issue is my phone Keeps on jumping in and out of charging. This is usually because the original usb cable is not used or it is defective.
vicmam said:
Regarding the first part, happens to me something very similar from KK 4.4.4 and 5.0.2 LP, continuing the problem, I have tried several ways to repair it without success. It may be necessary to replace the battery.
Click to expand...
Click to collapse
Well I guess I'll just have to wait when I am able to upgrade to the Z4. No point replacing the battery now.
vicmam said:
Regarding: Another issue is my phone Keeps on jumping in and out of charging. This is usually because the original usb cable is not used or it is defective.
Click to expand...
Click to collapse
It happens with other cables as well. When I connect it to the PC, I am able to transfer files over without problems. It's only the charging that keeps jumping in and out.
LeParkour012 said:
Well I guess I'll just have to wait when I am able to upgrade to the Z4. No point replacing the battery now.
It happens with other cables as well. When I connect it to the PC, I am able to transfer files over without problems. It's only the charging that keeps jumping in and out.
Click to expand...
Click to collapse
Mate I guess the way u root that coz the issue.
anakdayak said:
Mate I guess the way u root that coz the issue.
Click to expand...
Click to collapse
I just reflashed stock ftf and rooted the same way I did before. Didn't install the mod. We'll see if it's caused by the root method or the mod.
Why don't you make a clean install (without root) just to discard software/root issues
So a full day of testing shows that it wasn't my phone. It wasn't my root method. It probably is the audio mod. I don't have it installed and it's all fine
LeParkour012 said:
So a full day of testing shows that it wasn't my phone. It wasn't my root method. It probably is the audio mod. I don't have it installed and it's all fine
Click to expand...
Click to collapse
Mate its been 3 days I'm using the audio mod...so far its working great no battery drain.
Since I updated my phone (C6903) (2 days ago) Ive had a weird charging issue. Using the original USB Cable and Charger I have no problems. Using a Sony magnetic charging cable and the original charger it will charge to around 75-80% then keep cycling thru the charger connected/disconnected cycle and wont charge past there. Never had any problems pre-update. Cable all looks good still (it doesnt exactly move far!). I havent had a chance to do a factory reset yet - will try it in the weekend and see. The phones running everything stock, no rooting, no manual flashing, just OTA updates. Prior to the update it was still running the last version of Kitkat.
Anyone else experienced this? Or have any ideas?
askelon said:
Since I updated my phone (C6903) (2 days ago) Ive had a weird charging issue. Using the original USB Cable and Charger I have no problems. Using a Sony magnetic charging cable and the original charger it will charge to around 75-80% then keep cycling thru the charger connected/disconnected cycle and wont charge past there. Never had any problems pre-update. Cable all looks good still (it doesnt exactly move far!). I havent had a chance to do a factory reset yet - will try it in the weekend and see. The phones running everything stock, no rooting, no manual flashing, just OTA updates. Prior to the update it was still running the last version of Kitkat.
Anyone else experienced this? Or have any ideas?
Click to expand...
Click to collapse
I have a similar issue with Stock Sony cable and charger. I was having issues where my phone would get to 33% and then switch itself off, there are times, where I have been charging and its jump a great percentage ad only yesterday my phone was on about 28-30% and I restarted my phone, when it booted backup I was on 78%..
Since the 270 update I have messed on with the firmwares trying to sort it out, although I do have some problems charging, I seem to have sorted the issue of the discharging, as I can last pretty much all day and get the phone down below 33%. Can I ask what firmware did you use, did you make your own pre-rooted firmware or get one off this site?
Try a clean install, I never had that kind of issues...
DorianX said:
Try a clean install, I never had that kind of issues...
Click to expand...
Click to collapse
I did a few clean installs, the first instance of 270 is I created a flash file with ftf, Supersu, recovery, Xposed and the 4k camera mod, but since I removed 4k camera mod and xposed been working ok, so I might try and flash them separate.
phone says 100% but says 80% when off charging
Tried:-
1. 2 different battery callibration apps
2. charging 100%, depleting battery. repeated process a couple of times
3. Switched to Stock (Rooted), 2 Custom ROMs (Waited till it was 100% on both on and off before flashing)
Notes:-
1. Battery seems perfectly fine (takes a while before depleting and doesnt deplete before 0%)
Currently using stock rooted
l would start with replacing the cable and charger to make sure you are getting a full charge. Then monitor the usage time on your phone over a few weeks and see if the time to empty is getting less that is a sure sign of a bad battery
Recheck with another fast charger. Generally, we cannot say if is a faulty cable or you have an faulty adapter. I hope the device chargeboard is not shot/motherboard driven related issue. Also, have you recovered the device using Samsung Kies- Emergency firmware recovery?
gmfirebird said:
l would start with replacing the cable and charger to make sure you are getting a full charge. Then monitor the usage time on your phone over a few weeks and see if the time to empty is getting less that is a sure sign of a bad battery
Click to expand...
Click to collapse
I did try that and surprisingly an apple charger's ETA is 2hrs
I have like 3 fast chargers and they all ETA 6hrs
volcanojax said:
Recheck with another fast charger. Generally, we cannot say if is a faulty cable or you have an faulty adapter. I hope the device chargeboard is not shot/motherboard driven related issue. Also, have you recovered the device using Samsung Kies- Emergency firmware recovery?
Click to expand...
Click to collapse
I tried - original cable with original charger 6hr
- original cable with apple charger 2hr
- different cable with original charger 1.30hr
- different cable with apple charger 2hr
(Used different fast chargers too, same results)
I tried a smart switch recovery. Same conclusion which makes me think its a hardware issue
3zozHashim said:
I tried - original cable with original charger 6hr
- original cable with apple charger 2hr
- different cable with original charger 1.30hr
- different cable with apple charger 2hr
(Used different fast chargers too, same results)
I tried a smart switch recovery. Same conclusion which makes me think its a hardware issue
Click to expand...
Click to collapse
With original charger it takes 6hrs!!! Holy ****
I think its a usb port problem for sure.. Do one thing while connected to the charger go to device maintenance and open battery menu and see if it say charging via AC or USB if while us8ng the original charger it shows Chaging via USB then certainly its the port that has gone faulty..
Hit thanks if helped
Hello everyone! Though its not the right place to ask the question but I have been seeking solution to my problem from months. Long time before, my Galaxy Note II started to behave differently. Whenever I charged it completely, the phone worked normally till 75% to 80% and all of sudden a =low battery warning indication appears and phone proceeds to shut down. I tried changing ROM and calibrating the battery again but nothing worked. Finally I replaced the battery with a new one and also clean flashed another ROM in a hope to see if the problem is gone or still there. But to my surprise the problem is still intact. Now, when I turn on the phone the battery is 90% and when I keep using it, it drains normally, but as soon it reaches round about 80%, it turns off randomly. When I turn the phone back on the battery is still at the same percentage level at which is turns off. I believe there is not an issue with the battery. Please help me what to do, I am using TWRP recovery that doesn't gives the battery stats wipe option too. Should I flash a new ROM again? I would greatly appreciate if someone please helps me in sorting this problem.
What I have already done!
1. Replaced the battery
2. Changed the ROM
3. Re-calibrated the battery
3zozHashim said:
I have this weird issue thats been bugging me for a while now. The phone says 100% when im on it but when i power off and charge, it says 86%.
Click to expand...
Click to collapse
I have noticed the same issue, I think. I suspect it is a general bug.
Guys, try charging your phone while in Android. When it reads 100%, switch off your device. Either leave the charge cable attached or reattach it after you have switched off. Now wait for the off-line charging icon to appear. Unless I'm mistaken, the percentage won't correspond with whatever your phone reports while your in Android. If Android says 100%, this will be a lower number. And off-line charging will keep on charging until you reach 100%.
Androbots said:
With original charger it takes 6hrs!!! Holy ****
I think its a usb port problem for sure.. Do one thing while connected to the charger go to device maintenance and open battery menu and see if it say charging via AC or USB if while us8ng the original charger it shows Chaging via USB then certainly its the port that has gone faulty..
Hit thanks if helped
Click to expand...
Click to collapse
Sorry for the late response. Internet finished, had to wait until the renewal date. During this time, i wiped the rom and re-installed it (Khongloi V11). Since there was no internet, i didnt sign in any accounts, Switched off the location. The phone surprisingly took 3 days before reaching 0.
Indeed, it says USB Charging 6hrs. I sometimes keep plugging and unplugging, it changes to A/C 2hrs.
I have this problem too. But I change batt_capacity_max to 1000, phone on 100% phone off 100%. If we recharge to full it will return to the same state (phone on 100, phone off ~80) so i need to change again. I don't know if this destroy my battery life ? I don't know why. I thought I'm the only 1 who have this problem? (sorry for my bad english)
I think this may be a software/firmware problem, not a problem with the battery.
Crike said:
I think this may be a software/firmware problem, not a problem with the battery.
Click to expand...
Click to collapse
I figured that was the problem but i tried it with three different roms (Khongloi V11, Final, Stock).
Maybe it's some kind of battery protection thing created when your battery is old or something?
3zozHashim said:
I figured that was the problem but i tried it with three different roms (Khongloi V11, Final, Stock).
Maybe it's some kind of battery protection thing created when your battery is old or something?
Click to expand...
Click to collapse
The various ROMs may all use the same battery raportage code, which doesn't account for this discrepancy. After all, most ROMs are just fancy reskins of stock Android.
That said, maybe Samsung support can shed some light on what's going on.
On a side note? Is there anyone who reads this thread, whose reported battery charge (in percentages) is the same in Android as when the device is switched off and charging?
So... any solutions?