My N10 Keeps freezing and resetting

Search This thread

kswiss86

Senior Member
Jan 2, 2012
1,236
721
Germany
Just use another browser. Had my n10 since Saturday and the only reboot I had was trying chrome out for 5 minutes. So I have now rooted and put AOSP on it and no reboots to report.

If you don't want to root use dolphin or boat maybe. Just don't use chrome.

Sent from my Nexus S using xda app-developers app

OK i try. Is Firefox OK?

Sent from my Nexus 10 using xda app-developers app
 

rootusr

Senior Member
Dec 5, 2010
383
39
Just use another browser. Had my n10 since Saturday and the only reboot I had was trying chrome out for 5 minutes. So I have now rooted and put AOSP on it and no reboots to report.

If you don't want to root use dolphin or boat maybe. Just don't use chrome.

Sent from my Nexus S using xda app-developers app

Which installer did you use foe AOSP browser?
 

Warren_Orange

Senior Member
Jun 2, 2011
1,212
176
OK i try. Is Firefox OK?

Sent from my Nexus 10 using xda app-developers app

Don't see why not.

Sent from my Nexus 10 using xda app-developers app

---------- Post added at 09:50 PM ---------- Previous post was at 09:48 PM ----------

Which installer did you use foe AOSP browser?

I used this installer from the market.

https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller&hl=en_GB

Obviously you need root.

Working nicely on 4.3.

Sent from my Nexus 10 using xda app-developers app
 

Warren_Orange

Senior Member
Jun 2, 2011
1,212
176
Oh yeah I forgot. To get bookmark sync working in AOSP you need to go to your Google account settings and enable browser sync.

Sent from my Nexus S using xda app-developers app
 

johno86

Senior Member
Jun 1, 2010
359
164
Tutszania
I used to be plagued by SoD and random reboots when the tablet was in use or idle with 4.2.2.
Since upgrading to android 4.3 all random reboots have stopped for now. 3 days and no reboots.
I suggest you guys to upgrade if you haven't.

I use dolphin browser and no reboots.
Have not tried chrome as I have never been convinced it worked properly with tablets and alike.
Sent from my Nexus 10 using xda app-developers app
 

rootusr

Senior Member
Dec 5, 2010
383
39

ajwho

Senior Member
Jun 13, 2004
113
7
Such a shame there's talk about a new Nexus 10 while this reboot problem still exists. If the new one has no issues, I'd upgrade. But otherwise, I'm happy with my N10. Great product ruined by crappy support.
 

kswiss86

Senior Member
Jan 2, 2012
1,236
721
Germany

maximepull

Member
May 12, 2012
27
3
Ottawa
I received my N10, opened the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.

Tried hard and many times to finally get to enter my gmail account, etc

Updated to 4.3, problem persisted.

So I unlocked it, rooted it and tried flashing older stock versions, same problem.

Tried flashing CM, same; PA, same...

Even CM withouf GAPPS wouldnt work

Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same


Now I re-locked it, unrooted it and I am running stock 4.3: same problem

So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.

Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. I'm past the 15 day return period and the overall experience of sending it back fromhere would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.

Thoughts?
 

SalsaForte

Senior Member
Dec 11, 2010
288
24
Montreal
comobi.ca
Even when my N10 was rebooting or freezing, it was never this bad. You should call the Google support. They have an awesome service. I received my replacement within a week and you don’t need to ship the defective one right away.
 

dibblebill

Senior Member
Jun 3, 2012
1,466
673
35
Raleigh, NC
www.youtube.com
Even when my N10 was rebooting or freezing, it was never this bad. You should call the Google support. They have an awesome service. I received my replacement within a week and you don’t need to ship the defective one right away.

This is news to me. They had me call Samsung. That thread's somewhere in this section, my nearly 3-month journey to get Samsung to repair it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    We tell our customers who are rooted and testing to use Catlog (found here in the Google Play Store):

    https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

    It works well, has filtering, and can periodically write logs to a file so you don't miss something. If you don't know when your device is going to have an "issue" that you want to log, it is probably best to be conservative and have Catlog save more often.

    To make sure you catch every crash, we tell our customers to use Bootlog Uptime (found here in the Google Play Store):

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

    It will alert you with a Notification each and every time the device is restarted without you telling it to. It is an invaluable tool to use alongside Catlog to figure out when and how often a device is rebooting.
    4
    Update from "Paul from Google" on the Google thread:

    Thanks again to everyone for continuing to post your experiences and share information with the community. We're continuing to investigate this issue, and we'd like to collect some additional bug reports from some of you still experiencing this.



    To submit a bug report please follow this checklist:

    •You have a Nexus 10 running Android 4.2.2.
    •You have not modified the software on your tablet by installing a custom ROM or manually flashing/upgrading to Android 4.2.2.
    •There's no need to have your device in safe mode.
    •IMPORTANT: Your bug report must be captured immediately after your device reboots. Any delay, even a few moments, may mean the reboot data could be missed by the bug report. I recommend setting up your device for capturing a bug report well in advance of a reboot -- instructions are in the link below.

    For further info and instructions on submitting a bug report (including the set-up instructions) please see this page:

    http://support.google.com/nexus/bin/request.py?contact_type=bugreport&src=7638530


    Note that this page should only be used to submit reports about Nexus 10 spontaneous reboots running Android 4.2.2. Please also note that we will not be responding to individual reports, but will post updates in this forum thread.
    3
    We cannot explain definitively why some people and devices show the soft-reboot issue and some don't, but we do have some theories:

    • Heavy usage of Location Services and the apps that depend on this causes the issue to happen more readily
    • Poor or no GPS signal strength causes the issue to happen more often
    • Poor or flaky WiFi connectivity causes the issue to happen faster
    • Frequent use of Chrome makes the issue more likely to happen
    • Not having reboot/crash tracking logging means you won't catch every reboot

    The last item on the list is why we load Catlog (for root only on JB devices) and Bootlog Uptime (no root required) on every device we test with immediately after getting it:

    Catlog -- https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
    Bootlog Uptime -- https://play.google.com/store/apps/details?id=se.mumu21.bootlog

    Between these two apps, neither of which we make, we can find out fairly quickly if a device is stable, crashing or behaving in a bad way. Without these apps, however, it is just a guessing game, since no one can watch a device 24/7 or when the screen is off.

    As a matter of personal opinion, and from more than a decade of building, managing and shipping products (hardware and software), I don't believe in luck as an acceptable reason for why one device behaves well while another device responds badly. It almost always comes down to how the device is configured and how the customer is using it that determines stability or not. I am by no means an expert, but when looking into problems I prefer looking at instrumented and logged data versus customer observations as the data tends to be more reliable.

    It is great that you haven't experienced the soft-reboot issue on your Nexus 4, but lets not discount the hundreds of customers who have already reported this behavior on their N4's, as well as the N10's, GalNexus's and other devices since upgrading to 4.2.x. And to feedback on another post 'solution' above: we reflashed our Nexus 10 with CM 10.1 and, surprise-surprise, the soft-reboots are still there, at least with Chrome usage, as we would expect while running the same base kernel, same WiFi and GPS radio code, and same core Google libraries.

    I apologize in advance if this post comes of as curt or condescending, as that is not my intention. Instead, I'm trying to pass along some of my methodologies and experience from working in the semiconductor and software worlds while asking that we all try to gather data that will help Google fix the issue.
    3
    No need to return the tablet for software issues.... Updates will come quick. That's a Nexus!!!

    Sent from my Nexus 10 using XDA Premium HD app
    3
    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.