Package Details: archon 2.1.0-9

Git Clone URL: (read-only)
Package Base: archon
Description: Execute Android APKs
Upstream URL:
Licenses: custom, Apache
Submitter: prurigro
Maintainer: syncrtl64
Last Packager: syncrtl64
Votes: 38
Popularity: 0.002709
First Submitted: 2014-09-26 11:25
Last Updated: 2016-07-03 13:13

Latest Comments

« First ‹ Previous 1 2 3

PedroHLC commented on 2014-10-28 20:22

forgot the most important:
+change name from apk hash to package name

PedroHLC commented on 2014-10-28 20:10

This one method it's better, but I think it would be more interesting with this suggestion:
+rename archon script to "archon_apkinstaller".
+instead of deleting the xdg desktop file, patch it.
+instead of giving folder a hash as name, create one file ".version" with apk hash as its contents.
+instead of checking if folder "${ARCHON_TMPDIR}/${SUM}" exists, compare apk hash with the one in ".version".
+also ".version" file should only be created after conversion finishes, so we be sure conversion was successful and we do not have an empty folder
+stop linking apk, I might like moving it around thousands of times.
+chroumium-apk some times fails to get some package info and starts making some question, we are unable to see those and from terminal it seems like script just freezed.
+not use /tmp as its uses tmpfs by default which is space limited and clean after each reboot

prurigro commented on 2014-10-28 06:30

@PedroHLC: Not really actually. The instructions on the site expect archon to be loaded as a Chromium extension, which I believe is only possible to do in userland. Instead, to run a Android applications with this package you should execute the archon script with an APK file as an argument (eg: ]$ archon Application.apk), or if you're using an XDG-compliant desktop like Gnome, KDE, etc, you can double click on the .apk from a file manager as well.

The configuration stays separate from your Chromium config in ~/.config/archon, and each .apk gets its own config directory within that based on its application name (ie: The APK file *is* extracted and converted, but in a temporary folder in /tmp/, which will be used as long as it remains there and regenerated as soon as its gone (and it uses the md5sum of the .apk file to identify the temporary application folder to use, so different versions of the same app are doable).

If you want to go the traditional route, you should just install chromeos-apk and then install archon as an extension, but I'd recommend trying this method before deciding. :)

PedroHLC commented on 2014-10-27 23:14

Are the instructions to use the same as the ones explained in the official git??
I haven't be able to run the example game (crashes after an android appear on my screen), my archon automatically removes itself from extensions when I remove any other loaded app; also, as its installed into system, shouldn't it be forced to be on Chromium extension list, instead having to be added by the user? (I mean, at least mine is not in extension list when I open Chromium)

prurigro commented on 2014-10-24 08:48

The latest revision I posted earlier should handle the 'There is no "message" element for key extName' that started popping up instead of the .apk executing after upgrading to one of the most recent versions of chromeos-apk-git. It won't hurt anything once the issue is fixed upstream, but hopefully posting this has the added effect of reminding my future self to check periodically and see if it can be removed :)