Good luck. That appears to be what finally worked for me. I'm on 8 days now. This is a launch day tablet. 4.2 base flash rebooted after adding apps. 4.2.1 to 4.2.2 OTA started rebooting after a few days. I RMA'd for reboots plus my screen has lightbleed and a blemish towards the middle. By that time 4.2.2 image was available so I flashed that and it is still up. The RMA unit shipped with 4.2.1 got the OTA in about 30 minutes and it has been up since. I think that was Tuesday.
As far as your method to check for reboots, you do know most of these reboots are "warm" and don't reset the counter. If you are seeing something else I would guess you aren't seeing what the majority of us are/were.
Sent from my Nexus 10 using Tapatalk HD
OK - using the fastboot "flash-all" has generated better results than the factory-wipe! My tests are still in their infancy, but as I documented - before, using just factory wipe and then letting the tablet sit, even with no use and no signing into Google, it still crashed after 69 hours.
NOW - I have done fastboot "flash-all", then DID sign into Google, but did ZERO use. No web browsing, nothing. All I ever did was wake the screen to check uptime. Oh, and twice I dismissed new Gmail notices via the status bar - never even opened Gmail. As of this AM I am at over 100 hours of uptime!
A little tale here:
It was the thing Nexus 10 owners only dream of, seeing triple digit hour uptime on their device. I'd heard about it in the lore, but never seen it for myself. Much like the Tooth Fairy, I had my doubts such a thing even existed. As I went to sleep last night, seeing a full 96 hours (4 days) of uptime, I wondered... What actually would happen when the uptime counter went over the end of the double digits? Was there in fact a third digit that could be displayed? Would the uptime counter click back to 00? Would the device not know what to do with that third digit, akin to the Y2K problems all had feared? This AM when I woke up, just like on Christmas morning's I excitely rushed to my Nexus 10... Did Santa leave me uptime, or had I been bad and thus deserving of uptime coal? Well the sun parted the clouds and I heard angels singing in the backround, this AM my N10 had OVER 100 hours of uptime! Woo hoo!
Anyways, I've read the discussion where people are talking about "shell reboots" and how that can "keep the uptime". Long story short, I'm not concerned with that. My specific problem has been: N10 gets into the "off" state when I did not put it there, almost exclusisvly this happened while the unit was in sleep, sometimes only for a couple seconds. I am not opposed to "finding bad 3rd party apps and removing them/not using them". BUT - I had to see that this unit could remain powered on with no apps installed first as a baseline. (Otherwise all other testing is really not valid!) When I was stock 4.2.1 to 4.2.2 via OTA, even AFTER factory wipe - that was NOT happening. Now after fastboot flash-all it is. So now I can start other testing.
I am still not 100% convinced other, physical or environmental factors are not at play. You see, during this uptime I've left my N10 in a drawer in my desk. I slide it open and wake there screen to test the stats. It hasnt even had to go from landscape to portrati! It hasnt been "jiggled around in my book bag". SO MANY other things to test. But at least now I have a baseline.
It took me A LOT of research, actually WAY TO MUCH to figure out that there is a difference between factory wipe and flash all. I know that sounds trivial to you vets, but I am POSITIVE that there are others out there who have done factory wipe to try and fix their situation, thinking like I did, that its the same as a "re-flash".
So as of right now I feel that there is a problem w/ the OTA coming off of 4.2.1. Sadly, on Google's latest official paramaters for contributing to this process, they have stated if you fastboot load 4.2.2 you are out of the running for submitting bug reports. I think thats too bad becase I think I've honed in on an aspect they need to look into. I understand why they can not publicy advocate fastboot use, because when you click past the OK to unlock your bootloader you are clicking ok to "may void warranty". If they were to say "well thats ok only if you are troubleshooting 4.2.2" then they open the floodgates to return-abuse. I HOPE they are reading posts like this though and are in fact looking into these things on their end.
Thanks to the commmunity thus far, and I will continue my testing. Next step is to load only Boat Browser, so that I can avoid Chrome use, and use it only at my house. This adds one third party app, tons more use time, and some physical jostling to the mix. Typically you dont add 3 things in one step, but I'd like to actually use this thing!!
bm
