DPS android app for small screens, works, but poorly...

Question

There is a way to get the DPS android app compatable with 1400 devices, including mobile phones.
In theory if you here reading this its because you have an android app made by the DPS app builder live in the play store and...
A: found out that the android app is only available on large/xlarge screens
B: are getting yelled at by your employer who bought the Adobe DPS subscription and claims this should work on his phone "because I looked at the Adobe site and it says android, my phone is an android, read their site and make it work"
C: found this because you were smart enough to read through the forums before suggesting this as a publishing solution to your employer and want to know if it really works on android phones, in whcih case, you may want to make it easy on yourself and just say "no, it does not" and then waid for Adobe to officially support small/normal screens perhaps head over to this post and bring some attention to it so we can collectivly improve this already awesome tool: http://forums.adobe.com/thread/1097433
however, before you attempt this please keep in mind the following:
1- it does not work well, if at all, on certain devices. specifically the small phone devices with the slower processors. So what typically happens is that you need to delete the data for the app and wait nearly 10 min for the "checking for updates" to process and grab new edditions. Depending on your serivce provider, this can be a nightmare. So, do NOT even attempt this if you have a cap on your data plan, think about how long it would take to download a 100mb folio file on a 3g connection, not to mention the processor which the tablets have and phones do not have.
Here is some more data:
--Android 1 from Sprint: really super slow, thats all I gotta say
--Android 2 from Verizon, again, slow, but works
--Galaxy Nexus 4.1.1, Verizon 4g connection, works great, (10% of the time) lol. about 90% of the time the Galaxy Nexus needs to be restarted after installing, and will get stuck on the "updating library" screen. the only way to fix this for any of the above phones seems to be to clear all data, uninstall, re install, do not launch, restart phone, and then launch app.
I am going to test the following soon:
     Samsung Galaxy Note II N7100 (1.6GHz Quad-core)
     (1.5GHz Quad-core)
          LG Optimus G E973
          Xiaomi MI-2
          LG Optimus 4X HD P880
          HTC One X
(the idea being that perhaps we can go through the list from google in the play store and limit the devices its on, but at least with this solutuon as described below we can get rid of the "not availabe on your device" notice.)
So before you read on, consider that for your end users. If you find a way to fix this, let me know, I have considered turning off hardware acceleration but have not tested this yet.
2- if you choose to attempt this make sure you have a good understanding of command line AND you have a new version of the app ready if you want to roll back.
consider this concept: (you should have these ready)
app a- made by Adobe DPS app builder, works on only large and x-large android screens, lets say its version 100000 and 2.5.5.000. This is already in your google.play store account as a live app,
app b- the app you are about to build in this example below, it will in theory work on small, medium, large, and x-large android screens, lets say its version is 110000 and 2.9.9.000 (it will be MADE FROM APP A, you will open it, edit it, and wrap it back up.)
app c- made by Adobe DPS app builder, works on only large and x-large android screens, lets say its version 200000 and 3.5.5.000 (which would be good to have in case your version b above does not work the way you want)
notice the VERSION codes. These are important because you can only go UP, you can not "roll back" to a previous version.
Again, I do not suggest this, but if you are daring and have some development background, feel free to give it a shot.
(I am not going to be able to support this info, but I can verify 100% that I got mine working, very poorly and slow, but it installs, pulls folios, and loads)
PC WINDOWS ONLY, I have not tried this on a MAC.
get this:
  http://www.7-zip.org/
install it
get this:
  http://code.google.com/p/android-apktool/
read all about it.
go here:
  http://code.google.com/p/android-apktool/downloads/list
get:
          apktool1.4.3.tar.bz2
and
          apktool-install-windows-r04-brut1.tar.bz2
put them all in 1 folder, extract both items, all the way
the grab the
          android-viewer.apk
that Adobe DPS made, or whatever yours is named...
and the
          release.keystore
you made and put them in the same "stuff" folder. there should be 20 items total in here now.
get this:
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u30-download-1377139.html
          jdk-6u30-windows-x64.exe
do NOT use any other version, do NOT use version 7, use version 6.
install it all. then find it. should be here- (C://program files/Java/)
I recomend grabbing it all and putting it in your ROOT like this:
C://Java/jdk1.6.0_30/bin
then, put everything from the "stuff" folder into C://Java/jdk1.6.0_30/bin
yep, all of it.
now we are ready to get funky...
run cmd line.
open start menu, type
cmd
into the search bar, hit enter
-------- run command line, get to proper directory
cd ..
cd ..
cd Java/jdk1.6.0_30/bin
(or wherever your 'stuff' is)
--------open up
apktool d android-viewer.apk android-viewer
(this will make a folder called 'android-viewer' and you will be able to go into that folder and find the XML files in there)
--------edit XML
in file: /android-viewer/AndroidManifest.xml
open up in dreamweaver and change this stuff:
android:versionCode="_ENTER_NEW_NUMBER_" android:versionName="_ENTER_NEW_NUMBER_"
<supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true" />
in file: /android-viewer/assets/META-INF/AIR/application.xml
open up in dreamweaver and change this stuff:
          <versionNumber>_MATCH_ABOVE_</versionNumber>
          <versionLabel>_MATCH_ABOVE_</versionLabel>
<supports-screens android:smallScreens='true' android:normalScreens='true' android:largeScreens='true' android:xlargeScreens='true'/>
--------package it back up
apktool b android-viewer android-viewer-new.apk
(this will repackage the folder into a new APK, note the name -new.apk added to the end)
--------Sign
jarsigner -keystore release.keystore -signedjar android-viewer-signed.apk android-viewer-new.apk YOUR_ALIAS
(now you need to sign the -new apk and recreate it as signed)
--------Verify
jarsigner -verify -verbose -certs android-viewer-signed.apk
(if the last line does not say 'successfully verified' and there is an error, make sure you are using version 6 of JDK and not 7)
--------Update APK in play store
Visit this page
http://developer.android.com/distribute/googleplay/about/distribution.html#instant
read the line that says "Instant publishing, instant updates"
while you do, understand you are being lied to, it takes anywhere from 30 min to 4 hours for your update to be "instant".
take the new "android-viewer-signed.apk"
rename it, upload it, activate it, de activate the old one.
important: beofe you click save, switch over to the "product details" tab and update your version notes.
head over to your app page in the play store.
sit there and click refresh every 10 min or take a nap and come back in a few hours.
when you finally see the version number has updated, go to the browser on your phone
find your app in the browser, refresh the page, make sure its got the new version number on it.
install it on your small screen device, cross your fingers, and hope you do not get a message that says "not signed properly"
if you do, feel free to start googling the stuff above to see where you went wrong.
If it does work, go to your boss and have him download it and run it and say "see, there ya go, its on your phone now" and when he says it does not work hand him a minni screw driver and a 1.6GHz Quad-core from the Galaxy Note II and tell him to simply upgrade the procssor in his phone because its too slow. lol.
-good luck and enjoi

Answer 1

Hi,
This is very interesting.  I'm not an expert but i could do almost all the steps, but i can not do the sign step.  i dont know where my release.keystore is.  i created a .key.p12 file, is it?
I'm trying to do this for a Galaxy SIII
Thank you