Yakuzagang5
Member
No, because 2.0.1 for the Droid was ESD56. That was the official release too, so that explanation is not correct
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Explanation of FRF57 vs FRF83
- Thread starter cvpcs
- Start date
No, because 2.0.1 for the Droid was ESD56. That was the official release too, so that explanation is not correct
That's what cvpcs was thinking about. maybe it has something to do if it is a major update or a minor update? Just throwing out ideas
Great explanation! Now if only we could get the ROM developers to admit whether they built from source or not...
Bear in NM
Active Member
In this post in the news section, just posted this morning, a leak of frf84b is linked:
http://www.droidforums.net/forum/droid-news/55467-even-more-froyo.html
I am still a little confused on a couple of points related to source. CVPS and a few others are now building from the source files that were dropped last week. Are these source files the most current source files from Moto/VZW/Google for the Droid? Were these source files for a different device? Is a properly channeled drop of source for froyo a 2.2 set of files for all devices, with other features/apps being included/added/built that are device specific? And how does this frf84b fit in the source picture?
Sorry to probably be so confusing, the link above to frf84b confused me, as I thought the source files were dropped to the community, which would have ended "leaked" files?
Thanks,
Craig
http://www.droidforums.net/forum/droid-news/55467-even-more-froyo.html
I am still a little confused on a couple of points related to source. CVPS and a few others are now building from the source files that were dropped last week. Are these source files the most current source files from Moto/VZW/Google for the Droid? Were these source files for a different device? Is a properly channeled drop of source for froyo a 2.2 set of files for all devices, with other features/apps being included/added/built that are device specific? And how does this frf84b fit in the source picture?
Sorry to probably be so confusing, the link above to frf84b confused me, as I thought the source files were dropped to the community, which would have ended "leaked" files?
Thanks,
Craig
the frf84b, is motorola's 84th build of the froyo source. the source files that we are building from are updated daily by google and many other sources. if they built that 2 days ago the release we made last night is more up-to-date than that release.
with the exception of the drivers that allow the android OS to communicate with the hardware of the Motorola Droid.
we will be making another release tonight to update our drivers to the most recent leak.
outside of the drivers, all from-source roms will be more up-to-date than any leak can ever be.
with the exception of the drivers that allow the android OS to communicate with the hardware of the Motorola Droid.
we will be making another release tonight to update our drivers to the most recent leak.
outside of the drivers, all from-source roms will be more up-to-date than any leak can ever be.
Right, and you should understand, Google will continue to update this codebase, but if this FRF84B is indeed the RC for 2.2 on Droid, it will essentially be "frozen" at whatever time the build was compiled. Source ROMs are guaranteed to provide you with the latest and greatest.
Bear in NM
Active Member
Thank you Sniffle and P. Makes sense. I did not understand that the source code itself was dynamic. But as you (P) posted, it does sound like at some point the source will be finalized. So if I understand this correctly, then right now the source code built roms are likley to be the most stable, but we do not yet have the final source that will be ota'd eventually. Edit: I guess in theory, this new frf could be the final RC.
And I will be trying the Sapphire rom. I just went through the entire release thread, and see you hit a few minor snags which I am sure will be rolled into the "new" source. I actaully hate Wiki for political reasons, but your info format is head and shoulders above the way most of the other dev's handle the dissemination of files and info.
Craig
And I will be trying the Sapphire rom. I just went through the entire release thread, and see you hit a few minor snags which I am sure will be rolled into the "new" source. I actaully hate Wiki for political reasons, but your info format is head and shoulders above the way most of the other dev's handle the dissemination of files and info.
Craig
Pete's Bugless Beast v0.4 (FRF84B)
Damnit not the thread I was looking for .... still checking.
Here we go ....
http://forum.cyanogenmod.com/topic/818-froyo-or-cm/page__st__20__p__7658#entry7658
That's the laugh one, post #4 in that one. The first is still good too.
On the one hand, yes, I see that a ROM like BB is really just the stock system with some things removed, some things added, some things tweaked, some scripts changed/added...
But isn't that what ALL ROMS are, really?
Even the compiled-from-source ones - unless the source is changed drastically, you effectively end up with software that is the same as what's running on a stock system, with minor tweaks added in. The process of compiling source code into a rom is just a process, much like the process of repackaging a binary-based rom.
There's actually a benefit to running a "modified stock" rom over a "compiled-from-source" rom - a modified stock will be mostly IDENTICAL to a stock system. No chance for a slight difference in the build environment causing problems, you're running the exact same app that the motorola and verizon testers were running. It will run just like stock except for where changes are specifically made.
Of course, compiled-from-source has advantages, too - you can make changes more elegantly than you ever could in a modified stock rom, and you should have less compatibility issues between apps and system.
I've run BB for awhile, and I just recently installed Sapphire. They both have their merits, and really, ROMs don't really provide all that much over the stock system - stock Android already does a LOT. I wish the ROM makers would all be more clear about whether they are compiled from source or piecewise-assembled, and where their pieces come from.
I want to address some of the comments about people who say BB runs faster than stock - yes, it is running the same binaries for the most part, but the small little tweaks DO make a difference in end-user perception. It's not placebo. The BB startup scripts kill off some system tasks, which makes it a little snappier (but breaks some stuff). The virtual memory and task killer settings are tweaked, which may make some difference. Really anything you do can make a difference, it doesn't take much on a system like this.
This reminds me a lot of the binary-package vs compiled-source linux distribution argument. I run Gentoo, but sometimes I am a little jealous that Ubuntu "just works".