search

AtomicAcidbath / imame4all

Automatically exported from code.google.com/p/imame4all
1 stars 0 forks source link

Much i5 Device, cannot disable touch interface, because show constantly emulator menu #272

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. disable touch screen controls
2. back to interface to select game
3. without pressing nothing, the system show the menu config.
4. if i close the menu, this show up again, constantly.

What is the expected output? What do you see instead?
usage normally the emulator with device controls.

What version of the product are you using? On what operating system?
1.4.4

Please provide any additional information below.
I'm Deen0X. You can contact to me if you need any direct data from the device 
itself.

Original issue reported on code.google.com by dino.s...@gmail.com on 1 Oct 2013 at 9:47

GoogleCodeExporter commented 9 years ago 
Hola DeenOX. :)

It's strange. Try to do a complete MAME4droid unistall. Try again before you 
redefine Much buttons. Beware. There is a binding button to show up MAME4droid 
menu.

Original comment by seleuco....@gmail.com on 1 Oct 2013 at 10:23

GoogleCodeExporter commented 9 years ago 
May be Mame is registering small inputs on analogs and take this as some kind 
of action to show the menu?

This device don´t have native joystick support, but the sticks are true 
analogs and may be are sending some kind of data that the emulator is 
considering in some way to show the menu interface?

i tested, reinstalling the app, opening and disabling the on screen controls 
(without mapping nothing), and the menu show again.

Original comment by dino.s...@gmail.com on 1 Oct 2013 at 10:46

GoogleCodeExporter commented 9 years ago 
There is an option to set the analog dead zone value. But to take effect. 
mame4droid has to detect as a analog device. Try to unbing menu key from 
default value to none or other one.

Original comment by seleuco....@gmail.com on 2 Oct 2013 at 10:47

GoogleCodeExporter commented 9 years ago 
hi Seleuco!
sorry for the delay.

I do many tests trying to get a clue about what happening.
1- i unmap ALL buttons from ALL gamepads, but the problem persist.
2- i test using Tincore Keymapper to map the analogs and disabling them from 
the program. Only let the D-PAD enabled. Mame can map correctly DPAD (and 
nothing more, because i disabled all other inputs) but the problem persist. (i 
do the same test disabling analogs on mame)
3- I enabled "show touches" to check if there is any ghost touch, but there is 
nothing. the problem persist.
4- I enable "show pointer location" to check if there is any ghost pointer 
(mouse) that is generating some input. Then go to Mame, do a swipe on screen to 
stablish a Last pointer location visible (if there is any other pointer 
location, my swipe will disappear), but the problem persist (and there is no 
pointer location changes)
5- Opened Keytest app to check if there is any ghost key that is spreading to 
the system, but i don´t see anything.

I don´t know how to do more testing. If you need more specific testing, let me 
know.

Take note, this device don´t have a real joystick driver. The analogs are 
handled by a private driver. May be Mame is reading something on the system, 
and this is the same value that system is using for analogs? (sorry, i don´t 
know how to determine this. is only a suggestion/question)

Original comment by dino.s...@gmail.com on 3 Oct 2013 at 7:47

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
switch to software render and tell me if the problem is gone...

Original comment by seleuco....@gmail.com on 4 Oct 2013 at 11:11

GoogleCodeExporter commented 9 years ago 
Hi!

Yes, the problem gone if i use SW render.

Original comment by dino.s...@gmail.com on 5 Oct 2013 at 8:50

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
As I was thinking your bug is related to jelly bean lights out mode. Probably 
Imuch is having issues hiding the navigation bar and is related to inacurate 
event delivery.

Original comment by seleuco....@gmail.com on 5 Oct 2013 at 9:20

GoogleCodeExporter commented 9 years ago 
To clarify, light out mode is implemented on gl view. Sw view is as simple as 
possible to be as compatible as possible.

Original comment by seleuco....@gmail.com on 5 Oct 2013 at 9:24

GoogleCodeExporter commented 9 years ago 
Ok. i do some testings.

The device only have the top status bar (notification). There is no bottom

https://lh6.googleusercontent.com/-htDQqDEvZqs/Uk_beW7xvMI/AAAAAAAAJ_c/JmwlEPUGk
w4/s800/MUCH_20131005_112327.jpg

With this, in HW mode i get the message constantly

https://lh4.googleusercontent.com/-zx7UQ-0dC80/Uk_beeMTM6I/AAAAAAAAJ_o/3AfQvlOFw
Hs/s800/MUCH_20131005_112340.jpg

I have GDM Testure App, that there is an option to hide Status bar

https://lh3.googleusercontent.com/-8Nrpbhm6Eh8/Uk_beS0yEEI/AAAAAAAAJ_k/F-BUZcPLq
aE/s800/MUCH_20131005_112358.jpg

With this status bar hidden, start Mame and i can play without issues.

https://lh4.googleusercontent.com/-AKmh-bjj1rU/Uk_bfNFgVjI/AAAAAAAAJ_s/NR-GNQSII
pg/s800/MUCH_20131005_112409.jpg

Then, you right. the problem is related to light out mode (i understand this 
mode is no status bars or similar, to get full screen for an app)

let me know if you need more testings.

Original comment by dino.s...@gmail.com on 5 Oct 2013 at 9:32

GoogleCodeExporter commented 9 years ago 
Really the problem is on the Imuch side, as it is working on nvidia shield 
(which dont have navigation bar also) and nexus 7. Without proper testing I 
can't develop a workaround. Anyway sw render runs pretty fast if not is enabled 
filtering.

Original comment by seleuco....@gmail.com on 5 Oct 2013 at 9:42

GoogleCodeExporter commented 9 years ago 
or using any app that hide the bars (GDM Gestures or Full!Screen) before 
launching the app may help.

Original comment by dino.s...@gmail.com on 5 Oct 2013 at 9:48