Related
I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.
I was just wandering around in a store, not using my phone at all. It was in my pocket. The vibrate went off, like there was a notification. I took it out of my pocket and the screen was already on. It had a dialog box that said "Android update applied" and an OK button. I hit OK and the phone went to the home screen and nothing seems different. It didn't reboot or anything, and i had not previously received any notice that there was an update to apply. The whole thing felt unusual.
I had gotten the OTA ICS update a few days ago. Like many, i have had awful battery life, screen running hotter than normal, and wifi hanging. When I saw "Android update applied", I got my hopes up that it would address some of these issues, but its still too soon to tell.
Does anyone know what "Android update applied" actually did to my phone or where it came from? Since it didn't behave like a normal OTA update, I'm not really sure what is going on.
Dodongo said:
I was just wandering around in a store, not using my phone at all. It was in my pocket. The vibrate went off, like there was a notification. I took it out of my pocket and the screen was already on. It had a dialog box that said "Android update applied" and an OK button. I hit OK and the phone went to the home screen and nothing seems different. It didn't reboot or anything, and i had not previously received any notice that there was an update to apply. The whole thing felt unusual.
I had gotten the OTA ICS update a few days ago. Like many, i have had awful battery life, screen running hotter than normal, and wifi hanging. When I saw "Android update applied", I got my hopes up that it would address some of these issues, but its still too soon to tell.
Does anyone know what "Android update applied" actually did to my phone or where it came from? Since it didn't behave like a normal OTA update, I'm not really sure what is going on.
Click to expand...
Click to collapse
Either the PRL was updated, or that lawsuit that Google's involved in with Apple about local phone search? The update might've disabled local phone search.
How can i check if the PRL was updated?
I didn't update it (or anything) manually, though.
Hi everyone, I had some strange behavior with my note 7 last night, it locked up for abou 10-15 seconds and then rebooted itself and got stuck in a bootloop, it looped through the first boot screen for around 10-15 cycles and eventually managed to boot up, I kept having random reboots and bootlooping for the next hour or so, I suspected it could be the stock browser as it seemed to be what I had open when most of the reboots occurred so I disabled it with EZ disabler, I haven't had any trouble since last night and I have re enabled the stock browser a day still don't seem to have any problems yet. I googled it and found that apparently a lot of people with the exynos variant are having similar issues, I read somewhere that it was the July date coded models that had the issue but mine is an August coded model, does anyone know anything about this?
Edit, its possible that downloading or updating apps might have something to do with it.
Mine does this and has been doing it since day 3 of my 10 days of having it.
What I'm gathered, any form of lag that corresponds with the vibration motor causes the reboot - so if you touch the back button one too many times or hitting the menu button; heck, sometimes it even just reboots when I'm scrolling in anything and there's some lag (both Chrome and stock browser as well as Whatsapp/Playstore).
I talked to my Telco and they said they'd replace as it's a clear defect but there's no stock unfortunately for an instant swap. I'm about to switch to the international XSA firmware (Currently on OPS Optus firmware) to see if that does anything since the XSA had a recent update relating to performance issues. If it is a defect it won't do anything and the best bet is to go into store and send it off while they order a new one.
Mine's begun to do it more frequently now. Sucks that this is the experience of a first time Note user :'(
My phone was working fine prior to the update. Now since installing it once my phone screen turns off it's basically unresponsive to the power button and fingerprint scanner for about 15-30 seconds before it finally becomes responsive again. Then once I'm in it's fine and the issue starts all over again once it goes to sleep.
Not here. Just flashed the may update. Unlocked, and rooted.
Wout2426 said:
Not here. Just flashed the may update. Unlocked, and rooted.
Click to expand...
Click to collapse
Damn. I'm bone stock and had no issues.. Immediately after the update my screen takes 15 seconds or so to come on after hitting the power button or unlocking with my finger.
Did you flash the update manually or install OTA?
I've experienced similarly weird issues in the past when installing new updates from Google OTA and have since started pushing all of my updates through manually.
NippleSauce said:
Did you flash the update manually or install OTA?
I've experienced similarly weird issues in the past when installing new updates from Google OTA and have since started pushing all of my updates through manually.
Click to expand...
Click to collapse
I installed OTA.
I did just notice the issue does not exist if the phone is plugged into the charger. Very weird.
Flashed May update manually, all good. I'd suggest full image flash (without -w flag) if you're facing issues.
So I factory reset my phone and side loaded the latest update. All has been good for days. All of a sudden this morning the issue is back.
having issues with finger print scanner and phone taking long time to unlock. Pixel line just ain't good!
mongolx said:
having issues with finger print scanner and phone taking long time to unlock. Pixel line just ain't good!
Click to expand...
Click to collapse
I must respectfully disagree. I've had my 3XL since day one, and have not had any issues at all. All OTA updates installed without issue, and this is the best phone I've ever had, and I've had more Android phones that I can list dating back to the Nexus One.
Awesome 4 ya. Reddit and other threads speak 4 them self....
Girlfriends Pixel 2 XL started doing it today after the update as well. Although it stopped after a few hours.
Did anyone receive the google play system update? ive got the main may update but google play system update is still march?. Pixel 3a received them both the same day. Im wondering if this is the cause and it was removed.
I'm having the exact same issue. It started happening in the morning. Unrooted stock. As soon as i lock my device it will turn off. Don't know how to fix that.
Update: chatted with google. And they are sending replacement device
I faced lag on my 2xl couple of weeks ago after the update it seems but i guess it was google doing something in the background perhaps regarding Covid app or something they were trying to do. The random lag stopped in a week or two. So i assume it was google doing something on our phones.
Ok, so like the title says, every 3-4 days I must reboot my phone.
When I play games, the game icon will show up in the lower right corner, I have everything for the game stuff turned off. I can click on the icon and it will ask me to turn on. I back out and it's gone for a few minutes. Mostly until I swipe back, then it will reappear. I can reboot the phone and it will work fine again for a another 3-4 days.
There are other instances that force me to reboot as well, one happened last night. I was scrolling through a local news app and the touch stopped working. I could not scroll up or down, and swiping back did not work. I had to lock the phone and just as the screen went dark, the phone scrolled in the directions I did and it backed out. This only happened when I hit the lock screen.
Is there a fix for this? Has anyone else experienced this?
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Mine does not reboot or shutdown on it own, not once... I have to reboot every so often to keep it functional.
@thepersona My phone doesn't auto reboot either. I'd say do a backup and run https://flash.android.com/welcome to fully Factory Reset the phone and see if that helps (Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Like the OP I do have to reboot my phone about every 3-4 days, but I don't attribute that just to Google Android, coders have become lax on how tight they keep their code, and I say that because in Windows 10 and Windows 11 you have to reboot every few days as well or see an increase in weird issues.
card13 said:
@thepersona Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Click to expand...
Click to collapse
Just to clarify this, most carriers prevented the December update from releasing as Google has asked them to prevent it from going through, primarily due to an issue with calls dropping.
I always manually update my phone, however, I noticed the call dropping bug one day for about an hour straight.
But aside from this meaningless info, I agree with what you said: Attempt a factory reset and see what happens. I turn my phone off every night and charge it, so I don't notice any issues similar to what OP has mentioned.
thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
wilpang said:
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
Click to expand...
Click to collapse
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
thepersona said:
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
Click to expand...
Click to collapse
Yeah I was lucky and it was only once a week which was tolerable!
Something is definitely not right, hopefully is not a dodgy app but that would be preferable than something unfixable.
Ok guys you are missing my point and question. I DO NOT have the random reboots most have, but I have other issues that no one seem to have. Example, I listen to Spotify over night, I fall asleep to music, but 2 days ago it would randomly pause. At first I thought it was do not disturb that I just turned on, on my watch. It was not. Then I thought I may have been hitting my watch, I took it off and it still paused. I rebooted my phone and it's been fine since, no random pauses. Another example is, I play a game but I have the game dashboard turned off, but there times where the icon will pop up in the lower right. When I go into the settings for it, it shows it's off. When I go back to the game the icon is gone for a few minutes then it reappears. The only way for me to get it to stop showing for a few days is to reboot my phone.
I know you shouldn't have to reboot your phone every few days, and by few I mean sometimes it's 3-4 times a week. That tells me something is wrong.
Are you on the November or December update?
If November, I would try the December one.
Rooted or not rooted?
Either way, I would try a factory refresh and don't restore your apps from backup. Manually install only your most critical apps and see if you have the problem. Even better would be not install any additional apps at all and see if the problem happens. If it doesn't happen, install another small group of your most important apps and test again for long enough. Etc.
If you try thre update and/or factory reset, you could try restoring your cloud backup as normal and see if you have any problems still, but if you do, be prepared to factory reset and try like I mentioned in the above paragraph.
Until you can narrow down if the phone has this problem on the December update before you even change settings and add your favorite apps, then you won't know if it's the phone itself (possibly hardware problem), an app you have installed, a problem particular to a combination of factors including if you're on the November update, or what.
Good luck! Please let us know what happens.
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
darbylonia said:
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
Click to expand...
Click to collapse
Awesome!!! This is the kind of news I like to hear..... Just waiting for att to send it through. I checked this morning as my work Verizon Samsung phone got an update.