Marc from pandora was the one who figured out what caused the problem with several apps, not just pandora. There is a bug in.151 that got fixed in .164. From his description of the bug I think its something that would require them to make wide sweeping fundamental changes to their software, and this if there some other way to still do it on BBs. Its seriously way too much work and way too high risk to workaround a rim bug that rim has already fixed.
So options are put up with it until 164 is available, don't use pandora (Or slacker) or swap the radio code in your os to an earlier version. I just reset when it happens, and am waiting for 164
Posted from my CrackBerry at wapforums.crackberry.com
Marc from pandora was the one who figured out what caused the problem with several apps, not just pandora. There is a bug in.151 that got fixed in .164. From his description of the bug I think its something that would require them to make wide sweeping fundamental changes to their software, and this if there some other way to still do it on BBs. Its seriously way too much work and way too high risk to workaround a rim bug that rim has already fixed.
So options are put up with it until 164 is available, don't use pandora (Or slacker) or swap the radio code in your os to an earlier version. I just reset when it happens, and am waiting for 164
Posted from my CrackBerry at wapforums.crackberry.com
Thanks for the 411. Hopefully .164 comes out soon for the 9530. Still will listen to Pandora, but it is annoying to have to reset just because of this bug. It's practically the only thing I have to do a reset for anymore after .151. Somebody get that .164 leak out already!! ;-)
Marc from pandora was the one who figured out what caused the problem with several apps, not just pandora. There is a bug in.151 that got fixed in .164. From his description of the bug I think its something that would require them to make wide sweeping fundamental changes to their software, and this if there some other way to still do it on BBs. Its seriously way too much work and way too high risk to workaround a rim bug that rim has already fixed.
So options are put up with it until 164 is available, don't use pandora (Or slacker) or swap the radio code in your os to an earlier version. I just reset when it happens, and am waiting for 164
Posted from my CrackBerry at wapforums.crackberry.com
Hey! Can you help with that? Where do I find just the radio from an older OS and how do I swap it out? Thanks!!
Isn't this old news? I've had this version of Pandora for a while now. Anyways, I'm running Lyricidal's 6v7 Hybrid which appears as .151 on my Storm and I'm not having any radio problems whatsoever. Good luck to those that do have the problem.
Had Major issues with Pandora 1.1.1 with OS .151 First i had the same issues as everyone above where if i started listening to pandora and then closed the app and then went back to it, it would say not enough memory. The only way to fix it is either keep Pandora constantly on or do a battery pull. The other major issue i had with pandora was that i had a crazy error msg after i did a battery pull. the message said this Uncaught exception: java.lang.Null Pointer Exception" . Dont know what it means. Also my SMS and MMS text box were nowhere to be found and if i tried going to my email to do an SMS text the error msg would appear again. I didnt download anything after Pandora so i assumed it was that. Unfortunately the only way to fix it was to wipe my storm clean and reinstall everything. Hopefully someone can issue a better way to fix this as i liked pandora but not its issues
