Related
I've had my I747 at&t now for 6 months, about 2 weeks ago It started shutting down on me on it's own, at that time I was rooted and had a custom rom installed that was working perfect. It was the HighOnAndroid ROM v0.3 from galaxys3root.com. There were no problems at all until 2 weeks ago too. So I used Kies to factory restore and upgrade to1747UCDLK3 to see if it was my rom I I had installed. My phone works now, but I have a problem with the battery I can't figure out.
here's what it does, I charge my battery at the end of the day to 100% and turn it off, then the next morning it's always down to around 70% even though it is off all night. It didn't do this before at all, have you had this issue or can give me some advice? thank you
Edit...FYI I use this phone on Straight Talk and have reformatted my 32 gig sd too just to start clean.
Chocketbear said:
I've had my I747 at&t now for 6 months, about 2 weeks ago It started shutting down on me on it's own, at that time I was rooted and had a custom rom installed that was working perfect. It was the HighOnAndroid ROM v0.3 from galaxys3root.com. There were no problems at all until 2 weeks ago too. So I used Kies to factory restore and upgrade to1747UCDLK3 to see if it was my rom I I had installed. My phone works now, but I have a problem with the battery I can't figure out.
here's what it does, I charge my battery at the end of the day to 100% and turn it off, then the next morning it's always down to around 70% even though it is off all night. It didn't do this before at all, have you had this issue or can give me some advice? thank you
Edit...FYI I use this phone on Straight Talk and have reformatted my 32 gig sd too just to start clean.
Click to expand...
Click to collapse
Are you still rooted and on the stock 4.1.1 ?
This has been going on for two weeks ?
hednik said:
Are you still rooted and on the stock 4.1.1 ?
This has been going on for two weeks ?
Click to expand...
Click to collapse
No, kies removed the root and I'm on jelly bean"which was samsungs update
Chocketbear said:
No, kies removed the root and I'm on jelly bean"which was samsungs update
Click to expand...
Click to collapse
I never used the plain stock with Keis update. I would normally just suggest to just flash it again. Are you opposed to rooting again and installing a customer recovery or do you want to stay completely stock ?
hednik said:
I never used the plain stock with Keis update. I would normally just suggest to just flash it again. Are you opposed to rooting again and installing a customer recovery or do you want to stay completely stock ?
Click to expand...
Click to collapse
No, I liked it rooted....just trying to figure out what happened. I just don't understand how the battery can drain that much if the phone is off. I may reroot of I can get past this part, It's seems to run down no matter which rom is on it.
I would reccomend gsam battery monitor and cpuspy. That should help determine the problem. It helped me when I had a similar issue.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Powered off or sleeping?
If you physically turn the phone off (not just sleep mode), then something is up with the battery.
Try powering to 100% charge, then discharge all the way down to 5%. Then charge to 100% again and see if that helps.
My phone was only ever able to charge to 70% for a few days. A complete discharge was able to fix it for me.
CZ Eddie said:
Powered off or sleeping?
If you physically turn the phone off (not just sleep mode), then something is up with the battery.
Try powering to 100% charge, then discharge all the way down to 5%. Then charge to 100% again and see if that helps.
My phone was only ever able to charge to 70% for a few days. A complete discharge was able to fix it for me.
Click to expand...
Click to collapse
It's shutting down, but i cant say I've ever let it get down to 5%, I just top it off. I did charge it to 100% one night , remove the battery and reinstalled it the next morining, It was still 99% by leaving it out of the phone, go figure, I 'll try your tips too
boothcr79 said:
I would reccomend gsam battery monitor and cpuspy. That should help determine the problem. It helped me when I had a similar issue.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll check those out too
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Take your battery out and place it on a flat surface. Try to spin it. If it spins, it's time to replace it.
Sent from my SPH-D710 using xda premium
Try a stock rom for a few days if the battery seems fine. My phone has the sleep of death issue with various jellybean AOSP based Roms.
deviouskind said:
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Click to expand...
Click to collapse
One thing I've noticed. My Battery will get extremely hot. I'll pull the battery, wait for 5 min, put the Battery back in and will be able to proceeded.
Just my $.02 worth
It's certainly the battery, only fix is to replace it.
Happens to me once every other day. Not a big problem just take out the battery and replace it back in.
I'm about to change the rom temporarily from goodness to blu kuban to see if it continues.
If it does then it has to be a battery issue at least on my end...
Sent from my SPH-D710
Time for a new battery.
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Battery issue with Galaxy SII
The shutdown issue seems to be inherent in many SII regardless of carrier. I have had this problem with my Sprint phone since new. It has been exchanged twice thus far but the problem continues. Samsung will tell you to do a factory reset. DONTdo it. It will not fix the problem.
It is NOT the battery in most cases.
It seems to be OS related. I have cleaned the battery contacts; not charged unless below 20%; unchecked the Power Saver and Optimization functions; and did a factory reset without loading in any additional apps for awhile. Nothing stopped it from shutting down.
I was able to prevent shutdown for about a two week period by not charging it until it went below 20%.
I did notice that my RAM consumption was over 60% prior to the phone acting up.
Could it be a memory issue?
Thus far, I have not received any real support from Samsung or Sprint. The Galaxy SII is one of the few phones that cannot be run through a diagnostc test by Sprint. If you have warranty coverage, they will replace it but I can almost guarantee the problem will beda plague to the new one.
If anyone has found a solution to this shutdown thing, I would love to know it. Right now, I check my phone status very often throughout the day to see whether it is one or not.
:crying:
qanda said:
The shutdown issue seems to be inherent in many SII regardless of carrier. I have had this problem with my Sprint phone since new. It has been exchanged twice thus far but the problem continues. Samsung will tell you to do a factory reset. DONTdo it. It will not fix the problem.
It is NOT the battery in most cases.
It seems to be OS related. I have cleaned the battery contacts; not charged unless below 20%; unchecked the Power Saver and Optimization functions; and did a factory reset without loading in any additional apps for awhile. Nothing stopped it from shutting down.
I was able to prevent shutdown for about a two week period by not charging it until it went below 20%.
I did notice that my RAM consumption was over 60% prior to the phone acting up.
Could it be a memory issue?
Thus far, I have not received any real support from Samsung or Sprint. The Galaxy SII is one of the few phones that cannot be run through a diagnostc test by Sprint. If you have warranty coverage, they will replace it but I can almost guarantee the problem will beda plague to the new one.
If anyone has found a solution to this shutdown thing, I would love to know it. Right now, I check my phone status very often throughout the day to see whether it is one or not.
:crying:
Click to expand...
Click to collapse
What rom/build are you on? Rooted?
Your problem isn't a common topic here unless your running experimental nightlys or doing a bad flash/install or your battery is no good.
I have two Epics since 10/2011 and have never encountered this condition. We did replace the batteries on both phones in 12/12 because of rapid discharges, going from 90% to 50% after a reboot or running a system heavy app like browser, camera, or YouTube.
Other than that all we do is use and charge when necessary.
Both phones are rooted, her phone is a workhorse because of her job, fashion design NYC, keeping track of 4 email accounts (2 gmail, 2 Microsoft Eexchange) plus crazy messaging all day long.
Check your phone model.
It may be different. Maybe you have the wrong battery in your phone?
There where some instances that had some Epic's with 1500 mha batteries instead of 1800mha!
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Battery Issue?
PanchoPlanet said:
What rom/build are you on? Rooted?
Your problem isn't a common topic here unless your running experimental nightlys or doing a bad flash/install or your battery is no good.
I have two Epics since 10/2011 and have never encountered this condition. We did replace the batteries on both phones in 12/12 because of rapid discharges, going from 90% to 50% after a reboot or running a system heavy app like browser, camera, or YouTube.
Other than that all we do is use and charge when necessary.
Both phones are rooted, her phone is a workhorse because of her job, fashion design NYC, keeping track of 4 email accounts (2 gmail, 2 Microsoft Eexchange) plus crazy messaging all day long.
Check your phone model.
It may be different. Maybe you have the wrong battery in your phone?
There where some instances that had some Epic's with 1500 mha batteries instead of 1800mha!
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Click to expand...
Click to collapse
Phone is not rooted....straight OS. I will check the battery to ascertain if it is a 1500 or 1800.
Phone is an SPHD710. It's only three months old and has been swapped twice by Sprint. I think it may be ICS. When I got it, they updated it to the latest OS which was ICS fron Gingerbread, so I don't know if it would have had the same problem with GB.
I'll try to get a new battery from them and see if it makes any difference.
Thanks.
qanda said:
Phone is not rooted....straight OS. I will check the battery to ascertain if it is a 1500 or 1800.
Phone is an SPHD710. It's only three months old and has been swapped twice by Sprint. I think it may be ICS. When I got it, they updated it to the latest OS which was ICS fron Gingerbread, so I don't know if it would have had the same problem with GB.
I'll try to get a new battery from them and see if it makes any difference.
Thanks.
Click to expand...
Click to collapse
Most definitely I would say ICS. !!!!!
If it had been left on gb you wouldn't be experiencing these issues. :thumbup:
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
deviouskind said:
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Click to expand...
Click to collapse
Sounds like the power button might be going bad. If you are not getting sudden large drops or increases in battery % I would lean towards the power button.
Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
I'm having the same sort of issues on my S2. I've had it for about 6-7 months and it's worked fine but the last few weeks it's been almost unusable. Within 5-10 minutes of using my phone it will shut off, regardless of the battery level. Turning it back on would show that it was critically low on battery and it would shut off again within seconds. Plugging it into a charger would let me turn on again and restore the battery level to what it was, oftentimes over 60%.
It seems that the false battery reports come and go, but the real problem is that the phone just keeps turning off. It's useless without a charger anymore. I've looked on Sprint's forums and it seems like many people have been having the same problem. Especially after the new JB update. I've been running stock so I figured I might try a custom rom. I rooted and went back to FF18 but I can't load up a custom recovery to install a ROM. The link to download the autoroot package in this thread is dead.
I have run into the same issue starting about three weeks ago. I am already on my second battery, which is only six months old, but it was behaving as if it was dying again, so I got another brand new one from the sprint store just to make sure... Phone was still shutting off though. After some more research, I came across someone who had a bad card reader in their phone. They even wrote a program that keeps track of mounts, ejects, and bad ejects. I downloaded it (its called sd card monitor), and sure enough, my card is ejecting itself multiple times an hour (which is no surprise, this phone has destroyed several cards already)... If I remove the card, I have no more problems... So for now, I am using my phone without a sd card. I am not paying Sprint $50 for a refurbished replacement at this point, I am fed up with their service and will be changing carriers after the S4 comes out...
The strange thing though, the sd card issue doesn't affect the phone if it's plugged in.
MECHAnized said:
I'm having the same sort of issues on my S2. I've had it for about 6-7 months and it's worked fine but the last few weeks it's been almost unusable. Within 5-10 minutes of using my phone it will shut off, regardless of the battery level. Turning it back on would show that it was critically low on battery and it would shut off again within seconds. Plugging it into a charger would let me turn on again and restore the battery level to what it was, oftentimes over 60%.
It seems that the false battery reports come and go, but the real problem is that the phone just keeps turning off. It's useless without a charger anymore. I've looked on Sprint's forums and it seems like many people have been having the same problem. Especially after the new JB update. I've been running stock so I figured I might try a custom rom. I rooted and went back to FF18 but I can't load up a custom recovery to install a ROM. The link to download the autoroot package in this thread is dead.
Click to expand...
Click to collapse
Can you confirm that your phone is having the same issues due to the card reader.?
If so please share.
(Otherwise you need a new battery.)
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
PanchoPlanet said:
Can you confirm that your phone is having the same issues due to the card reader.?
If so please share.
(Otherwise you need a new battery.)
Click to expand...
Click to collapse
I ran that SD card monitor app for about 4 hours and no disconnects, so I guess it's a battery issue.
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.
Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk
The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.
Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:
Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.
I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.
I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.
I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk
I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.
So, I went to look at the time on my phone and it wouldn't turn on. I held down the power button and the back & home buttons just blinked a few times but it didn't turn on. I plugged it into the charger and it's not charging, no LED light or anything, and it won't turn on.
Does anyone know what could have happened or how to fix it?? I noticed earlier it was running a little hot after some app updates. could that have something to so with this? Is my phone dead??
There have been several reports as of late where the same thing has happened. Were you running a custom Rom and kernel?
What recovery were you running?
Sent from my Lunar Ecliptic One.
brymaster5000 said:
What recovery were you running?
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Recovery "might" be an issue, as if recovery cannot respond to a "power on" it will not turn on. Most recoveries will respond to a "adb reboot" command. That may fix his issue... If his PC recognizes the device. I know certain TWRP had issues with the DNA and it could have bled to the m7
Sent from my HTC6500LVW using XDA Free mobile app
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
disconnecktie said:
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
Click to expand...
Click to collapse
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Yea I generally try to not get way to low. It's a scary thought though that if you happen to forget to charge your phone it might not charge back up. That's why I was interested in what rom and kernel he was using. Plus it seemed to be that most of the people who couldn't recharge had an overheating issue before hand which is more or less why I don't believe it is a recovery issue.
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Also, this happened after I updated about 20 apps.
JGress said:
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Click to expand...
Click to collapse
That almost sounds like your battery might be going out but maybe you should update your rom and recovery just out of precaution. You'll need to update your firmware as well since you're probably still running jb firmware considering the age of that rom.
disconnecktie said:
You'll need to update your firmware as well
Click to expand...
Click to collapse
Wait... I thought a ROM and firmware were the same thing.
JGress said:
Wait... I thought a ROM and firmware were the same thing.
Click to expand...
Click to collapse
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
On the battery dropping to 95% quickly, this is a known software "feature" in android since froyo or earlier. When the phone is fully charged, power cuts off from the Phone and won't "charge" until it hits 90%. System will still show you 100%. It has been proven by many sources that keeping a "trickle" on a fully charged battery will damage it. That is why it probably dropped quickly. Only way to determine if battery is faulty is have it drop below 89% and see it's drain.
Sent from my HTC6500LVW using XDA Free mobile app
disconnecktie said:
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
Click to expand...
Click to collapse
Ok, thanks for the help!
Does the One maybe have an auto-shutdown feature that triggers if it overheats? I was thinking that was a possibility.
disconnecktie said:
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Click to expand...
Click to collapse
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
brymaster5000 said:
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
I understand. I asked because I didn't understand why this would be a recovery issue since you can't always keep your phone from dying and having your phone brick as a result would completely suck. Plus, it would be a lot more frequent (you would think anyway) for this same thing to happen. I wouldn't want to use whatever recovery had this issue either. However, I think he just really needed to update his firmware, rom and recovery. I'm surprised he made it this long without needing to upgrade. It also helps knowing all the info because if it was a rom/kernel issue the dev could take a look into what could potentially cause the overheating because the thermal protection written into the kernel isn't doing its job if it allows the phone to overheat to death.
I've read 10 pages on this subforum, random talks about updates, LTE fixes, etc...I've yet to find a single thread giving an official fix for random rebooting? I get this at least 4x a day...regardless of charging or not, SD card installed or not, all the latest updates are installed. I can't be the only one and if so, why isn't this a Sticky issue at the beginning?
I and few have others have the unpleasant experience with rebooting. But it was a little relief that this issue is not just with my Note4.
Laughter is the key to happiness
I had this problem with the early 6.01 stock roms, but it eventually calmed down. Now I get a reboot about once a week. I just assumed the first couple 6.01 stock roms were buggy.
I suppose lots of hardware issues could also cause it.
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
m5james said:
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
Click to expand...
Click to collapse
So, what rom is the phone running?
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
m5james said:
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
Click to expand...
Click to collapse
What version of stock? If it's old, some of the early 6.01 roms were pretty buggy. The current stock rom is QC1, which just began to roll out this week. Make sure you are on the most current rom.
Last update I received was this week which turned out to only be a security patch.
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
So I hope I don't jinx myself, but I think a new battery has solved my issue...with some extra steps Let me explain.
Bought the phone used, it'd reset about 3-4x a day...being charged, being used, whatever. It'd reboot anywhere from 80% down to 40%, no rhyme or reason. Sometimes it simply wouldn't allow me to turn it back on, the light would flash blue while dimming in and out, but wouldn't power up the screen. Plugging it back in and it'd be at 30%-45% no matter what. I downloaded an app called Battery Calibration from Meza (sp?) that had a little Android logo with a % on his chest. Resetting may or may not have completely solved the problem had it not soft reset when trying to get battery stats to refresh themselves. It's my understanding that if it reset, it rewrote a battery stat upon reboot, making this step useless.
I got two new batteries from eBay (http://www.ebay.com/itm/112344168032?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT), I charged one in the phone and one on an external charger. Even after running with the new battery, it still reboot once and shutoff around 43% reported on the phone itself. Once plugged in and phone still off, it said it was at 15%. I swapped in the other new and charged battery, powered on the phone, plugged it in until it read 100%. I fired up the Battery Calibration app, unplugged the phone as directed and then to force the battery to drain faster, I let YouTube play uninterrupted for about 4hrs. NOT A SINGLE REBOOT!! For the first time with this phone, it actually stayed on and dipped below the 30%'s and gave me a warning when the battery was getting low (yellow icon) and getting critically low (red icon) before it finally powered itself off at 1%. The phone is now charged on the factory fast charger, this time playing Pandora with the screen off and uninterrupted as well...it's currently sitting at around 57% last I checked.
Once it's fully charged, I'll run it like any normal user (texting, music, etc) without being plugged in and if all works well, it won't reboot.
Hopefully this helps someone with the same issue and is a $8 fix since I bought two batteries.
poit said:
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
Click to expand...
Click to collapse
I reset the phone the day I got it.
if your phone often reboot many times in a day, make sure that you don't use Ram kernel V6 or v7 for your Rom, V5 is only version that not make your phone randomly reboot. I try Ram kernel v6 and v7 in Note 7 port rom, note 5 port rom and stock either, and this kernel version always make my phone reboot many many times, unless i flashed v5 or stock kernel, the problem had gone.
I had this problem. I replaced the battery with an official Samsung battery I ordered from Sprint, and the problem went away. Simple as that. No reboots ever since.
Purchased a new battery from Amazon, Samsung OEM, problem solved. Put back old battery guess what it started again but only when battery reached 70% of the original charge. So it must be the battery memory problem.
Sent from my SM-N910P using Tapatalk
Four batteries later and this still happens. Can this be addressed via rooting and then undervolting? I remember phones of the past where people would overclock for speed and undervolt for battery life, but one way too high or too low and you'd either get random rebooting or freezing. This is so god damn annoying!!!!!!