Related
Only thing I have not been able to recover since the SP1 update
The two custom buttons for opening the Snapview control application and the Screen resolution switcher are dead.
I've gone through the HTC folder and can't find anything to reactivate these buttons or assign them to the correct apps.
Anyone else notice this?
Kakyou said:
Only thing I have not been able to recover since the SP1 update
The two custom buttons for opening the Snapview control application and the Screen resolution switcher are dead.
I've gone through the HTC folder and can't find anything to reactivate these buttons or assign them to the correct apps.
Anyone else notice this?
Click to expand...
Click to collapse
No, It's working here
No problems with mine either. sorry.
Execute \program files\htc\control\setup.exe . It will remap the buttons....
hmmm. strange. Ran it several times (once right after the update, once just now) and still no effect.
Buttons are still dead. Maybe something else is conflicting with it.
Pretty vanilla setup. Nothing added after the SP1 update (done using Windows Update).
Office 2007 installed. Bitdefender AV.
Only slightly off thing I am running is Firefox 3b4
Buttons assignment
Remaping of buttons is not by Snapview!
Buttons are working as Synaptics touchpad directional buttons.
Run Synaptics control panel and there is remaping of buttons.
Go:
MOUSE properties-SETTINGS-BUTTONS-SCROLL UP BUTTON-CONFIGURE.
For "Start ControlCenter" Define
SCROLL LEFT BUTTON as START SELECTED APPLICATION - Program Files\HTC\ControlCenterLauncher.exe
For "Change resolution button" Define
SCROLL UP BUTTON as START SELECTED APPLICATION - Program Files\HTC\ResolutionSwitchLauncher.exe
It is not detailed tip - You must help myself a bit.
I did it on my Shift and is it fully working.
Awesome! That seems to have done it. Thanks!
As an added bonus, I now can configure the buttons to be anything I want. Very cool.
Directions
I am not sure in directions,
may be is it RIGHT and DOWN directions.
You must try it.
1. Looking at buttons in Settings, the list is simply empty, no buttons to assign. Am I doing something wrong?
2. Also, I can't find an option to make the X button actually close an app, instead of minimizing it. Again, am I doing something wrong?
3. I noticed that on first startup Windows doesn't ask you to align the screen. Yet the option is there. But how do you accurately align the screen with fingers? I find the screen very unresponsive in the top left and right corner. Also, while typing I have to aim somewhat above the key I mean to hit. Is this a question of getting used to, or has it to do with bad alignment?
4. Where's the autorotation? Is there a way to tell the device which apps to autorotate and which not? For now, hardly anything rotates of its own accord. And since I can't assign rotation to a button it might as well go without a G-sensor.
bartveld said:
1. Looking at buttons in Settings, the list is simply empty, no buttons to assign. Am I doing something wrong?
2. Also, I can't find an option to make the X button actually close an app, instead of minimizing it. Again, am I doing something wrong?
3. I noticed that on first startup Windows doesn't ask you to align the screen. Yet the option is there. But how do you accurately align the screen with fingers? I find the screen very unresponsive in the top left and right corner. Also, while typing I have to aim somewhat above the key I mean to hit. Is this a question of getting used to, or has it to do with bad alignment?
4. Where's the autorotation? Is there a way to tell the device which apps to autorotate and which not? For now, hardly anything rotates of its own accord. And since I can't assign rotation to a button it might as well go without a G-sensor.
Click to expand...
Click to collapse
With point 3, you'll get some debate about this with various people. I think there should be an alignment as everyone presses the screen at different angles and its not going to know that unless you align it.
HTC Hero had same problem, screen edges were unresponsive, until you did a calibrate of the keyboard and then it was perfect.
It is an option missing...!
ad 1: if you make shortcut of any program you want to run, rename it to long_send.lnk and copy to C:\windows, then long press left button and this program will be executed. (I downloaded from XDA rotate.exe to rotate screen)
ad 2: install Duttys HTC task manager, restart and X is back (also in settings yo can configure its function)
ad 4: there is a possibility to "unlock" rotation in registry, but as long as you can not see any buttons in buttons setting it's pointless... that's why I used point 1 solution
bartveld said:
3. I noticed that on first startup Windows doesn't ask you to align the screen. Yet the option is there. But how do you accurately align the screen with fingers? I find the screen very unresponsive in the top left and right corner. Also, while typing I have to aim somewhat above the key I mean to hit. Is this a question of getting used to, or has it to do with bad alignment?
Click to expand...
Click to collapse
It's still there (sorry in Dutch)
Start > Instellingen > Menu > Meer > Systeem > Scherm
In English it should be something like
Start > Settings > Menu (at the bottom of the screen) > More > System > Screen
Vlk_77 said:
ad 1: if you make shortcut of any program you want to run, rename it to long_send.lnk and copy to C:\windows, then long press left button and this program will be executed. (I downloaded from XDA rotate.exe to rotate screen)
Click to expand...
Click to collapse
Is this some cruel joke ? how did you do that on HD2 ?? Would be awesome if it worked....
EDIT: MY BAD.... Best trick ever !! thx !
Thanks for the input, everybody.
if you make shortcut of any program you want to run, rename it to long_send.lnk
Click to expand...
Click to collapse
Still, that gives me just one long press button to assign. There are at least three buttons that could be used for different apps. I just don't understand what HTC were thinking. Why have 5 buttons on a device and disabling the assign option?
It's still there (sorry in Dutch)
Start > Instellingen > Menu > Meer > Systeem > Scherm
Click to expand...
Click to collapse
I know it's still there, but I wonder how you can properly align a screen with finger presses as opposed to the pinpoint accuracy of a stylus.
Before this I had the Omnia 2 with the same lack of autorotation options (actually, I'd hoped that returning to HTC would have solved that, but no...). Some clever developer had whipped up a very nice program called RotationDetection, with which you could decide which apps should autorotate. Something like that should be made for the HD2!
Vlk_77 said:
ad 1: if you make shortcut of any program you want to run, rename it to long_send.lnk and copy to C:\windows, then long press left button and this program will be executed. (I downloaded from XDA rotate.exe to rotate screen)
Click to expand...
Click to collapse
I tried this, and for some reason I can't get it to work. Here's what I did:
Downloaded rotate.exe to my storage card.
Created a shortcut to rotate.exe, also on the storage card, and renamed it long_send.lnk
Copied this shortcut and pasted it in the Windows directory on the phone.
Now, if I select long_send.lnk in the Windows directory, the screen does indeed rotate. But I can't get the screen to rotate by holding the send key down.
I have already soft-reset, and this does not solve the problem.
Any ideas?
robertlewisca said:
I tried this, and for some reason I can't get it to work. Here's what I did:
Downloaded rotate.exe to my storage card.
Created a shortcut to rotate.exe, also on the storage card, and renamed it long_send.lnk
Copied this shortcut and pasted it in the Windows directory on the phone.
Now, if I select long_send.lnk in the Windows directory, the screen does indeed rotate. But I can't get the screen to rotate by holding the send key down.
I have already soft-reset, and this does not solve the problem.
Any ideas?
Click to expand...
Click to collapse
Did you use THIS Rotate Screen with the shortcut link?
http://forum.xda-developers.com/showthread.php?t=347705
You will need to install Rotate Screen.cab (or Rotate Screen CW.cab) 1st
The Rotate Screen CW.cab is for counterclockwise rotation.
For me it's working great. When I hold the "call" button for some time the screen rotates.
did anyone install AEbuttons on the HD2
it works wonderfully on X1, HD1, diamond 2. it can assign 4 programs or functions to each button and that includes the volume buttons
htc-hd2 said:
Did you use THIS Rotate Screen with the shortcut link?
http://forum.xda-developers.com/showthread.php?t=347705
You will need to install Rotate Screen.cab (or Rotate Screen CW.cab) 1st
The Rotate Screen CW.cab is for counterclockwise rotation.
For me it's working great. When I hold the "call" button for some time the screen rotates.
Click to expand...
Click to collapse
Okay, so I used that rotate screen cab, installed it, found the shortcut it created in windows/start menu/programs and copied it. Then, I pasted a shortcut to it in the windows directory, and renamed that shortcut long_send.lnk. Then restarted.
Still doesn't work. When i run the shortcut directly in the windows directory, the screen rotates. When I run the 'Rotate' shortcut from the Start menu, the screen rotates. When I long press the send button, the screen does not rotate. Am I missing a step?
Not sure what you call the "send" button.
It's the most left button on the bottom that you need to press for about 3 to 4 seconds.
One more thing..
The "long_send.lnk" should be in the Windows directory.
htc-hd2 said:
Not sure what you call the "send" button.
It's the most left button on the bottom that you need to press for about 3 to 4 seconds.
Click to expand...
Click to collapse
Yes, the button on the bottom left - the one that if you press and release takes you to the phone screen. At any rate, I can't get it to work the way that has been described. Any suggestions?
I just did this and works realy good.
Thanks for the great tip.
htc-hd2 said:
One more thing..
The "long_send.lnk" should be in the Windows directory.
Click to expand...
Click to collapse
Yes, as i mentioned, I put the 'long_send.lnk' shortcut in the Windows directory. Have tried and retried this about a dozen times now. Still no joy.
Not sure about rotate.exe, but FWIW, Gyrator 2 works fine and is customizable based on apps.
robertlewisca said:
Yes, as i mentioned, I put the 'long_send.lnk' shortcut in the Windows directory. Have tried and retried this about a dozen times now. Still no joy.
Click to expand...
Click to collapse
Okay, I FINALLY figured it out, and I'll post what happened just in case anyone else runs into the same issue.
I followed the instructions as posted and changed the name of the shortcut to Long_Send.lnk and put it in the Windows directory. However, apparently when you use the Rename function, it just allows you to rename the file and not the extension. It doesn't indicate this anywhere, so I thought I was renaming both the file name and the extension. So, when I renamed to Long_Send.lnk, what I must have in reality been doing was renaming it to Long_Send.lnk.lnk - and therefore it didn't work.
Once it dawned on me that this might be the case, I renamed the shortcut again, this time without adding the extension at the end (Long_Send), and voila - it worked.
Never had to rename a file in WinMo before, so I was unaware that the Rename function only renames the file name, and not the file extension.
FYI, you can remap most (if not all) hardware buttons with the .lnk hack. Here's more information on how to do it.
Unlike programs like AEButton Plus, it will only allow you to assign short and long keypresses (no double- and triple-presses), but won't consume any system resources, won't be draining your battery, won't conflict with any other software that uses keyboard hooks.
Use it with caution though.
I missed it - does aebutton work? How about the utility like this one: http://forum.xda-developers.com/showthread.php?t=256525
I could have sworn I saw one specifically for HTC phones to remap the volume. It was something like vol up = dpad up, hold up for dpad left...etc.
I never use the volume controls on my current phone (Advantage 7501), and I'm expecting to be able to use vol up/down as dpad up/down for scrolling list and most importantly next page in reading a book!
polstein said:
I could have sworn I saw one specifically for HTC phones to remap the volume. It was something like vol up = dpad up, hold up for dpad left...etc.
Click to expand...
Click to collapse
This is the one you mean: http://forum.xda-developers.com/showthread.php?t=552947. Haven't tried it yet.
i tried to use the new system.ext2 today but i got SOD so restored back to original version.
now my home hardware button isn't working, any ideas' why it would stop? or how to fix it?
tried a search but looking for home button seemed to turn up random results
ta very much, love this place
Have posted this in android forum but no luck::::
Any ideas?
Originally Posted by corollatercel
Does anyone else have a problem with the windows button not bringing up the menu in most screens? It works at the home page, web browser and market but inside of most programs downloaded or not the menu button just takes you back to the home screen. Anyone know a fix for this? I'm using the desire build 5.7 with cotulla's new zimage.
i've searched High and low to see if someone has posted it already and couldn't find a solution.
I have had a similar issue with trying to use android.
I have a euro hd2 with 2_12_50_02_2, using chucky gtx rom, installed following task 29.
The rom seems to work well in windows with the problem of non-functioning hard key buttons in the WINMO also. It seems impossible to assign functions to the hard keys via the windows settings - only the send key option is displayed. The send key (green) button works fine for bringing up the dial pad and the end key (red) works fine also. The start button appropriately brings up the windows menu in this rom, though i have noticed that it does not work on other roms. Currently my home key and back key do not appear to do anything in the WINMO under chucky gtx rom!!
This presents no problems in WINMO as htc sense is easily navigated use touchscreen only and to be honest i never even touch the hard keys. However, this presents a massive problem in ANDROID - the android becomes impossible to navigate as I cannot ever go back or use the home key to get to the main screen. This is the same in sense or launcher mode.
I am using a clean fat 32 4gb class 2 micro sd, desire build v 5.7 from gamesquare and tried all the latest zimage files from cotulla and others but always the same problem. the send key is working fine but then i cannot get out of the dial pad. pressing the end key puts the sense in lock and screen off and i can long press this to power down but if i unlock then i am just stuck at dialpad or where ever i was when i locked. the windows key seems to bring up context menu fine and long press brings up key board in android. The home button does seem to wake from sleep sometimes i think, back button does not seem to work at all.
I have tried changing the rootcfs as well but this did not do anything. I had the same problem on FROYO build so im guessing it might not be an android problem. I am using JMZ dual boot on new rom installs without any other programs on windows or anything else other than android on the microsd.
I have not tried any stock roms to see if they solve the button issue in WINMO but cant really understand why they dont work so well in ANDROID or are they linked as android is ontop of windows?
Ihave found a workaround by installing "soft home key" app from market place which is helpful. but still looking for a fix. All very frustrating!!!
Searched everywhere on xda for answers to no avail. even googling for days!!!
PLEASE HELP. I think im not alone if above post is anything to go by
seem to have the same problem myself.
a short press of the windows button goes home, a long press brings up the recent apps; not the menu.
same issue here
i looked at the files located under /system/usr/keylayout and they all indicated that the correct functions were assigned to the correct keys
anyone else have any ideas?
Just remove the Android file from SD, then reload. Done. These builds are not complete yet. Crap is bound to go wrong.
i think the word we are looking for ..is.........beta
can be closed
I had the same problem...The home button on my rooted Nook Color stopped working. I finally stumbled on the answer. I double clicked the home button and it brought up settings. The home button was set to softkeys instead of home. Just change it and it works again.
On my NST Glowlight, I have a case that is beautiful but unfortunately covers the back power button (Verso Prologue Antique Tan, currently a steal on Amazon at $10). When I close the cover, it bumps things on the screen and either opens random books (in ReLaunch) or loses my place (in Coolreader). Does anyone know of a simple app that triggers the screen lock so I can map it to a hardware button? I set a "Lock Screen" shortcut in ReLaunch but at least half the time it doesn't work (instead, it asks if I want to power off). Thoughts?
Install Button Savior and tap its on-screen power button.
cowbutt said:
Install Button Savior and tap its on-screen power button.
Click to expand...
Click to collapse
IMO Button Savior is an eyesore and I can already duplicate all of its functions with hardware button mappings. I want to be able to map power to a hardware button, which I know I can do if I have an app shortcut of some sort.
OK, I found my own solution and it works well enough that I thought I'd share.
I found a whole bunch of screen lock apps but they all require Android 2.2 or later.
Thinking outside the box, I instead downloaded a simple app called "White Screen Flashlight" and mapped it to my n button. Now if I push n the screen goes completely blank and doesn't register touch input, so it's safe. I have the added benefit that if anyone swipes my Nook and wants to see what I am reading, they get a boring empty screen when they turn it on. Sleep mode kicks in as normal.
Alternatively, use http://forum.xda-developers.com/showthread.php?t=1848962 to set a Lock PIN. I combine this with a Tasker rule that disables the PIN if I'm connected to a 'friendly' WiFi network (i.e. my home WLAN) and re-enables it when I disconnect.
cowbutt said:
Alternatively, use http://forum.xda-developers.com/showthread.php?t=1848962 to set a Lock PIN. I combine this with a Tasker rule that disables the PIN if I'm connected to a 'friendly' WiFi network (i.e. my home WLAN) and re-enables it when I disconnect.
Click to expand...
Click to collapse
That is a great idea! I previously set a lock on my Nook ST (pre-Glowlight), but this time I'm simply keeping it disconnected from Google and any sensitive information. There's a bar on the screensaver that gives "please return to..." information. I figure if someone steals it, they won't get access to anything but some books, and if it's lost, a kindly soul may return it.
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