Last month the data was collected and a whopping 96.5% of Playbook users have the latest OS installed. The chart shows when and what OS version was released and approximately how many people had downloaded it. The current one was downloaded the fastest.
The WiFi version of the BlackBerry PlayBook has already received its update to OS 2.1, and today the 4G/LTE PlayBook is getting its update. The OS for the 4G/LTE version of the PlayBook has been updated to 184.108.40.2068 and includes many of the same features and fixes that we saw on the WiFi version.
We were expecting to see an update to the PlayBook OS sometime in the near future, especially since BlackBerry 10 Jam Americas is right around the corner. Well it looks like we will be seeing something very soon. RIM posted some blog articles today at BES 5 and Mobile Fusion updates, and in one of […]
As expected we for some news about the PlayBook 2.1 OS update at BlackBerry World. RIM announced that a developer build of the OS will be coming sometime around the end of the month, will a full release coming at the beginning of the summer.
RIM is hard at work behind the scene to keep us constantly updated on the new things to come about as well keeping above the competition and now according the latest HTML5test.com. RIM has tested the new up and coming Blackberry Playbook OS 2.1!! So does this mean we will see the update coming soon? […]
Just the other day they had an update, so what’s going on with this one? * before you upgrade to the latest OS 220.127.116.1167 a then Login via devuser and run /tmp/setuidgid root /bin/sh to gain root
RIM announced yesterday via beta zone that a new update for the PlayBook will be released prior to the update that is scheduled for February. This update on contains improvements and fixes to some problems that users have encountered.
New details have come out regarding RIM’s investigation into the 3-day service outage that occured world wide last month. There are some additional solutions that are being discussed in Waterloo to resolve the issue and prevent it from happening in the future. Hit the break for more info…