Has your Nexus** received a 4.2.2 OTA yet?

[LostPassword]

My wife's yakju got it last night (Feb 14). My takju got it same night after clearing the Google frameworks thing a few times.

 

[rh71]

Shocking to see so many people here with nexus devices running stock roms.

what are the negatives of rooting? I just want to stay in good standing with my carrier. People always talk about it but I just never took the leap.

 

[papaschtroumpf]

I was hoping 4.2.2 would fix some of the wireless problems in the Qualcom driver, but Google has confirmed those fixes are not present in 4.2.2.
I'm guessing they rushed it out to remove LTE capabilitie, and not much else.

Let us know if you fins anything significant that changed.

I used voodoo RootProtect before applying the update so I wouldn't lose root and it worked like a charm.

 

[Thor86]

Just got it on my GN OTA.

 

[Capt Caveman]

N10 updating now. No update for N4 yet.

 

[NightFox]

Got the update for N4 today.

 

[Crap Daddy]

N7, got it.

 

[BlahBlahYouToo]

what are the negatives of rooting? I just want to stay in good standing with my carrier. People always talk about it but I just never took the leap.

not much really. slight, minute chance of bricking the phone.
low risk, high reward. no brainer imo.

 

[lopri]

Go to Play store and do a search of "root" or "[root]" and see what kind of works require root access.

Oh, and it voids warranty although there usually is a way to revert it (unroot).

 

[Bateluer]

Galaxy Nexus... still showing 4.1.1. Why didn't I even get 4.2? I'm on VZW. Says last checked this morning at 8am.

EDIT>> nvm, found this: http://androidcommunity.com/verizon-galaxy-nexus-is-now-four-updates-behind-20130212/

WTF Verizon?

Verizon's support of the Galaxy Nexus has been abysmal, a text book example in how to fvck something so badly you ensure you never get a Google flagship device again.

Shocking to see so many people here with nexus devices running stock roms.

Well, a common desire for root is to remove carrier bloatware and manufacturer skins. Weaknesses the Nexii don't have. With a GSM Nexii, you get your OTAs pretty damn quick, often faster than the community roms can bake the new code into the ROM. Depends on whether Google uploads the new code into AOSP before or during the OTA rollouts. 4.2.2 went into AOSP right as the OTAs began.

 

[lopri]

Neither my N4 nor N7 has gotten the notice yet. Ugh.

This dude goes an extreme length to find out what's changed. I admire his attention to details.

http://www.androidpolice.com/2013/0...ely-tiny-changes-and-an-androidhome-sighting/

 

[Grey]

My n7 got it yesterday morning. Have to rma it for a speaker issue. I already miss it :-(

 

[Ksyder]

Well, a common desire for root is to remove carrier bloatware and manufacturer skins. Weaknesses the Nexii don't have. With a GSM Nexii, you get your OTAs pretty damn quick, often faster than the community roms can bake the new code into the ROM. Depends on whether Google uploads the new code into AOSP before or during the OTA rollouts. 4.2.2 went into AOSP right as the OTAs began.

I started feeling guilty about my Nexus being stock 4.2.2 but then i tried to think of what I would gain by putting a rom on it and the only thing that came to mind would be battery percentage on the battery icon.

Is there any other good reason to use a custom rom?

 

[BlahBlahYouToo]

Go to Play store and do a search of "root" or "[root]" and see what kind of works require root access.

Oh, and it voids warranty although there usually is a way to revert it (unroot).

The toolkit makes returning to stock just as easy as unlocking and rooting it.

 

[BlahBlahYouToo]

Well, a common desire for root is to remove carrier bloatware and manufacturer skins. Weaknesses the Nexii don't have. With a GSM Nexii, you get your OTAs pretty damn quick, often faster than the community roms can bake the new code into the ROM. Depends on whether Google uploads the new code into AOSP before or during the OTA rollouts. 4.2.2 went into AOSP right as the OTAs began.

there's also all the additional customizations and features you can't get with stock.
things that i love about aokp.
volume up/down to skip/rewind tracks
proper notification toggles (no, 4.2.2 still doesn't do it right and 3rd party toggles have always been buggy)
brightness slider at top of screen
ability to underclock/undervolt, set cap on clock speed (battery savings)

aside from ROMs, rooting allows you to load custom kernels (better batt optimizations), ability to mount usb drives, TiBu and other apps that require root.

 

[Bateluer]

there's also all the additional customizations and features you can't get with stock.
things that i love about aokp.
volume up/down to skip/rewind tracks
proper notification toggles (no, 4.2.2 still doesn't do it right and 3rd party toggles have always been buggy)
brightness slider at top of screen
ability to underclock/undervolt, set cap on clock speed (battery savings)

aside from ROMs, rooting allows you to load custom kernels (better batt optimizations), ability to mount usb drives, TiBu and other apps that require root.

True, just said that a big reason people root is to deal with the bloat.

Kicked my Google Services Framework this morning and my 7 pulled the ota.

 

[GTaudiophile]

Yes, yesterday.

A couple of minor oddities noticed I suppose:

1. The drop-down status/task bar descends slower than it use to.
2. The clock on the lock screen switches from being centered to right-justified. I lock the phone, go to unlock, the clock is centered, unlock, lock, go to unlock, clock is right-justified, unlock, lock, go to unlock, clock is centered, etc. (I think this may have something to do with the Lock Screen Policy App that disabled the newer lock screen functions.)

 

[abaez]

Just checked right now and it is ready to install. Takju GSM galaxy nexus.

I think clearing google services framework f's up a couple of things now. I was doing that the past few days and was having issues getting gmail and google voice notifications and stuff.

 

[Grey]

Yea when I cleared the framework I lost the google play store and Gmail as well. It came back after a bit but something to be aware of for sure.

 

[MoInSTL]

Just turned on my Nexus 10 and I had it waiting.

 

[LostPassword]

i noticed some issues doing that framework thing. so i just reflashed straight to 4.2.2. looks good so far, except i don't get any facebook notifications.

 

[Suspicious-Teach8788]

anyone notice the new colors in 4.2.2? It's much better than before although the display isn't the best calibrated still...

Neither my N4 nor N7 has gotten the notice yet. Ugh.

This dude goes an extreme length to find out what's changed. I admire his attention to details.

http://www.androidpolice.com/2013/0...ely-tiny-changes-and-an-androidhome-sighting/

So the vibrate option in stock SMS is only an on/off now. I hate how Google is forcing us to have only a few options in notifications. First they link notification and ringer volumes. Then they take away system volume. Next they force vibrate to override ANY in-app setting in 4.2 so that it always vibrates resulting in massive amounts of Gtalk and Gmail vibrations when my phone is in vibrate (no way to disable that unless I turn my phone to silent). I wonder if that vibrate checkbox in the SMS app even means anything since in vibrate mode the system will override in-app settings....

 

[lopri]

The vibrate option in SMS actually gives more options, I think? According to the description it looks like vibration is no longer tied to sound in SMS.

System-level vibration control does make sense since when you're in a sensitive place and want to disable vibration you don't want to go through every single app that might vibrate.

No idea on what is being forced in notification area. But then again, I've seen your concept of "being forced," so I suppose it can be anything. ^^ (I'm being forced to choose!)

 

[thecapsaicinkid]

Battery life at < 0.8%/hr with the screen off after the wakelock fix.

 

[Suspicious-Teach8788]

The vibrate option in SMS actually gives more options, I think? According to the description it looks like vibration is no longer tied to sound in SMS.

System-level vibration control does make sense since when you're in a sensitive place and want to disable vibration you don't want to go through every single app that might vibrate.

No idea on what is being forced in notification area. But then again, I've seen your concept of "being forced," so I suppose it can be anything. ^^ (I'm being forced to choose!)

But a lot of us use vibrate mode (especially males) everywhere we go. Google's 4.2 vibrate forces ALL notifications to vibrate. Previously, it would respect in-app vibrate. And as you said, if you want to disable vibration in a sensitive place, then you go to silent. But for those of us who want vibrate, we should be able to choose which apps. That's how it was in 2.x, 4,0, and 4.1. Right now I get a good number of Gmail alerts and Gtalk alerts. I don't want my phone vibrating nonstop. At the same time, going to silent is no good because then I miss critical texts and calls.

I think it's a foul up. Essentially Google's saying if you're in vibrate, EVERYTHING vibrates. You have no choice whatsoever.

What you're talking about is switching to silent mode, which still applies today. Once you switch to Mute/Silent, everything stops vibrating even if the in-app setting says vibrate.