On another forum, someone suggested that the frequent reboots may be the result of certain installed applications being incompatible with Jelly Bean. What does everyone here think of that theory? I would hope that the OS would be more robust that that. If true, however, and with so many dozens of installed applications, how could someone realistically identify the culprit(s)?
It's probably just because I have so many applications installed but I notice that after *every* time my GN reboots, at least one application update will have auto-installed. (It's always a different app.) Is that significant? Could the pending installs be somehow causing the frequent reboots? Prior to my GN, I used an HTC Incredible--running Eclair and then Froyo, I think. In any case, with that device/OS, there was some kind of a limited pool for applications; once that threshold was reached, frequent reboots were an acknowledged problem. Could something similar be at work with the GN and/or Jelly Bean?
i do not believe runaway apps will cause a sluggish system on every point. however it isnt impossible, it is actually quite possible, but i believe it is because of the update and that is the reason it isnt working the way he wants.
Sounds like you got a corrupt OTA download, specifically an issue with the kernel loading correctly. What is happening is basically this: The software that controls and governs your processor is gunked up with bad code because it didn't write correctly on the initial install, so it will run inconsistently and can't always manage the workload that it is receiving. When that happens, it basically overloads the processor and causes certain fail-safes built into Android to kick in and tell the phone to reboot before it damages itself. It also affects memory management, and is probably causing other issues that may not be obvious to you as the user. Other signs are extremely poor battery life, force-closing on apps, and random reception issues/degrades.
Go to the store, have them back up your data, and fully wipe/reinstall the OTA image (they have the software tools and the training to do so - or *should*, at least). Should fix the issue.
Downloading files OTA is always a risk...those 1's and 0's can get mixed up once in a while. A factory reset wouldn't work because you don't overwrite your kernel or the ROM that was installed, you just wipe user data. If user data being cleared didn't reset the issue, it's not an app - it's the operating system or a component thereof.
I've never heard of a corrupt OTA causing frequent and random reboots...nor that performing a factory data reset could be a waste of time in trying to resolve the problem. What do you think?
Sometimes downloads don't download every single bit, which could lead to the corruption in the ota. It happens a lot with ROM flashers which is why we check the md5s against the devs to see if it is a complete download. These easiest solution to fix this corruption would be to flash the factory image that Google provides which will wipe the device clean and put a fresh install of everything.
Sometimes downloads don't download every single bit, which could lead to the corruption in the ota. It happens a lot with ROM flashers which is why we check the md5s against the devs to see if it is a complete download. These easiest solution to fix this corruption would be to flash the factory image that Google provides which will wipe the device clean and put a fresh install of everything.
Thanks for the reply. I have a Verizon/LTE device -- so I (don't believe I) can flash the factory image that Google provides, can I? Is this something I need to take to my local VZW store -- and hope they know what they're doing?
Thanks for the reply. I have a Verizon/LTE device -- so I (don't believe I) can flash the factory image that Google provides, can I? Is this something I need to take to my local VZW store -- and hope they know what they're doing?
Yes, you can download the 4.1.1 factory image from google. The easiest way if you don't feel comfortable doing it manually through the command line is through Wug's Nexus Toolkit. If you haven't yet, download and install that. After that, follow it's tutorial to install the ADB/Fastboot drivers. Once both drivers are installed correctly, you can use the option to return to stock/unroot and that will reflash a factory image.
Nope, there is no such restrictions. In fact, the Verizon Gnex is the most unrestricted device Verizon has launched in the last year. All you need is the drivers installed correctly, the correct factory image, which the toolkit will provide, and about 10-15 minutes of time. Toolkit will take care of everything.
Nope, there is no such restrictions. In fact, the Verizon Gnex is the most unrestricted device Verizon has launched in the last year. All you need is the drivers installed correctly, the correct factory image, which the toolkit will provide, and about 10-15 minutes of time. Toolkit will take care of everything.
Thanks, again. After daily (and sometimes multiple times per day) reboots, my phone has been stable since Saturday--so I haven't taken any action yet. I'm using the device as extensively as I ever have, including continuing to receive numerous application updates. Perhaps the threat of a factory data reset or re-flashing/re-setting of the ROM is making the device have second thoughts about rebooting.
Here's another reply on the VZW thread:
I've done some research into the matter, and as best as I could tell, this issue is caused by apps that are not fully compatible with Jelly Bean. For example, the app Volume+ (which I had) did not work with JB and in fact would cause the phone to reboot. Note that this may not be the only cause for the phone rebooting. If anyone knows of any other apps that cause their phone with JB to reboot, please share.
I asked about this at the beginning of the thread. Has anyone here experienced random reboots that were caused by incompatible applications? If so, how did you identify the offending application(s)?
I had an increase in random reboots recently. I brought my phone into the Verizon store. They replaced under extended warranty without a problem. Shipped me a new unit overnight.
I've done some research into the matter, and as best as I could tell, this issue is caused by apps that are not fully compatible with Jelly Bean. For example, the app Volume+ (which I had) did not work with JB and in fact would cause the phone to reboot. Note that this may not be the only cause for the phone rebooting. If anyone knows of any other apps that cause their phone with JB to reboot, please share.
I had an increase in random reboots recently. I brought my phone into the Verizon store. They replaced under extended warranty without a problem. Shipped me a new unit overnight.
Did anyone at the store make any mention about what the problem might have been? Did they ask if you had performed any diagnostic steps first?
Last edited by cgwaters; December 6th, 2012 at 08:19 AM.
I knew it was too good to be true; my GN has started to spontaneously reboot again! So now I'm contemplating using Wug's Nexus Toolkit to re-install the factory image, as recommended earlier in the thread.
I would still appreciate knowing whether the problem could actually be an ill-behaved app. And after every reboot, the device is still immediately downloading and installing one or more updated apps -- which again makes me doubt that the problem has to do with the factory image.
I'm having the rebooting issue too... I'm actually in the middle of a factory reset to see if that fixes the problem.
This isn't the only time it happens, but I notice a lot of the time after I plug in/unplug the phone to the AC charger (one that came with Nexus) it will reboot.
Since I'm factory resetting the phone anyway, I'm going to root it tonight. If the problem isn't solved soon, I'll go in for a replacement... but I'm tempted to try and get an SIII out of them instead of a replacement Nexus.
I had an increase in random reboots recently. I brought my phone into the Verizon store. They replaced under extended warranty without a problem. Shipped me a new unit overnight.
How long had you had your original phone? I purchased mine the day it was released -- which is quickly coming up on one year. Just wondering whether my window to get a replacement is closing.
I am also experiencing random reboots lately and they come in 2 varieties.
One is just a straight forward reboot.
The other is a fake reboot. I see the nexus X on the screen and it looks like its booting up. But after a minute or two it takes me right back to my home page instead of the lock SIM screen.
A few times it happened during app updates so I'm suspicious of the play store app.
Once it happened (fake reboot) while I was using powerAmp but I use poweramp a lot and it happened just once.
Ok, this is getting ridiculous. I'm having at least 6 reboots a day lately. As I mentioned before, it seems to happen when I remove it from a charger, or when I turn the screen on or off suddenly. I did a factory restore and it didn't help. This never happened before the last update.
If it is an app, perhaps we should do some comparison. Here are some I have installed that may be causing the problem:
Go Launcher/Dialer/SMS/Contacts
Tasker
LightFlow
Lookout
Amazon App Store
Ok, this is getting ridiculous. I'm having at least 6 reboots a day lately. As I mentioned before, it seems to happen when I remove it from a charger, or when I turn the screen on or off suddenly. I did a factory restore and it didn't help. This never happened before the last update.
If it is an app, perhaps we should do some comparison. Here are some I have installed that may be causing the problem:
Go Launcher/Dialer/SMS/Contacts
Tasker
LightFlow
Lookout
Amazon App Store
I'm no longer having having daily reboots ... but reboots are still occurring once or twice a week.
Although I have about 150 apps installed, none are among the apps you listed.
I have also had random reboots. I discovered a couple of correlating conditions. YMMV, but:
1. If you have the extended battery installed, some of these batteries appear to have flaky contacts, so the GN may reboot if you knock the phone wrong. Some people (in another thread) have returned their batteries. Mine's not too bad so I just avoid thumping my phone down
2. Low available RAM. I have noticed increased sluggishness/random reboots are more likely when I'm using significantly more than 1/2 of the available RAM (check by Settings-->apps-->running). It seems to help if I am scrupulous about exiting apps I'm not currently using.
I'm having the same problem, at least 1 random reboot a day.
Usually noticed an app having been updated by google play after the reboot has completed. So I disabled automatic app updating. However while not as frequent it still is occuring -> only however if I've happened to use any type of bluetooth before the next reboot. No reboots if I haven't connected to a bluetooth device.
I look forward to hearing if rooting/flashing helps. This problem may have at last convinced me to take the plunge and do it.
I'm having the same problem, at least 1 random reboot a day.
Usually noticed an app having been updated by google play after the reboot has completed. So I disabled automatic app updating. However while not as frequent it still is occuring -> only however if I've happened to use any type of bluetooth before the next reboot. No reboots if I haven't connected to a bluetooth device.
I look forward to hearing if rooting/flashing helps. This problem may have at last convinced me to take the plunge and do it.
Interesting observations! I, too, notice app updates occurring immediately after unexpected reboots. I use bluetooth connectivity numerous times throughout the day, out of necessity; I haven't noticed a relationship to the reboots but will watch for it.
Device(s): Galaxy Nexus! Mom's Rezound, OG Droid (retired)
Carrier: Not Provided
Thanks: 1,504
Thanked 863 Times in 513 Posts
Also get random reboots. Seem to be of several varieties and causes like others have mentioned. I have Geek Squad protection so I'm thinking about swapping it for a new one But I'm also tempted to switch to an GS3 next month when I have an upgrade available.
I am tempted to flash a factory image but I'm not rooted and find it really difficult to do on a Mac. ugh.
I'm contemplating rooting my device and then installing Cyanogenmod. (For those interested in doing that, Install CM for toro - CyanogenMod is very helpful.)
Note the most recent comments on this thread; if the reboots are truly being caused by a 'corrupted app or database', then simply (ha) performing a factory reset would resolve the problem -- at least, until the/an app or database got installed and corrupted again.
I had random reboots since day 1 of having the device, not too frequently, but once or twice a week, sometimes more, I would reboot my device nearly daily and that seemed to keep the random reboots at bay. Usually a random reboot would occur after doing something intensive, like surfing the web or tethering for a long time. Ever since JB, I haven't had any random reboots, and I don't reboot my phone very often anymore.
Personally, flashing the factory image sounds like a good idea (which I did last week after a romming mishap). My phone was somewhat buggy ever since JB update, just not with random reboots. Having a clean phone after resetting/flashing factory is nice.
Thanks for the info. What steps did you take to flash the factory image?
I used mskips galaxy nexus toolkit V10.1, option 16 to select 4.1.1 verizon gnex, then option 9 to flash the factory image. It runs from a command window, but the directions are fairly straightforward. I already had the factory image downloaded to my computer. Also... check the md5sum when you download it, always a good idea. I use this to check md5 sums on windows. I would guess that the toolkit will verify the md5 if you let it download the factory image for you.
Device(s): Rooted GSM Galaxy Nexus with custom Android 4.2.2 AOKP ROM | Retired Optimus V
Carrier: T-Mobile USA
Thanks: 987
Thanked 1,066 Times in 696 Posts
The only way to know if it's a 3rd party app causing the issue is to factory reset and refrain from installing any new apps. Other than updating the apps that come default with the phone, run it like that for awhile and see if you still have the issue. If you do, then more than likely there's a hardware issue.
If not, then it's a safe bet you had a rogue 3rd party app causing problems. From there install maybe 5 apps at a time and install some type of logging tool, or Watchdog Task Manager Lite. That will tell you if an app is eating more system resources than it should.. basically just install and let it run in the background.
Thanks. Since it can be days between reboots, installing only a few apps at a time and then observing the results could take many months to arrive at a conclusion!
What logging tool do you recommend. I have Bootlog Uptime installed. It shows the history of reboots; however, the details that it is supposed to show are inexplicably not available.
Interesting observations! I, too, notice app updates occurring immediately after unexpected reboots. I use bluetooth connectivity numerous times throughout the day, out of necessity; I haven't noticed a relationship to the reboots but will watch for it.
I get these random reboots which are ALWAYS followed by app updates from Play Store. I have tried multiple combinations of different Play Store settings, deleting cache and data from Google Play, uninstalling Google Play updates. Still can't seem to stop this. Also, I'm having trouble finding any discussion of this problem (this is the first one which seems the same). Has anyone found a solution or found a better forum for this?
Also for me this has nothing to do with Bluetooth.
[Samsung Galaxy Nexus, Stock, 4.1.1]
I had the same problem, regardless of what people here say it is all too common. I rooted and flashed 4.2.2 and have had no issues yet (did it a few days ago).
The Galaxy Nexus is the third official phone contracted by Google and the first phone to come with Android 4.0 Ice Cream Sandwich. Specs include a 1.2GHz dual-core processor, 1GB of RAM, 16/32GB of internal storage, a 4.65 inch 720p HD Super AMOLED... Read More