Package Details: archon 2.1.0-9

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

Dependencies (6)

Required by (0)

Sources (2)

Latest Comments

sl1pkn07 commented on 2022-01-15 21:22 (UTC)

seems need installed like


iib commented on 2022-01-09 11:20 (UTC)

Can you explain normally how to use it? I don't have an android phone. And besides, all the links are broken in google play and there is no twerk

doragasu commented on 2020-01-21 12:47 (UTC)

Is there any way as of today, to run this on an up-to-date Arch installation?

haldrin commented on 2019-03-13 13:08 (UTC)

In "" show the message: "It appears you don't have permission to access this page. 403 Error. Forbidden."

maybe better to change the url's address to:

elka commented on 2018-09-10 18:30 (UTC)

Hello. Why I don't see any armv7h's sources?

sirHermit commented on 2017-01-02 18:18 (UTC)

It doesn't work on Chromium 55.0.2883.87 (64-bit).

kuba77 commented on 2016-11-02 10:41 (UTC)

Since Chromium 54 doesn't work.

prurigro commented on 2016-06-28 04:39 (UTC)

Hey all- I haven't been using archon for a while now and I don't have any big plans to start using it again, so I'm going to disown this in hopes that someone using it more regularly can pick it up and give it the proper maintenance it deserves!

soloturn commented on 2016-06-05 19:47 (UTC)

when i execute this the sha512 for is: b0ad6080f4c4ededef52d1a030e30c54e0dd67a945d39f3018499a674e07807bfa5e334b2088d88b90ff7931715f99aa8324dcc59a84ab600b3612ad4135d044

Alister.Hood commented on 2015-08-15 05:39 (UTC)

Has anybody ever got this to work on x86? I just get this error when I try to load an app: 'import' extension is not installed. And if I try v2 I get a window showing just an android logo.

prurigro commented on 2015-01-14 03:24 (UTC)

@PedroHLC: Thanks for putting that together! You saved me a ton of time digging through forum posts and documentation :). I ended up making a few additional modifications to where you left things before pushing: Changes for archon-(1.2|2.0.0)-7: * The initial set of changes come from PedroHLC's PKGBUILD update @ * As per PerdoHLC's recommendation, the APK launch script and .desktop file have been moved into a separate package that this one has as an optional dependency: * The extension file is installed to /opt/archon/archon.crx, and the metadata file in /usr/share/chromium/extensions/ points to this location * The metadata file is also installed to /usr/share/google-chrome/extensions/ so google-chrome can load ARChon as well * In addition to the extension file, the unpacked ARChon app directory is installed to /opt/archon too, allowing ARChon to be launched directly (without going through the chromium/google-chrome interface) as well as lots of other fun things you can't do with a packed extension. Anyone have thoughts on the best way to set things up?

PedroHLC commented on 2015-01-11 17:30 (UTC)

Here it's, archon packed and installed as an external extension loaded for all users: PKGBUILD If you put your "" on a github repo, I won't care adding some of the features I once commented here....

prurigro commented on 2015-01-11 13:01 (UTC)

@PedroHLC: I agree with your point about how ArchLinux packages generally work. That said, the reason I originally went with the script solution instead of a vanilla install + separate launcher package was because I'd only been able to find a way to install chromium extensions into the user config folder (~/.config/chromium/Default/Extensions for chromium) like the method described on the sidebar of that Reddit page. To use ARChon after installing it as a system-wide package, I needed to find a way to trigger its functionality directly like the script I wrote does. So my question to you is: do you know of a way to install ARChon in a system folder and have chromium for each user detect and include it as an extension? I feel like a vanilla ArchLinux package for ARChon might not make the most sense without a way to do this. In respect to the chromeos-apk-git dependency; ARChon does not depend on it to function beyond requiring its use to convert APKs before they can be run. The dependency in this package assumes the requirement of a wrapper script like the one I've written to be useful as a system package, and would no longer be the case if we came up with a way for the archon package to install ARChon as a system-wide extension.

prurigro commented on 2015-01-11 12:09 (UTC)

Updates in 1.2-6: * Version 2.0.0 is now selected for x86_64 (other archs are still at v1.2) * A new prepare() function has been added to increase application font size by 1.2 times (the default font size is too small when run on my configuration, though let me know if this isn't the same for everyone and I'll look at other options) * The ARChon folder is now installed to the /opt directory as per * The /usr/bin/archon script has been cleaned up and improved a bit, as well as updated to reflect the new ARChon location in /opt * Support for arm and armv6h has been dropped after reading that the v1.2-ARM branch is built to support Chromebooks (armv7h) * The license files in /usr/share/licenses/archon are now symbolic links rather than copies If anyone knows of a better way than the hack I've used to provide v1.2 for armv7h+i686 and v2.0.0 for x86_64, I'd be interested in hearing what that would be :)

PedroHLC commented on 2015-01-11 11:44 (UTC)

@prurigro: I haven't yet be able to use archon, it only shows me an android splash screen and closes it self in any apk I use. I believe this package should just build and install the archon as a chromium extension as described in ; while yours installer/manager app ( should be moved to another package - that's how ArchLinux packages generally works. Also, is chromeos-apk really a archon dependency, or only from your manager??

prurigro commented on 2015-01-11 08:32 (UTC)

@ricardomv: Hmm, I haven't had to do that myself (just tested with the latest chromeos-apk and both -a and --archon seem to do the same thing)- How come you needed to change the flag? (Is whatever it fixes more subtle than simply being the difference between working and not?)

prurigro commented on 2015-01-11 08:27 (UTC)

@PedroHLC: I ended up getting busy after we talked last, and then had a bit of trouble deciding on the best direction to do things once time was a bit more free again. I figured I'd start by updating and cleaning up the current logic, then play around a bit to see where to go from there... One thing I've been finding is that a lot of applications haven't been saving their settings, and I'm not sure if that's because of how things are configured or because of an issue upstream with archon (I'm running into this with the 2.0 version for x86_64 only too)- have you run into this and/or found a solution to the issue?

ricardomv commented on 2014-12-31 08:16 (UTC)

had to edit /bin/archon to get it working changed line :17 "chromeos-apk --archon ..." to "chromeos-apk -a ..."

PedroHLC commented on 2014-12-30 13:03 (UTC)

Still waiting (your github project || at least a gist)...

prurigro commented on 2014-12-15 02:06 (UTC)

@Allister.Hood: can you test this latest update, which no longer attempts to strip anything? I'm not sure why the i686 repo has x86_64 nacl in it on that note...

Alister.Hood commented on 2014-12-08 14:55 (UTC)

Something isn't quite right, because it spits out a bunch of messages like this on i686: strip:./usr/share/archon/_platform_specific/nacl_x86_64/ File format not recognized

prurigro commented on 2014-10-29 00:35 (UTC)

Another improvement I'd like to make but haven't found a solution for yet is to find a way for the font to be configured, or at least resized. I'd be interested if you have any ideas as to how that might be done. I might make this info a github project btw, so ideas and issues can be better tracked, instructions can be more clear than they currently are, and to open tbe doors to collaboration.

prurigro commented on 2014-10-29 00:28 (UTC)

I like the sound of most of those suggestions. Doing something more along the lines of an installation would definitely feel less like a toy than it does in its current state, and it would mean the installer could manually generate proper .desktop files with the apk's icon file and the correct path too, not to mention that it wouldn't need to worry about keeping track of app versions, since installing again could just replace the current one (since this wouldn't be happening regularly). I couldn't figure out what was creating the generated .desktop files btw, which is why I'd added that hack that removes them in the script, assuming it was likely chromium which would be a huge pain to patch, but of you know them to be originating from chrome-apk, or of a flag that can be passed to chromium to skip that step, I'd be happy to have a proper fix :) Let me take a look at all this when I get home. Cheers for the kindred interest!

PedroHLC commented on 2014-10-28 20:22 (UTC)

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

PedroHLC commented on 2014-10-28 20:10 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

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 :)