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.

NOOK Color’s update to Android OS 2.2/Froyo

B&N Update Next Week?
Just showing you the link:
http://androidos.in/2011/04/nook-co...-update-on-april-25-froyo-incoming-with-apps/

Doubt it. Would be all over the internet if it was (Engadget etc). Seems like a shady site.

I saw the same thread earlier today on the Barnes and Noble site.
I cannot post the link but title of the thread is "Monday it is"

http://bookclubs.barnesandnoble.com/t5/NOOKcolor-General-Discussion/Monday-it-is/td-p/970372

Look at post #6 in that thread. "Go to B&N if you need help with anything." Yeah right im going to make a trip to Barnes and Noble and tell a representative that i don't fully understand how to use the new update LOL.

I too heard the chatter, it might actually be monday. Let's hope they come out with a newer kernel. The one we have is kind of getting old.

I just hope the update contains something of use to the community that it doesn't already know -- like being able to use Bluetooth beyond a couple of feet.

Just as interesting as the date is the content. If you keep reading that thread, you get a link to another thread where they say a manager actually saw (and shared) the update: She shared what she saw....WOW. Flash, new PDF and lots of aps.
Monday will be interesting: if the updates actually comes, will it manage to get past the OTA blocking?

Just calm down and relax,if you're looking on the B&N Community board there's daily some folks that fool around those update.

Does anyone know if this update could maybe increase app compatibilty due to an official update to froyo such as Homerun battle when we get it rooted with android market and/or sideloading? Cause that would be the only reason I'd have for updating.

It will be interesting

Agree. It will be what it will be. But to be on the safe side, I've flashed back to stock 1.1.0 for a couple people at work who rooted. That should allow the OTA (whatever it will be) to install as BN designs.
And so it goes....

I really hope it's 2.2 and not 2.1 with an app store. I wonder if they're going to release a new kernel (and its source)? That would really help out the CM7 people...

I would think the likelihood of an update this week is very high. Remember they're taking on a major retail partner in Staples starting May 1st. If they have an update, they would want to make sure that it's finished before Staples start selling them, it'd make things a lot easier for their new partner.

buzz killington said:
Remember they're taking on a major retail partner in Staples starting May 1st.
Click to expand...
Click to collapse
Where did you hear/read this?

I think one of the most exciting features of the upcoming update will be an official froyo build that will have full aceess to all of the internal storage. That and an overclocked kernel plus being rooted will be pretty damn awesome in my opinion. I can't wait, time to backup my nook and revert to stock in preparation.

BN
Paul22000 said:
Where did you hear/read this?
Click to expand...
Click to collapse
Straight from a BN press release
http://www.barnesandnobleinc.com/pr...aples_announces_plans_to_sell_nook_color.html
Also the fiscal year for BN ends on 4/30. There may be things you want announced before year end or if it is bad news after year end. The NC product distribution strategy is beginning to resemble the Apple one. However, BN does not have its app developer support strategy in place.

Auto Update came through today (despite devicemanager editing and OTA certs renaming)
I was using my nook today, when all of a sudden a B&N permissions dialog screen popped up (specifically, it said something like "permissions error, rebooting". Then it rebooted into clockwork(???) which formated my data and cache partitions, pulled up a list of errors trying to change other things (possibly because I am rooted with an OC kernel?), and then rebooted.
Despite this, it managed to reboot into stock. I didn't get any further than the setup, before I decided to flash my nandroid backup. I'm actually kind of regretting that a bit now, since it would have been interesting to see what the new stock was like (presuming it worked correctly), but ultimately, I think it is probably best to wait for XDA to tell me what to do about updating or otherwise. In the meantime I'll be leaving my wifi off.
I've been debating upgrading to CM7, but the sleep / battery issue has prevented me. If this update really is froyo, and the devs here get it rooted nicely soon, I may not make that step at all, or at the least I may be able to wait much longer for the sleep issue to be fixed.
Also of interest is the fact that I had renamed the OTA certs and used sqlite editor to tweak the devicemanager.db file. I don't recall if I had spoofed the build.prop or not. But this seems to imply that we don't really have any reliable way of preventing OTA updates at this point, other than installing a completely new rom. That alone might be enough to warrant switching to CM7. I'm so confused!

I'll have to grab my NC and turn it off and take out the sd card.
I don't think I've turned it off for a couple of weeks...running CM7.
Nothing new showing up here yet:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758

CM7 won't auto-update, will it? I was running stock 1.0 rooted (and now that I've flashed my nandroid backup, I am again, though I lost two weeks worth of tweaking).

Boy, the leaks dried up.

For a few weeks there the leaks where coming one a week, sometimes two. Now nothing. Wonder if its the calm before the OTA storm.

This is just another piece of evidence in my theory that someone somewhere has made it their job to sit there and **** with the hackers and modders all day long.
The thought has crossed my mind to just go back to 100% stock, but I'm just too addicted to having at least root.

If you ever installed any of the leaks, there is no going back to 100% stock.

stevessvt said:
For a few weeks there the leaks where coming one a week, sometimes two. Now nothing. Wonder if its the calm before the OTA storm.
Click to expand...
Click to collapse
Generally, traffic like we've seen means one of a few potential things.
First, a specific phase in dev is complete. The testers provided, information/confirmation of results and they are moving on to next phase.
Second, they are now in a bake period, letting it sit ages days before processing for release.
Third, it's is ready but don't want to release with Razr. Normally multi releases are no big deal but they have a nice budget for advertising and are releasing in multiple formats. They may want to have some focus.
My guess is 2. 8 weeks post release is still early for an ota, so they have time. Reading up in the results of the ota seems to indicate a fair amount of success. Some last minute fine tuning may be in order. I doubt they want to stretch this to the week of thanksgiving...so its next week or december. Just my opinion

I'm just glad they leaked what they did. Really helped me not smash my Bionic into little tiny pieces. I hope they are still working on it because there are still problems with it.

The leaks have stopped bc they have pushed out a final release candidate till the next update.
Sent from my DROID BIONIC using xda premium

papi92 said:
The leaks have stopped bc they have pushed out a final release candidate till the next update.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
I got crucified on another forum for suggesting multiple releases. They might burn you in effigy.

One other factor is that the devs working on it are likely playing their cards much closer to their chest, now that Motorola seems to be actively working to counter the efforts of developers. So, I suspect many things are going on with the devs, and likely releases are being found, but they're not being discussed.

MODERATOR MESSAGE
alodar1 said:
I got crucified on another forum for suggesting multiple releases. They might burn you in effigy.
Click to expand...
Click to collapse
I really dont mind a little OT on my forums, as long as its civilised

stevessvt said:
If you ever installed any of the leaks, there is no going back to 100% stock.
Click to expand...
Click to collapse
Cant you get back to stock by running moto-rooter fastboot?

2fast4u89 said:
Cant you get back to stock by running moto-rooter fastboot?
Click to expand...
Click to collapse
With a locked bootloader, No. You can restore the stock system but the radio and kernal cant be rolled back because the update only goes one way.

r0ckstar323 said:
With a locked bootloader, No. You can restore the stock system but the radio and kernal cant be rolled back because the update only goes one way.
Click to expand...
Click to collapse
I disagree. As I recall (I haven't done it with the latest file format from Motorola) you can reset the entire phone using the fastboot restore files no matter what version of kernel/BP you have.
You start by flashing the "cdt.bin" file first. This resets the signatures that are verified on all of the other partitions.
Then do the entire set of files which will completely reset all of your partitions on the phone + the BP code.
If it's not CDT.bin first, then it's 1 of the other partitions, then the CDT.bin, and then the whole set of files.

Hello XDA and Thanks to HashCode! (Droid 3 ICS Kexec Alpha#4)

I wanted to put this in the development forum...but anyway. I have never until this morning messed with Safestrap or loading a custom ROM. I finally bit the bullet and loaded Safestrap 2.1 and the KEXEC Alpha 4 on my Droid 3 this morning. Very impressive work you guys do, and I can't wait to see a finished product!

mhelm23 said:
I wanted to put this in the development forum...but anyway. I have never until this morning messed with Safestrap or loading a custom ROM. I finally bit the bullet and loaded Safestrap 2.1 and the KEXEC Alpha 4 on my Droid 3 this morning. Very impressive work you guys do, and I can't wait to see a finished product!
Click to expand...
Click to collapse
Lots of people here do amazing work, good to hear another D3 happy with the progress. Do keep in mind... there's never a 'finished product' it's ALWAYS being updated with better enhancements and whatnot. It's a finished product when it's hardware bricked.
Glad to hear you jumped into the wonderful world of roms though! I hope you enjoy your stay for many years to come.

Major Battery Drain & Gmail Non-Functional
Wish I could post these bugs in the development forum for the Kexec ROM. Should this info be passed along to Hashcode or anyone? If so, what's the best way since I can't respond in the proper thread?
The first day and a half of using this ROM everything was great. All apps worked, the device ran cool and no bugs.
This morning my battery has drained about 80% in an hour. Not sure what caused that.
Other Notes:
Yesterday the Gmail app failed and will no longer work. "Sorry, Gmail has failed...." The screen flashes something so quick I can't read it and returns me back to the Home Screen. I have resorted to using a AquaMail for now. Seems like after the Gmail app failed when I reboot the device now I get some message about Droid is updating. This happens right after the Cynogen screen and before the Home screen loads.
Trivial - System Settings: Battery Usage time is always off.
EDIT: So after going back through the 42 pages on the thread....I am going to reduce the overclock on mine and see if that helps. I also didn't catch that I needed to recalibrate the battery. I will do that after the battery is back up to 100%.

I also can't post in the development forum (yet - one more post after this and I can so that's part of the reason for posting this ) and wanted to add one item to the above:
The car dock USB audio doesn't work. I wouldn't call this a bug so much as a not yet implemented feature. I assume it could be related to the whole audio routing involving missing phone speaker audio with Bluetooth on, etc.
I've been running alpha 4 for nearly a week and it's been surprisingly solid. A few reboots and freezes, but far less than I expected going in.

another user who can't post in development forum.
due to camera issues, shorter battery and random boots i have switched back to CM9 from the Kexec Alpha 4.
hoping to switch back to CM9 Kexec once it get more stable and/or out of alpha

The very bad stability with the stock rom is what lead me to look to alternatives about a year ago and I haven't looked away from Hash ever since! All in all, the instability in Kexec #4 is a little frustrating, but I can deal with it since I know it's not "ready for prime time" like the stock rom claimed to be!

The new jb preview from hash is quite impressive, although not usable at the moment.
Sent from my XT862 using xda premium

Jb is much smoother on my d3 as well. Ics has a force close issue on mine.
Sent from my DROID3 using Tapatalk

Im thinking about trying it out latter. Wish me luck

Anyone done a factory reset on their JB Droid 3 and been unable to pickup service?
For some reason I'm unable to pickup Verizon as my carrier and establish phone service after a factory reset. The phone just sits here and "Searching for Service"..
I'm thinking I just need to re-flash the latest KEXEC JB build and see if that brings me back to service functionality.
I just did a re-flash, and I'm still sittin on the "Searching for Service" screen.
--McBean
(Likewise dev-forum impaired!)

To my knowledge, there are no working "jb" builds for the d3. If you are referring to hashcode's cm10 preview, well the answer is in the title, its just a preview. I suggest wiping and flashing non kexec cm9 or aokp till development on the kexec process furthers.
Sent from my XT862 using xda premium

Hash is working on data for Jellybean. Until then nothing will work.

I must have done something weird my first time through as phone and normal services worked under the preview. (Not trying to ***** or start a flame out of it... just stating a reality.)
I'll go take a crack at CM9 then and see what's up. Maybe I can get Service back up under that and then flash to CM10 to restore phone service....
--McBean

McBeanTIO said:
I must have done something weird my first time through as phone and normal services worked under the preview. (Not trying to ***** or start a flame out of it... just stating a reality.)
I'll go take a crack at CM9 then and see what's up. Maybe I can get Service back up under that and then flash to CM10 to restore phone service....
--McBean
Click to expand...
Click to collapse
Not sure what you managed to do, but if you could replicate it, that might be useful to Hash (and the rest of us). Even on the "it might work" release today, I am not getting anything.

Devil's in the details
keithk23 said:
Not sure what you managed to do, but if you could replicate it, that might be useful to Hash (and the rest of us). Even on the "it might work" release today, I am not getting anything.
Click to expand...
Click to collapse
I'll see what I can do. I'll have go figure out how to go completely stock again and start from the ground up. That's where all the magic began for me. And I'll need to find the ROM from 2-3 weeks ago when I first got the guts to flash CM onto my phone. I don't know what in the hell possessed me to do a factory reset other than sheer stupidity. Totally jinxed a good thing.
--McBean