Forgot your password?

BlackBerry PlayBook OS Now Available


UPDATE: RIM has confirmed on their blogs that this update is for Adobe AIR 2.7 and Flash 10.3. Here is how they describe it:

This latest version of the BlackBerry Tablet OS includes support for Adobe® Flash® 10.3 and support for Adobe® AIR® 2.7 software. This means that with this update you should experience even better performance for Flash videos than before, and be able to access new applications that are being built with Adobe AIR 2.7 software.

Well it looks like we got our OS update for the week!. The BlackBerry PlayBook OS has just been updated to v1.0.6.2390. We have received multiple tips of the update and I have confirmed it myself. According to the notes this is the OS that RIM leaked to devs earlier to test our Adobe AIR 2.7 and Flash 10.3.

So what are you waiting for? Hit that Check for Updates button and let us know if you spot anything else new!

34 total comments on this postSubmit your comment!
  1. What a time for storms to be rolling in and my cable provider sucks so i have my Cable and Internet going in and out.

  2. downloadin….

  3. first off i friggin love how fast and easy the playbook is to update


    i am noticing huge improvements in speed all over the place. i find everything is flying. web browser is noticeably faster.

    love it

  4. flyyyyyiiinnnngggg

    just did a little more browsing and i am noticing hugggggeeeee improvements in browser


  5. The next update they should add a notification icon for updates and a universal search option.

    • They do have notifications for updates.

      I didn’t even find out there was an update online. The pop up came up on the top left of the playbook saying their was an update.

      The same popups let you know when there are updates to your appworld apps as well.

      • Thanks BB Addict. Hey, I
        found that some of the games in the Flash games app loads more efficiently.

  6. I will do the update once I got back home from work…

  7. wow it really is burning up the net. Like to see a retest between this and iPad 2. I recall some early test with iPad 2 just slightly quicker, but i can’t believe that is true now.

    Nice update RIM..

  8. That all sound so good cant wait to get a PB :)

  9. Now that this is finally out the door, I seriously hope that RIM will take the time to fix all the problems devs are having with web apps. It seems the list keeps growing and nothing gets solved. It is a big hurdle for devs that are trying to deliver an experience similar to what you can find on other platforms.

    • I like the idea but care to elaborate on what bugs with web apps?

      • If you have dev access you can see the whole list in the tracker, but the big ones are: lack of full hardware acceleration for transitions and visual glitches with some CSS combinations.
        You can also see how slow Google maps is compared to what you can find on other platforms.
        It’s a shame because that means cutting back on features and bling or spending lots of time designing temp workarounds that may not prove satisfying 😐

        • Well maybe that is exactly what they are doing because I just opened my google maps app.on my playbook and it’s blindingly fasts now.

          • Well, if it’s mapapp, we don’t have the same definition of fast and smooth. Scrolling is jumpy, sluggish and there is just a map, it’s not part of an app. Look at any demo of Google maps for iPad and you’ll see what I mean by smooth scrolling and fast transitions. Bing is OK on the PB, but it could be better.
            The PlayBook certainly seems capable of doing the same as the iPad because when hardware acceleration kicks in, the scrollers fly, but this needs to work everywhere.

            • No its not mapapp its map search, and I’m side scrolling between the BR website, my email, and map search. How smooth is that on the iPad 2? oh that’s right you can’t do that on the iPad 2. Let me know when the programmers fix that bug. Thanks.

              • Yes multi-tasking on the PB is more like WebOS than iOS, but that’s not the point. Webworks devs should be given the same chance as AIR devs. Rendering should be perfect and accelerated. And btw, your app may not be able to implement the PB swipedown gesture anytime soon because of another bug in Webworks…

                • Buy more like Web OS I assume you mean it actually has it while iOS doesn’t. Like I said, let me know when Apple fixes that.

                • multi-tasking on both iOS and webOS are pause and play, QNX is a different beast.

                • Actually, my app does implement the swipedown gesture with no problems. Hate to disappoint 😉

                  Of course, I haven’t published the app yet as I’m not happy with it visually. This isn’t due to WebWorks, it’s actually due to my decision to use Sencha Touch — which just isn’t there for the PlayBook.

    • This comment makes no sense. Move this crap some where else.

  10. I really wish there were in-depth change logs for these updates. It does seem like there are other tweaks throughout the OS but I can’t help but wonder if the placebo effect is to blame for all the positive comments. Don’t get me wrong, I honestly think other improvements are being made. I’d just like to have an explanation for each.

  11. Just a simple test to illustrate the speed problem that the browser has. Go to:

    On the desktop, you’ll get 60fps, the PlayBook does 10fps…

    WP7: 22fps, iOS5: 27fps

    So, the browser team at RIM still has a lot on its plate if it wants to compete and support Webworks devs.

    • Why do you come on here and spot utter bullshit. Watch the clip of the TAT guys showing their apps. They continually say the playbook does 60 that’s right 60 fps.

      Just because you don’t know how to program….

      • Haha, and you do and that’s why your app gets reviews that it’s sluggish?

        You can’t compare native apps that use OpenGL to web apps that rely on the browser. RIM needs to fix the browser environment so that it can compete as a viable technology to build apps. Other phone/tablet makers can, so RIM should be able to do it too.

        • So I imagine they will do it, so what’s your point???

          My point is the machine/chip set has the ability. so yes they need to do it.

          The point in coming on here and bitching is what? do you this Berry Review is RIM? Read the disclaimer at the bottom of the page.

          Or do you just like to bitch.

        • Oh right, now I get, you want to shift the conversation off of flash……

          How good is flash on Playbook cmpared to flash on the iPad??????

  12. Flash is both a curse and a blessing. It’s nice to be able to have access to 95% of the content that is out there, but without extensions that can block the plugin at times, a lot of websites can be annoying.
    And AIR was probably chosen as a dev env because RIM had nothing else to offer and that combo was available and worked well for cars. AIR is not known to be very fast and responsive when it comes to building UIs, even on the desktop, so I wouldn’t think that mobile device makers would choose that technology first to build their GUI.
    But anyway, my point is not to bash the PlayBook, but to wish for major improvements in the tools RIM provides for developing Web apps. The browser works very well, so it must be possible to let devs have access to the same optimisations. Btw, iOS had a similar problem that was only recently fixed with v5 and things like maps are quite problematic on mobile devices when they’re not native, but end users don’t know that and will always blame the dev…

    • Are you talking about hardware acceleration? I am not sure if that is implemented in the browser for everything yet. I have been chatting with the WebKit team and they have some cool things coming. Right now I have not figured out a trick for kicking in the hardware acceleration yet.

      • Thanks for the news Ronen, I hope copy and paste is coming before the end of the year…
        Regarding hw acceleration, if you use 3D CSS, then some acceleration will kick in, but it seems it’s easily broken by adding certain elements or properties to the div that will be moving. The difference between accelerated vs non-accelerated transitions is like night and day.

  13. I can’t reply above, so I’ll do it here.
    I agree with you, Marc, ST isn’t there yet. The learning curve can be quite steep because of the bugs and the missing/wrong documentation.

    If you’ve found a solution to the onSwipeDown problem when using the Google Maps API, I’m sure others would be grateful if you could publish your solution. There is a test case in the dev forums that shows that simply loading the API breaks the gesture.

    • You guys are using Sencha Touch? Haven’t you found it riddled with bugs even in regular browsers? Every time I thought I worked around one bug another one came up.

      • Agreed, I have lots of overrides and hacks in place to make it behave the way I want to for my PlayBook experiments, but 1.1 is not as bad as it was before and it still is the best mobile framework in terms of performance.
        The whole point of using a framework is to be able to build something very quickly, but I found that with ST, as soon as you were trying to build something more complex, you really had to understand how it all worked behind the scene, beating the point of using a RAD framework, really.
        Hopefully V2 which isn’t too far away will fix most problems, but I think they focused on Android, so PlayBook devs may have to wait some more ;(.

BlackBerry© is a registered Trademark of BlackBerry Limited. BerryReview is in no way affiliated with BlackBerry Limited though sometimes their lawyers send us love letters...

Copyright © 2007-‘2016’ BerryReview LLC