With this procedure you will be able to disable the capacitive buttons and enable the real android onscreen buttons, NOT PIE.
This has been tested in a Tab Pro 8.4 with the latest CM build. If you follow the instructions correctly you shouldn't have any issues, however make a backup just in case. If anyone wants to try it with a stock rom please let me know if it works.
Requisites: Root access and a root explorer.
1. With your preferred root explorer open your build prop and add the following line all the way to the end:
qemu.hw.mainkeys=0
Save and exit.
2. Navigate to system/usr/keylayout and open sec_touchkey.kl as text.
You should have two lines. Add a # at the beginning of each line as follows:
#key 158 BACK
#key 254 APP_SWITCH
Save and exit.
3. Exit the file explorer and go to settings, buttons and turn off the buttons light.
4. Reboot and voila!!!
I hope this helps.
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
It works fine in portrait but broken in landscape. Keys dont show up at all. Any fix for this?
burshturs said:
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
Click to expand...
Click to collapse
I have the same problem with stock ROM.
aeron16 said:
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
Click to expand...
Click to collapse
Are you trying it in stock or CM?
Hi am using Stock
Hi guys i tried on CM 11 and i dont find #key 254 APP_SWITCH , i rebooted my TAB and Hardware button still works , and appear Software button too , any clue?
Works like a sharme on cm11. The only thing is that the file isn't named 'sec_touchkey.kl' but 'sec_touchscreen.kl' (newest nightly 9-9-2014)
Thanks, works great for me on cm11, too
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Good stuff. Thank you ! So I guess the way to undo the process I is simply to flash a CM update?
Just flash the ROM again without reset and everything will be as before. Or edit the files as described in the OP and revert the changes.
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Sorry if this sounds like a dumb question but you said to open the build prop and add that line to the bottom and my question is where, exactly? I'm using solid explorer and am in the system root folder but to which file do I add that line? Is it in system>usr>keylayout>Generic.kl like I navigated to to disable the capacitive buttons?
I found how to do that in another post and then enabled Pie, but I'd rather have the normal buttons instead.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
@baldwyn: build.prop is a file in /system.
Does anybody know the key for the home-button? I have already disabled #172 but that's not working.
petty500 said:
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Click to expand...
Click to collapse
You can use this app instead of the build.prop edit. That works just great, The Pro version even allows many customizations incl. behaviour like auto hide or not or custom icons. Important - it works both portrait and landscape,
https://play.google.com/store/apps/details?id=com.mrbimc.udn.lite&hl=de
Working in CM12?
hypophysis said:
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Click to expand...
Click to collapse
Has anyone tried this in CM12? Or perhaps CM12 has a built-in setting that accomplishes the same thing?
Thanks,
Ron
kingofcomedy said:
Click to expand...
Click to collapse
Thank you for this. With this setting are the capacitive buttons disabled? I would prefer that they were.
Sent from my SM-T320 using Tapatalk
Related
Using a soft keyboard different than the Asus one, when the dock is connected an annoying message pop up telling us that if we don't change the soft keyboard to the asus one, the dock keyboard could not function well.
This is mostly important for non US users, as when the soft keyboard isn't the Asus one, the layout used for the dock is the standard US one.
Root needed
Using Autostarts we can disable the popup when the dock is connected:
Download autostarts from the market, open the app, let it load all the the way, then click on Asus Keyboard under "Docking changed" and disable it
or in terminal
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
For permanently change the standard layout of the dock keyboard:
Locate your national keychars in /system/usr/xt9/keychars
mine is qwerty-it_IT.kcm
The first 2 character after the - is the language of the keyboard, in my case Italian, the 2 characher after the _ is the country of the keyboard, Italy in my case.
copy this file in /system/usr/keychars
rename the standard one asusec.kcm in asusec.kcm.old for backup purpose.
then rename the one you copied in asusec.kcm
Locate your national layout in /system/usr/xt9/keylayout
mine is qwerty-it_IT.kl
copy this file in /system/usr/keylayout
rename the standard one asusec.kl in asusec.kl.old for backup purpose.
then rename the one you copied in asusec.kl
reboot and you are all done
P.S.
you can use root explorer to copy and rename those files, or you can do it with adb.
If you don't know how to use those, maybe is better to learn before messing around in the system files.
P.P.S.
If anyone know a free app that can replace autostarts, let me know so I can update the guide.
Great guide, thx a lot! If we mess with keychars and keylayout, we could also remap specific keys, right?
For example, I don't really need the three brightness buttons on the dock, i barely change brightness, and if i have to sometimes, i don't mind browsing to settings-->display.
Can we remap these to different keys OR specific apps, OR even better: to key combinations? Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Plus, one more off topic thing, I think you could know: Is there a file which could change mouse button mapping and perhaps enable additional mouse buttons (thumb mouse buttons for example)? I though of setting the "menu" key to the right mouse button instead of "back" for example.
Regards
qwer23
qwer23 said:
Great guide, thx a lot! If we mess with keychars and keylayout, we could also remap specific keys, right?
For example, I don't really need the three brightness buttons on the dock, i barely change brightness, and if i have to sometimes, i don't mind browsing to settings-->display.
Can we remap these to different keys OR specific apps, OR even better: to key combinations? Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Plus, one more off topic thing, I think you could know: Is there a file which could change mouse button mapping and perhaps enable additional mouse buttons (thumb mouse buttons for example)? I though of setting the "menu" key to the right mouse button instead of "back" for example.
Regards
qwer23
Click to expand...
Click to collapse
You can remap any key you want, I've seen a guide somewhere in the forums.
For the mouse I don't think you can do anything without some serious hacking, the dock trackpad follow the standard rules for mouses in android: left click = click, right click = back, whell button click = menu.
I also hate how they have implemented the 2 finger scrolling, when you scroll actually the trackpad long click where the cursor is, and invert the axis of the trackpad, so when you scroll down you are in fact long pressing and scrolling the cursor up, and so on.
It messes so many apps, as this simulated long click can be registered by the app
Updated on the first post how to disable permanently the asus keyboad popup when docking
qwer23 said:
Would be cool to have cut, copy and paste on the brightness buttons. What do you think?
Click to expand...
Click to collapse
You can do it with ctrl+x ctrl+c and ctrl+v
I can't see the Thank You button, but I thought I'd just say thanks!
This is an excellent guide and worked perfectly for my UK keyboard!
Much appreciated
I found an alternative to Autostarts, fire this commands in a terminal:
Code:
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
These are the "cut&paste" commands for changing the layout:
Code:
adb remount
adb shell
mv /system/usr/keychars/asusec.kcm /system/usr/keychars/asusec.kcm.old
mv /system/usr/keylayout/asusec.kl /system/usr/keylayout/asusec.kl.old
cp /system/usr/xt9/keychars/qwerty-it_IT.kcm /system/usr/keychars/asusec.kcm
cp /system/usr/xt9/keylayout/qwerty-it_IT.kl /system/usr/keylayout/asusec.kl
I found my own solution for disabling the dock connected popup.
I modified the XT9IME.apk so that the popup is not displayed and posted it here before stumbling upon this thread.
Would it be possible to make a update zip, to do this in clockwork, ive just insalled a new rom, now i need to redo the fix.
jambo89liam said:
Would it be possible to make a update zip, to do this in clockwork, ive just insalled a new rom, now i need to redo the fix.
Click to expand...
Click to collapse
I could script this and have update.zips for it.
Perhaps someone else could create an app that does it via a menu system to select your country.
Fixed?
Over on http://forum.xda-developers.com/archive/index.php/t-1152317.html the last post says:
"The warning message has now been fixed, after the latest update 8.4.11. It now gives you the option of 'Do not show this again."
So maybe it's now fixed? (Don't have my Transformer at work to check for myself.)
You can use this as an executable (755) script file if you want to use another keyboard with another language
Code:
#!/system/bin/bash
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mv /system/usr/keychars/asusec.kcm /system/usr/keychars/asusec.kcm.orig
cp /system/usr/xt9/keychars/qwerty-de_DE.kcm /system/usr/keychars/asusec.kcm
mv /system/usr/keylayout/asusec.kl /system/usr/keylayout/asusec.kl.orig
cp /system/usr/xt9/keylayout/qwerty-de_DE.kl /system/usr/keylayout/asusec.kl
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Just replace the "de_DE" parts with your language code.
Just wanted to bump this b/c of the ICS release.
While those ADB commands give me a "segmentation fault"...
Azhad said:
adb shell
su
pm disable com.nuance.xt9.input/.DockEventReceiver
Click to expand...
Click to collapse
the following procedure still works like a charm on ICS!
Azhad said:
Locate your national keychars in /system/usr/xt9/keychars
mine is qwerty-it_IT.kcm
The first 2 character after the - is the language of the keyboard, in my case Italian, the 2 characher after the _ is the country of the keyboard, Italy in my case.
copy this file in /system/usr/keychars
rename the standard one asusec.kcm in asusec.kcm.old for backup purpose.
then rename the one you copied in asusec.kcm
Locate your national layout in /system/usr/xt9/keylayout
mine is qwerty-it_IT.kl
copy this file in /system/usr/keylayout
rename the standard one asusec.kl in asusec.kl.old for backup purpose.
then rename the one you copied in asusec.kl
reboot and you are all done
Click to expand...
Click to collapse
Thanks again for working this out!
can anyone please make the dock keyboard work with latvian? i hate anysoftkeyboard, it stops working and its craching all the time.
i want to use dock like on a normal computer.
Does latvia have its own keyboard layout or do you use one that another country uses as well? Which county abbreviation would it be (like en for English and de for German)?
Doesn't work ?!
modmatt said:
the following procedure still works like a charm on ICS!
Click to expand...
Click to collapse
Doens' work for me, in fact, if I'm copying the de_DE files from Revolver 4 over to my EOS AOSP rom build and put the keychars (asusec.kcm) and the keylayout (asusec.kl) in their respective folders and reboot afterwards, nothing happens to the dock input. Still stays the same old QWERTY like before.
But I can see in file manager that the copying was successfull. New asusec.kl and asusec.kcm are there.
Someone help me ?
You already mentioned the reason yourself, I think. As you are using an AOSP ROM it means that you're using a plain vanilla android basis, which - correct me if I'm wrong - obviously doesn't know anything about asus*.* keyboard files. Just copying some files somewhere is not enough to let the system know what to do with it.
You probably have to deal with some scripts, that are run at every start up, that give proper instructions for the operating system. Unfortunately this is way beyond my knowledge.
modmatt said:
You already mentioned the reason yourself, I think. As you are using an AOSP ROM it means that you're using a plain vanilla android basis, which - correct me if I'm wrong - obviously doesn't know anything about asus*.* keyboard files. Just copying some files somewhere is not enough to let the system know what to do with it.
You probably have to deal with some scripts, that are run at every start up, that give proper instructions for the operating system. Unfortunately this is way beyond my knowledge.
Click to expand...
Click to collapse
What are you going on about? This works just fine on ICS with Revolver, just changed my dock back to azerty. rayman33 just did something wrong.
Please read that rayman33 uses an AOSP ROM that has nothin to do with Asus. You are using Revolver, which is bases on Asus' original ROM - that is why it works for you but not for him.
i just found this post as i'm having the very same issues using my transformer tf300 - currently running official stable CM10
the bad thing about it is only, in my CM10 i don't even have a /system/usr/xt9/ directory and when looking into the backup of my stock ASUS rom, I do have /system/usr/xt9/ and even subdirs keychars and keylayout, but without any content.
it would be lovely if someone would be so kind to suck out the de_CH files for me and could post them here!
ATT 2.3.5 SystemUI
quickpanel_title_background.9 I Can not define
This is nice!
A few suggestions:
- Less icon spacing. Should fit at least 5 on the screen at once.
- No vibrate icon. It's unnecessary. Holding the power button works fine.
- Brightness control.
Thank you. Well done
Sent from my MB860 using Tapatalk
Hi can I install this on rooted locked atrix on 2.3.4!? I'm on UK retail. The thanks
Sent from my MB860 using XDA App
Wow. This is what I wanted.
Thank you
I'm on a rooted US ATT 2.3.4. How can I get this to install? I tried abd install, that didn't work...
--Q
EDIT: I think I figured it out. You have to go into /system/app and rename SystemUI.apk and SystemUI.odex to have .bak then copy the modified SystemUI.apk and then chmod 644 it. Rebooting now...will keep you posted!
EDIT2: Yep! Totally worked! GENIUS!! THANKS!
Do I really need to use adb or can do chmod by using some tool on phone?
Sent from my MB860 using XDA App
You can do all this with Root Explorer if you have it. Same idea.
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Lack of ability to use a lot of smali. Or else can do more...
ein1002 said:
Lack of ability to use a lot of smali. Or else can do more...
Click to expand...
Click to collapse
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Shaydar said:
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Click to expand...
Click to collapse
I have no way to make the right moves Brightness：（
So I removed the BrightnessSettingButton
Leaving only the image resources
Hope someone can fix. And add this part.
sorry. My English is not good
Thanks, It does not matter anyway.
The Screen is so bright that I always set the brightness to its lowest.
malfuncion said:
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Click to expand...
Click to collapse
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
CyberPunk7t9 said:
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
Click to expand...
Click to collapse
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Abu-7abash said:
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
It's just the latest Aura ROM (found in the development section) + this awesome quick panel MOD.
Aura is based on 2.3.4. I noticed that arabic fonts were connecting properly in the system+browser with Aura ROM as-is. No framework.jar or lebwebcore.is hacks are needed with that ROM.
Root+Battery % icons MOD+No carrier logo MOD+proper Arabic font connecting+this quick panel MOD is pretty much what I want now in my Atrix. Currently happy to have all that.
Not to mention a lot of other plus features Aura ROM adds.
Hi,
I was using this mod on 2.3.4 and it was great! Just upgraded to Android OS 2.3.6 (att build 4.5.141) and it just boot loops until I replace it back with the original. Is there any way to modify this to work on 2.3.6? Or, is there a version around that I'm not finding that will work on 2.3.6?
Thanks!
--Q
The Screen unlocks in the "slide to unlock" mode, by just a press of the "= " button. Is it a bug or a feature...? its sort of buggy for me because screen unlocks itself in my pocket. Any one please check and see if its a one-off case of my phone or general???
jy0thish said:
The Screen unlocks in the "slide to unlock" mode, by just a press of the "= " button. Is it a bug or a feature...? its sort of buggy for me because screen unlocks itself in my pocket. Any one please check and see if its a one-off case of my phone or general???
Click to expand...
Click to collapse
its a feature, you can disable it in the build.prop file, i cant remember the line sorry.
Yes It's a feature in ICS as you can slide notification bar down in locking screen.
There is these three different ways to unlock: notification bar, "settings" button and slidelock.
Thanks. But how do I disable it?
Sent from my U8800 using XDA
Use a file manager with root access, go to /system/build.prop and open it with a text editor. I recommend ES file explorer and then es text editor it comes with.
Find the line:
Code:
ro.config.hw_menu_unlockscreen=true
and change it to:
Code:
ro.config.hw_menu_unlockscreen=false
Reboot and it should no longer unlock with menu key. You can also edit it before installing latest aurora rom by editing build.prop with wordpad in windows or gedit in linux.
Sorry. I couldnt find the above lines inside build.prop.
Sent from my U8800 using XDA
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie
hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium
aljazirrr said:
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Yuhuuu...is viperdhd an AOSP ROM?
Sent from my HTC Desire HD using Tapatalk 2
Magpie42 said:
Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie
Click to expand...
Click to collapse
I've tested myself and worked before I posted it and yes the cm have that tweaks,but I doesn't work for me when I set,btw thx
Sent from my HTC Desire HD using Tapatalk 2
hdorius said:
I've tested myself and worked before I posted it
Click to expand...
Click to collapse
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie
increase the hardware button britness on JB 4.2.1
Magpie42 said:
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie
Click to expand...
Click to collapse
Hi Guys,
can someone please help me and suggest me a way to increase the britness of the hardware button on my ZOPO 980 who is running JB 4.2.1
I have tried to edit the build.prop but did not find any line to modify , and I would guess this is not the right way.
thanks
Good
Sent from my KM-S220 using xda app-developers app
Thanks a lot
Works great on my d2vzw. I used option one and made the 644 changes that magpie suggested in second post
Sent from my SCH-I535 using Tapatalk
Thanks!
Great guide worked perfect on my htc amaze 4g
Thanks!
Viper DHD 3.0.1
in viperdhd this options is available in venom tweaks, version 3.0.1 is the latest and most stable version with complete sense 4.1 UI. I suggest you to try it once.
Nice guide, can I try this on nameless ROM, 5.0.2
total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything
ankitrajj said:
total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything
Click to expand...
Click to collapse
Maybe it don't compatible with samsung phone, i just tested it on my desire hd,sorry..
I am using micromax nitro A311 and its navigation key light is turned off, can anyone tell me how to enable the light of navigation keys?
hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
Brother can you help me up enabling button light in samsung exynos 7580 as button light feature is disabled in the RR sources.
Please it would be a great help to me struggling from months for the fix .
Just a quick info for people with Xiaomi Piston v3 headset, nothing new either:
As root you can assign all three keys in the file
Code:
/system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
Buttons in order top->bottom when you wear the headset
Upper button: Keycode 115
Middle button: Keycode 226
Lower button: Keycode 217
(at least on Cyanogenmod 13)
For example:
Code:
key 226 HEADSETHOOK
key 115 VOLUME_UP
key 217 VOLUME_DOWN
You can get some inspiration on what actions are available in the "Generic.kl" file in the same folder
Todo: Write a little script in /persist so it stays accross system updates.
so how i'm supposed to enable those actions? please explain the process step by step
Thank you
cameravala said:
so how i'm supposed to enable those actions? please explain the process step by step
Thank you
Click to expand...
Click to collapse
Hope this works on your ROM.
First the /system parition needs to be writeable, you need root for that.
In a terminal emulator or in "adb shell" on your PC do:
Code:
mount -o remount,rw /system
Then you can edit it, for example go to the location with a root-explorer and open it from there in a text editor (most comfortable)
or you can transfer it to your PC and edit it there:
On the phone:
Code:
cp /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl /sdcard
Then edit the file that is now in your internal storage that shows up on PCs over usb.
To put it back, on the phone:
Code:
cp /sdcard/msm8226-tapan9302-snd-card_Button_Jack.kl /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
chmod 644 /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
You need to reboot it after that. You can ask if you have other questions.
This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb
fonz93 said:
This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb
Click to expand...
Click to collapse
Damn, I was hoping this is universal.
Thanks for the clarification
fonz93 said:
This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb
Click to expand...
Click to collapse
Thanks you guy
Will this work with CM13?
tiagp said:
Will this work with CM13?
Click to expand...
Click to collapse
Yes
I can't find msm8226-tapan9302-snd-card_Button_Jack.kl on root/system/usr/keylayout
Should i make that file named msm8226-tapan9302-snd-card_Button_Jack.kl on that location?
I'm on Cm13 with latest build.
giboto91 said:
I can't find msm8226-tapan9302-snd-card_Button_Jack.kl on root/system/usr/keylayout
Should i make that file named msm8226-tapan9302-snd-card_Button_Jack.kl on that location?
I'm on Cm13 with latest build.
Click to expand...
Click to collapse
Yeah, you'll need to create it in that location. Your keycodes might differ from the OP (mine did) so you might need to use the keytest.apk to make sure your mappings are correct. Other than that, you'll be fine.
Works me perfect
I didn't create the file, instead of that i modified the "Generic.kñ" file and after a fast reboot worked fine
Sent from my Moto G using XDA-Developers mobile app