Printable View
Thanks...but why worked earlier this week and now nada. Maybe it did not like the PIN?Quote:
Originally Posted by Stiefler07
It works, fixed the lock...had to download the cod file to the desktop, would not let me put it into the utility...soon V5 will be here and we will party in the streets.
I still say that you can't test anything like the Storm without identical setups on every device. I'd start with 10 people who wanted to set back to defaults, wipe and install a bare OS without additional apps. If everything is the same but there's major differences in performance then I'd say hardware was the issue. We for sure can't have a wide area beta like the leaks are producing. There's no control. You have no idea what device base settings are, what apps are loaded and which are actually running. It's like prescribing a drug to a group of people who 'just don't feel well'. Depending on the drug some will feel better, some won't, some will feel worse and some may die. It doesn't mean the hardware is at fault, it means that there is not enough information to make an informed decision as to what drug to prescribe.Quote:
Originally Posted by jlevy73
Personally I have installed almost every leak and hybrid. So far I have had no significant battery life changes from .75. No disappearing browser, ever. Never had to resend service books. Have not had any signal or radio issues and I travel. I have several apps installed including Weatherbug. I do have memory leaks but I ignore memory for the most part. Even down at 1 meg I see no difference other than a very slight lag between apps. Eventually the memory recovers.
Do I actually have the best Storm on the planet? I think not but I do have a Storm that has not been picked through and reconfigured to run like an F1 car. I can count on one hand the changes to the basic operational settings that I have made, the biggest of which is changing screen brightness to 60 and enabling memory cleaner. I change nothing unless I am sure what I'm changing and have no desire to fiddle with something that is running good. After 37 years in technical services I have learned that if something is running good don't screw with it and if you want an F1 racer then you have to be ready to put up with the maintenance it requires. In our case battery pulls, random reboots and other glitches.
The other problem I think we have is RIM themselves. What's going on in development? Someone has to get a handle on these guys. A lock function that has worked since day one is broken in .141???? Why the f would you even touch code that worked perfectly???? Then the community comes up with a fix that works? Of course! The community (a few individuals actually) can come up with a better OS than RIM by mixing and matching the best of several versions. In my opinion this speaks volumes about RIM and the quality of their OS team. I don't think they've hit a wall with hardware, I think the OS team is disorganized and out of control. I seriously doubt there is a 'code boss' who locks all 'solid' modules from changes without specific approval. Without someone in charge of protecting 'gold code' modules and libraries and without a very specific and rigid set of rules for changes to them there can not be and will never be a new OS that gets approved.
I don't think VZW is screwing anyone when it comes to not releasing an new OS. They, like us, have the right to expect RIM to provide a reasonably solid OS that does not require battery pulls constantly, suffer random reboots and does not have bugs in basic functions including memory management. Supporting tens of thousands of Storm devices has to be a nightmare! The time alone between restarts ties up a tech for at least 5 or 6 minutes! Multiple restarts can quickly translate into an 30-60 minute call! Add to that the twit factor where peoples brains instantly lock up when anything technical even starts to creep in and lets not forget the hyperactive factor aka drama factor (can't be out of touch with my posse for more than 30 seconds) which requires the tech to calm the person and explain several times what to do and you have hours long tech line waits. It's not fair to other VZW customers and it isn't fair to carriers to have to support a broken OS. It doesn't matter how much money they have or how much they make they like us don't want to throw it down a rat hole and there is no logical reason to release an OS that is going to require mega support.
Excellent post Wrenchman very eloquently stated. Thanks again.
Can't agree more, excellent post!Quote:
Originally Posted by jlevy73
Sorta says it all..Couldn't agree more.
I have to agree. This OS is the best one for me so far. I'm staying with this one. Did the lock fix and now it's great.Quote:
Originally Posted by Proxis
Glad to hear that this works for you. I'm liking it myself.Quote:
Originally Posted by Striker951
Update: 4 days in and still doing great. I wanted to add that the search feature in messages works even faster in this OS. I lightly touch a name or Email topic and the blue line comes across searching out all like messages. Works in SMS too. I knew that this always worked but it is much quicker in .141 for me.Quote:
Originally Posted by Pain Producer
Thought I would share.
DO you use a bluetooth while talking on the phone? If so, have you noticed significant reduction in volume while on calls. I liked 141 but that started happening to me after about 24 hours and since I am on the phone 5+ hours/day that was a deal killer. Curious to know if you've had this issue.
Good morning jlevy73. Yes I do use BT. I use a Jawbone 2 all day long and I did not have some volume issues. However, I turned up the volume on my earpiece and I can hear the convo just fine. I can hear clearly now and it hasn't been a deal breaker for me.:arms:Quote:
Originally Posted by jlevy73
Quote:
Originally Posted by Wrenchman9
Very nice :)
Has anyone tried putting .132 sfi into .141 to see if that fixes QL flitter....I'll try tonight, after I get home from work if no ones tried it. I loaded .141 radio code into .132 v4 and QL flittered...meaning (to me) it has something to do with the radio code in .141...ya think?
If anyone has tried this lemme know, as that will save me some time this evening :D
Oriol, Lyric says there are a couple more .cods I should change also and theres a chance the way I was trying might work. So basically, Bricks-r-us is open for business again. lolQuote:
Originally Posted by oriofan8
I bet you figure this thing out......Quote:
Originally Posted by Shanepark2
....just in time for v5 :D
Really...why do you think it flittered in v4 when I added the .141 radio??
Thanks Shane
There's a chance that the radio might be the problem. There is also a chance that the 141 radio might need 132 .cods or vise-versa.Quote:
Originally Posted by oriofan8
I don't know..my battery life has been sucking this 141 any advice with a better os to use or the best one out there?
I agree that .141 is not a good one. I have tried every imaginable OS known to mankind lol, and thus far v4 has been the best both in terms of memory and battery life. I should point out that I am using the radio code from 113 with v4, since that gave me the best signal strength out of all the SFI's I've tried.Quote:
Originally Posted by quicknsilver
how can i get that?...possibly could you show me? tell me how. to get the v4
Here is the link just follow the instructions in the OP and you'll be all set. Let us know if you need any further help.Quote:
Originally Posted by quicknsilver
http://www.blackberryos.com/forums/c...ed-public.html
Ok guys, after about 15 bricked attempts, I think I finally got the correct .cod combination in Crackutil to get Quicklaunch to work on .141. Lyric found 5 cod files that needed to be swapped for it to work. After trying 20+ combinations of the cods, I could not get rid of the App Error 202. Adding the net_rim_bb_apps_framework corrected the App Error. Let me know if this works, as I don't even have Quicklaunch. http://www.blackberryos.com/forums/9...ues-141-a.html