Thread: 9530 5.0.0.2xx waiting room

Originally Posted by Dave12308

Kill3r, the thing is there will never be a 100% optimized OS for ANY device. OSes by nature are constantly being upgraded. A leaked OS such as 5.0.0.191 is an example of an OS build that was never meant to make it anywheres outside of RIM's testing labs. Most likely, they are fooling with something internally which required the camera to be disabled. So it's not so much that the OS isn't "optimized", it's more the case that it was never meant to be a fully functioning OS. It's all about the need to occasionally "break" things to make an improvement. Perhaps my previous post about a possibility of a change to the video "driver" inside of the SFI is the reason for the camera being disabled. Perhaps the method the camera app uses to display the preview is incompatible with the new video "driver" and thus the camera was simply disabled.

A higher build that is in fact meant to be released to carriers for their own testing would likely be "fixed" and feature complete. I think the problem is our expectations being set too high by the 4.7.0.x leaks that were all more or less feature complete, as they all leaked from a carrier testing phase for the most part; or were official releases by some obscure carrier. The game seems to have changed with 5.0.0.x; as out of 3 releases for the 9530, none are suitable for actual carrier testing.

5.0.0.140 has the alarm bug
5.0.0.154 has the browser text field bug
5.0.0.191 has the camera bug

Any software problems are the result of the app not being updated yet; but the three examples above are all complete showstoppers, as they all significantly affect usage in a negative way.

Oh, okay. It was alwasy my understanding these these recent builds leaked from the carrier testing stage. If that was not the case, then it makes perfect sense. Because of that assumption, I felt as if those builds should have never left RIM and gone to carriers for testing. But like you said, that was not the case, so I have nothing to complain about.

I wonder if there are any flick-scroll capable, as well as speedy, 5.0 builds that are in carrier testing right now then? .191 is the first flick-scroll capable leak available (also .140, enabled via a .191 settings backup), but does anyone know what the first 5.0 build with already-enabled flickscroll is?

Whatever 5.0 build Verizon decides to put out for the 9530, I hope it has flick scroll. I was never big on the feature before, but now that I've had it in .191, I don't want to lose it lol

Originally Posted by Storm5150

Oh man hittin below the belt, OUCH :laugh2: but wouldn't that make our waiting room more realistic, I mean we might be waiting a long time, so maybe you should rename Your room to "probably gonna get a leak" room

By renaming it that, it would sound like we're a waiting room full of plumbers!

Originally Posted by catstide

that one has a fix and a workaround. IMO it is the most stable of the three

I know there is a workaround, however what I was pointing out was that all 3 5.0.0.x releases for the 9530 contain a "showstopper" bug that a) would prevent it from reaching carrier testing to begin with; or b) fail pretty early on in the testing. I was not merely pointing out bugs, I apologize for the confusion.

I would give it a try but .191 its working great for me, I just miss my camera ... but guess what? I got a great quick pull! I'm ok with it :-D

I think we should rename it the "waterboarding room"...it's like torcher waiting for Verizon to approve new OSs or testers to work-up the nerve to let it out. With the .191 leak we get a taste of what the phone could be like...bring it on already...LOL

that is true my man but take into consideration OS's that get released as official to other company's... .151 to lucacell...streaming radio issue, 8330 .160 to sprint i think screeching noise when you answer.. I wont go on and on but in short remember that when vzw releases an os build at least it is fully functional may take them longer but that is because they test further and better than other company's the wait sucks but oh well huh?

yep...just sit and wait for the ketchup to drip man...LOL

Well.... You could always follow hybrid makers on twitter in the hopes of being fed the hybrid to end all hybrids.... Then watch all the tweet followers start slaughtering and eating each other due to no morsels of food for their hungry little storms.... :baby:

Have any of you .191 users tried OOAK's/Lyricidal's 5.0.0.140/154/191 hybrid? I'm really considering switching to this, especially since it retains flick scroll (.140 radio, but using a backup file from .191).

My only concerns are with the speed of the UI and the smoothness of the Sounds menu. I'm really liking how fluid the Sounds profile popup menu is in .191, is this a theme-controlled thing? Or is this in all available 5.0 builds? You all know how choppy that menu scrolled in 4.7 (as well as the Terms and Agreements boxes that popped up for RIM apps).

Also, is the sound profile customization in .191 in .140 or the hybrid? And how is the speed of the hybrid vs. .191?

May give the downgrade to the hybrid a shot tonight. I'm kinda wanting my camera back lol.

Originally Posted by f-castrillo

Have any of you .191 users tried OOAK's/Lyricidal's 5.0.0.140/154/191 hybrid? I'm really considering switching to this, especially since it retains flick scroll (.140 radio, but using a backup file from .191).

My only concerns are with the speed of the UI and the smoothness of the Sounds menu. I'm really liking how fluid the Sounds profile popup menu is in .191, is this a theme-controlled thing? Or is this in all available 5.0 builds? You all know how choppy that menu scrolled in 4.7 (as well as the Terms and Agreements boxes that popped up for RIM apps).

Also, is the sound profile customization in .191 in .140 or the hybrid? And how is the speed of the hybrid vs. .191?

May give the downgrade to the hybrid a shot tonight. I'm kinda wanting my camera back lol.

BTW, Welcome to BBOS. I liked 140 and would have stayed with it except I don't use my camera much.

This is my personal opinion concerning the 5.0 os's and I have tried them all 140, 154, 191, and tried hybrids.

You don't really need a hybrid to get great performance, simply back up your phone using DM and then uninstall the 191 OS from your computer. Install 140 and then using App loader downgrade your OS. This way you will have flick scrolling on the 140 OS.

The Sound Profile is fluid in al OS builds as is most menu scrolling. Good luck with your choice because OS's are definitely a personal thing.

so any luck on this leaking?

Wirelessly posted

There is no rumor of it leaking, just a lot of hoping that its even gonna pop..

Originally Posted by Fletchdude

Wirelessly posted

There is no rumor of it leaking, just a lot of hoping that its even gonna pop..

I need a new leak!!! .191 is running great its time for another upgrade :haha:

OK what the hell I'm in...

Originally Posted by P3Designs

BTW, Welcome to BBOS. I liked 140 and would have stayed with it except I don't use my camera much.

This is my personal opinion concerning the 5.0 os's and I have tried them all 140, 154, 191, and tried hybrids.

You don't really need a hybrid to get great performance, simply back up your phone using DM and then uninstall the 191 OS from your computer. Install 140 and then using App loader downgrade your OS. This way you will have flick scrolling on the 140 OS.

The Sound Profile is fluid in al OS builds as is most menu scrolling. Good luck with your choice because OS's are definitely a personal thing.

Thanks for the welcome!

Transitions are not part of the radio file are they? I considered a straight .140 install, but I'm worried that I won't get the same quick/consistent transitions as .191

Is there a significant difference in speed (straight .140 vs. .191)? I'm still trying to sort out what I'm going to miss from .191 if I do a straight .140, versus a hybrid that has the .140 radio and most .191 files.

QUESTION!! lol.. umm if i did a .140 with all of the java files from .191 and a restore from .191 to enable the flick scrollin... how yall think that would work? .. lol umm and bigger question.. would i still have bbm?

Originally Posted by f-castrillo

Thanks for the welcome!

Transitions are not part of the radio file are they? I considered a straight .140 install, but I'm worried that I won't get the same quick/consistent transitions as .191

Is there a significant difference in speed (straight .140 vs. .191)? I'm still trying to sort out what I'm going to miss from .191 if I do a straight .140, versus a hybrid that has the .140 radio and most .191 files.

Yes they are in the radio file. You could give .140 a try and see how it works for you. You could also try BBC's 8.5 hybrid.

Originally Posted by liljp41

QUESTION!! lol.. umm if i did a .140 with all of the java files from .191 and a restore from .191 to enable the flick scrollin... how yall think that would work? .. lol umm and bigger question.. would i still have bbm?

I believe you'd end up with a brick.

Originally Posted by sunkast

Yes they are in the radio file. You could give .140 a try and see how it works for you. You could also try BBC's 8.5 hybrid.

I believe you'd end up with a brick.

... sigh.. but.. but.. i need to do somethin to my phone.. !!! im losin my mind.. lol.. i dont wanna brick.. i wanna upgrade.. lol.. or somethin new to mess wit.. and thats not goin backwards.. lol

I'm torn between straight .140, straight .191, or a hybrid 5.0 lol. But I'm leaning towards keeping the full .191 - I just really miss my camera at times. But the speed is just so much...better than anything before it IMO. So I think I'll stay.

But don't let that stop anybody from leaking a high .2xx build for the Storm . Does anybody know what the latest build for the 9530 is, and if there's a remotely possible leak on the horizon?