[Q] Weird battery issue when using TWRP to backup - Nexus 4 Q&A, Help & Troubleshooting

I have a very strange problem. I can't decide if there's something wrong with TWRP or with my Nexus 4. Here's the series of events:
1) I want to backup my phone using TWRP 2.3.2.3 that I have installed.
2) Battery is at ~58%
3) I plug the N4 into my wall charger.
4) Reboot into TWRP and start a backup, with everything checked to backup, using compression.
5) TWRP shows battery is "58%+" (I assume "+" means charging)
6) A couple minutes into the backup the screen goes dark.
7) I press the power button and get a battery charging symbol. I press again and eventually boot into Android.
8) Battery is at 1-2%
How can my battery go from ~58% to almost 0% in two minutes, especially when it's on the charger?
To make things even more strange:
1) I wait until battery is charged to 100%
2) Reboot into TWRP and start the exact same backup.
3) It completes successfully, reboots into Android, and battery now shows at ~92%
What is going on here?

Slight battery loss is normal upon a reboot. As to your first issue... beats me. I doubt it's a problem with the phone. Maybe a one off.

asawoszc said:
Slight battery loss is normal upon a reboot. As to your first issue... beats me. I doubt it's a problem with the phone. Maybe a one off.
Click to expand...
Click to collapse
I'm not so concerned about the battery going down when backing up. I would expect that. Although with it being plugged in you wouldn't think...
But the part where it suddenly dropped to near 0%... if it only happened once, maybe, but this has happened twice when my battery was not at or near 100%. I suspect it would do it every time.
I was just wondering if anyone else had experienced something like this?

As a constant ROM/MOD flasher over the past 2 weeks of having this phone I have not had any similar issues.

Loosing 20-30% at once after doing something like backup in recovery is unlikely, but possible.

asawoszc said:
As a constant ROM/MOD flasher over the past 2 weeks of having this phone I have not had any similar issues.
Click to expand...
Click to collapse
Have you ever flashed/backed up using TWRP when battery wasn't near full?
I have a Nexus 7 and have never had this issue.

ahalford said:
Loosing 20-30% at once after doing something like backup in recovery is unlikely, but possible.
Click to expand...
Click to collapse
Even when plugged in?
What about a 50-60% drop after two minutes of backing up?
If I'm the only one, I might have to RMA my phone.

Try 2-3 times the same scenario, then switch to CWM and repeat the procedure. Then you'll know where is the problem, for sure.

ahalford said:
Try 2-3 times the same scenario, then switch to CWM and repeat the procedure. Then you'll know where is the problem, for sure.
Click to expand...
Click to collapse
That sounds like a GREAT idea. Thanks, I'll try that. Although I was hoping to use TWRP because it compresses backups, and my N4 is in danger of running out of space. But it would be worth trying just to see if it works.

I doubt you can charge whilst in recovery. I'm sure cwm will not let you charge even of you shat your pants ....
Sent from my Nexus 4 using xda premium

MattSkeet said:
I doubt you can charge whilst in recovery. I'm sure cwm will not let you charge even of you shat your pants ....
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I thought charging would be a hardware thing, so it should do that no matter what your phone was doing. ?? Besides, TWRP shows a "+" next to the battery percentage when plugged in. It's not there otherwise, so...

I've had this issue happen a few times on my i777 S2. The phone would randomly reboot and the battery would drop down to <10%. I've had it happen at an original 90%, 50%, you name it. I chalked it up to issues with the battery.

Ok, so I installed CWM, but then ran into some threads that said it had issues with JB 4.2. As in, it doesn't know how to properly handle the new "/sdcard/0/" folder structure that was introduced for multi-user support. So, I chickened out and went back to TWRP. But then TWRP did another 55% battery to 0% battery crash again. Only when I have a lot of battery left will it actually complete. *sigh* I will try CWM again, at a similar battery level, to see what happens.

DangKid said:
I've had this issue happen a few times on my i777 S2. The phone would randomly reboot and the battery would drop down to <10%. I've had it happen at an original 90%, 50%, you name it. I chalked it up to issues with the battery.
Click to expand...
Click to collapse
So what did you do with that phone? I'm considering an RMA, especially since I seem to be the only N4 owner on here with this issue.
When mine crashes, it doesn't finish the backup and it goes to a blank screen. Only after having it plugged in for a minute or so will it actually start up. Like the battery was completely empty. And it only seems to happen when the % left is under maybe 70%. It's always completed in the 90% range.

RMAing this early in the life of the phone is a waste. How do you it isnt a bug with twrp. I would wait it out for a bit. I also feel nanodroids are over rated. Titanium Backup makes things so easy. Since the bug happens only when doing that one thing it sounds like a bug with twrp.
Sent from my Nexus 4 using Tapatalk 2

Prod1702 said:
RMAing this early in the life of the phone is a waste. How do you it isnt a bug with twrp. I would wait it out for a bit. I also feel nanodroids are over rated. Titanium Backup makes things so easy. Since the bug happens only when doing that one thing it sounds like a bug with twrp.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I can't imagine a bug in recovery that is able to deplete your battery 50%+ within 30 seconds. Another weird thing happened: I was at ~70% and then rebooted into TWRP, which then immediately had the battery at ~20%. I rebooted back into Android and it had the same thing. I didn't even kick off a backup or anything. ??? See the screenshots here to see the two dramatic cliff drops I've had, one earlier today the other a few minutes ago.
I will wait on the RMA to see how things go WITHOUT using TWRP for backups. I think nandroids are very annoying to make and use, but I didn't want to learn how to use Titanium (it *looks* complicated). I think I'll look into that now though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cwappy said:
Ok, so I installed CWM, but then ran into some threads that said it had issues with JB 4.2. As in, it doesn't know how to properly handle the new "/sdcard/0/" folder structure that was introduced for multi-user support. So, I chickened out and went back to TWRP. But then TWRP did another 55% battery to 0% battery crash again. Only when I have a lot of battery left will it actually complete. *sigh* I will try CWM again, at a similar battery level, to see what happens.
Click to expand...
Click to collapse
Do us a favor... There is no issues with CWM & 4.2. Do your CWM checks, don't waste time.

ahalford said:
Do us a favor... There is no issues with CWM & 4.2. Do your CWM checks, don't waste time.
Click to expand...
Click to collapse
I'm not sure what all the issues were that I was reading about, but one I experienced was not seeing the CWM backup folder when connected to my computer. I like to transfer them there to save space on my phone. CWM puts it in the wrong folder for that in JB 4.2, although I think it can be moved.
I'm looking into Titanium now.

I have to say, as a former iPhone 3GS owner, that Apple made all this backup/restore stuff drop dead simple. Completely and utterly automatic even. Your average user would NOT be able to figure this out on an Android phone.

cwappy said:
So what did you do with that phone? I'm considering an RMA, especially since I seem to be the only N4 owner on here with this issue.
When mine crashes, it doesn't finish the backup and it goes to a blank screen. Only after having it plugged in for a minute or so will it actually start up. Like the battery was completely empty. And it only seems to happen when the % left is under maybe 70%. It's always completed in the 90% range.
Click to expand...
Click to collapse
It wasn't that much of an issue for me since I had multiple batteries. It would happen about once a week. The battery would soon and I would pop in a new battery. Ended up selling the phone to fund my Nexus.
Sent from my Nexus 4 using Tapatalk 2

Related

I figured out what drains the battery

Its rayanza's lag fix i just formated my internet sd card flashed vibrant 6 rom and did not apply any lag fix and guess what the battery is not draining anymore. But the phone lags is there a alternative to rayanza's lag fix?
And for the people with battery problems try it.. You will see
I have the lag fix and not one thing has changed for me but benchmark scores. Although I didnt have battery issues before so I do not know if it helped anything or not lol
flameinthefire said:
Its rayanza's lag fix i just formated my internet sd card flashed vibrant 6 rom and did not apply any lag fix and guess what the battery is not draining anymore. But the phone lags is there a alternative to rayanza's lag fix?
And for the people with battery problems try it.. You will see
Click to expand...
Click to collapse
You're wrong.
I have gone through 2 vibrants and now on my third one. First one never would lock a carrier signal to use it, so back it went. The 2nd i rooted and applied lagfix and had all sorts of issues, and than finally it just bricked and would just go to the first image boot over and over and over and never came out of it. Couldnt even get to recovery mode to just put back to stock. Third one now is working great without lagfix but is still rooted. I dont see the need for it to use lagfix just for it to open apps faster. Doesnt really do anything but that to me. Sorry.. im very new to this type of smartphone as i came from using blackberry for over 5+ years. My wifes vibrant has no issue at all so far but only rooted to use the wifi hotspot. As for the battery part i didnt really notice a differnce in battery time on the lagfix and the non lagfix vibrants i have.
no i am not i am speaking from experience there is no need for me to lie.
is there any other lag fix? i just applied it again to see if it makes a difference and it drained 10 percent in 5 mins so.......
The only one that i used was RyanZAEXT2LagFix BETA 2-3 when i used lagfix on my 2nd vibrant. But it just led up to issues after issues until the phone pretty much bricked. But i dont ever recall seeing any difference in battery drain.
You killed 2 vibrants? You sir are a bad bad man and I hope you had to pay for the third one full price. You should know what your doing before you do something to your phone.
Sent from my SGH-T959 using XDA App
This is the lagfix I use: http://android.modaco.com/content/s...fix-using-internal-memory-and-playlogo1-hack/ If you have Vibrant6 then just use ADB and type the commands in.
I prefer this lagfix,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
compared to RyanZA.. since I actually get more app space, Will I use it all? No. but its nice for whatever reason.
Quadrant Benchmarks:
Stock Kernel.
But when I did use RyanZA.. I didn't notice any battery life drains, so it's most likely something else.
I have the lag fix installed and haven't seen any difference in battery drain.
bauerlucas said:
You killed 2 vibrants? You sir are a bad bad man and I hope you had to pay for the third one full price. You should know what your doing before you do something to your phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im pretty certain i know i was doing.
The first phone was not even me at all. It was like that out of the box. Brought the phone home, put in my sim and nothing, no carrier network lock. Thought it might of been the sim card itself. Went to tmobile corp store and showed the phone and swapped out for new sim. It had the same issue.
Second phone carrier network locked fine. First thing i did was root it. Piece of cake. than did the lag fix.. no issues after install, than installed setcpu and juice up on it. after i set them up the phone would still get extremely hot and than basically reboot on its on even when i had setcpu clocked down to 800. 400 when screen is off. Even than when i did that the phone would go into a deep sleep and never come out unless i battery pull. uninstalled juice and setcpu seem to work where it wouldn't reboot, but still get extremely hot, not even being on it for 5-10 minutes. Than started to setup my emails and other apps and apps where forcing to close and freeze. phone calls would work but the screen would freeze where i could not get to the dial pad to enter numbers and look for contact info while on the phone, and than one day i was on the phone for like 2 minutes and the phone complete rebooted into the vibrant boot screen and loop at that only never getting past the vibrant boot screen image. It would just blank and go back to it, blank and go back. Took it back to tmobile and they never seen that happen.
Swapped out for third one now. Rooted but no lag fix and installed all same apps i use and emails etc.. and phone works flawless. So i don't think the lag fix is a necessity for me to use at this time. Only thing i saw with using it was that it open apps quicker. I dont see a huge point for me to use that if thats all it does. I dont see any other advantages of using lag fix at this time.
That's bad luck you made it sound like you briked your 2nd one installing the lag fix. I have not had any problems with my vibrant besides the gps. Well good luck man.
Sent from my SGH-T959 using XDA App
zephiK said:
This is the lagfix I use: http://android.modaco.com/content/s...fix-using-internal-memory-and-playlogo1-hack/
Click to expand...
Click to collapse
Ummm... That IS the RyanZA fix, just without the scripts to make installing it easier.
I've used all the lag fixes, and run without one. The battery doesn't really change with them. The biggest problem I've found is that something in the System process occasionally goes nuts and runs at 100% all the time. The phone gets hot and the battery drains very fast. You can see it if you get the System panel app and scroll to the bottom. Rebooting fixes it, so it's probably just a firmware bug.
ttabbal said:
Ummm... That IS the RyanZA fix, just without the scripts to make installing it easier.
I've used all the lag fixes, and run without one. The battery doesn't really change with them. The biggest problem I've found is that something in the System process occasionally goes nuts and runs at 100% all the time. The phone gets hot and the battery drains very fast. You can see it if you get the System panel app and scroll to the bottom. Rebooting fixes it, so it's probably just a firmware bug.
Click to expand...
Click to collapse
Oh it is? Never noticed, just noticed that when I applied the RyanZA's one-click, it would always appear with a error about low internal space so I tried the adb code one and ended up with more space. Thanks for the clarification!
bauerlucas said:
That's bad luck you made it sound like you briked your 2nd one installing the lag fix. I have not had any problems with my vibrant besides the gps. Well good luck man.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I dont think it was the lag fix itself. since it installed fine after i got the new phone and first thing i did was root it and applied lagfix very first two things i did with the 2nd phone. so i really dont know what it was or what happened. But oh well.
"Third times a charm" hehe
Have y'all tried disabling the phone's animations to help with lag?
settings > sounds and display > animation > no animation
Just set mine to that setting. Appears to be running quite a bit better.
I had the lag fix on mine last week but it crashed and I had to wipe the phone clean. I'm not too eager about doing it again.
flameinthefire said:
Its rayanza's lag fix i just formated my internet sd card flashed vibrant 6 rom and did not apply any lag fix and guess what the battery is not draining anymore. But the phone lags is there a alternative to rayanza's lag fix?
And for the people with battery problems try it.. You will see
Click to expand...
Click to collapse
For some reason, my battery would drain like crazy (stock, non rooted,) after about two weeks of usage. One day, I had pulled out the batter and noticed the 4th quarter of the battery was swelling. I called TMO and they sent me a new battery free of charge. No more battery drains and this one lasted a full day of work while blasting Pandora in my ears to cut out all the idiots yelling at each other. So, before you start blaming apps and lag fixes for battery drain, physically check your battery. These Li-Ion batteries do it, not all of them, just some of them. It also happened on my G1, which TMO would not replace it and I just took the battery out of a friends G1 who was sending it back for warranty work.
Edit: I have now rooted my phone, and with the old swelling battery after 3 hours of up time, and simple usage (mms, two short 5-6 minute phone calls and Terminal Emulator) I'm already at 64% off a full "off-state" charge. Meaning I charge my batteries while the phone is off so it doesn't drain while charging, as they say you should do. With my new battery with an "off-state" charge, 3 hours of uptime and I am sitting at 96% battery life with minor usage.
ttabbal said:
Ummm... That IS the RyanZA fix, just without the scripts to make installing it easier.
I've used all the lag fixes, and run without one. The battery doesn't really change with them. The biggest problem I've found is that something in the System process occasionally goes nuts and runs at 100% all the time. The phone gets hot and the battery drains very fast. You can see it if you get the System panel app and scroll to the bottom. Rebooting fixes it, so it's probably just a firmware bug.
Click to expand...
Click to collapse
Ive had a very similar issue happen to me, my battery was daining completely in under 2 hours. But I found restarting the phone corrected whatever process got hung up. I thought it was Ryan's fix.. and it's possible it might be linked to it, but I don't think it's necessarily the cause of it. Just a combination of things going wrong.
red96turbols said:
Edit: I have now rooted my phone, and with the old swelling battery after 3 hours of up time, and simple usage (mms, two short 5-6 minute phone calls and Terminal Emulator) I'm already at 64% off a full "off-state" charge. Meaning I charge my batteries while the phone is off so it doesn't drain while charging, as they say you should do. With my new battery with an "off-state" charge, 3 hours of uptime and I am sitting at 96% battery life with minor usage.
Click to expand...
Click to collapse
Please, do NOT use bulging batteries! They do that shortly before they fail internally and li-ions go up in a fireball when that happens.
You should dispose of that battery immediately. Don't have it in your home or near anything flammable. Treat it like it will spontaneously combust at any moment, as it has a good chance of doing exactly that.
my story is a bit different
I can personally say that RyanZA one click lag fix is what saved me from ultimately getting a different phone. I installed the lag fix one day and noticed I could go nearly 2 days on one charge with the same amount of usage. I did not install/uninstall anything other than apply the lag fix one weekend and bam, my battery is performing on par with what I'm used to on my old G1.

Stuck at 100%?

My battery is stuck at 100% and won't go down. Normally I'm not complaining about battery life in this way, but this is really weird. I'm running Paradigm by the way.
Fully charge your battery, then wipe your battery stats in CWM. If that doesn't work, then it's probably an issue with the ROM.
Sent from my Nexus 7 using xda premium
That didn't help, so I flashed the euroskank cm10 nightly, and I still have the issue. Ahhhh. I don't want to have more issues with this tablet. Any other recommendations?
Go back to completely stock and see if it works. Then you'll at least know if it's software related.
Sent from my Transformer TF101 using xda premium
I'm now stock unrooted, all set up. I'll run stock for now until the new Paradigm hits. Then, I'll try rerooting. If I run into this issue again on stock then I'll call Google, and probably just return it. I don't really want a third one. BTW, when it happened, recovery would also show 100% as a reading, but would usually go down to 99% after a while, and then when I rebooted, it would discharge at a normal rate, but would never compensate for the weird extra time at 100%. Does this point to a software or hardware issue?
Is it plugged in?
Lol no. It says discharging, 100%. But my screen was on for 31 min, and it said that and I'm pretty sure the n7 isn't rated for 30+ hrs screen on time.
Amphibliam said:
I'm now stock unrooted, all set up. I'll run stock for now until the new Paradigm hits. Then, I'll try rerooting. If I run into this issue again on stock then I'll call Google, and probably just return it. I don't really want a third one. BTW, when it happened, recovery would also show 100% as a reading, but would usually go down to 99% after a while, and then when I rebooted, it would discharge at a normal rate, but would never compensate for the weird extra time at 100%. Does this point to a software or hardware issue?
Click to expand...
Click to collapse
how long was it at 100%? its normal for it not to drop from 100% over a period of time, battery life is that good. heres a screenie from my n7 from yesterday..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
how long was it at 100%? its normal for it not to drop from 100% over a period of time, battery life is that good. heres a screenie from my n7 from yesterday..
Click to expand...
Click to collapse
I'm fairly sure 6+ hours with the battery still at 100% is not normal, unless it was asleep the entire time.
Sent from my Transformer TF101 using xda premium
just lou said:
I'm fairly sure 6+ hours with the battery still at 100% is not normal, unless it was asleep the entire time.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
majority of the time, i was busy at work. but, ive seen and some other people have seen 2+ hours at 100% with use. so, depending how long hes been watching it drop, it might be normal. especially since he said he saw it drop in recovery then drop after he booted up.
As I said earlier, battery was at 100% for 31 minutes of SCREEN ON. Then I rebooted, cleared caches, hung around in recovery for 5-10 min, saw it hit 99%, rebooted, and system said 99%. Like I said, that would mean I could get 30 HOURS of screen on time. NO WAY is that possible.
Amphibliam said:
As I said earlier, battery was at 100% for 31 minutes of SCREEN ON. Then I rebooted, cleared caches, hung around in recovery for 5-10 min, saw it hit 99%, rebooted, and system said 99%. Like I said, that would mean I could get 30 HOURS of screen on time. NO WAY is that possible.
Click to expand...
Click to collapse
that doesnt mean that you would get 31 hours. what you just described is normal and youre freaking out for nothing.
Maybe you have a super battery saving kernel try just to run it flat, then do a charge while the device is off
Amphibliam said:
As I said earlier, battery was at 100% for 31 minutes of SCREEN ON. Then I rebooted, cleared caches, hung around in recovery for 5-10 min, saw it hit 99%, rebooted, and system said 99%. Like I said, that would mean I could get 30 HOURS of screen on time. NO WAY is that possible.
Click to expand...
Click to collapse
my first day with the n7.. happy now? i ended up getting over 7 hours screen on time. you cant extrapolate 30 hours from it that way like you were doing.
This happened to me too.
After taking it off the charger it wouldn't go down. Now keep in mind my case I had left it overnight and hadn't played with it so I had at least a day in my battery info on 100%. Rebooted, then tried factory reset, all the normal stuff to try and nothing. Then tried CWM wiped everything then even reflashed the ROM and tried a different kernel after going back to complete stock it started decharging finally but now dies at 20%. It just turns off doesnt even shut down, and when it finally gets enough juice to start it would flash a little text message in the upper left "show low low battery logo". I finally managed after flashing CM10 then back to stock and charging and decharging a few times and deleting batterystats.bin from data and pulling the charger while it was booting to get it to realize there was an inbetween 0 and 17% and it sat charging for a while on 0, where it had just jumped straight to 18 but is now charging up normally again, that is where I am at.
I've got like 3 days left on my exchange with GameStop and I'm back and forth whether I should just take it back because I don't have any of this screen lift banter every talks about but don't want to end up with a faulty battery because it only just started here like last week.
People, the nexus 7's battery is not that good that it can go for hours without dropping 1%!!!
It could be that there is a problem with the battery indicator. That could be hardware or software.
tomb20 said:
People, the nexus 7's battery is not that good that it can go for hours without dropping 1%!!!
It could be that there is a problem with the battery indicator. That could be hardware or software.
Click to expand...
Click to collapse
say that in the trinity kernel thread, i bet just about everyone in that thread will disagree with you.
simms22 said:
say that in the trinity kernel thread, i bet just about everyone in that thread will disagree with you.
Click to expand...
Click to collapse
Even with the best kernel available.
Your saying that a 7" LCD can be turned on for hours without a 4325 mAh battery losing 1%!!!
And that's without system, apps etc running.
tomb20 said:
Even with the best kernel available.
Your saying that a 7" LCD can be turned on for hours without a 4325 mAh battery losing 1%!!!
And that's without system, apps etc running.
Click to expand...
Click to collapse
yup. remember, theres no 3G/4G radio sucking the battery juice dry.
Well, flash all stock, and watch the battery meter.
Flash a custom rom with stock kernel and watch the battery meter.
Flash a custom rom and a custom kernel and watch the battery meter, what do you get?
FYI, look at the screen on and total time at 50% battery, i bet you won't have double those time by time you hit 1% either.
You can't look at the first 30 minutes and go crazy over it. That's as bad as watching wakelocks and going crazy over wakelocks before you have an issue, wakelocks are normal and needed.
Stop obsessing, enjoy the tablet.

[Q] Battery from 45% to dead immediately?

Last night before going to bed I decided to turn my tablet off (it was around 45% battery left). When I tried to turn it on this morning, it was dead; no response. So I plugged it in and after a few minutes it booted up. I went to the battery settings and saw that it dropped off to dead pretty much instantly. Here's a screenshot after charging for a few hours.
Does anyone know how this happened, if it can happen again, or if it was just a random occurrence?
I'm on stock 4.2.2 rooted, and the only app I installed yesterday was "avast!" security to try it out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
drewgillesp said:
Last night before going to bed I decided to turn my tablet off (it was around 45% battery left). When I tried to turn it on this morning, it was dead; no response. So I plugged it in and after a few minutes it booted up. I went to the battery settings and saw that it dropped off to dead pretty much instantly. Here's a screenshot after charging for a few hours.
Does anyone know how this happened, if it can happen again, or if it was just a random occurrence?
I'm on stock 4.2.2 rooted, and the only app I installed yesterday was "avast!" security to try it out.
Click to expand...
Click to collapse
Same thing just happened to me only I had more than 45% and was using it at the time. The screen would flicker every time I would touch it and keep flickering for about 3 secs if I swiped to change home screens. Display went dark and was unresponsive. After plugging it in it finally booted and said I was at 0% battery.
OP: it could be a problem with the reported charge left in the battery, or a hardware defect that is grounding to the chassis and then through you that is sucking all the charge out. No app or anything can possibly drain the battery that fast, even at max load and max CPU speed constantly. The only way charge can leave a device that abrupt and by that large an amount is by a short somewhere in the hardware.
Vindico: sounds like a definite hardware problem to me and the tablet should be replaced. As I said above, there is no possible way in all of electronics and physics for a battery to be drained that fast and suddenly with our hardware in any situation other than a short in the hardware.
45% of charge loss in a few minutes is simply not possible without huge amounts of heat being generated... I assume the calibration or measurement is completely off... Or do you see bubbles coming out of your Nexus 10? :laugh:
I've had this happen to me twice, each around the same 45%. Except i must have caught it pretty much soon after it happened because the tablet was really hot each time, and took about 5 minutes of being plugged in before the charging icon would come up.
This happened to me today, and it happened 2 weeks ago.
While I don't have any technical advice to give, I purchased my tablet in December and Google is replacing my tablet free of charge.
Samsungs quality control on this thing has been pathetic. Here's hoping I get a better copy next time.
Cahce?
Have you tried clearing Battery stats? You should give it a shot, I have had a similar problem with my Galaxy S2 & S3.. It was fixed after i cleared the stats.
ExjeetzZ said:
Have you tried clearing Battery stats? You should give it a shot, I have had a similar problem with my Galaxy S2 & S3.. It was fixed after i cleared the stats.
Click to expand...
Click to collapse
Probably a coincidence. Android generates battery stats on boot always. Clearing them does absolutely nothing. That is straight from what Google said when it was all the rage to clear your battery stats when flashing a new ROM or kernel years ago.
Well I think its more of a reportage problem... I have this new nexus 10 which is showing the same problem..
Once my tablet screen flickered and went off... And it responded only after 10-15 min of charging...
Now also at times the battery status will get stuck at some particular percentage and wont update automatically however a reboot will set things straight...
Overall battery life is not diminished so the other scenario of battery being rapidly depleted due to some hardware is quite unlikely...
Besides the whole time the battery was stuck at one particular percentage was when i was actively using it and screen was on... So ideally the battery should have drained during this time...
Bringing this back to life, mine just died at 50%
Sent from my Nexus 10 using Tapatalk 4 Beta
I have the same problem. Battery is 100%, I disconnect charger and then few seconds/minutes and reset. After reboot it stop at X sign and reset again and again, and again.
When I connect charger Nexus can boot but it shows 0% empty battery! After few seconds/minutes battery shows 100% again.
So I think that my battery is broken (or battery controller at least).
In my opinion Nexus 10 has very poor quality during production (reboots, battery problem, heating problem etc.). So I'll never ever buy a Android tablet again, especially a Nexus line or from Samsung. It is unacceptable for me to sell product with so many bugs.
I just charged to full while the device was off and plugged in, and deleted the battery stats. I'll report how it goes.
Sent from my Nexus 10 using Tapatalk 4 Beta
No change after deleting battery stats, still shut down at ~32%.
Time for a warranty.
Exact same issue, 2 days in a row :/ Every time it reaches around 50% it powers off and won't turn back on without the charger :/ What do I do? I only got this on Wednesday!
Sent from my Nexus 10 using Tapatalk 4 Beta
Ughhh just had this happen to me. Hit 32% and boom shut off. Really lime the tablet but this is kind of a deal breaker. Anymore news of a fix. I'm running AOKP 4.2 right now.
Sent from my SCH-I605 using Tapatalk 2
jmill75 said:
Ughhh just had this happen to me. Hit 32% and boom shut off. Really lime the tablet but this is kind of a deal breaker. Anymore news of a fix. I'm running AOKP 4.2 right now.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Not sure about an actual fix, outside of a battery replacement, etc.
Mine is currently at Samsung for repairs, which has been "fun". I started by sending it in after describing the problem as "while discharging, the battery will drain as it should to about 50%, then immediately to 0% and the tablet shuts off saying the battery is dead". The original call taker, who was really nice, took it as a "charging problem" and didn't say anything to me. The repair status tracking online just said "component replaced" so I decided to call. Turns out they just replaced the charging port, nothing else. Not going to fix my problem though. So, I re-explained the problem and the nice lady said that she should transfer me to advanced tech support. Sweet! Finally someone who knows the issue! WOOT!! Someone named Robert totally understood the problem, put me on hold, and came back and said "Okay, so, just to make sure we really get the problem fixed, I'm having them replace the whole motherboard, battery, and the connection terminals that the battery hooks to" (I forgot the name). "We're taking the shotgun approach here, so hopefully it'll fix your problem. I'm also writing a better description of the light leak in the bottom corner, and having them expedite the repair since it's been here for 5 days already".
Robert, you sir, are my hero today.
snowboarda42 said:
Not sure about an actual fix, outside of a battery replacement, etc.
Mine is currently at Samsung for repairs, which has been "fun". I started by sending it in after describing the problem as "while discharging, the battery will drain as it should to about 50%, then immediately to 0% and the tablet shuts off saying the battery is dead". The original call taker, who was really nice, took it as a "charging problem" and didn't say anything to me. The repair status tracking online just said "component replaced" so I decided to call. Turns out they just replaced the charging port, nothing else. Not going to fix my problem though. So, I re-explained the problem and the nice lady said that she should transfer me to advanced tech support. Sweet! Finally someone who knows the issue! WOOT!! Someone named Robert totally understood the problem, put me on hold, and came back and said "Okay, so, just to make sure we really get the problem fixed, I'm having them replace the whole motherboard, battery, and the connection terminals that the battery hooks to" (I forgot the name). "We're taking the shotgun approach here, so hopefully it'll fix your problem. I'm also writing a better description of the light leak in the bottom corner, and having them expedite the repair since it's been here for 5 days already".
Robert, you sir, are my hero today.
Click to expand...
Click to collapse
Who did you contact for repair? There was nothing in my warranty book about who to contact. The pay store said to contact Samsung directly for the nexus 10
Sent from my SCH-I545 using Tapatalk HD
Okay I had the same problem that everybody else here has had. I have reflashed the stock rom and unrooted and locked my Nexus and everything seems to be working perfectly since then. No more reboots freezes or incredibly large battery dropping since then.
Sent from my Nexus 10 using Tapatalk HD

4.2.2 update turned the sceen a vampire ready to suck my battery life

Well the topic tells pretty everything i used to have no real issues with the battery life of my phone, till i got the kitkat update. Since then as soon sa i turn the screen on i can really see the battery % drop. I mean 1% for minute of usage. And the back turns Hot.
I'm pretty confused since i have not read such kind of problem around here. I already greenified what i can (no root). And hard and chache reset too..
Any other idea about the nature of the issue (9005 model) Tank you!!
You forgot the garlic.
Those Samsung battery draining problems are really getting ridiculous. But what's funny, i owned 5 Samsung phones till now, but never had any issues. I know, I'm not helping...
Sent from my N9005
This is my first samsung device, and actually i was really happy about my battery life and when i got the notification of the 4.4.2 update i was even more happy cause i was sure that it would have improved it even more. LOL.
What amazes me is that even if there's clearly something wrong, and even if the note is a company flagship, there is no plan for a patch -.-
Aleckxander said:
This is my first samsung device, and actually i was really happy about my battery life and when i got the notification of the 4.4.2 update i was even more happy cause i was sure that it would have improved it even more. LOL.
What amazes me is that even if there's clearly something wrong, and even if the note is a company flagship, there is no plan for a patch -.-
Click to expand...
Click to collapse
I had this problem - i cleared cache in recovery then charged to 100% and it appears to be fixed now? Hope it doesnt come back
Not related to the topic . But am i missing something as most of the people call 4.4.2 as 4.2.2 ?? is that a joke or a mistake ??
Aleckxander said:
Well the topic tells pretty everything i used to have no real issues with the battery life of my phone, till i got the kitkat update. Since then as soon sa i turn the screen on i can really see the battery % drop. I mean 1% for minute of usage. And the back turns Hot.
I'm pretty confused since i have not read such kind of problem around here. I already greenified what i can (no root). And hard and chache reset too..
Any other idea about the nature of the issue (9005 model) Tank you!!
Click to expand...
Click to collapse
Try a fresh flash and wipe the device, usually fixes it.
Dejan Sathanas said:
You forgot the garlic.
Those Samsung battery draining problems are really getting ridiculous. But what's funny, i owned 5 Samsung phones till now, but never had any issues. I know, I'm not helping...
Sent from my N9005
Click to expand...
Click to collapse
lol - I've only ever had the issue on my Note 3 - never had it on my S3 or any other device.
fahadali2315 said:
Not related to the topic . But am i missing something as most of the people call 4.4.2 as 4.2.2 ?? is that a joke or a mistake ??
Click to expand...
Click to collapse
ropably jst a tpoy
radicalisto said:
ropably jst a tpoy
Click to expand...
Click to collapse
i boudt taht>
radicalisto said:
Try a fresh flash and wipe the device, usually fixes it.
Click to expand...
Click to collapse
I'm quite new with all of these matters.. This "fresh flash" you are talking about will trigger that infamous bit? Would you be so nice to address me to a topic where i can read how to proceed with such fresh flash procedure?
radicalisto said:
ropably jst a tpoy
Click to expand...
Click to collapse
LOL
P. S. 2% battery Juice went lost to write this post.. Gimme that garlic! NOW
Aleckxander said:
I'm quite new with all of these matters.. This "fresh flash" you are talking about will trigger that infamous bit? Would you be so nice to address me to a topic where i can read how to proceed with such fresh flash procedure?
LOL
P. S. 2% battery Juice went lost to write this post.. Gimme that garlic! NOW
Click to expand...
Click to collapse
A fresh stock flash won't trip Knox no. So long as you are flashing
A)The same firmware
B)Not trying to downgrade
---
Grab the stock ROM you require from one of the threads in the General section of the Note sub forum.
Grab Odin 1.85.
Once you download the .zip file, unzip and you should get an .md5 file around 2GB in size.
Put your phone into download mode, plug into PC, fire up Odin and load the .md5 file into PDA/AP slot. Hit start. Grab a beer and chill until it has finished.
Have a read through the threads with the different ROMs though, sometimes there can be minor issues with file sizes etc which then require a PIT file, but you should be OK tbh
Sent from my Nexus 5 using XDA Premium 4 mobile app
Thank you!! I'll try tomorrow i'll keep you updated
Aleckxander said:
Thank you!! I'll try tomorrow i'll keep you updated
Click to expand...
Click to collapse
Look at usage under settings, general, battery. if you see mm-qcamera-daemon at the top....you've got a known issue with KitKat.
Sent from my Note 3 via Tapatalk
I installed battery doctor and the problem disappeared with a default diagnosis and optimisation. I'm rooted, not sure if that makes any difference.
Clicky
I'd really like to root my phone and finally have some serious fun with it, but i'm not really a guy who like to take a risk like this.. It's not a budget phone and i do not want to pay for some factory issue, even if this is a real bad move by samsung and i won't ever buy a samsung device again for this reason, but in the meanwhile i have to try to take the best from my unrooted phone.
I've already read the camera issue, my note do not fall into it.. As i said the Phone act very good and is really energy savvy, until i wake up the screen, this literally drinks the battery juice.. 1% per minute! Less or more.. And no matter if i lower the screen brightness.
As soon as i'll have some spare time i'll try that fresh flash procedure
fahadali2315 said:
Not related to the topic . But am i missing something as most of the people call 4.4.2 as 4.2.2 ?? is that a joke or a mistake ??
Click to expand...
Click to collapse
n00b's bro. Mistake, just like allowing them on this forum.
Same as everyone having issues with battery life on the Note 3 /w 4.4.2. All n00bs.
The very fact that n00bs think that Sammy would release a ROM with obvious issues? No. Not going to happen.
The issue lies with the end user. Period.
Aleckxander said:
Well the topic tells pretty everything i used to have no real issues with the battery life of my phone, till i got the kitkat update. Since then as soon sa i turn the screen on i can really see the battery % drop. I mean 1% for minute of usage. And the back turns Hot.
I'm pretty confused since i have not read such kind of problem around here. I already greenified what i can (no root). And hard and chache reset too..
Any other idea about the nature of the issue (9005 model) Tank you!!
Click to expand...
Click to collapse
Yep, join the KitKat bug club. Note 3 users are having horrendous battery drain issues with 4.4 along with wifi instability and cellular network drops. I went through 3 Note 3's until I finally gave up and decided to stick with 4.3, the hassle was not worth it at all.
My battery usage went to crap with Kitkat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HothTron said:
Yep, join the KitKat bug club. Note 3 users are having horrendous battery drain issues with 4.4 along with wifi instability and cellular network drops. I went through 3 Note 3's until I finally gave up and decided to stick with 4.3, the hassle was not worth it at all.
My battery usage went to crap with Kitkat.
Click to expand...
Click to collapse
You wiped data and cache in recovery correct?
i
Aleckxander said:
Well the topic tells pretty everything i used to have no real issues with the battery life of my phone, till i got the kitkat update. Since then as soon sa i turn the screen on i can really see the battery % drop. I mean 1% for minute of usage. And the back turns Hot.
I'm pretty confused since i have not read such kind of problem around here. I already greenified what i can (no root). And hard and chache reset too..
Any other idea about the nature of the issue (9005 model) Tank you!!
Click to expand...
Click to collapse
I got this issue and solved it in this way;
let ur phone to discharge ~15% or less
then turn off ur phone and connect it to charger
and let it to charge 100% then turn ur phone on.
It s like re-gauge battery.
there s some apps for it on some laptops but nothing yet for smartPhones
:good:
x102x96x said:
I got this issue and solved it in this way;
let ur phone to discharge ~15% or less
then turn off ur phone and connect it to charger
and let it to charge 100% then turn ur phone on.
It s like re-gauge battery.
there s some apps for it on some laptops but nothing yet for smartPhones
:good:
Click to expand...
Click to collapse
Had to do this with multiple phones before. By doing this and factory resetting I can guarantee you will not have issues with battery drainage.
nexxusty said:
You wiped data and cache in recovery correct?
Click to expand...
Click to collapse
Wiped data partition and did factory reset on KitKat on TWO Note 3's. Same result. KitKat is a POS
HothTron said:
Wiped data partition and did factory reset on KitKat on TWO Note 3's. Same result. KitKat is a POS
Click to expand...
Click to collapse
Then why is mine perfectly fine?
Exact same as Jelly Bean. The radio acts a bit different, battery life is identical.
I still think these are the dreaded PEBKAC error. Or in this case a "PEBPAC" error.
Flashed mine with Odin 3.09... hmm.

GT-i9505 weird battery behaviour

I've got this weird battery level increase every time after usage period and when phone is in standby. Long ago I had something similar with a cheap "original" battery from amazon which was surely a product falsification. But the battery I'm using now I purchased directly from Samsung online shop and it worked flawlessly for over half a year. About a year ago I switched to a S5 and didn't use the S4 that much anymore.
What I did so far:
- I calibrated the battery (guide by @lawyer_06)
- did couples 0 to 100% charging
- cleared system cache
- updated rom to latest (TW deodexed/stock kernel)
-> nothing changed
Any Ideas what's going on here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The battery percentage display is an approximation of the battery level, it's not the actual level.
With high usage it may start to approximate it wrongly, but in the standby phase it will start slowly going back to a value closest the the actual level.
Doing the 100-0 discharge is most damaging. If you want to keep this battery for a longer time, then stop.
Also, this is completely normal. Happens on my phone which runs the same battery I bought it from the store with, and the same happened on my previous phone which also used the original battery it was bought it (and it wasn't a Samsung).
Just to add, battery calibration routines don't do anything except waste battery cycles: they only delete batterystats.bin, which is deleted anyway when the battery is fully charged. Stop trying to calibrate the battery.
Pwnycorn said:
...
Doing the 100-0 discharge is most damaging. If you want to keep this battery for a longer time, then stop.
Also, this is completely normal. Happens on my phone which runs the same battery I bought it from the store with, and the same happened on my previous phone which also used the original battery it was bought it (and it wasn't a Samsung).
Click to expand...
Click to collapse
Partially disagree:
Sometimes a 0 to 100% charging IS necessary to get a "digital reset", means the bat controlling system driver and the bat hardware need to be synchronised from time to time, especially when you sometimes take out the bat or even replace it with another one. And I really don't agree that this behaviour is "normal", I really never ever had s'thing like this with none of my Galaxy S phones (2-5) when using a original bat.
But thanks anyways for your thoughts.
Strephon Alkhalikoi said:
Just to add, battery calibration routines don't do anything except waste battery cycles:...
Click to expand...
Click to collapse
All the same what I wrote above to you. But thanks.
v00d007 said:
Partially disagree:
Sometimes a 0 to 100% charging IS necessary to get a "digital reset", means the bat controlling system driver and the bat hardware need to be synchronised from time to time, especially when you sometimes take out the bat or even replace it with another one. And I really don't agree that this behaviour is "normal", I really never ever had s'thing like this with none of my Galaxy S phones (2-5) when using a original bat.
But thanks anyways for your thoughts.
Click to expand...
Click to collapse
I've never had to synchronize anything. Is there any actual evidence to what you're saying?
I've taken my battery out many times, and I even had 2 batteries that I alternated between at some point.
And does this problem bother you that much? I already told you it has happened on 2 of my phones, both of which used the factory original battery.
Maybe you have never paid attention to it before.
v00d007 said:
All the same what I wrote above to you. But thanks.
Click to expand...
Click to collapse
Then you're a fool. Lithium ion batteries don't need calibration. The circuitry within the battery is designed to not only ensure the battery doesn't overcharge, but also that the battery's cells charge evenly. Claiming the battery needs "synchronization" is a load of horse crap, in that it's justification to treat the battery like an old NiCd.
Whatever. You go ahead and waste your time, and shorten the life of your battery. Perhaps on your next phone you'll get a clue.
Strephon Alkhalikoi said:
Then you're a fool. Lithium ion batteries don't need calibration. The circuitry within the battery is designed to not only ensure the battery doesn't overcharge, but also that the battery's cells charge evenly. Claiming the battery needs "synchronization" is a load of horse crap, in that it's justification to treat the battery like an old NiCd.
Whatever. You go ahead and waste your time, and shorten the life of your battery. Perhaps on your next phone you'll get a clue.
Click to expand...
Click to collapse
Sorry, but your comments are a bit off topic. It's the battery LEVEL INCREASE in standby what's irritating me and what's surely not meant to be like this. You just have to READ what I'm describing here. No need to be rude, I'm neither. [emoji6]
Pwnycorn said:
I've never had to synchronize anything. Is there any actual evidence to what you're saying?
I've taken my battery out many times, and I even had 2 batteries that I alternated between at some point.
.
Click to expand...
Click to collapse
I've expierienced quite a few times that battery level isn't calculated correctly AFTER doing things like this in row: flashing something with odin that goes wrong somehow, getting bootloop afterwards, no buttons work so taking out the bat for reset, flash something else to fix the boot problem and so on - after such procedure I sometimes had inconsistent battery stat, so that the phone i.e. shut down while showing 10%.
And concerning "original" batteries, I can tell you that the leading german computer magazine (c't) discovered in 2016 that so called "original" Samsung batteries that are sold at the german amazon/am.marketplace are up to 80% (!!) product falsifications from China. This "copies" have reached a such incredible high level of professionality that even for experts it's really hard to identify them as fakes. The only secure way to get a 100% original one is from the Samsung online shop. I had such a fake too and wondered why this bat life was so bad + this wierd battery behaviour I'm talking about here. But this time it's different cause the bat I'm using atm is surely a original one.
https://m.heise.de/newsticker/meldu...ef=https://duckduckgo.com/&wt_t=1489485953395
v00d007 said:
I've expierienced quite a few times that battery level isn't calculated correctly AFTER doing things like this in row: flashing something with odin that goes wrong somehow, getting bootloop afterwards, no buttons work so taking out the bat for reset, flash something else to fix the boot problem and so on - after such procedure I sometimes had inconsistent battery stat, so that the phone i.e. shut down while showing 10%.
And concerning "original" batteries, I can tell you that the leading german computer magazine (c't) discovered in 2016 that so called "original" Samsung batteries that are sold at the german amazon/am.marketplace are up to 80% (!!) product falsifications from China. This "copies" have reached a such incredible high level of professionality that even for experts it's really hard to identify them as fakes. The only secure way to get a 100% original one is from the Samsung online shop. I had such a fake too and wondered why this bat life was so bad + this wierd battery behaviour I'm talking about here. But this time it's different cause the bat I'm using atm is surely a original one.
https://m.heise.de/newsticker/meldu...ef=https://duckduckgo.com/&wt_t=1489485953395
Click to expand...
Click to collapse
The battery I'm using now is 100% original. I bought the phone brand new back in 2014 from a renown electronics store here in my country.
This self charging phenomenon doesn't happen only when the battery is in the phone. I mentioned that I used to alternate between two batteries, right?
Well, while stock battery was out, and secondary battery was in the phone, the stock battery used to have up to 10% more charge than when I did the switch.
So if I switched it at 50%, when I switched back it had 60%.
Someone once said that it's a sign of a healthy battery. I don't know about this. But you should stop worrying about it, I'm telling you it's normal.
Or you can have it your way and do a couple of more software changes, ROM changes, battery changes and whatever else, until you come to the realization that there's nothing wrong with it.
The only time you should be concerned, in my opinion, is when your phone shuts down prematurely.
Pwnycorn said:
....until you come to the realization that there's nothing wrong with it.
.
Click to expand...
Click to collapse
I'm not "worried", I just want a reliable status that I ALWAYS had before. I guess there's something broken either in software, blootloader or hardware. The issue even persists with another orig bat a friend gave me yesterday and no matter which rom, TW or cm12, 13 that I tested in the meantime.

Categories

Resources