[Q] n button is not working! - Nook Touch General

Hello there, i've bought nook glowlight(bnrv500) 2 days ago. Tried to register device but it was giving me error. So i couldn't complete registration no matter how many times i tried.
Then i rooted nook. Opened launcher through adb and removed oobe.apk. Now when it boots, launcher is opening so registration problem is solved now.
But n button is not working!
I've found that when i change system/usr/keylayouts/gpio-keys.kl i can change the behaviour of n button.
key 158 BACK WAKE_DROPPED
key 102 HOME
key 116 POWER WAKE
I've tried WAKE and WAKE_DROPPED also. Nothing changes. When i press for 2 seconds back lightning is working. And when i press n button while nook is asleep. it wakes the device so there is no hardware problem.
I've also tried some of the button reassignment apps with no result. What do you think i can do?

I'm looking into this.

ИΘΘK¡€ said:
I'm looking into this.
Click to expand...
Click to collapse
Thanks very much. Could you find anything?

kreston said:
Thanks very much. Could you find anything?
Click to expand...
Click to collapse
Nothing promising yet. I'll post in this thread when I find something, though.

Related

[SOLVED][REMAP DIAL BUTTON TO SEARCH BUTTON] Lack of search button

Hi.
I really miss the search button from the Desire device. I have tried to remap the send (dial) button to search by altering the bravo-keypad.kl file in /system/usr/keylayout. But the change didn't work. My altered keypad file is posted below, maybe someone can tell me why it's not working?
SOLUTION: Edit the right file. In my build the default qwerty.kl file was used not the bravo-keypad.kl. Adding SEARCH to key 231 and 61 turns the send key into a search key Even voice search by long press works
key 102 HOME
key 139 MENU
key 158 BACK
key 217 SEARCH
key 107 ENDCALL WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 231 SEARCH
key 61 SEARCH
Sent from my HD2 running Android
just revert what you changed back to how it was.
then hold down the start button (Windows Logo) and the keyboard will pop up, once you start typing it will go into the search app.
mr_billionaire said:
just revert what you changed back to how it was.
then hold down the start button (Windows Logo) and the keyboard will pop up, once you start typing it will go into the search app.
Click to expand...
Click to collapse
Thanks for that tip, but unfortunately it does not work inside all applications.
Thought u ment the Hardware search buttom, missing that a lot, couse a lot of apps maps it (search buttom) to combine some function. If we take ån sms progie fex. The search buttom is maped to compose sms's, hope someone fine a way to map a Hardware key to the search buttom
Yeah I need to map Multi Task manager to a hard key, can you help with that?
-------------------------------------
Sent via the XDA Tapatalk App
Cobra2 said:
Thought u ment the Hardware search buttom, missing that a lot, couse a lot of apps maps it (search buttom) to combine some function. If we take ån sms progie fex. The search buttom is maped to compose sms's, hope someone fine a way to map a Hardware key to the search buttom
Click to expand...
Click to collapse
This is exactly what I have done, remapped the physical send button (left most button on the HD2) to behave like a search button. HTC Desire does not have a send button either, and I don't miss it. I find it more usefully to have a search button then a send (call) button.
Sent from my HTC Desire using XDA App
Where are you entering this data to change these settings?
-------------------------------------
Sent via the XDA Tapatalk App
Try remapping a button to DPAD_CENTER and see if it works for the trackball in camcorder.
paalkr said:
This is exactly what I have done, remapped the physical send button (left most button on the HD2) to behave like a search button. HTC Desire does not have a send button either, and I don't miss it. I find it more usefully to have a search button then a send (call) button.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi paalkr
Where is the file qwerty placed ? That would be great if it worked for me, I really miss the hardware search buttom.
Thanx
Cobra2 said:
Hi paalkr
Where is the file qwerty placed ? That would be great if it worked for me, I really miss the hardware search buttom.
Thanx
Click to expand...
Click to collapse
All files related to key mappings are located in /system/usr/keylayout . The qwerty.kl is the one that android is defaulting to if not specified otherwise. There may be some other kl files in the folder, but the vendor specific file is just "left overs" from the ROM rip (in some cases).
paalkr said:
All files related to key mappings are located in /system/usr/keylayout . The qwerty.kl is the one that android is defaulting to if not specified otherwise. There may be some other kl files in the folder, but the vendor specific file is just "left overs" from the ROM rip (in some cases).
Click to expand...
Click to collapse
Thanx big time mate for pointing me the right place, that is just what i needed for the handcent sms.
Sent from my HTC HD2 using XDA App
Mapping End Key
Has anyone mapped the end call button to work. On my Darkstone build I have to hit the end call on screen, hitting the red hard key just shuts the screen off (very annoying). I then have to wake up the phone and end the call.
I pulled both bravo_keypad and qwerty files but both seem to be set to the right end key.
Any ideas or help?
Jwatt0918 said:
Has anyone mapped the end call button to work. On my Darkstone build I have to hit the end call on screen, hitting the red hard key just shuts the screen off (very annoying). I then have to wake up the phone and end the call.
I pulled both bravo_keypad and qwerty files but both seem to be set to the right end key.
Any ideas or help?
Click to expand...
Click to collapse
theres an options in the settings menu to do this, i just cant find it. I used to have it set correctly, but changing roms every few days, you start to get confused. I would appreciate it if someone could point us in the right direction.
Thank you.
Thanks for this useful tip that works perfectly !
A way to only map quick press to Search and keep long press on DIAL Button associate to Phone ?
here is my qwerty.kl file. what did i do wrong?
songokussm said:
here is my qwerty.kl file. what did i do wrong?
Click to expand...
Click to collapse
Didn't succeed either, I mounted system as read write and modified qwerty.kl, rebooted but nothing changed. I would like a lot too having the search button on the call key :-(
I am on Shubcraft build
DocteurN said:
Thanks for this useful tip that works perfectly !
A way to only map quick press to Search and keep long press on DIAL Button associate to Phone ?
Click to expand...
Click to collapse
I would like that too, but I haven't sorted that out.
songokussm said:
here is my qwerty.kl file. what did i do wrong?
Click to expand...
Click to collapse
Could be that your build uses an other file then the qwerty.kl. Have you tried to edit the vendor specific file instead?
on my device using shubcraft v1.4 it was the htcleo-keypad.kl
Sent from my HD2
phrozendevil said:
on my device using shubcraft v1.4 it was the htcleo-keypad.kl
Sent from my HD2
Click to expand...
Click to collapse
phrozendevil is 100% correct it is the htcleo-keypad.kl file.
Now i just need help with chaning the volume buttons to the camera buttons.
I changed:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
To:
key 115 CAMERA WAKE
key 114 CAMERA WAKE
Upon press it starts the camera app, but will not take a photo. However when i switch to the camcorder function, that works just fine.
Ideas?
ps: i just use a widget to control my volume, which is very rare for me.

Disabled n button from waking up device?

Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App
ramiss said:
Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
I don't know that you can stop one of the 4 inputs from waking up the hardware, but...
You can define the 'n' button to do something that doesn't offend you and set your screen to sleep after a very brief moment (15 seconds).
Why do you want to change the hardward button behavior?
byronczimmer said:
Why do you want to change the hardward button behavior?
Click to expand...
Click to collapse
Hi, thanks for answering. The reason for this request is because the screen keeps waking up as it moves around in my bag. Just lightly pushing on the case/cover I use will activate the button and leave the screen on until the timeout. I am surprised this isn't an issue for more people (or perhaps people aren't noticing their nook turning on.)
Lowering the timeout is not going to work since I do a lot of reading and having to tap the screen every 15 seconds would be a pain. Unless anyone has figured out how to get screebl to work??
You can completely disable the "N" button by editing the keyboard layout file. Using Root Explorer (paid app - but WELL worth it!) or equivalent, navigate to SYSTEM>USR>KEYLAYOUT then click the button at the top to "Mount R/W", now long-press the file "qwerty.kl" and choose "Open in Text Editor". Then find the following line:
Code:
key 102 HOME WAKE
and simply add a # to the beginning of that line so that it looks like this:
Code:
#key 102 HOME WAKE
Now press your MENU button and choose "Save & Exit". You'll need to reboot the Nook for the change to take effect.
Now your N button should be completely disabled. Just make sure you have the soft keys set up with a home button so you'll have a way to use that functionality when needed.
If you want to maintain the functionality of the "N" button but just prevent it from waking the Nook, simply remove the word WAKE from that line and don't insert the # character. I haven't tried this implementation, but it should work fine.
If you did what jason suggest, make sure you not hide the status bar.
You can change the "unhide" button to something else in Tablet Tweaks or you can use the long-press Power menu option which is also in Tablet Tweaks.
911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
Simply removed WAKE from the home button as suggested.
Works beautifully. Doesn't wake the device, yet does all the other stuff it's supposed to.
Score one victory for increased battery life for shared knowledge.
I have a soft case and it gets turned on in my pocket.
I went ahead and also removed WAKE from the volume up and down buttons.
Now the only way to wake the screen is the power button. The way my case is, that's the one button that won't get pressed in daily travel.
(don't know if reboot is necessary, but i'd assume so, and did after each change before testing)
Thanks!
TCAndroid said:
911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
[ ... ]
I went ahead and also removed WAKE from the volume up and down buttons.
Click to expand...
Click to collapse
I also took WAKE off the volume keys, because I tend to reach into my bag and adjust the volume while walking or waiting for the train. My buttons don't tend to get pressed, since my bag is for a netbook and my uncased NC doesn't rattle around. However, after adjusting the volume, the screen was live and the bag and its contents sometimes made random touches all over the screen...
The volume buttons now work exactly the way I want! Thanks for the very clueful answer to this question!
Of course, now I have another thing to do every time I update my ROM. I should learn how to make update scripts!
I am curious why HOME has WAKE and not WAKE_DROPPED, when it appears to behave like WAKE_DROPPED.
From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.
911jason said:
From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.
Click to expand...
Click to collapse
Exactly so. HOME acts like WAKE_DROPPED, doesn't it? But it's marked WAKE.
Actually, yes, you're right... just realized that. Not sure why it's behaving that way.

[SOLVED] End call with back key

This feature is now available in FroyoBread. Thank doixanh.
i wonder if it can be remapped to the camera button instead. some of us still use the back button to navigate around while chatting on the phone (handsfree mode)
There is a thread allready for this!
http://forum.xda-developers.com/showthread.php?t=1044810
No, use... we need a pro to do this...
Sent from my X8 using Tapatalk
I also think that this will be perfect
There must be some correlation between files shakira_keypad.kl and 7k_handset.kl
because the second one has lines
Code:
107 ENDCALL WAKE_DROPPED
116 POWER WAKE
and the first one
Code:
key 158 BACK WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 102 HOME WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 215 FOCUS
key 212 CAMERA
key 107 POWER WAKE_DROPPED
and when you change key 107 into ENDCALL, power button also ends calls,there must be something to make back button to has multiple actions without loosing its original function...
Or to make back button like power button just during call
Sent from my X8 using Tapatalk
I tried editing those files, but in every case I loose back button function...
Charmed :) said:
I tried editing those files, but in every case I loose back button function...
Click to expand...
Click to collapse
Yup. I know. I hope it's posiblle to make back key as "ENDCALL" just during phone calls...
Damn it! If we can have all other features thanks to our module man doixanh, we could have this too.
I think that this is way more important than multitouch, or screen on/off animation.
I use power button to end calls. It's enough for me
It's even better then wait till the display turns on to end a call...
When you say power button you mean the one that turns off the screen right?
I tryied this today but the screen turned off without ending the call...
I do not think it can be changed from phone's files. We need an apk programer. The solution must be in the phone.apk
Yours GreatApo
(X8 under MiniCM)
GreatApo said:
When you say power button you mean the one that turns off the screen right?
Click to expand...
Click to collapse
Right, this one that turns off the screen/phone.
I have only add the line
Code:
key 107 ENDCALL WAKE_DROPPED
in shakira_keypad.kl and reboot my phone.
I use stock rom...
GreatApo said:
I do not think it can be changed from phone's files. We need an apk programer. The solution must be in the phone.apk
Click to expand...
Click to collapse
Hmm... but what about all of these replacments for dialer? Or it changes just dialer, not phone.apk?
Deeeevss? We need your asses
I am a web developer... may be I can find how to fix the phone.apk. The problem is that I have no freetime... I will try to have a look in phone.apk files...
Yours GreatApo
(X8 under MiniCM)
K, but do you know how to write in C?
And I think you need Linux64bit and Android sdk and ndk for starting such development.
You should ask blagus or someone other expirienced for info about developing tools, especially apks
Sent from my X8 using Tapatalk
Someone finally! Thank you for even announcing that you will try to do something!!!
Any progress?
I thought that you guys have this already?
No...is there a way? ( You are our only hope module man )
Yeah I think I can include it in FroyoBread

[guide] disable capacitive buttons

I have seen a bunch of posts regarding the capacitive buttons and on screen navigation buttons. Love them or hate them, this is how you can turn them off.
I will leave that up to you on how to get onscreen Navy buttons.
As for turning off the capacitive buttons this is how I did it.
1.To eneble onscreen buttons follow this thread http://forum.xda-developers.com/redm...mi-1s-t2950455
2. Download a root file explorer. Root Browser Lite --> http://goo.gl/b9ISW This is what I will use.
3.Load up Root Browser and navigate to system>usr>keylayout. We will be looking for a file called "atmel_mxt_ts.kl".
4. Select it and hit "Open as..." then "Text file" then "RB Text Editor"
5. Now we see this:
key 139 MENU
key 102 HOME
key 158 BACK
key 217 SEARCH
All you have to do is option out the keys you don't want to work with a #. So if you are like me and think the home button is fine, it will look like this.
#key 139 MENU
key 102 HOME
#key 158 BACK
key 217 SEARCH
6. When you have the ones you want optioned out just tap the little disk icon in the top right. It will ask for root rights, grant it, saved.
7. Now just reboot and DONE!
Tested on
1. One plus one a.k.a bacon(miui6, h2os, oxygen..you tell)
Sent from my bacon using Tapatalk
Hit thanks if this post helped you[emoji106]
Why on earth would anyone want to do that when there is a toggle to switch between On-Screen and Hardware Keys
PsyGik said:
Why on earth would anyone want to do that when there is a toggle to switch between On-Screen and Hardware Keys
Click to expand...
Click to collapse
OK give me a screen shot of that toggle in h2os,miui6
@Snapdragon815
Will this guide also turn off the HW key backlight?
Will it survive a reboot?
Mr.Ak said:
@Snapdragon815
Will this guide also turn off the HW key backlight?
Will it survive a reboot?
Click to expand...
Click to collapse
As you can see, i made this post 2 years ago, you can give it a try, do a backup on TWRP first, if everythinggoes as you expected, that good. If not you know how to restore.
Snapdragon815 said:
As you can see, i made this post 2 years ago, you can give it a try, do a backup on TWRP first, if everythinggoes as you expected, that good. If not you know how to restore.
Click to expand...
Click to collapse
Sorry for reviving the thread. ?
But I was hoping you atleast remember if this trick turn off HW key backlight or not.
Mr.Ak said:
Sorry for reviving the thread.
But I was hoping you atleast remember if this trick turn off HW key backlight or not.
Click to expand...
Click to collapse
Np mate,. Did it work? I don't rememberif it did or not

Rooted S8 on Nougat, want to disable home softpress waking phone

My problem is the software home button on the bottom of the screen. Any touch near the bottom of the screen when it's off will wake it.
I'm trying to disable that function so I can press anywhere on the screen and not wake it up.
I think the setting is in either Generic.kl or gpio-keys.kl in the keylayout folder, but I don't know exactly.
I've tried disabling anything relating to Home in those files, but to no avail.
Any help would be greatly appreciated
crazysoccerman said:
My problem is the software home button on the bottom of the screen. Any touch near the bottom of the screen when it's off will wake it.
I'm trying to disable that function so I can press anywhere on the screen and not wake it up.
I think the setting is in either Generic.kl or gpio-keys.kl in the keylayout folder, but I don't know exactly.
I've tried disabling anything relating to Home in those files, but to no avail.
Any help would be greatly appreciated
Click to expand...
Click to collapse
I am going to assume they are in there I will look around tonight and see if I can find anything related as well...Even with mine turned down Its awfully sensitive..
TheMadScientist said:
I am going to assume they are in there I will look around tonight and see if I can find anything related as well...Even with mine turned down Its awfully sensitive..
Click to expand...
Click to collapse
I figured out how to disable it from turning on the screen.
In Generic.kl put # in front key 172. Save and then reboot for it to take effect.
The phone still vibrates when you press the bottom of the screen, however the screen doesn't turn on.
crazysoccerman said:
I figured out how to disable it from turning on the screen.
In Generic.kl put # in front of key 143 and key 172. Save and then reboot for it to take effect.
I'm sure which one it is exactly, but disabling both of those worked. The phone still vibrates when you press the bottom of the screen, however the screen doesn't turn on.
Click to expand...
Click to collapse
Does the home button still work?
TheMadScientist said:
Does the home button still work?
Click to expand...
Click to collapse
I use lmt pie control so I don't know. I would wager it's disabling the wakeup input rather than the home input that actually works.
Edit: It's key 172, not 143.

Categories

Resources