yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
For the sake of repeating what has already been said (again):

These issues are not related to the Nexus 10 or its hardware

Any device running Android 4.2 shows these issues

Google has acknowledged the issue and assigned it as a to-fix in "FutureRelease"

The reboot can be minimized by disabling all Location Services, stopping Google Currents, not using Chrome, Avoiding weather widget apps

Stick to places where you have good WiFi signal or turn WiFi off when you don't have good signal

For the brave, try running CyanogenMod 10.1 nightlies as they have greatly reduced the soft-reboot issue

Do I wish the N10 was more stable out-of-the-box? Sure. But I also recognize the Nexus devices for what they are intended to be: a developer platform on which to build and test apps on the latest/greatest version of Android. Because of this I don't expect perfection or stability, and I'm not surprised by the crashes... and it is exactly what I've seen with every previous Nexus device. Maybe what Google needs to do is rebrand the early devices as "for developers only" and tell end-customers to either stick with name-brand devices or wait until a solid point-release of Android is available.
[Nexus 10 Q&A, Help & Troubleshooting] DGMayor:
So yeah... I haven't had a reboot to my knowledge/memory in almost 5 or 6 days now... Not sure if one of my regular apps updated and fixed something, but yeah. I even re-installed HD Widgets a few days back and haven't had any issues.
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
Everyone who feels that their device is now "fine" or "stable" should please install and track this with Bootlog Uptime:

https://play.google.com/store/apps/details?id=se.mumu21.bootlog

It is free, it uses very low resources, and it keeps us all honest on how often our devices reboot. That data is very helpful to have when we report these issues to Google, or any other developer for that matter.
[Nexus 10 Q&A, Help & Troubleshooting] nyijedi:
I'm sorry, but this is not true. I have an N10 and an N4. I have experienced countless freeze/reboots on the N10, yet have literally experienced ZERO freeze/reboots on the N4. I got them both on the same day, and use my N4 a lot more than my N10. Maybe the freezing/rebooting also happens on some other 4.2 devices (I've heard it happens on the Galaxy Nexus), but it is inaccurate to say that it happens on "any" device running 4.2.
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
I'm sorry that you feel that way, but we have several Galaxy Nexus's, Nexus 7's, and Nexus 10's and they all behave and crash exactly the same way when Android 4.2 is installed. Rolling the N7 and GalNexus back to 4.1 and the issue goes away. We have also confirmed this behavior with Google. That data and result is definitive, regardless of your N4 experience.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
Are Nexus devices really just developer devices?

Nexus devices were traditionally developer devices, but can one really say that today? I'm sure they are still good at performing that role, but Google has certainly failed to inform any of the tech press that this is the Nexus line's sole or even main purpose. I'm not sure about prior to the Nexus S, but the Nexus phones at least are sold on store mobile carrier's store shelves along with all the others. The Nexus 7 is sold at several retail outlets.

Your suggestion is a good one if that's even what Google has in mind for the Nexus line. As it is, they haven't said that and they either need to come out and say it or they need to release a better product to consumers.
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
For what it's worth, in our conversations directly with Google employees, they do know and understand the issue of expectations versus availability of Nexus devices. Part of the reason that the N10 and N4 are only available directly from Google first is a way of targeting the kind of people who can accept the behavior and quirks of a developer device.

Where things get complicated is when carriers and retailers start selling devices. We saw this with the Galaxy Nexus and Verizon, where Verizon has actively restricted the pace and amount of updates we can get. If you ask a Google employee where to get a development device they will almost always say "the Play Store", but if you ask them for a device to give your family they will point you to Samsung, HTC, Sony, Motorola, etc.
[Nexus 10 Q&A, Help & Troubleshooting] nyijedi:
I can't help but notice that you didn't cite any reports of N4s crashing exactly the same way.

Actually, I forgot about the N7 - I have an N7 too and don't experience any crashes. I also regularly frequent both the N7 and N4 forums (the N4 forums a bit more), and haven't seen any reports of this type of crashing for these devices. Do you happen to have any links discussing the crashing on these devices handy? If not, don't go crazy looking - I just thought I'd ask.
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
I cherry-picked these results. There are many, many more.

For Nexus 7:

http://code.google.com/p/android/is...ot&colspec=ID Type Status Owner Summary Stars

http://code.google.com/p/android/is...ot&colspec=ID Type Status Owner Summary Stars

http://code.google.com/p/android/is...ot&colspec=ID Type Status Owner Summary Stars

For Nexus 10:

http://code.google.com/p/android/is...ot&colspec=ID Type Status Owner Summary Stars

For Nexus 4:

http://code.google.com/p/android/is...ot&colspec=ID Type Status Owner Summary Stars

For Galaxy Nexus (and all Nexus's):

http://code.google.com/p/android/is...c=ID Type Status Owner Summary Stars&id=39912
[Nexus 10 Q&A, Help & Troubleshooting] nyijedi:
Thank you. I'll go through these in a little bit. I can't explain the difference in my personal experiences with all 3 Nexus devices, but I stand -- at least somewhat -- corrected.
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
As I've mentioned to other folks before, we thought our Nexus 7 was "fine" and "stable" until we looked at the Bootlog Uptime log and saw that it had been rebooting... just not when we were looking at it.

Not using Chrome, turning off GPS, disabling all Location Services, turning off WiFi when not in use and disabling all weather location apps (except our own, of course :) ) have made the N7 with 4.2 a very pleasant experience. It still doesn't completely eliminate these soft-reboots (this is what Google is calling it) but at least they happen far less frequently. The N10, on the other hand, has this issue at least twice a day with the same settings.

I can't explain why some N4 customers don't see it and some do, but I can state that Google has acknowledged an issue on all devices running 4.2, and the fix is scheduled for the next version of Android.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
For what it is worth, there are people that say they have no problems with their Nexus 10 running the stock 4.2.1 ROM either.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
My N4 is stable in hand, however looking at reboot logger (didn't have boot log installed) it showed two reboots without shutdowns which I infer to mean they were random reboots. They were also at sketchy times I wouldn't normally be rebooting the phone. That being said two since 11/21 I can handle. N10 every 4 hours of use.... Grrrr.
[Nexus 10 Q&A, Help & Troubleshooting] ShadowVlican:
i have no problems with my nexus 10... uptime for as long as i allow it

running paranoidandroid with KTmanta kernel (overclocked and undervolted)

no facebook

no chrome

yes google currents

location services (under map settings) all off

GPS/wifi/bluetooth enabled all the time
[Nexus 10 Q&A, Help & Troubleshooting] vittogn:
Tx mstroud.

It is good that Google is working on it as well as the source of issue is sw.

Do u have any idea on where they are in term of understanding and resolving this issue.

Tx.
[Nexus 10 Q&A, Help & Troubleshooting] aflamovie:
I've had this a few times too
[Nexus 10 Q&A, Help & Troubleshooting] mstroud:
I don't have any more status than what Google themselves posted in the bug reports: it has been marked as fixed in "FutureRelease".
[Nexus 10 Q&A, Help & Troubleshooting] xdp:
I love the Nexus 10 hardware but I am absolutely sick of Android 4.2 and Chrome, they both just absolutely suck. Web pages randomly freeze while scrolling, switching tabs locks up or crashes Chrome, have to wait a while before it comes back, and often it crashes the whole tablet and makes it reboot. Sometimes it takes several minutes before rebooting. One time I just gave up and walked away and when I came back it had lost like 50% of its battery while being "off". Chrome also has severe memory leaks. Recently I noticed on my Galaxy Nexus that after browsing semi-heavy web pages all my icons would reload when hitting home, indicating that Chrome ate up all the memory and kicked out the launcher. Well, that even happens on the Nexus 10 with 2 GB! What a disgrace. This is why Apple is kicking Google's ass in all market segments outside of the geek crowd and low end, because they don't deliver this sort of experience to the end user.

I know this tablet can be amazing with some updates and I intend to hang on to it, but holy **** does Google need to get Android 4.3 and Chrome updates out fast. I think they rushed the release to make the 2012 holiday season (for what reason I don't know, they never even advertised it), and I'm disappointed in the quality they've pushed out.
[Nexus 10 Q&A, Help & Troubleshooting] nyijedi:
Yup, I agree on this. It's a shame. I just wish they'd hurry up with an update.
[Nexus 10 Q&A, Help & Troubleshooting] Westfire:
Yeah I am getting really tired of the random reboots. I was listening to Google Music for about an hour and then all the sudden in the middle of a song it rebooted. No rhyme or reason. I hope they release an update soon. Mine reboots randomly 2-3 times a day.
[Nexus 10 Q&A, Help & Troubleshooting] btucker2003:
Sucks...I guess I'm not the only one. I came looking for a fix. :(
[Nexus 10 Q&A, Help & Troubleshooting] KestrelX:
I'm running cm 10.1 and ktmanta kernel. Google ads, location services, chrome disabled. No reboots. Give it a shot!
[Nexus 10 Q&A, Help & Troubleshooting] metaled222:
http://xdaforums.com/showthread.php?t=2009595&page=6

I found a cause for my n10 to keep freezing/rebooting. Maybe someone can find the fix with it? I posted it in the msg linked above in another topic. Any questions, please let me know.

Ed
[Nexus 10 Q&A, Help & Troubleshooting] samaraki:
Terrible advice... Not quick and how do you know its software?

They never fixed the crashing or WiFi. I just bought my tabby this week... I dunno why everyone thinks its firmware, I have 2 friends with the N10 without any of these problems.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
Im on cm10.1,but you have link to this ktmanta kernel?
[Nexus 10 Q&A, Help & Troubleshooting] Serial Abuser:
Fixed!

My N10 has had the random hangs and reboots from the beginning but lately it got to the point where I couldn't browse for more than about 15 minutes without a reboot. I finally got fed up with it and thought I would try a factory reset like some people had recommended. I installed TWRP and SuperSU while I was at it since I knew I'd want root at some point just so I can use Titanium Backup. I did a factory wipe but did not change the kernel or ROM. I also turned off location services (again) and disabled Chrome.

It's been three days of heavy use with Chrome Beta and I haven't had a single hang or reboot. In a few days I'll turn location services on and see if it stays stable. I suspect magic was the wipe, but can't prove it at this point.

---------- Post added at 11:02 AM ---------- Previous post was at 10:48 AM ----------

Firmware engineer here...

Hardware has bugs. Hardware manufacturing has bugs. These bugs are difficult to find during development because low-volume manufacturing is very expensive, so a development team may only have a few tens of prototypes to with with and a QA team may only have a few hundred. When this scales up to millions of units, there are going to be new bugs found as the manufacturing processes scale up. These bugs get fixed in firmware because it can be done later in the development cycle (though it goes on through the entire development as well). So people might mistakenly identify these problems as firmware bugs or not, but either way, the problem gets fixed in firmware.
[Nexus 10 Q&A, Help & Troubleshooting] Infobits:
suggested OS fix for the random reboots issue

Since I also have seen this random reboot issue on my nexus 7 tablet, as a software developer myself (though not an Android dev) I've been looking into this bug myself analyzing reports and debug trace logs. Every error dump log I've seen so far when the reboot occurred shows that it was due to an invalid argument variable or null pointer exception within the activityManager processing in the java routine called Parcel().

My own nexus log showed me that an app (winamp pro in this particular case) was the culprit. Apparently the app comes alive all by itself to do whatever mysterious tasks under the covers without you starting it explicitly. It passes an invalid value argument to the activityManager Parcel() method which triggers an error condition that is not caught by the Parcel() method. Since the error is not caught and handled locally in this routine, the error is passed up to the default OS error handler routine which is to stop and reboot the system. I suspect that there are many apps that were compiled for earlier OS SDK versions and are what is triggering this uncaught error causing the random reboots. It is not just the winamp app I mentioned above in my case but can be any old app from before Jelly Bean version v4.2 or v4.2.1.

My suggestion to Google development team then is to add java try{} catch {} blocks wrapping around those sections of code where the errors are happening. Let me know if this helps you solve the mystery reboots bug. If you need help, I am for hire at this point in time space. Not joking either.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
only thing about this is, i also have the galaxy nexus(sprint),running 4.2.1

your definition sounds like its independant of phone that android is running on, since you pinpoint older apps being the problem

i pretty much run the same apps on my phone and tablet

only had the phone for 2 weeks but havent had a reboot,or even a freeze that i can remember

on nexus 10 i get 5 or so reboots a day

so not sure why the galaxy nexus is catching the error, but not the nexus 10,making it crash/reboot

and i guess there is no 4.1 JB rom to test to see if indeed 4.2.1 is definitively the culprit?
[Nexus 10 Q&A, Help & Troubleshooting] Infobits:
I can't speculate on why your Galaxy Nexus phone does not or has not yet crashed and rebooted but your Nexus 10 does assuming you really do have the exact same apps and environment loaded under v4.2.1. However there could be lots of reasons why.

- It's possible that you do have something different loaded on your Nexus 10 causing the reboots that you are not aware of is not on your phone.

- It's possible that the offending app or apps (whatever it or they might be) are not executing the same routines on each of the devices. That's because the Android apps are (or might be) designed to run different routines (code sections) depending on the hardware it detects (like cpu, gpu, screen size, etc.) thus one branch of the code may cause the error trigger and the other branch of code maybe does not cause the error.

The best way for you to find out which apps are causing the reboots is to enable the 'Developer's Mode' and turn on debug tracing to generate log files each time it crashes and reboots. When you examine the logs, you should be able to get a clue as to which app was being processed when the FATAL error occurs. The logs are very busy and complex looking but you can simply search for certain keywords like 'FATAL EXCEPTION IN SYSTEM PROCESS' or 'java.lang.IllegalArgumentException' or 'am_crash'.

When you find those lines in the log, look at the lines preceding them for the name of an app. It's the app that caused the exception.

When you get the name of the app, uninstall it from your Nexus device and see if the reboots stop.

If you still get yet another reboot after removing the first bad app, then look at your debug log again from the next crash and see what other app caused the crash. Then again remove that app and run again to see if you get reboots still. and so on until you've eliminated all the incompatible apps. That's all I can recommend for now until Google dev team delivers their ultimate OS fix.
[Nexus 10 Q&A, Help & Troubleshooting] punzada:
Thanks for this wonderful information as I'm currently one of the people getting random reboots a good few times daily and would love to narrow down the culprit. However, in the developer options I don't see a specific option to turn on debug tracing do you know what I need to enable? (And also where the log files are stored so I can review them?) I have the option to select a debug app but don't have one installed, and I see options to enable tracing on lots of things like graphics, input, audio, etc but nothing either application, shutdown/reboot or debug specific. Thanks for any help in advance hopefully if enough of us review these logs we can collectively narrow down some problem apps to avoid.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
This page should tell you everything you need: http://support.google.com/nexus/bin/request.py?contact_type=bugreport.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
yeah would like to know the same 2 things

how so? its just a page to send in a bug report

it says to attach a report but as mentioned we 2 at least dont know how to do that
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
It tells you exactly how to take a bug report. Click on the device name for the per-device instructions.
[Nexus 10 Q&A, Help & Troubleshooting] Infobits:
Rather than retype all the steps here, here is a link to another forum where someone has already posted how to enable the developer mode on the new Android v4.2.x OS. It is post #26 here:

http://code.google.com/p/android/issues/detail?id=40140

my handle on that forum is exists2Wonder where I have also been posting my findings and thoughts on this issue. Over there I posted an example of my debug log lines that show how I found out that the winamp pro app that was installed on my Nexus 7 caused a random reboot. You can use those log lines I showed as an example for what to search for, for similar keywords in your logs. I think one of the main keywords you can search for that is shown is 'boot_progress_start' which to me seems to indicate the point at which the system restarte was initiated. Good Luck and post all your findings to help troubleshoot this issue.
[Nexus 10 Q&A, Help & Troubleshooting] Hiro11:
Still no news from Google on a fix for this, huh?

If I use Chrome, mine crashes about one time for every 3-4 hours of use. It spontaneously restarted last night while I dumped out of HBOGO: no lock-up, just suddenl went to the "Nexus X" symbol and restarted. It's the first time that has ever happened. The vast majority of the other crashes have been Chrome related. Regardless, a very, very annoying bug that should have been caught given that it's a first-party app on first-party hardware.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
Some guy from Google responded in the official Google product forum and sort of informally acknowledged the issue, but that is all I've seen directly from Google on this issue. Also no real whispers of when the next version of android might drop. There were some reports of Nexus 4 devices showing up with 4.2.2 in Brazil am couple weeks ago, but I don't know if they were ever substantiated. It is pretty easy to modify build.prop to show any version you want.

Here is the link to the Google product group I am referring to: http://productforums.google.com/d/topic/mobile/VFYnt7uN9d0/discussion.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
I reverted back to 4.2 and minimal apps. I had only stock apps and boot logger and still had lockups. I got the logs and I'll see what apps are prior to the errors.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
So if I am reading my logs right it looks like talk is the culprit? That can't be right, can it?

That is the nearest thing I see to "java.lang.IllegalArgumentException". Again this is on 4.2 with no updates applied and only bootlogger installed.
[Nexus 10 Q&A, Help & Troubleshooting] ndirish2001:
I give up

I just got off the phone with Google to return my Nexus 10, as I'm fortunately still within the 15-day return window. I couldn't be more bummed out about having to return the tablet. I'm a big Google and Android fan, so I was thrilled when the Nexus 10 was announced. However, the experience has been beyond disappointing. My tablet simply doesn't work. The constant crashes are unacceptable. My previous tablet was a Galaxy Tab 8.9 and I almost never had a crash, either on the official or on custom ROMs. Given that this is a problem shared by so many Nexus 10 users, I just can't believe that Google hasn't even acknowledged it. It's their obliviousness that has forced my hand to return the tablet. If they would come out and admit that it's a problem and promise a fix in the near future, I would gladly keep my tablet.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
I'm surprised this issue hasn't gotten any press, especially with how Apple-centric the press is. I sent an email to Ars Technica a couple weeks ago, but it doesn't look like they are going to take up the topic. I was hoping some press coverage from a major tech site would force Google to say something. Alas, it doesn't look like that is going to happen.
[Nexus 10 Q&A, Help & Troubleshooting] Infobits:
well there can be many of those "java. lang. IllegalArgumentException" statements, but the one you should look for is one that has statements following after it that say "boot_progress_start". That's how I spotted my bad app.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
I have two of the illegal arguments and one boot_progress_start. I don't see anything near it. Like I said though, this is a base 4.2 flash with only bootlogger installed so it would point to the google apps themselves if your theory is correct?
[Nexus 10 Q&A, Help & Troubleshooting] mascondante:
I'm using CM 10.1 And mine is about as stable as a lunatic. I do realize that issues are to be expected with nightly build software but this thing is all over the place.
[Nexus 10 Q&A, Help & Troubleshooting] Infobits:
I don't know what to tell you about base v4.2 compared to v4.2.1 differences but here is a cut and paste of example from my log output that I got when I had the random reboot. This is where I show you how I identified it as the winamp app because it says so in the error log where it restart to reboot...

I am showing you my log sample in case it helps you see the format and sequence of the log messages for a particular app:

01-26 20:29:55.375 23835 23848 I am_kill : [0,20018,com.nullsoft.winamp,15,too many background]

01-26 20:29:55.385 23835 24141 I am_proc_died: [0,20018,com.nullsoft.winamp]

01-26 20:29:57.085 23835 23851 I am_crash: [23835,0,system_server,-1,java.lang.IllegalArgumentException,NULL,Parcel.java,-2]

01-26 20:29:58.375 20591 20591 I boot_progress_start: 257787661

01-26 20:29:58.565 20591 20591 I boot_progress_preload_start: 257787853

01-26 20:30:02.035 20591 20591 I boot_progress_preload_end: 257791323

01-26 20:30:02.205 20815 20828 I boot_progress_system_run: 257791492

01-26 20:30:02.385 20815 20828 I boot_progress_pms_start: 257791678

01-26 20:30:02.865 20815 20828 I boot_progress_pms_system_scan_start: 257792151

01-26 20:30:06.085 20815 20828 I boot_progress_pms_data_scan_start: 257795370

01-26 20:30:19.295 20815 20828 I boot_progress_pms_scan_end: 257808585

01-26 20:30:19.525 20815 20828 I boot_progress_pms_ready: 257808810

01-26 20:30:19.665 20815 20828 I battery_status: [3,2,1,0,Li-ion]

01-26 20:30:19.665 20815 20828 I battery_level: [61,3806,220]