Page 2 of 35 FirstFirst 123412 ... LastLast
Results 9 to 16 of 278

  1. #9
    jlevy73's Avatar
    jlevy73 is offline BlackBerryOS Einstein
    Join Date
    Mar 2009
    Location
    Los Angeles, CA
    Device
    9630/9550/9530/
    Posts
    8,538
    Quote Originally Posted by HarlyFan View Post
    Still waiting for the Hybrids!!!
    I am sure there will be many of them



  2. #10
    catstide's Avatar
    catstide is offline BlackBerryOS Fanatic
    Join Date
    Mar 2009
    Location
    bama
    PIN
    what's tha
    Device
    DROID
    OS
    2.0
    Posts
    1,210
    Quote Originally Posted by HarlyFan View Post
    Still waiting for the Hybrids!!!
    me too ...i'm no hybrid builder but it seems like the 2- 5.0 sfi files that have been leaked have the flaws in them and cod's won't fix them. we will probably have to wait for a 5.0 os to be leaked with a nice sfi file that they can use.

  3. #11
    Dave12308's Avatar
    Dave12308 is offline BlackBerryOS Gifted
    Join Date
    Mar 2009
    Location
    Schenectady, NY
    Device
    Motorola Droid
    OS
    Android 2.0
    Posts
    375
    Quote Originally Posted by catstide View Post
    as someone stated earlier RIM may have known that the camera didn't function in this beta but didn't care because they may have been concentrating on other functions with this build. we can't complain about the scraps we get.
    I think the problem here is that folks are really more used to the 4.7.0.xxx leaks; which tended to leak once they were in the hands of the carriers for testing. Thus, with 4.7.0.xxx; we were actually seeing builds that were POTENTIAL official releases.

    The game has been a little different with the 5.0.0.x builds we have seen so far, as they seem to be builds that were never meant to make it outside of RIMs testing labs. I don't believe that ANY of the 5.0.0.x builds that have leaked were actually meant for carrier testing, the packages put on the secure download site for the carriers wouldn't include "RIM internal tools" and would just be the OS packages that we are used to seeing. Once a build has passed enough testing at RIM to make it to carrier testing, the "Quincy" app has served its purpose and is no longer needed.

    Application compatibility and functionality as a whole would likely be less important for an internal build, as an internal build wouldn't necessarily be built with everyday functionality in mind. Anytime something new is tested, the whole OS must be repackaged, and a new build number assigned. I would venture to guess that there are WAY more internal builds in existence, than builds meant to see the light of day with a specific carrier.

    Now, I could be completely off base here, I don't know; as I don't work for RIM or a wireless carrier. But it makes sense if you think about it.



  4. #12
    Brett Wyman is offline BlackBerryOS Master
    Join Date
    Feb 2009
    Location
    CT
    Device
    Tour
    OS
    .230
    Posts
    2,198
    test

  5. #13
    catstide's Avatar
    catstide is offline BlackBerryOS Fanatic
    Join Date
    Mar 2009
    Location
    bama
    PIN
    what's tha
    Device
    DROID
    OS
    2.0
    Posts
    1,210
    Quote Originally Posted by blackberryos View Post
    test
    1,2,3



  6. #14
    catstide's Avatar
    catstide is offline BlackBerryOS Fanatic
    Join Date
    Mar 2009
    Location
    bama
    PIN
    what's tha
    Device
    DROID
    OS
    2.0
    Posts
    1,210
    Quote Originally Posted by Dave12308 View Post
    I think the problem here is that folks are really more used to the 4.7.0.xxx leaks; which tended to leak once they were in the hands of the carriers for testing. Thus, with 4.7.0.xxx; we were actually seeing builds that were POTENTIAL official releases.

    The game has been a little different with the 5.0.0.x builds we have seen so far, as they seem to be builds that were never meant to make it outside of RIMs testing labs. I don't believe that ANY of the 5.0.0.x builds that have leaked were actually meant for carrier testing, the packages put on the secure download site for the carriers wouldn't include "RIM internal tools" and would just be the OS packages that we are used to seeing. Once a build has passed enough testing at RIM to make it to carrier testing, the "Quincy" app has served its purpose and is no longer needed.

    Application compatibility and functionality as a whole would likely be less important for an internal build, as an internal build wouldn't necessarily be built with everyday functionality in mind. Anytime something new is tested, the whole OS must be repackaged, and a new build number assigned. I would venture to guess that there are WAY more internal builds in existence, than builds meant to see the light of day with a specific carrier.

    Now, I could be completely off base here, I don't know; as I don't work for RIM or a wireless carrier. But it makes sense if you think about it.
    nice post dave

  7. #15
    jasonfyc's Avatar
    jasonfyc is offline BlackBerryOS Fanatic
    Join Date
    May 2009
    Location
    Walla Walla Wa
    PIN
    ned her ag
    Device
    Storm
    OS
    8959765.655we80.754.
    Posts
    1,290
    Wirelessly posted (storm 9530)

    Quote Originally Posted by BlackberryOS
    test
    #test

  8. #16
    jlevy73's Avatar
    jlevy73 is offline BlackBerryOS Einstein
    Join Date
    Mar 2009
    Location
    Los Angeles, CA
    Device
    9630/9550/9530/
    Posts
    8,538
    Quote Originally Posted by Dave12308 View Post
    I think the problem here is that folks are really more used to the 4.7.0.xxx leaks; which tended to leak once they were in the hands of the carriers for testing. Thus, with 4.7.0.xxx; we were actually seeing builds that were POTENTIAL official releases.

    The game has been a little different with the 5.0.0.x builds we have seen so far, as they seem to be builds that were never meant to make it outside of RIMs testing labs. I don't believe that ANY of the 5.0.0.x builds that have leaked were actually meant for carrier testing, the packages put on the secure download site for the carriers wouldn't include "RIM internal tools" and would just be the OS packages that we are used to seeing. Once a build has passed enough testing at RIM to make it to carrier testing, the "Quincy" app has served its purpose and is no longer needed.

    Application compatibility and functionality as a whole would likely be less important for an internal build, as an internal build wouldn't necessarily be built with everyday functionality in mind. Anytime something new is tested, the whole OS must be repackaged, and a new build number assigned. I would venture to guess that there are WAY more internal builds in existence, than builds meant to see the light of day with a specific carrier.

    Now, I could be completely off base here, I don't know; as I don't work for RIM or a wireless carrier. But it makes sense if you think about it.
    Woooaahhh, that's some good stuff Dave. When does OS 101 classes begin lol

Page 2 of 35 FirstFirst 123412 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •