Hello, I have been looking for possible solutions to repair a roms problem that I have for my device with Mediatek 6735 and I have crossported from MT6735, the strong problem that these roms have is that the physical buttons do not work, they have activated the bar of navigation, a single rom of 4 that I have ported the buttons work but in the other 3 roms nothing works, I have changed the file generic.rl and remain the same then, because of that I do not know where the problem comes from, the roms that I have ported from the Meizu M2 Mini Note device, for the ZTE Blade V6 device, the problem is the buttons I do not know if you can help me tell me where the problem of the physical navigation buttons comes from, since on the other hand the volume buttons and power, they work perfectly but the physical navigation buttons do not work, what could be the problem that only one works and in 3 do not work what will be the cause? I hope you can help me thanks.
Related
2 problems with picodrive. The directional buttens are screwed up. left is up en up is right and so on. I have solved this myself no prob just keep on trying finding the right button.
Next problem is with the ABC buttons of Picodrive. Al the alfabethical keys are mapped to the same keyadress so A=> 0xe5 B=> 0xe5
They al have the same function in picodrive.
Is this a problem regarding the Touch Pro or with picodrive or with a windows setting
somebody else on here has mentioned exactly the same problem with another emulator, so I guess the Touchpro somehow represents it's buttons as the same, either that or what you are seeing is the response from the touch screen not from the button (as was proved in another thread the whole area is touch sensitive not just the screen) in which case turning off the touch feature might sort you out.
Its not the screen im talking about. It is the keyboard.
same with final burn
have the same problem with finalburn (mame emulator). Every key from the keyboard except the directional keys, enter and 2-3 others is beeing mapped / recognized as 0xe5
does somebody has a fix?
Besides that problem - has anyone been able to play either of those emulators to evaluate speed?
I'm concerned that the Qualcomm processor coupled with the VGA screen will result in slow performance.
I'm debating getting this phone, but wouldn't want to if it's too much of a drop off from my 6700.
The speed isn't a problem. Runs flawlessy. The applications are still buggy under some other aspects. But I wouldn't buy myself a device in order to run these emus. There are cheaper ones on the market.
Back to the problem with the keymapping...
I hard resetted the device and skipped the extended rom installation. The problem with the keymapping is still there. Therefore I can exclude the applications in the extended rom causing this problem.
Anyone some advices, fixes or workarounds?
no key mapping
key mapping is weird yes.
Mate of mine has the tytn II with a pocketSNES i loved it And i was in need for a new phone... HTC touch pro / raphael / MDA vario IV was a phone i really looked out fore for a while nice design etc etc etc ... just the key mapping for an emulator is a big .. down for me
Any fixes?
same problem here:
http://forum.xda-developers.com/showthread.php?t=420159
and
http://forum.xda-developers.com/showthread.php?t=425646
SOLUTION HERE: http://forum.xda-developers.com/showpost.php?p=2703133&postcount=3
Hello,
My Raphael 100 dpad buttons are not working in android roms!
I can't go 'back' or to 'home' in Android
"Home" button and "call" button act as navigation key (left)
"back" button and "call end" button act as navigation key (right)
I have tried numerous roms (neofroyo, thunderbolt, hercules, cbv2, cherrypie and more), even non-cwm roms (frx07, froyob v5, v6)
Non of them worked
I also tried with several different kernels (very old, old and new) but still same.
Does anyone have solution for this?
Haven't had that problem in a while but then again I haven't really played with XDAndroid about that long. Even still, never had that much of an issue. Usually I could just cycle the screen off then on and the problem was gone.
Is it possible that you are constantly sliding across the buttons? I know I can get it to go crazy after sliding across the buttons a few times...
No its completely not working only in android roms as if the keys are not mapped
I even tried FRX03 (which was working fine couple of months back in the time) but somehow the keys are not working now... really strange
That's a new issue to me. I take it the d-pad works in winmo but not after you boot into android? Have you filed a bug report yet?
Curious, does the screen react to touch?
Curious said:
Nope it doesn't light when I touch dpad
Click to expand...
Click to collapse
So the d-pad doesn't work in winmo or does it?
it works ! but will take full advantage of your d–pad, your driver must generate the proper virtual key codes ~ http://msdn.microsoft.com/en-us/library/bb821761.aspx
I have a generic A10 tablet (iRulu brand) that I recently flashed with CM9 (this thread here)
So far so good but the Back, Home. and Menu buttons are not working.
These are not physical buttons. They are basically built into the lower part of the touch screen.
I tried adding the keymap files from my stock rom to /system/usr/keylayout but this did not work.
Anyone else know where I can enable these buttons?
Ok, got this figured out.
The buttons are defined in the module for the touchscreen (ft5x_ts.c)
Lucky for me, a modified module was already available.
I own an S7 Flat , and my Physical power button is about to stop working (I can even feel it) in the past with my previous owned phones there was always a way for developers of custom roms to add some lines in the SystemUI.apk to create a virtual power button in the statubar.
on the S7 I found no such feature in any custom ROM and Iam an Android NOOB Can anyone be able to include that feature if i provide the stock SystemUI.apk I would really appreciate it and Iam thankful in advance
For two weeks the on-screen keypad of this model does not work correctly, from one moment to the next it stops detecting the pulsations. Pass with any of the buttons and I have seen the problem in more than one unit.
If you use the "Gestures on screen" you have no problem.
Someone have the same problem? I think it can be MIUI 9.6.2