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..
Related
damn.. today I got a complete freeze of my HD2 running on original ROM, original radio and HSPL1.42..
It was very low on batt (4%) and I was searching a file on Total commander.
has anyone got one of this before?
holy cow WTF, i would leave it of for a while then charge it turned off, try again, I never seen that man.
Can you enter the bootloader? Btw. I've never seen such an issue.
It was the first one.. (and I hope the last one) and I got scared like hell!
BTW I pulled off the battery and it came back to life. Now it is charging normally and everything is ok..
Just wanted to know if someone else have faced this kind of hangs..
de Wolfe said:
Can you enter the bootloader? Btw. I've never seen such an issue.
Click to expand...
Click to collapse
thank god it was just a hang... everything is ok now..
I have seen it on other units when the battery gets critically low. Some units will go into a continuos boot cycle,others will turn off, and some others will hang on certain screens..... Glad that you sorted it out.
Later
woah! that green color is freakishly close to the HTC theme "green".
its as if the HTC "HAL" inside is trying to come out, like it had become "self aware" for a fleeting moment
beware!
God damn... ^^ You made me freak out after 4 dead Xboxs due to the red ring of death...
hdbueller said:
I have seen it on other units when the battery gets critically low. Some units will go into a continuos boot cycle,others will turn off, and some others will hang on certain screens..... Glad that you sorted it out.
Later
Click to expand...
Click to collapse
I remember old days with my 2nd winmo device.. it was an HP IPAQ running WM 6.0, when the battery was really really low, it started rebooting on an endless cycle.. Now this is my 4th winmo device, I never thought ill see something like that again...
Paschinski said:
God damn... ^^ You made me freak out after 4 dead Xboxs due to the red ring of death...
Click to expand...
Click to collapse
you really can't immagine my freaked out face while looking at the green screen...
i want it... i want it...
got same trouble often with any batt status
agreed with previous replies, gsod in this case probably more relates to low battery...
in wm, using sync mode when connecting to pc via usb cable, reboot to android, and you will not get gsod... at least works for my hd2: either using this way or reboot when battery is not too low (above 40%??)
Someone got their hands on the rare HTC Hulk...
Never seen that solid gsod before -- at least outside of the Android port's early builds.
I GOT ONE TOO!!!
but mine was while booting into Android
Never seen one within WinMo though... ever.
leepriestenator said:
I GOT ONE TOO!!!
but mine was while booting into Android
Never seen one within WinMo though... ever.
Click to expand...
Click to collapse
I too have had it with android, allot of people have!
But never ever in winmo, Ive never even heard of it till now!
got it when booting to android too
GSOD repeatedly
Hi, this is really scary. This morning I had so far 5-6 GSODs. Battery's fine (90%). The only different thing is the GSM's turned off since I'm in roaming. After a GSOD the screen is hanging on the white screen with the ROM details 3.14 ROM btw. Reset needed after that too. Original batteries. First time it happened it was during a USB sync.
Is anyone getting the same?
No Android, no ROM experiments.
------edit
Getting out the microSD card helped. I uninstalled a couple of programs, now it's all right.
I remember installing some multialarm program and IMDB mobile, midomi all from OPNmarket. They are out of my phone now.
do a hard reset
GSOD
I got the same thing on WM. i send my phone to htc for warranty, and they replaced my motherboard. dont why but they did. since that moment i got the GSOD. it also keeps rebooting. very annoying. called htc and im getting a new phone. hope this helps
GSOD Moto Triumph
The same senario has happened to me and I can't seem to get my Triumph to work again. Any tips would be appreciated.
hey all dumb question and yes I know there are tons of threads on this
but i want to find out just how common this is and also is there any correlation between touchscreens stopping and using android?
The reason I ask is because this will be the second HD2 I have sent back to tmobile
Thanks,
Yonu
ok here is a odd on i just placed the battery back in the HD2 and the touchscreen works should i still send it back in or not worry about it
Are you putting any stress to the front of the screen - like putting it in your pocket or have a case that may be too tight?
People here have been using Android for many months and we would have seen more posting of failed screens. Software should have no bearing on the touchscreen AT ALL. Heat may be another issue - possibly your phone or battery is getting super hot and may be causing a poorly soldered bridge to open up. This would be one theory and that would only mean you have a poorly constructed phone. I've been using Android daily for the past couple of months and my phone does have a tendency (based on battery widget) to run on the warm side around 40C during peak periods - phone on, etc. with GPS running but I don't think thats out of the norm because I think when running WINMO it ran at that temp during load.
If you are still under warranty or have insurance - send it back but first check your temps or maybe it could be a bad battery - bad power sometimes does strange things.
The interesting thing is that all the people with this problem seem to be T-mobile HD2 users, I would like to know if any Euro HD2 has this problem.
I had the problem on an EU HD2. Started a few weeks after installing android.
reflashed back to stock rom and returned it for repair and had no problems with that (until I broke the damned LCD screen
Been running it on android for 2 months now (Nand version - no WM at all) and had zero problems
I would really appreciate any suggestion in regard to this topic. I have a Tmous HD2 that is still under warranty with T-Mobile. I need to return the device back for a replacement as two out of three of the metal pieces in the back where it touches the battery are badly bent out of shape and they seem as if they can jz break off anytime. I guess this is the result of playing with different roms and having to take the battery out for resets
My question is .. what is the best way to restore it back to factory rom/radio? I have hspl3 and upgraded radio to 2.15 and I later also have mgldr 1.13 installed as well. Can someone please tell me how I can find/flash a stock rom/radio and wipe out all that stuffs to return it? I remember seeing a thread on this topic a while back but couldn't find it now.
Again, any help or suggestions are greatly appreciated .. thanks guys!!!
Sent from my HTC HD2 using XDA App
Go to the TMo site, find the HD2, there there'll be a tab with 'downloads'. Then just download the stock ROM from there and flash it from HSPL from the RUU.
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
samsamuel said:
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
Click to expand...
Click to collapse
Sam! You're always correcting me, stop it! haha.
This might be a silly question but what you are referring to as 2.08 and 2.10 is the radio right? So jz the stock rom then radio? And thanks a lot for the fast respond guys .. I love the spirit of this community
samsamuel said:
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
an easier way
flash the stock ROM you got from HTC via SD, that way it overwrites HSPL with the correct SPL and flashes the correct radio that came with your phone.
You really don't want to end up like this guy:http://forum.xda-developers.com/showthread.php?t=1025001
so make sure you are good to go before sending it in.
qdochemistry said:
I need to return the device back for a replacement as two out of three of the metal pieces in the back where it touches the battery are badly bent out of shape and they seem as if they can jz break off anytime. I guess this is the result of playing with different roms and having to take the battery out for resets
Click to expand...
Click to collapse
I am not trying to be a wise ass here, but I really do not understand people always wanting to do a battery pull to do a soft reset of their HD2. It has a soft reset button on the back under the battery cover. Now I am no Enstien or Sir Isak Newton but the designers of the HD2 had tro have included this for a reason. I think the reason was to be able to reset the device without doing a battery pull as the pins for the battery on the HD2 are some what delicate. Doing a battery pull not only puts more ware and tear on the battery pins, but the abrupt loss of power is some what detrimental to the performance of the device as well. You see the devices software has protocols that it goes through to shut down just like the IPL of bootloader initializes all the hardware on boot it has to up shut everything down. When you do a battery pull the hardware that did not get de initialized at shut down may have problems initialized on start up, this leads to one having to do a hard reset and thinking the device is crap or the ROM is crap. When actually it is kinda their own doing that has messed the performance of the device up. I mean the hardware and software have to be functioning correctly together for the device to perform at expected levels.
Thanks for the heads up .. imma read up on it before trying cuz I haven't flash by SD before
Sent from my HTC HD2 using XDA App
http://shipped-roms.com/index.php?category=windows mobile&model=Leo
maybe there is your ROM
I have two HD2 and the other one is for my wife .. when you are on the go or on an important phone call and it freezes on you (happens a lot back then with the early days of winnow roms and beta android) its jz convenient to reset by pulling battery cuz I don't carry anything on me specifically that fits the tiny button. As far as performance goes, both devices are running rock solid regardless of the battery pulls.
When I do test a rom and experience problems I simply report back to the chef hoping there will be a fix .. and if I am the only person experiencing it then it is something on my part. However, that has never been the case!
As for your comment, I definitely agree with everyone in this forum that HD2 is the most flexible device to date. Since we didn't want to be bound to the additional 50/mth data plan contract for both devices we bought them at retail price. Even with that price .. and even if both of them malfunction at this point, I have no regret about my decision! We had so much fun playing with this phone and we are proud owners of HD2.
I created this thread as it was unfortunate that one of them has its pin coming loose and I need to seek help from the community. Thanks again .. to those members that pointed me in the right direction.
For the record, I'm also NOT Einstein or Newton .. but I am a PhD chemist. I wont say that you are being a wise ass .. but I think your comment is harsh and irrelevant!
T-Macgnolia said:
I am not trying to be a wise ass here, but I really do not understand people always wanting to do a battery pull to do a soft reset of their HD2. It has a soft reset button on the back under the battery cover. Now I am no Enstien or Sir Isak Newton but the designers of the HD2 had tro have included this for a reason. I think the reason was to be able to reset the device without doing a battery pull as the pins for the battery on the HD2 are some what delicate. Doing a battery pull not only puts more ware and tear on the battery pins, but the abrupt loss of power is some what detrimental to the performance of the device as well. You see the devices software has protocols that it goes through to shut down just like the IPL of bootloader initializes all the hardware on boot it has to up shut everything down. When you do a battery pull the hardware that did not get de initialized at shut down may have problems initialized on start up, this leads to one having to do a hard reset and thinking the device is crap or the ROM is crap. When actually it is kinda their own doing that has messed the performance of the device up. I mean the hardware and software have to be functioning correctly together for the device to perform at expected levels.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
Awesome!! I'll look thru those .... thanks
birdra said:
http://shipped-roms.com/index.php?category=windows mobile&model=Leo
maybe there is your ROM
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
qdochemistry said:
For the record, I'm also NOT Einstein or Newton .. but I am a PhD chemist. I wont say that you are being a wise ass .. but I think your comment is harsh and irrelevant!
Click to expand...
Click to collapse
I am truly sorry you feel this way about my comments as they were truly not meant that way. I just felt it was needed to further point out the cause of your problem as so many have suffered the same problem as you. I have seen plenty with your problem here in the forums. Even you yourself admited it was a problem of your own making. I do not carry something around to push the rset button with either but I am a firm believer in using the reset button and not doing a battery pull.
I am glad you and your wife have not experienced any bad side effects off doing a battery pull. But when I first got my HD2 8 months ago I was doing battery pull after battery pull and the more I pulled the battery the worse my HD2 got. It would freeze one the orange Windows splash screen at least 10 times in a row, I tried hard reset after hard reset and no joy. So I got a replacement HD2 sent to me and I have not done one battery pullthe whole 5 and a half months I have had it. I am running Android on it now but that has only been for a little over a week. ran stock ROM on it until now besides testing several custom ROMs out for a couple of hours to a day. I hardly had any lock up or freeze issues the whole time.
I hope you get your problem fixed, but please just take my words into consideration.
Thanks for sharing the experience .. afterall it is what the xda community is about
T-Macgnolia said:
I hope you get your problem fixed, but please just take my words into consideration.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
T-Macgnolia said:
I am truly sorry you feel this way about my comments as they were truly not meant that way. I just felt it was needed to further point out the cause of your problem as so many have suffered the same problem as you. I have seen plenty with your problem here in the forums. Even you yourself admited it was a problem of your own making. I do not carry something around to push the rset button with either but I am a firm believer in using the reset button and not doing a battery pull.
I am glad you and your wife have not experienced any bad side effects off doing a battery pull. But when I first got my HD2 8 months ago I was doing battery pull after battery pull and the more I pulled the battery the worse my HD2 got. It would freeze one the orange Windows splash screen at least 10 times in a row, I tried hard reset after hard reset and no joy. So I got a replacement HD2 sent to me and I have not done one battery pullthe whole 5 and a half months I have had it. I am running Android on it now but that has only been for a little over a week. ran stock ROM on it until now besides testing several custom ROMs out for a couple of hours to a day. I hardly had any lock up or freeze issues the whole time.
I hope you get your problem fixed, but please just take my words into consideration.
Click to expand...
Click to collapse
I am of the same opinion with you.
In the past, I frequently flashed my Leo and used to remove the battery for easy and fast hard reset. I just followed the instruction in the relevant threads without thinking that it might damage the NAND.
I experienced many freezes but I just ignored it until the time when I cannot flash NAND Android anymore and I found it so many badblocks in the NAND.
Luckily, I still can go back to Winmo. Although, some custom roms still cause freezing. But, with Athine OS (check my sig) I never experience freeze so far, and I still can use Android via SD Card.
Cheers...
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
After I updated my Nexus 4 about a week ago it already shut down by itself 3 times. The weird thing is that in all three times it happened it was in some place somewhat hot, two times I was in the beach, and both happened like an hour apart from the other (until I picked up the phone and noticed it).
And another one was after I got in my car that was left in the sun and put the phone in the door.
It's important to mention that the phone was exposed to this kind of situation many times before the 4.3 update and it never ever shut down.
Crazy, right?
Yuri.. said:
After I updated my Nexus 4 about a week ago it already shut down by itself 3 times. The weird thing is that in all three times it happened it was in some place somewhat hot, two times I was in the beach, and both happened like an hour apart from the other (until I picked up the phone and noticed it).
And another one was after I got in my car that was left in the sun and put the phone in the door.
It's important to mention that the phone was exposed to this kind of situation many times before the 4.3 update and it never ever shut down.
Crazy, right?
Click to expand...
Click to collapse
Sometimes the CPU is intelligent enough to power off itself when it detects that there are extremely temperatures. This is to prevent damage. I´m not sure if this could be case, because I know this is a feature in many notebooks and desktop computers, but not completely sure if it is present in smartphones.
Galaxo60 said:
Sometimes the CPU is intelligent enough to power off itself when it detects that there are extremely temperatures. This is to prevent damage. I´m not sure if this could be case, because I know this is a feature in many notebooks and desktop computers, but not completely sure if it is present in smartphones.
Click to expand...
Click to collapse
I think the battery might have that. But even if that's the case, in 4.3 it's faulty, like I said, before 4.3 it would never shut down in this kind of situation, and also by surfing the web for a long time the phone gets far hotter than it got in the beach (it was left in a bag, in the shade).
Yuri.. said:
I think the battery might have that. But even if that's the case, in 4.3 it's faulty, like I said, before 4.3 it would never shut down in this kind of situation, and also by surfing the web for a long time the phone gets far hotter than it got in the beach (it was left in a bag, in the shade).
Click to expand...
Click to collapse
Which ROM do you have?. Android 4.3 JW has not many commits and patches from last AOSP repository, so grabbing some AOSP(JS) ROM could be a good idea. Also trying to get another kernel and UV/UC could be also a good idea for heat if you are not a heavy user(games for example).
:silly:
Galaxo60 said:
Which ROM do you have?. Android 4.3 JW has not many commits and patches from last AOSP repository, so grabbing some AOSP(JS) ROM could be a good idea. Also trying to get another kernel and UV/UC could be also a good idea for heat if you are not a heavy user(games for example).
:silly:
Click to expand...
Click to collapse
I'm using the stock rom
Yuri.. said:
I'm using the stock rom
Click to expand...
Click to collapse
Try to change your 4.3 build to some AOSP variant, that could help.
:fingers-crossed: