yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Q&A, Help & Troubleshooting] thg_:
I was in fact trying to ask this in the franco kernel thread, but since newcomers are not allowed to post in dev-areas, I'm placing it here.

Maybe someone can crosspost for me or even knows the answer...

So, I was flashing the franco r5 kernel yesterday on my N10 and since then got occasional reboots and black screens (the tablet won't wake up, after pressing the power button). I have the last_kmesg log as indicated in francos FAQ but don't know what to look for (the log is 1.8MB big and doesn't have proper timestamps - just absolute values in seconds)

Thanks in advance for your help.
[Nexus 10 Q&A, Help & Troubleshooting] Curtox:
So this is starting to sound more and more like a trend, but I too was getting 2 or 3 random reboots per day prior to the 4.2.2 update, and then things were great and stable for about 2.5 days after receiving the update... however on the evening of day 3 I got my first random reboot post-update. And then day 4 had another 3 random reboots, followed another one so far on day 5. In other words, like almost everybody things seemed to be great for the first couple of days after the update, and then it returned to being pretty terrible.

As a devoted Android user for years now, I have to say, this experience has been anything but enjoyable, and Google should be, and probably are rather embarrassed by this fiasco.
[Nexus 10 Q&A, Help & Troubleshooting] vittogn:
Agreed. I'm lucky because I'm still freeze and reboot free after a week of normal usage.

As u said Google must be very embarrassed.

As this topic is not so populated, and now after 4.2.2 even less I start thinking it could be an hw issue, for the folks that are getting freeze and reboot after the update.
[Nexus 10 Q&A, Help & Troubleshooting] pfmiller:
Please don't post off-topic in discussions. There is an off-topic thread where you can post on anything you like, use it.
[Nexus 10 Q&A, Help & Troubleshooting] Hiro11:
I went several days with zero reboots and then Chrome crashed last night. To be fair, it gave me plenty of "warning" that it was about to crash, i probably should have killed the process when things started to get laggy. Still, 4.2.2 seems to be a fairly dramatic improvement over 4.2.1 in terms of both stability and smoothness. No, it's not 100% perfect but I think it's fair to say it's moving in the right direction.
[Nexus 10 Q&A, Help & Troubleshooting] thg_:
Agreed, aside from the fact that my post is about freezing and resetting - just like this thread, isn't it?
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
Over 100 hours uptime on 4.2.2, loads of time in Chrome, and not a single lag or freeze up.

... beamed from my Nexus 10 to your planet
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
While I was able to turn on location services and use Chrome after 4.2.2 without having a very high frequency of freezes and restarts like it was on 4.2.1, I was still experiencing the issue about every 1.5 days regardless of if I avoided Chrome and location services or not.

I went ahead and wiped my Nexus 10 and re-flashed stock 4.2.2. with the SDK. I also rooted it. I elected to not have Google restore my apps and settings and instead just set my settings manually and installed only the bare minimum of apps that I use all the time.

We'll see how it goes.
[Nexus 10 Q&A, Help & Troubleshooting] vittogn:
Just got my first reboot during a play store apps update.

I had a good 1 full week of hope.

As the most of u I can say that I'm not crash free but 4.2.2 decreased the frequency a lot.

I guess we'll have to leave with it till the lemon update!
[Nexus 10 Q&A, Help & Troubleshooting] cadiken:
Not sure if this will help any of you but I'll share my experience.

I never got any reboots on my Nexus 10 but I didn't have Chrome installed so I thought that might be why. One day I installed flash and went through a hand full of browsers to see which supported flash. To my surprise none did so I uninstalled the browsers and settled with AOSP browser and Ocean browser as they were the smoothest.

Soon I experienced my first reboot. I never thought much of it I just thought my luck ran out. I did wonder why AOSP browser didn't work with flash though. I was reading one day and found that the version of flash I had may not work with 4.2.1 so I uninstalled it and installed the one ending in.27. To my surprise AOSP browser started working with flash but so did Ocean. I then started to get mad freezes and reboots.

My Nexus would freeze for a couple seconds then reboot at any time I was using it. I did a couple factory resets and restores and the problem always came back. One day I started over and was selective about what I restored and when I didn't restore nor install flash - no more reboots. I'm now on CM 10.1 with 4.2.2 base and no reboots so far so for me flash was the culprit.

TL;DR - Uninstall flash, clear cache and Dalvik and see if you still have reboots or at least less reboots.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
Thanks for sharing your experience. For me I was and am using only stock system apps and apps available normally through the Play store.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
Yay! It is back to acting normal again. By normal I mean freezing in chrome and eventually rebooting itself. I just got done installing a bunch of apps as well. Made it over 130 hours I think. Bleh.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
Something is definitely wrong with Chrome. I was using it about an hour ago to browse the Google product forums (in the big thread about the Nexus 10 reboots) and scrolling was extremely laggy and the tablet got very hot near the camera.
[Nexus 10 Q&A, Help & Troubleshooting] pfmiller:
Yeah, clearly Chrome has a major problem. My Galaxy Nexus has been quite stable, never reboots. Until last night when I installed Chrome on it and it rebooted like my Nexus 10 within the hour. Regardless Android itself still deserves most of the blame. No matter what an app does the OS should not allow it to bring the system down.
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
True... The fact that it is the OS crashing, and that it happens primarily with Chrome, suggests that 1) Chrome is making some call or reference that most other apps aren't, 2) Chrome isn't handling the exception it's causing or raising, and 3) Android also isn't handling this relatively obscure condition and/or exception properly after it bubbles up, unhandled, from Chrome. I'm also curious about why it seems so much better now with 4.2.2 for many users, but not all....

... beamed from my Nexus 10 to your planet
[Nexus 10 Q&A, Help & Troubleshooting] saltxyz:
Reboot happened very frequently (2-3 times per day) on my Nexus 10. But after flash 4.2.2 factory image, it happens less frequently but still happens.

I recently found one of root cause is write error on bad flash memory block.

"Bootlog Uptime" app helps me capture following log.

[ 9734.318166] dw_mmc dw_mmc.0: Data0: Never released by cmd1

[ 9734.318477] end_request: I/O error, dev mmcblk0, sector 2969160

[ 9734.318612] end_request: I/O error, dev mmcblk0, sector 2969168

[ 9734.318886] Aborting journal on device mmcblk0p9-8.

[ 9734.319066] EXT4-fs error (device mmcblk0p9) in ext4_reserve_inode_write:4356: Journal has aborted

[ 9735.323162] dw_mmc dw_mmc.0: Data0: Never released by cmd18

[ 9736.328199] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)

[ 9736.328353] dw_mmc dw_mmc.0: Hardware locked write error

[ 9736.828128] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80200000)

[ 9736.828220] dw_mmc dw_mmc.0: Hardware locked write error

[ 9737.328126] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80200000)

[ 9737.328217] dw_mmc dw_mmc.0: Hardware locked write error

[ 9737.828127] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80200000)

[ 9737.828217] dw_mmc dw_mmc.0: Hardware locked write error

[ 9739.833255] dw_mmc dw_mmc.0: Timeout waiting for hardware interrupt

[ 9739.833289] cmd13, state: 1, status: 00000306, rintsts: 00010000

[ 9739.834237] mmcblk0: error -123 sending status command, retrying

[ 9739.834672] mmcblk0: error -110 sending status command, retrying

[ 9739.835372] mmcblk0: error -110 sending status command, aborting

[ 9739.835885] mmc_host mmc0: device is being hw reset

[ 9740.072109] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)

[ 9740.098808] Kernel panic - not syncing: EXT4-fs (device mmcblk0p9): panic forced after error
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
If true that is kind of awesome because I've suspected that almost from the beginning. Mine acts fine until I start filling the drive.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
The crazy thing is that it looks like Google thinks the problem is now totally resolved. Check out Paul's response on the last page of the thread in the Google product forums:

---

"Thanks everyone for sharing your experiences so far. As others on this thread have already noted, Android 4.2.2 is currently rolling out to the Nexus 10. If you've received the 4.2.2 update and experience a random reboot, please try running your tablet in safe mode (as explained in this help center article) for a while. If you don't have any reboots while in safe mode that's an indication that something you've installed is triggering it.

If you do see random rebooting even during safe mode, please post back here on this thread to let us know what happened. "

---

Source: http://productforums.google.com/forum/#!msg/mobile/VFYnt7uN9d0/hiBfBdXTdkwJ
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
Disappointing to see that, unless when he talks about "something you've installed" he's assuming that the tablet is rooted and that something that was installed is compromising Android itself. If that's not what he means, this makes it sound (at least to me) as if Android isn't quite as robust as I always thought it (or any OS) should be. I'd love to get to the bottom of this and really understand what's going on that's causing the issue.
[Nexus 10 Q&A, Help & Troubleshooting] vittogn:
Flash??

Do you all guys have flash installed (side loaded)? I read a report that removing it sorted the reboot issue out....

Still an OS problem, it could be helpful for Google to understand the bug...
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
I do not have Flash installed.

What about multiuser? From the moment I got the Nexus 10, I added a second user account. I'm wondering if that new feature is a possible source of issues?
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
No flash, no multiuser. Got ~130 hours uptime installed probably 20-30 apps and it rebooted twice in 20 minutes. As another poster found I'm thinking maybe the disk has bad blocks. As soon as I start adding apps it seems things go bad.

Jonstrong, still no crashes? Approximately how many apps installed?
[Nexus 10 Q&A, Help & Troubleshooting] sus4ntoh:
I have a feeling Google will not think it is an OS issue since it specifically said it doesn't support flash. It is like you put a diesel fuel in your car that takes gas and think it is the manufacturer problem.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
....won't think....?
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
I had no idea I've installed so many apps until you asked and I just looked via Play store. It's showing that I have 189 apps installed! Sort of embarrassing... Have to review the list. Probably a lot that I could happily remove.

No crashes or freezes yet since the 4.2.2 update. I had reached somewhere around 170 hours uptime, and started messing around with themes for TWRP, so my uptime figure isn't meaningful right now since I've restarted manually a couple of times while playing with the themes. But I'm not aware of any crashes or freezes so far.

Still using Chrome now, and actually moved the icon for Chrome beta off my home page since I no longer seem to need it.

I think those log entries we saw showing write errors may indeed be a clue, but I don't know how that would relate to OS updates which do seem to make at least some difference..? I still also wonder if different WiFi setups could make a difference. I haven't had any issues with WiFi yet, but at home I'm still on an ancient (2 year old?) Verizon FIOS ActionTec router that actually doesn't provide 802.11n. I've had the N10 out and about a few times and never had trouble connecting to hotspots, but I don't know for a fact that any of them were using N. No particular reason for me to assume this is a factor, but I've read a number of threads with people reporting varied experience with different WiFi protocols. In an OS like Windows bad drivers could crash the system... Don't know if Android is as vulnerable to this. Just speculating out loud...

... beamed from my Nexus 10 to your planet
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
If you would could you try this and see how your tablet behaves?

4 for 4 this am locking up tablet with this method.

Box installed but not logged in.

Astro file manager installed.

Launch Astro and have it try to connect to box. My tablet freezes 4/4 this am. No reboots though, it just freezes. I have to hold power button to reboot.

I rooted and ran dmesg last night to see if there were any bad blocks. Not sure if that was the way to do it or not but didn't see anything. Tablet got really warm after that I just said screw it and reflashed 4.2.2 stock. So it is locking up on me with the above method completely stock.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
That's disheartening being on stock

Where are you Google!
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
OK...just tried to duplicate that. Seems to have worked fine. I've pasted in two screen shots: one in Astro, accessing Box, and the other in the native Box Android app:

(using Dropbox to host these, ironically... :) )

---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------

Sorry about image size in post above! Didn't expect this... BTW: Box was NOT logged in when I first fired up Astro -- when Astro connected to Box, it requested and used my Box credentials to log in. For the second shot when I opened the Box app, I had to log in all over again, as the Box app didn't "know" my credentials through its own UI yet.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
Thank you. Mine freezes as soon as I touch the box icon in Astro. Maybe time to RMA and see what happens?
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
What are the turn around times do you know? And you just say you returning just because of reboots?
[Nexus 10 Q&A, Help & Troubleshooting] jonstrong:
Maybe... Not sure what to think.

I'm trying to imagine what could be wrong with the tablet itself that causes this. I suppose it could be that there is some kind of memory error in a location within the stored copy of the Box app, and that attempting to open Box triggers a read exception.

Just to test that out, I fired up ES File Explorer (free in Play store) and tried the same thing: I added Net (cloud) access from ESF to Google Drive, Dropbox and Box accounts. Just tried it as I'm typing this, and ESF is able to open Box with no error. Can you try this too? I'm assuming that ESF would have to invoke the same interface to Box that Astro is using. Should be a good test for you if you could try using ES File Explorer to get to your Box account. Might yield some more clues.
[Nexus 10 Q&A, Help & Troubleshooting] derrick603:
From my experience in returning a Nexus 7, they will ship you a replacement tablet with 2-day shipping and give you plenty of time to return the old one, so no downtime except for the time needed to install apps and transfer data.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
Wow a replacement really? Maybe I'll try that before I ebay this thing.
[Nexus 10 Q&A, Help & Troubleshooting] derrick603:
I would definitely give it a try, it was actually one of the most painless return procedures I've ever been through. IIRC, you fill out an online form with your phone number and one of their techs calls you, so no waiting on hold.
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
Reboots and my screen has less light bleed and a smudge.

---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------

Yes, I had already done that. Didn't go through with the login but no freezes
[Nexus 10 Q&A, Help & Troubleshooting] Schubi89:
productforums.google.com/forum/#!msg/mobile/VFYnt7uN9d0/sObM7j5P6WoJ

Google supporter says you should try to disable single apps and look if it works better. If so, just don't use these apps. Or the whole tablet. Don't use it. No reboots for sure! Too bad it even reboots in the middle of the night when it's sleeping. Better turn it off then.

Also: the uptime doesn't get set back to zero if a reboot happens, at least for me. So you can't really say if you experience reboots if they happen in the night, except for the battery graph which shows a gap when a freeze/reboot happened.
[Nexus 10 Q&A, Help & Troubleshooting] akhan47:
Used to have this problem until I did a complete factory wipe about 6 weeks ago. My Nexus 10 has never rebooted since. It's been perfect.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
Thanks for tip it was easy. I have a replacement coming early next week. Hope the new one is a better build
[Nexus 10 Q&A, Help & Troubleshooting] gunslingerfry:
I don't know if this has been said or not, but please please pipe up in the Google product forum above and make sure they understand this is still an ongoing issue. The Android community guy, Paul, says that that's the forum that Google will actually read. I'd be happy to see some Android experts get in there and tear Paul's posts apart for the bs they are.
[Nexus 10 Q&A, Help & Troubleshooting] saltxyz:
To determine bad block, I builded "badblocks" command and then ran it with write test option on TWRP. But no bad block found on system, cache and userdata partitions. :what:

There may be no bad block on flash memory but write error happens. It's strange. Kernel emmc driver bug?
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
So I reflashed 4.2.2 and let it restore apps. Astro didn't restore. I think I uninstalled and reinstalled multiple times to try to fix it. So I downloaded it and it worked like a champ. Crazy device...can't reflash every time I hit an app it doesn't like.
[Nexus 10 Q&A, Help & Troubleshooting] bigmatty:
Glad I finally found this thread! Started in the normal-human-forums but SO happy to advance to the tech-guru-forums!

I am no dev, so no true program knowledge here - but I am an IT guy, so I am good at "troubleshooting". Here is what I did:

-I am on 4.2.2

-Using a 3 day test cycle, my goal was to see the unit on w/ no crash for 72 hours

-Factory wipe & reset

-Full charge, unplug

-Dont even sign in to Google, just let the tablet sit there

-Occasionally turn it on to check uptime

The uptime got to 69 hours before it crashed & rebooted! No Chrome use! No extra apps installed! Nothin! Anyways, I do see now that even if you dont connect a Google Account, both Play and Maps still run in the background and "perform activites". So who knows - maybe if I would have added 'disable all disableable services' I would have been able to get 72. (So close!)

I chimed in on that Google thread too.
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
Mine has been running great since I reflashed. I got over 7 days of uptime before I rebooted to update the SuperSU binary. Bootlog Uptime shows that as a crash but it wasn't. Zero real crashes so far.
[Nexus 10 Q&A, Help & Troubleshooting] SayWhat10:
wow thats crazy. crashing with NOTHING

glad u took time out to do this though

would take me forever if i was trying to find a faulty app one by one
[Nexus 10 Q&A, Help & Troubleshooting] pfmiller:
After having been on 4.2.2 for a while now, it does seem like the crashes are much less frequent, which is great. I've also noticed that they don't seem to happen for a couple of days right after a cold boot. It would not surprise me if a memory leak was responsible which causes problem after 3 or so days of uptime.
[Nexus 10 Q&A, Help & Troubleshooting] bigmatty:
All the threads I've looked at re: Nexus 10 errors are bleeding together in my mind, so forgive me that I cant cite the exact links where I saw this, but I've seen people say even after a Recovery generated factory wipe that actifacts are still left in the file system. Is that true? When I have been "factory resetting" I have not been transferring a .img file... I know that photos and stuff I take get wiped out via the method I've been doing.

Can anyone advise?
[Nexus 10 Q&A, Help & Troubleshooting] scottws:
I did a complete wipe and re flash of the 4.2.2 image using the Android SDK. Not just a factory reset.
[Nexus 10 Q&A, Help & Troubleshooting] bigmatty:
Ok, I will try that. Could you help me out and verify this is the best advised way?:

http://xdaforums.com/showpost.php?p=38091931&postcount=210

I currently am rooted w/ SuperSU and have TWRP installed. I belive 'flash-all' completly overwrites these?

I will try this method (after a recharge here) and then start my "install and do nothing" test again.

~bigmatty
[Nexus 10 Q&A, Help & Troubleshooting] irishrally:
Yep that should work. The flash-all commands are listed below. If you don't want to lose user data then skip the erase userdata step and remove the "-w" from the last command.

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jdq39.zip

I usually just do:

fastboot flash bootloader bootloader.img

fastboot reboot bootloader

fastboot update factoryimage.zip (or "fastboot -w update factoryimage.zip" if you want to erase userdata too)

... but can't hurt to do the other erase commands.
[Nexus 10 Q&A, Help & Troubleshooting] bigmatty:
Thank you irishrally!

---------------------------

update - success! a small change in my troubleshooting plan, this time i did sign in to my google account. the other aspects will remain the same - i am now going to not do anything other than power on the screen to check the Status -> Uptime to monitor for reboots. goal = 72 hours. so.... *ahem* my guess i'll be back in less than 3 days time... :|
[Nexus 10 Q&A, Help & Troubleshooting] rxnelson:
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.
[Nexus 10 Q&A, Help & Troubleshooting] Varekai:
I have at least one crash a day no matter what rom/kernel I'm running. A couple times I've had a crash and it resulted in data loss. Also on Antutu I have extremely low memory read/write scores. In the compare chart of other Nexus 10's most people have about 167 write and 219 read and all I get is 40 write and 150 read. Also I can't install a updated nightly without having to fully wipe or I get stuck in bootloader, whereas others running the same rom dirty flash nightlies without a problem. I'm really starting to think I have corrupt memory.