[88 FLUX]

Ok. I feel that a few things need to be clarified because people continuously post frustration and questions without doing their research.

Froyo has not been officially released for the Nexus One. Not at all whatsoever. Everyone that seems to think that FRF83 is the official release build is reporting it as such incorrectly. YES, IT MAY BE POSSIBLE THAT FRF83 IS THE BUILD THAT DOES GET MADE OFFICIAL AND PUSHED OUT BUT THAT HAS NOT BEEN CONFIRMED OR PROVEN YET.

All the sites reporting "OMG!!! FROYO OTA!!! ZOMG!!! FINAL BUILD!! WEEEEE!!!!" are not giving all the facts. FRF83 was pushed out as an OTA to those who had manually updated their phone to the leaked FRF50/FRF72 that was not meant for public release. The only two FRF83 updates that have been leaked have been FRF83-from-FRF50 and FRF83-from-FRF72. Those with ERE27 still have to go FRF50-from-ERE27 and THEN go to FRF83. Backwards logic shows that this is not a final OTA push of Froyo as many blogs are incorrectly referring to it as. An update that only applies to those using a pre-release leaked build does NOT constitute "official".

Everyone needs to stop flipping out. I am just as frustrated as everyone (as an EPE54B user) that the rollout has not officially begun. But that does not give us the right to complain. When it is ready, it'll come out. Until Froyo was announced, everyone was perfectly content with their phone. So stop acting like suddenly the phone is worthless just because Google hasn't come through with the official Froyo release yet.

Here is what everyone has every right to get angry at though (if it happens): I support a fully mad internet-based riot if ANY other Android phone gets an official Froyo update before the Nexus One. This would completely negate one of the main aspects that drew people to the phone.

Now can't we all just get along?

[potheadhero]

Ok. I feel that a few things need to be clarified because people continuously post frustration and questions without doing their research.

Froyo has not been officially released for the Nexus One. Not at all whatsoever. Everyone that seems to think that FRF83 is the official release build is reporting it as such incorrectly. YES, IT MAY BE POSSIBLE THAT FRF83 IS THE BUILD THAT DOES GET MADE OFFICIAL AND PUSHED OUT BUT THAT HAS NOT BEEN CONFIRMED OR PROVEN YET.

All the sites reporting "OMG!!! FROYO OTA!!! ZOMG!!! FINAL BUILD!! WEEEEE!!!!" are not giving all the facts. FRF83 was pushed out as an OTA to those who had manually updated their phone to the leaked FRF50/FRF72 that was not meant for public release. The only two FRF83 updates that have been leaked have been FRF83-from-FRF50 and FRF83-from-FRF72. Those with ERE27 still have to go FRF50-from-ERE27 and THEN go to FRF83. Backwards logic shows that this is not a final OTA push of Froyo as many blogs are incorrectly referring to it as. An update that only applies to those using a pre-release leaked build does NOT constitute "official".

Everyone needs to stop flipping out. I am just as frustrated as everyone (as an EPE54B user) that the rollout has not officially begun. But that does not give us the right to complain. When it is ready, it'll come out. Until Froyo was announced, everyone was perfectly content with their phone. So stop acting like suddenly the phone is worthless just because Google hasn't come through with the official Froyo release yet.

Here is what everyone has every right to get angry at though (if it happens): I support a fully mad internet-based riot if ANY other Android phone gets an official Froyo update before the Nexus One. This would completely negate one of the main aspects that drew people to the phone.

Now can't we all just get along?

Agreed! I just recently purchased an N1 for AT&T and would be pretty pissed off as well if the N1 does not get updated before the other phones seeing as after all this is a GOOGLE phone. I am just patiently waiting but Froyo is one of the reasons why I chose this phone so I am hoping Google does not screw us over.

[Krak-a-Lakn]

Agreed! I just recently purchased an N1 for AT&T and would be pretty pissed off as well if the N1 does not get updated before the other phones seeing as after all this is a GOOGLE phone. I am just patiently waiting but Froyo is one of the reasons why I chose this phone so I am hoping Google does not screw us over.

Yup, same here. The Nexus 1 darn better be the first.
Though, as a fellow AT&T subscriber I fully expect that AT&T will delay their OTA version of 2.2 so they can strip out the tethering.

I mean, AT&T never looks past an opportunity to screws it's customers.

[Phil Nickinson]

EXACTLY! I knew I wasn't the only person screaming this from the rooftops.

[88 FLUX]

Yup, same here. The Nexus 1 darn better be the first.
Though, as a fellow AT&T subscriber I fully expect that AT&T will delay their OTA version of 2.2 so they can strip out the tethering.

I mean, AT&T never looks past an opportunity to screws it's customers.

AT&T has no say in the firmware going to the N1. The only thing associating the phone with AT&T is that the model in reference includes support for their 3G bands. Since they do not offer official support nor do they sell it through themselves with subsidy, AT&T can hold no say in what gets pushed to it.

But yeah, definitely. If Google does it just simply to be on AT&T's good side, that would be messed up. But that would be Google's decision, not AT&T.

[vebix]

Thank god somebody gets it. The blogosphere has been horrible about delivering this info. And it shows no sign of stopping any time soon.

Oh and something I reserve the right to complain about - if the next release doesn't fix the 3G radio issues on the nexus. I actually can't use my phone as a phone if I don't lock it to 2G. (T-Mobile, Jacksonville FL area)

[potheadhero]

I have just been very bothered due to the fact that only T-Mobile updates have leaked out and not one sign of an AT&T update in sight. It is a little bothersome and makes me worry that I might have invested my money on a phone that is not going to get the right support.

[maevro#CB]

This is not even a Google issue. I've been a loyal AT&T user for years and they have always been behind on updates. I had tons of WinMo phones that I used cracked ROMs and radios.

People shouldn't buy a phone hoping that the company keeps its promise of an update. I was a rep for companies like HTC, Nokia and Samsung. The US is a small market on the scheme of things.

When its released, its released. I've seen too many updates in phones where the Rom was rushed and then you have everyone whining about update issues.

I go thru phones, both locked and unlocked like water. I was just given a HTC Aria. Is love it to have 2.2 butits running 2.1 and I'm happy with this phone, very happy.

BTW I had a Backflip with a non official 2.1 update. It was full of problems, which is what happens when you rush this stuff. No wonder AT&T nor Motorola has officially released it.

I agree with the OP. Relax.

[88 FLUX]

I have just been very bothered due to the fact that only T-Mobile updates have leaked out and not one sign of an AT&T update in sight. It is a little bothersome and makes me worry that I might have invested my money on a phone that is not going to get the right support.

This is pure speculation but the reasoning that I would assume is simply because the T-Mobile variant was the original version and the one that the devs at Google were supplied with (for example, the holiday phones). So this is the one that is being used to produce, test, and rework Froyo as it's built. I'm sure once it's ready for primetime, they will then complete the port of it over to the AT&T variant as well which won't require too much modification.

[Krak-a-Lakn]

AT&T has no say in the firmware going to the N1. The only thing associating the phone with AT&T is that the model in reference includes support for their 3G bands. Since they do not offer official support nor do they sell it through themselves with subsidy, AT&T can hold no say in what gets pushed to it.

But yeah, definitely. If Google does it just simply to be on AT&T's good side, that would be messed up. But that would be Google's decision, not AT&T.

With AT&T charging $20/month for iPhone tethering, I just can't see them letting this slip by on the 2.2 update.

If somehow they do allow the tethering, it will be sooo much fun to rub it in on all the iPhone users I know.

[88 FLUX]

With AT&T charging $20/month for iPhone tethering, I just can't see them letting this slip by on the 2.2 update.

If somehow they do allow the tethering, it will be sooo much fun to rub it in on all the iPhone users I know.

IF 2.2 makes it's way to the Aria (or even the Backflip), I'd be willing to bet that there will be no built-in Froyo tethering due to it being blocked out at AT&T's request. But with the Nexus One, AT&T can complain all they want but they have no control over it since it's not under any of their control whatsoever. I'll give you another example:

Let's talk about the Nokia N95 (a phone which I had the pleasure of previously owning both variants of). Nokia produced and sold a version of both the N95 (the N95-3) and the N95 8GB (N95-4) that were fully compatible with AT&T due to them being both quadband GSM and triband UMTS on the frequencies that AT&T uses. However, AT&T never once sold the phone through their channels nor supplied official support. This is the exact same situation as the AT&T-banded Nexus One. If Nokia had chosen to add a feature to the N95 that included mobile hotspot service or something else that AT&T did not like, AT&T would have absolutely no say in it and there would be nothing that they could do because it was not their phone whatsoever. Same applies to the Nexus One.

In fact, not officially supporting it and offering subsidy is probably one of the worst mistakes they made regarding their Android offerings. Reason I say that is because the Nexus One is the type of Android device that those who want it are going to find a way to get it whether the carrier offers them a discount or not. By not just biting the bullet and offering it, they lost out of any chance of holding any control over what gets applied to the AT&T variant. But, based on the purpose of this phone on Google's project plans, they probably wouldn't have come to an official agreement anyways.

[XXXdc5]

Posting as a reminder to read op when I'm not driving.

Edit and update:

i completely agree and understand your frustration. I hate (with any form of technology) people that go around spreading information that is not true. ESPECIALLY when that false information then becomes widely accepted as fact. WE DONT NEED A FORM OF TMZ IN THE TECHNOLOGY WORLD!! haha. That is jst the way the world goes though when it comes to technology. These are the same people that will but the iphone 4 thinking that its a complete revolution, the first of its kind, not only having 4G but also a video chat feature that works everywhere whenever. (just an example. I know people that think this). People just need to get their stuff straight. The topic of the OP should be a post on the androidcentral home page.

I dont have a Nexus One but MAN did i wish i could get one when it first came out (im on Verizon) and if the official froyo came out on anything else first i would definitely be pissed.

[Simer03]

So FRF83 on a Tmobile Nexus One is STILL not the final build? hmmm...im not even mad though cuz at least we have froyo love, and updates are only gonna make it better!

[Jerry Hildenbrand]

opinion follows

FRF83 is final. But it was only intended as an update to holiday nexi that previously rec'd FRF50 or FRF72. No reliable reports of an Eclair to Froyo OTA yet.

Why do I say this? Because the official source for Froyo has been committed. It will not change, unless the version number changes (2.2 r2, etc). FRF83's build time and date is after the source was released. I built AOSP from the latest code, and apks are 100% interchangeable. So are framework and lib files. FRF83 is froyo.

What remains to be seen, and very likely what Google is testing on holiday nexi, is how Google bits works with the Froyo update. Once they are confident that they do not need to change any of the closed source Google apps, a full 2.2 build will be pushed out.

[88 FLUX]

opinion follows

FRF83 is final. But it was only intended as an update to holiday nexi that previously rec'd FRF50 or FRF72. No reliable reports of an Eclair to Froyo OTA yet.

Why do I say this? Because the official source for Froyo has been committed. It will not change, unless the version number changes (2.2 r2, etc). FRF83's build time and date is after the source was released. I built AOSP from the latest code, and apks are 100% interchangeable. So are framework and lib files. FRF83 is froyo.

What remains to be seen, and very likely what Google is testing on holiday nexi, is how Google bits works with the Froyo update. Once they are confident that they do not need to change any of the closed source Google apps, a full 2.2 build will be pushed out.

Thank you for clarifying that. I fully trust your word. I was just pointing out that there was no concrete proof provided in all of the spreading reports out there and that people were misinterpreting the situation. Which is why I said that FRF83 could very well be the official build. There just wasn't anything backing it up.

[icebike]

I was a rep for companies like HTC, Nokia and Samsung. The US is a small market on the scheme of things.

US=Small Market. Chuckle.



Admittedly there are only 48.81 handsets per 100 people in the US, but then the US had a late start and has best terrestrial phone system going in. Some places like Taiwan have 106 handsets for each 100 people.

[icebike]

What remains to be seen, and very likely what Google is testing on holiday nexi, is how Google bits works with the Froyo update.

What pray tell is "holiday nexi"?

[88 FLUX]

What pray tell is "holiday nexi"?

The holiday phones were the original Nexus One's given out to employees that sparked the initial viral leak of the phone. They are characterized by the lovely Andy waving a QR code on the back and (IIRC) have a relockable bootloader.

[Jerry Hildenbrand]

Thank you for clarifying that. I fully trust your word. I was just pointing out that there was no concrete proof provided in all of the spreading reports out there and that people were misinterpreting the situation. Which is why I said that FRF83 could very well be the official build. There just wasn't anything backing it up.

No, you're absolutely right. FRF83 is only an update to AOSP. "Googlebits" are as important, if not moreso, to the final build than the Android base is. We can't call anything official until Google gives a green light to the Google apps, puts everything together and tosses out a build that anyone can install.

Personally, I hope they make some adjustments. Things like having to clear cache on GMail, sign in and out of GTalk to get market downloads to work, etc. are annoying as hell and need some fixin'. I'll happily wait as long as the end result is good

[jasonpich]

Thank god somebody gets it. The blogosphere has been horrible about delivering this info. And it shows no sign of stopping any time soon.

Oh and something I reserve the right to complain about - if the next release doesn't fix the 3G radio issues on the nexus. I actually can't use my phone as a phone if I don't lock it to 2G. (T-Mobile, Jacksonville FL area)

So do I wisby.

[XXXdc5]

updated my post on number 12. sorry for the space waster LOL but hey its hard to read a post like this while in the middle of a 7 hour drive lol

[deecee52]

I agree 100% with the OP. but...
the viral dribble leading up to FRF83, and no viral breadcrumbs to ATT makes me nervous. I don't claim to understand software development, but simply porting it to ATT bands at the end seems well, late. Surely, someone at goog has rolled one up for the consumer AT&T experience.

Call me paranoid, but I keep feeling ATT is pressuring them in some way as is TM and we will be the losers. I so wanted this to be an unsubsidized world phone - beholden to no carrier, but that is another thread.

I'm not saying the ATT version or any other version should be leaked, but some reassurances from goog that they "are working to develop a common upgrade OTA path, to refine native apps, give developers time to refine their apps, creating a common, seamless, featurefull upgrade experience for all N1 users. We expect this rollout to be complete by the end of the 3rd quarter (or some late date so they can under promise and over deliver). Thank you for your support, etc...."

so as an ATT customer. I'll wait for the official OTA. I'll still grumble about the way this has been handled by google. I'll grumble about the mis information and poor reporting in the blogoshphere. I'll still be glad I have the N1. I'll hope that in the end the unlocked, unsubsidized n1s will be treated the same, get the release at the same time*, etc (and before the subsidized and branded phones -- okay, I want to brag -- and that google doesn't cave in/make deals with tm or att.

*I understand the roll-out will take days, but mix att and tm delivery. I never did like being the stepchild.

Okay, I guess this sounds like I am complaining!

[robsw]

Google already has confirmed in the Nexus One support forums that the official release will be the same for AT&T and T-Mobile.

[avengerbb#ac]

I agree 100% with the OP. but...
the viral dribble leading up to FRF83, and no viral breadcrumbs to ATT makes me nervous. I don't claim to understand software development, but simply porting it to ATT bands at the end seems well, late. Surely, someone at goog has rolled one up for the consumer AT&T experience.

Call me paranoid, but I keep feeling ATT is pressuring them in some way as is TM and we will be the losers. I so wanted this to be an unsubsidized world phone - beholden to no carrier, but that is another thread.

I'm not saying the ATT version or any other version should be leaked, but some reassurances from goog that they "are working to develop a common upgrade OTA path, to refine native apps, give developers time to refine their apps, creating a common, seamless, featurefull upgrade experience for all N1 users. We expect this rollout to be complete by the end of the 3rd quarter (or some late date so they can under promise and over deliver). Thank you for your support, etc...."

so as an ATT customer. I'll wait for the official OTA. I'll still grumble about the way this has been handled by google. I'll grumble about the mis information and poor reporting in the blogoshphere. I'll still be glad I have the N1. I'll hope that in the end the unlocked, unsubsidized n1s will be treated the same, get the release at the same time*, etc (and before the subsidized and branded phones -- okay, I want to brag -- and that google doesn't cave in/make deals with tm or att.

*I understand the roll-out will take days, but mix att and tm delivery. I never did like being the stepchild.

Okay, I guess this sounds like I am complaining!

There are people with AT&T versions that have received the update. There's just not enough of them that someone new to capture the link. I don't have time to find the link right now, but one of them posted video proof to youtube.

[Krak-a-Lakn]

There are people with AT&T versions that have received the update. There's just not enough of them that someone new to capture the link. I don't have time to find the link right now, but one of them posted video proof to youtube.

This the first I have heard of this. If true, this would indicate that contrary to my gut instinct, that AT&T will not delay the OTA update.
However, I searched YouTube and only found AT&T 2.2 demos on rooted phones.

It would be greatly appreciated if you could find the original link to the video you mentioned.