yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Blueman101:
ok, cool

Thanks, I tend not to go into the Dev forum, I may be a CS student but all that code is a bit over my head

Ok so it will update from FRF72, so now i have to sit here and wait

but wait, what is the difference from waiting for the OTA vs downloading this file and updating it manually? Something sounds fishy shouldnt they be the same file? Which means why would the downloaded version not let 72 upgrade but the OTA will?
[Nexus One General] galaxys:
here's the info filled thread on dev: http://xdaforums.com/showthread.php?p=6922738#post6922738
[Nexus One General] :
I'm an epe54b unrooted in Tanzania. Just used the *#*#2432546#*#* code and now I'm running frf83. Everyone enjoy!
[Nexus One General] :
There are different updates for each different build. If you can get your hands on the appropriate update for you build before they push it to you, it doesn't matter, it's the same file.
[Nexus One General] mik3l04:
logcat you can share?
[Nexus One General] slowz3r:
Negatory sorry :(

but check the discussion thread here, someone might have it

http://xdaforums.com/showthread.php?p=6925238&posted=1#post6925238
[Nexus One General] ChronoReverse:
Looks like I managed to update from 50 to 83 using the manual update since the OTA didn't show up for me even with that keypad combination. Glad I didn't update to 70.

Now I just have to wait for CM6.
[Nexus One General] slowz3r:
Glad that worked out for you :)
[Nexus One General] Patsfan123:
I keep rebooting and typing in the checkin code. Nothing, I better leave this alone for a while..
[Nexus One General] Legacystar:
can anyone with the official update confirm if froyo supports connecting to ad-hoc yet?
[Nexus One General] mooselander:
Slowz3r which recovery were you using when you updated? I didn't see it posted but I'm assuming the stock recovery?
[Nexus One General] Orangeandblue302:
im about to downgrade from 72 to 50 lol. you guys are killing meeeeeee!
[Nexus One General] McHale:
log or it didn't happen. I've seen a few people claiming to get the OTA from epe54b to froyo yet NONE have been able to provide the URL for the download. something's fishy.
[Nexus One General] Orangeandblue302:
dude im with you, why the eff can no one pull a log? haha im just being rude cuz my Nex hasnt been hit yet :-(

Edit

well i cheated and I woulda had it but Im on 72...now i wish i wasnt...
[Nexus One General] :
Fishy, why? There's gonna be combinations of every upgrade path getting pushed. There's gonna be ALOT less epb54b's out there which means the chances of one of them actually logging the url before excitely upgrading diminishes greatly.
[Nexus One General] McHale:
because there's enough of us poor saps running stock 54b that are community minded enough to capture the log to get the URL to help others out. If nobody had claimed to have gotten it, I'd be less suspicious but the people claiming to have gotten it have extremely low post counts.

I hope I'm wrong and I wake up to froyo, I just don't think so right now.
[Nexus One General] :
From what I see those claiming are not att bound. The one I see on this page is form tanzania. Those carriers will be much easier to get an update through than ATT in the US will.

(Updates still need to be okayed by carriers). Switch to wifi overnight, you might get luckier. =P
[Nexus One General] slowz3r:
from FRF72
[Nexus One General] tjsimmons:
I was on EPE54B before I rooted. I think I have the right PASSIMG.zip to go back to stock recovery and ROM and I can try to get the OTA link.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] mortzz:
http://xdaforums.com/showthread.php?t=709340
[Nexus One General] McHale:
UPDATES ARE NOT OK'd BY CARRIERS.

Again, I believe he's a troll. When someone with a reputable post count says they got it, I'll believe it. Until then or I get it myself, I call shenanigans.
[Nexus One General] tankmorph:
If you are on FRF72 like I was, follow the instructions I found here to get to FRF83...

http://www.nexusoneforum.net/forum/...3-update-froyo-2-2-frf83-frf72.html#post59679
[Nexus One General] :
Feel free to keep believe that phone updates that are pushed through cell carriers don't have to be approved by them. (Hint: They do).

Considering froyo includes built in tethering, and ATT has dedicated tethering premium services, I'll eat the only hat I own if

ANYBODY gets froyo pushed by ATT on a nexus through an ATT 3g connection.

(and not manually going to the update link for epb54 build.)

ALL other carriers that push 2.2 on any androind phone will work with their respective manufacturers to included a "toggle" to activate tethering after having appropriate data plan as part of the update to 2.2.
[Nexus One General] slowz3r:
I dont see a real purpose to go through all that hassle. if you have FRF72 you WILL get FRF83 OTA. just like any OTA you may have to wait a little bit as they issue updates to devices by their IMEI number
[Nexus One General] tjsimmons:
My understanding was that those of us buying carrier unlocked Nexus Ones weren't dependent on the carrier to push updates like every other phone out there, and ours came direct from on high at Google themselves.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] tankmorph:
Yeah...I'm inpatient. But only took me about 20 minutes. I'm at work right now, so I'm getting paid to play with my phone!
[Nexus One General] slowz3r:
That was also my understanding, but hell I/we could be wrong
[Nexus One General] McHale:
The Nexus One OTA updates have nothing to do with the carriers. The carriers are not pushing out the update. AT&T N1 owners are not waiting for AT&T to approve it. How do you not know that?
[Nexus One General] :
You'll have to switch to wifi to download it, you won't get in on att's data connection.
[Nexus One General] tjsimmons:
Data is data.

AT&T isn't going to dive in and kill tethering for a phone they don't officially carry. My phone is not tied to AT&T, which is one of the main reasons I bought it. If they disabled that feature for a phone they eat no cost of, they'd have the EFF and a whole slew of net neutrality folks all over them.

Edit for clarification: I can download ROMs over AT&T 3G. They'd have to do deep packet inspection to sniff out a Froyo	OTA and block it or replace it. Which they aren't going to do. Comcast already got in trouble for similar things regarding torrents.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] McHale:
to get the OTA?!?!?

WHAT?!?!?!?

um, no.
[Nexus One General] logger:
Likewise. Need a few more EPE54B users to report having got it non rooted before I believe it. I am in Australia with a stock 850mhz. Can merrily "checkin" with or without sim fitted. So via wifi or cell and no sign of any OTA.

Can an OTA come via WiFi and bypass a carrier altogether?
[Nexus One General] :
K, sit tight guys, ATT is gonna bend the rules in order to lose money intentionally.

(feel free to shame me if you ever get to download the OTA over 3g on ATT in the US)

Every person getting the update on EPB54 is outside the US and outside of ATT.

Look through the reference material for android. OS updates MUST be approved by their respective carriers if the carrier is going to push it. Outside the US carriers are more lenient with customer provided phones.
[Nexus One General] McHale:
did you hack someone's account and take over their post count? How did you get that many posts and not have a clue what you're talking about? Do you even have a Nexus One? Android? A cell phone?

I'm embarrassed for you.

Seriously.
[Nexus One General] AvengerBB:
Of course it won't be pushed by AT&T - it's not a phone sold by AT&T.
[Nexus One General] McHale:
Yes, you can get it via WiFi. The update is a simple file download from Google to your phone. The carrier is merely a data pipe like your internet connection at your house.

However, JCopernicus may think that AT&T is denying you your update too so maybe you should call AT&T? ;)
[Nexus One General] SBERG117:
I dont see how he doesnt get it either. The one factor above all else that the N1 represents is .....Freedom. It really is that simple. :D:D
[Nexus One General] DMaverick50:
I am on 50 and the code gave me "this call cannot be completed as dialed..."
[Nexus One General] :
Do you guys really think Google and ATT are entirely independent of each other with service and the Nexus phone?

Naivety, oh it's so wonderful.
[Nexus One General] logger:
Do they accept collect calls from Australia ;)
[Nexus One General] slowz3r:
really, you sure your not messing something up?
[Nexus One General] pfmiller:
Ready. OTAs come over the internet. It doesn't matter if your network connection is WIFI or 3G, as has been said already data is data. In order for it to not work over 3G AT&T would have to intentionally block connections to the update server. Why would they waste their time doing this if as soon as a user gets on a WIFI connection they'll get the update anyway?

Perhaps "if the carrier is going to push it" is the key phrase. If Google is going to push it, as with the N1, the carrier would not need to approve anything.
[Nexus One General] mikehoffer:
*#*#2432546#*#*
[Nexus One General] iboj007:
I have a Canadian (Rogers) sim card as well as an AT&T sim card.... im going to try to see if if allows me to update with a different sim.
[Nexus One General] tjsimmons:
Ding ding ding. The internet is a series of tubes, kids. Data is data.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] tjsimmons:
Thanks for articulating what I was trying to say. It's late and I'm tired.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] hotsoda:
Make sure you dialed the code in correctly. After dialing, you shouldn't press the send key, the code should disappear and you should receive a notification in the pane saying "success."
[Nexus One General] GldRush98:
Dude, you sound like such a moron. Just stop now.

McHale is 100% accurate, and every damn thing you have said is flat out WRONG. Just stop it.
[Nexus One General] bajansurfer:
it's *#*#2432546#*#*
[Nexus One General] McHale:
No. In case you haven't followed news about AT&T, they suck balls. They send cease and desist letter to their own customers! :eek:

-Mc
[Nexus One General] slowz3r:
Should get this, without needing to hit dial
[Nexus One General] :
I agree, data is data. If you can browse directly to the download link that has the proper update.zip for EPB54, short of ATT putting an IP block on that site, you WILL get it.

That is different from getting a PUSHED notification update for the phone OS.

The system updates for android go THROUGH the carrier before getting to the google servers if you are using 3g. ATT will not be actively sending updates to essentially bypass their current plans.

Do you guys have any idea how much **** ATT can get into for knowing PUSHING updates to customers with whatever a MFG decides without some kind of consultation before hand?

edit:

Just for reference on how "free" you are, the Carriers have absolute say on what applications can appear on the Android Market. (this is not conjecture, this is fact).
[Nexus One General] logger:
I think AT&T are blocking him from using "checkin" :D
[Nexus One General] J.L.C.:
You should be able to update with wifi and no sim at all

That is, once the OTA is actually available
[Nexus One General] GldRush98:
NO, it is in fact NO different. GOOGLE pushes the updates. AT&T is no more involved in it then your cable ISP is involved in allowing you to post stupid things on message boards.

The system updates are STRAIGHT from Google on the Nexus One. AT&T has NOTHING to do with Nexus One system updates.

Again, AT&T DOES NOT PUSH ANY NEXUS ONE UPDATES. GOOGLE PUSHES ALL NEXUS ONE UPDATES. AT&T HAS NOTHING TO DO WITH IT.

Jesus.
[Nexus One General] GldRush98:
It is final Froyo. Google merged all the 2.2 code in to the AOSP today. This update contains the final release code of Froyo. Give it time, the other update files will come man. They probably just started with the update that was supposed to only be on Google dev phones first. They will be pushing the other updates soon enough.

Regarding Exchange enhancements, I didn't think that was for 2.2. I think that was in their "down the road" section along with the music push stuff.
[Nexus One General] :
Must be nice to think you ATT data connection is "free from restrictions".

These are not things that I'm making up folks, these are things that are written by google themselves.
[Nexus One General] clickwir:
You are thinking from a Network Infrastructure perspective... try a bit more towards the Board Room perspective.

Google and ATT have agreements. You can't just make a phone and have it work on someone's network without getting some paperwork in order first. If ATT and Google want to, they can (and probably do) have at least some basic testing procedures they would both like to signoff on before actually starting the technical part of rolling it out.

So unless we hear from someone inside at Google and/or ATT, assume the possibility that ATT could be influencing the OTA upgrade.

I'm on TMO anyway and running FRF72 anyway. So I'm close enough for now to wait patiently.
[Nexus One General] pfmiller:
I hope you're wrong. I think you are. ;-)

One reason, they released the source code. They aren't going to release the Froyo code until it is done. If they are still testing things that means changes can still be made which means the Froyo code they released today is not really Froyo. I don't see that happening.
[Nexus One General] slowz3r:
Oh AT&T, i think #/* codes are carrier specific?
[Nexus One General] mikehoffer:
Wi-fi on.

Did about 6 successful checkin's.

Rebooted, did another checkin.

Nothing.

The good news is a woot off just started:)
[Nexus One General] Orangeandblue302:
@GldRush98 & JCopernicus

not to sound like a **** but you guys need to chill before this thread gets locked, you guys can battle it out on your facebooks or something, please dont get this thread closed it has some good info buried under childish nonsense.
[Nexus One General] McHale:
I know they released the code to AOSP. But not only did I watch the I/O, I took screen shots and the Exchange integration (Calendar) was specifically mentioned as a 2.2 enhancement and they made it pretty clear it was to be released when 2.2 came out. It wasn't explained like a "down the road" feature - at least I didn't take it that way.

http://developer.android.com/sdk/android-2.2-highlights.html

If the Exchange and security features are not in the final OTA, than they suck balls and failed.
[Nexus One General] slowz3r:
guess you gotta wait till the system gets to your IMEI..

I find it really annoying that people still think that this whole FRF83 OTA is just a big elaborate troll
[Nexus One General] Yatyas:
However, the ATT version was actually made for Rogers (but works on ATT) if I am not mistaken. So why would Google need any agreements with ATT. This could be supported by the fact that there are no ATT subsidized versions.
[Nexus One General] mikehoffer:
No, checkin works fine with AT&T.

Starts with *#*#

ends with #*#*

Don't press "send". It sends the code as soon as you press the last "*"
[Nexus One General] pfmiller:
You're not wrong, but the situation according to JCopernicus is that AT&T users can get updates pushed to them, but only over WiFi. If Google was waiting on approval from AT&T then Google wouldn't push an update to any AT&T phones, no matter how they are accessing the internet. So regardless of if AT&T will hold up Froyo for their customers or not, I think it is still safe to say JCopernicus is wrong on this one. (Sorry JC, no offense)
[Nexus One General] GldRush98:
No, these things are NOT written by google themselves.

Yes, actually you can. That is why you can take your provider's SIM card and stick it in to ANY UNLOCKED GSM phone. GSM is a standard. Any phone complying with those standards will operate on any provider's sim card (network).

The amount of misinformation in this thread is terrifying.

I am trying to stop the spread of misinformation. JCopernicus needs to go read up how GSM carriers and phones work. He is obviously clueless.

However you're right. This isn't the time for this.

The OTA update is out there. Now we just need a dev to pre-root it so it can be installed on rooted devices (assuming this IS the final release).
[Nexus One General] DMaverick50:
Check in worked thanks for the help
[Nexus One General] vanessa13006:
Hi,

My nexus one is already unlock but because of frf83 i lost the root. So is it possible to re-root my N1 with frf83 installed ?

Thanks before and sorry for my english
[Nexus One General] McHale:
I believe it's another step in the beta cycle.

Check Android's highlights list for 2.2:

http://developer.android.com/sdk/android-2.2-highlights.html

Are those in FRF83?

hint: no.

The only file we have is the upgrade from frf50. And why hasn't a single Google employee state that OTA's have started? They've tweeted everything else.

-Mc
[Nexus One General] Orangeandblue302:
@GldRush98

like i said i didnt wanna sound like a **** cuz I know how it goes, i just wanna see this thread around for a bit ;)

Now will someone get a goddarn Logcat for frf72????? AHHHHHHHHH
[Nexus One General] pfmiller:
Are you sure calendar support isn't in there? I thought I heard a few weeks ago from Froyo users that Exchange calenders now show in the Calendar app.

Also, their are screen shots showing the new remote administer options for exchange, don't these work? Even if this wasn't final, there's no way Google is adding features this late in the game. Either the feature is there or it's not a part of Froyo.
[Nexus One General] slowz3r:
I'm not second guessing the validity of this update but last i heard (AKA yesterday) google said something along the lines of "we are working feverishly" So maybe this isn't final as in with all the advertised features, maybe this is just a tease to make everyone happy? and newer 2.2 OTA will come in the near future?
[Nexus One General] SBERG117:
Assuming this isnt the "final" build, with what was released yesterday, is that what the mod makers need to build newer stuff? I mean this is the "source" thats been waited on?

Thnx, im learning as i go :D:D
[Nexus One General] pfmiller:
No way. Feature freeze comes at least a month before final release. If they are still working on adding features now then that would have to mean they were straight up lying at I/O when they said Froyo was only a few weeks away.
[Nexus One General] :
I won't get get this thread locked, I'm not the one throwing insults.

Os update notifications are initiated by carriers as a request from MFGs. This is done after an approval process. Google has almost definately submitted their 2.2 update to ATT to push it to it's customers. Likely response form ATT : lol, take out free tethering first. One thing I'm unsure of, is if the 2.1 build "checks in" periodically for updates. If it does then you will get a notification. If it doesn't you will only get the notification for an update after you INITIATE the system update. At that point it's the user requesting the update, and short of ATT turning orwellian and actively blocking the IP/DNS address for the update you will get it. This scenario is ENTIRELY different form actively pushing an update to consumers by ATT.

Take a few minutes and dig through the AOSP develpoper's site, you'll find it, something along the lines of:

OTA updates are to be approved by carriers before being PUSHED out by carriers.

ALL of those things have been included since FRF50...
[Nexus One General] McHale:
I heard the pin code and remote wipe were not in there at all and the calendar wasn't working that well. Again, I could be wrong since I'm still stock but I'm also following the Google forums and getting bits and pieces from those that did the manual update.

http://xdaforums.com/showpost.php?p=6926100&postcount=271

All I need to see is one Google employee state that OTA's have started. Just one. Otherwise, it's another beta. Even if an AT&T friendly version shows up...

-Mc
[Nexus One General] slowz3r:
Then could it have been an "oops" release seeing as FRF72 to FRF83 was only around 600kb
[Nexus One General] Orangeandblue302:
The source that the Devs were waiting for was the 2.2 AOSP which was released during the Droid X sexfest
[Nexus One General] SBERG117:
Ok cool, Just makin sure lol
[Nexus One General] mikehoffer:
I'll put my 2 cents in here then I'm going to bed.

1. The market was mysteriously down for 30 minutes today much like Apple's "oops we'll be right back" crap on itunes whenever they release a new product. And I'm pretty sure a market re-design was part of the Froyo announcement at i/o. Sounds like a Google engineer screwed up.

2. Tomorrow is iPhone 4 day. Hopefully Google will piss in their cheerios a little by releasing Froyo OTA.

3. AT&T clearly stated when the Nexus One was released that they would "happily sell anyone a SIM card and data plan that walks into an AT&T store with an N1 because of our open network policy" blah blah blah. They have no affiliation with Google regarding the N1. I don't see them blocking OTA. Are they blocking root users from tethering? No.

4. Since the code went AOSP any OEM could release a Froyo update today. They won't, but they could. It's only logical that the N1 gets updated first and ASAP.

One more checkin. Nothing.

Goodnight!
[Nexus One General] MENDEH:
i used to have a t-mobile g1 unlocked and on at&t yet i still got updates pushed to my phone.

which of the following makes the most sense to you?

1. at&t had to approve t-mobile's update to push to my g1

2. t-mobile pushed the update to my g1 even though i was running on at&t's network

3. google pushed the update to my phone
[Nexus One General] cmstlist:
I do love this word "push" but based on my understanding of Android OTA updates, the phone actually polls periodically for updates. So really it pulls them. :)

My understanding is, when a carrier releases *their version* of an Android phone, that carrier gets to be a gatekeeper for OTA updates delivered through Google's (or the manufacturer's) checkin service. So if you have a Sprint Hero, then even if you've fuddled it to work on Verizon or Page Plus or some other carrier, it will get the OTA when Sprint releases the OTA. If you have a Vodafone HTC Desire and you're using it on 3, or Giffgaff, or O2, or whoever else, it's still a Vodafone Desire for the sake of OTA updates. An AT&T HTC Aria on Rogers will receive OTAs destined for the AT&T Aria; and a Telus HTC Hero on AT&T (if it ever does get an update!) would receive an OTA destined for a Telus Hero.

The Nexus One is not any carrier's phone (unless you did get it through a carrier, in which case maybe it is). The phone polls Google for OTA updates, over whatever data connection is available. It never asks T-Mobile, or AT&T, or Rogers, Bell, Telus, Telstra, or anyone else for any input into the matter.
[Nexus One General] Blueman101:
Google directly pushes updates for the G1, MT3G and the N1, all other phones (as they are carrier based) must be updated through the carrier.
[Nexus One General] MENDEH:
hey that was meant for jcopernicus ;)

how will he learn if other people take the quiz for him?
[Nexus One General] musashiken:
Ok then what about us users from outside USA? I'm in Asia, my local carriers have no contract with Google to sell Nexus ones here and I got mine straight from Google's website. So care to explain how I can get my OTA? I don't really give a rat's ass about american carriers so all that talk about ATT is just hocus pocus to me.

And I got my Eclair 2.1 to 2.1 update 1 OTA 1.5 weeks after the americans got it. So is there some kind of priority given to users of certain countries?
[Nexus One General] mortzz:
Seems a bit better than FRF50. I don't have as much trouble with the Market not connecting.
[Nexus One General] erikiksaz:
Courtesy of hpe:

(72->83)

http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF72.684bd56a.zip
[Nexus One General] slowz3r:
im sure this will be appreciated