Related
Some of us are having problems with our Captivate randomly shutting down. AT&T technical support thinks it could be apps that we've installed. Could they be right? My replacement device didn't start shutting down again after 3-4 days of owning it. By that time, I have already installed some favorite apps. Here's my list. Let's compare and figure this out. It's just a theory. Can't hurt.
<<<< OMG! While typing this new thread to turn on my phone so I can see the list of apps I have installed, MY PHONE TURNED OFF ON ME! WHAT THE...!!! >>> Anyway...
Apps installed:
-SMS Back Up and Restore
-Yahoo! Mail for Android
-Adobe Reader
-XDA-Developers
-Market History Manager
-Speedtest.net
-Google Maps
Mine never did it until I set advanced tag killer to harsh every half hour. I watered down the harshness a little bit and it hasn't shut off since
Sent from my SAMSUNG-SGH-I897 using XDA App
Theres a thread in the vibrant section that's about the same problem and it happens after 3 days could try there
Sent from my Nexus One using XDA App
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
andy2na said:
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
Click to expand...
Click to collapse
Is there a memtest type application for android? Bad memory would make sense, but so would a number of other theories.
Ur welcome hope it helps and u get it figured out
Sent from my Nexus One using XDA App
RexEscape said:
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
Click to expand...
Click to collapse
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Jack45 said:
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Click to expand...
Click to collapse
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
RexEscape said:
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
Click to expand...
Click to collapse
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Jack45 said:
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Click to expand...
Click to collapse
Agreed. Like I said, this is my second device and the shutdowns didn't start until 3-4 days after ownership on both devices. The reality (for me) is that the Captivate isn't so great after all after two devices already (sorry to say) but I'm not going to give up just yet. I have until the 31st to decide whether I will continue this 30-day early upgrade trial or take it back and continue to use my HTC Fuze and just let my contract expire (in October). If I take it back, come October, I will decide whether I will stay with AT&T and take on another (hopefully bug-free) Captivate, or move to Verizon and check out their Android phones -- HTC and Motorola devices!
I just did a hardware master reset. It isn't exactly a hardware master reset like the tech guy described it. He gave me the directions to "delete user data". It deleted the apps that I have downloaded from the Market, and other things. I don't know what else. However, when it booted up again, I noticed my settings and widgets are still there. My homescreen was still customized the way I had it. So, it's not a total master reset. The software Factory Reset isn't also a total (software) reset. I did that and found some folders left in my internal memory (not my external MicroSD) from the previous working session. Hmm..
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
exactly how it happens on mine.
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
vksf01 said:
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
Click to expand...
Click to collapse
Even after 30 days, you will still be able to return it (maybe to Samsung) for repair or a replacement. Good luck.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
The two Captivates I've owned (and returned due to a combination of GPS and Random Shut Downs) have shut down on me even in the middle of the day (not only in the morning after recharging for the night). It shut down on me while getting my afternoon coffee. I was showing the phone to the Barista, set the phone down on the counter to pay, picked it up, walked back to my office and just when I'm about to wake it up, it does the bootup. It also shut down on me at night while walking in the dark. I noticed my pocket lit up. I pulled out my phone and I saw the Shut Down screen as if you had pressed and held the power button (but nothing else was in my pocket that could have pressed the button!).
Random, I tell ya. Random.
pmpntl said:
exactly how it happens on mine.
Click to expand...
Click to collapse
Larry202br said:
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
Click to expand...
Click to collapse
no, i just turned it back on using the power button.
I just wanted to chime in to say that I am having the same problem. Random shutdowns, not necessarily related to charging. Often they are in the morning however. For me it has been happening a few times a day. Likewise, it seems to have not happened at first, but began a few days ago (I have owned the phone about 2 weeks.)
Are you guys rooted? I have tried unrooting to see if that matters. I don't know why it would, but perhaps...
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!
Ok, so my friend got HTC Rhyme, 2 year contract and all that. The phone worked fine for about a week, when it started having random shut-downs. She sent the phone to an official HTC repair shop, it was there for about a 20 days, and they returned it, stating that they couldn't find any of the issues she reported (random shut-downs, overheating problems, bad responsiveness, and stuff like that). But, they "put the phone under serious work load to test things mentioned". They reflashed the RUU.
2 week later, the phone has the same issues. We take it again, this time with a specific request that they change the complete motherboard, with the CPU, camera server, NAND, etc. She got the phone about a week ago, and it still has the same shut down issues. Should we request a new phone, or is there any other solution. And, does anybody here know, what could be the trigger for this problem.
Thanks.
Seems to me like the CPU is having problems maintaining the clock. That same thing happens on my wildfire when I overclock it to the max. It the phone is rooted try to underclock it. If not, you should definitely take it back and request a new one
Hypercaine said:
Ok, so my friend got HTC Rhyme, 2 year contract and all that. The phone worked fine for about a week, when it started having random shut-downs. She sent the phone to an official HTC repair shop, it was there for about a 20 days, and they returned it, stating that they couldn't find any of the issues she reported (random shut-downs, overheating problems, bad responsiveness, and stuff like that). But, they "put the phone under serious work load to test things mentioned". They reflashed the RUU.
2 week later, the phone has the same issues. We take it again, this time with a specific request that they change the complete motherboard, with the CPU, camera server, NAND, etc. She got the phone about a week ago, and it still has the same shut down issues. Should we request a new phone, or is there any other solution. And, does anybody here know, what could be the trigger for this problem.
Thanks.
Click to expand...
Click to collapse
i have same problems
random shutdown
There are two conditions for the occurrence
first - dockstation
second is - unlockboot and super user
but when i delete su and lock boot.....i have all the same shi......but after a while.....
SO i think problem with power lies in a dock....may be...
ps/english/for/my/sorry)
If you still have the option, I would advise you return the phone. My girlfriend has had the Rhyme about 6 months now and has had nothing but problems. Power cycling hers takes a minimum of 5 minutes (no exaggeration) to come back up At least half a dozen times a day it will show HTC white loading screen or just loading icon when she presses the Home key or back key, etc when she goes back to the main screen. It freezes a lot and gives the same HTC loading screen, etc. Overall, the experience with the Rhyme has been very negative experience and we haven't been able to fix it regardless. :/
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.
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.