View Single Post
Old 10-25-2011, 10:25 PM   #68
porkupan
Fanatic
porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.
 
porkupan's Avatar
 
Posts: 556
Karma: 1057213
Join Date: Sep 2006
Location: North Eastern U.S.
Device: Sony Reader
Well, that's true that many apps cannot be "installed" via normal install procedure due to a failure to create a secure container (logged error). However, some of those apps can still be installed via direct copy to /data/app. The only problem is, when the file is simply copied to /data/app, the proper install procedure is not carried out, so the native libraries, which may be needed for the app to operate, are not unpacked and placed in their correct locations.

There are a couple of tricks to installing such library-dependent apps. One may extract the library from the APK, and copy it into the /data/data/<app-name>/lib folder. That's not too difficult. Or one may install one version of the app, then remove it, and put another version into /data/app. Android is pretty smart to notice the upgrade (or downgrade), and follows the correct upgrade procedure.

For instance, if installing eBook Droid (the DJVU reader), we can do
Quote:
adb push ebookdroid_old.apk /data/app
adb shell rm -f ebook_/data/app/ebookdroid_old.apk
adb push ebookdroid_new.apk /data/app
porkupan is offline   Reply With Quote