Feeds

Hackers jimmy Android Marketplace onto PlayBooks

RIM App Planet bypass blow

New hybrid storage solutions

Hackers have managed to get Google's Android Marketplace running on the RIM PlayBook, potentially bypassing RIM's App Planet though the mod is far from mainstream.

The hack follows the successful rooting of the PlayBook, but isn't for the fainthearted. The process involves installing a beta version of the OS formerly known as BBX and getting one's hands dirty with a shell prompt, but once completed one can install applications from the Android Marketplace without having to wait for RIM's approval or a PlayBook-specific version.

Twitter user neuraloc has posted text instructions, but for those who prefer incidental music to accompany their hacking there's a YouTube video stepping through the process here.

The PlayBook's QNX OS, in common with most modern mobile operating systems, will only run applications that are digitally signed by the vendor. The next version of the OS (currently in beta) can execute applications written for Google's Android OS as long as they are signed (and thus distributed) by RIM.

Installing the Marketplace installs another certification authority - Google - so applications can be installed without recourse to RIM, which is good if you want to run lots of cheap applications but bad if you want to control the distribution mechanisms for the purposes of quality and revenue generation.

RIM needs the Android App Player, as the company calls its emulator, as an important leg-up in filling out the application store for its new OS. Mobile users only really want a handful of the most popular apps, so if RIM can sign the Android versions of those apps then it can claim to have a populated store while trying to build up enough market share to attract native developers. So the Android App Player is only intended to be an intermediate step - the aim is native applications solely distributed through the RIM store.

That means RIM will probably make the process harder before the official launch of the new OS. Until we know how well Android apps run on that version we can't tell if we'd ever want to install the Marketplace - it's likely emulated Android will run slower, and from the video demonstrations it seems that Android apps won't benefit from the PlayBook's elegant multitasking system, but until it's released we won't know for sure.

Getting the Marketplace installed is an impressive technical hack, but one which will probably have limited impact on the PlayBook. Unless RIM does an HP and abandons its unpopular tablet, in which case we'll all have to get our hands dirty with a bit of SSH. ®

Security for virtualized datacentres

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Top 5 reasons to deploy VMware with Tegile
Data demand and the rise of virtualization is challenging IT teams to deliver storage performance, scalability and capacity that can keep up, while maximizing efficiency.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.