Database Info

Random Shutdowns and LauncherPro

I've been very careful not to point a finger at a particular app as a cause of random shutdowns (other than aggressive user settings within SetCPU). Before I continue, let me say that I believe there is more than one culprit responsible for shutdowns and that most are caused by non-app related issues.
I've had my third device for 2-1/2 months. No shutdowns whatsover...until I installed LauncherPro last week. Then they started. I removed LauncherPro and - back to normal. Another user on another forum experienced the same effect and caused me to start this thread. I hereby declare an official suspicion that LauncherPro is one of the causes of random shutdowns. Before you react, I understand that many use LauncherPro with no problems. Great. I'm not saying that the app itself is poorly coded, but rather that it may begin a chain reaction in some devices that causes random shutdowns. I have not taken this declaration lightly. I waited a long time before openly stating my theory. I hope it proves of interest.

Are you using Task Killer? I was having the same issue and thought it was Launcher Pro for a while but when I stopped using Task Killer my random shutdown problems stopped.
Captivate Cog 2.2 Beta 9

No task killers.

I've recently had some extended freezes and one force close with launcher pro, and one shutdown when I was launching Vlingo and/or starting bluetooth, can't recall which step. Might be something to do with the recent update.
Sent from my SAMSUNG-SGH-I897 using XDA App

I suppose I can test this out on mine. I'll let you know what I find.

I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.

I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky

pezx44 said:
I suppose I can test this out on mine. I'll let you know what I find.
Click to expand...
Click to collapse
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.

pfroo40 said:
I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.
Click to expand...
Click to collapse
Agree. LP, IMHO, is simply offered as one possible culprit.

tysj said:
I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky
Click to expand...
Click to collapse
You are fortunate, as there are multiple scenarios under which shutdowns have occurred...e.g., during high charge percentages as experienced repeatedly by some. My LP experience is being offered as my phone has served as an otherwise stable environment.

Jack45 said:
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.
Click to expand...
Click to collapse
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.

pezx44 said:
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.
Click to expand...
Click to collapse
Excellent. Two separate potential culprits - charge level and LP. I'm looking forward to your assessment.

I decided to reinstall LP to get a baseline. 6 minutes after unplugging it I tried to turn the screen back on and found that it had shut down. I recharged and repeated. Again I found it had shut down when I checked after 6 minutes.
I then recharged and removed LP. I waited 6 minutes and found that it was still on. I am recharging and will try again after a longer period of time but it looks promising. I will let you know when I have more info.

Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.

pezx44 said:
Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.
Click to expand...
Click to collapse
You have no complaints, my friend. A half hour of uptime is better than 6 minutes!
So, yours is a power-related issue and it looks like CKA is the answer. I wonder if Froyo will address this.

But it was only a half hour when I saw it was off. It could have been 6.5 minutes in.
I'm currently running Froyo (Cognition 8.1). This has been an issue for me since before that though. One thing I can't quite remember is if it happened before I unlocked my phone. Is yours unlocked? I needed to do this because I do not live in the US.

pezx44 said:
Is yours unlocked? I needed to do this because I do not live in the US.
Click to expand...
Click to collapse
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.

Jack45 said:
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.
Click to expand...
Click to collapse
1. I have the same setting for wifi (I use my phone for SIP calls often).
2. I absolutely agree with you on this and it is also already my setting.
3. I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
I'll let you know how things go.
And just in case, by unlocked we are talking SIM unlocked right?

>>> I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
As the timeout for sleep mode is power-related, I wanted to take that out of the Captivate's hands. The on-off switch is OURS to deal with at will. Want the room light on? Turn it on. Etc. Basically, I wanted to generate persistent under-the-cover activity (WiFi) while eliminating decision making activity on the part of the device.
>>> And just in case, by unlocked we are talking SIM unlocked right?
I can place any non-AT&T SIM in the phone and it will work.

No LP issues here since I've owned the phone.
I've had LP on with full charge all the way down to 30% +/- and still ran like a champ.
Currently on Cognition beta 9 - still the same story.
I truly think you have a lemon phone. And I just flashed and haven't tweaked any of the default settings that are "out of the box" after a flash... so I assume they are all default.
The only FC/shutdown issues I've had recently were with Cognition beta 7 and advanced audio manager. I removed it and *poof* no more FC's. And since I was never that concerned with my sound settings (it's on vibrate 99% of the time anyways due to work environment and a lil' guy) I didn't care.
I'd look into getting a refurb - or flashing to Cognition's latest and greatest (hmm... well I would wait for 9.2 as he is having some "growing pains" with his new kernel) and see how it goes then. Can always Odin back to stock if needed.

[Q] Another G2x noob, is my phone going to be a lemon?

I'm kinda hesitant to post this, because I know you guys go through great lengths to emphasize searching first. I watched the video when I registered, nice touch. More forums could use vids like that!
oh well, here we go:
I have owned an Iphone every since they where introduced to the market. I have been wanting to make a switch for a while now. I was very close to purchasing a G2x back in April when they came out, but I held off. Well recently, a coworker let me check out his HTC G2 and I was amazed at the functionality, features, and other misc items compared to my old Iphone 3GS. I was never a fan of the slide out keyboard, so I knew the G2 was not for me.
Last week, I just missed the free promo on T-MO's web site, so Instead I purchased a G2X locally. I was totally unaware of all the problems you guys where having, as the typical review sites never mention these issues.
I have owned the phone for 8 days, So far here is whats been a going on:
7-29-11 Purchased the phone from Best Buy, decided to buy from them since they where the cheapest out the door with out rebate. I hate rebates! lol
Right before I am going to bed, I plug in to charge, and the phone shuts off, I cannot get it to power back up. I did not know about pulling the battery, I thought it had just died. I was going to wake up the next morning and take it back.
7-30-11 When I woke up, I looked around online, and found out about removing the battery and putting it back in. Now phone is working again.
I was able to get the OTA update to 2.3.3, right after the update, I did a master reset.
8-2-11 I downloaded a "radio scanner" app, and the first time I executed it, the phone froze, requiring another battery pull. Afterwards, the app ran fine.
Those are the only 2 major issues I have had.
Here are a few other things I noticed:
Screen: No separation, very slight light blur around top corners with lit black screen. Does not bother me, and I can't really notice it 99% of the time.
GPS: I know some have been having issues with this, for me, The time to get an accurate fix can sometimes take anywhere from 5-30 seconds. Even with the stock toggle always turned on, I do not always have the GPS Icon in the top bar, I don't know if I am supposed to. Can someone please confirm this?
WI FI: Seems to be working like intended, no complaints there.
BT: I have nothing to pair with the phone, so I will probably never know.
Making calls: this is kinda annoying, I will look through my call log and select a person, I see the dialer initiating so I put the phone to my ear, but a few seconds go by and nothing.... I look at the phone and find myself looking at the call log again, like the dialer crashed? Also, during the conversation the screen will turn off. I think this is normal, but when the phone detects motion shouldn't the screen turn back on?
Other than that, I love this phone so far. However, I do not want to swap handset after handset, refurb after refurb with T-MO or LG.
Is it possible that the phone will NOT continue to get worse as time goes on? Or should I take the first shut down as a sign of whats to come in the future? I have a 6 days left to take this thing back, but I am having a major conflict with myself about keeping it. What makes it even harder, Is I have already ordered a 32g micro SD, Trident case, and 3 extra data cables.
My plans are to root it, and run some sort of rom with it once I read up and half ass know what I am doing.
---------------------------------------------------------------------------------------
TLDR:
Have owned phone for a week. Shut down instantly the first time I charged it requiring a battery pull. Froze/crashed due to an app maybe Second battery pull.
Question a few functions but otherwise works like a champ.
Purchased case, micro sd, extra data cables.
thinking of taking it back and cancelling contract to avoid future headaches, but not sure if I should or want to at this point. need avdice please!

Doesn't sound like a lemon. The stock software is buggy. If you're gonna root it and flash another rom then you're gonna love this phone.
The GPS indicator is normal. It only shows when an app is using GPS for your location. Otherwise it doesn't show.
G2X CM7

It doesn't sound like a lemon to me either. I bought mine in April and my phone had a few reboots while charging overnight and two freezes in the first month. It has been OK since then, although I did not do anything about it (and I'm still on Froyo). The only thing I do is that I reboot my phone manually once in 7-10 days because the phone starts to lag. I believe this is normal for all smartphones including iPhone...or am I wrong?

Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.

HTXg2x said:
Oh, forgot to mention when I hit the power button to wake the phone and go to the lock screen, I briefly see the last screen I was in before the phone went into sleep mode. Total lack of QA in my opinion... Will a rom fix this?
And yes Man of La Mancha, the iphone would get somewhat glitchy, but a reboot always took care of it. I didn't really have to reboot it too often, maybe once every 2 weeks or so.
Click to expand...
Click to collapse
The lockscreen issue is a known bug. CM7, or any ROM with 2.3.4+ doesn't have that problem.

Phone keeps randomly powering off!

Hi, been away from the forum, as i have just got back from holiday
i am having a prblem with my desire.. i went to florida, left my phone at the theme parks, desire s, zte blade, ipod touch in the car for 8 hours in around 30-40 degrees. since then, my desire s has been faulty.
my touch, and zte work fine, but my desire has a major problem now. it works normal in use, but when i lock it and put it into sleep mode, when i try to unlock it , it will start up the whole phone again. basically, it powers off on its on randomly in sleep mode.
The problem is really annoying. it is also very common on the desire hd..
http://www.google.co.uk/search?sour...360GB360&q=htc+desire+hd+randomly+turning+off
Im running leedroid port from dhd. i thought the rom was the problem, but it isnt. i flashed other roms, hydrogen, but the problem still exists. shoud i test the stock unrooted ROM?
i dont think it is a software fault anyweay. the phone was working fine for 2 weeks running leedroid, then suddenly i have the problem now.
i have emailed htc, and awating a reply now. so will i need to get it repaired? or replaced as a faulty unit?

Hmm.....does sound like the heat has done it in....damn!
Although there are plenty of other countries where the temp is close to this all the time, you would have thought....
Try installing close to stock ROM with no apps installed, (Yes perform wipe). I'd suggest installing battery moniotr widget and get iot to log full details (including apps), force log in sleep mode so that you can at least see when it dies and what temp it's at when it does and what apps are running at the time.
Although does sound like warranty return issue (at least this way you get a new motherboard and possibly even a new device)...(you might want to check the recommended running temp levels in the warranty book first - just so that you get your story straight)
Positive note: at least its still functioning so that you can re-install RUU etc and mask S-OFF before returning it?
ps
Mines done this a couple of time over the last few months...although I always figured that I've hit the buttons in my pocket?

ben_pyett said:
Hmm.....does sound like the heat has done it in....damn!
Although there are plenty of other countries where the temp is close to this all the time, you would have thought....
Try installing close to stock ROM with no apps installed, (Yes perform wipe). I'd suggest installing battery moniotr widget and get iot to log full details (including apps), force log in sleep mode so that you can at least see when it dies and what temp it's at when it does and what apps are running at the time.
Although does sound like warranty return issue (at least this way you get a new motherboard and possibly even a new device)...(you might want to check the recommended running temp levels in the warranty book first - just so that you get your story straight)
Positive note: at least its still functioning so that you can re-install RUU etc and mask S-OFF before returning it?
ps
Mines done this a couple of time over the last few months...although I always figured that I've hit the buttons in my pocket?
Click to expand...
Click to collapse
Cheers Ben! Love how your always here to help!
I'll try installing battery monitor widget , and go back to stock, s-on
So do you think it was the heat that damaged the phone? My ipod touch and zte blade were left in the car, but they work 100% fine
I've checked the warranty thingy, it says do not expose battery to 60 degrees or higher.
But to be honest, I dot really know how hot it could get in the car... Florida is very hot!
I'm just waiting for a reply from HTC now
The phone works fine everywhere else, its just this problem.. I tried cooling the phone by switching it off and taking the battery out, and leaving it for an hour.
The thing with this problem, is that it is entirely random! It sometimes last ages in standby before the problems occur, or within 10 minutes.
How can I prove it to HTC??
I wouldn't worry too much about your phone doing the same once in a few months or so
Mine is happening at least 6 times a day!!
I'll try to keep the thread updated to how it all goes
Cheers Ben
Sent from my HTC Desire S using XDA Premium App

olyloh6696 said:
Cheers Ben! Love how your always here to help!
I'll try installing battery monitor widget , and go back to stock, s-on
So do you think it was the heat that damaged the phone? My ipod touch and zte blade were left in the car, but they work 100% fine
I've checked the warranty thingy, it says do not expose battery to 60 degrees or higher.
But to be honest, I dot really know how hot it could get in the car... Florida is very hot!
I'm just waiting for a reply from HTC now
The phone works fine everywhere else, its just this problem.. I tried cooling the phone by switching it off and taking the battery out, and leaving it for an hour.
The thing with this problem, is that it is entirely random! It sometimes last ages in standby before the problems occur, or within 10 minutes.
How can I prove it to HTC??
I wouldn't worry too much about your phone doing the same once in a few months or so
Mine is happening at least 6 times a day!!
I'll try to keep the thread updated to how it all goes
Cheers Ben
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Hello,
Could have been the heat, but could simply be a faulty motherboard....either way a new device might be a good thing, 1/2 way through your warranty period.
Don't know how hot it gets in cars in Florida....but I know that it can kill pets let alone phones!
Cheers, not worried about my phone, just trying to relate that's all
You're just going to be have to forcefull in your email and exaggerate...even
best of luck

ben_pyett said:
Hello,
Could have been the heat, but could simply be a faulty motherboard....either way a new device might be a good thing, 1/2 way through your warranty period.
Don't know how hot it gets in cars in Florida....but I know that it can kill pets let alone phones!
Cheers, not worried about my phone, just trying to relate that's all
You're just going to be have to forcefull in your email and exaggerate...even
best of luck
Click to expand...
Click to collapse
Yeh thanks I think it must be the heat that damaged the phone; it was working perfectly before for the last 3weeks!
My phone is just a month old now
Hopefully they just send me a new phone
I tried to act pleading in the email, but I did not mention anythig about leavig it in heat or the car. I just said it keeps crashing on me...
Hopefully I get a reply soon tommorow!
Sent from my HTC Desire S using XDA Premium App

Though my phone was not left anywhere where temp was extreme, mine is also doing this since this week,, Also a few months old and I blame the apps installed . I ahd battery monitor and suspected just that prog..
I have not yet gone to a clean rom yet but selectively remove apps till I find improvement....
Meaning there are others with the same problem !
olyloh6696 said:
Hi, been away from the forum, as i have just got back from holiday
i am having a prblem with my desire.. i went to florida, left my phone at the theme parks, desire s, zte blade, ipod touch in the car for 8 hours in around 30-40 degrees. since then, my desire s has been faulty.
my touch, and zte work fine, but my desire has a major problem now. it works normal in use, but when i lock it and put it into sleep mode, when i try to unlock it , it will start up the whole phone again. basically, it powers off on its on randomly in sleep mode.
The problem is really annoying. it is also very common on the desire hd..
http://www.google.co.uk/search?sour...360GB360&q=htc+desire+hd+randomly+turning+off
Im running leedroid port from dhd. i thought the rom was the problem, but it isnt. i flashed other roms, hydrogen, but the problem still exists. shoud i test the stock unrooted ROM?
i dont think it is a software fault anyweay. the phone was working fine for 2 weeks running leedroid, then suddenly i have the problem now.
i have emailed htc, and awating a reply now. so will i need to get it repaired? or replaced as a faulty unit?
Click to expand...
Click to collapse

A2Z said:
Though my phone was not left anywhere where temp was extreme, mine is also doing this since this week,, Also a few months old and I blame the apps installed . I ahd battery monitor and suspected just that prog..
I have not yet gone to a clean rom yet but selectively remove apps till I find improvement....
Meaning there are others with the same problem !
Click to expand...
Click to collapse
Yeh, some of them have the same problem after a couple if weeks old (not exposed to heat or anything) what causes this problem?
How often do u have this problem??

My old Nokia 5230 has the same problem

Mine has the same problem and has never been exposed to extreme heat. I think the power button is faulty and after some use it get stuck some times and closes the phone down. I started pressing the button with less force and the random power downs stopped happening.

What happened? I have not found a relationship yet. It seems random too me so far. If it happens once more i will go to factory default plain htc stock rom (i have not fiddled with the device or rom)
If it then happens as well i know enough. I will see and report me experience in due time.
Btw its android 2.3.3 build 1.47.401.4
Sent from my HTC Desire S using XDA App

A2Z said:
What happened? I have not found a relationship yet. It seems random too me so far. If it happens once more i will go to factory default plain htc stock rom (i have not fiddled with the device or rom)
If it then happens as well i know enough. I will see and report me experience in due time.
Btw its android 2.3.3 build 1.47.401.4
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
To be honest, I think its more of a hardware problem!
My phone was running fine on stock and custom roms for 3 weeks, then it just started last week when I left my phone in the car
A lot if desire hd users had the same issue as us!
I'm awaiting a reply from HTC now
Will update on what they say.

the heat probably was the culprit
my phone reaches around 45c at times due to the high outside temperature here,but i don't have any problems so i guess yours was heated more
but if you can, try changing the battery it may help

Random shutdown
I also suffered from this. A new Radio + ROM + cleaning some apps has solved the problem.

Thanks for the replies everyone!
I received the following e-mail of HTC today:
Dear Oliver Loh,
Thank you for contacting HTC regarding your HTC Device.
I understand that you are currently experiencing difficulties with rebooting and random restarts.
I believe that the reason for this is because of a hardware issue.
In order to rectify this I would like you to perform the following actions:
) Make sure your device is fully up to date:
Menu - settings - about phone - system software update - tick box - check now.
) If possible test the device with or without a (new) battery, SIM, SD card.
To assist you further I have attached links to the HTC Support Site which will enable you to work through the above step by step:
http://www.htc.com/uk/support.aspx
Once the above has been completed you may be required to do a factory reset, for your convenience I have detailed the steps below:
) Restarting or factory resetting your phone:
Restarting your phone (soft reset):
If your phone is running slower than normal, an application is not performing properly, or your phone becomes unresponsive, try restarting your phone and see if that helps solve the problem.
Please remove the battery, wait for a few seconds, reinsert the battery, and then turn the phone on.
Performing a factory reset (hard reset):
Note: Factory reset will not remove the data and files that are in your phone’s microSD card.
Factory reset is not a step to be taken lightly. It will permanently delete all your data and customized settings, and will also remove any applications you've downloaded and installed. Be sure to back up any data and files you want to keep before you do a factory reset.
Performing a factory reset via settings
Performing a factory reset using phone buttons:
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
1. With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
2. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button..
3. Press VOLUME DOWN to select CLEAR STORAGE or (Factory Reset), and then press POWER.
4. Press VOLUME UP to start the factory reset.
Should the above solution not resolve your query please can you confirm the following and reply to me:
1) Has the device been recently updated/upgraded or changed:?
2) Has a new application been recently downloaded:?
3) Please can you turn off all applications and UN-install any which are unessential, As they may be causing issues:?
4) What have you already done/tried to troubleshoot your issue/s:?
5) When did your issue/s occur or re occur:?
6) Is you device or applications fully up to date:?
Should the above fail to restore your device to full working order, the device (MAY) need to be sent for repair.
I hope that this information meets with your requirements, should you have any further questions please do not hesitate to contact us again.
If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxxxxxxx.
Sincerely,
Robert
HTC
Want to see what others are saying? Have a question to ask other HTC fans?
Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc
Explore our development resources developer.htc.com
We are unable to receive replies to this email account. Please visit us at htc.com if you have any questions or need further assistance.CONFIDENTIALITY NOTE : The information in this e-mail is confidential and privileged; it is intended for use solely by the individual or entity named as the recipient hereof. Disclosure, copying, distribution, or use of the contents of this e-mail by persons other than the intended recipient is strictly prohibited and may violate applicable laws. If you have received this e-mail in error, please delete the original message and notify us by return email or collect call immediately. Thank you. HTC Corporation
Click to expand...
Click to collapse
And today i can confirm the problem has occured 8 times today. Now it can do the problem up to 3 times in a row, when the device is in use.
It happened this morning 3 times, 2 in the afternoon, and as i am typing now, i just booted into recovery and the phone crashed on me twice at the recovery screen.
I will reply to HTC and tell them i have the stock rom etc, and will s-on my device and send it for repair soon hopefully

So what's your uptime since you changed??
rotem said:
I also suffered from this. A new Radio + ROM + cleaning some apps has solved the problem.
Click to expand...
Click to collapse

If the problem persists through multiple ROMs, it definitely sounds like a hardware problem. I'd return it to stock and have it sent in for repair under warranty.

Haven't read all replies... but this is a well-known battery fault (and isn't necessarily triggered by either heat or humidity... it is most commonly a manufacturing defect).
My very first HTC Desire S handset had almost exactly the same issue, only the battery from that handset would power off the phone only when the GSM picked up a signal (I.E.... you get reception, but the phone kills itself instantly. No reception, phone ran fine).
O2 replaced the entire thing under warranty (but I sneakily kept the battery to prove my theory). I placed that battery into my replacement handset, and behold.... EXACTLY the same thing!
Put the new battery in, everything works perfectly.
Bottom line: don't replace the phone, just replace the battery!

LaKraven said:
Haven't read all replies... but this is a well-known battery fault (and isn't necessarily triggered by either heat or humidity... it is most commonly a manufacturing defect).
My very first HTC Desire S handset had almost exactly the same issue, only the battery from that handset would power off the phone only when the GSM picked up a signal (I.E.... you get reception, but the phone kills itself instantly. No reception, phone ran fine).
O2 replaced the entire thing under warranty (but I sneakily kept the battery to prove my theory). I placed that battery into my replacement handset, and behold.... EXACTLY the same thing!
Put the new battery in, everything works perfectly.
Bottom line: don't replace the phone, just replace the battery!
Click to expand...
Click to collapse
Hmm.. it does make a bit more sense that the heat could have affected the battery rather than the phone itself.
The battery is probably unable to run under low power that is used when put in sleep mode so it just cuts itself out altogether.
My hypothesis...

i have the exact problem!!
i thought i was the only one... mine turns off at least 3-4 times a day for no apparent reason.
at first, i thought it was the heat during the summer.. but now that the temperature is getting milder i dont really think thats the cause.
sometimes when i place it on the desk and i tap it or just bump it hard enough it'll turn off.
i think its more of a hardware problem then software.

Julzx said:
i have the exact problem!!
i thought i was the only one... mine turns off at least 3-4 times a day for no apparent reason.
at first, i thought it was the heat during the summer.. but now that the temperature is getting milder i dont really think thats the cause.
sometimes when i place it on the desk and i tap it or just bump it hard enough it'll turn off.
i think its more of a hardware problem then software.
Click to expand...
Click to collapse
That's sounds like a bad battery connection, I'd take it back under warranty {if possible} as the chance of a fried eMMC chip must be high!

[Q] Nexus 5 Screen Tantrum

My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?

DutchessDucky said:
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
Click to expand...
Click to collapse
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.

FourPointedFreak said:
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
Click to expand...
Click to collapse
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.

DutchessDucky said:
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
Click to expand...
Click to collapse
Well based on my experience with Google and Nexus devices, typically they'll try hard in your situation to get a you a new device and sooner. They'll probably resell yours as a refurb but issue you a new one.
Fingers crossed.

Question 7Pro - Screen locked up 2 times now.

I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.

This happened to my wife's Pixel 7 the first morning she had an alarm set with it.
Did you by any chance snooze it half a dozen times? It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.

That sounds familiar as if it might've happened once on my OG Pixel years ago, but I can't say for sure.
rczrider said:
It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.
Click to expand...
Click to collapse
LOL! Good point.

No snoozing and it just locked up for the second time just now. The time is displayed but stuck at 8:16 and it currently 9:57, never had this issue on the 6. I'm wondering if I have bad RAM or something that is causing random lockups.
I do see that it vibrates when I press and hold the power button but I can't see what it's doing with the screen locked up.

Talking to support, they wanted the IMEI number and a picture of the screen? The screen looks normal but is locked up. ???
They have to put me on hold to talk to someone else for each part of the questions. I called Google support but it sounds like someone overseas.
I don't see what they can do, other than replace it. I copied everything from the old phone that was working fine.
They want me to back it up and do a factory reset. I just did that when I got the phone a few weeks ago.
Then they asked that I run the phone in safe mode for a few weeks to see if its a bad app that was installed.
I asked to speak with someone more knowledgeable and they needed to put me on hold again saying I could get an email from someone or wait to talk with someone. They then said I had to give consent for them to look at all my data. ??? After the long hold I was told that I'd be getting an email. Total waste of time.

My screen froze and became unresponsive when I swiped down for notifications while watching non-fullscreen video on Youtube TV. The audio continued to play. I recovered by holding down the power button for 60 seconds to force a reboot. I can't duplicate it though.

I have had these screen freezings too. By pressing power button for 30 sec it boots the phone back up. Then after a minute or an hour it happens again. Had to do factory reset two times already. That's the only thing that helps.
I have no idea of what is causing that.

Mine has done it three times now, had to power cycle it as mentioned above, and each time it was a different app

Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.

Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
SystemUI has crashed a few times on mine, which causes a lockup. Rebooting seems to fix it, for the most part.

Tanquen said:
Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.
Click to expand...
Click to collapse
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.

miimaa said:
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.
Click to expand...
Click to collapse
Just rebooting the phone fixes it for a little while. That's the trouble with random inconsistent issues. It could take a week or two or more for it to do it again. With a number of others having similar issues I don't think a factory reset again is going to do anything. I just got the phone a month or so ago and it was at factory default. What good would it do to put it back to factory again? Sounds just as unreasonable as using my phone for several weeks in safe mode to see if it's another program causing the problem.

Woke up this morning and the phone had rebooted.

RMA your device keep trying until you get someone that understands your issue. Google support is absolute rubbish and if the rep doesn't understand that you're losing all touch input just hang up and try again. It's frustrating but it's sadly the only way you'll be able to get your phone swapped out. I had this problem on my P6P and only a RMA solved my problem.

They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.

Oh wait it's 21 days to return it.
"Remember that if we don’t receive your old item 21 days after your replacement ships, you will be charged $968.67, which is the full value of your replacement item."

Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
I would attribute it to buggy software. My 7 pro locked up about a week into ownership. The last time I had a phone lock up was my last pixel phone (the 3). Not sure what it is but it always clears up after a couple updates. Maybe the same will happen for you.

Tanquen said:
They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.
Click to expand...
Click to collapse
I believe it's part of their call flow offering the repair shop or mail in option. There's always the advanced RMA option where they put a hold on a card you provide and the temp charge is removed once they receive the defective device. If you don't want the chance at getting a refurbished replacement do the advanced RMA sooner rather than later.

The phone froze on me 3 times already - 2 times using Samsung browser, 1 time on Chrome.
Android 13 QPR1 Beta 3.1 introduces a GPU fix, which will hopefully resolve this issue:
Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.

I'm swapping it out for a new(?) one. Hopefully all goes well.