Jump to content

Nexus 7 (2013) Keeps Crashing


Marv1

Recommended Posts

I bought this tablet not long ago, and enjoy it very much! Since the 4.4.2 Kit Kat update, it crashes way too much with browsers I've used. It's very annoying being kicked off online so many times throughout the day or night. Browser's I've used are Google Chrome and Dolphin. I'm currently using Dolphin. Is there a way to stop this, or is it the update that causing the havoc? 

Link to comment
Share on other sites

I bought this tablet not long ago, and enjoy it very much! Since the 4.4.2 Kit Kat update, it crashes way too much with browsers I've used. It's very annoying being kicked off online so many times throughout the day or night. Browser's I've used are Google Chrome and Dolphin. I'm currently using Dolphin. Is there a way to stop this, or is it the update that causing the havoc? 

First obvious question, have  you performed a hard reset? Also, do you have the 16gb or the 32gb?

Link to comment
Share on other sites

Yes I did a hard reset and it still crashes and reboot itself. I have the 16gb. I read all over last night others have the same issues, and some never did with the 16gb. Bad batch maybe?

Link to comment
Share on other sites

My first thought is if there is an app that is not compatible with KitKat that could be causing your grief.  Has Dolphin received an update to make it 4.4 compatible yet?

 

Robert

Link to comment
Share on other sites

My first thought is if there is an app that is not compatible with KitKat that could be causing your grief.  Has Dolphin received an update to make it 4.4 compatible yet? Robert

Yes Dolphin is compatible with Kit Kat. I was having this same issue with Google Chrome also. It may be an app not compatible. How would i know which one it is? I was doing some Google searching about this issue, and seen a handful of things mentioning it may also be a widget that's causing crashing and rebooting issues.

Link to comment
Share on other sites

Crashing and rebooting a has stopped. I resolved this issue by doing another hard set, and selecting not to sync all Google apps from my S3 onto the tablet. As Robert mentioned, there may have been an app not compatible with Kit Kat that was causing the issue. Now I'm really enjoying it!!!

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • T-Mobile and EQT Announce Joint Venture to Acquire Lumos and Build Out the Un-carrier’s First Fiber Footprint https://www.t-mobile.com/news/business/t-mobile-eqt-jv-to-acquire-lumos
    • Unable to confirm if it's really off but I noticed this morning that I'm no longer connecting to Band 41 on my home site. Switching my phone to LTE-only pretty much always put me on Band 41 since it was the least used band on T-Mobile's network. Now I'm only able to connect to Band 2/66. Not complaining because it means speeds are faster on LTE and maybe 150MHz n41 is around the corner.
    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...