Related
hi i have a
Gnex
im using
>Codenameandroid v3.3.2
>Trinity kernal
Everytime my phone reaches around 30% my phone just dies, then wont start till i connect it to a ac wall charger.
i have two batteries and at first i thought it might of been a ebay battery i purchase but it does it with both.
any help?
Try to wipe the battery stat in recovery.
I tried wiping it Ndnit continues to behave this way. Thank you for replying
Sent from my Galaxy Nexus using xda premium
Did this just start happening with the new kernel? If you are sure it isnt a hardware/battery issue, I would set it back to stock and see if that fixes it. Hopefully its just a bad combination of kernel/rom. Good luck !
You know what it might be the kernal I using the Trinity kernal experimental 537. I'm flash back to the stable version. See if that helps.
Sent from my Galaxy Nexus using xda premium
I had a odd quirk earlier today. My phone showed around 40-55% the suddenly died. I turned it back on and saw 8% left.. hasn't happened again but was strange.
Sent from my Galaxy Nexus using Tapatalk 2
withbloodskies said:
I had a odd quirk earlier today. My phone showed around 40-55% the suddenly died. I turned it back on and saw 8% left.. hasn't happened again but was strange.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Its happened to me too in the 50%'s. Its odd isn't it? Such a beautiful phone though. I thought nothing would ever separate me from my HTC HD2.
Sent from my Galaxy Nexus using xda premium
Am on everything Stock...
I have never gone into any such issues like this b4...
If i feel like battery drain or something like tat.. I do wipe cache and dalvik and install the ROM and fix permission in CWM...
Then it will be back again..
Its my Daily driver. So most of the time i will be on Calls and msgs and also Wifi and bluetooth will be on 24/7
Auto Sync on..
My Battery will Remain till nxt day morning and still i will be having 25~30% left out...
THIS HAS BEEN VERIFIED BY ME, AND JOKERSAX HAS TOLD ME ABOUT TWO OTHER DEVS WHO HAVE HAD SIMILAR RESULTS
This is a public service announcement saying that if you leave recovery (I left TWRP on overnight while restoring a nandroid) on too long, under certain circumstances not yet completely determined may lead your device to a hard brick. This has happened to 3 people so far, and want to avoid anymore issues with this.
For more details on what happened I was flashing a V5 test build of my rom im working on adding aroma too where I got another syntax error to fix. It was about 11:30 at night, so I just started restoring from a nandroid, threw the phone upside down, and knocked out. When I woke up the next morning I checked the device and it was off in recharge mode- nothing too big. I then tried to boot and it ended up flashing the notification light and softkeys repeatedly, and did nothing else. I was able to get it into download mode, but LGNPST kept timing out. Then after trying several times with it timing out it wouldnt get into download mode. I then tried to just get anything to light up, and left it on the charger for several hours, and then gave up that my device was hard bricked. No data remained. I had to go to best buy and wait about an hour and a half for them to get me a new device. I hope everyone can avoid this happening to their device. It is a slow, but sure death reported by a few people.
And to think I left my phone in recovery. for about 2 hours =x scared to even boot to recovery now
Sent from my LG-LS970 using xda premium
Veritass said:
And to think I left my phone in recovery. for about 2 hours =x scared to even boot to recovery now
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
If youre phone boots it will be fine. I left it for about 8 hours or so.
You should make this a sticky
Ya i was taking my time with the aroma installer and noticed my phone heat up real quick! Had to turn my phone off after the rom booted. Close call!
Sent from my LG-LS970 using xda premium
This must be what happened to my first LGOG, I feel asleep running a backup. When I woke up it wouldn't boot. Thank goodness for Geek Squad coverage.
Does anyone know if this problem exists with clockwork too? I already fried a phone just making a simple backup using TWRP.
I'm using CWM now and made a backup and flashed a rom and my phone survived.
Sent from my LG-LS970 using XDA Premium HD app
toprock23 said:
Ya i was taking my time with the aroma installer and noticed my phone heat up real quick! Had to turn my phone off after the rom booted. Close call!
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Every time I use aroma my phone gets scorching hot. If I recall my GS3 did the same thing with aroma.
Sent from my LG-LS970 using xda premium
_Epic said:
Every time I use aroma my phone gets scorching hot. If I recall my GS3 did the same thing with aroma.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Any time I boot to recovery my phone heats up =p
Sent from my LG-LS970 using xda premium
My phone also gets really got while in recovery mine also overheated exactly like the OP but mine came back to life I left it alone for a few hours then put it on the charger and finally got into download mode then recovery and restore. We definitely need to do something like timeout where after 10 minute the phone shuts off or something. Not sure it is possible but I like ranting lol
Sent from my LG-LS970 using xda app-developers app
We need to fix recovery
Sent from my LG-LS970 using xda app-developers app
Thanks for the info! I used to leave backups running overnight all the time with my previous devices. Good thing I haven't with this one.
Sent from my LG-LS970 using xda premium
Only thing that could heat up the phone like that is the cpu core running at max.or spiking to max very very rapidly. Basically the soc with all the chipsests are not going into a sleep mode. I can see why all the data was gone and or damaged. I've seen something like this with other electronics.
Sent from my LG-LS970 using Tapatalk 2
I have not left recovery on long enough to experience noticeable overheating myself. I wish I knew how to fix the recovery myself though. Also as for making this a sticky (I read half the posts through email, and might have got this thread mixed up) mods are kinda inactive, so it will be hard for us to do.
evodev said:
I have not left recovery on long enough to experience noticeable overheating myself. I wish I knew how to fix the recovery myself though. Also as for making this a sticky (I read half the posts through email, and might have got this thread mixed up) mods are kinda inactive, so it will be hard for us to do.
Click to expand...
Click to collapse
If I am in recovery for 5 seconds, my device heats up really bad. But it is the only time it heats up.
_Epic said:
If I am in recovery for 5 seconds, my device heats up really bad. But it is the only time it heats up.
Click to expand...
Click to collapse
I have heat up while playing games or streaming music, or leaving it at the lockscreen too long. Maybe undervolting it can fix it? IDR if joker's test kernel added it or not.
Happened to me to. But mine was adb push file to sdcard and lost power due to usb low charge and recovery turning phone into a glass top stove
Sent from my LG-LS970 using xda premium
Mine overheats after playing Beach Buggy Blitz for five minutes, in recovery. Too often really :/
These are reasons I always finish what I'm working on before I sleep! It drives my girlfriend nuts ha ha. But yes, the phone does get hot rapidly in recovery hotter than I have ever gotten it running any game or app
Sent from my LG-LS970 using xda app-developers app
well TWRP 4.2 is out now, maybe itll fix our little problem.
I came home from grabbing a bite to eat. About 30 minutes had passed and I was wondering why I havent heard my phone in a few. Checked and the notification light was blinking. Tried to press the power button to turn it on and nothing. Pulled the S Pen out because that would make it come on and still nothing. Pulled the battery and now all i get is the "Samsung Galaxy Note 2" screen. If i leave it there, after about 2 hours it will make the T-Mobile jingle and go into a boot loop. The boot loop lasts until i pull the battery again.
My phone was not rooted, no ROMs or anything. Only apps I had that did not come preinstalled on the phone were, Facebook, Tweetcaster, Instagram, Hill Climb Racing, Subway Surfer and my banking app.
My Galaxy 2 did something similar but i blamed it on the ROM I was using and figured I had bricked it some way. My faith in Samsung products is declining....
Are you able to connect it to a pc and is it recognized through ADB?
If so, I would try using ODIN and dumping the stock firmware and start from fresh.
nmw407 said:
Are you able to connect it to a pc and is it recognized through ADB?
If so, I would try using ODIN and dumping the stock firmware and start from fresh.
Click to expand...
Click to collapse
Yeah i tried that after i talked to TMobile and my replacement phone was on the way. It is recognized in ODIN but it takes about 45 minutes to complete the process and then it fails.
Weird. Had the same problem about a couple of hrs ago. Also I tried hitting the middle button. And turn on button and nothing. Turned it off. Took the battery off and waited about 30 secs. But it back in. And it worked. Never had happen to me...
Sent from my SGH-T889 using xda app-developers app
Galaxysm said:
Weird. Had the same problem about a couple of hrs ago. Also I tried hitting the middle button. And turn on button and nothing. Turned it off. Took the battery off and waited about 30 secs. But it back in. And it worked. Never had happen to me...
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Similar scenario/solution except never a bootloop.. just went from 6% battery to completely dead.
I didnt try to turn it on, but pressed (tapped power button) and the phone wouldnt do anything. It also didnt respond to a charge, plugged it in to several wall outlets in various rooms, until I pulled the battery for, like ive been trained through older droids, 30 seconds...
Replaced the battery, plugged it in and got it charging, waited til 20-30% before turning on phone to verify, and yes everything was working fine!!
No issues since
Sent from my SGH-T889 using xda app-developers app
Well thats good but yeah it has been weird lol. I had never had that on my s2. So I got scared D: LOL.
Sent From Land Of Ooo. Using a Jedi Mastered Note 2.
I had the same problem, I had tjot my phone died but I know I had at leas y 80% of battery left. I tried using my phone nothing, plugged it up nothing. So I pulled the battery and it finally came on. This wad the 1st time it occured, the next time was like yours only the notification light was fladhing the power button and nor the home button worked. I removed apps that I tjought wad causing it. I had called Samsung and tmobile snd they never heard of such problem. They only suggested I do a hard reset. It hasn't happened in a while now but if it does I want a replacement, since I now know im not crazy, and you guys have had the same problem
Sent from my SGH-T889 using xda app-developers app
tl08newbie said:
I had the same problem, I had tjot my phone died but I know I had at leas y 80% of battery left. I tried using my phone nothing, plugged it up nothing. So I pulled the battery and it finally came on. This wad the 1st time it occured, the next time was like yours only the notification light was fladhing the power button and nor the home button worked. I removed apps that I tjought wad causing it. I had called Samsung and tmobile snd they never heard of such problem. They only suggested I do a hard reset. It hasn't happened in a while now but if it does I want a replacement, since I now know im not crazy, and you guys have had the same problem
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well at least you all's phone started back working, mine didn't. I. Got my replacement today.
same thing here
yesterday my phone was up with blue light then when i try hit the power button get black screen took out the battery and now the phone didnt even charge or show any signal i will apreciate any help thanks
Dont know if thats SDS (don't know symptoms) but did you ever check to see if your phone is safe?
Sent from my SGH-T889 using xda app-developers app
can u explain what u mean by safe.....
Sent from my SGH-T889 using xda app-developers app
Certain SGIII and GNII chips are vulnerable to SDS... I meant, by chance did he download eMMC Brickbug to verify what type of chip he has and if it chip was "vulnerable"?
Sent from my SGH-T889 using xda app-developers app
---------- Post added at 06:21 PM ---------- Previous post was at 06:14 PM ----------
My chip is good but one time my phone died from 6% and wouldnt start charging through any wall plug, so I then pulled the battery, waited 30 seconds, and it started charging.
20-30% later I turned on the phone, and it hasnt had an issue since (even through rom/kernal flashes)
Sent from my SGH-T889 using xda app-developers app
Where do you get the program to verify?
It happen again to me. But I was at 100% charge. Weird...
Sent From Land Of Ooo. Using a Jedi Mastered Note 2.
acjames said:
Where do you get the program to verify?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my GT-N7105 using xda premium
It says no. Sane chip?
Sent From Land Of Ooo. Using a Jedi Mastered Note 2.
Its not whether it says sane or not... what matteres is the chip you have... screenshot please
Sent from my SGH-T889 using xda app-developers app
Sent From Land Of Ooo. Using a Jedi Mastered Note 2.
My phone has been randomly turning off for no reason. But only when I'm on battery, does nothing when I'm plugged up. I haven't dropped it or done anything to damage it. It's just a little under a year and a half old. At first I thought it was my rom being screwy. So I flashed back to PA 1.98 and it still turns off randomly. When it turns back on the battery will be about 25%-70% lower than it was when it died. So I'm thinking my battery has a short in it or something that makes it lose power randomly long enough for the phone to turn all the way off, but I don't wanna drop the money for a new one (broke right now...stupid speeding ticket) just for it to still be messing up. So does anyone know of any software/rom issues that would be causing this? I'm currently running Condemned's CM7.
If it's a short mine has one as well. I'll get a black screen then nothing n it'll pop back on after a semi short wait or battery pull n same about the battery.
Sent from my HTC Droid Incredible 2 using xda app-developers app
Mine has been doing that from time to time too.
Its getting worse and starting to really get annoying. It pretty much always does it unless its plugged up
Sent from my Incredible 2 using xda app-developers app
JehC said:
Its getting worse and starting to really get annoying. It pretty much always does it unless its plugged up
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Well it is a year and a half old phones do tend to age and as well as battery. I'd look for batteries on amazon maybe even a new charger.
Sent from my SCH-I535 using xda app-developers app
not only did a new battery fix the problem, i got one for 6.39 free shipping off amazon and now my battery literally last 4 times as long.
So I left my S4 under my pillow while I was making a nandroid backup via CWM Recovery and I fell asleep. When I woke up, the phone was still on recovery mode and it was really hot when I picked it up. When I rebooted the S4, a messaged popped up (after it finished booting). It said something about the battery overheating and my phone has stopped charging. There was also a red led light flashing and the battery icon was flashing as well. I can charge it now but I was wondering if there's any long term effects to this.
Sent from my SGH-M919 using xda app-developers app
Extra Info - My battery temp was at 44 Degrees Celsius when I picked it up and my CPU temp was 66 Degrees Celsius.
Sent from my SGH-M919 using xda app-developers app
Mine phone is hot too but never got msg like that. May be ur battery got problem.
Sent from my SGH-M919 using xda premium
I did leave it on for about 7 hours, under the pillow, and on the CWM Recovery screen which is probably at full brightness.
Sent from my SGH-M919 using xda app-developers app
I wouldn't worry too much about it. It stopped charging to percent damage. So just let it cool and you should be alright. I've done it before myself with my s3. Everything still works though.
Sent from my SGH-M919 using Tapatalk 2
Thid exact thing happened to me on my S3, I was also making a nandroid and fell asleep. When I woke up, phone was hot as hell. Didn't see any problems afterwards though.
Sent from Flip's Galaxy S4
Making a nandroid is anyways boring lol!
Sent from my SGH-M919 using xda app-developers app
WOW I can't believe a lot of peoples fall to sleep during nandroid . I need to do a nandroid when I have a hard time sleeping that night woo hoo.
Twrp Recovery turns screen off automatically fyi
Lmao!! @makomek Gonna give it a try, will report back
Sent from my SGH-M919 using Tapatalk 2
kevin95 said:
I was wondering if there's any long term effects to this.
Click to expand...
Click to collapse
Although this hasn't happened on my GS4. This did occur on my previous phone (G2x) when I simply left it to charge overnight while running some unstable ROM/Kernel/OC combinations.
It happened multiple times and may have affected my overall battery life and possible system stability. But otherwise it never created a problem. I've often heard excessive OC or overheating can shorten the lifespan of hardware as well, but my last phone overheated multiple times and its been without fail for 2+ years.
I wouldn't worry about it too much, but always be careful.