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

    • Tbh not that surprising. Every ISP seems to want to have an MVNO to pitch to their customers to make them stickier and maybe make some money in the process. And unlike USCC the MVNO should be able to cover TDS's entire wireline area, with infrastructure costs that are borne by someone else. Entertaining, yes. Surprising, not really...particularly when competing against Comcast or Spectrum, or even eventually T-Mobile fixed + mobile. This also strengthens my bet that they'll rebrand all their fixed wireless stuff as TDS, as that runs on spectrum they're keeping for now.
    • No? RCS on Google messages works great for me, messages between anyone with RCS enabled go through with no problems. Don't remember the last time I had an issue. I only have issues with people on iPhones on different carriers from T-Mobile.
    • Has anyone experienced a ridiculous amount of difficulty with Google messages with RCS enabled?  It has been a train wreck for me for the past year so I now use WhatsApp.  That works very well for all of us.... Android and iOS.  
    • Probably not worth the fiddling given that that's a few percent of the band. Also, if they really wanted to push my assumption is there are still guard bands in play for the n41 carriers so they could fit two "100 MHz" carriers into 194 MHz anyway. Looks like minimum guard band is less than 1 MHz and a 100 MHz channel is only 273 30 KHz resource blocks, which is a bit over 80 MHz total, so if they really wanted to pull another 5% or so capacity out they could.
    • Saw that for a while. Now back to n25 + n71 + n41-100Mhz + n41-90Mhz.
  • Recently Browsing

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