Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.
Nickb1989 said:
Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.
Click to expand...
Click to collapse
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.
androidtoy09 said:
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.
Click to expand...
Click to collapse
on the dot.
its specifically within cwm, even other phones are experiencing the same issues with cwm
So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App
Nickb1989 said:
So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.
r3s-rt said:
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.
Click to expand...
Click to collapse
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.
Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App
androidtoy09 said:
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.
Click to expand...
Click to collapse
Nickb1989 said:
Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Meh. I've had a bunch of people tell me they had to buy new batteries from leaving their phone charging all night and a few reps have told me not to do it. I think specifically that was when I had my BlackBerry. That's only reason I thought that. =P Either way, thanks for the info. Learning is great. =]
Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App
shortlived said:
Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I agree. Night time charging to me seems to be the best amd I've never had a problem with a battery from doing that. Even if the phone wasn't completely dead. Seems to be ok with me lol
Sent from my T-Mobile G2 using XDA App
ever notice ur phones charging led change colors when its full? we have a smartphone fellas, its smart enough to hold a charge, stop charging, let it trickle, and maintain a full charge safely.
Sent from my T-Mobile G2 using XDA App
Related
Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk
I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.
Evostance said:
Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.
mskip said:
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.
Click to expand...
Click to collapse
Good point.
Wonder what app it is
Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium
SweetPAIN225 said:
Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off
Thanks! I made a wrong assumption!
Sent from my Galaxy Nexus using xda premium
Evostance said:
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off
Click to expand...
Click to collapse
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Exactly, it is way way too likely that turning your CPU down will result in 'Sleep of death'
matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well its still worth noting. SetCPU never did this on my DHD
I had exactly the same thing last night, I even made my own thread
http://forum.xda-developers.com/showthread.php?t=1360847&page=2
I even wrote a simple app for logging the battery temperature and time, so I'll leave it on next night and I'll see what happens. Because I'm pretty sure my phone switched off due to overheating, as it was really,really hot in the morning, after I switched it on the battery was at 46C.
I'm afraid I can confirm that I have experienced the same "sleep of death" problem twice now. I can't remember what I was doing the first time, but the second time I was only browsing and I know I didn't have any apps installed because I had previously reset my phone. I've only had the phone for two days now and if it does it again I might have to send it back.
I expected a glitch or two, but with the volume bug and other annoying things like the lack of flash and poor camera quality, I'm beginning to regret my purchase. Although I love the ice cream sandwich experience, I'm now thinking of getting the Galaxy Note instead, and waiting for ICS to arrive on that next year. At least then I will be able to watch iPlayer in the meantime.
Mines done it about 4 times. Pre installed Movie maker seems to induce it.
Rawkode said:
I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.
Click to expand...
Click to collapse
Had a sleep of death for the first time yesterday - the only "different" thing I did during the day was use spotify so there maybe something in that!
Same again last night, woke up this morning and phone was on but wouldn't wake. Notification light was on solid. Was plugged in at wall all night, didn't seem too warm when I held it.
Time to start debugging I guess
I've had this issue twice too.
I do not have spotify installed, and the phone was NOT hot at all. Not even warm!
I was just in gmail, sent a mail, then pressed the home button, and black.... gone.
Had to pull battery.
Thinking of having phone replaced by Handtec. I know this is probably a software glitch, but the volume bug, and the fact my unit was one that handtec had "tested" etc, I might just ask for a brand new one from the new flashed batch due next week.
Wtf! Just how wide spread is this??? Seems like too many people are having this issue.
Phone hasn't even arrived yet and I'm already starting to question my purchase.
1 more bug and im cancelling my order !
Well, it's the first device with ICS so I expect there will be a few bugs in the future which will need to be fixed. That's the reason why I'll go for the Nexus ... it's a nice piece of hardware but even more important is that it will be the device which gets the fixes first.
Did anyone check to see if you've had an OTA for the volume ghost fix and this problem has spawned instead? Seems like a fairly new problem if you have followed the forum.
Sent from my X10i using xda premium
Hello, i don't see a question and answer forum so i am asking it here. My wife has a t-mobile Samsung galaxy 2 and the phone does not show the correct percentage and she has had the phone shut off because it ran out of power. Only if she charges to full and reboot does it work properly. Any help would be great. Thanks in advance. By the way the phone is not rooted.
Sent from my SGH-T959 using XDA App
Uhmm calibrate it. Pull out the battery for 5 seconds pull it back in... Then power it on. Male it to where so the phone shuts off completely then charge it too 100%
Sent from AN AMAZING PHONE WITH A FREAKING DENT TT^TT
Oh and this goes in the general.. The reason why we dont have a Q and A is because the general section needs like 1000 post daily to get it. So thats why. Also and more question go to general for the time beingg
Sent from AN AMAZING PHONE WITH A FREAKING DENT TT^TT
Are you using the original charger and cable? I had the same issue and it started working after I finally pulled them out of the box.
To answer your initial statement, anything that doesn't fall under development would go on the general forum.
That being said, I remember this issue being brought up by lots of members at the beginning. So, a search should give you some answers. I think rooting and trying out one of the great roms currently available here is the best way to go IMO. I personally recommend Juggernaut
edshawn911 said:
Hello, i don't see a question and answer forum so i am asking it here. My wife has a t-mobile Samsung galaxy 2 and the phone does not show the correct percentage and she has had the phone shut off because it ran out of power. Only if she charges to full and reboot does it work properly. Any help would be great. Thanks in advance. By the way the phone is not rooted.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i had a problem with the apps not showing the correct battery at first too when it wasn't rooted, but even before i rooted i found this app to work for me and it always displayed the right battery. like it never freezes the battery life while it is actually being drained.
https://market.android.com/details?...51bGwsMSwxLDEsImNvbS5sYXJyeXZncy5iYXR0ZXJ5Il0.
Battstatt is another really good battery widget
known issue http://forum.xda-developers.com/showthread.php?t=1322050
please use search next time
My issue does not seem to be specific to any one rom, I have flashed nearly all of them. When I try to use my phone while it is charging, the touch screen is slow to respond or extremely laggy. I use the stock USB cable and AC adapter.
Does anyone else experience this?
whewitt56 said:
My issue does not seem to be specific to any one rom, I have flashed nearly all of them. When I try to use my phone while it is charging, the touch screen is slow to respond or extremely laggy. I use the stock USB cable and AC adapter.
Does anyone else experience this?
Click to expand...
Click to collapse
Hi. Did you do a search 1st ? No, because this has been answered before. Next time don't be afraid to go thru some pages and do a search before posting a redundant question. Thanks.
Muff Burner said:
Hi. Did you do a search 1st ? No, because this has been answered before. Next time don't be afraid to go thru some pages and do a search before posting a redundant question. Thanks.
Click to expand...
Click to collapse
I did try to do a search, but the search field disappears when I try to use it on my tablet. Ever time the android keyboard comes up, the search field goes away. Could you kindly direct me to the correct post.
I finally was able to search the threads when I switched to my phone.(it had charged enough to unplug out and use) From what I gather, it is a result of a built in feature on this Samsung phone used to eliminate "ghost touches"
This doesn't help the fact that it is annoying and counterproductive when I am trying to read xda posts while at work.
Sent from my SGH-T989 using XDA App
whewitt56 said:
I finally was able to search the threads when I switched to my phone.(it had charged enough to unplug out and use) From what I gather, it is a result of a built in feature on this Samsung phone used to eliminate "ghost touches"
This doesn't help the fact that it is annoying and counterproductive when I am trying to read xda posts while at work.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
people can be meanies on here. xda search isn't the greatest thing. But it could be that the charger is faulty. Probably need a new one. T-mobile could supply you one through warranty for free. Try to ask for the cable and battery too while you're at it. they're all covered.
Teo032 said:
people can be (Mod Edit) on here. xda search isn't the greatest thing. But it could be that the charger is faulty. Probably need a new one. T-mobile could supply you one through warranty for free. Try to ask for the cable and battery too while you're at it. they're all covered.
Click to expand...
Click to collapse
Thanks, I'll give TMO a call. Worst case scenario is that I'll get a new charger. I agree about people bring pricks on here, I see it every day in the dev section. I just thought I could post in Q A without getting grief.
Sent from my SGH-T989 using XDA App
whewitt56 said:
Thanks, I'll give TMO a call. Worst case scenario is that I'll get a new charger. I agree about people bring pricks on here, I see it every day in the dev section. I just thought I could post in Q A without getting grief.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
It's not super clear what the issue is. Some people say that the issue goes away when not using the stock Samsung charger, some say the issue is a grounding issue. I personally have experienced this issue in the lock screen and it'll take like 5 tries to unlock but outside of the lock screen I don't have issues with general usage. Rest assured it's not a faulty phone, or even a faulty charger.
yoft1 said:
It's not super clear what the issue is. Some people say that the issue goes away when not using the stock Samsung charger, some say the issue is a grounding issue. I personally have experienced this issue in the lock screen and it'll take like 5 tries to unlock but outside of the lock screen I don't have issues with general usage. Rest assured it's not a faulty phone, or even a faulty charger.
Click to expand...
Click to collapse
I experience the exact same symptoms from lock screen. However, there is also a lag in responsiveness even after it finally unlocks. I'll give my wifes my touch 4g slide's charger a go. Thanks for the suggestion.
Sent from my SGH-T989 using XDA App
I plugged my t989 into my wifes HTC OEM charger and experienced no strange behavior from the phone.
Sent from my SGH-T989 using XDA App
whewitt56 said:
I plugged my t989 into my wifes HTC OEM charger and experienced no strange behavior from the phone.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Glad to hear you solved the issue with one of those solutions.
Thanks for the suggestion yoft1......+1
Simply reboot! Yes, it's that easy.
Recently my phone has been acting... odd. Basically every reboot reported a completely different battery level. It went like this:
Reboot: 67%
Reboot: 17%
Reboot: 45%
Reboot: 0% (Whhaaat!?)
Reboot: 75%
It was really fun after playing a game that apparently draws just a little too much current, causing it to instantly power off. Fun times.
That's not normal. If your phone is doing that, buy a new battery. From what I've been reading here, it seems like these phones either kill batteries in disproportionate amounts, or we were given lots of bad ones. Seems odd.
Or if u think ur rom is wonky take out ur battery out and try to spin it if it spins then its ur battery
Sent from my SPH-D710 using xda app-developers app
I thought losing battery percentage was normal if you do a reboot.. It was a known issue in a lot of threads even with individuals with a good battery
-TeaM VeNuM Like A Boss
MiguelHogue said:
I thought losing battery percentage was normal if you do a reboot.. It was a known issue in a lot of threads even with individuals with a good battery
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
I'm pretty sure it is normal. I've only had my phone since June 1st of this year, and it did that. So unless I got screwed on the battery, I think it's normal.
Sent from my SPH-D710 using xda app-developers app
E4GTUser94 said:
I'm pretty sure it is normal. I've only had my phone since June 1st of this year, and it did that. So unless I got screwed on the battery, I think it's normal.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
i think what hes tryna say is every reboot shows a diff %.. it is normal to lose some when doing a reboot but not sure how normal it is if you go lower.. then higher.. then 0% then up to 50% lol as the op suggests happened if im reading it right? either way quite useless thread lol theees plenty of battery discussions going on xda.. i thouht this was going to be informative and maybe goin over all different ways to tell if a battery is bad in one thread lol
Sent from my SPH-D710 using xda app-developers app
I thought to fix that you just calibrate your battery
trifthen said:
Simply reboot! Yes, it's that easy.
Click to expand...
Click to collapse
Unfortunately, it's not quite that easy. For those of us who have a battery that is going bad (starting to bulge) a reboot does not always screw with the battery value, other times it does. :screwy:
Sent from my SPH-D710 using XDA
Typically on Reboots you will drop battery % a bit.. Not as drastic as OP is showing... I don't know if it applies on this side so much but on the OG Epic, Since it was first rooted you would sometimes get a false battery % on reboot (Start at 90% before reboot, after reboot shows 20% or less!) Which case reboot, pull battery, toss it in and reboot would clear it. The "Spin Test" is a fairly accurate test. Battery's due bulge after being overheated for so long. So that's a quick indication as well that she's gone. Nice post btw..
Haha. Yeah, it fails the spin test too. I was just shocked that it couldn't get a consistent reading after half a dozen reboots. Didn't have anything handy to do a spin test on the train, so this works too. I haven't flashed for months, so I seriously doubt it's a calibration issue. I've seen charge drop before, but never jump up by 50±%.
I went in to a Sprint store for a replacement, and they had to order one. Really? One of the most popular phones last year, and they don't carry any spare batteries?
Oh well. At least it was free after they confirmed it was bulging.
Sent from my SPH-D710 using xda premium
Removed.
I used battery calibration from the Play Store and it kinda help. I highly suggest that app
Sent from my SPH-D710 using Tapatalk 2
locoboi187 said:
Removed.
Click to expand...
Click to collapse
Nope, it's still there.. How'd you get those like that??
milky1112 said:
Nope, it's still there.. How'd you get those like that??
Click to expand...
Click to collapse
Get what like what?
Sent from my SPH-D710 using xda premium
locoboi187 said:
Get what like what?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hahaha.. You said Removed.. So i was just messing around.. (Making people wonder what you removed) hahaha.
trifthen said:
Simply reboot! Yes, it's that easy.
Recently my phone has been acting... odd. Basically every reboot reported a completely different battery level. It went like this:
Reboot: 67%
Reboot: 17%
Reboot: 45%
Reboot: 0% (Whhaaat!?)
Reboot: 75%
It was really fun after playing a game that apparently draws just a little too much current, causing it to instantly power off. Fun times.
That's not normal. If your phone is doing that, buy a new battery. From what I've been reading here, it seems like these phones either kill batteries in disproportionate amounts, or we were given lots of bad ones. Seems odd.
Click to expand...
Click to collapse
Lmfaooooooooo report IDC. You are not informed at all lol! That's a Samsung issue with all the phones! Go do some research b4 you post & b4 I take out the flamethrower on everyone here!
ÄÖK¶ B4
"420 Special Edition 10/16"
The problem i think starts when you charge your phone with a charger thats not the one that came with your phone. My battery is OK if im 90% and do a reboot it stays 90% or 89% but one day i had to charge it with another charger and it happened to me. It went from 75% to 20%. I let it go to cero and then charge it with the original one and it fix it. At some point the battery will f#ck uff LOL
Sent from my SPH-D710 using xda premium
krazy_smokezalot said:
Lmfaooooooooo report IDC. You are not informed at all lol! That's a Samsung issue with all the phones! Go do some research b4 you post & b4 I take out the flamethrower on everyone here!
Click to expand...
Click to collapse
Can someone translate this into English?
Just so you know, I did research. That research commonly led to several threads where people complained that their battery percentage suddenly dropped following a reboot. I also experienced this, and thought nothing of it. It is in fact common, especially after a ROM flash. But you'll notice I said nothing of a ROM flash, nor did I complain about the drop in percentage itself.
It's the fact that the percentage acts like a yo-yo. I rebooted about 10 times while on the train home from work, and every time, the charge was effectively a random number between 0 and 80. I say 80 because that's the highest number I saw during those reboots. When I finally got home, I was able to spin my battery on a flat surface, confirming my earlier suspicion.
Since you're so enlightened, flush with the knowledge of all Samsung devices and their numerous quirks, perhaps instead of ridiculing us, you could point out some of the "research" we're missing?
Wait... let me try putting it your way:
"[email protected]! I liek red all teh threads, yo! lolololl! Teh % geos up, too! srsleeee, no disrespec but my bat was bad bcus it spun man so i guess i was right lololololo!!1!!eleventy!!"
krazy_smokezalot said:
Lmfaooooooooo report IDC. You are not informed at all lol! That's a Samsung issue with all the phones! Go do some research b4 you post & b4 I take out the flamethrower on everyone here!
ÄÖK¶ B4
"420 Special Edition 10/16"
Click to expand...
Click to collapse
Not true, I own 3 Samsung phones. None of them have ever done that. So YOU might wanna do some research first.
Sent from my Galaxy Nexus using xda app-developers app
Im on my second, not a single issue with either of them. Mom took my OG Epic. Because i got touch. Both are goin strong.
Sent from my braille Epic Touch
trifthen said:
Haha. Yeah, it fails the spin test too. I was just shocked that it couldn't get a consistent reading after half a dozen reboots. Didn't have anything handy to do a spin test on the train, so this works too. I haven't flashed for months, so I seriously doubt it's a calibration issue. I've seen charge drop before, but never jump up by 50±%.
I went in to a Sprint store for a replacement, and they had to order one. Really? One of the most popular phones last year, and they don't carry any spare batteries?
Oh well. At least it was free after they confirmed it was bulging.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wife's phone has been having the same issues. Went in to Sprint, they saw the battery was bulging and wanted to run additional diagnostics. They said it would take an hour and a half, when we came back they said all problems are caused by the battery. Sprint didn't have any in stock and recommended we try Batteries+ who also didn't have any in stock. Going to try the Anker batteries recommended in the E4GT Accessories forum.
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.