Works on beta but not higher?
To fix this we need to get ARC arc-runtime-39.4410.139.0 from an Intel Chrome OS machine running something higher than beta channel.

Yup. See the resolution of #16.

@Flytomars- On OS X I'm running Version 39.0.2164.0 canary (64-bit) and ARChon works for me. So I'm not sure, I think a lot of issues with , it just shows up as an Android logo. are related to 32-bit machines

But still there might be Chrome OS dev machines that have arc-runtime-39.4410.139.0, not sure if it was released or not.

I guess on Windows 64 bit it doesn't work on any build higher than beta and in OS X it doesn't work on build below canary. Just an observation from various comments.

@subi54 I test it on my 64 bits Windows 8.1 with Chrome Stable 37.0.2062.120 m (64-bit), still not working here.

Below is the console message I got when I am using the ARChon runtime with the 2048 APK provided in this github:

ARC onInstalled HTML5 FS init: 631.000ms main.js:370
ChildPlugin jsInstaller:0:dexopt(so_executable) Run: 2005.000ms main.js:370
timeout to spawn ChildPlugin process: dexopt(so_executable), dexopt --preopt /vendor/chromium/crx/com.uberspot.a2048.android.apk $auto v=r,o=v,m=y,u=n main.js:370
retry to spawn with timeout 4sec. main.js:370
ChildPlugin jsInstaller:0:dexopt(so_executable) Run: 1286.000ms main.js:370
Dexopt plugin terminated main.js:370
ARC Window Popup: 66.000ms main.js:370
the child process has been loaded: so_executable/umareporter main.js:370
ChildPlugin backgroundpage:0:umareporter(so_executable) Run: 340.000ms main.js:370
0x7318EB09 is not a valid instance ID. main.js:370
Received a crash main.js:370
prod: ARC main.js:370
arc_app_name: com.uberspot.a2048 main.js:370
ptime: 60937 main.js:370
crash_time: Sun Sep 21 2014 19:54:48 GMT+0800 main.js:370
ver: 38.4410.120.25 main.js:370
arc_build_tag: arc-runtime-38.4410.120.25 main.js:370
message: heartbeat ping timeout main.js:370
chrome_version: 37.0.2062.120 main.js:370
app_id: kdjbiekcidfncdnaocdfbeflnpomjabn main.js:370
app_version: 1337 main.js:370
width: 360 main.js:370
height: 672 main.js:370
is_minimized: false main.js:370
is_maximized: false main.js:370
is_fullscreen: false main.js:370
Attempting to report crash... main.js:370
FINISHED REPORTING CRASH

@st6315 I am sorry, i am a noob, i just wrote what i observed. Even i started having some problem. I think Mr @vladikoff or @Flytomars- or somebody might be able to help.

@st6315 You could open a new issue or something, but I don't think here is the place to discuss it. @subi54 Thanks! I didn't realized OSX didn't have the problem. To be honest, I don't really know much about ARChon either.

@Flytomars- Oh. Really? You sure do know more than me. And from what I gather on OS X canary is the only build for now that is x64 hence it works. No x32 support whatsoever, for now.

As for now, the latest ARC runtime for x86-64 is 38.4410.120.28.

@niutech I Was looking at the diff, not much has changed it seems.

Is this fixed now?

@vladikoff Indeed, the new version basically added appWindow.contentWindow['arc']['runtimeUpdatedWhileRunning'], changed some *.so; *.nexe files and removed libLLVM.so.

Hi @vladikoff , ¿How i get the "ARC arc-runtime-39.4410.139.0" in my chrommebook HP 14?, Skype don't work (open but not sign in..... "initiating session"), tumblr, 2048, Games of thrones and others work perfect.

I try with ARChon 1.0 - 1.1 -1.2 for Chrome OS 64bit.
I have:
Versión 39.0.2171.94 (64-bit)
Plataforma 6310.61.0 (Official Build) stable-channel falco
Firmware Google_Falco.4389.89.0

Thanks!!!