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...
My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en
Are you using a custom recovery/ROM? That icon you posted isn't the stock image
Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?
just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet
Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!
Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.
I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...
I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?
I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.
Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.
Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !
No, but this problem is not ROM related.
discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.
I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.
welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.
Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.
Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks
I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
The de-casing was fun, and yet there isn't an obviously damaged component. It was pronounced dead at 6:20 yesterday evening.
R.I.p.
Sent from my SGH-T699 using XDA Premium 4 mobile app
tylik said:
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
Click to expand...
Click to collapse
Get a new battery for it....had this issue before and placing new battery in it fixed my bootlooping and not being able to flash or get past samsung screen...the samsung batteries have an overcharge feature which has been known for causing errors such as this...
Hi all,
Long story, but the quick version is my home button rarely does anything any more and the screen wakes up by itself from being asleep after anywhere from 3 seconds to 12 seconds.
Now for the long version:
Non-rooted Galaxy S6, by the way. I did a factory reset last week, just because things were getting sluggish. It went well, things were back to speed, and I reinstalled the essentials I wanted. Last night I noticed my phone kept waking itself up over and over again. Then I noticed the home button wasn't doing anything. I rebooted it and it didn't change a thing. After a little more time, the power button also stopped responding. I couldn't even do an emergency reboot with those two buttons disabled. I even tried sticking it in the freezer for a few minutes to see if it was too hot. Google told me about the on screen menu thing to emulate the softkeys so I was able to use that to get around and do reboots.
I hadn't installed any new apps in the last 24 hours, but what the heck, I did another factory reset. I had the option to restore all the apps and settings from 1 day ago, so I chose that. The problem still was there. Dang it, I thought I should not have restored those apps, so I did another reset, this time a totally clean one. The problem not only still happened after the reset, it was doing it during the reset, if the screen went to sleep during a step in the factory reset, the glitch would wake it back up in a few seconds.
I decided last night to just turn it off and charge it fully and hit the Sprint store in the morning. Oddly while charging with the phone powered off, the green battery display would go off and on the whole time it charged.
In the morning I turned the phone on....and NO problems. (of course) For 2 hours not one glitch. So just before leaving for work it starts happening again. Another factory reset at work and a system update from Samsung and still, the problems are there.
I'm just thinking I'll hit the Sprint store tomorrow and swap it out for a new one...but I thought I would tap you guys for any info if you had any.
Thanks in advance, Larry
Sounds like your phone got wet. Factory reset over and over again will not fix this problem ha
Hi,
It seems like a problem with the hardware itself. So yeah, factory resetting all times won't help. Go get a new one .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Try to use this method
http://forum.xda-developers.com/showthread.php?p=62872996
_______________________________________
thereassaad
XDA Assist
Thanks for the ideas, I tried the dialer thing, thereassaad, but it didn't help. It does sound like water damage, but there is no way. I've never dropped it or been near any water. I'm heading to the Sprint store tomorrow, too busy today. I'll let you folks know how it went tomorrow night.
Just FYI, they replaced the screen saying that fixed the home button not responding and the screen waking itself up, but said I probably shouldn't restore with my google account, since it's likely corrupting my system... Huh? I said. They said the hardware was fixed, but I should create a new google account. I said no way. I said what does having just my contacts imported (no apps) have to do with hardware failure. I said, open up a new phone and lets put my google account on it and see if it breaks the new phone, they said no.
In the store we added my google account to my "fixed" phone with the new screen and all and it messed up again. They said, never mind, we'll replace it, and it should be there this Tuesday.
I didn't ask if it would be a refurb, but I really don't care as long as it works.
So that's my story. So far.
They swapped it out for a new phone, refurb likely, but I'm not sure how to find that out. (not that I care too much) I'm loving the new phone, it's like unboxing day again. No cost out of pocket for me too, which is nice.
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.