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.
Related
Hi, I recently replaced the screen on my Samsung Vibrant because the previous screen had broken. Unfortunately, I had mistakenly taken the sensors for the 4 main function buttons with my efforts. As such, I was wondering if anybody knew of an app that would replace these 4 function buttons through a software solution? Possibly an app that places them in the pull down menu as an ongoing program?
Interested in this as well. Although I do still have working volume keys, those could be mapped to one of the other functions. But I'll start a new thread on that elsewhere.
If there isn't an app, can anybody think of a workaround?
I upgraded to PRIME 1.5 and tried to change my keymap to dvorak using the instructions on this site (can't link to thread because I'm too new). I since changed the asusec.kl and qwerty-en_US.kl files back to what they were when I found them. Now I've found that the majority of the special keys don't work on the dock. The only ones that do work are Browser, Skip Back, Play/Pause, Skip Forward, Mute, Vol Up, and Vol Down. None of the other keys works.
If the tablet is locked, none of the keys unlock it like they used to. It's almost like the Generic keyboard is being used instead of the asusec.kl file...
Has anyone else run into this? Suggestions?
I reinstalled PRIME and didn't install the modified dock widget and now the special keys work again. My guess is the modified dock widget isn't exactly the same code as the existing one and it doesn't take into account that it's not a stock keyboard. Guess I'll just have to forgo having the dock battery % in the bottom right.
Hi there,
my HTC One S (ville) fall down and the display was broken completely.
I bought myself a new a one and have build it in. While replacing the screen I screwed the Flex cable which is responsible for the hardware buttons at bottom (and the sound however).
I also got a new flex cable and replaced the old one.
1) Problem
When I restart my phone the buttons at the bottom work, until I get into lockscreen. After that they won't work anymore, I don't know why. (Only restart helps, again they work only until I got into lockscreen).
2) Workaround-Problem
So, as a workaround a decided to install CM10 to use the navigation bar (I set qemu.hw.mainkeys=0 in prop.build before I flashed the rom).
Now I have the problem with the menu button. The 3-dot menu button shows up but has obviously no function. When I click on it nothing happens - I can't access any settings menu in apps.
I tried also Virtual Button App - either there the menu function does not do anything.
Of course I rooted my phone etc...
Is there something special with the HTC ONE S and the menu button function?
Thanks very much in advance,
Maik
I know it may be stupid but I want to test something. So is it possible to get hardware and on screen buttons working at the same time on rom like cyanogenmod 12.1 where is no option in settings to choose that? I found some old forum thread where was told to edit build.prop file but I tried it and I got only lights on hardware keys but buttons doesnt work.
Well... It can, if you are using blisspop rom...
But why you want to turn both on ?
First, enable hardware keys through settings. Then with a root explorer/file manager, edit the file system/build.prop by adding "qemu.hw.mainkeys=0" at the bottom.
Have you tested this? If I remember right, this is the way to get those lights working but not buttons.
Hi all, hoping someone is able to help with the below issue.
Have a Xtron TB706PL, currently the volume up button is not working.
All other buttons work fine, pressing the Reset button briefly mutes the unit on/off, long press resets the unit.
The unit was working fine when I first picked it up, but bluetooth was not working in terms of finding devices.
Did a dmcu.cfg update using the file from the link below, and the problem with the volume button began after that. Unfortunately I did not back up the system dmcu.cfg correctly as I saved it to flash instead of GPS (SD Card) before the change.
Managed to get the bluetooth finding devices though.
Any way of getting the factory dmcu.cfg?
Is that most likely the issue?
https://forum.xda-developers.com/an...development/bluetooth-xtrons-tb706pl-t3703730
Running Android 6.0.1
MCU Version MTCE_GS_V2.84_1
Cheers,
Have you tried assigning button in factory settings?
Thanks marchnz for the reply.
I believe I have got the correct process, but could be doing something wrong.
I have gone to factory settings and reset the key panel, then when I go to key panel study, pressing any of the four input keys does nothing at all, as if it doesn't register the press. Nothing appears on the screen to allocate the function for the key. I have seen other people's videos on how this is meant to work but doesn't for me.
As a new member, can't link any think yet.
YouTube search:
Touch-screen calibration and touch button program for PX5
(Be sure to touch the "red" mark!, I did it backwards messing around and caused my touch input to be all inverted)
Try this, I did the same thing on my Dasaita unit.
Note: (at least for my unit) don't program longpress function...it won't take it and thus default you back to square one (no working panel buttons)
Hope this helps
Sent from my SM-G955U using Tapatalk
Guys, thanks for the help and advice!!!
Doing what Hkw84 advised resolved the issue, video made things clear.
I was using panel key study in trying to setup the keys and not the touch key study which makes complete sense now as the keys on my unit a touch sensitive like the screen...doh
Appreciate the help, deciding if i should upgrade to malaysk Android 8 now
Cheers,