| | 10-20-11, 02:37 AM Thread Author #1
Tools to help make the APK -> BAR process easier (UPDATED)
Well guys, I made some batch files to simplify the loading of BAR files before and now I'm back with some more batch files to streamline the APK to BAR conversion process, and the signing process.
Grab this ZIP file and extract it to the root of your C drive. You should end up with a folder structure like so "C:\apk2bar" that has my "apk2bar-HaTaX.bat" and "signbar-HaTaX.bat" in there.(apk2bar-HaTaX.zip)
If this is your first time dipping your toes into this, all you need besides this file is the Android SDK to get started. And if you plan on sharing these BAR files with others, you should go get yourself some signing keys pronto, they take a few days to get sometimes. That means yes, the Blackberry command line converter and signing tools are in this ZIP file and you don't need to go grab those again.
I don't need to go into detail twice for this, I included a "README" file in the zip that outlines the steps you need to take, so I'll just post the contents of it here:
So basically just follow those steps to get setup and you'll be on your way to converting and signing your very own Android app.
Hello fellow BlackBerry lovers!!!
I've made a few batch files before to make things easier, and here
is the latest installment to simplify the two step process to porting
Android APKs over to the Android Player on the BlackBerry Playbook.
This batch file processes the APK and converts it to a loadable BAR file.
It will place the BAR file in the same directory the APK file was in.
First things first, go get your Android SDK downloaded from here:
When running the installer, remember where you installed the SDK!
You're going to need that path in a future step, I installed to
"C:\android-sdk" to keep things simple and clean.
Second, get that SDK installed and download the "SDK Platform" from the
"Android 2.3.3 (API10)" list in the Android SDK Manager tree.
Third, setup the apk2bar-HaTaX.bat file by opening it up in notepad and make
sure the "ANDROIDSDK=" line has the correct path to the installed SDK.
You're set at this point! Just drag an APK onto the batch file in windows
explorer and it should start working it's magic. If the file isn't
compatible you'll see that listed in the output at the end.
This batch file signs the BAR file created by apk2bar-HaTaX.bat.
First, make sure you've gone through the steps to get your signing keys from RIM.
Start that process at this URL:
Second, get those keys activated and create a working p12 certificate file.
Follow the steps at this URL if you need help:
Third, setup the signbar-HaTaX.bat file by opening it up in notepad and make
sure the 3 lines are properly filled out. You should know where your
.p12 file is, and the passwords for both the .p12 and the CSK password.
(You created these passwords when you went through step 2 above)
You're set again! Just drag a BAR file made with apk2bar-HaTaX.bat onto the
batch file in windows explorer and you will get a signed BAR file
ready to be loaded on any Playbook running OS 2.0 with developer mode on.
Let me know what you think and how it works for you! I'll consider putting together OSX / Linux shell scripts for this if there's enough demand as well.
New version 1.2 posted on 12-17-2011
This version supports multiple files at once, now you can select multiple files to have converted or signed and it will process them one by one. I know, something that would have been more useful a while ago, but better late then never!!
New version 1.1 posted on 11-1-2011
This version now supports long file names in paths and APK names.
Problems with APKs in a root folder of a drive fixed (C:\ for example).
Some additional tweaks to ensure the correct file is passed.
Default output of APK left up to apk2bar application now, they WILL be placed where the original APK was located
Previous versions available:
1.1 - Download apk2bar-HaTaX-1.1.zip
1.0 - Download apk2bar-HaTaX-1.0.zip