How Google killed my Nexus 7 (and then brought it back to life)

Update: January 19, 2015 – Scroll to bottom to see the latest drama.
Update: March 25, 2015 – Two months later, I did an official time test – see the results here.

It was a chilly October night in 2012. Friends had gathered to my surprise to celebrate my birthday – with great Chinese food, a bonfire, and finally getting the gang together, it was a great time… And at the end of it all, my parents put the icing on the (not literal) cake – they gave me the shiny new tablet of my dreams, a 16GB Google Nexus 7.

I’d never had a tablet before, so I wasn’t entirely sure what I’d use it for, or if it would really be used at all. I had gotten frustrated reading my morning news on my phone, so I figured for the sole use of reading it could be justified, but found it was so much more. Reading, video, browsing, gaming, everything I wanted to do my little Nexus 7 could plow through it – once, when my laptop was down, I actually spent a couple of days doing productive web design on it (though I don’t recommend it for your sanity). Even though it had newer models released with even sharper screens and more internets packed in, not once did I feel like I needed to replace it… Until the last month, after an update to Google’s KitKat OS, 4.4.4 (I think).

From then on, it crawled. To load a web page, I’d have a good fifteen second delay, if it didn’t time out at all. The battery life was pathetic – no matter what apps I removed or how little I used it, it would go from full charge to empty in twelve hours. Google had killed my little tablet, no doubt as part of their grand scheme to make me buy a new one. I was disgruntled, and while (trying to) browse for other tablets as a replacement, a notification popped up.

“A system update?” I didn’t say out loud, because I was alone. “Yeah right, that’ll go REAL well.” Figuring I had nothing to lose, I agreed to install Google’s new OS – 5.0.2, named Lollipop. It took FOREVER – hanging on install, non-responsive, and generally being shady – the update failed.

I was determined. “You won’t get my money today, Google!” inner me exclaimed, being overly dramatic about an oversized smartphone. I went for the nuclear option, and after the smoke cleared… My tablet blazes. It’s as fast as it was the day I got it, with amazing battery life and almost no delay. Google hadn’t been out to get me, they’d been like a tech guardian angel – always looking out for their little Nexus users.

I know that my experience was not an isolated incident – page after page of search results showed people with the same issues I was experiencing, so without further ado…

How I improved my 2012 Nexus 7 Performance

  1. Commit to the end goal. It’s going to get ugly, people.
  2. Plug in your device to a computer so you can view it as a storage device. Some people would say to copy everything – that’s silly. Instead, I copied the few Kindle books I had, along with the entire contents of the /Android/ folder (where most program info and game saves are stored).
  3. Factory reset the device. This is where the tears come down and you’re wondering if you’ve made a huge mistake.
  4. If you already had the update downloaded, it should update to the newest OS. If so, skip to Step 7.
  5. If you didn’t already have the update downloaded, then update your device to the newest version of the OS. It should have no issues getting through the update process, though it may take a while – leave it for a couple of hours so you don’t keep stressing.
  6. Now that you’re in Lollipop, factory reset AGAIN. Just to be safe.
  7. You’re clear! Download apps, copy back files, and your Nexus 2012 will act as good as new.

It seems silly to write an article that just says to factory reset, but after trying every option under the sun, this was the solution. I’ve tried rooting, I’ve tried managing startup programs, I’ve tried reducing programs, and I was considering chicken sacrifice, but luckily it didn’t get to that. The honest-to-god only solution I could find that worked was a straight out factory reset, something I hate to do, so if you’re wary then you’re in good company… I wouldn’t have believed me, either.

In the end, though, I can assure you it was worth the work of it… Lollipop is here, and the water feels fine.

Android Lollipop 5.0.2

Mmm mmm flat UI.

Update – January 19, 2014

As it turns out, the initial luck I had with Lollipop was short lived. Although the device is still very fast running apps (even demanding RPGs), something has dealt a serious blow to the internet connectivity. It could take me five times longer (if I’m lucky) to load something on the Nexus 7 than my laptop sitting next to it – yes, I even tested. Looks like I’m back on the market. :/

Update – March 25, 2015

Frustrated, I did a time test – you can see the results here.


Have any questions or comments about this article, or ways you think it can be improved?
Join the conversation in the comments below, or sign up for my newsletter to recieve periodic updates!

Tags: , , , , , , ,

5 Responses to “How Google killed my Nexus 7 (and then brought it back to life)”

  1. Applegirl March 20, 2015 at 16:14 EDT (4:14 PM) #

    Lollipop update killed my 2013 nexus 7 just barely 18 mo. old. After, the update it had crashing problems which it hadn’t had earlier. Just before a trip (literally before I stepped on the plane) it crashed and wouldn’t reboot. It only showed Google logo. I called Google from the hotel and the guy I talked to said that it was the update that had done it and that they had been getting lots of calls. He said since I had not purchased it through Google play store that Google would not help me. He transferred me to Asus who of course had no desire to help me as well. I said that Asus should be angry with Google as its software turns their hardware into bricks. Who wants to buy something risky? In the end this affects Asus also. I went out that morning and bought myself an iPad mini 3. Google you are greedy and not acting responsibly. I have my box and original receipt. When the class action suit comes, I’m first in line!

  2. bb March 27, 2015 at 12:09 EDT (12:09 PM) #

    Called Google demanding they do something to compensate for my Nexus 7 ruined by Android 5.
    Best they would do is give me the phone number for ASUS.
    Where is that class action suit?

  3. lomby@yahoo.com June 27, 2017 at 20:39 EDT (8:39 PM) #

    Google decided they didn’t like selling such a high resolution screen so cheaply, so they first disable texting, then they slowed it to a crawl with 5.x . They are scum pigs, no doubt about it. Google is a criminal enterprise in my observation.

    • TJ July 29, 2018 at 23:45 EDT (11:45 PM) #

      My tablet has been sitting for 2 years. I’m still pissed about this and looking for solutions to fix it. Can’t believe nobody started a class action for it.

Leave a Reply to Applegirl Cancel reply

%d bloggers like this: