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.
Related
I seem to be having an issue with my phone overheating and rebooting. It seems to happen consistently when using navigation or when playing games (I'm hooked on Gem Miner). Always at an inopportune time. To me this seems like a result of bad hardware or something but is it possible that rooting and installing ROMs like CM7 or Kingdom Stock Sense?
I bought my phone at Best Buy and ended up getting the warranty, so assuming I can revert the phone back to stock, I should be able to get this covered under warranty. Right?
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
TheWhiteBandito said:
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Click to expand...
Click to collapse
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Hot enough that it's shutting down. I couldn't tell ya specifically.
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Its higher than 119F. Mine hit 122F the other day and didn't reboot, unless the safety shut off didn't kick in on mine. Don't think it is much higher than that though before it does.
I had heard it shuts down at 119 but my phone hasn't ever gotten that hot. I've only managed to get it up to about 114, that was multitasking and charging, overclocked to 1113.
When it reboots, do you get 5 vibrations and then the indicator flashes green until you pull the battery? If so, you are starting to have serious problems.
This thread helped me recover my Incredible..
http://forum.xda-developers.com/showthread.php?t=982454
I had mine at 120F the other day loading a new rom and no shut off
Sent from my Incredible using XDA Premium App
Mine gets hot when using wireless tether.
jetsaredim said:
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
Click to expand...
Click to collapse
I'm leaning toward a hardware issue. The reason I say that is because I'm using CM7.0.3 and Chad's Incredikernal and when I use navigation I also connect my car charger and have never had a heat issue nor any reboots. I drove from SC to FL back in Feb and had navigation running the whole time.
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
jetsaredim said:
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
Click to expand...
Click to collapse
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
fLaWx said:
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
Click to expand...
Click to collapse
I assume you're not completely an expert in this matter, but let me see if I get this right... I have to go back to having CWM on my phone so I can apply the S-ON zip and then re-run the stock recovery to get back to complete 100% stock. Sound right? I wouldn't even consider it if I didn't think there was a slight chance that I'd get flagged on the warranty review for having S-OFF set. I don't want them to have any reason to deny my getting a new phone.
Hi - long time lurker, barely ever post, but I'm gonna chime in here.
My DInc also reboots, and it is warm to the touch when it does happen. Don't know how hot though sry. I've been rooted since November, but haven't installed a Custom Rom, just removed bloat, and added some other useful tools. The biggest change I've made was changing the fonts. I don't over/under clock either (it runs just fine for me). My reboots seem to be increasing in number. At first it would be once a month, then a few times a week, and now a couple times a day.
Sometimes, my phone will reboot just once, and then continue to work. Sometimes 2-3x in a row, and then continue to work or not. Sometimes, it just vibrates 5x quickly, and then is locked (LED flashes), and the only way to recover is to pull the battery and start over.
Seems to happen MOSTLY around certain times of day - 4:30-6pm when I'm on my way home from work (no, not using my phone, but it happens anyway), and around lunchtime (again, not using it, or if I am it's barely). Other times it happens too - but really randomly. I'm ruling out different apps that might be triggering it, but don't think that's the issue.
QUESTION - if it is heat related, and the phone is supposed to go into shut-down mode at 119*, but seems to be different temps for everybody, could it be the thermostat? Could it be registering a false temp reading and think it needs to shut down? Has anyone explored this?
I'm not an engineer, or even a programmer, but I like to play one on TV. Thx
Oh - I forgot to add this:
There have been times when it would reboot, and I've placed my phone and battery (removed from phone) on the vents of an airconditioner, or even sitting on a frozen ice pack (the kind for a cooler) and it would still happen afterwards. To the touch, my phone would be cold, not freezing, but cold. Seriously lower temp than what it was when it was very warm to the touch...
I'm definitely with you on the first scenario. I just brought it to my local Best Buy where I bought it (with warranty) and they sent it off and gave me a loaner DInc to use till mine's repaired. They said, if they can't repair it, they'll give me a DInc2 as a replacement since the Dinc1 is "backordered" (aka not being carried).
jetsaredim - I was able to get a replacement DInc sent to me overnight (free!). My first replacement had a faulty USB port, so I couldn't charge my phone. I have 'another' DInc being sent to me now. Other than the faulty USB port, I haven't had any overheating issues so far (knock on wood).
First phone manufactured in June 2010
First replacement phone, manufactured in April 2010, and remanufactured June 2011 (via ##7764726)
I just got my replacement Incredible today. I just tested my original phone again by watching 15 minutes of video on youtube and BANG!!!!!!!!!! It rebooted as usual. Screen and battery get very warm. The reboots seem to happen when watching videos online or offline, playing games for 10 to 15 minutes, browsing the web for 15 to 20 minutes, using Google Maps with or without charging at the same time, and charging and talking on the phone at the same time. Well, I'm sending back the original and hoping that the replacement doesn't fail me. Glad that I swapped it just before the manufacturer warranty was up.
Have had the Dinc since week one. 100% stock - have not rooted (yet) and stock battery - in the past month it has 'overheated" and rebooted twice. Never happened before. Both times while using navigation and charging. Could it simply be the battery? It's not holding a charge like it used to too which also makes me wonder about the battery.
my phone literally just died on my desk
for absolutely no reason
the battery is charged, so that's not it I was using it less than 30 minutes ago and just picked it up to watch a video... nothing... did a battery pull... nothing
out of deperation I tried using one of the USB jigs that I have used in the past on older galaxy s to get into download mode and it worked
now to try to find a stock odin flashable image, even though i'm debating on just returning this phone... just dying like that in one week is unacceptable and reminds me of the issues the G2x had
ppctester said:
my phone literally just died on my desk
for absolutely no reason
the battery is charged, so that's not it I was using it less than 30 minutes ago and just picked it up to watch a video... nothing... did a battery pull... nothing
out of deperation I tried using one of the USB jigs that I have used in the past on older galaxy s to get into download mode and it worked
now to try to find a stock odin flashable image, even though i'm debating on just returning this phone... just dying like that in one week is unacceptable and reminds me of the issues the G2x had
Click to expand...
Click to collapse
This happened to me as well. check this out http://forum.xda-developers.com/showthread.php?t=1306852
princeasi said:
This happened to me as well. check this out http://forum.xda-developers.com/showthread.php?t=1306852
Click to expand...
Click to collapse
damn it.. if this is ANOTHER G2x-like fiasco.. I'm gonna return this and say goodbye to Tmo... it's their retarded request that the hardware be changed for their network instead of having the normal exynos CPU
didn't hear of any issues like this for the original SGS2 international/AT&T versions
ppctester said:
damn it.. if this is ANOTHER G2x-like fiasco.. I'm gonna return this and say goodbye to Tmo... it's their retarded request that the hardware be changed for their network instead of having the normal exynos CPU
didn't hear of any issues like this for the original SGS2 international/AT&T versions
Click to expand...
Click to collapse
I dont think its that serious. I think its a software bug with the battery meter freezing without knowledge of it. When it freezes without indication, we end up continuously using the phone till the battery completely discharges without knowing.
princeasi said:
I dont think its that serious. I think its a software bug with the battery meter freezing without knowledge of it. When it freezes without indication, we end up continuously using the phone till the battery completely discharges without knowing.
Click to expand...
Click to collapse
i replied in your other thread... I was able to reflash the kernel and the phone booted right away without having to wait for a charge like it would have if the battery was completely drained
So here's my story...
I hated the new ICS official update that sprint rolled out because of my diminishing battery life. So i decided to finally root the phone and install some roms. Everything went well for the past week but now my phone screen flickers and then my phone shuts off when i still have around 80% battery life left. I try to turn it back on and it loads up the boot screen but sometimes it fully loads the phone and sometimes it doesn't. When it does load ... my battery life is chopped to like 20% or maybe 5%. I calibrated my battery after the flash like someone told me to do but it still didn't work. I thought it was the rom i was using but I flashed 3 different roms and I still have the same problem.
I'm wondering if it's something wrong with my battery or my power on my phone? When the phone is charging it doesn't flicker and shut down on me.
Did anybody else have this problem? Is this considered a SOD? Wondering if I should get a new battery and see if it works. Also... is your battery flat? Mine seems to be a curved a bit in the middle back and front and i don't remember it being like that.
THANKS FOR THE HELP PEOPLE!!!! I really need it
Spin the battery on a flat surface and if it continues to spin, its bad. From your description of the back if battery, it sounds bad. Take it to a sprint store and get a replacement.
Sent from my SPH-D710 using xda app-developers app
+1
I dont want to hijack this thread, but im having similiar problems. if my phone was charging the screen would flicker. it doesnt do it anymore but now sometimes the screen wont turn back on. its almost like its off. there is no haptic feedback no lights. i have to pull the battery and then it will turn on. im running UPDATED 9/12] [ROM] RE-CALKED 0.2.0 [FI03] Calk's ROM Re-Cooked in FI03
BluesRulez said:
Spin the battery on a flat surface and if it continues to spin, its bad. From your description of the back if battery, it sounds bad. Take it to a sprint store and get a replacement.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
yeah this battery is deff spinnable... so this should be a battery problem right?
Dont' know how this could've happened
Thanks
aznne0 said:
yeah this battery is deff spinnable... so this should be a battery problem right?
Dont' know how this could've happened
Thanks
Click to expand...
Click to collapse
This is just the effects of ICS. Go to to your sprint store , they should replace it free. Consider a custom Rom to remedy the issue.
Pp.
Sent from my GT-P5113 using xda premium
hardwirk1 said:
+1
I dont want to hijack this thread, but im having similiar problems. if my phone was charging the screen would flicker. it doesnt do it anymore but now sometimes the screen wont turn back on. its almost like its off. there is no haptic feedback no lights. i have to pull the battery and then it will turn on. im running UPDATED 9/12] [ROM] RE-CALKED 0.2.0 [FI03] Calk's ROM Re-Cooked in FI03
Click to expand...
Click to collapse
PanchoPlanet said:
This is just the effects of ICS. Go to to your sprint store , they should replace it free. Consider a custom Rom to remedy the issue.
Pp.
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
I'll check the store tomorrow.. but i read that there's a 6 month warranty on the battery.. sighh...
aznne0 said:
So here's my story...
I hated the new ICS official update that sprint rolled out because of my diminishing battery life. So i decided to finally root the phone and install some roms. Everything went well for the past week but now my phone screen flickers and then my phone shuts off when i still have around 80% battery life left. I try to turn it back on and it loads up the boot screen but sometimes it fully loads the phone and sometimes it doesn't. When it does load ... my battery life is chopped to like 20% or maybe 5%. I calibrated my battery after the flash like someone told me to do but it still didn't work. I thought it was the rom i was using but I flashed 3 different roms and I still have the same problem.
I'm wondering if it's something wrong with my battery or my power on my phone? When the phone is charging it doesn't flicker and shut down on me.
Did anybody else have this problem? Is this considered a SOD? Wondering if I should get a new battery and see if it works. Also... is your battery flat? Mine seems to be a curved a bit in the middle back and front and i don't remember it being like that.
THANKS FOR THE HELP PEOPLE!!!! I really need it
Click to expand...
Click to collapse
We need more info on your setup to be able to help you.
1.What ROM are you on? (Name, Build etc.)
2.Kernel / Tweaks / etc.
Omar04 said:
We need more info on your setup to be able to help you.
1.What ROM are you on? (Name, Build etc.)
2.Kernel / Tweaks / etc.
Click to expand...
Click to collapse
It happened on every rom i flashed.. but this is what i'm on now.
Rom version Blazer FF18
kernel version 3.0.15-sph-d710.ff18-cl663858
Baseband version FH13
I am trying to underclock the phone now and see if it solves any problems till I get a new battery. Realized that while the phone is plugged in... it doesn't flicker and shut down on me. So maybe if i lower the power consumption, it'll work. But it's just an idea I came up with.
THANKS FOR YOUR HELP!!
aznne0 said:
It happened on every rom i flashed.. but this is what i'm on now.
Rom version Blazer FF18
kernel version 3.0.15-sph-d710.ff18-cl663858
Baseband version FH13
I am trying to underclock the phone now and see if it solves any problems till I get a new battery. Realized that while the phone is plugged in... it doesn't flicker and shut down on me. So maybe if i lower the power consumption, it'll work. But it's just an idea I came up with.
THANKS FOR YOUR HELP!!
Click to expand...
Click to collapse
Your experiencing a condition that's clearly battery related, while phone is plugged in it clearly shows that the problem is the battery. Making changes and undervolting may just complicate things, I would wait for a new battery before going any further.
You need a proven rom to start with, ask around and see what works for others and give yourself a fresh start. I would recommend going back to stock gingerbread el29,and trying it out for a week or so, then go from there.
Pp.
Sent from my ginger infused Mayan calculator.
PanchoPlanet said:
Your experiencing a condition that's clearly battery related, while phone is plugged in it clearly shows that the problem is the battery. Making changes and undervolting may just complicate things, I would wait for a new battery before going any further.
You need a proven rom to start with, ask around and see what works for others and give yourself a fresh start. I would recommend going back to stock gingerbread el29,and trying it out for a week or so, then go from there.
Pp.
Sent from my ginger infused Mayan calculator.
Click to expand...
Click to collapse
Will do. Just ordered a battery. Hopefully it is a battery issue because I am not due for an upgrade yet. Thanks a lot for your advice!
It's the battery, I have the same issues right now and if I use a different battery they instantly disappear.
And you're right about lowering the power consumption, for me it only happened with 4G enabled together with the capacitive LEDs. Disabling one or the other made it go away.
Sent from my SPH-D710 using xda app-developers app
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
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.