Database Develop

Is Froyo (FRF50) official - or just an "accident"?

I have updated my stock 2.1 N1 to Froyo (Build FRF50) manually. I'm wondering, though, if this release is really meant to be the official, final Google-supported update.
Is there any word from Google (except for MG Siegler's "The roll out to Nexus One devices has begun!" over at Seeking Alpha) that this is the one?

Same question here. Also if this turns out to be a pre released update, can the stock N1 be updated to a official version?

from what i understand there is no actual official word. That said im loving froyo: As with previous updates, froyo added features and bug fixes and also brought some new issues, so if you are thinking maybe its not official because of some bugs, to me that wouldnt be sufficient evidence: I havent experienced any of the complaints save one- Anyone else having the phone randomly go to sleep and not wake up?
The scrolling,
updated native apps (youtube is amazing now),
overall speed increase,
awesome camera/camcorder updates,
very smooth BETA flash,
simple and effective tethering,
fantastic new setting options throughout the OS,
left AND right rotating
updated UI (love the phone/app drawr/ browser buttons)
and im sure im forgetting stuff...All extremely awesome features and my personal new issues of freezing and hard sleep i can live with i just hope they arent harmful.

i't doesn't feel like a complete FroYo. I have little bugs that i noticed. screen goes black and don't go on anymore, have to take out battery. When the phone is in the charger and i'm playing with it, It gets really really hot.
The new features are great i miss some CM tweaks The UI was a little different at the IO so maybe there will be more surprises?

this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update

jdmoore81 said:
this was a prerelease to the developer holiday phone the official is coming out around the 29th of may and will continue to roll out till all nexus ones have the update
Click to expand...
Click to collapse
How do you know this? also will we get that update too?

Well the "leaked" URL was pulled, wasn't it?

this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.

Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.

Wouldn't bother me any if this was the official ... its flawless for me. No freezes or any wierd stuff. Pure froyoness

m00moo said:
this was very likely to be a pre test release. I've looked into the build.prop and there are signs that it is a test release as the word test appears several times throughout.
Click to expand...
Click to collapse
Thnx for the info, so this is a test version. felt that way
Rusty! said:
Given the silence from Google, and the subsequent removal of the link, I suspect this was an accident... meant it to go to a select few whilst forgetting how easy it was to distribute the location of the update.zip.
Click to expand...
Click to collapse
So the link is gone than it's definitely a accident.

I'm gonna say this ain't the final release. But I doubt it'll be any diff. How much more could they fix or improve from the accidental release to the real one.... I bet the same bugs people are seeing now will be present in the final...
Nothing's perfect
Except for me.lol no issues

oh dear... not so good if this is true!
I spose people on here flashed the update.zips from xda?
Hopefully Google will push out the live update now certainly with the potential problems people could be getting

No, I flashed with the file direct from Google before the link was pulled.

So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?

No stock AT&T/Vodafone customer can get it yet.

Zenoran said:
So it's all over the news Nexus has froyo now but has anyone with a legit locked stock phone actually gotten it? Like one of the ATT folks?
Anyone have any links to some real clarification on this?
Click to expand...
Click to collapse
No, I am one of the many AT&T folks that is still waiting for the official release from Google. I have a 3 week old N1 that is still stock and with locked boot loader, and I have no problems waiting, as I am not ready to root my new N1 just yet.

the official will we the frf86 as seen in a couple threads this version will work fine for the holiday version of the nexus one . i tried it on both the holiday nexus one and the official release of the nexus one and it runs better for some reason on the holiday version

Where are you getting all the info from?
Is there likely to be much added between FRF50 and FRF86?

How SO we know if its a holiday one?

[ROM] Final Froyo Release for Obsidian by CCRoms V2.02 Next Up Gingerbread

Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.

sniffle said:
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
Click to expand...
Click to collapse
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?

Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?

avlfive said:
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
Click to expand...
Click to collapse
No they are not. It shows all the known issues from the dl link posted above

bravo1234 said:
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Click to expand...
Click to collapse
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.

joebob296 said:
No they are not. It shows all the known issues from the dl link posted above
Click to expand...
Click to collapse
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.

avlfive said:
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
Click to expand...
Click to collapse
Those are all a must for me at least
Sent from my DROIDX using XDA App

I don't understand the gps issue or the camera issue. If there was fine GPS and a camera i would love the fact it is AOSP however not that i use them all that often but if i loaded it i would inevitably need one or both. and its still beta if you can't get a totally stable and working froyo rom how will you ever get the GB stable. Will the kexec(?) be used to use custom kernels to make the gps and camera work?

I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App

Funnyface19 said:
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same here. it's been reported in other obsidian forums too. i was able to get around it by using an older version of market. i installed cm gapps instead of obsidian gapps. The cm gapps had a version of market from 2 month ago. everything worked fine. then i updated my market to 2.2.11 and the "There's not enough room..." error message was right back again.
other than that, i really love how clean and fast this rom is. thanks a ton cvpcs and best of luck with the cyanogenmod team.

any pics of the drop down toggles???

tttuning said:
any pics of the drop down toggles???
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=RbKJy6MPUz0

cvpcs said:
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
Click to expand...
Click to collapse
what...? What!? That is completely wrong... Nothing says you have to upgrade the kernel... unless Gingerbread uses modules not currently in the present kernel, which I can pretty much guarantee it will... Your statement could hold true for something such as minor update like 2.2 to 2.2.1 as we saw earlier, but would very like cause many things to not work come gingerbread. A good example is the previous hacked upgrades of 2.1 to 2.2 back before the proper kernels were released (specifically in memory of the HTC Incredible) sure, 2.2 could run without the proper kernel, of course your WiFi wouldn't work, GPS didn't work, if you tried to run the 720p camera it would crash, as well as several others that I cannot remember as of this moment. The kernel is not "just a low level piece of software" it is the backbone of your entire system, especially when it comes to the system talking with the hardware itself.

I think Taco that you should reread CVPS post. It stated this...
"nothing says that when you upgrade an android version you MUST upgrade the kernel as well"
Which is what you said was wrong, then said the same thing following it.

So how is the rom working for everyone? or it's pretty much dead..

ram130 said:
So how is the rom working for everyone? or it's pretty much dead..
Click to expand...
Click to collapse
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.

JagoX said:
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
Click to expand...
Click to collapse
Well that sucks ..development on this phone is so slow..

The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App

ksizzle9 said:
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
The X development has all but ceased from what I can see. Such a bummer since I'm stuck with it for another year and a half. Hopefully we can see a few updates to some ROMs once gingerbread rolls around for the phone, but after that I don't see much reason for hope.

True...so what was the most annoying issue with this rom? Im thinking about flashing it. Im on 3.4.2 now.
Also you can sell your DX on swappa.com then pay the difference and get a htc.

When are we get gingerbread back??

I haven't even heard any rumors about expected re-release date for gingerbread.
I was sure we were gonna get our gb back within two to three weeks, but my faith is fading very rapidly now.
Some people are expecting mid-May for re-release.
What you guys reckon?

I reckon G00glez took their G1ng3rbr3ads back and are not going to release it again until 24 hours goes by without someone creating a thread and asking about it.
In all honesties, I'm patient as long as it's rock solid.

it's pulled buy google so i think it's because of patent infringements

Naeem786 said:
it's pulled buy google so i think it's because of patent infringements
Click to expand...
Click to collapse
Patent Infringements? Seriously?
Unless there is a court order restraining Google from distributing Android, which there is NOT nor will there be in the future in my opinion, there is no way they would have pulled the release based on patent issues, which are never ending anyway for all companies these days. Also, GB HAS been released for other devices, including the Nexus S.
I would say it is far more likely to have been due to carrier integration problems, or that they recalled it to fix a relatively minor issue, such as the camera fix that was rumored, and the fix ended up breaking something else, and fixing that killed the wifi and so on and so on.
As it is JVB seemed a bit underdone for a final release. Hopefully we will get a better version all around, once they get around to putting it back in Kies. Could happen tomorrow, could happen next month....who knows. In the mean time, several of the custom versions are maturing nicely and the Kitchen is soon to move GB from beta to mainstream...so be happy and try those.

Samsung apps is offering an update. No serious change, but might be a sign for rerelease.
Sent from my GT-I9000 using XDA App

Naeem786 said:
it was pulled by google
Click to expand...
Click to collapse
AFAIK that was debunked.

Nobody knows
I haven't heard any truly plausible reasons for taking Gingerbread of Kies again. I am currently running the Kies version (JVB) of Gingerbread and compared to the earlier Samsung releases the JVB is a dream to run on.
Yes there may be bugs in it, though I personally haven't run into to any yet, but all of the official realeses I have run so far, has had bugs in them, so no change there.
The only reason I can see to hold it back is that they are waiting until the SGS2 to come to market, so they don't have to compete with there own product.
Thats my two cents.

Small update
I can tell you that the official release date of the SGS2 from one of the major carriers in denmark (TDC) is week 19 (the 9th to the 15th of may), which accidentally coinsides with the releasedate of branded Gingerbread on the SGS in Scandinavia.
Sources are here (This will give you a chance to work on your danish ) :
http://forum.tdc.dk/t5/Mobil/Samsung-Galaxy-S-II-hos-TDC/m-p/36167
http://forum.tdc.dk/t5/Mobil/Samsung-Galaxy-S-opdatering-til-Android-2-2-1-hvorn%C3%A5r-kan-det/m-p/35897#M3499

It returns on a Tuesday .
jje

Hopefully they get rid of touchwiz

Wesp1024 said:
Hopefully they get rid of touchwiz
Click to expand...
Click to collapse
Get rid of Touchwiz and i get rid of SGS .
jje

2.3.4 is out so maybe that's the primary reason it was pulled... Will it return as 2.3.4?
**Simply Honey 3.0, UltimateGB beta7 kernel, JQ1 modem**

I have a feeling we'll see it as 2.3.4 with TW4

[ROM][NIGHTLY] CyanogenMod 7 Nightlies Discussion

CyanogenMod for the Vibrant currently contains intermittent issues with the emergency dialing system. I strongly urge you NOT to use CyanogenMod on the Vibrant until they can be fixed.
Help by testing a test CM9 build for it​

awesome! nice to have you as "The bringer of CyanogenMod", if it wasn't for this great community, vibrant would be dead!

I know you aren't in charge of these things Fault but any idea when we'll get a new nightly?

jvpde said:
I know you aren't in charge of these things Fault but any idea when we'll get a new nightly?
Click to expand...
Click to collapse
By the looks of it, we might get one tonight.
http://jenkins.cyanogenmod.com/job/android/

The latest nightly link seems down. Would someone else confirm?
Sent from my SPH-D710 using Tapatalk

Working atm

I don't even know who the specific cm7 vibrantmtd mantainer is (if any), that's why I asked if the project had been declared dead. No sign of activity since late February, while other phones have been getting constantly updated nightly builds. There will be a reason for sure.

°_° The OP guy is the maintainer, and we will have cm7 nightlies either this week or next. Cm servers are being upgraded...
Sent from my T959 using XDA

flapane said:
I don't even know who the specific cm7 vibrantmtd mantainer is (if any), that's why I asked if the project had been declared dead. No sign of activity since late February, while other phones have been getting constantly updated nightly builds. There will be a reason for sure.
Click to expand...
Click to collapse
Glacier hasn't had any since ours.
Captivate has had 1 since ours.
Fascinate hasn't had any since ours.
Galaxy S hasn't had any since Feb 16th.
It doesn't mean that it's dead...

does this mean what i think it means
cm: Tag 7.2.0-RC1​
looks like cm7/gingerbread is reaching its ripeness!

akfelipe said:
does this mean what i think it means
cm: Tag 7.2.0-RC1​
looks like cm7/gingerbread is reaching its ripeness!
Click to expand...
Click to collapse
It still lacks proper TV out (no hardware decoding). And I'm not sure whether the mute/unmute bug has been solved or even whether the GPS is truly functional... apart from those, yep, the ROM seems quite stable...

O never really use TV out or GPS so I wouldn't know, but the mute/unmute should be fixed by now,
the mainteiner is that one who deals with device specific bugs...ask him what's the status with those two.
Sent from my T959 using XDA

akfelipe said:
O never really use TV out or GPS so I wouldn't know, but the mute/unmute should be fixed by now,
the mainteiner is that one who deals with device specific bugs...ask him what's the status with those two.
Sent from my T959 using XDA
Click to expand...
Click to collapse
I'm not sure if the mute-unmute bug is localized to Vibrant. (The changelog was copied from Captivate, which said the mute-unmute was hopefully fixed, Galaxy S also says it.)
(I'm not saying I won't I'll look into it though)
The mute-unmute bug is not fixed. I don't know about TV out, my cable is faulty. raymonddull tested it for me, he got black and white, which is more than I got, but his cable was faulty too!
GPS is most likely poo. Just flash YAGF2 or what ever works for you.

update-cm-7-20120226-NIGHTLY-vibrantmtd. Never work on my vibrant cause of the systemUI error. Are they going to build another nightly or is this the end of the nightly build?

FaultException said:
I'm not sure if the mute-unmute bug is localized to Vibrant. (The changelog was copied from Captivate, which said the mute-unmute was hopefully fixed, Galaxy S also says it.)
(I'm not saying I won't I'll look into it though)
The mute-unmute bug is not fixed. I don't know about TV out, my cable is faulty. raymonddull tested it for me, he got black and white, which is more than I got, but his cable was faulty too!
GPS is most likely poo. Just flash YAGF2 or what ever works for you.
Click to expand...
Click to collapse
TV out works but only partially. Its quality is worse than Froyo's (Samsung's official) and it shows a black screen when someone tries to play a hardware accelerated video.
The mute/unmute bug most of the times is there.
GPS may work to some, it won't to most and the fixes are hit or miss on equal measure. Personally I have last had my GPS working on Froyo days. I know it's not a big deal for most people here on XDA, but for the rest of the world (outside XDA) GPS is kind of a big deal and it's one of those modules that makes smartphones to be "smart"...
Anyhow the situation for CM7 (on our Vibrant) is about the same as in those GB ports from i9000; i.e. most things work, not all. If one needs the full experience of the phone *has to* go back to Froyo ... sadly.

Stevethegreat said:
TV out works but only partially. Its quality is worse than Froyo's (Samsung's official) and it shows a black screen when someone tries to play a hardware accelerated video.
The mute/unmute bug most of the times is there.
GPS may work to some, it won't to most and the fixes are hit or miss on equal measure. Personally I have last had my GPS working on Froyo days. I know it's not a big deal for most people here on XDA, but for the rest of the world (outside XDA) GPS is kind of a big deal and it's one of those modules that makes smartphones to be "smart"...
Anyhow the situation for CM7 (on our Vibrant) is about the same as in those GB ports from i9000; i.e. most things work, not all. If one needs the full experience of the phone *has to* go back to Froyo ... sadly.
Click to expand...
Click to collapse
Can you play hardware accelerated video on Froyo via TV out?

FaultException said:
Can you play hardware accelerated video on Froyo via TV out?
Click to expand...
Click to collapse
Yes, everything works on Froyo as intended... in fact because TV out is a feauture I often use (useful for presentations and such) I often have to go back to Froyo...

update-cm-7.2.0-RC1-vibrantmtd-signed.zip is up now on get.cm
Btw, anyone else not seeing "CyanogenMod Nightlies" in Premium Rom Manager? I used to, but it was quite some time ago.

ginzberg said:
update-cm-7.2.0-RC1-vibrantmtd-signed.zip is up now on get.cm
Btw, anyone else not seeing "CyanogenMod Nightlies" in Premium Rom Manager? I used to, but it was quite some time ago.
Click to expand...
Click to collapse
10char....

Mostdef said:
update-cm-7-20120226-NIGHTLY-vibrantmtd. Never work on my vibrant cause of the systemUI error. Are they going to build another nightly or is this the end of the nightly build?
Click to expand...
Click to collapse
New nightly cooking now: http://jenkins.cyanogenmod.com/job/android/304/
I'll start a build each night for one, until automatic nightlies are sorted out.
EDIT: Hmm, looks like there is a problem right now. I'll try again tomorrow.

[Q] Official 2.3.5 update. Will it experience ghost calls like O3D

I'm still on the 2.2 running Doom Froyo ROM. I want the update... but don't wanna get the ghost calls that I heard about from the O3D. Will the thrill experience it from this update?

faresr said:
I'm still on the 2.2 running Doom Froyo ROM. I want the update... but don't wanna get the ghost calls that I heard about from the O3D. Will the thrill experience it from this update?
Click to expand...
Click to collapse
I upgraded to the 2.3.5 from doomed froyo and it's working perfectly.

no problems for me

Thanks for the feedback guys. Appreciate it.
If in case you do experience it, will you guys post here and notify me?
Thanks

Is the battery life a little better with 2.3.5
Thanks.

obtained said:
I upgraded to the 2.3.5 from doomed froyo and it's working perfectly.
Click to expand...
Click to collapse
You didn't need to return to stock before updating??

LG Chat:
"Guest: Hi. The update for the trill to 2.3.5, i heard, has been released through the lg update tool.
Guest: I had a uestion about the reliability of the update
Ginno: I am sorry, but the release will be over the air through AT&T, they are being doing this since last night actually =)
Guest: Oh ok, thank you for notifying me.The Optimus 3D apparently received ghost calls after being updated. Will the thrill experience s
Guest: experience this* from the update?
Ginno: we have noticed that and we have reported to AT&T and they stated that as they have not complete the release then some devices may have issues
Ginno: or some inconveniences on the network
Ginno: but are working on that
Guest: So the thrill has this issue too?
Ginno: just momentarily
Guest: Ho safe would you say updating is? I would rather stick with froyo in this case
Ginno: oh no no, please do not get me wrong, this issue is because they were doing some maintenance at the same time while the update was released ok ?
Ginno: please do not worry
Ginno: \just give them a time to correct all the network
"
I am thoroughly confused... Horrible support

You may or may not get ghost calls. The reason is because it's 2.3.5
Apparently, 2.3.6 fixes that issue.

faresr said:
LG Chat:
"Guest: Hi. The update for the trill to 2.3.5, i heard, has been released through the lg update tool.
Guest: I had a uestion about the reliability of the update
Ginno: I am sorry, but the release will be over the air through AT&T, they are being doing this since last night actually =)
Guest: Oh ok, thank you for notifying me.The Optimus 3D apparently received ghost calls after being updated. Will the thrill experience s
Guest: experience this* from the update?
Ginno: we have noticed that and we have reported to AT&T and they stated that as they have not complete the release then some devices may have issues
Ginno: or some inconveniences on the network
Ginno: but are working on that
Guest: So the thrill has this issue too?
Ginno: just momentarily
Guest: Ho safe would you say updating is? I would rather stick with froyo in this case
Ginno: oh no no, please do not get me wrong, this issue is because they were doing some maintenance at the same time while the update was released ok ?
Ginno: please do not worry
Ginno: \just give them a time to correct all the network
"
I am thoroughly confused... Horrible support
Click to expand...
Click to collapse
You asked a hypothetical question. I'm surprised you got someone trying to offer an honest response, however speculative it might be.
Update: just tried to make a call and after about 30 seconds of sitting on the "calling" screen I got "reorganizing internal processes" ghost calls confirmed.

shinydesert said:
Is the battery life a little better with 2.3.5
Thanks.
Click to expand...
Click to collapse
It is indeed, the O3D GB was a bit unstable on the Thrill!
Sent from my LG-P925 using XDA

Ghost calls confirmed..
Sent from my LG-P925 using xda premium

What does the ghost want? Why can't we make him happy? Block his number if worst comes to worst.