1. You want that $100.00 in your pocket or an Amazon Fire TV don't you? Well here's the deal. With our new updated look we are in desperate need of an updated logo. The 'old' one has certainly served us well, but it's time. Find all the details here: bit.ly/1q0k6Wa
  2. DroidForums.net is currently undergoing a major software upgrade. If you are experiencing any problems logging in please: Contact Us

Explanation of FRF57 vs FRF83

Discussion in 'cvpcs' started by cvpcs, Jun 27, 2010.

  1. cvpcs
    Offline

    cvpcs Premium Member Premium Member Developer

    Joined:
    Jun 14, 2010
    Messages:
    151
    Likes Received:
    0
    Trophy Points:
    0
    Ok, i wanted to post this because i've gotten many questions about it lately.

    Since the drop of froyo source, there are a lot of ROMs flying around with build ids on them like FRF57 and FRF83. I'm going to clear up what these ids mean and how they are significant.

    Basically, a build id is just that, it's an identifier that lets a developer know that for any given piece of software in the field, what build of the code it is. This helps them identify problems.

    Although I have not found any definitive proof of how the first three letters of the build ids are generated, they tend to relate to what version of android is being ran as well as it's stability. I would guess something along the lines of:

    ABCXX

    Where

    A = Android codename (C = cupcake, D = donut, E = eclair, F = froyo, etc)
    B = Stability (R = release-candidate, S = stable)?
    C = ?? no idea on this one, possibly just a letter increment
    XX = build number

    So for instance, FRF57 is the 57th build of a release candidate for froyo.

    So back to the difference of FRF57 and FRF83. FRF57 is the build id for the latest leak from motorola. An FRF83 leak for the Droid DOES NOT EXIST. FRF83 is the build id for the nexus one release.

    Now, the numeric build number is DEVICE SPECIFIC. Just because the nexus build is FRF83 and the motorola build is FRF57 DOES NOT mean that the nexus build is necessarily more stable or more advanced. All it means is that nexus has built their source 83 times, whereas motorola has built theirs 57 times.

    Also, it is important to know that for source builds, the source itself is IN NO WAY RELATED TO THESE BUILD IDS. The only exception is for some tagged sources, which reference device-specific source, but that does not currently exist for froyo.

    So what does this all mean?

    Many source ROMs will be released in the following weeks that will label themselves FRF57. This means that they use the PROPRIETARY files from the FRF57 leak. The source is still the latest source.

    Some ROMs will label themselves FRF83. Although I am not certain this only means that SOME proprietary apps, were taken from Nexus and placed on the Droid. The actual hardware drivers on these ROMs are STILL FRF57. Also it is important to remember what was stated above about the numeric portion of a build id being device-specific. Although the ROM may pull device-independent apps from nexus, that doesn't guarantee that they are any more advanced than the motorola ones. (They may be, but it's not a guarantee)

    Since the source itself as well as the features implemented are not related to these proprietary files, as of Sapphire 0.6.1 I will be dropping the build ID labeling from the release page, and the reference to these proprietary files will be available in the changelog and build.prop, but not be used to identify the ROM.

    I feel that this is the right thing to do, as personally I think it is somewhat of a lie to users to label a ROM FRF83 when the core hardware files are still FRF57, especially when most users don't fully understand what those build numbers mean, other than that one number is higher than the other. Also, pairing a source ROM with a leaked id, confuses users into whether a ROM is truly built from source or not.

    I hope that this has cleared up some confusion about all of this. :)
  2. Thoraldus
    Offline

    Thoraldus New Member

    Joined:
    Nov 13, 2009
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    SE Idaho at 6000'
    Thanks for the explanation! +1
  3. Rouger
    Offline

    Rouger New Member

    Joined:
    Mar 30, 2010
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Longmont, CO.
    I was just wondering about this, thanks for the good info...
  4. crdnilfan
    Offline

    crdnilfan New Member

    Joined:
    Dec 22, 2009
    Messages:
    207
    Likes Received:
    0
    Trophy Points:
    0
    Thanks for posting this! I agree with you when you say that you disagree with people posting builds as FRF83, when they're still just basing it off the FRF57 files for the Droid.

    Good post. +1
  5. Fulle
    Offline

    Fulle New Member

    Joined:
    Jun 14, 2010
    Messages:
    66
    Likes Received:
    0
    Trophy Points:
    0
    Thank you for the explanation! Now for the moral dilemma....

    Do I refer the Bugless Beast zealots to this post.... or just let them continue to go on, confused as heck?
  6. Kmart95
    Offline

    Kmart95 New Member

    Joined:
    Dec 27, 2009
    Messages:
    342
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    Wow nice post I just learned a ton

    Sent from my Droid using Tapatalk
  7. PJnc284
    Offline

    PJnc284 New Member

    Joined:
    Nov 21, 2009
    Messages:
    111
    Likes Received:
    0
    Trophy Points:
    0
    Look for an FRF85B rom now since it's out for the N1. lol
  8. nagmier
    Offline

    nagmier New Member

    Joined:
    Apr 9, 2010
    Messages:
    176
    Likes Received:
    0
    Trophy Points:
    0
    Just an FYI I think I remember seeing someone explain that the 3rd char is a repeat of the first char ESE, FRF... etc but if could be that its just something I keep telling myself so I'm not 100% but it seems to make sense over the last few releases we've seen
  9. cvpcs
    Offline

    cvpcs Premium Member Premium Member Developer

    Joined:
    Jun 14, 2010
    Messages:
    151
    Likes Received:
    0
    Trophy Points:
    0
    I used to think so as well but I believe the first eclair leak for droid was ERD56, or something along those lines. I may be mistaken though
  10. Tanknspank
    Offline

    Tanknspank Beta Team Premium Member

    Joined:
    Jan 13, 2010
    Messages:
    3,506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    ESE53 is what I thought it was. I'll check Adamz's section because his 6.0.1 ROM is based off it.

    Yeah, it's ESE53.
  11. cvpcs
    Offline

    cvpcs Premium Member Premium Member Developer

    Joined:
    Jun 14, 2010
    Messages:
    151
    Likes Received:
    0
    Trophy Points:
    0
    Well it appears i stand corrected :)
  12. Johnly
    Offline

    Johnly Guest

    Seeing how I have a droid, the best build for me is the FRF57???
  13. Tanknspank
    Offline

    Tanknspank Beta Team Premium Member

    Joined:
    Jan 13, 2010
    Messages:
    3,506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    Unless another leak comes out, that's the only option you have right now. All the other are for the Nexus 1.
  14. Johnly
    Offline

    Johnly Guest

    That is what I figured, and I tried a FRF83 rom and everything seemed OK except major players like maps and Navigation? I head into Denver often, and that Nav app is my very good friend! What is the deal with people thinking FRF83 is better? Bigger number? lol! Thank you for confirming this sir.
  15. jroc
    Offline

    jroc Well-Known Member

    Joined:
    Apr 9, 2010
    Messages:
    3,837
    Likes Received:
    61
    Trophy Points:
    48
    Location:
    Washington DC
    Thanks for the lesson.

    I know who I wanna vote for now....
  16. Yakuzagang5
    Offline

    Yakuzagang5 New Member

    Joined:
    Dec 15, 2009
    Messages:
    235
    Likes Received:
    0
    Trophy Points:
    0
    No, because 2.0.1 for the Droid was ESD56. That was the official release too, so that explanation is not correct
  17. Tanknspank
    Offline

    Tanknspank Beta Team Premium Member

    Joined:
    Jan 13, 2010
    Messages:
    3,506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    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 :D
  18. idulfingz
    Offline

    idulfingz New Member

    Joined:
    Mar 29, 2010
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    different every week, you would have to ask
    sweet... i feel like i just listened to an episode of paul harvey's "the rest of the story"
    Thanks for the explanation :)
  19. Se7enLC
    Offline

    Se7enLC New Member

    Joined:
    Nov 16, 2009
    Messages:
    1,263
    Likes Received:
    0
    Trophy Points:
    0
    Great explanation! Now if only we could get the ROM developers to admit whether they built from source or not...
  20. Bear in NM
    Offline

    Bear in NM Active Member

    Joined:
    Nov 12, 2009
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    38
    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
Search tags for this page

android baseband explanation