yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] RGNDI:
Just an Update on my Particular case, Via TWRP i formatted EVERYTHING data system sd etc. then via OTG Cable I Flashed the Latest gapps and cm10.2 build , and now im at 0 Reboots for 11+ Hours!!!

Just to sure ive refrained myself from installing CHROME and using any Location Services, I'll report tomorrow!

Hope this helps anyone
[Nexus 7 (2013) Q&A] cobyman7035:
Is jss15q old ota? I have new system ota pending…

Can I install if I'm on elementalX kernel?

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Q&A] NoNameProvided:
I have a 2nd Gen 32Gb N7 and it shut down ( not reboots ) at least one per day. Most of the shutdowns happen at night, when I sleep, and I not understand why it happen, then I investigate and it seem the tablet go off when my father turn off the wifi at home. Strange, but it does!

I havent seen how it go off since yesterday, when electriity go off so wifi too and my tablet immediately show the "System is shutting down dialog" and go off.

Is this happen with someone too?
[Nexus 7 (2013) Q&A] cobyman7035:
Edit your wifi. Settings

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Q&A] NoNameProvided:
What edit on it? I want to be on wifi .
[Nexus 7 (2013) Q&A] cobyman7035:
In wifi advanced. Settings, mess. Around with settings and test if it shuts down one ur wifi home goes off

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 7 (2013) Q&A] jdkadius:
I'm up to 350+ hours of uptime running CleanROM 1.6 and ElementalX 1.4 with regular Chrome uninstalled. I used to get random reboots maybe one every couple of days.
[Nexus 7 (2013) Q&A] RGNDI:
I'm @ 30+ Hours Uptime Free of Reboots!
[Nexus 7 (2013) Q&A] Hamza141:
A few of my apps are reporting that they've been running for at least 138 hours continuously so I can confirm as a fact that no reboots have been experienced during that period, although I don't remember or haven't noticed any reboots since I updated my device to the latest version, JSS15R, around a week ago.
[Nexus 7 (2013) Q&A] darll:
Ever since I updated to the latest update "R", I havent had a single rebbot. I am currently at almost 400 hours uptime with all my apps intact ( chrome, google plus and so on). I am currently rooted with stock recovery and stock rom, no modificatoons at all..
[Nexus 7 (2013) Q&A] cowisland:
For me it's the opposite. I did not have any reboots after the first OTA. However, I started getting reboots after the JSA15R OTA. Did a factory reset, still getting reboots... Annoying.
[Nexus 7 (2013) Q&A] shivian:
Me Too

Months after people started to announce this problem, I'm still having it happen to me as well (all the OTA updates later)
[Nexus 7 (2013) Q&A] danvee:
Have you contacted Google/ASUS about it?

If they don't know how many are having issues, they can ignore them with greater ease.
[Nexus 7 (2013) Q&A] May82:
I am having a random reboot about once a day. Last time it was up for 23 hours then froze while I was in the play store and rebooted. I am on the latest update. Has anyone had success by reloading a factory image? I don't want to but if there's a chance it will help I will do it.
[Nexus 7 (2013) Q&A] danvee:
People have flashed factory images as well as custom ROMs.

Problem returned in majority of cases, but might take over a week to reoccur.
[Nexus 7 (2013) Q&A] crachel:
Yep.. as danvee said, people have tried most everything. I figure this issue not getting fixed when they fixed the multi touch + GPS problems was probably a good indicator there will be no fix coming.

I've gone ahead and RMA'd mine.. that process has been very painless so far. I was getting some grief from them initially but once I mentioned "random reboots" the representative gave me my RMA # shortly there after
[Nexus 7 (2013) Q&A] jdkadius:
Something strange just happened. I started up tapatalk and clicked around a couple times and then a system message popped up, said that there was only 1.61 MB of internal storage remaining, then it rebooted. Weird thing was that my uptime counter didn't reset. Also weird that it said I was low on internal storage as I have 5+ gigs free.
[Nexus 7 (2013) Q&A] joeshmoo:
For me, definitely hardware issue across a sample of 3 devices. I had one with multiple reboots per day 06-2013 batch from Best Buy launch. JSS15R helped but it didn't eliminate the problem. Tried everything and sent it in for RMA on 9/25. Received back today with a replaced main board. Also (funnily enough) came back from them with an unlocked bootloader. Was definitely locked when I sent it in. Will test it out.

Meanwhile had a second unit from Google Play, 07-2013 manufacture. Random rebooted less frequently, but still was doing it. Got up to 100 hours idle uptime, then RR within 1 hour of use. Play sent out a replacement I've been using now for 5 days. No freezes, no random reboots, same apps and software.

Interestingly enough the RMA for Google Play is the same address in Texas.
[Nexus 7 (2013) Q&A] sfhub:
This bug has migrated over to i5s :) except as usual they try to make it prettier by replacing our black screen with a blue screen.

http://www.youtube.com/watch?v=DNw457joq5I
[Nexus 7 (2013) Q&A] autumnmist:
Check out this page; it was posted to the Google forum thread about Nexus 7 random reboots and it certainly sounds plausible!

Crashes and reboots on the Nexus 7 2013 caused by memory corruption: apps can overwrite memory of other apps

https://sites.google.com/site/nexus7reboot/memory-corruption
[Nexus 7 (2013) Q&A] sfhub:
The memory corruption is present in his test and memory corruption can cause reboots.

However I don't think that user has done enough to determine if the app is the cause or his hardware DDR3 memory is malfunctioning.

If *everyone* that runs the HelloCpp app gets the corrupted memory, then what he assumes is probably happening.

However, if his hardware DDR3 memory is malfunctioning, he would get the same corruption and the HelloCpp app might just be a red-herring.

The reason why I say this is because he did not get a completely reproducable deterministic set of commands that triggers the corruption.

His test plan indicates you need to run HelloCpp *over and over again* until his other app detects corrupted memory. Well, what if the DDR3 memory is malfunctioning, wouldn't the corruption look the same?

He runs the app multiple times and eventually memory corrupts, but if he ran any app multiple times, it might also corrupt. It might be that he just noticed the corruption when he ran that particular app, but it was really the DDR3 memory that corrupted coincidentally when he was running that app.

Alternatively it could also be a race condition that only happens when certain factors hit at the same time. That would explain why you need to run the app over and over again. In that case might be the memory corruption via software that he is assuming.

So yes, he is definitely seeing memory corruption and corruption can result in reboots.

However it hasn't been determined whether that memory corruption is software or hardware (at least from what he has posted so far, it wasn't conclusive to me) Maybe there are other factors that weren't posted or that I missed when I read over his post.
[Nexus 7 (2013) Q&A] autumnmist:
Ah, so he originally posted on Reddit (if you follow the links on his page you can find the thread) and two different users on Reddit replicated his memory corruption findings before he created the Google bug.

I'm going to install the apks he linked to on my Nexus 7 (reboots 1-3x a day when I'm not even home) tonight.
[Nexus 7 (2013) Q&A] MalcolmEvershed:
Hi sfhub, I'm the person who put together the 'memory corruption' page and test. I had many of the same questions when putting together the page, I'll try to address them:

I also was wondering if it was just my DDR3 memory malfunctioning so I also wrote a memory intensive test (which I didn't publish) and it didn't find anything.

I also was wondering if it was just my device or if everyone else also encounters this, so I posted to XDA and to Reddit and two other Reddit users were able to reproduce the problem on their devices.

I looked at what data was written (the corruption) and it didn't look like single-bit errors which I've seen when PCs have memory hardware problems. The data looks more like longer sequences of data from the app.

Yes, it is odd that the steps are not 100% reproducible, but that might just be due to the nature of the bug. For example, my app allocates memory in its own process, but even if those virtual addresses are always the same, at runtime, it may map to different physical addresses. That might be enough to make the issue not 100% reproducible all the time. Basically, without fully understanding what the issue is, we can't explain why it isn't 100% reproducible all the time.

If there is a race condition in the app, it should not be able to affect other processes. Imagine a race condition in the Facebook app -- it shouldn't be able to affect the Gmail app, right?

Still, the big question is: is this a hardware problem or a software problem? I'm really not sure, but my current guess is a software problem.

Anyway, I'd love to hear other people's experiences trying to reproduce the problem.

Thanks.
[Nexus 7 (2013) Q&A] darll:
582 hours uptime for me....Not a single reboot since the "JSS1R" update. All stock and rooted
[Nexus 7 (2013) Q&A] BladeZero:
I thought mine was gone but every now and again I get one, most of the time locking the screen saves me
[Nexus 7 (2013) Q&A] oldtimer42:
Wel,l I made it to 16 days ( how many hours is that?).

It last serially rebooted 3 times when placed in portrait mode on a Qi Tylt Vu Wireless Charger 16 days ago. The Vu does not charge the Nexus 7 2 in portrait mode but interestingly the home screen was pulsing....

The latest occurred while starting a download of a movie from Google Play. It completed the download but rebooted at some time after I started it.

S/W with hardware marginality (ram timing issues or emmc or ?) annoying but I'm past my warranty so will persevere.

I don't know if it helps but I use the clean master app and regularly (every 24 hours) purge memory and sometimes kill apps.

:confused:
[Nexus 7 (2013) Q&A] sfhub:
Doesn't the unit come with 1yr warranty?

Or do you mean return/exchange period?
[Nexus 7 (2013) Q&A] oldtimer42:
Sorry.. I meant the exchange period.

It comes with the 1 yr warranty but for occasional reboots (due to what who knows...) I don't believe the return/rma is worth the trouble. I can wait a while to see if anything changes with 4.4 and then decide.

Proving marginality is challenging as a cause since its most likely how the s/w and h/w are interacting or apps are interacting with the memory. Also, my faith in a "repaired" unit is also not high.

I used to operate a return and repair center for a major manufacturer and understand the challenges in diagnosing issues. A good one would replace boards and then trouble shoot the board separately. I don't know how asus is approaching these repairs.

It sounds from descriptions sent back after RMA that they are replacing components. This is surprising as replacing a surface mount component which is likely bga (ball grid array) is not simple. With the size of the mobo in these units it would be simpler to replace it and repair the mobo off line. However, they may say they are replacing a component when they are doing the board.
[Nexus 7 (2013) Q&A] sfhub:
If you have the preheater and heat profile programmed into your professional rework station it isn't that bad.

If you are going guerilla-style like those folks do reballing the xbox 360 using a griddle and waving a hotair gun looking at a stopwatch, then it is more challenging.
[Nexus 7 (2013) Q&A] tvdang7:
Just rebooted while reading a PowerPoint.
[Nexus 7 (2013) Q&A] crachel:
My RMA status is now listed as "Product was repaired OK and is now packed ready for shipping or pick up."

Hopefully when I receive the device I will get more information as to what exactly this means.

Edit: received device; documentation lists the problem rather cryptically as "Firmware issue".. It has JSS15R on it, which is what I shipped it back with. Now I have to watch and see if it actually is repaired
[Nexus 7 (2013) Q&A] sensboston:
From my experience - I don't have random reboots since:

- I've replaced the device;

- installed ElementalX kernel.

But... Currently I do have (sometimes, but really rare) a "screen freeze" for 3-4 seconds. With original kernel, that "freeze" cause immediately reboot; with ElementalX, it continues work.

It's not too annoying and acceptable to me. IMHO, it's a hardware and software problem (what's why nobody can't figure out what is the real source of the issue).
[Nexus 7 (2013) Q&A] musicluv04:
Have been facing the random reboot issue since beginnning...sometimes it occurs once a day while sometimes it occurs 5 times a day...no particular app is causing it...its almost with every app be it chrome, firefox, music...any idea if kitkat will sort ouut this issue?
[Nexus 7 (2013) Q&A] TheDarkDefender:
If you're not in a position to apply for an RMA, then you have to just sit back and hope kitkat solves it.

Or you could try out custom roms/kernels which may be a temporary solution until kitkat drops in.

Sent from my Nexus 4
[Nexus 7 (2013) Q&A] mrbradeli:
I just realized that I've actually run my phone with 100% stock JSS15R before, so I'm going to try that out for a day or two and hope it solves the reboot issues I've been having.

Just in case it doesn't though, how painless is the RMA process? I got mine through the Play Store and have already unlocked the bootloader. Can I lock it again via fastboot, flash back to complete stock and not worry about Google complaining about a voided warranty?
[Nexus 7 (2013) Q&A] player911:
Reboots typically are caused by the kernel. Using a different kernel should fix it unless is caused by some other outside factor (rogue apps).

I had reboots until I flashed CM using CMs kernel.
[Nexus 7 (2013) Q&A] ramdyc:
Well I'm on my fifth Nexus 7 now from 4 different Best Buys in the SF Bay Area. The first 4 all had random reboot issues with and without custom kernels and /or ROMs. This fifth one is up to 275hrs now and has not had a single random reboot since the day I got it.

Currently I'm running the Perfect Android ROM with Faux's Kernel 006, though I have tried this combo on the older tablets and still got reboots.
[Nexus 7 (2013) Q&A] player911:
Hmmm. Did you flash any OTA updates?

I'm assuming you probably use the same apps. Did you take any logcats?
[Nexus 7 (2013) Q&A] dangitnghia:
I have the 32GB version running latest cm nightly and experience the random reboots.
[Nexus 7 (2013) Q&A] sensboston:
Do you have (currently) rare screen/device "freezes" (up to 2-3 seconds)?
[Nexus 7 (2013) Q&A] roxanna77:
mine will go sometimes a week with no reboots and then like today three random reboots. I know every time mine reboots because it's encrypted and makes an annoying click sound waiting for encryption password. Its great at 2 a.m.

I have to say the Nexus 7 2013 is the most disappointing piece of technology I've ever owned. It cannot be trusted, there's no way I can do real work on it.
[Nexus 7 (2013) Q&A] shams6:
I buy my nexus 7 2 two weeks ago from US Google play store. After opening the camera 1st saw the reboot issue. Then it increases day by day. Then update all apps and OS but no change.

Then I root it, delete all Google Apps but still problem persist. Then go to CM but no solutions. Then revert back to factory image jss15q but no solution. Now during serving Internet, fb apps, or opening of any apps it reboots multiple time. Also reboots during movement of tabs in my hand or take it a flat surface it reboots automatically. I can't use this tab and I can't change this tab as I am now in Bangladesh. Pls pls

Give a solution. Or will I have to wait upto Kitkat update?
[Nexus 7 (2013) Q&A] crachel:
I RMA'd my device a couple weeks ago now and it was returned to me fixed listed as "firmware problem"

Previously I could get a day or two or every once in a while over 100 hours, but never anymore. My device has over 215 hours of uptime currently and I am confident they did in fact fix it.

Since it came back with the same version of Android on it, I can only assume the "firmware" the factory was referring to has to be something other than the OS, perhaps hardware level on the board. Whether this can be fixed in subsequent OTA updates remains to be seen, but if you are having this problem I highly suggest you contact ASUS and get it RMA'd. Use the terminology "random reboot" when talking to them.
[Nexus 7 (2013) Q&A] sfhub:
IMO you either have a an elpida ddr3 memory issue or hynix emmc flash memory issue.

You *might* be able to alleviate a ddr3 memory issue by running any ota successfully, so that is what I would try. I am just guessing maybe 20% chance the behavior will improve. Not great odds, but better than zero. If hynix emmc flash memory issue, best to wipe the tablet multiple times, then install latest jss15r release.

If all else fails, you need to find a way to RMA the unit, it is likely a hardware issue.
[Nexus 7 (2013) Q&A] shams6:
I think I have only one solution now. Wipe it multiple times then install jss15r.

How to send a product RMA in USA., what are requirements to send products in Google play store and what will be the cost? I have neither product packet or recipient copy but a manual paper about warranty. I bought it from Google play store by my cousin.

If I use any kernel will it solve the problems?
[Nexus 7 (2013) Q&A] sfhub:
Why can't you rerun the jss15r ota?

Regarding sending it in from overseas, someone else with more experience in that area will need to help you. Maybe your cousin can help?
[Nexus 7 (2013) Q&A] kernco:
So I see in this thread that some people have gotten rid of their problem by putting a different kernel on their device. If the problem (or at least some people's problem) is a software issue in the kernel, is this something that an OTA can fix, or can the kernel only be updated/changed manually?
[Nexus 7 (2013) Q&A] sfhub:
Depends on what is causing your reboots. I wouldn't assume there is one core problem causing all the reboots. If the reboots you happen to be experiencing are kernel related then yeah a future update can resolve. If there are hardware issues like memory or flash memory, then maybe they can be worked around, but if none of the changes they've put in to address hardware issues so far have made a difference, the chances of a magical fix in kit kat are not high and RMA or return/exchange are the likely routes.

If the reboots you are experiencing are os related but triggered only by certain apps, then by avoiding those apps you may be able to avoid the reboots.

People have some combination ranging from none to all these issues causing their reboots so there is no one right answer for everyone.
[Nexus 7 (2013) Q&A] shams6:
Bro, I get a solution for mine. After giving flash the slim rom till now I have no reboots though 3 reboots occur during flashing Gapps in TWRP recovery mode. I think my Google apps doing this reboots.

Don't know how long this sustain without rebooting.

Update : reboots problem starts again.
[Nexus 7 (2013) Q&A] sensboston:
No way... Those people who think they are got rid of the random reboots by removing Chrome or Google Apps, just simple hide the problem. Some of Google Apps are using a lot of memory (like Chrome browser); this is a real issue/defect.
[Nexus 7 (2013) Q&A] sfhub:
If you are seeing reboots when flashing files in recovery, IMO you have questionable hardware and should consider return, exchange, or RMA. Sometimes with flash memory issues repeatedly writing to bad areas can lock them out, but I wouldn't really feel safe with such memory over time.

---------- Post added at 08:36 AM ---------- Previous post was at 08:30 AM ----------

Right, some of the reboots are caused by ultimately what are os problems, but if one can have an effective experience by avoiding certain apps, they convert it from being a bang your head problem to something you don't see and can wait for Google to eventually fix.
[Nexus 7 (2013) Q&A] shams6:
Yeah I think so. Flash memory issue how to solve? Because reboot problem starts again :(
[Nexus 7 (2013) Q&A] sfhub:
They put in some changes to alleviate flash memory issues in the latest versions so if you are running the latest version and still seeing them, it is probably a hardware issue that can't be worked around.

However difficult it may be from your location you should try and return, exchange, or get an RMA.
[Nexus 7 (2013) Q&A] mrbradeli:
I don't know if I mentioned it yet, but my issues magically went away after reflashing to stock a second time. Anyone know what could've changed?
[Nexus 7 (2013) Q&A] sfhub:
Depends what was causing your reboots to start with.

If OS issue triggered by certain apps, you might not have reinstalled or run those apps.

If kernel issue, you might have flashed a different version from the first time.

If flash memory issue, bad blocks might have eventually been locked out.

If DDR3 memory issue, something you did may have triggered memory retrain.

Then again, it may be you just need to wait a bit longer and the reboots will return.
[Nexus 7 (2013) Q&A] shams6:
But I am feeling better in this rom. Less reboots than stock and cm.

I want slim developers works hard to fix problems that presents in stocks.

Oh, nice presentation. Clears Many things.
[Nexus 7 (2013) Q&A] sensboston:
This should be pinned/listed in FAQ.
[Nexus 7 (2013) Q&A] superfastmonkey:
I just had one while watching Netflix on my 16gb 2013 Nexus 7, it just froze and I had to reboot. Have had a few slight freezes, seeming to be while using Swype...
[Nexus 7 (2013) Q&A] mrbradeli:
I've been getting lots of freezes in Netflix, but no reboots anymore.
[Nexus 7 (2013) Q&A] Osiris19:
I turned GPS off and haven't had one reboot yet and have gone a solid 11 hours uptime. I was getting like two or three in a half hour period like three times a day. The only thing I get now is the occasional 10 second lockup and keyboard freeze

Sent from my Nexus 7
[Nexus 7 (2013) Q&A] crachel:
Ok this ^^^^^ is all nonsense.. After a little over 2 weeks my device finally started rebooting again and is now doing it as much as ever.. So don't fool with RMA if you haven't already!

The people talking about changing kernels seem to be the only one's on the right track. Maybe 4.4 provides a fix, but I doubt it
[Nexus 7 (2013) Q&A] Osiris19:
I installed touch control which changes the kernel, and now I have issues with rebooting again, Even after switching back to franco. I'm gonna restore and try again.

Sent from my Nexus 7
[Nexus 7 (2013) Q&A] JackalJackalJackal:
My tablet will reboot as well, but only when charging in standby mode, when not working.

I have a tablet back or wait for KitKat 4.4 ?

Do you think that will KitKat 4.4 solution to this problem ?

Thank you.
[Nexus 7 (2013) Q&A] danvee:
It still shouldn't do that.

If a factory reset doesn't cure it (eliminating 'aftermarket' apps as an issue) it may well be hardware.
[Nexus 7 (2013) Q&A] JackalJackalJackal:
I did Factory reset and not install any application and had six hours in the charger and no restart, everything was fine. I installed about 35 applications and restart again when charging. All the applications I have purchased, no warez.

On the Nexus 7 2012 was no problem.

OK, I'll wait for KitKat 4.4 and hopefully it works out. I charge-off tablet. Thank you.
[Nexus 7 (2013) Q&A] Osiris19:
This is my forth nexus. (Second 2013) I don't know if I can even exchange it. This one was a warranty device through best buy.

Sent from my Nexus 7
[Nexus 7 (2013) Q&A] danvee:
If you installed them one at a time, waiting 10 minutes or so between each, you'd know which app was the problem.
[Nexus 7 (2013) Q&A] Osiris19:
I just had four reboots in literally five minutes

Sent from my Nexus 7
[Nexus 7 (2013) Q&A] danvee:
Welcome to the club...