Questions regarding TF701T and keyboard dock - Asus Transformer TF701

1. Whenever I press the tablet's power button just to make it sleep (not shutting down, just sleep), the keyboard dock seems to keep the tablet awake. What can I do in order to get my tablet to sleep while the tablet is still connected to the dock?
2. There are some settings that I want to modify, such as text repeating speeds, the behaviors on holding down key buttons, find a way to "delete" words from the right of the text cursor, etc. Where can I do this?
3. Even if the keyboard dock build date is later than November 2013, but the tablet seat of the dock is still making the tablet wobbly (by a little bit), is it because I'm not seating the tablet deep enough? How deep should I push down, even after the locking mechanism is already in the locked state?
4. Are there any tutorial/guides on how to use the MobileDock keyboard? Everywhere I look in Google, it's always Reviews Reviews, and Technical Reviews.

tom_mai78101 said:
1. Whenever I press the tablet's power button just to make it sleep (not shutting down, just sleep), the keyboard dock seems to keep the tablet awake. What can I do in order to get my tablet to sleep while the tablet is still connected to the dock?
2. There are some settings that I want to modify, such as text repeating speeds, the behaviors on holding down key buttons, find a way to "delete" words from the right of the text cursor, etc. Where can I do this?
3. Even if the keyboard dock build date is later than November 2013, but the tablet seat of the dock is still making the tablet wobbly (by a little bit), is it because I'm not seating the tablet deep enough? How deep should I push down, even after the locking mechanism is already in the locked state?
4. Are there any tutorial/guides on how to use the MobileDock keyboard? Everywhere I look in Google, it's always Reviews Reviews, and Technical Reviews.
Click to expand...
Click to collapse
1. Try just closing the lid? The not sleeping issue has been an issue on other transformers as well.
2. shift + backspace = delete. No options for the text repeating speed I'm aware of.
3. Known issue - you can fix it yourself with some foam tape. Asus cannot fix it as I have found out.
4. What do you want to know?

sbdags said:
4. What do you want to know?
Click to expand...
Click to collapse
Anything from telling you what button does what to hotkeys in Android.
There are a few keys I don't understand, such as keys with weird symbols on it. The hotkeys is needed, because I would like to use them often.
I am not sure if common Android apps also used hotkeys optimized for tablets.

tom_mai78101 said:
1. Whenever I press the tablet's power button just to make it sleep (not shutting down, just sleep), the keyboard dock seems to keep the tablet awake. What can I do in order to get my tablet to sleep while the tablet is still connected to the dock?
Click to expand...
Click to collapse
Mine also has this 'issue'. Also, when the tab is in deepsleep i cannot wake it using the unlock button on the dock. When i just let the tab go into standby, or whatever it is called, and immediately use the unlock button it works. When letting it stand by for a bit longer and pressing the unlock button it doesn't do anything and i have to use the powerbutto on the tab to unlock. Any possible solution for this?
Verstuurd vanaf mijn K00C met Tapatalk

doom_71 said:
Mine also has this 'issue'. Also, when the tab is in deepsleep i cannot wake it using the unlock button on the dock. When i just let the tab go into standby, or whatever it is called, and immediately use the unlock button it works. When letting it stand by for a bit longer and pressing the unlock button it doesn't do anything and i have to use the powerbutto on the tab to unlock. Any possible solution for this?
Verstuurd vanaf mijn K00C met Tapatalk
Click to expand...
Click to collapse
The Asus docks have always worked that way. Deep sleep is deep sleep - power button to wake. Otherwise it has to waste battery and cpu cycles polling the dock to see if you have pushed the unlock button.

sbdags said:
The Asus docks have always worked that way. Deep sleep is deep sleep - power button to wake. Otherwise it has to waste battery and cpu cycles polling the dock to see if you have pushed the unlock button.
Click to expand...
Click to collapse
Didn't know that. Then, no issues
Verstuurd vanaf mijn K00C met Tapatalk

My other question is: Where can I find a list of hotkey combinations that I can use on the keyboard dock?
I only know a few shortcuts:
CTRL+C: Copy
CTRL+V: Paste
CTRL+A: Select All
CTRL+Z: Undo
One day, I hoped to see ALT keys used for inputting characters with symbols on them (like `e)

I just got my dock today (it is a 2013.10 but no connection issues yet). My boss is making me go to the UK in April so I made him buy me a dock instead of me getting a laptop.
Any who, you can configure the the keys to do what ever you want how ever it is a lot of work to set it up.
You need to scan the codes for each key and then modify the keyboard layout.
It can be done but it is a big pain in the ass.

Never heard of that before. Do you know how?

tom_mai78101 said:
Never heard of that before. Do you know how?
Click to expand...
Click to collapse
I thought I better take a closer look after I opened my big mouth and it is not the difficult
Attached is a key character map file that does what you specifically suggested ALT e is now mapped to `e however I think that there is a better solution that is already built into Android.
The below unicode characters are defined as dead keys in android what that means is this:
"When a dead key is typed followed by another character, the dead key and the following characters are composed. For example, when the user types a grave accent dead key followed by the letter 'a', the result is 'à'."
In the current key character map file "Generic.kcm" these are the dead keys
'\u0300': Grave accent. ALT + GRAVE
'\u0301': Acute accent. ALT + e
'\u0302': Circumflex accent. ALT + i
'\u0303': Tilde accent. ALT + SHIFT + GRAVE
'\u0308': Umlaut accent. ALT + u
For the attached unzip the file and put it in /system/usr/keychars and change the permissions.
Hopefully with the dead keys and adjusting the map, you can get all the characters that you need.

Further questions regarding special characters
Sleeepy2 said:
I thought I better take a closer look after I opened my big mouth and it is not the difficult
Attached is a key character map file that does what you specifically suggested ALT e is now mapped to `e however I think that there is a better solution that is already built into Android.
The below unicode characters are defined as dead keys in android what that means is this:
"When a dead key is typed followed by another character, the dead key and the following characters are composed. For example, when the user types a grave accent dead key followed by the letter 'a', the result is 'à'."
In the current key character map file "Generic.kcm" these are the dead keys
'\u0300': Grave accent. ALT + GRAVE
'\u0301': Acute accent. ALT + e
'\u0302': Circumflex accent. ALT + i
'\u0303': Tilde accent. ALT + SHIFT + GRAVE
'\u0308': Umlaut accent. ALT + u
For the attached unzip the file and put it in /system/usr/keychars and change the permissions.
Hopefully with the dead keys and adjusting the map, you can get all the characters that you need.
Click to expand...
Click to collapse
Hello, thank you for providing the asuspec.kcm file. I found the link to this through http://forum.xda-developers.com/showthread.php?t=2693602 and looked at the previous discussion in the thread to which you posted this message about the TF701T.
I am using a docked TF101 rooted with Katkiss 4.4.4 and I do not know if I can accomplish what you explain with a different model than TF701T.
I followed your instructions as best as I could understand. I put the asuspec.kcm in the location you instructed using SD Maid. I changed its permissions to be the same as those of the other .kcm files (-rw-r--r--).
I rebooted the TF101 and tried to type in special characters with the keyboard shortcuts. I believe I am missing additional steps to this process. Could you please instruct me on this matter?
Thanks in advance.

Related

Remapping the two small keyboard buttons

There are two small buttons (each marked with a small horizontal line) on the keyboard. The left is over the letters R and T. It is assigned to the "Send" button for email. The trouble is that it is very easy to hit by accident when typing R or T, and then the email flies off prematurely! The right one is assigned to the Menu and if you hit it by accident, it is easy to correct (just hit the OK button). Is there a way of remapping these two buttons? Except for this issue, the email with Kaiser is perfect. Does the AT&T Tilt have the same problem?
See my thread here. Those are the same as the softkeys on the font keypad (so remapping one remaps the other). I ended up using AE Button Plus to remap those (and other keys) to other functions, which I like because of the additional functionality that can be assigned to double clicks, triple clicks, etc. But if you just want to remap it to something else, check that thread for some alternatives.
dscline said:
See my thread here. Those are the same as the softkeys on the font keypad (so remapping one remaps the other). I ended up using AE Button Plus to remap those (and other keys) to other functions, which I like because of the additional functionality that can be assigned to double clicks, triple clicks, etc. But if you just want to remap it to something else, check that thread for some alternatives.
Click to expand...
Click to collapse
Err... I don't think this addresses the problem the OP has. I too suffer from this problem (must be big fingers!).
When using Outlook the soft keys change function so remapping the Today Calendar softkey, for example, doesn't help.
Anyone else got a solution to this problem, I'm fed up with sending half-finished e-mails!
I haven't played with AE Button Plus, but if you can assign "No Action" to a button (which some of the add-ons let you do) and do that for the messaging app specifically, then that would be a solution to the problem of large fingers/thumbs. The you could remap one of the FN keys you never use to the context menu or send...
TexasPenguin said:
Err... I don't think this addresses the problem the OP has. I too suffer from this problem (must be big fingers!).
When using Outlook the soft keys change function so remapping the Today Calendar softkey, for example, doesn't help.
Click to expand...
Click to collapse
As PerfAlbion pointed out, you can just remap them to nothing. I remapped these keys, not because of the problem with the keyboard, but simply because I never used them since it's just as easy to use the touch screen. But if you want to maintain the softkey functionality on those buttons, use AE button to map a single press to nothing, and a double-click (or even a click-hold) to the softkey function. You would then still be able to use them for their original purpose, but they wouldn't be as easy to accidentally activate.
dscline said:
As PerfAlbion pointed out, you can just remap them to nothing. I remapped these keys, not because of the problem with the keyboard, but simply because I never used them since it's just as easy to use the touch screen. But if you want to maintain the softkey functionality on those buttons, use AE button to map a single press to nothing, and a double-click (or even a click-hold) to the softkey function. You would then still be able to use them for their original purpose, but they wouldn't be as easy to accidentally activate.
Click to expand...
Click to collapse
I'm sorry, I must be missing something obvious here.
Any of the soft button remappers will NOT work on application-specific softkeys - AE ButtonPlus specifically says this in it's FAQ. Remapping the "send" key is application-specific - it only becomes the Send key when you launch Outlook. So how did you manage to re-map this key?
TexasPenguin said:
I'm sorry, I must be missing something obvious here.
Any of the soft button remappers will NOT work on application-specific softkeys...
Click to expand...
Click to collapse
The distinction is between remapping the softkey, or remapping the hardkey that correlates to the softkey. What the remappers can't do is change the function of the softkey... if, for example, Outlook is coded to make the left softkey the send key, you can't change that. That's programmed in to Outlook. But what you CAN change is whether or not the hard button that corresponds to the left softkey is recognized as the left softkey. For example, I've remapped the single press of the hard keys that correspond to the L & R softkeys to copy and paste, respectively. If I open Outlook, the soft softkey (the button on the touchscreen) is still going to be send. But my hard button is no longer mapped to be a softkey, it's mapped to be copy.
I used all the programs from the thread that you pointed out, including the cab file that was mentioned. This allowed me to change the left front soft key but does not affect the assignment of the left keyboard soft key as "Reply" when in email mode and with the keyboard slided out. Is there a way to change the left soft key assignment only for the email (eliminate the reply option) or just inactivate the left soft key altogether? I have installed the SoftKey applet form your thread in my Settings.
I sent my reply to one of the earlier messages wihout having read all the answers that came after it....I was out of the office for a couple of hours..my apologies. I will find the AE button plus and give it a try, but is there any registry solution? they usually work the best.
I downloaded and used the AE Button Plus, and it worked! I set it to double press and that did the trick. The program is very good by the way, the only one that allows multiple pressing options, etc.Many thanks!
I have benefited from this thread!
Thanks everybody.
Adequate description on the issue provided, and adequate solutions and then a follow up post.
A really appealing solution would be to isolate the keyboard softkeys from the front ones. I tried the double press method but it turned out to be incredibly annoying and I'm not sure that constant annoyance is outweighed by an accidental softkey hit on the keyboard. What I'd like to do is disable the keyboard softkeys while leaving the front ones completely intact on a single press.
I find it surprising that you even need to use the softkeys, period. I came to the Kaiser from a Smartphone edition phone (no touchscreen), which I had for for over two years. So I was completely accustomed to using the smartkeys. Yet, surprisingly, once I got the Kaiser, I found myself immediately and instinctually accessing their functionality from the touchscreen rather than the hard buttons. Perhaps because the hard buttons aren't directly under the screen like they were on my smartphone, so the tie betwee the label and the button wasn't as obvious as it was on the smartphone.
dscline said:
See my thread here. Those are the same as the softkeys on the font keypad (so remapping one remaps the other). I ended up using AE Button Plus to remap those (and other keys) to other functions, which I like because of the additional functionality that can be assigned to double clicks, triple clicks, etc. But if you just want to remap it to something else, check that thread for some alternatives.
Click to expand...
Click to collapse
Thank you, AE Button Plus worked great. I just deactivated the "Left Softkey" and now I don't have to take care of that damned button anymore.
dscline said:
I find it surprising that you even need to use the softkeys, period. I came to the Kaiser from a Smartphone edition phone (no touchscreen), which I had for for over two years. So I was completely accustomed to using the smartkeys. Yet, surprisingly, once I got the Kaiser, I found myself immediately and instinctually accessing their functionality from the touchscreen rather than the hard buttons. Perhaps because the hard buttons aren't directly under the screen like they were on my smartphone, so the tie betwee the label and the button wasn't as obvious as it was on the smartphone.
Click to expand...
Click to collapse
I've been using touchscreen pocket pc's for a while and no such instinct has kicked in.
so no one has an answer besides installing that AE button plus prog on the phone?
try removing the actual key. i wouldn't try it but it may work.
I'm really glad I found this thread, I keep sending half written and blank sms messages because of the left soft and keep doing weird things because of the right one. It's gonna cost me a fortune in text messages so I'm gonna go try that prog mentioned.
It would be better for a solution more specific to the application but this is certainly better than nothing!
the best solution I can think of is:
- remove the sender name whilst creating email.
if you accidently hit send it will prompt for sender info. when you are ready to send, simply insert the contact details in and all is well.
hope this helps some of you
firstbuddha said:
the best solution I can think of is:
- remove the sender name whilst creating email.
if you accidently hit send it will prompt for sender info. when you are ready to send, simply insert the contact details in and all is well.
hope this helps some of you
Click to expand...
Click to collapse
I think we have a WINNER SOLUTION

How to disable inner "soft" keys

How can I disable these?? The keys above and between "I" and "O", and between "R" and "T"? I hate them. I type incredibly fast and happen to blunder on them at least once per message, email, etc...
I've tried to change my typing style, but that isn't 100% effective and only slows me down.
I would like nothing to happen when I push them. I also do not use the "soft" buttons above the IE and Mail buttons. I don't have issues with accidentally hitting them, though. But if they get disabled with the ones in the full keyboard, it won't bother me (not sure if they're tied together).
I only want the actual onscreen soft buttons to work. Can anyone help?
By the way, I went into Settings > Personal > Buttons, but only 6 are shown (not counting "push and hold").
There are a total of 13 buttons on this thing if you include the push button on the wheel, and don't count the keyboard mappings. 11 buttons if you count the front and inside soft buttons as only 2....
I am currently searching for a solution to the same problem for the same issue. I cannot even count how many times I have accidentally hit the send button when all I wanted was the letter.
I am not that an incredibly fast typist, though.
I use AE Button Plus and this allows you to remap all of the keys to other things as well as map one, two and three presses along with long press.
You could use this to remap one press of the softkey to nothing and two presses to activate the softkey. This would mean that you would have to press them twice to make them work, but would stop teh accidental presses.
dryden said:
I use AE Button Plus and this allows you to remap all of the keys to other things as well as map one, two and three presses along with long press.
You could use this to remap one press of the softkey to nothing and two presses to activate the softkey. This would mean that you would have to press them twice to make them work, but would stop teh accidental presses.
Click to expand...
Click to collapse
Would that have the same affect on the "onscreen" soft buttons (touch screen).
I've just had a quick play and it appears to only affect the hardware buttons, which, I think, is what was originally wanted.
It's a good program, I use it a lot and it's FREE!
Is there nothing someone maybe found to disable these in the registry. I also hate these buttons too.

[Q] Can the hardware keys be redefined on the Droid 3?

After downloading and playing with a basic vt100 terminal emulator I soon noticed that there is no ctrl key on the hardware keyboard. In order to get a ctrl-c, for example, I have to press and release the volume lowering button to get "ctrl" and then the "c". This is very awkard. Especially with the keyboard fully extended! I later downloaded the hackers keyboard which has a ctrl key but it was not working at the time and I have reported it as a bug. Regardless, I would like the option to use the hwkb to do this. Perhaps this is premature as we don't have root yet, but is there a way to define say alt-shift, or the "ok" key or what ever to be ctrl. Also, while it is nice to have a fifth row of keys with numbers, I would think that these keys should have other functions too. Whatever one likes, i.e. alt 1 for F1 and so forth.
It is possible, there are apps in the Market, or you could hard code it into a ROM, but all of this requires root to my best knowledge, unless we have that I do not believe it is possible, but would be great if root wasn't needed, so if someone knows more hopefully they can let you know, but that's what I know.
search for Button Remapper, it is also on XDA: http://forum.xda-developers.com/showthread.php?t=850464
mscion said:
After downloading and playing with a basic vt100 terminal emulator I soon noticed that there is no ctrl key on the hardware keyboard. In order to get a ctrl-c, for example, I have to press and release the volume lowering button to get "ctrl" and then the "c". This is very awkard. Especially with the keyboard fully extended! I later downloaded the hackers keyboard which has a ctrl key but it was not working at the time and I have reported it as a bug. Regardless, I would like the option to use the hwkb to do this. Perhaps this is premature as we don't have root yet, but is there a way to define say alt-shift, or the "ok" key or what ever to be ctrl. Also, while it is nice to have a fifth row of keys with numbers, I would think that these keys should have other functions too. Whatever one likes, i.e. alt 1 for F1 and for forth.
Click to expand...
Click to collapse

Is there a way to wake the device using the volume buttons?

I'm thinking of buying this device when it will become available but I have one think that bothers me. The position of the power button is not well enough and makes it annoying when one needs to wake the device. Since htc was "kind" enough to void the warranty on rooting the device, is there a way to wake the device using the volume keys without rooting?
I also found an app called "no lock" on the play store. Does this work with the one? Thanks in advance.
I'm not even sure what that app does exactly. Removes the lock screen?
It also says it doesn't work on certain phones so hopefully someone who owns the HTC One will test it for you.
there is an app i used to use for my sensation but drained battery widget locker i think
Use the smart screen off LITE free from play store it's work perfectly with flip cover, it's use proximity sensor, when you close flap it's off the screen and on when open but can't lock screen, I use screen off and lock app to secure lock the phone with just one click or confiigure using any gesture if you use apex launcher which much battery friendly and lots of customization option if you don't like blink feed
Sent from my HTC One using xda app-developers app
Απ: Is there a way to wake the device using the volume buttons?
onlinejobwork said:
Use the smart screen off LITE free from play store it's work perfectly with flip cover, it's use proximity sensor, when you close flap it's off the screen and on when open but can't lock screen, I use screen off and lock app to secure lock the phone with just one click or confiigure using any gesture if you use apex launcher which much battery friendly and lots of customization option if you don't like blink feed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'll take my chances and not use a cover or case of any kind. Hopefully someone will try the app I mentioned.
I know OP is asking about a no-root, app solution for this, but is there anyway at all of mapping the volume keys to power on device, even if it requires root and/or flashing files?
Cm usually has it in settings
Sent from my Galaxy Nexus using xda premium
Απ: Is there a way to wake the device using the volume buttons?
moeahmad1995 said:
Cm usually has it in settings
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Cm is goodbye warranty. I intend to do that after at least a year.
bouss said:
Cm is goodbye warranty. I intend to do that after at least a year.
Click to expand...
Click to collapse
Oops, I forgot to quote the guy above me, he was wondering if it was even possible, even with root
Sent from my Galaxy Nexus using xda premium
Anyone got any other suggestions that dont involve root ???
App from market called Tap Tap.
Sent from my HTC Sensation 4G using Tapatalk 2
Wake on volume keys research
gustav30 said:
App from market called Tap Tap.
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
Tried many of those apps using the proximity sensor to turn on the screen. I reall hate them because :
1- None of them would have a very high accuracy. Mostly due to the sensors on most of the phones beeing not very accurate to detect multiple wave in a short time frame. It's not their initial purpose anyway.
2- The sensor is at the far top left of the screen which does not help in any way to use turn on the screen with one hand.
3- The fact that you have to swipe 2 or 3 times in front of the sensors which are not very accurate makes it equal in time if not longer than using your 2nd hand to reach the power button.
I believe these apps are not that useful and would prefer something to wake the screen with volume keys or tactile keys at the button.
For the moment I use an app called Flip Flap which is working pretty well. You jsut have to do a quick shake like if you suddenly had to take a look at your wrist watch while holding your phone. It's a half second movement and it unlocks/locks your screen with a movement that you will not trigger by accident so it's kinda nice and quick.
But still, it's not as good as volume keys which are perfectly placed to turn on the thing.
So my phone is rooted now and I've looked into a few things.
I've read that the file handling the keymapping would be in there : /System/Usr/Keylayout and the file to be modified would be l0-keypad.kl
Unfortunately the file is simply not existing on my phone. (Maybe it's got something to do with the fact I do not use the original Android keyboard but Swiftkey instead ? Dunno.
So here is the full list of file I've got in this /System/Usr/Keylayout :
Sorry guys you'll have to enter the h before my links to see them as I don't have 10 posts and can't use external links yet
ttp://i.imgur.com/wkPts92s.png and ttp://i.imgur.com/Ab5sI3Rs.png
Unfortunately I can't find eaxctly which one is used by the phone to map the volume keys exactly.I tried to modify the Generic.kl file :
ttp://pastebin.com/0JdTHwsy
Lines 136 and 137 seems to be mapping the volume keys :
key 113 VOLUME_MUTE
key 114 VOLUME_DOWN
I have tried to add "WAKE" in the same way it is written for the POWER key : key 116 POWER WAKE
Saved the file, restarted the phone but then the file was reset to its intial value so I don't think we can modify this one.
Then I checked another folder : /sys/keyboard/
This one contains a file named vol_wakeup. Was pretty happy to find that one.
It only contains a single character : "0"
The most obvious thing was to try and replace that 0 by a 1 to enable the option but same thing as last time. After saving and restarting the phone this file was restored to its inital value with the 0 in it.
At this point I simply don't have the knowledge to go further. Blocking points :
- I don't know if physical keys like volume are mapped in a generic keyboard file or in a file specific to the virtual keyboard the user has chosen (Android default keyboard or Swiftkey or any other...). This would mean editing different files after identifying them.
- I don't know why the files I've tried to modify went back to their initial states. My phone is rooted, I used ES Explorer to get to the root folder and ES Notepad to edit them and save. I had no error message on saving so I don't think it's got anything to do with access rights.
Could use anyone's help
I was unable to find the app called flip flap. Are you sure that's it's name?
bouss said:
I was unable to find the app called flip flap. Are you sure that's it's name?
Click to expand...
Click to collapse
Nop sorry it's called Justflip :
https://play.google.com/store/apps/...MsIm5ldC5qdXN0bmljZS5hbmRyb2lkLkp1c3RGbGlwIl0.
And the review I posted about it :
"Works great on the new HTC ONE. The Roll is not very precise but the pitch trigger is very accurate. It is also easier on this phone to flip its top/bottom than rolling sideways so no trouble there. Settings for me are the following and I find it great that way : Roll tolerance 15% Pitch Tolerance 48% 500ms Would be the perfect app if it was allowign us to use volume keys (instead of the power key) to turn ON the phone screen."
iKoyy said:
Tried many of those apps using the proximity sensor to turn on the screen. I reall hate them because :
1- None of them would have a very high accuracy. Mostly due to the sensors on most of the phones beeing not very accurate to detect multiple wave in a short time frame. It's not their initial purpose anyway.
2- The sensor is at the far top left of the screen which does not help in any way to use turn on the screen with one hand.
3- The fact that you have to swipe 2 or 3 times in front of the sensors which are not very accurate makes it equal in time if not longer than using your 2nd hand to reach the power button.
I believe these apps are not that useful and would prefer something to wake the screen with volume keys or tactile keys at the button.
For the moment I use an app called Flip Flap which is working pretty well. You jsut have to do a quick shake like if you suddenly had to take a look at your wrist watch while holding your phone. It's a half second movement and it unlocks/locks your screen with a movement that you will not trigger by accident so it's kinda nice and quick.
But still, it's not as good as volume keys which are perfectly placed to turn on the thing.
So my phone is rooted now and I've looked into a few things.
I've read that the file handling the keymapping would be in there : /System/Usr/Keylayout and the file to be modified would be l0-keypad.kl
Unfortunately the file is simply not existing on my phone. (Maybe it's got something to do with the fact I do not use the original Android keyboard but Swiftkey instead ? Dunno.
So here is the full list of file I've got in this /System/Usr/Keylayout :
Sorry guys you'll have to enter the h before my links to see them as I don't have 10 posts and can't use external links yet
ttp://i.imgur.com/wkPts92s.png and ttp://i.imgur.com/Ab5sI3Rs.png
Unfortunately I can't find eaxctly which one is used by the phone to map the volume keys exactly.I tried to modify the Generic.kl file :
ttp://pastebin.com/0JdTHwsy
Lines 136 and 137 seems to be mapping the volume keys :
key 113 VOLUME_MUTE
key 114 VOLUME_DOWN
I have tried to add "WAKE" in the same way it is written for the POWER key : key 116 POWER WAKE
Saved the file, restarted the phone but then the file was reset to its intial value so I don't think we can modify this one.
Then I checked another folder : /sys/keyboard/
This one contains a file named vol_wakeup. Was pretty happy to find that one.
It only contains a single character : "0"
The most obvious thing was to try and replace that 0 by a 1 to enable the option but same thing as last time. After saving and restarting the phone this file was restored to its inital value with the 0 in it.
At this point I simply don't have the knowledge to go further. Blocking points :
- I don't know if physical keys like volume are mapped in a generic keyboard file or in a file specific to the virtual keyboard the user has chosen (Android default keyboard or Swiftkey or any other...). This would mean editing different files after identifying them.
- I don't know why the files I've tried to modify went back to their initial states. My phone is rooted, I used ES Explorer to get to the root folder and ES Notepad to edit them and save. I had no error message on saving so I don't think it's got anything to do with access rights.
Could use anyone's help
Click to expand...
Click to collapse
What you are doing is perfectly valid, but system is protected with the stock kernel and all changes to the /system partition are reverted on boot.
Yeah thanks for the update. I've learned a lot this week while looking a way to enable wake on vol.
Most of the ROMs developped for the One so far have it working, although it does not work when the phone goes to deep sleep. The HTC One source code was released by HTC yesterday so it's only a matter of time until we see many unprotected kernels popout.
The OrDroid ROM is the one with which I had the most successful experience so far : not a single problem, very close to stock ROM and wake on vol is working 9 times out of 10.
So I'd recommend everyone to check it out : http://forum.xda-developers.com/showthread.php?t=2191358

[Q] Enable Software + Disable Hardware Buttons

So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
not until we have s-off. The emmc checks files against its last known configuration and discards any changes. Its been that way since the evo3d. its the same reason supercid wont stick also.
Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?
rougegoat said:
Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?
Click to expand...
Click to collapse
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.
benmatlock said:
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.
Click to expand...
Click to collapse
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.
rougegoat said:
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.
Click to expand...
Click to collapse
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...
tmuka said:
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...
Click to expand...
Click to collapse
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."
rougegoat said:
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."
Click to expand...
Click to collapse
Yeah, sorry, i realize i didn't answer your question. I hope you find the low level solution you're searching for, and that my tip helps you in the short term.
rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE
luisrod03 said:
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE
Click to expand...
Click to collapse
No dice. The files are editable but have no impact.
Is there now any way to disable the hardware keys? I only want to have software keys (paranoid android 4.4 rc1)
Gesendet von meinem Nokia 3310 LTE

Categories

Resources