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.
Related
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.
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
First, just want to say thanks for the development on the Note Pro. CM on this thing is awesome. That said, I still have a couple of lingering issues, hoping someone may have found some work arounds/solutions. Inevitably there will be someone that will reply with "USE THE SEARCH!". For those that do, I will offer you my sincere admiration. Your search foo is only exceeded by your wit. For those that are still willing to read on and assist, know that I've come up empty in my search attempts. Believe me, I'd rather have found a simple search result than to have typed all this up... In any case:
1. Hardware keys and navbar -
CM has a setting for "Enable on-screen navigation bar and disable hardware buttons". Checking this box enables the navbar, but fails to actually disable the capacitive and physical buttons. This causes me some grief when using the tablet in portrait mode. I've tried hacking around in the build.prop and the Generic.kl files, but haven't found that magical combination of new lines/commented out lines. Maybe CM does this differently than other roms? (I've not observed a difference in these files when toggling back and forth in the settings, so there must be something else I'm missing.) Any pointers?
2. Key Mapping -
I have the Logitech Pro Keyboard Case. Seems to work well, for the most part. (I'm typing on it now...) However, not all of the keys work. Example - there are keys on the top left row for "back", "menu" and "task switching". Nothing appears to happen when pressing these now. Again, probably something in a .kl file somewhere, but I'm coming up empty. There doesn't appear to be a Vendor-Specific.kl file, but Generic.kl doesn't seem to cut it either.
3. On-Screen keyboard still displays when using bluetooth keyboard.
Well, that about says it all really. I've tried using both the Google keybard, and SwiftKey. Both continue to show up on-screen, even though I'm typing on the bluetooth keyboard. Swiftkey even tells me that it cannot detect a physcial keyboard. Probably related to the key mapping issue from above, but...
Again, thanks for all the work on this. Having CM saved my tablet from it's date with eBay.
Thanks!
- Bri
1. i thought about it but now i haven't spare time to implement. next week maybe.. but i dont promise
2. and 3. try this programm https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
171
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
bribash said:
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
Click to expand...
Click to collapse
Hey, try going with Null Keyboard, enable all your keyboards, and switch between them depending on whether the device is connected or not
Hello,
Last week my phone went off because the battery was drained to 0.
Then next morning I connected the phone to my car's charger and when I turned it on, I figured that the soft keys are not working anymore.
I have tried multiple methods like clearing cache, factory reset (through Settings and Recovery), but none of that worked.
I am running the latest stock firmware (5.1.1 U2COH2).
Did this happen to any of you before? Is there an app that allows me to reconfigure the keys? Could this be a hardware issue?
I appreciate your response.
If you are rooted, you could try reflashing the kernel. Works fir me. Sprint variant
I'm not rooted. I believe it's a hardware issue, unless somebody else has a different opinion.
i have the same problem on the recent app softkey (left botton) . i made all kind of reset, but nothing change, sometime i have a "crazy" soft button that start to work like a spirit! or stop to work.
i tried also "safe mode" and a little less, but same (random) problem!
The only way, i find, before to go to assistance (or to put in the garbage!!!) is to disable the softkey.
i find this on xda:
Use a root explorer (I used X-plore with root enabled).
Go to
/system/usr/keylayout/Generic.kl
Backup file Generic.kl ( copy it as a .bk or something )
Then open the file Generic.kl using the text editor within X-plore.
Then find the word APP_SWITCH linking with the code number (mine is key 254), change APP_SWITCH to MENU. Then reboot and your are done. The Recent Apps button is now back to being a Menu button. Life is great.
http://forum.xda-developers.com/galaxy-s6/help/how-to-remap-buttons-t3084638/page4
put"#" before key 254 and the key stop to exist, and stop to crash my balls
if someone has a different way to fix is wellcome for me.
thanks!
EDIT: this has noting to do with a software upgrade, but is a hardware problem on my device. This post can be deleted.
After an upgrade, I noticed my capacitive buttons were not working after a little while.
Only after a power cycle, they are usable again, but not for too long.
I suspect Android disable them when the "Helicopter home button" occurs.
I found some solutions:
Solution 1: Install "Soft keys" from the Play Store. The buttons are set on top of the display, and for some uses, they sometime get in the way (while using keyboard for example), and you have to reduce the size and have small fingers. It is possible to switch long press to change location.
Solution 2: Tell the system to use Nexus-like Buttons. That way, the buttons are not displayed on top of the screen, but, the screen resolution is reduced and the buttons are set below it. No app to install. Pro: the buttons don't get in the way.
I found a guide here: https://mgeeky.com/how-to-get-nexus-like-buttons-in-any-android-phone/
Add "qemu.hw.mainkeys=0" at the end of /system/build.prop, and reboot. You need an file explorer with an editor and root access. I use Cyanogenmod 12.1, the File explorer has all what's needed.
Optional: Turn Capacitive buttons Back-light off in the system menu. On my system, it is in "buttons"->"backlight"
Maybe it can help someone here.
sadly this does't work on Sense roms