Welcome to the CrackBerry Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Page 1 of 17 123411 ... LastLast
Results 1 to 25 of 411
  1. markdental's Avatar
    CrackBerry Genius

    Posts
    2,301 Posts
    Thread AuthorThread Author   #1  

    Exclamation No Way Verizon Makes .141 Official

    There is no way that Verizon is going to make .141 official.


    It still contains the same Html bugs that .132 has.

    AND

    It added a new really GREAT lock/unlock bug that completely destroys the ability of the phone to stay locked. That alone will not let it out into the public.

    Let the wait continue. If nothing else, this increases our chance of seeing a 5.0 official but delays the release of an official OS indefinitely.

    Apparently a build has "been certified and is ready to go", but it can't be .141

    Only CX and Radio know where the 5.0 builds that VZ are testing stand, so hopefully RIM is working hard to get VZW some great 5.0 builds so we can get a great 5.0 official and be done with this mess.
    OS: Cyanogen's Best

    Follow Me on TWITTER
  2. TheComebackKidd's Avatar
    CrackBerry Addict

    Posts
    850 Posts
    #2  

    Default

    The unlock bug is in .132 as well........
  3. 46alpha's Avatar
    CrackBerry Newbie

    Posts
    6 Posts
    #3  

    Default

    Quote Originally Posted by TheComebackKidd View Post
    The unlock bug is in .132 as well........
    I'm running .132 & no unlock bug. Works fine. I thought this was a .141 issue only?

    Posted from my CrackBerry at wapforums.crackberry.com
  4. markdental's Avatar
    CrackBerry Genius

    Posts
    2,301 Posts
    Thread AuthorThread Author   #4  

    Default

    Quote Originally Posted by TheComebackKidd View Post
    The unlock bug is in .132 as well........
    No it's not.

    Lock your phone in .132, then hit any of your bottom 4 buttons. The phone stays locked.

    Do the same in .141, Voila, unlocked phone!!!
    OS: Cyanogen's Best

    Follow Me on TWITTER
  5. pmas's Avatar
    CrackBerry Addict

    Posts
    716 Posts
    Global Posts
    783 Global Posts
    PIN
    I81U812
    #5  

    Default

    Quote Originally Posted by TheComebackKidd View Post
    The unlock bug is in .132 as well........
    No it's not. 132 unlock functions correctly
  6. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #6  

    Default

    ...maybe it's actually not a bug?
  7. radioguinea's Avatar
    CrackBerry Master

    Posts
    1,349 Posts
    Global Posts
    1,352 Global Posts
    #7  

    Default

    VZ "might" and I stress "MIGHT" be holding out for 5.0. I will know more soon.
    Owner - GizmoFusion.com
    BBM Pin: 7A98537B
  8. JasonM.'s Avatar
    CrackBerry Abuser

    Posts
    306 Posts
    #8  

    Default

    Quote Originally Posted by onstageone View Post
    ...maybe it's actually not a bug?
    If this was purposefully done I can't understand why. I highly doubt this is VZW's MR2 either, it's been hourglassing for me like .103 used to.
  9. JordanofMadden's Avatar
    CrackBerry Abuser

    Posts
    160 Posts
    PIN
    306B50D9
    #9  

    Default

    my 132 locks fine.
    I am the Mike Jordan of playing Madden
  10. JordanofMadden's Avatar
    CrackBerry Abuser

    Posts
    160 Posts
    PIN
    306B50D9
    #10  

    Default

    Im a little iff to go to .141 it seem like it wont be as good as .132
    I am the Mike Jordan of playing Madden
  11. blaisedinsd's Avatar
    CrackBerry Genius

    Posts
    1,501 Posts
    Global Posts
    1,537 Global Posts
    #11  

    Default

    Its a bug. But oh boy does It unlocks super fast.

    In .132 and some others pressing and holding the END key will unlock the phone.

    .141 unlocks on any tiny tap of any of the four physical keys

    Posted from my CrackBerry at wapforums.crackberry.com
  12. olta777's Avatar
    CrackBerry Genius

    Posts
    1,663 Posts
    #12  

    Default

    I think the slotted official is between .122 and .132. They have the least of bugs. I do like the speed of .141 I do agree with you Mark. For us those may be tolerable but they are pretty big bugs. I say nay .141 as official. I want 5.0 to be official .

    Posted from my CrackBerry at wapforums.crackberry.com
  13. markdental's Avatar
    CrackBerry Genius

    Posts
    2,301 Posts
    Thread AuthorThread Author   #13  

    Default

    Quote Originally Posted by radioguinea View Post
    VZ "might" and I stress "MIGHT" be holding out for 5.0. I will know more soon.
    WOW, this could the best news EVER!!!!

    When could you hear more Radio?
    OS: Cyanogen's Best

    Follow Me on TWITTER
  14. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #14  

    Default

    Quote Originally Posted by JasonM. View Post
    If this was purposefully done I can't understand why. I highly doubt this is VZW's MR2 either, it's been hourglassing for me like .103 used to.
    Well, people also couldn't understand why they took away being able to unlock the phone or wake the phone up to by clicking the screen...they liked it and also thought it was a bug, something wasn't right...until they realized it was done to avoid accidentally unlocking in your pocket and **** dialing the first few contacts in your addy book.
  15. radioguinea's Avatar
    CrackBerry Master

    Posts
    1,349 Posts
    Global Posts
    1,352 Global Posts
    #15  

    Default

    Quote Originally Posted by markdental View Post
    WOW, this could the best news EVER!!!!

    When could you hear more Radio?
    When I know, you will know Thats all for now.
    Owner - GizmoFusion.com
    BBM Pin: 7A98537B
  16. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #16  

    Default

    Quote Originally Posted by blaisedinsd View Post
    Its a bug. But oh boy does It unlocks super fast.

    In .132 and some others pressing and holding the END key will unlock the phone.

    .141 unlocks on any tiny tap of any of the four physical keys

    Posted from my CrackBerry at wapforums.crackberry.com
    So you've read the end report and this is noted as a bug?
  17. mbvdlza's Avatar
    CrackBerry Abuser

    Posts
    169 Posts
    PIN
    20D3D607
    #17  

    Default

    Quote Originally Posted by onstageone View Post
    ...maybe it's actually not a bug?
    Boring. Where would the fun be in that
    Vodacom, South Africa / Curve 8520 / Storm 9500(R.I.P)
  18. JasonM.'s Avatar
    CrackBerry Abuser

    Posts
    306 Posts
    #18  

    Default

    Quote Originally Posted by onstageone View Post
    ...until they realized it was done to avoid accidentally unlocking in your pocket and **** dialing the first few contacts in your addy book.
    So now we're in the same boat... Lock your phone, put it in your pocket and hit send a couple times and you call either the last person on your call log or whoever your on in your address book. It's dumb.
  19. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #19  

    Default

    Quote Originally Posted by mbvdlza View Post
    Boring. Where would the fun be in that
    LOL

    Well, clearly the little green "go" arrow that showed up awhile back was a bug...as was the ability to go full qwerty in portrait mode...I don't like that at all, must be a bug they need to fix.
  20. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #20  

    Default

    Quote Originally Posted by JasonM. View Post
    So now we're in the same boat... Lock your phone, put it in your pocket and hit send a couple times and you call either the last person on your call log or whoever your on in your address book. It's dumb.
    Honestly hasn't happened yet...also, screen click is obviously more sensitive to this than one of the 4 hard buttons. Unless you're jamming the phone into a pocket in your jeans it shouldn't be an issue
  21. markdental's Avatar
    CrackBerry Genius

    Posts
    2,301 Posts
    Thread AuthorThread Author   #21  

    Default

    Quote Originally Posted by onstageone View Post
    Well, people also couldn't understand why they took away being able to unlock the phone or wake the phone up to by clicking the screen...they liked it and also thought it was a bug, something wasn't right...until they realized it was done to avoid accidentally unlocking in your pocket and **** dialing the first few contacts in your addy book.
    That change actually made sense.

    This is a bug. There is no debate.

    Lock means lock until you CHOOSE to use it.

    You can inadvertently unlock the phone by accidentally pressing any of the 4 physical buttons, it is impossible to inadvertently unlock the phone using the Unlock button like it was in .132

    So back to the real discussion.

    I am excited at the potential prospect of seeing a 5.0 official release in the relatively near future knowing that .141 is not good enough to be official and development of 4.7 has stopped.
    OS: Cyanogen's Best

    Follow Me on TWITTER
  22. JasonM.'s Avatar
    CrackBerry Abuser

    Posts
    306 Posts
    #22  

    Default

    Quote Originally Posted by onstageone View Post
    Honestly hasn't happened yet...also, screen click is obviously more sensitive to this than one of the 4 hard buttons. Unless you're jamming the phone into a pocket in your jeans it shouldn't be an issue
    Screen click doesn't even do anything while it's in your pocket... put a piece of clothing over your finger and try to click your screen. It's capacitive touch. All your pocket dials are belong to green send key!
  23. cadsystems's Avatar
    CrackBerry Abuser

    Posts
    461 Posts
    PIN
    t of Guinness
    #23  

    Default

    I'm wondering what this unlocking bug is all about. I could be wrong but I had the original OS, .109, .113 then .132 as I remember the only way to unlock and lock the phone was by hitting the un/lock button.

    None of my other buttons unlock the device. I'm still on .132
    Listening to The Von Ehrics
  24. olta777's Avatar
    CrackBerry Genius

    Posts
    1,663 Posts
    #24  

    Default

    And per our good sources here on CB, vzw is testing 5.0. I am excited as well.

    Quote Originally Posted by markdental View Post
    That change actually made sense.

    This is a bug. There is no debate.

    Lock means lock until you CHOOSE to use it.

    You can inadvertently unlock the phone by accidentally pressing any of the 4 physical buttons, it is impossible to inadvertently unlock the phone using the Unlock button like it was in .132

    So back to the real discussion.

    I am excited at the potential prospect of seeing a 5.0 official release in the relatively near future knowing that .141 is not good enough to be official and development of 4.7 has stopped.
    Posted from my CrackBerry at wapforums.crackberry.com
  25. onstageone's Avatar
    CrackBerry Abuser

    Posts
    372 Posts
    #25  

    Default

    Quote Originally Posted by markdental View Post
    That change actually made sense.

    This is a bug. There is no debate.

    Lock means lock until you CHOOSE to use it.

    You can inadvertently unlock the phone by accidentally pressing any of the 4 physical buttons, it is impossible to inadvertently unlock the phone using the Unlock button like it was in .132

    So back to the real discussion.

    I am excited at the potential prospect of seeing a 5.0 official release in the relatively near future knowing that .141 is not good enough to be official and development of 4.7 has stopped.
    The real discussion? Ummm, the OP mentions the lock / unlock as being a NG for this being released....so, pretty much us ******** back and forth is part of the real discussion.

    So, back to that...yeah, LOCK means until you choose to use it....except when it's in your pocket and you can also ACCIDENTALLY not by choice hit the LOCK / UNLOCK button....which has happened to me far more with .132 and lower than it has in the day+ I have had .141 with the 4 buttons on the bottom being able to unlock it...

    meh....I'm over it
Page 1 of 17 123411 ... LastLast

Posting Permissions