Apps do not start - Githubissues

Rudloff commented 8 years ago

Hello,

I am using ARChon 1.2 with Chromium 47.0.2526.80 on Debian 8.2. Every app I try (including the sample app) gets stuck on the loading screen: capture d ecran - 07012016 - 20 20 27

GeographicCone commented 8 years ago

Hi,

I have just started using Archon (excellent software, thanks a lot @vladikoff) and experienced a similar issue, which as improbable as it seems, turned out to be caused by being connected to Bluetooth speakers.

In my case, the screen would actually turn black with a white crash icon in the middle if you waited a little longer, and there would be an entry in the log saying Unknown namespace 'androidHeartbeat' for command 'ping'. Unless you added a manifest keyisSlowDebugRun": true, in which case it would remain forever at the screen like you posted, without the heartbeat error and no other relevant messages.

My issue was resolved by switching Bluetooth off and reloading the extension.

A similar issue was identified and resolved in Chromium sometime ago: https://code.google.com/p/chromium/issues/detail?id=472716#c9

Also this issue seems to be related, and seems to have been resolved by switching to 32-bit Chrome (I am on a 64-bit build): https://github.com/vladikoff/chromeos-apk/issues/94#issuecomment-58522462

The thing happening to you @Rudloff might be something different altogether but reads remarkably similar, so hopefully this provides some guidance.

Once again thank you for the awesome piece of software @vladikoff. If the fix I referenced above could be ported from ARC, it'd be great to have it in some future release of Archon.

Version numbers for reference: ARChon 2.1.0 Beta (ARC 41.4410.238.0) Chrome 47.0.2526.106 m (64-bit) on Windows 8.1U1 x64 Also tried: Chrome Canary 49.0.2617.0 (64-bit) to same effect

Edit: after writing the above I realized that @Rudloff is reporting is a Linux issue, so it's probably something unrelated to what I had then, sorry for the confusion.

Rudloff commented 8 years ago

Thanks @GeographicCone, but I don't have bluetooth on this computer so I guess it is a different bug.

GeographicCone commented 8 years ago

Just to clarify, it's not about Bluetooth at all but about certain kind of audio drivers (apparently, those sending audio to a remote device in particular) triggering Fast Mixer in Android, which is not implemented in ARC/Archon:

At the time AudioFlinger creates a normal mixer thread, it decides whether or not to also create a fast mixer thread. Both the normal mixer and fast mixer are not associated with a particular track, but rather with a set of tracks. There is always a normal mixer thread. The fast mixer thread, if it exists, is subservient to the normal mixer thread and acts under its control. https://source.android.com/devices/audio/latency_design.html#mixerThreads

It appears as a solution to this bug Fast Mixer path was disabled altogether in ARC. @vladikoff might consider doing the same in Archon, which would allow people such as myself to use Bluetooth speakers and an Android app at the same time.

I posted here because your bug seems to have very similar symptoms although we don't really know since you didn't post the logs. If I were you, I'd do that, and also check if it reappears with different versions, such as Archon 2.1.0 branch, Chrome Canary / and old version / 32-bit if you're on a 64-bit. (Just a suggestion, anyway.) Good luck.

Rudloff commented 8 years ago

I can reproduce with ARChon 2.1.0 beta. Is there any log file I can provide to help diagnose this?

Neoramasay commented 8 years ago

@Rudloff - what process are you using to package an APK for use with ARChon? ARC Welder or Twerk (both Chrome apps also), or are you using ARChon Packager on a phone, or some other method? Also, what apps are you attempting with?

In addition, are you on 32-bit or 64-bit version of your OS? I have found that as long as you are on a 64-bit OS, even if you are on 32-bit Chrome/Chromium, you can use the 64-bit ARChon extension (and rightly should use it!). Also, the 1.2 Stable ARChon worked better for the apps that I have worked with, 2.1.0 beta caused them to crash at various stages of operation.

Rudloff commented 8 years ago

I use chromeos-apk to package the apps, but it does not seem to be relevant because even the sample app (which is already packaged) does not work.

I use a 64-bit kernel and a 64-bit Chromium. I tried the 32 bit version of Archon but I get the same behavior.

Neoramasay commented 8 years ago

Just out of curiosity, have you attempted packaging apps with ARC Welder, letting the ARC Welder Chrome app install the standard ARC run time? Does that yield any different result?

Rudloff commented 8 years ago

I get a similar behavior with ARC Welder. It stays forever on this screen: capture d ecran - 02022016 - 22 00 17

Neoramasay commented 8 years ago

If ARC Welder also won't complete packaging, then this is definitely something on a larger scale than just ARChon. Given that, I might try with Chrome, as opposed to Chromium to see if that yields any different result...

tulakalbeyo commented 8 years ago

i also have this issue. i'm using "ARChon Custom Runtime 2.1.0 - x86_64 41.4410.238.0" on chromium (version 48.0.2564.82) on xubuntu 15.04 vivid, on an asus 1225B 32bit netbook. i will soon upgrade to xenial. perhaps that will help (newer chromium build, etc) ??

EricGebhart commented 7 years ago

I have the same problem. Even the sample app which is pre packaged shows exactly the same window you showed. Every app I try does exactly the same thing. But I would expect the sample to work. I've used chromeos-apk to convert packages. all sorts of various ones all with the same result.