Could someone assist me in enabling the volume keys to wake the screen?
I have root access and tried this method:
Install Root Explorer (only one I advise for this).
Root.
Go into \system\usr\keylayout
Edit generic.kl and gpio-keys.kl (I recommend taking backups first).
Find key 115 and 114 in both files.
Remap as you wish. I have mine set to Menu and Home.
Save and reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2484185
And I changed
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
in both files and rebooted.
But it did not work. I noticed this while I was searching: https://github.com/SomethingExplosi...mmit/d18879528bc4de75d03620ee7636acd404bfcdf9
Does WAKE_DROPPED mean anything?
Edit: WAKE_DROPPED apparent means to turn the screen on and forget the keypress.
What's odd is that many of the keylayout .kl files already have VOLUME_UP WAKE already...
Related
I rooted my Ziio" yesterday.
Installed Google apps.
Have some problems with SetupWizard.apk.
First time after restart work setupwizard i configured my google acc etc. , but after other restart hang on start screen where i must push the android in middle of screen to start, but after do it nothing happens. And homebutton not work , but after i deletet it with adb my Tablet work. Google MArket, Gmail. maps works.
MY Creative Ziio 10, heve 7 Hardware buttons under Display.
All of them work, only my Home button dnot work.
Normyly if i hold Home Button started Taskmanager, or if i press it i go back to desktop.
i have in /system/usr/keylayout/ 4 Files.
ACRPC.kl, qwerty.kl, Touchscreen,kl, wm8350_buttons.kl
But i dnot know where is for my home button.
Maybe blocking some App this button.
Other guy where rootes his ziio 10" , have same problem like me...
Any Ideeas ? how to fix it
I try to Edit Touchscreen.kl for Test.
I Set Homebutton @ 165
And Menu @ 163.
Menu works on new button but home still dnot work.
I think maybe google setup disabled the home funktion.
here a little cu on my touchscreen.kl
key 108 CALL WAKE_DROPPED
#key 103 CALL WAKE_DROPPED stargate rev0
key 139 MENU WAKE_DROPPED
key 103 ENDCALL WAKE_DROPPED
#key 108 ENDCALL WAKE_DROPPED stargate rev0
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 102 HOME WAKE
key 158 BACK WAKE_DROPPED
key 216 BACK WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
key 164 MEDIA_PLAY_PAUSE WAKE
key 201 MEDIA_PLAY_PAUSE WAKE
key 163 TOUCH_NEXT WAKE
key 165 TOUCH_PREVIOUS WAKE
key 212 CAMERA WAKE
key 116 POWER WAKE
Click to expand...
Click to collapse
Plz any one help me.
How did you obtain permanent root? I've gotten almost as far as you have but I've had to reset my tablet after the first or second reboot after rooting.
Thanks!
I dont know if it would be of help.... I have a Ziio 7
Rooted it - and the menu/homescreen would not work....tried lots of work around nothing happened (deleting the google accounts etc..etc..)
Finally i did a factory reset....
my google applications stayed (market, gmail etc...)
Rooted again.. and now everything works....
I tried to modify system/usr/keylayout/pyramid-keypad.kl and system/usr/keylayout/qwerty.kl, then search key can lock my device and let it sleep, but it can't wake up my device.
i modified that:
system/usr/keylayout/pyramid-keypad.kl
key 217 POWER WAKE_DROPPED
system/usr/keylayout/qwerty.kl
key 217 POWER WAKE_DROPPED
anyone here?
wangyu1221 said:
anyone here?
Click to expand...
Click to collapse
as far as i know you can use the vol up key but not the search key to wake the phone
My sprint epic power button failed and I am trying to fix it by moving the function of the power key to the volume up or down key and setting the power key function to null. I have several questions on how to do this.
1. I know that I will have to gain root access but is there a way to do this without installing a custom kernel?
2. If i do end up having to root hte thing how do I get into download mode if the power key is not working?
3. My current /system/usr/keylayout/ has several files in it and am I right to assume that I should be editing the gpio-keys.kl file?
4. Is the 116 button assigned the power button value and 115 volume up?
5. Currently the file looks like this
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
so if i edited it to something like
key 115 POWER WAKE
key 114 VOLUME_DOWN WAKE
key 116
would it still work? I want to leave the power key funciton blank as it looks like it is stuck and I dont want it to get stuck performing volume up the whole time.
That is all. Any help would be extremely appreciated by me and as you can see I am new to this whole process so if you have any pointers or better ways of doing this I would be extremely grateful for any input.
Bump
Bump
sacaAf unto
Any suggestions would def help
Hi all
I made some searches but didn't find any answer, hope some of you could help me.
I want to edit the system/usr/keylayout/device-keypad.kl to make my device go to sleep when screen on & longpress vol down.
Here is the original file content :
Code:
key 116 POWER WAKE_DROPPED
key 114 VOLUME_DOWN WAKE
key 115 VOLUME_UP WAKE
In fact, I don't know the keycode and keyevent name of a vol down longpress.
Can someone know this ? Or at least how to get it ? (Already tried KeyCode Display but it doesn't work as expected).
NB : I already tried Xposed Additions module, and it made the job quite well (device goes to sleep when longpress the right key), but all other keys seems to be messed up (double vibrate, sometimes some keys doesn't even work) so I decided not to use this module anymore and make it manually by editing the right file.
Thx for reading
Oppo R9 detects headset volume down button as volume up
I have checked the .kl files in /system/usr/keylayout/ and they are alright. Specifically, generic.kl has:
key 114 VOLUME_DOWN
key 115 VOLUME_UP
which is the standard in Android...
I modified keys 114 and 115 on generic.kl, but it did not change anything. (meaning ColorOS does not care about /system/usr/keylayout/generic.kl )
I then tried to freeze a bunch of system apps that could interfere with the headset (music, voice assistance, etc...) but that changed nothing either, volume down still detected as volume up.
using Key Test app and pressing headset volume down key:
keyCode=KEYCODE_VOLUME_UP,scancode=115
Any hint on how to fix this bug? Thanks