Thread: 9530 OS 5.0.0.191 Findings and Fixes #3

This is the continuation of the the 9530 OS 5.0.0.191 Findings and Fixes #2

9530 OS 5.0.0.191 Findings and Fixes
9530 OS 5.0.0.191 Findings and Fixes #2

This will make it easier for members to search for answers.

Thanks for the cleanup so to keep topic alive... anyone hear the diffrences between 191 and the next leak? "Besides Camera and Apps Working"

Actually, if the next leak happens to be 5.0.0.202; from what I understand (and could be wrong, just been reading around) the camera is STILL broken. It gets fixed past .202

camera is a plus but what about all the rim apps like app center and etc.?

Seems a little crazy that BB would have an OS that does not even support their own app.

Originally Posted by kcschultz

Seems a little crazy that BB would have an OS that does not even support their own app.

You must keep in mind this this is a leak and was not intended for public consumption. So it is not RIM's fault that these are not working.

Originally Posted by kcschultz

Seems a little crazy that BB would have an OS that does not even support their own app.

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.

Still waiting for the Hybrids!!!

Originally Posted by HarlyFan

Still waiting for the Hybrids!!!

I am sure there will be many of them

Originally Posted by HarlyFan

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.

Originally Posted by catstide

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.

test

Originally Posted by blackberryos

test

1,2,3

Originally Posted by Dave12308

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

Wirelessly posted (storm 9530)

Originally Posted by BlackberryOS

test

#test

Originally Posted by Dave12308

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

i am loving the 191, its now on both storms

cant wait to snag 202 if its leaked

also is there a easy way to go back to 4.7 without having to wipe[e the phone just curious is all

Originally Posted by newberry

i am loving the 191, its now on both storms

cant wait to snag 202 if its leaked

also is there a easy way to go back to 4.7 without having to wipe[e the phone just curious is all

Yeah you can use loader.exe and it will ask you "if you want to downgrade" just make sure the OS you want to load is the only one on your PC

Originally Posted by Bryan

Yeah you can use loader.exe and it will ask you "if you want to downgrade" just make sure the OS you want to load is the only one on your PC

OK, whats with the eye avatars????:laugh2:

Originally Posted by Natemz

OK, whats with the eye avatars????:laugh2:

Big Brother Bryan is always watching :haha: