sorry no solution but yea ive been bugging my apple mates about this when asking them to help test my apps. my fullscreen button dosent work on ios and none of my buddues seem to know another way to go fullscreen. so yea + one me on this, ..I would also love to know.

you say your game is supposed to be horizontal but your view-port aspect ratio is portrait (9:16)?

<edit> just ignore me its been a long day...

FYI Google are now tracking this as a Chrome issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=1014614

Oh... I raised my bug on the Android tracker but they closed it to track the issue against this bug in the Chrome tracker instead. But they stated that the bug is in Android ?? (reporting too high latencies to chrome) not in Chrome?. Unless they have maybe resolved the issue in latest Android?

Hmm , I dont know. But it is good that Google have at least acknowledged the issue and are looking into it. (Although you would think a company the size of Google would be all over these sort of issues long before joe public starts to raise them, makes me a little nervous about the organisation there.).

Ok Constructors. More information on Android + Audio + Chrome / Webview audio lag.

So, according to Google.

Chrome assesses the device capabilities based on Android OS returning a value for baseLatency

this value

BaseLatency TEST http://rtoy.github.io/webaudio-hacks/tests/osc.html

if the value is "high" Chrome adds a ton of latency into the audio path to avoid audio glitching.

apparently the value returned is erroneously too high (far too high) on most of the Android phones currently out there. even on powerful phones capable of much lower latency.

This is where the 300-400ms lag is coming from.

Ive noted on the two phones I have direct access to

Cubot power. Very little lag on the app.website , returns a baseLatency of 256 frames

On the MOTO G5. 300ms lag on the app/website/ returns a baseLatency of 3200 frames.

Cheers tarek2 youve been super helpful there.

ive raised a bug report. https://github.com/Scirra/Construct-3-bugs/issues/3457

Ive linked to your vids but if you want/need to delete those video let me know and I can stick them on my gdrive no problem.

Im thinking I could get an Ipod for now so at least I could test websites on IOS apparently they have the same chipset as an iphone 7. But will just wait to see what Ashley has to say regarding this. As it may be again outside his control. If so then its back to desktop apps or I have to learn to program with JUCE.

edit< just been down the apple store, ipods are tiny! Too small for major gaming or music apps. Maybe just good as music player. So I await see what Ashley say.

OK then cheers, I will try to raise with the G men for FWIW.

I still love construct BTW.

Blizzcon / Overwatch 2 OMG ! 😮😮😮

Ok, this is my first venture into Android mobile land with Construct 3 but I must admit Im a little shocked.

Before we kill this thread off only to be resurrected by the next poor sucker who ventures down this road.

Please Ashley if you could confirm the following.

1) You are essentially saying that 300-400ms sound lag is normal and accepted on android games on what must be over 90% of devices?

a. If this was the case then I don’t think anyone would be playing games on android. I have just played geometry dash on 2 of the offending devices and there is no perceptible sound lag when dying or when entering a portal. (I would estimate it is under 3 frames at 60fps)

b. The superpowered website is talking about a general RT lag of 30-50ms for 99% of android devices , this would be acceptable and almost non perceptible for most gamers however this is 10 times less than what we are seeing with the Construct exports something dosent add up?

c. If you are saying that 300-400ms is generally the accepted norm with Construct 3 games or mobile javascript games in general (and only native can give you low sound lag) then you are admitting that Construct 3 games on android are not actually viable. Is this so?

2) The superpowered website are selling Javascript audio libraries that boast very low latency.

a. Can these be uses with construct scripting?

b. Could similar tech be used for Construct audio?.

3) The superpowered website database shows that IOS has low sound lag on all devices. Like less than 12ms on most of the range as compared to the 30-50ms on android. Which is why it is the choice for audio applications I assume.

a. But do construct games also display this low latency on iphones. Or is there an extra 250-350+ milliseconds added into the path like on android? (I ask As I am ready to ditch Android and embrace apple if this was the case)

so far pretty much exact same lag showing in 7 , 8 , 8.1 and 9 on devices tested.

Currently showing lag on 9 on S8 (as shown in tarek2s demo above and linked on the bug report)

so unless someone can show otherwise Im going with the current evidence.