Database Develop

Tips - use G button as camera button / lock screen (change key binding)

I found it in a chinese forum (bbs.gfan.com/android-2014369-1-1.html)
I'm sure most people found the G button useless, so it would be nice to change that. The following is my experience with it:
The position of the G button make it perfectly useful as lock/unlock button, you can use it to shutdown as well, but cannot use it to switch on the phone, I guess it is electrically hardwired to the power button at the top.
Not too bad for camera, long press it will launch the camera app, but it don't have 2 levels so press it once and it will start auto-focus and take picture immediately, similar to touch and release shutter button in camera app, which mean you can't "dis-engage" a failed focus attempt.
here is the method:
1. make sure you have root and r/w to system partition
2. the file in question is "TWL4030_Keypad.kl", it's in /system/usr/keylayout/
3. before making any changes, copy the file to SDcard as a backup
4. open the file with any text editor, scroll down to 3rd line from the bottom, it should be "key 95 GESTURE"
5. if you want to use it as camera button, change it to "key 95 CAMERA WAKE_DROPPED"
if you want to use it as power/lock button, change it to "key 95 POWER WAKE_DROPPED"
6. save the changes, reboot to see the changes.

Very good.
In fact, I may even use this on nova.

the method is work.
after edit file it create backup file which is name "TWL4030_Keypad.kl.bak"

It works! Great!

worked perfectly thx!

thank u..
this work

hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??

My phone still on Original ROM.
After modify to Power/Lock mode, it's work.
but into Shutter mode, doesn't work.
Any idea?
SnoopyZ

digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
did u reboot after making the changes?

digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
notice you need to long press to start the Camera App. (you should feel the phone vibrate)
or just start the camera app, then press the G button to take a picture to see if it works.
It should be a pretty straight forward modification.

Could it be
"key 95 RECOVERY WAKE_DROPPED" ???

wow, very nice

Very nice. Thanks.
To all who could not manage get it to work: You must take care of file attributes after modyfing the file content ( otherwise it won't work ). It must be CHMOD 644.
( I use SD Maid for this )

It doesn't work for me, i am using pays ROM. Can someone upload the file? Thank u!
Enviado desde mi LG-P970 usando Tapatalk

"key 95 HEADSETHOOK WAKE"
to use headset button

I tried modifying the file and saving it ... but the it always comes up as an error and doesn't allow me to save it... any solutions???

you need to have your phone "root" AND mount system partition as read and write

fjsw said:
you need to have your phone "root" AND mount system partition as read and write
Click to expand...
Click to collapse
Hey my phone is rooted, how do I mount system partition a read and write ? Sorry I'm a noob

if you use ES File Explorer, goto setting, select 2 checkboxs "Root Explorer" and "Mount File System"
if you use root explorer, change directory to /system, then press "Mount R/W" button

yabgo said:
"key 95 HEADSETHOOK WAKE"
to use headset button
Click to expand...
Click to collapse
Sorry to ask but: what is the "headset button" and what is it good for?
Thanks,
Kusie

[Q] NOVA-could it wake up by pressing G or volume key

Hello,
I am using NOVA V8 and flash the huexxx fix
could I use any script to use the G button or the volume button to wake up my phone?
I tried to read the script and tutorial...but i wonder there is no key 95 which correspond to G button. I tried to make a new script for key 95...but it doesn't work at all.
it doesn;t matter to use G button to wake up, but i really want to use other key besides power key to wake up.
sorry for my poor english

In /system/usr/keylayout edit this file: TWL4030_Keypad.kl (I user root explorer, dont forget to backup!) and change this entry (it is in the bottom for me):
key 95 POWER WAKE_DROPPED
It worked for me.

dcop7 said:
In /system/usr/keylayout edit this file: TWL4030_Keypad.kl (I user root explorer, dont forget to backup!) and change this entry (it is in the bottom for me):
key 95 POWER WAKE_DROPPED
It worked for me.
Click to expand...
Click to collapse
I sorry to tell you that there is NO LINE with key 95 for me.
I tried to add this line "key 95", but it doesn't work at all. any other means?
how about volume key to wake up the phone?

Try this: http://forum.xda-developers.com/showthread.php?t=1210341
more specifically:
# Phone will wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=1

dcop7 said:
Try this: http://forum.xda-developers.com/showthread.php?t=1210341
more specifically:
# Phone will wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=1
Click to expand...
Click to collapse
i sorry to tell you that i don;t know how to do so...
Are there any tutorial to change this value?
Besides, I would like to ask whether we can have 2 or more function on one key, such as G button for both camera and power.
THANKS
Thanks

sonicpeter said:
i sorry to tell you that i don;t know how to do so...
Are there any tutorial to change this value?
Besides, I would like to ask whether we can have 2 or more function on one key, such as G button for both camera and power.
THANKS
Thanks
Click to expand...
Click to collapse
try the link I gave on the last post... it is there

Nova V10D?
Can I flash Nova on V10D?

dcop7 said:
In /system/usr/keylayout edit this file: TWL4030_Keypad.kl (I user root explorer, dont forget to backup!) and change this entry (it is in the bottom for me):
key 95 POWER WAKE_DROPPED
It worked for me.
Click to expand...
Click to collapse
This didn't work for me. I don't get it at all. I updated the key 95 line but still no waking up with g key... Suggestions would be very appreciated. Thx.

Paracetamol100 said:
This didn't work for me. I don't get it at all. I updated the key 95 line but still no waking up with g key... Suggestions would be very appreciated. Thx.
Click to expand...
Click to collapse
Check the permissions of the file,maybe it changed, and check the tabs in the file,maybe the spaces cause some type of conflict

Allow or Disallow the Home key from waking up the Phone [Galaxy Note]

PREVENT - ALLOW GALAXY NOTE HOME KEY FROM ACCIDENTALLY WAKE UP DEVICE:
Some people complained about the Home keys of Galaxy Note sometime is touched and turned on accidentally when taking it in-out of the pocket.
After studying some articles on-line for Droid X phone (not same as the Galaxy Note), I digged around in the directory system/usr/ keylayout. Finally, I have found a way to do it. I can disable the HOME key from wake up the phone in off-screen state, but still let it to move from apps drawer to standby screen as usual. And I think it works!!
- Goal: Modify 2 file related to wake up function of the Home key (code 102).
- How to:
+ Using Root Explorer go to the folder: system/usr/keylayout, set permission to Mount R/W;
+ Click to select the 2 files: gpio-key.kl and sec_key.kl to modify them. When the menu appears, select: Text Editor to modify the files.
+ Move to the line: "key 102 HOME WAKE" in the 2 files above and put the cursor on the position of "WAKE" to erase the word "WAKE".
+ Press Menu hard button, select Save Changes, the phone will save the backup file and save the current files.
+ Set permission to Mount R/O for the folder: system/usr/ keylayout.
+ Shut down and then restart, Ahh, it worked!
Note: If you want to use Home key to wake up Galaxy Note again, go to delete two above modified files and rename the two backup files to gpio-key.kl and sec_key.
For people don't want to do it manually, I make the 2 flashable files for Allow and Disallow the Home key for Note and tested for working, at least on my Galaxy Note.
The 2 flashable files to do that is attached below. Copy to SDCard/ExternalCard and flash them in CWM Recovery, then reboot:

works for me. thx.
Sent from my GT-N7000 using XDA

kui425 said:
works for me. thx.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
OK. Hope that help.
Thanks for reply.

flashable zip
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...

bunique said:
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...
Click to expand...
Click to collapse
Yes..please.
+1
GT-N7000-LiquidSmooth-V [2.2] .

Wish I could give u more thanks for this. Works like a charm. Very very annoying that the home button would wake the phone up by default.

Flashable files to Allow or Disallow the wake-up function of Home key for Note
Flashable file for Allow and Disallow the Home key for Note
Phew! I tried my best to make the flashable file and tested for working, at least on my Galaxy Note.
Here is the link for Allow and Disallow the Home key for Note.
Copy to your SDCard and flash them with CWM Recovery.
Hope them could help.
bunique said:
Could you make a flashable zip file for this?
Would be great!
Thanks in advance...
Click to expand...
Click to collapse
firasusman said:
Yes..please.
+1
GT-N7000-LiquidSmooth-V [2.2] .
Click to expand...
Click to collapse

a big THANKS for the flashable files!
will give it a try....

Works perfectly, thanks
Cassie's xtra lite v2.9

Good Job

AWESOME. thanks!

Do not work on JB SLIM BEAN
Sent from my GT-N7000 using Xparent ICS Blue Tapatalk 2

I can not thank you enough for this as I have struggled with this issue for the past 12 months and as my job is a dirty one I can feel my phone getting hot in my pocket but cannot take it out as by hands are black. Thanks.

looks like this is not working in Jelly Bean / Cyanogen 10.1
vasiaeva said:
Do not work on JB SLIM BEAN
Sent from my GT-N7000 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
does somebody know whitch file(s) to edit for this to work in Jelly Bean or Cyanogenmod 10.1.
I'm on asylum 4.2.2.this is a cyanogen 10.1 mod , like slim bean .
It looks like we need to change more/other files for this to work , wile when i canche the here adviced ones , nothing seems to change ,, the volume buttens still behave the same.
/system/usr/keylayout/sec_key.kl is changed to..
key 115 POWER WAKE
key 114 POWER WAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
look at line 115 and 114 this would change te volume button function in the power funtion , i suspect , AM I RIGHT ????
in fact this does not change the behavior of the volume buttons at all it still changes te volume , btw i did restart after changing te sec_key.kl file
please advice manny thanks in advance

Is it possible to add long press action to Home key or other capacitive keys like in CM roms ? How to make it turn on flash light ?

Any idea if this works on the s4 too?

StuartTheFish said:
Any idea if this works on the s4 too?
Click to expand...
Click to collapse
Just tried, and yes it does work on the s4. We only have the one file though, gpio-key.kl. Same location though. Find the line that says home, and delete the word wake. Save changes and reboot, job done!

[APP] Nook Touch Mod Manager

Nook Touch Mod Manager
This app+patched jars allows you to customize the behavior of your Nook. All customizations are opt-in and can be enabled/disabled through the use of the NTMM app. If you install the patched jars and do not configure them with using the app, your Nook's behavior will not change in any way.
Features:
Re-map the n button, quicknav buttons (including the glowlight button), and top statusbar buttons to run installed programs or trigger defined actions (toggle glowlight, home, back, etc)
Option to disable slide to unlock screensaver (avoid battery drain from constantly looping animation)
Option to always show the back and menu buttons on the statusbar.
Option to restore the Glowlight state after waking from screensaver.
Option to disable or customize the "press the n button to unlock" text on the screensaver (1.2+ only)
Option to remap side buttons (1.2+ only)
Completely open source, including both the application and the patches to the jars
.
Requires patched jars.
Patches are available for software revisions 1.1.5, 1.2.0, and 1.2.1 (1.2.0 and 1.2.1 use the same patches). You can upgrade to 1.2.1 using the directions on the B&N support page.
Instructions for building the patched jars are available here: https://github.com/doozan/NookTouchPatches
Download NTMM 0.4.0

EDIT: @jeff_kz has fixed this.
--------------------------------------------------------------------------
I would like to try this. I get an error:
C:\nooksmods>java -jar baksmali-1.4.0.jar -o android.policy android.policy.orig.jar
C:\nooksmods>patch -p1 < android.policy.patch
patching file android.policy/com/android/internal/policy/impl/LockScreen.smali
missing header for unified diff at line 20 of patch
can't find file to patch at input line 20
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|8,7 @@
|
| .field private mSelector:Lcom/android/internal/widget/LeftSlidingTab;
|
|+.field private mNotFirstResume:Z
|
| # direct methods
| .method static constructor <clinit>()V
--------------------------
File to patch:
Click to expand...
Click to collapse

I think git is messing with the line-endings. Patch.exe expects them to be Windows \r\n and I think they're getting converted to Unix \n somewhere in the process. You can use a text editor like Notepad2 to open and re-save the patches with Windows line endings.

EDIT: @jeff_kz has fixed this.
--------------------------------------------------------------------------
This is line 14 to 23. I am not sure exactly what line endings to change?
.field private mSelector:Lcom/android/internal/widget/LeftSlidingTab;
+.field private mNotFirstResume:Z
# direct methods
.method static constructor <clinit>()V
@@ -950,6 +951,47 @@
.line 693
.end local v0 #r:Landroid/graphics/Rect;
:cond_17
[\QUOTE]
Click to expand...
Click to collapse

Open the patch file using notepad2, go to File | Line Endings and choose "Windows (CR+LF)" and save.

Excuse me, so I can just update my NST to 1.1.5/1.2.0, and it will work?
NookSimpleTouch/Tapatalk 2

EDIT: @jeff_kz has fixed this.
--------------------------------------------------------------------------
I like that this can set the quicknav Glowlight button!
The status bar back and menu buttons work at times, but not consistently.
The side buttons work in some apps, but not in the Reader.apk or Library.apk.

domi.nos said:
Excuse me, so I can just update my NST to 1.1.5/1.2.0, and it will work?
Click to expand...
Click to collapse
Yes, you can update your non-glowtouch nook to 1.1.5 and it will work with this tool. 1.2.0 is not yet supported. The 1.1.5 factory zip is in the "Nook ST Glowlight - ready to root" thread, see my post on the "uk nst vs us nst" thread for directions on flashing new software (sorry, can't post links yet).

@jeff_kz, where are you storing the images for the quicknav buttons. Previously I had changed these in the framework-res.apk. with your nooktouchmod it is using other images, is it possible for me to put in my own images?

ladykayaker said:
@jeff_kz, where are you storing the images for the quicknav buttons. Previously I had changed these in the
framework-res.apk. with your nooktouchmod it is using other images, is it possible for me to put in my own images?
Click to expand...
Click to collapse
The action icons (back/home/glow) are loaded from system resources, by resource id. The application icons are read from the application's package. You can customize the icons by pulling settings.db and adjusting the mod.<button>.icon value. An integer value will load a system icon by id, a package name will load the package's icon. Currently, there's no way to read an icon from an external file.

I've fixed the problem with the git line endings, so anyone else trying this will not need to bother with manual conversions.

Nice work!
LastSilmaril and I were working on a NookTouchTools for Glowlight here, but we hadn't yet finished so thanks for saving us the trouble!
Have you not posted patched jars so as to avoid copyright issues? I can respect that, but I understand that B&N have already made statements that their source is available on request (in the USA at least), so you'd save folks much trouble if you could post patched jars. I'll for sure go the long, 'clean' way around if I have to, but would prefer not to if there's no need!
Thanks again for providing this fundamental Nook tool for the 1.1.5 firmware,
Ian

EDIT: @jeff_kz has fixed this.
--------------------------------------------------------------------------
Is anyone else having problems with the side buttons in the Reader? The sidebuttons work in other apps, just not the Reader.
I previously had NookTouchTools installed, but with this app I uninstalled NTT - so I wasn't sure if that is what caused this problem, or is it possible that it happened with this mod?

ladykayaker said:
I previously had NookTouchTools installed, but with this app I uninstalled NTT
Click to expand...
Click to collapse
I'll admit I've not yet installed this, but here's one thought; what jar files did you start from when doing the patching for Nook Touch Mod Manager? Were they vanilla 1.1.5 jars or the ones you'd already installed for NookTouchTools?

ladykayaker said:
Is anyone else having problems with the side buttons
Click to expand...
Click to collapse
This app does not alter or affect the side buttons in any way. The side buttons are just hardware buttons that send a specific hardware key as defined in system/usr/keylayout/qwerty.kl. I believe NTT had a function that allowed you to change the button definitions within that file. I don't know if NTT re-alters that file when it is uninstalled. For reference, the last four lines of that file should be:
Code:
key 250 LEFT_NEXTPAGE
key 251 LEFT_PREVPAGE
key 252 RIGHT_NEXTPAGE
key 253 RIGHT_PREVPAGE

I've just taken a look in that file and it is just as you've quoted it even though I have used NTT to remap a couple of those buttons, so I guess NTT achieves it in some other way.

Patches are now available for 1.2.0 for those with nooks on the other side of the pond.

dr_diem said:
I'll admit I've not yet installed this, but here's one thought; what jar files did you start from when doing the patching for Nook Touch Mod Manager? Were they vanilla 1.1.5 jars or the ones you'd already installed for NookTouchTools?
Click to expand...
Click to collapse
I used vanilla 1.1.5 jars - the same ones that I made a backup of before installing NTT.

ladykayaker said:
I used vanilla 1.1.5 jars - the same ones that I made a backup of before installing NTT.
Click to expand...
Click to collapse
Gotcha - okay well today some time I hope to have this installed and will report back on how the side buttons behave for me.

EDIT: @jeff_kz has fixed this. NookTouchMods is now working 100% and I no longer have a need for NTT or Button Savior!
--------------------------------------------------------------------------
dr_diem said:
Gotcha - okay well today some time I hope to have this installed and will report back on how the side buttons behave for me.
Click to expand...
Click to collapse
I'd be insterested to know. For now i have gone back to NTT. With NTT I modified the quicknav icons in framework-res.apk.
With nooktouchmods the icons for quicknav are not pretty at all and the font is too large.
With NookTouchMods I like being able to toggle the glowlight instead of having to first pull up the glowlight settings window.
and with nooktouchmods the longpress takes me to android home without glowlight turning on, which is great.

[APP][NST/G] Alternate Power Menu

6-22-23: Update to 1.2
--removed dependency on Screenshot Easy app (you can uninstall it)
--added small binary file, fb2png, to replace broken native screenshot binary
This app enables an alternate shutdown menu dialog which includes some typical items in an "extended" power menu: Power Off, Reboot, and Screenshot (see screenshots below). Functional in both Portrait and Landscape orientation.
Requirements
--Root
--fb2png binary
--As this is a Tasker-generated app (but does not require Tasker to run!) there is a dependency on two library files
1. Copy the two files found in the attached zip into the locations shown below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
2. Copy fb2png to /data/local. Permissions should be rwx-rx-rx.
3. Create the folders /sdcard/Pictures/Screenshots (if not already existing).
4. Install the Power Menu app.
---------------------------------
How to use
The alternate menu can be invoked either by tapping on the app icon or by assigning the app to a hardware button using Nook Touch ModManager (I use a long-press of the "n" button).
"Power Off" invokes the stock power-off dialog and requires root so expect a Superuser request on first run.
"Reboot" invokes a dialog similar in appearance to the stock power-off dialog and, if confirmed, executes a full reboot, starting from the "Read Forever" screen. This is executed via a shell command and also requires root.
"Screenshot" uses the fb2png to create an image file (in .png format) from the contents of the frame buffer. When a screenshot is taken, there is a brief pause, then a brief "flash" of a smaller image of the screen (see image attached), followed by a notification.
Ideally this might replace the hardware-button shutdown but Android zealously protects that one button from being hijacked. There is an app which appears able to do the trick, but it only runs on Jellybean or higher
Bug reports/comments are welcome.

Ideally this might replace the hardware-button shutdown but Android zealously protects that one button from being hijacked. There is an app which appears able to do the trick, but it only runs on Jellybean or higher
Click to expand...
Click to collapse
didn't someone already hijack it by adding the 'reboot' and 'recovery' buttons to this button ... can't your app too be assigned like that app ?

aiamuzz said:
didn't someone already hijack it by adding the 'reboot' and 'recovery' buttons to this button ... can't your app too be assigned like that app ?
Click to expand...
Click to collapse
I looked at the mod which requires altering jars and apks. I could not decipher the patches (on older FW, to boot) and the OP did not list them, so it's a no-go for me.

nmyshkin said:
I looked at the mod which requires altering jars and apks. I could not decipher the patches (on older FW, to boot) and the OP did not list them, so it's a no-go for me.
Click to expand...
Click to collapse
Oh ok ... could @Renate be of any help ... in helping you decipher it ?

I've never seen the patch.

Renate said:
I've never seen the patch.
Click to expand...
Click to collapse
Nor have it. All the patching is done on framework.jar but there's no documentation so you would have to do a diff and tease out the patches.
That's the "good" news. As for modifications, I would not know where to start. As you are well aware, I am no Java programmer nor at my age do I aspire to that exalted skill. This little app I cooked up (in this thread) suits my needs.

hmmmmmm ... tech talk ... i seldom understand beyond a point ...
I like the fact your @nmyshkin power button does not have 'Recovery' option given you brought it to my attention on the detriments of accidentally invoking booting into 'Recovery' ... if one has installed CWM recovery on to the device then there is no harm on accidentally ending up choosing recovery, in fact its a convenient option, BUT for people who choose to leave the stock recovery as is ... the accidental booting in to recovery will prove to be catastrophic for the fact that it resets the device to factory without any warning.
If only i knew who the author was of that app that was able to patch the device so the power button could trigger the power down menu ... would've been nice to know and attempt a modification of your app so as to bind it directly to the power button. Until then we can surely manage with your current implementation.
thanks for your invaluable contributions @nmyshkin ... to this small NST/G community.