Database Users

Android Overheating, temporary screen freeze.

Good morning,
I did a search for this topic but didn't find anything which could help so I thought I'd start a new thread and ask you guys.
I have installed the Desire version of Android and it runs fine apart from two issues.
The first is that when the phone is plugged in to either the wall charger or the PC it gets really hot. The heat is coming from the back of the phone but right at the bottom (not from the battery). It got so hot after around twenty minutes last night that I rebooted it into Windows just so I could charge my phone overnight. Windows has no similar issues, by the way.
The second thing is that sometimes the screen becomes unresponsive while running Android. This is mainly on the homescreen and you have to usually turn the screen off (stand-by) and switch it back on again to make it work.
If anyone can offer any solutions to either problem I'd very much appreciate it. If I've left anything out, let me know. It's nearly 7am and I'm barely thinking straight.
Many thanks.

i get the same heat issue whether its plugged in or not(its much worse when its plugged in though). this & the battery life are why i cant run android for more than a couple hours. im sure theyre related too. the heat scares me, i dont want anything to fry out. as soon as i boot back into windows it cools right down. i really hope this issue gets fixed soon.

yeah the problems you have are what some ppl have and to my knowledege they have not been fully solved yet. But its still a work in progress, just give it some time

I can deal with the overheating I turn the screen off for a while and its good.
What I can't deal with is THE CONSTANT FREEZING!
It's really starting to piss me off!!
I think its because of the class 4 SD card, I'll get a class 6 SD some time this month and I think that should help out A LOT!

i 100% using external charger with few batteries, so i've never realize the problem.

find a good task manager app from the marketplace and kill all apps that are running in the background. that cooled down the device quite a bit for me

i don't think so
tuppaacc said:
I can deal with the overheating I turn the screen off for a while and its good.
What I can't deal with is THE CONSTANT FREEZING!
It's really starting to piss me off!!
I think its because of the class 4 SD card, I'll get a class 6 SD some time this month and I think that should help out A LOT!
Click to expand...
Click to collapse
i don't think so. mine is 8GB class 4.
I think it may be related to your radio and rom.
I am on claudyfa's 1.5 rom and 2.12.xx radio - you can give it a try
If I use a lot of apps in android, it gets really hot, like in win mo. but android is hotter
good luck

It's freakin beta. Secondly use set CPU and lower your clock speed. It save battery life also. As far as the freezing its a result of the beta nature of the roms
Sent from my HTC Desire using XDA App

I got the same problem with MdJ Froyo HD 4.4
Is it a known issue now ? Can it be solved by anything ?
PS : Sorry if my message is not very understandable but I don't really speak english ^^

HD2 Bricked???

Alright, so I think I bricked my phone! I had put android on it. 2.2 bluetopia? and everything was running fine. My battery was low so I go to charge it, but before I do that a page I was loading from the net froze on me without realizing and the screen dident turn off. I left and did some things and come back to the phone, screen is still on, still frozen and EXTREMELY hot. I get really nervous and get my phone and its to the point where I cant even hold it for too long without it hurting my hands. I take out the battery and pray for the best. My praying sucks apparently because now it does not turn on. Ive tryed letting the phone cool down though the night and it does not turn on. Ive tryed taking out sim card and mem card and it does not turn on. Ive tryed taking out the battery and plugging the the charger it does not turn on. Ive tryed with the battery with the charger it does not turn on! phone gets warm when I put the battery back in. Light that indicates when its charging with the charger doesnt turn on. only slight good news is when I turn the power on I feel a slight vibration from the phone like if its trying to turn on but just cant. Hope someone could shed some light and let me know If I should just move on because this sucks!!!!
ps. I hope people learn from my mistake.
pss. What are the return polices from htc or tmobile? Im concerned because I bought the phone second hand.
thanks for reading/helping.

As far as any return/exchange, it's definitely a no on both HTC &T-Mobile... And if she won't even boot at all, it sounds like a classic but common overclocking mishap.
Sorry to say, but it may be time to move on.
Sent from my HTC Desire using XDA App

One question for my personal understanding: Android ROMS that are offered here on the board are not innatelly overclocking my HD2, are they?! Now I´m really anxious, due to the fact that i´m using biffmod and my HD2 gets much warmer during strong usage (e.g. gaming)

Try doing a hard reset
Hold Volume up and call end button, it will go to the multi color screen and do a factory reset, this will erase all your data.

If possible, can you try a different battery? If you killed the battery by overheating (which is often easier than killing the phone using the same method), it might not even get to the first screen without power. A sure sign to see if it's your battery, is check the feel of it. if it's in any way bulged or kinda squishy it's probably fried, and if it's just the battery that's a lot cheaper than the whole phone.
In fact, I've gotten quite a few nice phones for real cheap, since the original owner thought it was "broken", when all it needed was a new battery.

cavemaneca said:
If possible, can you try a different battery? If you killed the battery by overheating (which is often easier than killing the phone using the same method), it might not even get to the first screen without power. A sure sign to see if it's your battery, is check the feel of it. if it's in any way bulged or kinda squishy it's probably fried, and if it's just the battery that's a lot cheaper than the whole phone.
In fact, I've gotten quite a few nice phones for real cheap, since the original owner thought it was "broken", when all it needed was a new battery.
Click to expand...
Click to collapse
+1 on this. I also had one phone like this before. Change the battery.

it ended up being the motherboard. i sent it in for repairs through htc and they fixwe it. i tryed your guys suggestions on trying a different battery but it still would not turn on. lesson learned, Im going to try to avoid Android on my phone from now on.

queefinout said:
it ended up being the motherboard. i sent it in for repairs through htc and they fixwe it. i tryed your guys suggestions on trying a different battery but it still would not turn on. lesson learned, Im going to try to avoid Android on my phone from now on.
Click to expand...
Click to collapse
Hate to hear what happened, but staying away from Android doesn't really seem like a solution to me. The percentage of bricks due to Android is very small, so I'd say go out, have fun with your phone while it's still up to date (lets face it, hardware improves too quick) and don't be left behind with WinMo 6.5. That's just not worth it imo. If you stick to non-overclocked kernels you really are pretty safe.

probably go 2 the shop and try 2 get a battery tested into your HD2
if that works, buy the battery

StephanV said:
Hate to hear what happened, but staying away from Android doesn't really seem like a solution to me. The percentage of bricks due to Android is very small, so I'd say go out, have fun with your phone while it's still up to date (lets face it, hardware improves too quick) and don't be left behind with WinMo 6.5. That's just not worth it imo. If you stick to non-overclocked kernels you really are pretty safe.
Click to expand...
Click to collapse
you know what, you make a lot of sense. i did enjoy android quite a bit and will continue to use it. funny thing is I bought the hd2 just for android and did that until my phone broke and now im kinda liking winmo a lot now.

So NAND builds killed my HD2. Nice. Lol.

Well last night, I decided to flash a NAND build of gingerbread. Never thought it would be the last time my touch screen worked properly again.
Since then, my touch screen has been sporadic, working off and on. WP7 or Android.
I flashed back to stock ROM + Radio and the problem still exists. And Im not the first person this has happened to.
Be weary of the NAND builds, ladies and gentlemen.

From what I understand this can happen under any OS. It has nothing to do with just nand builds. It can happen under a 3rd party 6.5 build, Android SD build, WP7........etc
If the temperature of the phone reaches a certain point you can kiss the touch screen good bye.

This is an issue HTC will repair if u send back. But return everything to stock. It's not the roms its the screen. Android. Rocks
Sent from my HTC HD2 using XDA App

But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.

trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
Harware related not software.

trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
I fail to see how flashing a ROM could affect your digitizer in any way (read: it can't).
Just unfortunate coincidence, time to call HTC!

No, it's like blaming Shell for a flat tyre which occurred after you had just filled your tank with their petrol....
Return phone to Factory condition. Contact HTC and send it back. It'll be fine.

trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
It is related to ignorance and hardware not software.
This is NOT a common occurrence, It can and does happen in ANY OS, Its simply that on those occasions that it actually happens while you are using android you get n00bs posting saying "hey android killed my phone", this simply isnt the case.
Its just pure coincidence that your screen decided to fail whilst you was using android. IF it was an Android issue the forums would be flooded with topics/replies about if from everybody who uses Android. Its like saying, "hey I was using linux in a VM on my machine and my monitor failed, must be software related "
I have been using Android on HD1/HD2 for a year+ and have never experienced any TS failure, even in the early days of android builds when power management was an issue and CPU would heat up, plus ive used countless different builds.
Virginise your phone and sent it to HTC for repair.

Well since you decided to reply in such a condescending matter, Ive been doing IT work for the majority of my life.
If NAND builds do indeed increase the heat, that would be a software related issue. IE, the phone wouldnt overheat unless the software said to.
Pure coincidences of this magnitude are rare. And with the amount of time it took to happen, its more then just a mere coincidence.
Get off your high horse for a second. You arent getting paid for posting, so stop acting like it

trill12 said:
Well since you decided to reply in such a condescending matter, Ive been doing IT work for the majority of my life.
If NAND builds do indeed increase the heat, that would be a software related issue. IE, the phone wouldnt overheat unless the software said to.
Pure coincidences of this magnitude are rare. And with the amount of time it took to happen, its more then just a mere coincidence.
Get off your high horse for a second. You arent getting paid for posting, so stop acting like it
Click to expand...
Click to collapse
and this is exactly why i fix my own computer at work rather than call IT; 2 weeks of trade school in IT programs dont beat my 20 years of computer knowledge as a gamer (build my own rigs) and programmer. most people working IT know very little.

I have to agree......while running a rom for the first time or even after the first couple restarts the phone runs very very hot.....sometimes freezing n only choice left is to pull the battery....but if the phone is still too hot magdlr displays fatal error n wont boot till phone cools off takes a minute or 2....but once the rom settles no more issues.....no such behavior on sd roms.....my experience
Sent from my HTC HD2 using XDA App

These phones are not supposed to be used while they are being charged. Plugging in the USB cable to flash the phone not only charges it but also put the screen on. Then it runs a pretty heavy process. That is almost surely how most (if not all) of these screens are damaged. Do you notice it is almost always right after flashing a build that the screen is damaged and not after using adroidn for a day or so?
How about this? How many users do you think plug their phone into a wall charger and charge at around 800ma, and then play Angry Birds? You want to heat up your phone and damage it try that.
Slightly side note: I do not think NAND builds increase the heat. I actaully they reduce energy consumption (evidence in longer run times). You have to use energy (in this case from the battery) to heat up the phone. NAND uses less current and has longer run times. This should result in a cooler phone on average (assuming the phone stays in this demension ;-))
-Unconnected

All in all, this discussion is irrelevant now. HTC has my phone now (luckily, I live 10 minutes from the Nationwide service center, how quaint) and I should have it repaired by monday.

My experience with this issue
I have been flashing various roms for years here at this site. Including Android Nand Roms here for the last few weeks while they have been available on my HD2 without any issues.
About 5 days ago I installed MDJ's 2.5 (I had previously been using 2.4 with no issue). Right after flashing, the screen would not respond. Went back and tried it again with the same issue. Tried another android rom that had been working fine previously, and the screen would still not respond.
Did a task29 and went back to windows mobile and the screen still would not respond. The hardware buttons always worked.
Finally I started to get some screen response and went back to my NexusHD2-Gingerbread by tytung and was able to restore everything and the screen was fine from then on out.
Thinking it must have been a fluke, the next day I tried it all again. Guess what? Same exact problems happened. Went back to NexusHD2-Gingerbread and it would not respond either. I eventually just started hitting buttons rapidly while hitting the screen and it started to work. Restored everything and the phone (and screen) have been flawless for the last several days.
If this is strictly a hardware problem as several people claim here, it is very unusual.
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.

deweylima said:
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.
Click to expand...
Click to collapse
IMO it is definitely a hardware issue, maybe affected by excessive flashing/heat/etc but not due to software/roms.
Btw, my own HD2 also suffered from a total defective TS some months ago (phone was about 3 months old) and it happened without any flashing with stock WM6.5 out of the blue. No TS response whatever I did. Had to send it to HTC for warranty repair. Got it back repaired and it's working rocksolid since w/o any issues. ATM I am using Gauners HD-FI nand rom and also used some custom WM6.5 roms before. So....
Just my 2 cents here.
Cheers, Olioaglio

Olioaglio said:
IMO it is definitely a hardware issue, maybe affected by excessive flashing/heat/etc but not due to software/roms.
Btw, my own HD2 also suffered from a total defective TS some months ago (phone was about 3 months old) and it happened without any flashing with stock WM6.5 out of the blue. No TS response whatever I did. Had to send it to HTC for warranty repair. Got it back repaired and it's working rocksolid since w/o any issues. ATM I am using Gauners HD-FI nand rom and also used some custom WM6.5 roms before. So....
Just my 2 cents here.
Cheers, Olioaglio
Click to expand...
Click to collapse
I am not suggesting it is not a hardware issue, but I can't seem to figure why it has happened in this manner.
Screen has been rock solid in the almost one year that I have had the phone.
Twice it has happened right after flashing mdj roms. Once was even via clockwork so there was no usb cable connected (and therefore the battery/heat issue via usb theory doesn't apply).
And then once I finally get it to work again, screen is rock solid again.
If anyone has any ideas or theories, I would love to hear them.
Thanks

deweylima said:
I have been flashing various roms for years here at this site. Including Android Nand Roms here for the last few weeks while they have been available on my HD2 without any issues.
About 5 days ago I installed MDJ's 2.5 (I had previously been using 2.4 with no issue). Right after flashing, the screen would not respond. Went back and tried it again with the same issue. Tried another android rom that had been working fine previously, and the screen would still not respond.
Did a task29 and went back to windows mobile and the screen still would not respond. The hardware buttons always worked.
Finally I started to get some screen response and went back to my NexusHD2-Gingerbread by tytung and was able to restore everything and the screen was fine from then on out.
Thinking it must have been a fluke, the next day I tried it all again. Guess what? Same exact problems happened. Went back to NexusHD2-Gingerbread and it would not respond either. I eventually just started hitting buttons rapidly while hitting the screen and it started to work. Restored everything and the phone (and screen) have been flawless for the last several days.
If this is strictly a hardware problem as several people claim here, it is very unusual.
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.
Click to expand...
Click to collapse
Weirdly enough, that was the EXACT SAME ROM I flashed when the touchscreen started dying. I kid you not.

MDJ's build (i think) is already over-clocked. Many times i used his build, my phone heats up fast.I don't know but in my case.this is what i experience. So every time i think my phone is heating. I eventually stop using it and let it rest for a while.Abuse the phone=brick phone.
Is there a way or a tool (Coolant maybe) that we can use so that our phone wouldn't heat up fast? (Couldn't imagine a fan tied to my phone..Haha)

I had my touch screen/phone completely died on me after flashing a nand build. It was fine before nand came out (and i've been flashing for many months now). But, sent it back to tmobile and got a new one. Don't know what the problem was but I had the same issue with OP. Not blaming NAND or anything but yeah...

archiesnet said:
MDJ's build (i think) is already over-clocked. Many times i used his build, my phone heats up fast.I don't know but in my case.this is what i experience. So every time i think my phone is heating. I eventually stop using it and let it rest for a while.Abuse the phone=brick phone.
Is there a way or a tool (Coolant maybe) that we can use so that our phone wouldn't heat up fast? (Couldn't imagine a fan tied to my phone..Haha)
Click to expand...
Click to collapse
Maybe because you have many app's running on the background? I'm using his last rom 2.5 and I'm not experiencing any problems..

Red Light Of Death - Should I Be Concerned?

Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??

S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.

Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...

S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason

S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app

Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348

So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??

Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution

Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2

Yes, it's what I said, ah I forgot this link.
When you search, you find

Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.

Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.

Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.

I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app

Alright. Sounds good.

Got mine last week but it's a Rev 10 not an 11.

indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)

Loosen the screws?? Do you have a link to the YT video?

Ordered mine when they were first available, got it 2-3 weeks later (end of November).

Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again

[Q] How to fix strange battery behavior?

Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...

Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2

This looks pretty strange 0.o
Consider buying a new recovery
HITTTTTTT THANNNKKKKSSS
galaxy star duos ****rooted*** xda offical app ) )

I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.

nwsk said:
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
Click to expand...
Click to collapse
Well *#!$
I'll observate it for the next few days and see if it's getting worse...

If your phone is rebooting as opposed to just powering off, then I suspect it is hardware related (motherboard) as already mentioned.
I do hope I'm wrong though.
Maybe try using it for extended periods while plugged into a charger and see what happens. If it doesn't reboot then it may just be the battery.

Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.

I9500 owner. Had this exact same problem when using older firmware. After updating to the latest one, never had this issue again. Its been two months now, even more.
Try this. Flash the latest available firmware for you phone, not talking about OTA but the downloadable one from any region (whichever is latest for i9505). I guess it may have something to do with the kernel too.
Edit: wait a minute, why is your battery level going up when it isn't even charging in the second screenshot. Middle of the battery timeline. That's weird. I guess you should send the phone back
Sent from my GT-I9500 using xda premium

Its a hardware issue(motherboard).I hope your under warranty.Best of luck .

i have something strange like that also on my device ..
http://forum.xda-developers.com/showthread.php?t=2409284

Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)

E_Cartman said:
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
Click to expand...
Click to collapse
Same problem here. It started three days ago and today I'm barely able to use it... I'm still on warraty and I even have insurance, but it's a major inconvenience anyway.

Mines gone in for repair back to my carrier still no movement despite them having it for 2 days now really should have sent it back to Samsung directly. Will keep you guys posted.
Sent from my Nexus 4 using Tapatalk 2

Will send it in tomorrow. Lady on the hotline told me apparently the motherboard is defect and I'll get a new S4. Exchange, no repair. I'm fine with that...
Sent from my GT-I9100 using Tapatalk 4

That's good to hear, just inconvenience but at least you won't have to pay for it (or have the defect materialize a year later or something)

E_Cartman said:
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Click to expand...
Click to collapse
nikzDHD said:
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
nikzDHD said:
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
Click to expand...
Click to collapse
im4eversmart said:
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
Click to expand...
Click to collapse
Hey
I am new here.
but i was looking for information becuase my s4 9505i has the same problem
shuts of almost everytime i open apps too quickly or stream youtube or some other high usage apps etc.
battery drops up to 50 percent then back 40 percent then to 0 percent, the fact it that the phone never seems to know where the battery is.
by the way my phone is not rooted and i have done the factory reset a few times.
samsung... hmmm.. they seem to be real hard to talk to on the phone, i have had to call them 4 times already about the s4 i ahve had since june, and they just play me off like i am some kind of idiot etc. and deny that there is possibly any reason for random shutdowns, phone freezing, and now this battery/motherboard issue.
next bit is kinda stupid, the phone has a few internal scratches on it from when i ahve stupidly had the phone next to keys and all that. im sure they are going to try and void my warranty and say i have mistreated the phone...
had many phones before, maybe close to 50 and never, never, never have had to ring up a company to try and complain etc.....
any ideas.
I am in Australia,
I am thinking of trying the CONSUMER AFFAIRS kind of threats, but i have to word it the right way...