[Q] Random Reboots? - Nexus 7 Q&A, Help & Troubleshooting

Hello everyone, my Nexus 7 (32gb Wi-Fi Model) has been randomly rebooting itself. I have unlocked the boot loader on it, but I have not installed any custom ROMs yet. I've mainly noticed it rebooting when I'm watching YouTube or using Google Chrome. Any idea on how to fix it? Thanks.

Just a test.

same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?

Best app to help figure this out. Go into the options and check the top 3.LINK

Might be a shot in the dark but I had experienced reboots that was caused by HD Widgets (was acknowledged by them) and possibly Beautiful Widgets. uninstalling them cured my nexus 7 rebooting syndrome.

gokart2 said:
Best app to help figure this out. Go into the options and check the top 3.LINK
Click to expand...
Click to collapse
Currently giving this app a try. Hopefully this will shed some light on the situation. Thanks.

Jomari29 said:
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Click to expand...
Click to collapse
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.

Infobits said:
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Click to expand...
Click to collapse
Awesome! Thanks for the tip! I spent the last week slowly removing apps and re-installing them and I think I've solved the problem.

Related

[Q] Clicking an App takes you back to the main page

Have you ever encountered this phenomenon where, when you click an app it just takes you back to the main page. The app does not load at all.
Why does this happen? What is causing the app not load.
The only way for me to work around this problem, is to restart the OS. Powering down and then powering up again solves my problem. There have been no need for me to pull out the battery or use the Reset feature.
But it puzzles me what is going on in the back ground to cause this problem.
Marketplace is one app that i had problems with at times.
I just need to understand this problem. Cos i do not want to keep rebooting the phone to solve such problems.
I noticed this behavior yesterday -- specifically with the Marketplace App after my son had tried to install the Assasin's Creed demo. Seemed like the Marketplace was in a "hung" state at that point, which only an OS restart would resolve -- either that or waiting for the OS to fix itself, if that's possible.
You're not alone, and it's certainly something that Microsoft will resolve in their 1.1 update.
Honestly, this was such a minor issue for me, that I really did not pay too much attention to it, but it IS there, and I think it is an OS problem, rather than the LG Optimus' fault. How I fixed it was that I launched something else, like Facebook or Twitter ( basically something third-party ), and then pressed the start button. It seemed to resolve the issue for me, not sure what degree of success others will have.
The marketplace is fairly buggy and can cause you in some pretty irritating issues. I know Microsoft is working on it... with new servers and services sometimes getting everything right can take a bit...

Down here in Aus CYANOGEN MOD9 HELP!!??

Hi all, Noob of xda here,
I've been reading the forums as a non registered user and used some of the tutorials to root my samsung android device, I'm now running ICS 4.0.4 on my GT-S5660 and running 1096mhz instead of underclocked 800mhz from the shop. I spoof my devices imei number on a regular basis due to localized phone jackings from authority figures, lets just say I like my privacy and here in aus I have the right to keep it this way. I'm an Unlimited customer for calls, sms/mms and mobile internet data access. No there is no cap on my unlimited, and as far as I'm aware I'm probably 1 of very few customers in this country that have purposely done this, because we all know it.. phone companies are ripping people off all around the world, and some of us just happen to know it all to well.
Hopefully somebody will read this topic, bcuz I need a little help with ICS 4.0.4 bugs :/ My mobile internet data usage limit is programmed to be unchecked and "hidden" therefore do NOT have red and orange data warning and data limit "lines" and cannot access the checkbox to tick it and just raise bar 999###gb, I can hard reset or recover to the base copy I custom edited *to suit my own needs* and it will reset all data counters. I got the base from cyanogen mod 9 and it appears the project was unfinished. I get data warning limit at 2gb...... I have downloaded over 450gb in the last month and have just put up with the warning in notification bar. I have several other bugs that are getting annoying.. but would be simple if i had a larger knowledge of java script and open source code or the time to learn it. I have everything working perfect except camera display auto focus on screen was incorrect or uncompleted. few other bugs with on off switching of bluetooth and wifi though 90% of time works after reboot. I have no bootscreen and on phone start from being off it will not load any picture except my SAMSUNG *which is a mainboard bios image* when it first turns on, screen hangs black bcuz screen timeout settings, I changed my screen timeout to 15seconds and now it hangs on black screen for 15s then goes into sleep mode *turning screen and button lights OFF* as soon as I push menu or power button it loads up and starts working PERFECTLY, when beforehand main settings were set to never turn off screen therefore it constantly hangs with no onscreen image display and eventually freezes entire OS bcuz it seems to think its running perfectly when its not. Lots of reports of other device noobs saying "my phone is bricked" when really you are just a noob.
Can anyone help with the bugs I have or somehow get someone to finish the project using the original projects files or similair??????
Oh and I swear to god if noobs post dumbass unrelated s**t comments on this post...
Camera issue - no idea? sorry
Data limit notifications
My wife had this issue on her phone after I flashed it (CWM, Cyanogenmod7)
Needless to say I got the blame!
I updated to the latest cyanogenmod7 nightly
Hers is a Galaxy S2 which we got here in the UK
After that update it seemed to be working ok
Appreciate that my phone is different, I guess what Im saying is, try another rom or a nightly?
Apologies if this didnt help
Good luck
elPaulio said:
Camera issue - no idea? sorry
Data limit notifications
My wife had this issue on her phone after I flashed it (CWM, Cyanogenmod7)
Needless to say I got the blame!
I updated to the latest cyanogenmod7 nightly
Hers is a Galaxy S2 which we got here in the UK
After that update it seemed to be working ok
Appreciate that my phone is different, I guess what Im saying is, try another rom or a nightly?
Apologies if this didnt help
Good luck
Click to expand...
Click to collapse
As far as I read in the forums the project on samsung galaxy gio gt-s5660 wasnt finished or mastered whatever one of the project workers stole money from account and project ended? my baseband version is S5660VXXKQ4 4.0.4 ics i dont know what other roms there are other then gingerbread n i dont like gingerbread much its what it came with preinstalled n it had heaps of annoying keyboard bugs n app crashes. Maybe there is another rom like ics that is fully operational on my gio????? i want to install rom from zip file on sd card like i did with ICS.

CM10.1 Nightlies - recent hiccups?

I'be been dirty flashing the CM10.1 Nightlies for a couple months now - but not nightly. (I do a dalvik/cache wipe following flashing of the new nightly ROM & gapps, of course - just no "factory reset" in TWRP).
Flashed the 20130518 nightly and developed strange touchscreen errors after a couple hours - dropped screen touches, phantom-touch zooming behavior in Chrome.
Freaked out and immediately flashed back to the prior version I had flashed - 20130504 - and no problems since.
Wondering if anybody else experienced anything similar in the 0504-0518 interval. The kernel gets rebuilt with every nightly. I have to imagine this is a kernel issue, but haven't checked the kernel commit history (yet).
Just wondering if any one has experienced this in recent nightlies.
Did you actually try a clean flash?
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Did you actually try a clean flash?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes and no. The kernel (boot image) is always a clean flash
I've been rolling along with dirty flashing for a while with no artifacts other than gapps FC'ing a fair amount, but that seemed to be true right out of the gate.
FWIW the rollback which resolved the problem was also a dirty flash.
TBH there is all sorts of stuff which could be done to investigate (e.g. binary search for the trouble in the 0504-0518 interval, etc) but I thought I'd ask if anybody else experienced similair issues recently... before I invest a bunch of time in it.
But a clean install is probably due.
So that's a no then. Please try a clean flash.
Sent from my SGH-I747 using Tapatalk 2
I poked around on the CM site.
It is unambiguous that they do not want problem reports about nightly builds.
I guess if someone experiences a problem with a nightly, and then goes to the trouble of trying to track it down, they need to wait until a M build is made, and then see if the problem can be reproduced in that ("stable" release candidate) - and only then open an issue in the CM issue tracking system.
As it took 5 or 6 hours after installation for the problem to show up, I think I'll just stop flashing nightlies and wait for the next stable RC. For the moment I have what I need out of earlier nightlies (Ad-hoc WiFi for tethering purposes).
FWIW, I did do a clean install last night for the 20130504-Nightly. gapps jb-20130301 still seems to FC a lot. Anyone on CM nightlies notice the same?
.
What is actually FC'ing?
peneoark said:
What is actually FC'ing?
Click to expand...
Click to collapse
My bad for using FC terminology - it is not a failure of a foreground task.
I get a toast-like popup dialog that says
"Unfortunately, the process com.google.process.gapps has stopped"
(This dialog has a single "OK" button to dismiss it.)
As fate would have it, I read your question on my phone, and thought - maybe I can find something in a logcat... picked up the tablet, turned the screen on, and it happened. So I generated a logcat.
If you are curious, I can post an excerpt. The preceding 20 seconds or so have several error conditions, starting with an exception in com.google.android.gms, and then a problem with a sync adapter, and finally a sandboxed thread failure in Chrome (the fg task). Nothing that is definitive - to my eye anyway.
bftb0 said:
My bad for using FC terminology - it is not a failure of a foreground task.
I get a toast-like popup dialog that says
"Unfortunately, the process com.google.process.gapps has stopped"
(This dialog has a single "OK" button to dismiss it.)
As fate would have it, I read your question on my phone, and thought - maybe I can find something in a logcat... picked up the tablet, turned the screen on, and it happened. So I generated a logcat.
If you are curious, I can post an excerpt. The preceding 20 seconds or so have several error conditions, starting with an exception in com.google.android.gms, and then a problem with a sync adapter, and finally a sandboxed thread failure in Chrome (the fg task). Nothing that is definitive - to my eye anyway.
Click to expand...
Click to collapse
Have you tried updating G Play Services?
peneoark said:
Have you tried updating G Play Services?
Click to expand...
Click to collapse
It apparently updates itself automatically - without asking me. As a matter of fact, immediately prior to the crash that I captured the logcat for, I noticed (in the logcat) it had just finished updating. When I say "prior", I mean less than 10-20 seconds earlier. (The installation process takes a while.)
Perhaps the pop-up is a red Herring, as the existing service needs to be stopped at some point during the installation of the new .apk. But I don't think that's what is going on here. If that really is the explanation, it means that .gms must be auto-updating rather often.
Dunno. As I said, I can post up an excerpt of the logcat.

Freeze on charge

I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance
Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5

Random Reboot Help

So I have spent a lot of timing trying to figure out the lag on this phone after a bad experience recently with a custom ROM I changed my approach. I went back to the latest stock odexed ROM and I decided not to install xposed as unfortunately I have noticed it has added lag to my system after installing it multiple times.
However now that I have everything setup the way I want the phone is finally buttery smooth without any dirty hacks but now I am getting random reboots. I don't even know how to troubleshoot this problem I thought some apps might be to blame so I tried disabling a few but that didn't help. Worst part it that it is truly random no one situation seems to cause it. It will even happen when I am not even interacting with the phone at all for several hours.
I am rooted. Tried systemless but when I told TWRP not to write to system it would not honor this setting when flashing and always installed in system mode so I had to install a modified boot image. I'm not sure if that could potentially be the cause of my issue but I am really getting annoyed with this. I am just confused about the best way to try and troubleshoot this issue. Any advice is welcome
I too have a similar issue. My phone randomly shuts down(not reboot) whenever using any random app. Sometimes i get a battery indication of 0% and sometime it just shuts down. Very frequently aswell.
Are you getting anything in last_kmsg? When kernels crash they're supposed to write to it, but it doesn't seem to be there after 100% of crashes.
Check it with:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Or by using an app like syslog.
Hmm with the command im getting "no such file or directory" and syslog is telling me i dont have root access or the commands failed.. hmm
tainger said:
Hmm with the command im getting "no such file or directory" and syslog is telling me i dont have root access or the commands failed.. hmm
Click to expand...
Click to collapse
Sorry. It's not always there even after a crash.
Welp now my phone does not power on / charge. I believe my phone has bricked itself or somehow the battery connection is loose. What are the chances that this is hardware related and the connector is Loose or disconnected?
You tried a different charger?
Yep, I've tried a few(0.8 amp, 2amp, computer) None seem to work and the phone doesnt get warm from charging.
I've seen that if you physically disconnect the battery connector and reattach it will fix some software issues. But i dont want to break apart my bamboo back

Categories

Resources