bhughesiii
Member
There is a lot of good news in that post! Keep up the good work cvpcs. Can't wait for 0.6.1
+1 Your guys' ROM is the best so far and I also cannot wait to see what 0.6.1 brings.dancedroid
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!
Two Releases Two Days, Froyo Anyone? - Sapphire 0.6.0
- Thread starter sniffle
- Start date
+1 Your guys' ROM is the best so far and I also cannot wait to see what 0.6.1 brings.dancedroid
this rom is working great for me!
thanks!!!
my pre-release froyo build starting running like a turtle in the mud so i had to find something else.
so far so good.
i will be giving the wifi tether a good workout today when i make my drive from Nashville to Knoxville while i stream the US Soccer game vs Ghana.
we'll see how it holds up.
thanks!!!
my pre-release froyo build starting running like a turtle in the mud so i had to find something else.
so far so good.
i will be giving the wifi tether a good workout today when i make my drive from Nashville to Knoxville while i stream the US Soccer game vs Ghana.
we'll see how it holds up.
Gearhead Geek
Member
So, I had a thought/suggestion.
It's been bugging me as to why this is FRF57, vs the Nexus One has FRF83, and supposedly word on the street is that the Droid's build will be FRF84.
Come to find out, the vendors are infact the ones that decide on these build numbers, and there are more infact like a ROM version number it seems. If one were to look at different versions of Cyanogen, you'd find build numbers make no mention of a source version.
Perhaps it would be better off to remove the FRF57 (or ESE81 for the older versions) labels, and simply say AOSP 2.1, AOSP 2.2, etc.
While it's no big deal, it could lead to some confusion, and I'm sure for some, give a false sense of fragmentation.
Again, just a thought.
BTW, Lovin 0.6.0, can't wait for 0.6.1!
It's been bugging me as to why this is FRF57, vs the Nexus One has FRF83, and supposedly word on the street is that the Droid's build will be FRF84.
Come to find out, the vendors are infact the ones that decide on these build numbers, and there are more infact like a ROM version number it seems. If one were to look at different versions of Cyanogen, you'd find build numbers make no mention of a source version.
Perhaps it would be better off to remove the FRF57 (or ESE81 for the older versions) labels, and simply say AOSP 2.1, AOSP 2.2, etc.
While it's no big deal, it could lead to some confusion, and I'm sure for some, give a false sense of fragmentation.
Again, just a thought.
BTW, Lovin 0.6.0, can't wait for 0.6.1!
this rom is working great for me!
thanks!!!
my pre-release froyo build starting running like a turtle in the mud so i had to find something else.
so far so good.
i will be giving the wifi tether a good workout today when i make my drive from Nashville to Knoxville while i stream the US Soccer game vs Ghana.
we'll see how it holds up.
yea i've been running the froyo leak since it was first released, it was getting buggier and buggier, things were starting to not work (Gmail wasn't deleting anymore, GPS didn't work, couldn't update maps, and none of the suggested things worked but reflashing it with maps 4.3 in the .zip worked)
i'll probably be running this until Cyanogen comes out with CM6 or Pete brings out the next version of bugless beast(0.2.1 is anything but lol)
Certain things will break if you don't have that build identifier.
Sent from my Droid
well i can't get you nav but i can get you maps, the easiest way i can do is put this .apk in the sapphire-0.6.0-update.zip's system/apps
Maps.apk
its maps.apk v 4.3...its how 4.3 on to the froyo leak
after adding it flash and go
Last edited:
While I will probably try out both CM6 and BB (my first experience with BB was 0.2.1 and ugh so many problems), I really like Sapphire. The speed of it is great. I had been running UD RC2, but the "self compiled from ASOP" version was horrible for me. Came back to Sapphire and it's all nice a stable and working.
Can't wait for 0.6.1
Gearhead Geek
Member
Guess I'm just confused then how there's an FRF83 rom out for the Droid?
there is no frf83 out for the droid... that is the Nexus one...
the nexus one's drivers will not make any of the hardware on the moto Droid work.
if there IS another leak for the moto droid, those drivers will be used instead and the updated # used.
once the final 2.2 release is made, we won't even use FRF as a reference because there will be no need. it's more of a reference for ourselves, though most people identify with the build #'s google assign's a specific revision of code.
by pulling the froyo branch of the source code we actually are quite a few build #'s beyond FRF83 to be honest...
the nexus one's drivers will not make any of the hardware on the moto Droid work.
if there IS another leak for the moto droid, those drivers will be used instead and the updated # used.
once the final 2.2 release is made, we won't even use FRF as a reference because there will be no need. it's more of a reference for ourselves, though most people identify with the build #'s google assign's a specific revision of code.
by pulling the froyo branch of the source code we actually are quite a few build #'s beyond FRF83 to be honest...
anything that says FRF83 for the droid is just the google apps that aren't device specific.
example, cyanogen doesn't release his roms with any google apps, and then you need to use a gapps.zip to add the market, and all the other google apps. Those gapps.zip are usually based on the manufacturers releases, FRF83 (nexus one), FRF57 (droid leak). Cyanogenmod is built for nexus one, and ported to droid by koush.
so when someone builds a rom, and includes those files with the rom, they are just saying it's based off FRFxx.
you are 98% accurate, there are also proprietary drivers from the leak as well that have been updated from teh previous proprietary drivers required for the Android OS to operate on the Motorola Droid, without these updated drivers, bluetooth, wifi, GPS, sound, video, calls... none of it would work... you would just have a lump of software unable to interface with the hardware... when the update is officially released, or another leak is aquired, those drivers will change once again... and we will update to the newest set
though i must say your explanation is much more simple and easier to understand... i'm being too technical sorry...
Gearhead Geek
Member
you are 98% accurate, there are also proprietary drivers from the leak as well that have been updated from teh previous proprietary drivers required for the Android OS to operate on the Motorola Droid, without these updated drivers, bluetooth, wifi, GPS, sound, video, calls... none of it would work... you would just have a lump of software unable to interface with the hardware... when the update is officially released, or another leak is aquired, those drivers will change once again... and we will update to the newest set
though i must say your explanation is much more simple and easier to understand... i'm being too technical sorry...
Thanks. Between these posts I understand
installed this last night. its been running great. fast too. I used Chevy's 1.25 lv kernal and it works perfectly. initially the restoring process took forever and i some how lost root per titanium but a reboot fixed that. market was slow to load because of all my apps. i had no issue with maps. im not sure if its because i restore it from my back up or not. but i just realize that my Droid sound clip isnt there anymore. Instead i get "incoming message" as the default. what gives? other then that everything seems to be working correctly. im not sure about facebook since i dont use and uninstall it already.