• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Ota 2.2.2 frg83g

Hi,
Does anyone knows if this update has any effect on Rooted phones ?

I have a stock but rooted FRG83D and my N1 has already downloaded the OTA...
For now I'm refusing it, as most OTAs Un-root rooted phones.

Can such a small (~500kb) update unroot a rooted phone ?
I prefer to be on the safe side and wait untill I know...
 
i have a problem with 2.2.2.. i cannot connect to 3G since i got t. 2G only.. wtf!!?? im seriously gonna give it a couple of days before hard reset
 
I received an OTA System Update notification from Google. It stated it was issued to fix "minor bugs". After updating, my Android Version is still reading 2.2.1 and the Build Number is still reading FRG83D. It appears nothing has changed.

Same here ... stock N1 on AT&T.

Perhaps we're lucky for not having a successful update. It seems to have created even more "bugs" rather than actually fixing them.
 
Stock Rom ATT Nexus1. Although my bootloader is unlocked, I went back to the stock rom.

The system update popped for me today and it installed without a hitch, just like the 2.2 did.

I checked the menu because others said they were not getting it updated, mine's 2.2.2.

But, you shouldn't care. From what I read 2.2.2 is just a fix to incorrectly sending text messages to the wrong person. It never happened to me personally.

2.2.2 doesn't do anything for you, so you can effectively not care about it.
 
I also received the update today, but after a reboot the version is still 2.2.1 and when I manually check for updates it tells me I'm up to date. Don't recall ever experiencing the SMS bug. Stock N1 unrooted on T-Mobile in Houston.
 
Hi,
Does anyone knows if this update has any effect on Rooted phones ?

I have a stock but rooted FRG83D and my N1 has already downloaded the OTA...
For now I'm refusing it, as most OTAs Un-root rooted phones.

Can such a small (~500kb) update unroot a rooted phone ?
I prefer to be on the safe side and wait untill I know...
Yes, you will always lose root with an OTA update. You can still get it back with SuperOneClick though.
 
i have a problem with 2.2.2.. i cannot connect to 3G since i got t. 2G only.. wtf!!?? im seriously gonna give it a couple of days before hard reset

Got my update last nite.. Updated fine (unrooted). No apparent probs with either wifi or 3G...

Reports itself as 2.2.2, baseband 32.41.00.32U_5.08.00.04 - I failed to check what 2.2.1 was first -- anyone know what 2.2.1 baseband was & what the differences are??
 
I downloaded an app called Blade Wifi Fix. It doesn't stop the wifi from disconnecting in sleep mode, rather it toggles the wifi on and off automatically when it senses that it's be disconnected. It's not exactly the solution I was looking for but it's a helpful alternative.

Thanks, I'll give it a shot.
 
Got my update last nite.. Updated fine (unrooted). No apparent probs with either wifi or 3G...

Reports itself as 2.2.2, baseband 32.41.00.32U_5.08.00.04 - I failed to check what 2.2.1 was first -- anyone know what 2.2.1 baseband was & what the differences are??

Hmm, mine is just stock (was on 2.2.1, no idea about baseband) - ota update arrived yesterday afternoon and installed with no hiccups.
But, it's now listed as 2.2.2, baseband 32.36.00.28U_4.06.0012_7 , kernal version 2.6.32.9-272.40-gbca5320, FRG83G.

Is this as it should be? Why is Artful's radio different? Have I missed something along the way?
Cheers Guys, apologies if they are stupid questions :o
 
I got mine last night; installed flawlessly.
(stock N1 running 2.2.1)

Swype doesn't work anymore; I have to reinstall it.
 
Has anyone noticed bugginess in wifi since the 2.2.2 update? My wifi seems hit-ro-miss now and rebooting doesn't help...
Yup, it's happening with my N1, WiFi can not be catch .I think the security update affects the WiFi holding software with some new routers. I don't know wt 2 do? Please if any one has any clue? thx.
 
Hmm, mine is just stock (was on 2.2.1, no idea about baseband) - ota update arrived yesterday afternoon and installed with no hiccups.
But, it's now listed as 2.2.2, baseband 32.36.00.28U_4.06.0012_7 , kernal version 2.6.32.9-272.40-gbca5320, FRG83G.

Is this as it should be? Why is Artful's radio different? Have I missed something along the way?
Cheers Guys, apologies if they are stupid questions :o

Weird - and you & me both on 3 in UK... Dunno why we are different...

If relevant I recently had mine fixed (touchscreen prob..) by HTC MK and returned to me ....
 
why change the radio version along with touchscreen ? that's not the problem. if you remember ,the 2.2.1 FRG83D [for some] came along with a newer radio version ...tha's why some are different.
 
Oh, it's not a problem - just my idle curiosity.
I wondered how Artful had ended up with the Korean radio version whilst mine remained on v.4.06 when we both ordered our phones within two weeks of each other (in the first month of the N1's "birth"), both ordered direct from Google and shipped from USA to UK, and both on same network (3UK) - I'd expect the radios to be the same :confused:.

Having said that, the Sept 2010 update arrived ota (wifi) whilst I was on hols in France *shrugs*
 
that is the EU version of the radio ,the Korean is 5.12.0..somethin' .

you can always update it if you have root :)
 
Oh no! You mean there are even more versions of the little buggers!! :eek: :D

Thanks, tho :)


  • 4.06 = Original US 2.2 radio
  • 5.08 = Original Korean/Euro radio (and also included in the unreleased US FRG33 passimg for some reason)
  • 5.12 = Korean FRG83 radio
 
Second time i get the notification for the update to 2.2.2 ... second time i select reboot phone to install ... second time it fails to update.

Third time's the charm? Or should I be looking for something else?
 
why not try to manually update it ?? did it to my stock ROM 2 days ago and was fine ...backed it up ,and went for cyanogen again :)
 
Has anybody else had the issue of their car home app causing the phone to reboot when placed into the car dock? I didn't have this problem until this update and now I have it nearly every time that I use the dock.
 
I posted this separately, but I haven't gotten any responses on this...since the upgrade, have you encountered delays in your messages being delivered out? I didn't have this issue prior to the upgrade, but since then, I've had some messages in a "sending" status, but not deliver. Even more noticeable when I'm sending a message to multiple people.
 
Back
Top Bottom