Hey guys, I just updated to .141, everything seems to be running well. However, my quicklaunch is playing up. It flashes rapidly when opened? Is this happening to anyone else and is there a fix??
I'd also emailed NikkiSoft. Possible solution(s) are posted elsewhere here on CB.
I was not expecting NikkiSoft to actually DO anything about this issue, since the OS is beta. But the developer emailed me back..
Unfortunately QuickLaunch will not work with .141 without one of the OS fixes that can be found here on CB. I've been working on this the last 15 hours trying everything I could think of. There is a bug in a fundamental function in the .141 OS. I tried to rewrite and restructure the app many different ways to get around it but nothing was successful. Believe me I tried. I didn't even sleep last night.
RIM has stopped development on 4.7 and is going to 5.0 from here on out and from what I'm told (by RIM) there will be no more 4.7 leaks. QuickLaunch works correctly on 5.0 on other devices and I'm going to assume it will also work on the Storm 5.0. If not then I will addresss the issue again at that time.
.141 is an unofficial beta leak and over 90% of QL owners are still running .75 therefore I am going to stop working on a solution to this and return back to QL 2.0 development.
If you need QL then you'll have to stay with OS .132 or earlier or use one of the patches / hybrids to .141.
I'm sorry for any inconvenience.
I must say, I'm VERY impressed that they gave it so much effort. Seriously, they justifiably could have just dismissed this due to the nature of betas.
So...I'm off to play with the fixes that have been posted.
Could you please let us know how you get on with the fixes and where we can find the one that works. I really don't want to have to downgrade os or wait for 5.0
Really impressed with NS efforts though
Posted from my CrackBerry at wapforums.crackberry.com
Common issue, there are some fixes which people claim to work others say they brick their phone. The fix I have seen that has been claimed to work the best are the hybrdis...the one by ONE or Lyrical
There are a couple threads on this in the OS section with more detailed information on the fix. Works for some and not for others...likely because of different install methods. But, the fix involves replacing the java files in .141 with the files from .132. I use all of the leaks but creating a hybrid strikes me as defeating the purpose in hoping for a solid OS from RIM/Verizon.
If I'm reading between the lines correctly, Cheetah is hoping this problem is confined to .141 and won't appear in later leaks (if there are any with 5.0 on the way) or in whatever is leaked/released in 5.0. I don't think he knows that for sure as he doesn't have higher 4.7 versions or 5.0 versions for the Storm. If it happens on future versions, he's got a problem he has to solve.
Common issue, there are some fixes which people claim to work others say they brick their phone. The fix I have seen that has been claimed to work the best are the hybrdis...the one by ONE or Lyrical
I did this fix and it WORKS!!! Just take you time and follow the directions exactly and you wont have any issues......
Common issue, there are some fixes which people claim to work others say they brick their phone. The fix I have seen that has been claimed to work the best are the hybrdis...the one by ONE or Lyrical
Yes, early attempts to fix this problem with crackutil did indeed brick your phone. But after about 2 days of using different combination, it was found that there are 6 .cods in the Java folder of .141 that are causing the problems with Quicklaunch. It can be fixed here.
Yes, early attempts to fix this problem with crackutil did indeed brick your phone. But after about 2 days of using different combination, it was found that there are 6 .cods in the Java folder of .141 that are causing the problems with Quicklaunch. It can be fixed here.
The 'it can be fixed here' link doesn't work could you please re-post
I like 141 for now - not going back to 132. I am using alt. apps for now.
I'm with you...I'm pretty happy with .141 for now, and am not a fan of hybrids - just my preference. I'll have to either wait for a fix (now that .141 has gone official from Vodafone) or wait until 5.0 is released.
Just got this reply from Nikkisoft, 5 mins after emailing them, that's service!
"There is a bug with 141 that causes QL to not work correctly. 141 also has other issues like you can't lock your device.
There are fixes to 141 on crackberry.com that fixes the QL issue along with some other issues if you don't want to wait for the fix.
The fix to QL will be in version 2.0 which is coming out soon.
Thanks for understanding."
I'll be waiting on the fix, life's too short to be messing around with somthing that might brick my phone ;-)
shaneparks fix on blackberry os WILL NOT brick your phone ive been using it since the release of 141 however i will be doing the ql update when its available with the official unmolested 141
