Android Smartphone volume keys trigger gamepad discovery [FIXED]

[bluetrack]

Lately i noticed that on some Android smartphones pressing the volume +- keys triggers the gamepad discovery (async system gamepad). This is an issue for me since on AndroidTV when i discover gamepads i destroy the onscreen virtual keys. That means on some android smartphones by pressing the volume -+ buttons the virtual keys disappear. Is this a new bug, since i did not notice it before?

 

[Nocturne]

Can't say I've ever heard of this issue before. If you could create a test project and file a bug report that links to it then it'd be appreciated. Also try and mention as many devices as you can that you know show the issue...

 

[joakimFF]

Can't say I've ever heard of this issue before. If you could create a test project and file a bug report that links to it then it'd be appreciated. Also try and mention as many devices as you can that you know show the issue...

Can confirm that this happens in 2.1.4.200 on Samsung S6 and Note 3 if using the sample code from the official gamepad tutorial. It also seems like the "Android TV banner" 320 x 180 is not placed in the correct folder or simply not packaged at all if using the apkexpanion. As Google rejects the apk due to missing image.

 

[rmanthorp]

Hey, can you report this as a bug on APK expansion https://accounts.yoyogames.com/report-bug

also a separate one about the volume +/- coming in as gamepads

Thanks!

 

[joakimFF]

Hey, can you report this as a bug on APK expansion https://accounts.yoyogames.com/report-bug

also a separate one about the volume +/- coming in as gamepads

Thanks!

Okido Both issues have been reported.

 

[bluetrack]

Okido Both issues have been reported.

Great! Thanks joakimFF. I can only add then some android devices where it happens:
Nexus5X, Xiaomi Redmi 5, Samsung Galaxytab A6. Nexus5 on the other hand does not have this issue but it also runs marshmallow os; not sure if related.

 

[bluetrack]

Any news on fixing this bug? It is still there today.

 

[Nocturne]

This has been fixed internally and will be available in a coming update.

 

[bluetrack]

This has been fixed internally and will be available in a coming update.

Thanks Nocturne. Is this included in the latest release 2.2.2.326? I went quickly through the change log but did not see anything mentioned. I hope I just missed it

 

[bluetrack]

Thanks Nocturne. Is this included in the latest release 2.2.2.326? I went quickly through the change log but did not see anything mentioned. I hope I just missed it

So I 've tried it and the problem is indeed fixed (at least in a few devices that I tried).