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.
I just got an NST today and rooted it with the clockwork mod method. So far things are working pretty well, with one major setback: I am having trouble getting back to the ADW. I selected ADW as the default home, but the nook button -> home still takes me to the original home screen, and the menu bar at the top only shows menu & back buttons. So once I open an app, I have no way to launch anything else (besides rebooting, which will bring me back to ADW).
Any help would be greatly appreciated, and I apologise if this has been answered elsewhere, but I couldn't track it down...
Thanks!
Oh, also, I lose the navigation buttons when I go into of the nook interface/reader/settings etc.
Sent from my SGH-I997 using xda app-developers app
B&N modified Eclair co-opts the Home key.
You need to either install Button Saviour (which gives you a constant selection of micro buttons on the edge)
or install one of the mods here that will hack the "n" button.
I use a modified /system/framework/android.policy.jar but I'm trying to clean up the mod.
Thanks, button savior did the job. Actually, I had already installed it with the CWM flashes, but I just hadn't figured out how to activate it; I'd noticed the little icon on the side of the screen, but hadn't actually managed to click it!
An alternative to Button Savior is to launch NookTouch Tools and use it to customize the B&N QuickLaunch menu via the B&N Buttons option to open your launcher of choice instead of one of the standard B&N apps. I find the side buttons for BS, Virtual Button Bar or similar programs always seem to be too small to press when I want them, yet get in the way when I don't. The QuickLaunch menu also won't get closed accidentally.
I've over-ridden all of the standard app selections and don't actually see the B&N apps anymore unless I deliberately launch one.
Hmm, that sounds ideal, but I can't seem to find an apk anywhere, can you link me? The root process installed nookcolor tools, which doesn't seem to have that option.
Thanks!
Sent from my SGH-I997 using xda app-developers app
Nook Touch Tools is by XorZone.
Be sure to check the Show extra action buttons in recent dialog option to get the Home, Menu, Back, Search and Orientation options when you long-press the 'n' button, and you can completely eliminate the need for Button Savior.
Just got it up and running, that makes for a much more comfortable configuration. Thanks again!
Sent from my NOOK using xda app-developers app
Hello,
I have just made an account here so sorry if I'm putting this in the wrong subject or something.
Let me just get something straight...I'm 13...so please explain if asking me to do something like 'install a customized kernel' :laugh:
So, with the help of NookManager, which is awesome, I have managed to root my stock UK nook simple touch (n2e), running software version 1.2.1
It is great. I have managed to install many apps, such as Kindle, Dropbox, Gmail, Opera Classic, Titanium Backup, WikiMobile etc.
I attempted to remap the bottom page turn keys in order for the right hand key to be a back button and the left hand key to take me to my android home.
After using ES File Explorer (granting it Superuser permissions) and copying /system/usr/keylayout/TWL4030_Keypad.kl to my SD Card.
Next I edited it, roughly following an online tutorial, using Jota text editor (a free text editor I found on the android market).
Next I saved it, and used Root Explorer to mount /system/usr/keylayout as r/w and copy the file to it.
I rebooted my device, using ReLaunch, the default launcher supplied with NookManager. I discovered that the 'back' button worked, but the 'home' button instead worked as a menu button.
This was slightly annoying, but I managed to using the Nook Touch Mod Manager (or whatever its called), which I discovered later, to send me to my android home launcher (LauncherPro).
I then went to the stock Library app and discovered, much to my annoyance, that the top two page turn buttons would not work to turn the pages.
Obviously, I can still use the touch screen to turn pages.
So I thought, fine, I'll re-remap the keys back to their original positions and use the top soft-keys in the menu bar for back and menu buttons.
I tried this many times, using a variety of different tools (inc. ES file explorer, Root Explorer, DB text editor, Jota text editor, NookTouchModManager etc)
Every time, after I rebooted, the keys were mapped back to my original position (?!) and I could not use the page turn buttons.
I tried renaming the TW4030_Keypad.kl file to TW4030_Keypad.kl.backup to see if the system would reload this and make a new file with the default buttons (allowing me to use the page turn buttons) but this did not work. For some reason, no file was created, however, the keys were still working (to do back and menu).
Next I tried factory resetting the device (by Powering it off and, as it turned on, holding the two bottom page turn buttons, I had found out how to do this online), but, even with the Stock ROM, the page turn buttons would not work.
I tried doing the 'swap page turn buttons' thingy in settings, but that did not work either.
I re-rooted the device, and it still did not work.
As I said earlier, it is OK because I can use the touch screen to change the page, but I like the page turn buttons (one of the things that made me choose nook over kindle paperwhite) so any help would be greatly appreciated.
Thank You in Advance
Sorry for the long post
ps. I deleted the following stock apps using TitaniumBackup, DeviceManagerService, Music and Phone. I restored music and phone later.
Hardware button configuration
The four hard buttons are configured by /system/usr/keylayout/TWL4030_Keypad.kl
The "n" button and the power button are configured by /system/usr/keylayout/gpio-keys.kl
I don't use the stuff that you are using.
Some of that rewrites the keylayouts behind your back (I think).
Here's my TWL4030_Keypad.kl:
Code:
# Layout file for Nook Touch hardware buttons
key 412 LEFT_NEXTPAGE # Upper left
key 407 LEFT_PREVPAGE # Upper right
key 139 BACK # Lower left
key 158 MENU # Lower right
The LEFT_NEXTPAGE LEFT_PREVPAGE is done to make the usage compatible with the real PageUp/PageDown on Android 2.2
Set your reader page buttons as shown in http://forum.xda-developers.com/showthread.php?p=24632564#post24632564
Renate NST said:
The four hard buttons are configured by /system/usr/keylayout/TWL4030_Keypad.kl
The "n" button and the power button are configured by /system/usr/keylayout/gpio-keys.kl
I don't use the stuff that you are using.
Some of that rewrites the keylayouts behind your back (I think).
Here's my TWL4030_Keypad.kl:
Code:
# Layout file for Nook Touch hardware buttons
key 412 LEFT_NEXTPAGE # Upper left
key 407 LEFT_PREVPAGE # Upper right
key 139 BACK # Lower left
key 158 MENU # Lower right
The LEFT_NEXTPAGE LEFT_PREVPAGE is done to make the usage compatible with the real PageUp/PageDown on Android 2.2
Set your reader page buttons as shown in http://forum.xda-developers.com/showthread.php?p=24632564#post24632564
Click to expand...
Click to collapse
Thanks so much for replying. Being a n00b, I am slightly confused about some things.
'I don't use the stuff you are using'
I assuming you are referring to the factory reset by booting down and holding the bottom two page turn keys. If so, this was the only way I could factory reset because the factory reset in settings got stuck on Deregistering your Nook (I assume because NookManagerService 2.1.apk had been deleted) and the 8 continuous reboots just made my device crash after I tried the first one (I had to do a hard reset with the trick of holding down the power and nook home buttons together for 40 seconds)
But I might be wrong. Are you talking about deleting DeviceManagerService 2.1.apk, or about my current key layout.
'Some of that rewrites the keylayouts behind your back (I think)'
Do you have any idea where that might be because I have been scouring my nook in root explorer and a search for 'key' or '.kl' only brings up the files in /system/usr/keylayout and some backed up .kl files on my sd card.
I am really confused because I know it must be communicating with another file (when I rename TWL4030_keypad.kl and omap_twl4030_keypad.kl and reboot it still sticks to the same keys and does not appear to generate a new file)
Also, however I modify the twl4030_Keypad.kl file (Root Explorer, ES File Explorer, Settings/Reader/Page Buttons, Nook Touch Mod Manager) the page buttons do not change, however the home button shortcuts (I set my home button to open my android home launcher (LauncherPro) on long press) work fine.
I tried editing the last pard of TWL4030_Keypad.kl to exactly what yours said, but same result probably due to what I have described in the above paragraph.
I just want to know, is there a way to completely reset all keypad files, or at least do something like that.
I cannot find anything about this on the internet other than cracked buttons, screen freezes etc.
Thank you very much for the help though.
Again, sorry for the long post.
Thanks again
ps Other than this (minor) issue, the nook is still working perfectly, apart from the occasional Barnes and Noble Nook Error Message (don't know why - I assume it has something to do with the deletion of the NookManagerService APK. The only reason I deleted it was that it was the only simple way to stop OTA updates, and I really don't want to see Barnes and Noble release an automatic update that bricks my rooted Nook, nor do I want to disable wifi whenever the update comes out, as some have suggested. When I factory reset, I get DeviceManagerService (and nook shop) back. Please let me know if the disabling of DeviceManagerService is necessary). It is just an annoyance.
I meant NookManager. I don't know if that goes around patching things or rewriting files.
Copy what I put in the box above and write it to the file.
Do things work?
Does that file get overwritten?
Renate NST said:
I meant NookManager. I don't know if that goes around patching things or rewriting files.
Copy what I put in the box above and write it to the file.
Do things work?
Does that file get overwritten?
Click to expand...
Click to collapse
I have done that (I did it just over your last thread) and the file does get overwritten. However, when I reboot, although the correct file is still there, the page buttons work as -------- --------
Menu Back
The file is still rewritten with the what you told me to put (minus the hashtags and the things that followed them, which I assumed were comments). This is why I am confused.
Thanks for helping. I'm sure there is a solution.
Also, I had no idea how to root a nook through any other method (USB Debugging is disabled, so how would you do it directly through ADB? I don't know)
One other thing - The page turn buttons worked just fine before I started editing - so im not sure nookmanager is necessarily to blame
Install UsbMode.apk (in the signature).
Among other things it will tell you what scan code and key code get generated for the hard keys.
(It does use the Android 2.2 names for PAGE_DOWN & PAGE_UP.)
Renate NST said:
Install UsbMode.apk (in the signature).
Among other things it will tell you what scan code and key code get generated for the hard keys.
(It does use the Android 2.2 names for PAGE_DOWN & PAGE_UP.)
Click to expand...
Click to collapse
Also, if you are using NookManager, make sure you have the hardware page keys mapped to "default" in Nook Touch Mod Manager when you are messing with the key layout file or you will get confused really fast. Conversely, if you are messing with NTMM mapping make sure you are using the stock key layout file to avoid confusion. NTMM has a hook in the Android key press code that captures the hardware keys to remap them to other keys or other functions. The key code NTMM sees is whatever the key layout file sends it. So if you key layout file remaps something NTMM will remap the remapped key rather than the actual key it says its remapping.
Thanks for all the help. I found out (using UsbMode.apk) that my top page turn buttons had scan codes but no key code, my bottom ones had both. I set all the page turn button shortcuts to default in Nook Touch Mod Manager.
I navigated through querty.kl, TWL4030_keypad.kl and omap_twl4030_keypad.kl and found out that the bottom keys had been called up earlier in the .kl file as menu and back. Using Root Explorer, I mounted the file system writable, deleted these earlier lines, then rebooted. It didn't work. After much more trying and rebooting, nothing worked, however, I had managed to unmap the bottom keys from menu and back, and now they are just shown in USBMODE as UNKNOWN.
I think I have a plausible solution. If one of you could send me your qwerty.kl, TWL4030_keypad.kl and omap_twl4030_keypad.kl files, then I could backup my originals and try copying them into /system/usr/keylayout. If logic talks, that should mean that, if your keys were working just fine for you, my keys should work in exactly.
Please let me know about this and send those files if you can.
Thanks in advance.
You already have my TWL4030_Keypad.kl, see above.
If that's not working, something is screwing around behind your back.
Renate NST said:
You already have my TWL4030_Keypad.kl, see above.
If that's not working, something is screwing around behind your back.
Click to expand...
Click to collapse
I tried using your twl4030_keypad.kl text earlier (as soon as I had seen your thread) but it was to no avail. I was actually referring to the physical files, not just the text from them. Also, I think that it is not just the twl4030_keypad.kl but also the other two files I mentioned above, because of what I did earlier.
Earlier, I looked at my querty.kl file and found that the keys 139 and 158 had been called up earlier for back and menu. I deleted these lines, and thought that my problem was solved. Unfortunately, what ended up happening was that I just lost my two back and menu-mapped page turn buttons. Now none of them do anything at all. Under your UsbMode.apk they are UNKNOWN.
I think something is screwing around behind my back, but I don't know what, how or where.
I have searched for 'key' and '.kl' before and only files I knew existed (in /system/usr/keylayout and in /sdcard) were found in the search results. Maybe it is a hidden file or something.
It is definitely not in /data because, after yet another factory reset (this time after renaming all my .kl files to .kl.test, the pages still did not work, stock or rooted.
Is there a simple way for a n00b like me to restore my nook completely, resetting /data, /system, etc.
If so, I would love to know.
Otherwise, please let me know if you have any ideas.
Again, sorry for the long post.
Thank you for all the help you've given me. I would have got nowhere near this far on my own.
If you think it would help, I could send you my /system/usr/keylayout zipped or something like that, I don't know about forum rules etc.
qwerty.kl is the default file only for Qwerty keyboards, that is USB keyboards
gpio-keys.kl is only for the power button and the "n" (home) button.
TWL4030_Keypad.kl is only for the four side hardware buttons.
If your four side hardware buttons are acting up the only thing in keylayout that can affect it is TWL4030_Keypad.kl
Do you have the file name capitalized correctly?
You are editing it with a Unix style text editor (LF, not CR/LF)?
I forget if it tolerates CR.
After you write it and reboot does it stay the way you wrote it last?
I'm giving you a thanks because, although the file had the right name and capitalization, and did not change on reboot. When I was carefully checking the name, I saw the permissions underneath. I edited them in root explorer to exactly what the permissions of the qwerty.kl and omap...kl
I rebooted and.....SOLVED!
So thank you very much for helping me and keeping me going on this.
I have 1 other thing I just wanted to ask. It is not major but is just slightly annoying me.
I have my four keys - this is what I want to happen:
Top left - Page Back and Volume Down (for modified Kindle app)
Top right - Page Forward and Volume Up (for modified Kindle app)
Bottom left - Menu
Bottom right - Back
I have tried to make this happen, but failed so reverted to a backup. This is what I have:
Top left - Page Back
Top right - Page Forward
Bottom left - Menu
Bottom right - UNKNOWN.
My main sub-annoyance (in this small annoyance) is the lack of the back button's working. It would be nice to have the top left and top right usable for pretty much any app that supports either nook page turn buttons or volume buttons for page turning.
Thanks again.
ps Don't worry about this one too much, it's not a big deal.
pps I'm going on a school trip, after which I am going on a youth camp trip, so from Sunday to Monday I won't be on here.
I'll be straight back when I can.
PowerNOOK said:
I have my four keys - this is what I want to happen:
Top left - Page Back and Volume Down (for modified Kindle app)
Top right - Page Forward and Volume Up (for modified Kindle app)
Bottom left - Menu
Bottom right - Back
Click to expand...
Click to collapse
I wanted my hardware buttons to page forward/back in the B&N stock reader and other readers I installed. So I contributed a mod to NTMM to support mapping a button to screen taps since most readers support page turns by tapping on the left or right side of the screen. I use the Tap Left/Right with the B&N reader, Aldiko and Overdrive Media Console and it works great. I just installed the stock (unmodified) Kindle app to test and it works with it as well.
So try this. Put your TWL4030_Keypad.kl file back to stock. Use NTMM to map your keys like this:
Top Left - Tap Left
Top Right - Tap right
Bottom Left - Menu
Bottom Right - Back
straygecko said:
So try this. Put your TWL4030_Keypad.kl file back to stock. Use NTMM to map your keys like this:
Top Left - Tap Left
Top Right - Tap right
Bottom Left - Menu
Bottom Right - Back
Click to expand...
Click to collapse
Thank you for this. I have tried it but could only get it to work with all the page turn buttons turning pages, not with back and menu. When I set the bottom buttons to back and menu, they do not work and neither do the top page turn buttons work as standard page turn buttons.
I am not too bothered about this, but the thing that is really annoying me is this: One of the bottom page turn buttons will not work. This is a variable, as, upon remapping, I can make the one that is not working at one time work fine another time, however, then, the other one will not work.
eg. The right bottom page turn button is not flicking the page forward. Using root explorer, I remap the right button as 'back'. Then the right button works, but the left one stops working.
Thank you for the help though, as I mainly use the top page turn buttons (they are right by my thumbs) and its really neat to have the same comfortable page turn buttons for both nook stock reader and kindle app
I think you have problems with your keylayout files. Attached are the stock files from the /system/usr/keylayout directory. Backup then delete everything in that folder and unzip this into it and then try mapping the keys with NTMM.
Sorry, but where are the attachments. Sorry if im being stupid.
PowerNOOK said:
Sorry, but where are the attachments. Sorry if im being stupid.
Click to expand...
Click to collapse
Sorry, I'm the one being stupid. Here's the attachment.
Thanks. ill try this when i get back to camp at the moment im using my friends wifi hotspot
I used root explorer to backup /system/usr/keylayout as /system/user/keylayout backup and then unzipped and copied and pasted your folder in. I found it to not work. I tried a lot of different things like editing lines, permissions, etc.
Eventually I gave up so I renamed my /system/usr/keylayout backup folder back to /system/usr/keylayout, hoping that a message would come up on the screen asking me if I wished to overwrite the files. No such message came up. Instead, I could see two folders in /system/usr, both entitled keylayout. I found the backup one and deleted it, then root explorer decided to delete both. Now, I have no keylayout folder, and none of the keys work. I tried re-decompressing your zip file and putting it in again, then factory resetting, but my nook stops me from registering after the wifi connection stage, with the following error message:
Error
Sorry we're having trouble setting up your NOOK.
Please shut down the device and try again.
For help, visit www.nook.com/support or call Customer Support on 1-800-THE-BOOK
(1-800-843-2665)
I have tried with many different wifi networks, but still the same result. I have tried rebooting several times by holding down the home and power buttons simultaneously for 40 seconds, and have re-factory reset but still no result.
Is there a backup image or something out there so I don't have to either treck to the shop from which I bought my nook or fork out £29
Please, any help would be hugely appreciated
I have just managed to use nook manager to completely restore my nook and then re-root it. everything is working great. i am now using nook touch mods manager to configure the page turn buttons and have the ideal setup I talked about earlier. I am just installing all the bits of pieces but everything is working. thank you to everyone for helping me so much. i am now going to only change button actions with nook touch mod manager and not do it manually.
Thank you so much jeff_kz for making NookManager