Database Users

Incorrect keyboard symbols after upgrading radio, hboot and cm7 on g1

I put cm7 onto my g1 but the slide out keyboard has some of the alt keys in the wrong place.
I will try to show you.
If I press
Wer
Sdf
Xcv
I get in return if I press alt
123
456
789
Instead I should have a load of symbols like _ all of the numbers across the top of the keyboard are in the correct place but all the symbols are wrong.
The keyboard worked fine with cm 6.1.0 I have upgraded the radio and hboot for cm7 but I'm not sure if it has anything to do with which country I'm in or if I can change the settings within the phones keyboard options.
Any help with this would be great or if its a bug then let me know what I can do to help.
I am in the UK
Thanks,
Dave.
Sent from my HTC Wildfire using XDA App

ok i have searched and searched and found that there is a file called qwerty.kcm within the cm7.zip rom file 2.3.2, i can edit this file within notepad to my correct key press when pressing alt! i will do this later on tonight for the english tmobile g1, if anyone wants the file once its finished then let me know! i jst hope i can edit it, save it, flash the rom and hopefully it works!
apart from that that is the only really issue im having with the phone within 2.3.2!

davidbbb said:
ok i have searched and searched and found that there is a file called qwerty.kcm within the cm7.zip rom file 2.3.2, i can edit this file within notepad to my correct key press when pressing alt! i will do this later on tonight for the english tmobile g1, if anyone wants the file once its finished then let me know! i jst hope i can edit it, save it, flash the rom and hopefully it works!
apart from that that is the only really issue im having with the phone within 2.3.2!
Click to expand...
Click to collapse
I am definitely having this issue with my G1 (English). Lost my question mark among other things due to the keyboard mapping. If you were able to fix this issue, let me know with a PM or something as I am in need to that file fix.
Thanks,

i wish i had the correct file! i have tried to edit the cm7 files by changing the keys via windows notepad but when i save the file and try to run the flash again it wont let me due to a verification error
if trout-keypad-v3.kcm.bin was in with cm7 like it was with cm6.1.0 then it might of worked but it doesn't look to me that the english version of the g1 has been added to 2.3.1 i would like to get in touch with the devs about this but i dont want to annoy them!
i also tried to copy and paste the correct files from cm6.1.0 to cm7 but there was also a verification error!

i have also just done a little bit of searching into creating my own rom and signing rom files for flashing but i am not that clever unfortunately!
maybe i can take the correct layout and post the zip file on here or email it to someone for it to be signed by someone else that knows what they are doing and then the signed.zip file could be returned?
DEVS! HELP! lol

philly2va you will be pleased to know that this post i will send you has the correct v3 keypad file within the rom, i haven't flashed it yet but i am about to. . .
i have downloaded the top one in that list.
http://forum.xda-developers.com/showpost.php?p=9987696&postcount=2

my keyboard works fine now

well after messing around with all of that and getting the keyboard working i thought i would freshen up the phone a bit, i put rc7 back on to make it stock android 1.0 (it was quick i must add) i formatted the sdcard put RA 1.7.0 on it again and then cm6.1.0 it works fine and i'm happy with the result, the phone is just for messing around with as i have a wildfire but i got bored, im just waiting for a root option for the hbooted 1.001.0010101.1.010.101.1. wildifre lol

An "easier" way to update the keys/keyboard layout...
I did :
1. Grabbed GINGERBREAD-DS-Alpha-20110129-1.zip from http://forum.xda-developers.com/showpost.php?p=9987696
2. Unzipped it to 'gingerbread' directory
3. cmd
>adb shell
# mount -o rw,remount -t yaffas2 /dev/block/mtdblock3 /system
# cd /system/usr
# mv keychars keychars_o
# mv keylayout keylayout_o
#mkdir keychars
#mkdir keylayout
# exit
> adb push gingerbread\system\usr\keychars system/usr/keychars
> adb push gingerbread\system\usr\keylayout system/usr/keylayout
Rebooted and works like a charm.
( I than went back and deleted the keychars_o and keylayout_o dirs...

[GUIDE] How to enable Swiftkey on Kindle Fire

UPDATE: updated instructions for Swiftkey X version 2.2.0.35 (released 11/18/2011) and later.
UPDATE 2: added known values for some other keyboard apps.
UPDATE 3: added warning, split the copying and chown/chmod step into two separate steps.
These instructions assume:
You've already rooted your KF and have ADB access.
You have the adb.exe debug shell installed. This is included with some rooting kits, or you can install the Android SDK (software development kit) from Google and get ADB straight from the source. The examples assume you have a directory called "C:\Android" where adb.exe is installed but yours may be installed elsewhere.
You've got some way of installing the Swiftkey X app, either by installing Android Market or by sideloading the apk.
You're using the purchased version of Swiftkey X (not the tablet version, not any beta or free version that might be out there).
You've got a SQLite editing software (or can use "sqlite3" itself); the instructions below use the free SQLite Database Browser 2.0 which can be downloaded from Sourceforge; just Google for "sqlite browser" (sorry as a n00b I can't post links).
WARNING: use these instructions at your own risk! Modifying, removing or incorrectly setting the permissions on the settings database can result in a non-booting device!
ALTERNATIVELY, you can use various Android apps to edit the database on the device without using ADB, and skip many of the steps below. Posts further down this thread has some recommendations for such apps. Two caveats if using such an app: make sure it doesn't alter the settings.db file ownership or permissions, and be very cateful when modifying the database entry, as there is a tendency for the keyboard or cut-and-paste to "helpfully" insert spaces or change capitalization.
If you try and install Swiftkey as you normally would, you'll get stuck at installation's step 2, which requires you to enable Swiftkey as an input method by redirecting you to the device's input method settings window; in the case of the KF, the option to enable alternate keyboard has been omitted, but as others (thanks PSXtreme and mfisch) have found it's possible to get around this problem and successfully install an alternate keyboard.
Connect the KF to your computer via USB.
When the Kindle tells you that USB storage is enabled, press the "Disconnect" button to disable it (having the USB storage mounted will prevent us from using ADB to copy to the sdcard directory).
Open an ADB shell and use it to make a backup copy of the settings database file (settings.db), and then to a directory where you can edit it (we'll use /mnt/sdcard/Download here) (stuff you need to enter below is in boldface):
C:\android>adb shell
$ su
# cd /data/data/com.android.providers.settings/databases
# cp settings.db settings.db.bak
# cp settings.db /mnt/sdcard/Download​
Now enable USB storage by tapping on the KF's top notification bar and then on "USB is Connected / Select to copy files..."
Open the SQLite Browser, and then open the settings.db file you copied by navigating to the mounted USB drive (e.g. D:\Download\settings.db).
Click on SQLite Browser's "Browse Data" tab, and then "secure" from the droplist of tables. Find the row with the entry named "enabled_input_methods" (it's number 19, ID 21 in my file); you may need to widen the columns to see the full name.
Double-click on the entry's "value"; this will open an "Edit database cell" dialog.
The default value of the entry should be "com.android.inputmethod.latin/.LatinIME"; regardless, you want to add ":com.touchtype.swiftkey/.KeyboardService" to it (the ":" is a separator), e.g. changing the value to "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/.KeyboardService". (Note: if you're installing a different keyboard program, you'll substitute a different value; I found the correct value for mine by downloading the settings.db file from another Android device with Swiftkey already installed.)
UPDATE: for Swiftkey X versions 2.2.0.35 (released 11/18/2011) and later, the value to be added is ":com.touchtype.swiftkey/com.touchtype.KeyboardService", so the resulting enabled_input_methods value is: "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/com.touchtype.KeyboardService"
UPDATE 2: here's a list of known values for various keyboard apps:
Swiftkey (paid version): com.touchtype.swiftkey/com.touchtype.KeyboardService
Swiftkey Tablet (paid version): com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService
Swype: com.swype.android.inputmethod/.SwypeInputMethod
SymbolsKeyboard & TextArt Pro: com.mobisters.textart.pro/.AsciiTextArtKeyboardPro
SlideIT: com.dasur.slideit/.SlideITIME
Graffiti Pro: com.access_company.graffiti_pro/.Graffiti
FlexT9: com.nuance.flext9.input/.IME
Beansoft Thumb Keyboard: com.beansoft.keyboardplus/.LatinIME
Hacker's Keyboard: org.pocketworkstation.pckeyboard/.LatinIME
Simeji: com.adamrocker.android.input.simeji/.OpenWnnSimeji
After you've changed the entry and double-checked you got it right, hit the "Apply Changes" button, close the dialog, and save your changes to the settings.db file. You can now close the SQLite Browser.
Disable USB storage again by hitting the "Disconnect" button on the KF.
Back in the ADB shell, copy the modified settings.db file back to its original location:
# cp /mnt/sdcard/Download/settings.db .​
Still in the ADB shell, fix the file owner and permissions (IMPORTANT! skipping this step can prevent your KF from booting properly!):
# chown system.system settings.*
# chmod 660 settings.*
# ls -l
-rw-rw---- system system 22528 2011-11-17 21:04 settings.db
-rw-rw---- system system 22528 2011-11-17 17:30 settings.db.bak​(The last command just confirms your handywork.)
Reboot the Android device using the ADB "reboot" command:
# reboot​
Once rebooted, you can proceed with the Swiftkey installation. When you reach step 2 of the installation and it directs you to the KF input settings window, you can return from settings window and if you've correctly modified the settings it won't complain that you haven't enabled Swiftkey, and you can go on with the rest of the installation process.
After finishing the install, long-press on a text field to bring up the "Select input method" pop-up menu, which will allow you to switch between the Kindle keyboard and Swiftkey X.
Voila!

I love Swiftkey on my phone but damn this looks so complicated. Thanks though for getting it to work on our devices.

Sooner or later someone will write a script or an app to make it easy.

Interesting timing. A new version of Swiftkey X was released this morning that changed the input methods path; I've updated the instructions above.
If you updated Swiftkey and found it no longer working, as I did, all you need to do is edit the settings.db file using the procedures described above, and reboot the device, after which you can select Swiftkey X as an input method again.

Can you unroot after completing this guide and still keep Swiftkey? Or, in other words, can I temporarily root my KF just to install Swiftkey?
Thanks!

vtluu, why not the tablet version of Swiftkey?

scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.

vtluu said:
scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Click to expand...
Click to collapse
Cool. I decided to use Voodoo OTA RootKeeper for now, but it's good to know a full unroot is viable.
vtluu said:
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.
Click to expand...
Click to collapse
That's exactly what I was hoping to hear!
Thanks!

This works great.
Maybe a list of what should be added for different keyboards in the first post?

Excellent! Waiting on my KF, was hoping someone would have SwiftKey working. Thank you!
//Tapatalk//

Anyone have the value for the Tablet version of swiftkey? It isn't the same as the phone version and I can't install the Tablet version on my phone to check it(it won't let me). Any help is appreciated.

Just figured out the value for Swiftkey X Tablet (v 2.1.0.223):
com.touchtype.swiftkey.tablet.full/.KeyboardService
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version [EDIT: confirmed by scrotty]

Nice work! Swiftkey is my favorite!!

brian112358 said:
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version
Click to expand...
Click to collapse
Confirmed. I just purchased Swiftkey Tablet X v2.2.0.38 through the Marketplace and used the value you hazarded above successfully. Yay!

By the way, with Swiftkey Tablet X, I did not get the number pad in the middle when in landscape mode.
On a hunch, I figured that this was due to the KF's resolution. So I installed the free LCD Resolution app from the Marketplace and set the pixel density from 160 (KF default) to 155. That was sufficient to get the number pad to appear.
WARNING: I tried to set the density to 159 at one point (just to set if I could get it as close to 160 as possible). That value seemed to prevent the KF from restarting (stuck forever at "Kindle Fire")! Thankfully, I had not selected the "apply setting on boot" option in the resolution app and so a simple reboot restored to the default 160 pixel density and the KF started properly. Whew!

I'm waiting for a easier way to do it with out risking so much cause knowing me I would mess up something. Keep of the good work
Sent from my Kindle Fire using Tapatalk

Updated: added values for various other keyboards, copied from Swype keyboard thread.

Any ideas if something similar would work on the Nook Tablet?

Very usefull, thank you bro!

downsay said:
Any ideas if something similar would work on the Nook Tablet?
Click to expand...
Click to collapse
If the NT has the same limitation (i.e. no UI to allow alternate keyboard) I would imagine the same procedure could work, yes. That assumes B&N hasn't screwed around with the text input field code to prevent you from selecting between enabled keyboards (via long-press on text intput field).
Only one way to find out... good luck!

ATT 2.3.5 SystemUI Quickpanel

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

[GUIDE][HOW-TO]Disable Hardware Keys Lights and Function

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 .

[HOW TO] Disable Capacitive Buttons and Enable REAL android onscreen buttons

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