If you are like me you are not happy with the power button placement. I modded a few files that will allow any bluetooth keyboard to wake the screen from sleep. Very handy when the Xoom is docked. Requires Reboot.
Modded Files
Push the files via adb to /system/usr/keylayout/
Example:
adb remount
adb push Generic.kl /system/usr/keylayout/Generic.kl
adb reboot
Apple Keyboard (Vendor_05ac_Product_0239.kl) - Wake with eject key
Generic Keyboard (Generic.kl) - Wake with F1
Motorola Keyboard (Vendor_22b8_Product_093d.kl) - Wake with right ctrl key (Not Tested - Sorry do not have one)
Note:
After the keyboard and the Xoom have been asleep for a while, there may be a delay before the Xoom wakes. Bluetooth devices sleep to save power and it takes about 15-30 seconds to wake and sync again.
Thorough Explanation of Key Remapping:
Better explanation of this is here.
Getting back to default:
If you want to return things to default, download the default files and adb push them back to the Xoom.
Sweet! I'm going to give this a try later. Thanks!
Works great with the Motorola BT Keyboard...
edit: I did remap it back to the default CTRL_RIGHT and instead used the unmapped "reserved" key on the keyboard. It is the 4th key from the top right with 3 lines. Since this key is unused, it seemed more appropriate for now. It is key 226 in the mapping.
@triadX1
Sent from my Xoom using XDA App
Maybe someone in this thread can help me. I posted in other threads but nobody replied. I bought a generic BT keyboard with Apple keys. To remap the keys I downloaded a program to get the scancodes for each key and modified the Generic.kl. It di not change anything. The question is now, is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected? I hope I got my point across...Thanks everyone!
[sent with Xooming Android technology]
Just a heads-up: I have what must be an older version of the Apple Keyboard (bought in '97); the VID:DID are 05AC:022C :
Code:
apple 0005:05AC:022C.0001: input,hidraw0: BLUETOOTH HID v1.36 Keyboard [Apple Wireless Keyboard] on 40:FC:89:27:62:5C
I just copied your Vendor_05ac_Product_0239.kl to Vendor_05ac_Product_022c.kl and it works fine. Thanks for the mod!
funnycreature said:
is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected?
Click to expand...
Click to collapse
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
it was easy i just edited one file one line next to menu i put wake
Sent from my Xoom using XDA App
system/ust/keylayout/ and vrdb ....093 something then r/w then right click to edit text and scroll to 125 where it says MENU and make it look like this MENU WAKE and reboot and your good menu key is now wake one press wakes and two presses unlocks
Sent from my Xoom using XDA App
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I found out that the generic keyboard uses the Apple layout. I want to post a How-to soon but I have very little time lately Thanks for the info though; how would I find the information? I tried connecting the keyboard to my laptop via BT and opened the device manager. Is there any property that shows the VID:DID?
I'm curious as to why the key 226 isn't being used when there's actually no key used to open the app menu. I would have assumed the key used for menu (two keys to the right of the spacebar) would be used for the app menu and the unused key (three horizontal lines) would've been for the menu since most apps I've seen with the on-screen menu looks the same. Plus the icon for the Apps menu actually looks like what is on the Menu key for the keyboard.
What would I need to add to the keyboard file to make a key open the application menu? After looking over the keymaps in the file I couldn't see any key on the keyboard that would open the app menu.
Use 226 for whatever
You can remap 226 to be menu if you want, but i don't know the command to open the app "drawer" on honeycomb.
Just like they said above, the file you want to edit is in
/system/usr/keylayout/
I use root explorer because it lets me edit easily as well. If you want to do it the way i do just follow the steps below:
1- Mount R/W when you get in the folder
2- Long hold on "Vendor_22b8_Product_093d.kl"
3- Select "Open in Text Editor"
4- Scroll all the way to the bottom where it says 226 and edit the line to read
key 226 MENU (3 spaces between 226 and MENU)
if you simply want it to be another Menu key. (Before editing, it says unused or tbd or something, just erase all of that )
Alternatively try:
key 226 MENU WAKEif you also want it to wake up your tablet.
Personally, I edited key 125 to wake up the tablet as described above, and put
key 226 POWERso that i could also lock the screen, thus using the otherwise useless key.
As a sidenote, Root Explorer *should* automatically make a backup for you when you edit the keylayout file, but doing one manually (aka: copy and paste somewhere else on your sdcard) is always a smart move.
Good Luck!
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I tried this command and I get a "error: device not found" message. I am using my droid 1 and the blueputdroid app to use my hard keyboard as a bluetooth one. The keyboard works... I just would like to map some things out to open the app drawer and such. Thank you in advance for any help
Sent from my Droid using Tapatalk
That error means adb can't find your xoom. Make sure you have USB debugging enabled
sangreal06 said:
That error means adb can't find your xoom. Make sure you have USB debugging enabled
Click to expand...
Click to collapse
Hmm I have tried it from the zoom itself with a terminal app as well as from the PC and have made sure debugging is running and have gotten the same result each time :/
Sent from my Xoom using Tapatalk
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
B Dizzle said:
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Hmm it STILL doesn't see it. I know I am an unlocked and rooted xoom. I am running rooted apps just fine and browsing all my system files just fine on the computer with Droid explorer. I just can't get it to see my device in adb. Any ideas?
Sent from my Xoom using Tapatalk
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
SPIDERTECH said:
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
Click to expand...
Click to collapse
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
SPIDERTECH said:
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
Click to expand...
Click to collapse
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
ruvort said:
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks for that. It looks like the 226 key is STILL not being used. I'm curious now as to what the additional shortcuts were supposed to be.
I saw this and wanted to know if it works on our phone. Or is there an easier way to do it? "I've been browsing the forums for some helpfull stuff and I found this little mod that allows you to turn Media Scanning off." The original topic by aditya_t90 can be found here
Requirements:
- USB Debugging: ON
- Root Access
Enter one of the following commands in terminal emulator, adb shell or in a script file
To enable media scanning on boot:
su
pm enable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
To disable media scanning on boot:
su
pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
Screenshot:
Sent from my SPH-D710 using xda premium
try it and let us know
What's the verdict on it? I HATE that constant media scanner crap.
Works like a charm
Now If I knew how to remove the cache files generated by this scanner...
Just add a folder to the root of your SD card called ".no media"
Sent from the near past
I've been trying to install Game killer (the equivalent of CheatEngine on PC) except I ran into a very unusual problem. I've been using "Application installer". I would provide a link to the app, but I seems that the site won't let me.
The problem is that when I try to install the Game killer .apk through this installer app, I get to the usual permissions interface where I see what permissions the apk needs and all that. What's strange is that I cannot seem to click the Install button. I can interact with every other part of the screen, but I simply cannot hit the install button. Even pressing my finger onto the install button and then sliding towards the "Back" button will cause the back button to illuminate like it usually does, but I still cannot select the install button.
I'm running stock ROM, stock Kernels, stock everything. Device is rooted. I can install apps from google play just fine, but of course, Gamekiller is not on the play store.
I ran into a similar problem when I installed a screen rotation app. With the rotation app intstalled I could not install any other apps that were not from the app store. Once I removed the rotation app everything was fine. This a security feature in android to prevent apps from modifying your screen without you knowing it. Check if you have installed any app that could have modified your screen.
I had the same issue on mine, the app total screen control was the culprit. I couldn't get apps to install when TSC was active.
Are you using any type of screen filters? If you are, disable them and it should be able to work now.
Hi
given alot of methods on XDA and others i was stuck on enabling some type of data toggle switch widget or any thing but none worked. Every one opened the settings app for enabling data.
Finally i figured the folowing method
1. Root your device using CF-Auto-Root-zenltetmo-zenltetmo-smg928t.zip from Cf-Auto Root Website use Google
but first sheck Enable OEM Unlocking in Developer options. Flash the above Cf-Autoroot Package Using Odin From Download Mode.
Turn Off Your Device and Press Volume Down + Power + Home Button. Confirm By Volume Up its Download Mode
2. Install View attachment Power_Toggles_6.0.4.apk
3. Add Widget to home screen.
4. Enjoy Data Toggle Switch on Marshmallow
Checked on Android Version 6.0.1.
I want it to be completely disabled, I managed to make it go away with Tasker but it comes back when I swipe up or use the keyboard.
With the XDA gesture control app it does goes away completely, but the app is really buggy, so I guess it can be done someway.
I also tried with a magisk module but it didn't do anything, any ideas?
adb shell wm overscan 0,0,0,-150
hides the navigation bar using the same method the XDA app uses.
adb shell wm overscan reset
Goes back to normal
Enviado desde mi XT1635-02 mediante Tapatalk
moxtrom said:
adb shell wm overscan 0,0,0,-150
hides the navigation bar using the same method the XDA app uses.
adb shell wm overscan reset
Goes back to normal
Click to expand...
Click to collapse
I'm getting this error: /sbin/sh: wm: not found when trying to run that code. Any ideas on what i might be doing wrong?
I'm getting this error /sbin/sh: wm: not found , any idea why?
Ivanrl said:
I want it to be completely disabled, I managed to make it go away with Tasker but it comes back when I swipe up or use the keyboard.
With the XDA gesture control app it does goes away completely, but the app is really buggy, so I guess it can be done someway.
I also tried with a magisk module but it didn't do anything, any ideas?
Click to expand...
Click to collapse
You better use the latest beta of navigation gestures from XDA, just join the telegram link.
Ivanrl said:
I'm getting this error: /sbin/sh: wm: not found when trying to run that code. Any ideas on what i might be doing wrong?
Click to expand...
Click to collapse
are you trying to run this from recovery?
if so, try running it while the system is booted. From what i noticed, a lot of adb commands don't work in twrp.