Package Details: archon 2.1.0-9

Git Clone URL: https://aur.archlinux.org/archon.git (read-only)
Package Base: archon
Description: Execute Android APKs
Upstream URL: http://archon-runtime.github.io
Licenses: custom, Apache
Submitter: prurigro
Maintainer: syncrtl64
Last Packager: syncrtl64
Votes: 33
Popularity: 0.998881
First Submitted: 2014-09-26 11:25
Last Updated: 2016-07-03 13:13

Dependencies (6)

Required by (1)

Sources (2)

Latest Comments

sirHermit commented on 2017-01-02 18:18

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

kuba77 commented on 2016-11-02 10:41

Since Chromium 54 doesn't work.

prurigro commented on 2016-06-28 04:39

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

when i execute this the sha512 for v2.1.0-x86_64.zip is:
b0ad6080f4c4ededef52d1a030e30c54e0dd67a945d39f3018499a674e07807bfa5e334b2088d88b90ff7931715f99aa8324dcc59a84ab600b3612ad4135d044

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

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

@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 @ https://gist.github.com/PedroHLC/606da5b1bc3a141fee30
* 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: https://aur.archlinux.org/packages/archon-exec
* 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

Here it's, archon packed and installed as an external extension loaded for all users:
PKGBUILD https://gist.github.com/PedroHLC/606da5b1bc3a141fee30

If you put your "archon.sh" 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

@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

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 https://wiki.archlinux.org/index.php/Arch_packaging_standards#Directories
* 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

@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 https://www.reddit.com/r/chromeapks ; while yours installer/manager app (archon.sh) 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??

All comments