I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?
I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12
Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.
The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.
If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.
Hi,
A few days ago I upgraded my Note from a very ancient (stock) Gingerbread ROM to (stock) Jellybean. I hadn't been getting OTA updates because the Gingerbread was originally German rather than UK, so quite a long time had passed without any updates. Anyway, because of the no OTA, I used Odin. Everything went fine and I had a nice few days of usage, although the battery consumption seemed to suddenly be quite high, mainly due to additional wakelocks from the new Google Search it looked like. The night before last at about 3% the phone turned itself off, which is unusual as normally the battery will run itself lower than that. BTW, it's an official battery bought just a few months ago to replace the one before, which was getting old.
Yesterday evening when I went to use the phone it was dead. Completely unresponsive. It wouldn't charge either. (The battery had been at about fourteen percent I think, so it should have still had a lot of juice left.) Turning it on would leave it stuck on the Samsung logo only. Recovery mode didn't work, but I could get download mode up, so I installed the Philz kernel as people have said, and then did a reset using that, and all was okay again and after reflashing the ROM I could use the phone again, although because of the reset I had to set everything up again.
Just wondering what people think caused it. Just a weird coincidence, or something else? As far as I'm concerned, the problem has been sort of mitigated for now, but definitely not fixed, because what's to stop it happening again? Has anyone heard of strange things going on with Jellybean? I know there's an issue with flashing/resetting from ICS, but I never used that so I don't think that's an issue, and it looks like it was just a soft brick only. Still, a bit weird and worrying. Does anyone have any ideas?
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
XxPixX said:
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
Click to expand...
Click to collapse
I didn't take the battery out though. It was low but not dead.
Since then it has happened once again, a few days ago, this time at 93% full. I was doing nothing at all taxing to the phone. I was just in a shop listening to an mp3 with the screen off, and then it stopped and the next thing I saw was the bootloop. Luckily (thanks to the new kernel?) I could just delete cache/dalvik and be back up and running again without having to reinstall everything. Today my screen temporarily went a weird purple colour like in this thread: http://forum.xda-developers.com/showthread.php?t=2216867 . Sounds like it's just dying in general really, rather than anything else. My phone contract upgrade date is in two days. Purely a coincidence of course. Weird how phones tend to last about the length of a mobile phone contract. Until then I'm just running on power saving mode and hoping for the best.
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
this should not be in the general sections, but in the Q/A help section...
have you tried reflashing the stock img?
I had some major issues like that after updating to 5.0.1. I'm on cm now but if you flash back to stock it should fix things too
Sent from my Nexus 6 using Tapatalk
Harmanpreet Singh said:
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
Click to expand...
Click to collapse
Stock Nexus 6, or are you using custom stuff?
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Harmanpreet Singh said:
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Click to expand...
Click to collapse
Happened to me too today.got n6 on 11th Dec.initially reboots started then after 2 weeks of observations I turned off ambient display and now random shut downs..
Phone turned off on 14 % battery just when I picked up an incoming call..then again turned off when there was a call..really fed up of this issue..
Don't know if its a hardware or software issue..
backup your phone, reflash stock img completely, and test without restoring apps.
[email protected] said:
Happened to me too today.got n6 on 11th Dec.initially reboots started then after 2 weeks of observations I turned off ambient display and now random shut downs..
Phone turned off on 14 % battery just when I picked up an incoming call..then again turned off when there was a call..really fed up of this issue..
Don't know if its a hardware or software issue..
Click to expand...
Click to collapse
I've never had a random reboot but I have had the random shutdown issue. This was running stock 5.0.1 with stock kernel. Also had the same occurrence on CleanRom with stock kernel (this is basically a stock rom/kernel with a few tweaks. Another user recommended flashing LeanKernel which I did and haven't had a problem since. This random shutdown was happening roughly once per day. I have been running strong for almost a week now I'd say. I always am the guy to run custom roms and kernels myself anyways but I actually don't mind the stock rom so flashing the kernel was no big deal to me. There are a few threads on this subject if you search the forums. I too am hoping this isn't hardware related since it's always a pita dealing with RMA.
Is there anything new onto that? Any possible solutions? Same issue for me, generally happens during calls ... :/
hmm strange, i never had any shutdowns, could be either your rom or kernel your on. make sure the kernel your using with ur rom is compatible
Harmanpreet Singh said:
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Click to expand...
Click to collapse
I was just looking for this.
Mine started doing the same.
I have the battery saver set to 5%, but it never turns on!
The phone shuts off between 10% and 5%.
The battery saver turns on for only for a few seconds(if at all) and the phone shows the powering off animation.
Connecting the charger and turning the phone on, after booting shows 8% already.
Its not normal, because i remember having my phone at 1% without any problems for tests when i got it in November...
For the last few weeks i never went lower than 25% so i don't know when this started, but since i found this out(5 days ago), i tried it every day and it happens like clockwork. Flashed the factory image back has no effect( i was on stock anyways).
Hoping not to have a replacement to save the cost of my dbrand and screen protector...
I give it one more week and if it doesn't change i call Moto. I have MotoCare so replacement should be easy.
Harmanpreet Singh said:
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
Click to expand...
Click to collapse
Same here ....
Hi guys,
My 2 month old nexus 6 is powering down unexpectedly. Random shut downs (not reboots). Thought it was snap chat was the culprit (read a few articles how some 3rd party camera apps can cause lollipop to power down) but the phone shuts down even after uninstalling all suspicious apps.
Any advice or suggestions will be highly appreciated
Devs please help
I'm starting to really wonder if these "turbo chargers" are causing major degradation to the batteries. The phone will shut down when the battery *voltage* drops below a specific threshold, regardless of what the percent display is actually at.
Another thing to consider is that adding a significant load to a battery will cause it to read a lower voltage, even if that load does NOT immediately deplete the battery, those who notice this happening when running a very demanding game could be experiencing this. I would suspect though, that this will only be an issue if the battery level is already fairly low.
Any update on this?
5% is still my dead-spot and nothing i tried helps...
I just ordered my nexus but my s5 (current phone) randomly reboots. We figured it was due to volte. Turned that off on the s5 and no issues so far. Was really tired of it and the reason I'm going to nexus. That and the bigger screen
Sent from my SM-G900T using Tapatalk
Same issue here...
It must be caused by a bad batch of battery defects, Factory reset or re-flash factory image won't fix it... To get a replacement from Google seems to be the right way...
Davzone said:
I was just looking for this.
Mine started doing the same.
I have the battery saver set to 5%, but it never turns on!
The phone shuts off between 10% and 5%.
The battery saver turns on for only for a few seconds(if at all) and the phone shows the powering off animation.
Connecting the charger and turning the phone on, after booting shows 8% already.
Its not normal, because i remember having my phone at 1% without any problems for tests when i got it in November...
For the last few weeks i never went lower than 25% so i don't know when this started, but since i found this out(5 days ago), i tried it every day and it happens like clockwork. Flashed the factory image back has no effect( i was on stock anyways).
Hoping not to have a replacement to save the cost of my dbrand and screen protector...
I give it one more week and if it doesn't change i call Moto. I have MotoCare so replacement should be easy.
Click to expand...
Click to collapse
I use to have this issue. However, it has not happened since I started using Franco kernel. Multiple people have had the problem resolved by changing kernels. That leads me to believe that it is software related rather than hardware. Other benefits of flashing Franco for me is I can now use the built in led for notifications and I am using double tap to wake.
joshpdavis80 said:
I use to have this issue. However, it has not happened since I started using Franco kernel. Multiple people have had the problem resolved by changing kernels. That leads me to believe that it is software related rather than hardware. Other benefits of flashing Franco for me is I can now use the built in led for notifications and I am using double tap to wake.
Click to expand...
Click to collapse
My battery issue happened after I kept using Franco for a while...then I switched back to elementalX or stock kernel, nothing resolved...
if the back cover doesn't peel off or the battery doesn't start to expand, it might be a good sign that it is just a software issue.
Otherwise, battery defect could be happening already, as in my case...
Changing kernels fixed my issue which was the phone shutting down on its own randomly. I guess some of you are experiencing a different problem.
Davzone said:
Any update on this?
5% is still my dead-spot and nothing i tried helps...
Click to expand...
Click to collapse
Just a little update.
I did an advanced replacement with motorola.
Did it over chat on sunday, received the new phone on wednesday from texas.
Deposit was 500+tax.
The phone was brand new unopened box. Cloud White 64GB
The package had a box and a prepaid label to send the bad phone back.
The box was too small to fit a nexus 6, so i had to modify it a bit.
It was probably for the moto X or smaller.
Sent the phone back on Friday, they got it on Monday, and my money was back.
Everything looks great, the new phone can go down to 1% no problem.
The new turbo charger does not have the electrical noise that the old one has.
That may caused the battery problem. Using it since last Wednesday, and no problems so far.
The advanced replacement was great and easy, if i have to i would do it again, although in 3 months its gonna be a refurb device not a now.
Mine was in mint condition, had dbrand on and no scratches. The person who will get it after me will be happy with that refurb device
And i am happy with my new phone.
If the HTC M9 will have a GPE edition i might switch
Hey Everyone! Want to share with all about this problem i have been facing.
This GT-N7000 of mine has a very strange problem that has been bugging me since the beginning.
Be it using stock ROM (the days of being in totally stock ICS and jellybean ROM) or now, when i use CM11 4.4.4 (Created by the nice people here on XDA and cyanogen), if i leave the phone idle (e.g screen locked and turn off, when i don't use it and place it in my jeans pocket or lying on the table), once every few days (basically whenever the phone feels like it), when not connected to the charger, it will:
1) randomly decide to become unresponsive (means you can't wake the phone up when pressing any physical buttons or touching the screen)
2) Phone becomes hot while in this unresponsive state (I assume the processor is fully utilized, but doing something totally irrelevant and silly)
3) Need to do a battery pull before you can turn on the phone again
4) Notice upon boot that x% of battery was used up. The battery stats would indicate a break, and sudden drop from 72% of battery to 48% battery.. In other words, it seems the phone does not know what it was doing when it was unresponsive. The faster you catch the phone in this state, the more battery you'll have left. if this happens and you didn't catch the phone in this state, the phone would happily guzzle all the life out of your battery, to 0%.
Now that i am rooted and running CM11, i Digged a little deeper, and it seems that after each unresponsive state reboot, setCPU will indicate that there was alot of CPU usage at 1.4Ghz. At first i didn't bother about it, until i remembered my CPU settings was only supposed to run at 500mhz Maximum when my screen is off, or at 1Ghz when battery is below 80% and screen is on. My CM11 kernal is standard kernel and has NO overclock/underclock.
This means the phone somehow managed to overide setCPU while being in unresponsive state and remain clocked at 1.4 ghz even though the screen is off, thus draining the battery extremely quickly and becoming hot
I have tried multiple factory resets with Stock rom, then Re-flash stock rom with ODIN, to changing to CM11 ROM, and i still have this issue. I do not have a sim card Or SD Card plugged into this phone. (Even with sim card/sd card connected, it still has this issue)
Any other users that encounter this? And has anyone found a way to solve this? Thanks for your inputs!
I currently have a Sony Z1 Compact which I think the battery thermal sensor is broken...
It all started with, I have a Euphoria OS with android lollipop 5.1 installed and one day I was copying videos into phone, and then during that time.... my phone sudden rebooted when I was transferring videos from my laptop, and not just normal reboot, it keep on rebooting every time it succeed on loading into the OS. (Yes it will reboot every time it reached the lock screen....)
And I also tried restoring a backup it was the same too... so I decided to charge the phone instead of letting reboot, but sadly it won't charge too! So I just decided to leave my phone to run dry and then only charge it back to see if it will work again. I can still enter fastboot and flashmode during this time.
After it ran dry, I can't charge it, I can't enter fastboot nor use flashtool to flash back to stock too, so I decided to spend some money on getting a battery replacement.
Once I got my battery replacement, I instantly flashed back stock (yup with some capacity in battery I can enter fastboot) and I just found out that when I plug my phone to charge it shows "Your device turned off due to overheating ,charging will continue once the device cools down." even know the battery isn't heating, so I felt bad for the old battery as I assume it was in good condition but the phone just refuses to charge it!
So after researching I ended up with, I think the battery thermal sensor is broken and I saw something such as kernel has setting that can disable battery throttle, but I know it's risky but I don't use my phone much, all I use it is for listening to music, messaging if I receive a SMS or maybe a short call which won't go more then 2mins.
I want to ask if I can actually disable thermal throttle via recovery because even now that I installed back to stock it's the same still ( I still get reboots after every time it loads finish the OS, weirdly for custom ROMs it will run finish till optimizing apps finish then only it will show the "Shutting down..." message ).
I can provide my TWRP backup of my Euphoria OS upon request and I hope that someone can help me out!
Thank you very much and I hope that you can help me out! (Sorry English isn't actually my native language but I checked twice for spelling errors so I hope you can understand my situation!)