Android 4.1.2 OTA Update Now Rolling Out to Nexus 7 - Adds Landscape Mode

NYC suburbs as well. After clearing cache twice for framework, it finally downloaded.cinstalling now.
 
I just spoke to tech support and was told that most have gotten the update and to do the framework. He said you have to sign in again I in play store if you use the framework method.

I didn't have to sign in again when I did framework.

Sent from my Galaxy Nexus using Tapatalk 2
 
No update yet for me, I am not desperate for it so going to wait it out, see how long it take to deliver (I am in the UK)

Sent from my Nexus 7 using Tapatalk 2
 
Hi, new here and to the Nexus so be gentle. Bought mine in UK but it now lives in Israel with me. Loving the tablet and the whole Android experience (1st time buyer) but one thing on my Nexus is really annoying. I got a prompt for the 4.1.2 update 3 days ago, updated and thought that was it, but my tab now sticks in landscape mode. I actually uninstalled Rotation (with license) as I thought this might be conflicting but nothing changed. If I reboot the tablet will start in portrait mode and flip into landscape when I start a game, but then stays there.

Should add, I know how to unlock the rotation from the notification bar top of the home screen, but nothing helps. Is this a hardware issue or something associated with the updated OTA?

Thanks
 
I'm in Delaware and no update yet after clearing framework several times.

Sent from my Nexus 7 using Android Central Forums
 
Thanks for the tip on clearing the framework. Now downloading the update 5 days after my daughter's came through automatically... :-s
 
I'm in Delaware and no update yet after clearing framework several times.

Sent from my Nexus 7 using Android Central Forums

Next door in Delaware County PA and nothing yet either. :-( Probably a coincidence though. Hoping for later today finally...

Sent from my Nexus 7 using Tapatalk 2
 
So I've had an interesting experience...

The update let me know without me doing the "clear data" on the Google Framework. So I let it do it's thing, but when it rebooted into Recovery, the signature could not be verified so it ask me if I want to continue with the update. I say "Yes" and then the whole process fails on me.

So eventually I had to update ClockworkMod Recovery using ROM Manager. I then had to do the "Clear Data" trick on the Google Framework. Once I did that, it picked up the update again and rebooted into recovery. It still asked me if I wanted to continue, but this time, the update went through...

Very weird experience. Hopefully all is well. Just in case anyone runs into this issue, try updating or uninstalling/reinstalling your ClockworkMod Recovery...
 
So I've had an interesting experience...

The update let me know without me doing the "clear data" on the Google Framework. So I let it do it's thing, but when it rebooted into Recovery, the signature could not be verified so it ask me if I want to continue with the update. I say "Yes" and then the whole process fails on me.

So eventually I had to update ClockworkMod Recovery using ROM Manager. I then had to do the "Clear Data" trick on the Google Framework. Once I did that, it picked up the update again and rebooted into recovery. It still asked me if I wanted to continue, but this time, the update went through...

Very weird experience. Hopefully all is well. Just in case anyone runs into this issue, try updating or uninstalling/reinstalling your ClockworkMod Recovery...

those are expected behavior. The google signed ota update can update using stock recovery without the signature warning and CWM cannot but it has a feature to disable signature check on update. i think that's what the warning you saw.

Now it makes me wonder how you got the update since i always thought you wont get ota update if you are on custom recovery
 
Last edited:
those are expected behavior. The google signed ota update can update without the signature warning.
and CWM cannot but it has a feature to disable signature check on update. i think thats what the warning you say.

Now it makes me wonder how you got the update since i always thought you wont get ota update if you are on custom recovery

I was pretty sure that it would notify that there was an update, but when you tried to install it would fail....strange.
 
those are expected behavior. The google signed ota update can update using stock recovery without the signature warning and CWM cannot but it has a feature to disable signature check on update. i think that's what the warning you saw.

Now it makes me wonder how you got the update since i always thought you wont get ota update if you are on custom recovery

Because I'm so lovable? Maybe Google threw me a bone...

I really don't know. While I was reading a book, the notification just popped up. Even when I went to go get it again, it only took me one time to "Clear Data" from the Google services framework and "check for update".
 
I was pretty sure that it would notify that there was an update, but when you tried to install it would fail....strange.

Well, it did fail, but only after trying to run the update through CWM Touch...I downgraded to regular CWM and it worked fine...

I was able to download it and actually ended up downloading it three times...
 
Happy ending to a weekend that ended rough. Got home from an exhausting night of work Saturday and accidentally washed my iPhone 4S. Luckily I had an upgrade available so on Sunday, I hit a VZW store up and walked out with a brand new GS3!! And now, I'm downloading the update to my N7. It's a good Monday.
 
Happy ending to a weekend that ended rough. Got home from an exhausting night of work Saturday and accidentally washed my iPhone 4S. Luckily I had an upgrade available so on Sunday, I hit a VZW store up and walked out with a brand new GS3!! And now, I'm downloading the update to my N7. It's a good Monday.
seems like it :-)
 
Edit> Nevermind, figured it out.

For anyone else having this problem, I had edited the build.prop to manually get a rotatable home screen. Bleh and I wiped my data already.... Drat.

====

I reset frameworks and got the update.
About 25% of the way into installing, I get the red triangle dead android error.
Does this every time -- I tried 3 times.
Rooted, unlocked, but stock ROMs. Tried wiping cache and all user data from recovery - no help.
Any ideas?
Thanks.
 
Last edited:
Finally got update notice yesterday (October 15) at 935 PM in NYC. After installation and 3 -4 hours of utilization, I noticed no performance change at all in GN7 - 16Gb.
 
For all you folks who are pining for the update, this will drive you crazy:

My wife was watching a video on her N7 this morning, when it suddenly stopped and she muttered a curse under her breath.

She used to do this a lot, right before she stopped using the iPad entirely, so I was concerned. I asked "What's wrong?"

Her reply: "Oh, nothing -- this thing has been telling me for three days that there's an update available, but it always pops up when I'm doing something, so I keep killing it."

When I told her that there were thousands of people worldwide complaining because they hadn't been able to receive the update yet, she said (without looking up) "Why? It's working just fine as it is."
;) :D

Sent from my Nexus 7
 

Latest posts

Trending Posts

Forum statistics

Threads
956,608
Messages
6,969,161
Members
3,163,584
Latest member
glastek15