Showing posts with label PlayBook. Show all posts
Showing posts with label PlayBook. Show all posts

Friday, September 20, 2013

Download BlackBerry Bridge for BlackBerry 10

All PlayBook owners can rejoice today as BlackBerry Bridge has been updated to version 3.2.0.8 - bringing full support to BlackBerry 10 devices. Although long overdue, those of us that are still rocking our PlayBooks can now at least get the full features we were used to having on legacy devices.

These features include the use of BBM on the PlayBook (the perfect weekend for it) as well as using our BlackBerry 10 handset as a remote control - great for when the PlayBook is connected to the TV via HDMI. Being able to use the BlackBerry 10 devices cellular connection will be the most used feature - bringing the PlayBook back to life for many folk.

The update is rolling out as we speak so if you can't see the new version just yet give it a bit of time and try again.

Download BlackBerry Bridge for BlackBerry 10 smartphones

Friday, September 13, 2013

Sideload Apps to BlackBerry 10 that use Google Maps API

The new adventure of “sideloading” has certainly taken on quite an evolution:
  • Back since OS 2 of the Playbook and the early days of BB10, we were able to quickly sideload simple apps – but not apps using Android native code.
  • Along came what has become known as “the xsacha method ” to use the DebugToken to sideload apps that use native code, such as Angry Birds
  • For me, there were still a bunch of apps that didn’t work until AT&T graced me with the OS 10.1 upgrade
  • Along came the solid 10.2 leak which suddenly opened the door to even more Android apps that required a higher version of the Android OS than the Gingerbread that 10.1 had to offer, e.g. Feedly
But there has still always been a tremendous void. A whole handful of simple apps just would not work. Using Catlog (when it still worked – I believe tighter security in Jelly Bean blocks it from reading logs in 10.2 without root) it was apparent that the failure was due to the apps expecting the Google Maps API which is not baked into BB10′s Android runtime. I had simply resigned myself to the reality that those apps would just never work.
…Until now! I stumbled upon yet another CrackBerry Forum post  which lead me to a solution. In a nutshell, the AndroidManifest.xml file contains directives as to which libraries to expect and, more importantly, whether or not they are required. I will document the steps to modify the APK file so that the missing libraries are no longer required. For the purposes of keeping this as brief as possible, I will have to assume you are already familiar with how to obtain an APK  and “the xsacha method .
  • First, download and unpack the APKTool application
  • Place the APK you want to modify in the same directory. Let’s call the APK Foo.apk
  • Get a Command Prompt in that directory (Shift+Right-click, Open Command Window Here should work in recent versions of Windows)
  • Type the following command:
    apktool d Foo.apk Foo
    This will create a sub-directory called Foo and decode the APK contents into it. Don’t close the Command Prompt just yet.
  • Go into the Foo directory and open the AndroidManifest.xml file in your favourite text editor
  • If the Google Maps API is the only problem, you are looking for the following line:
    <uses-library android:name=“com.google.android.maps”/>
  • Modify it to look like so:
    <uses-library android:name=“com.google.android.maps” android:required=“false”/>
    (Repeat this process for any other required library which might be causing problems.)
  • After saving the XML file, go back to the Command Prompt. Type the following command to repackage the APK to Foo2.apk:
    apktool b Foo Foo2.apk
  • I wish I could say we were done. But unfortunately, I’ve found that since the resulting, modified APK is not signed, it will fail when you try to convert it to a .BAR
  • The simplest way around I found, based on this YouTube video  was the SignAPK app. Follow the instructions in the video description to download and unpack the utility.
  • Place Foo2.bar in the same directory and run the following command in a Command Prompt:
    java -jar signapk.jar certificate.pem key.pk8 Foo2.apk Foo2-signed.apk
  • (Obviously, you need to have Java on the machine for that to work but anyone who’s come this far almost certainly does.)
That’s pretty much it! Foo2-signed.apk is now ready to run through the standard APK-to-BAR conversion process and sideload to your device. I’ve used this method to successfully sideload and run apps such as Dunkin Donuts, 7-Eleven and Geico. It should be noted that these apps do contain functionality that relies on Google Maps (such as “Find the nearest …”) and if you try those, the app will crash. Have fun!

Thursday, September 5, 2013

Leaked OS 2.1.0.1753 for the BlackBerry PlayBook

A new leaked OS has popped up today for the BlackBerry PlayBook. It was certainly unexpected but still very welcome. Most PlayBook users didn't expect a new OS I'm sure so anyone that is looking to tinker around a bit will want to give this one a go.

While this is a full OS there is nothing super new but it's said to have some speed improvements which is good to hear. The method for installing is the same of that for BB10 devices so you'll need to use a Windows PC to run the autoloader. Be sure to perform a full backup before you dive in and don't hold us responsible if anything breaks.