yashsingh1/xdaforums huggingface dataset:
[Nexus One General] princeasi:
For those with att N1's, i wouldnt be so quick to root and install the unofficial froyo. I would advise to wait and see if the official OTA addresses the touchscreen issue. This problem has existed for over 6 months. If the new update doesnt fix this, it would be safe to say that its an hardware problem. If this be the case, you would want to be in position to flex your warranty power without any lashback from HTC/Google. There's a reason why google is taking so long to up 2.2. They might be having a hard time ironing out or producing a work-around solution to some of the bugs plaguing this unit! Be careful fellow XDAian!
[Nexus One General] PacoL250:
Specifically what touchscreen issue? You talking about the issue where there feels like there's sticking when typing? If so, I had my phone warrantied out the second week I had it to take care of that and the replacement has barely shown any issues with that. Some rare times it comes up, but not often.
[Nexus One General] GldRush98:
Uh, what touchscreen issue? I have no problems.
[Nexus One General] McHale:
They're not writing software to cure cancer here, it's a stupid phone OS where they have the ability to send OTA updates daily if they want. The fact that they refuse to release something when it's CLEARLY better than the stock 2.1 is simply a matter of making other vendors happy. It's similar to why they didn't release the N1 for Verizon - they didn't want anything to get in the way of Verizon's sales of their top Android devices. I'm pretty sure they will release it just about when everybody else releases it so it doesn't affect their sales.

-Mc
[Nexus One General] princeasi:
This problem here http://www.youtube.com/watch?v=_JCSEnkntEI I have this exact same problem with mine and many others have as well! This shouldnt be happening "sometime" it shouldnt be happening at all! I'm hoping Froyo addresses this issue!
[Nexus One General] :
Maybe that's what taking so long?

That'll be one hell of a feature set.
[Nexus One General] jatinps:
^^ mchale completely agree - google cares more about android acceptability than its nexus one base. They can hold the OTA now and win brownie points with carriers/manufacturers and thats all they are doing frf83 or frf86 does not really matter. They can just release frf83 as 2.2 now and then release frf86 as 2.2update1. We are still better off than being stuck on ere27 with no real exchange support.
[Nexus One General] McHale:
DAMMIT! They're copying the iPhone again!

GRRRRRR!!!!!!!!!!
[Nexus One General] kwonger:
Google Still Testing Froyo Builds; FRF83 Not Final Release

...says androidguys.com

"Today, a source inside Google let us know that Froyo builds for the Nexus One are still in testing, and that at least one build numbered higher than FRF83 has been OTA'd to a small testing group."
[Nexus One General] jatinps:
some news from the google forum

http://blogs.computerworld.com/16414/froyo_ota_rollout?source=rss_blogs

so the ota did happen and then it was pulled off!
[Nexus One General] McHale:
man, it just gets weirder and weirder since "inside sources" claim that FRF83 is not the final OTA.

ugh...

Luckily, I'll be gone tonight and tomorrow so when I return tomorrow night, maybe this'll all be a bad dream.

-Mc
[Nexus One General] j.bruha:
Haha, I hope it bothers you as dramatically as you make it sound.

Dude, go outside for a bit. It's not the end of the world.
[Nexus One General] ohgood:
please don't change your signature. it helps me weed out the comments that are meaningless. :)
[Nexus One General] McHale:
ironically, no. The Nexus One isn't my primary phone. Hell, I also have an iPhone 3GS (which has NEVER had an active SIM card in it), a CDMA Touch Pro 2 (on a carrier I don't have an account with) and a ton of other phones. As stated previously, the Nexus One is just a test platform for me. I *WOULD* like to get 2.2 on it so I can test the Exchange stuff so I can see if it meets the security requirements for work, but other than that this whole debacle is almost observational humor.
[Nexus One General] xguntherc:
Yea i think FRF83 was another incremental update just like FRF72. Thats why it was like 1.78mb or whatever. The entire build should be bigger than that and we'll probably get a larger file here soon.
[Nexus One General] McHale:
Google Still Testing Froyo Builds; FRF83 Not Final Release
[Nexus One General] :
Probably experimental build testing for a possible ".1" upgrade between now and Gingerbread.
[Nexus One General] player911:
FRF83 Issues

Hey guys. I just flashed FRF50->FRF83 and I'm finding that I can't access webpages over a 3G connection.

I checked *#*#4636#*#* and it is set to WCDMA PERFERRED.

If I change it to GSM ONLY, internet works. WCDMA ONLY and WCDMA PERFERRED doesn't. I DO see the 3G and I have almost full signal. I've reset and pulled the battery and everything I can think of... but no go.

Right now I have it set to GSM ONLY which is EDGE. I'm getting a whopping 70kpbs download stream from SpeedTest app. Any suggestions other then, your using a beta so expect problem?
[Nexus One General] McHale:
There are a lot of people who have done the upgrade that you performed and everybody seems to be good for data.

2 questions: Is it possible there's a 3G outage in your area and have your power cycled your phone?
[Nexus One General] player911:
Yea that was the first thing I've done. I even pulled the battery, removed the sim, powered cycled a few times, went in and out of airplane mode, and nothing.

Perhaps they are upgrading us to HSDPA because when I connect to 3G, in the *#*#4636#*#* menu, when I do a PING TEST, it initially comes up as HSDPA then refreshes back to UTMS after a few seconds... unless that is normal. My gf has a 3G android phone and she hasn't mentioned any issues about data.

When I flashed FRF83, I was in a EDGE only area. I flew home around 1am last night and hit the sack. I noticed it said 3G and I did test to make sure my wireless is good. Everything is great except data while on 3G.
[Nexus One General] :
Probably tower upgrades, give it a few hours and try again.
[Nexus One General] dudebro:
I've had this problem with my phone for quite some time and was stuck on EDGE for a long time.

was hoping it was tower upgrades but still the same results when on 3G.

got a replacement and it still persists although I'm never on EDGE anymore.

HSDPA is the only way I can use data but not 3G, the up arrow just stays lit and eventually switches to H and data works again.
[Nexus One General] GragDroid:
android is never final :D so keep cool :cool:
[Nexus One General] mr_notorious:
Latest build is FRF85B.
[Nexus One General] spamlucal:
here we go again xd
[Nexus One General] mik3l04:
If that's true, given that the current AT&T version is EPE54B, note the "B", any thoughts on if this could be the elusive version for those of us not on the Tmo version?

Pure speculation but here's hoping.
[Nexus One General] mr_notorious:
No, I use my Nexus for GV calls only (in conjunction with SIPdroid), I don't have a provider. If anything, B stands for Beta.

All I can tell you guys is that Google will be pushing Froyo to the public mid next week.
[Nexus One General] player911:
Yea it is up and down, even on my gf's phone. HSDPA shows steady but doesn't work yet. Perhaps we're finally getting upgrades.

I did have a look into my APN settings and found the proxy and a few settings were off or not set (although EDGE was working). So I'm not quite sure the APN was the problem.
[Nexus One General] :
They started moving builds on the weekend? Interesting
[Nexus One General] jatinps:
There we go - frf85b :)

FRF83 cant be final as I realized that frf83 does not have something critical - corporate address list (GAL) - which is stated as deliverables in 2.2.

Here is my message on the google code issue

"I'm on android 2.2 build frf83 and can't find any way to get to gal. Yes I do see my personal contacts from outlook but there is no way to search the global address list. My organisation has 80000 employees and this is a showstopper. To summarize no gal function in build frf83(unless someone can point me to how to do it) and can't find this so called corporate directory app from Motorola in marketplace. I'm on nexus one stock. "

http://code.google.com/p/android/issues/detail?id=4602

http://code.google.com/p/android/issues/detail?id=8536
[Nexus One General] :
So i just realized there would be four builds of froyo had thecdma versions of the nexus come to fruition. Lol
[Nexus One General] MENDEH:
i hope you are right :eek:
[Nexus One General] :
B stands for Revision B (as in nexus att is nexus (b), t-mobile is neuxs)
[Nexus One General] antikryst:
hopefully final build has the multitouch keyboard like the droid x
[Nexus One General] MENDEH:
i thought that was something moto did on their own?
[Nexus One General] :
Anybody on frf50, try checkin?
[Nexus One General] antikryst:
heres hoping. at least we know its really possible.
[Nexus One General] mr_notorious:
Google probably pushed it on Friday. I didn't check the phone since a few hours ago.
[Nexus One General] mik3l04:
@mr_notorious

Can you share the link for your build or no logcat?
[Nexus One General] :
Pretty sure OTA servers are back up.

Checkin guys. =D
[Nexus One General] jakelauer:
What is supposed to happen after checking in? I just tried it, got checkin success, but so far nothing else has changed.
[Nexus One General] jatinps:
^^ what do you mean by servers are back up - I could checkin successfully everyday for the last 3 days (once every few hrs :) ) so as per me the servers never really went down!
[Nexus One General] clickwir:
FRF72 here. Just did a checkin. Nothing special.

Oh, I did change my background. http://www.icanhasinternets.com/wp-content/uploads/2010/06/popicon421.jpg

That's more news than we got on Froyo. :p:p
[Nexus One General] :
I just tried a frf50-frf83 link and it worded successfully, I was under the impression ALL update links were closed off while their servers were "undergoing maintenance" as they stated earlier.
[Nexus One General] McHale:
According to Google (and as seen by the couple of people who got the FRF83 legitimately), the builds for the T-Mobile and AT&T variants are supposed to be the exact same version.

And if the rumor is correct that the rev number is based on days, the B could simply mean it was the second build during that day.
[Nexus One General] naturefreak85:
Where did google say that about the builds being identical.? I don't remember reading anything from Google on that topic.
[Nexus One General] McHale:
Google Employee Ben1010 wrote on 5/25

"Hi everyone,

The update to Froyo / 2.2 is the same for both T-Mobile and AT&T versions of the Nexus One, so all of you should receive it over-the-air (OTA) at around the same time.

Cheers,

Ben"

http://www.google.com/support/forum/p/android/thread?tid=6fe002a637858b44&hl=en
[Nexus One General] naturefreak85:
So with that being said, how can people think the updates would come out at separate times? (like months apart)
[Nexus One General] Clarkster:
Because they are either trolling, or are so 'hurt' by Google that they are lashing out? I don't understand it. It's just an update, let them get the bugs worked out.
[Nexus One General] :
Two builds can have the same feature set and be released at different times.

The two nexus phones, while nearly identical, have to be tuned for different frequencies. (as can be seen by the two different radios for 2.1 nexii).

Att and T-mobile nexii with 2.1 r 1 have different build numbers but they share the same feature set, with slightly updated AOSP code.

The FRF85B is probably just the port of the FRF83 being tweaked for the different radio.
[Nexus One General] McHale:
The radio code is confirmed identical same for both the AT&T and T-Mobile. There are a LOT of people running the leaked Froyo radio on AT&T and T-Mobile devices.
[Nexus One General] ROBIN50N:
google are doing a sterling job in stopping fragmentation.

cant even sort it out on a single model.
[Nexus One General] AvengerBB:
Everything is speculation until it's officially released.
[Nexus One General] ROBIN50N:
true. its just been uncertainty for nearly a month.

they should just say whats happening.
[Nexus One General] :
Oh I know, I was using that as an example. We don't know if the att froyo update will include a different radio or not though.

Chances are though, that it will have a different radio. Just because a radio works, doesn't mean it's optimized.
[Nexus One General] McHale:
POSSIBLE but not likely given HTC's track record of radios. In fact, I can't think of a single HTC model since their first phone that regardless of frequency bands, one radio doesn't work for all versions of the same model (and other models). And I'm pretty sure I read on one of the XDA forums that the Nexus One radio was coded specifically to work on both.

It's not impossible, but just doesn't follow HTC's history. I'm *REALLY* hoping that all the Nexus One's will be on the exact same revision starting with Froyo just to end the hassle of updates.
[Nexus One General] mr_notorious:
The difference between FRF83 and FRF85B is bug fixes and further optimizations.
[Nexus One General] McHale:
hmmmm... just noticed in your tag that you're running FRF85B. Gotta link?
[Nexus One General] :
How come no one asks for my halo halo build?

=*(
[Nexus One General] mik3l04:
Yeah I noticed that last night which is why I asked of he had a link to share. My request went unanswered and he is the only one that I've seen claiming to have that build. Not saying he is lying but would love to have seen the logcat of his update.
[Nexus One General] mr_notorious:
No can do for that link. Sorry. But I was told if all testing passes, Google will push public mid next week, but no promises.

If you want to know if I am legit or not, just look at my old posts. I got the Nexus 1 month before it went public (the one with the Android holding a barcode flag).
[Nexus One General] McHale:
I have not seen a single other person mention 85B and I'm pretty sure he's telling the truth. First, he didn't say "I think..." or "I read that..." so he is pretty confident. Second, he didn't say 85 he said 85B. People just don't randomly tack on additional numbers or letters. :)

I have no doubt he's running it. And since FRF85B was released to a very select group of people, I may need to keep an eye on his posts. :)

EDIT: NP on the link. Never hurts to ask around this place. :) I *AM* jealous as hell though...
[Nexus One General] mik3l04:
Yep.. I do think you are legit but what does my opinion matter :)

Just out of curiosity was it an incremental update from 83? Just trying to find out if it was a build compatible with EPE54B. I know the comments have all stated that the official update will work on both but the fact that not a single update has been leaked for the 54B build makes me seriously doubt that. Any insider info on that?

I can wait for however long it takes for official but if when it does come out there is no upgrade path for EPE54B then I just might lose it. If I knew that would be the case I would just go ahead and root now and be done with this whole fiasco.
[Nexus One General] mr_notorious:
I wasn't in the test group until now. My Froyo update came directly from ERE27 to FRF85B. It was approx. 45MB update.
[Nexus One General] princeasi:
so far have you experienced the touchscreen issue with your current build???
[Nexus One General] player911:
The problem was with the Towers. I called Tmobile and setup a ticket with the engineer to work on the problem. Had nothing to do with Froyo.

But with FRF83, I just got a Facebook notification and my trackball light was blue using Bloo. Never seen that before. Are trackball notification colors apart of the update?
[Nexus One General] :
Trackball colors are a setting that developers can put inside the notifications settings if they so choose. The setting has been around since january.
[Nexus One General] vomer:
Would you know if the GSM N1 will get the update at the same time as the CDMA one? :confused:
[Nexus One General] MTGap:
I don't think there is a CDMA Nexus One... I believe it was canceled.
[Nexus One General] vomer:
Sorry, meant the AWS one...(T mobile etc).
[Nexus One General] tekrhino:
I'm new here guys so please go easy on me.

Found this in another Forum: About how to set your Radio to USA only Bands.

==========================================================

Nexus One--> Nexus One Q&A3G --> H Data problems

Setting your Radio to USA Bands only.

1) Go into the "Phone Dialer" Enter *#*#4636#*#*

2) Then select "Phone Info"

3) Then select "Select Radio Band"

3) Then select "USA Band"

4) Press Back a few times to exit.

5) Your phone is now only trying to use USA bands.

=========================================================

Ok so, I couldn't get past step three because there was no "Select Radio Band"

BUT I did find a pop down window that gave me a choice to "SET PREFERRED NETWORK TYPE:" the options were "WCDMA Prefered, GSM Only, WCDMA Only, GSM Auto (PRL), CDMA Auto (PRL), CDMA Only, EvDo Only, GSM/CDMA Auto (PRL), Unknown."

I have my Nexus One Un-Rooted Via T-Mobile w/FRF83 updated manually so I'm just curious to know if I set that preference to CDMA would I be able to use my T-Mo GoNexOne on the Verizon Network if I swapped SIMS and set the preference to CDMA?

Right now its set to "WCDMA Prefered" and I never changed it.

:confused:
[Nexus One General] Mokurex:
@tekrhino No.
[Nexus One General] degs:
I haven't been able to catch an OTA since I got my n1. I have always had to do it manually.

I just did the manual update to FRF83 and now my google contacts won't sync. All other syncing to my gmail account works just fine but the sync spinning arrows stop spinning for contacts and my contacts list is empty since updating. Any ideas?

<edit> Sync issue fixed. I was able to get contacts to sync after a few resets. Startup is a lot longer on FRF83 too.
[Nexus One General] snijper:
Nexus One Vodafone Nederland EPF30

Is there anybody knows..when froyo 2.2 OTA update will come to nexus one vodafone...or howto manually update EPF30 to Froyo..
[Nexus One General] dan1431:
It is my understanding that Nexus Ones will receive Android 2.2 regardless of mobile provider.

Dan
[Nexus One General] KidTech:
Why is it taking google so long to send out the OTA.. Would i have to change WCDMA perffered, to get this OTA?
[Nexus One General] :
Because it's not finished testing?
[Nexus One General] MENDEH:
there are reports of droids getting a test froyo build now. if Google doesn't hurry up Motorola is going to beat them at their own game.
[Nexus One General] arcticreaver:
been waiting for froyo for like a month now. c'mon google!
[Nexus One General] SoberGuy:
Moto will beat Google by releasing a crappy ass version of Android 2.2? Riiiiiiiight. I'd rather get 2.2 two weeks after Moto, just to not have the Moto crap on it.

EDIT: And besides, how long have 2.2 test builds been going out on the N1? I'd expect it to take Moto at least a month to finalize their build.
[Nexus One General] :
The droid as been in testing side by side this entire time in regards to 2.2.

They'll probably end up with a later build number probably week apart from N1.
[Nexus One General] SoberGuy:
Interesting. I did not know. Thanks for the correction.
[Nexus One General] mattinglis:
Im am quite happy patiently waiting for the official OTA, but i cant help feeling google have scored a horrendous own goal with the whole froyo announcement thing.

I feel sorry for those people that google have pursueded to buy a nexus one after the promise of froyo in weeks, this was quite blatantly an attempt to steal custom and headlines from the forthcoming apple iphone4 announcement.

In the end they have both shot themselves in the foot trying to roll out stuff they havent prepaired properly before committing to release it. Google in that froyo obviously wasnt ready or tested properly and apple as in they didnt bother testing the phone in their left hand lol.

However at least google havent released their software half arsed unlike apple. They have just rattled a lot of folks.
[Nexus One General] Erigion:
I'm not at all surprised at the time it's taken Google to officially release Froyo. I'm pretty sure if Google could they would have slapped "Beta" on Android 1.5-2.0 a la any number of their other products, hell maybe they would have kept it around for 2.1 as well.

If people haven't learned by now that Google will release things when they want to I think they'll continue to be disappointed in Google.
[Nexus One General] nexusdue:
Agree on Google shooting themselves in the foot with how they handled this update. I know a lot of devs that are royally pi$$ed off at how google is handling the update cycle and might stop developing for android because of it.

People want a reliable timetable, when updates happen and what gets changed, so that they can prepare for it.

Coming from a WM device to Android/N1, I can't help but feel that 2.1 is very much a "beta" version.
[Nexus One General] jatinps:
well this has been doing the rounds on the google forum :)

FRF83->FRF85B

http://android.clients.google.com/packages/passion/signed-passion-FRF85B-from-FRF83.f62ffd2b.zip
[Nexus One General] imfloflo:
Thanks for the link
[Nexus One General] texas-saluki:
AT&T Froyo Update Files??

Mr Notorious can you post the file for the OTA update? It should be in the log file.
[Nexus One General] Zynon:
http://android.clients.google.com/packages/passion/signed-passion-FRF85B-from-EPE54B.75b107d6.zip

Supposed AT&T OTA. See other thread for info.

Sent from my Nexus One
[Nexus One General] :
the froyo release cycle has nothing to do with app development. the sdk has been out since may 19th

there are only two official updates for froyo and thats the SDK and code drop....both are done
[Nexus One General] :
Lazy developers are lazy.

shock. awe.
[Nexus One General] crutis:
Out in the cold on FRF72

Won't flash over FRF72 for me.

Anyone else stranded on FRF72?
[Nexus One General] :
Go up to 83 the to 85
[Nexus One General] crutis:
Correct me if I'm wrong, but there's no 72 -> 83 ROM.
[Nexus One General] SBS_:
Here it is:

http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF72.684bd56a.zip

That one only works on stock recovery of course.
[Nexus One General] crutis:
Just what I needed. THANKS!
[Nexus One General] Erigion:
Are you kidding me? I came from an AT&T Tilt running WM6.5 and it was a POS, it rebooted itself multiple times every day until I slapped a custom ROM on it and even then it was barely tolerable. The ONLY thing that WM6.5 had on Android was better Exchange support which I no longer need since the N1 syncs will everything Google.
[Nexus One General] n4s720:
I tried flashing that over the FRF72 and it just sat at the screen with the white triangle and the android.

That is, the FRF72-FRF83 from the link posted above.

I couldn't quote because it wouldn't let new posters post links without mod approval.
[Nexus One General] PeRRiiN:
FRF85B IS THE OFFICIAL FROYO UPDATE!

Google announced it and its on Android Central too.
[Nexus One General] slowz3r:
Official Google Announcement
[Nexus One General] :
Lol, just like Google to link to the developer site to highlight the new features for their retail product. haha
[Nexus One General] geemaan:
We should be thankful they're not driven by some greedy marketing people. they're still a sw company ;)
[Nexus One General] EwanG:
Which other thread, and does it include instructions for us newbies? :-)
[Nexus One General] vomer:
http://xdaforums.com/showthread.php?t=712983
[Nexus One General] pandabear:
please let me know if you find a compatible froyo motogal.apk, thanks!
[Nexus One General] apollostees:
:(Guess I'll be waiting for cm6
[Nexus One General] phocusrs:
Yes wise decision to wait for the CM6... Thank you anyway for the buzz... more than 60 post within less than 12 minutes...:)
[Nexus One General] attn1:
the rom will have to be repacked so that it flashes.
[Nexus One General] attn1:
Got logcat?