Use as your own risk! a wrong keylayout may totally disable the input device. Tested on Shield TV 2017 16GB
If you are using 3rd party remote on Shield TV some key may not work as intent, or you want to remap the key for another function, for example I had a xiaomi remote (just $4 dollar) which the home key not working.
Although you use custom IME (such as mkr Multilanguage Keymap Redefiner) or some keyboard remap app (such as buttons remapper), which work but not perfect, some function may not work such as double press the home button to show recent app list, or conflict with shield tv controller button (buttons remapper disable the voice search button on my shield controller), and you may need to change every time for each different remote/controller.
Luckly android allow you to use specific key layout for each different remote.
1. flash the developer image, which is pre-rooted, or root it yourself
2. adb shell
3. cat /proc/bus/input/devices
Now you will have a list of connected remote/controller, take a note of the Vendor number and the Product number4. adb pull /system/usr/keylayout
5a. modify a exist keylayout file, or create a new one. The file name should be Vendor_XXXX_Product_XXXX.kl, Don't change the Generic.kl
5b. use any keytest app to check the key scancode, I am using "Multilanguage Keymap Redefiner"
for example my xiaomi remote home key scancode is "102", which map to MOVE_HOME by default, so I create a new file "Vendor_2717_Product_3200.kl", the file will be like this:key 28 DPAD_CENTER
key 102 HOME
key 103 DPAD_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN
key 114 VOLUME_DOWN
key 115 VOLUME_UP
key 116 POWER
key 127 MENU
key 158 BACK
Any key not listed will be disable, so make sure you have all key listed
6. copy the file back to shield tv:
adb root
adb disable-verity
adb reboot
adb root
adb remount
adb push "layout file" /system/usr/keylayout7. reboot.
P.S. Don't change the Generic.kl, change the keylayout file one at each time
Shield TV remote Home button is map to HOME, and the dpad center is map to DPAD_CENTER, so other remote which map to MOVE_HOME and ENTER (such as my xiaomi remote) will need this mod
The shield TV come with lot of keylayout file for many different controller/remote, I see MI, wii,xbox 360, but there seems no amazon
I had attach the keylayout file pull from my sheild tv, may be you can take a look which controller/remote is support offically
I cant do adb remount, it says I have to be root, and when I do adb root first it seems to pass but it still says I have to be root when i try adb remount.
How do I set my /system to r/w instead of r/o? I have tried adb mount o rw,remount /system but it wont do anything.. also the command you tell me to use, "adb disable-verity" says:
disable-verity only works for userdebug builds
Can you please help me?
Kylistar said:
I cant do adb remount, it says I have to be root, and when I do adb root first it seems to pass but it still says I have to be root when i try adb remount.
How do I set my /system to r/w instead of r/o? I have tried adb mount o rw,remount /system but it wont do anything.. also the command you tell me to use, "adb disable-verity" says:
disable-verity only works for userdebug builds
Can you please help me?
Click to expand...
Click to collapse
you need to root it yourself or using the developer firmware in here:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD
note that future OTA may fail because it will send you normal firmware even you are on developer firmware
DummyPLUG said:
you need to root it yourself or using the developer firmware in here:
note that future OTA may fail because it will send you normal firmware even you are on developer firmware
Click to expand...
Click to collapse
I did root my nvidia shield. It is supposed to be rooted, I got super user(superSU) installed on it and Everything..
Kylistar said:
I did root my nvidia shield. It is supposed to be rooted, I got super user(superSU) installed on it and Everything..
Click to expand...
Click to collapse
you mean mount -o remount,rw /system didn't work? but I suppose it can't as verity will prevent it, I hear SU in 7.0 will disable verity but I didn't try it before, sorry about this.
DummyPLUG said:
you mean mount -o remount,rw /system didn't work? but I suppose it can't as verity will prevent it, I hear SU in 7.0 will disable verity but I didn't try it before, sorry about this.
Click to expand...
Click to collapse
I actually got the kl file into the system/usr/keylayout directory now, using TWRP
with these steps:
Reboot to Bootloader
Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.
Fastboot with TWRP
Type “fastboot devices” and make sure your Shield TV is visible.
If your Shield TV is listed, type “fastboot boot twrprecovery.img”
in the TWRP i can chose mount and check system, then i was able to move the .kl file from the sdcard to the keylayout directory, still my nvidia shield doesnt give it the new settings.. its given the same configuration as my nvidia controllers. I have double checked that Vendor nr and Product nr is the same as the controllers.
here's my .kl file:
# ps4
key 304 BUTTON_X
key 305 BUTTON_A
key 306 BUTTON_B
key 307 BUTTON_Y
key 308 BUTTON_L1
key 309 BUTTON_R1
key 310 BUTTON_L2
key 311 BUTTON_R2
key 312 BACK
key 313 HOME
key 314 BUTTON_THUMBL
key 315 BUTTON_THUMBR
key 316 BUTTON_START
looks correct?
Thanks for your time!
Kylistar said:
I actually got the kl file into the system/usr/keylayout directory now, using TWRP
with these steps:
Reboot to Bootloader
Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.
Fastboot with TWRP
Type “fastboot devices” and make sure your Shield TV is visible.
If your Shield TV is listed, type “fastboot boot twrprecovery.img”
in the TWRP i can chose mount and check system, then i was able to move the .kl file from the sdcard to the keylayout directory, still my nvidia shield doesnt give it the new settings.. its given the same configuration as my nvidia controllers. I have double checked that Vendor nr and Product nr is the same as the controllers.
here's my .kl file:
# ps4
key 304 BUTTON_X
key 305 BUTTON_A
key 306 BUTTON_B
key 307 BUTTON_Y
key 308 BUTTON_L1
key 309 BUTTON_R1
key 310 BUTTON_L2
key 311 BUTTON_R2
key 312 BACK
key 313 HOME
key 314 BUTTON_THUMBL
key 315 BUTTON_THUMBR
key 316 BUTTON_START
looks correct?
Thanks for your time!
Click to expand...
Click to collapse
Yes TWRP can write into system, but last time when I try it trigger the verity protection sometime, don't investigate it though as I am lazy and just use the developer build since then. (another reason I semi brick my shield a few time with twrp)
the.kl looks correct, to see what is the problem try remove one of those key from the .kl, if shield load the file correctly that key should be disable, if not then the .kl file is not work.
I can't remember if the file need to be in unix EOL style or not, that means if you edit it in windows notepad it may not work, try notepad++ or pspad. (I may mix up with bt_config.conf, which I use to maually pair my xiaomi remote)
DummyPLUG said:
Yes TWRP can write into system, but last time when I try it trigger the verity protection sometime, don't investigate it though as I am lazy and just use the developer build since then. (another reason I semi brick my shield a few time with twrp)
the.kl looks correct, to see what is the problem try remove one of those key from the .kl, if shield load the file correctly that key should be disable, if not then the .kl file is not work.
I can't remember if the file need to be in unix EOL style or not, that means if you edit it in windows notepad it may not work, try notepad++ or pspad. (I may mix up with bt_config.conf, which I use to maually pair my xiaomi remote)
Click to expand...
Click to collapse
It looks like my shield wont recognize the files im putting in there, I tried replacing the Generic file with a modified one, after that the ps4 controller wont work at all, Before it just had the wrong buttons, then i tried changing back to the original file and the shield wont read it.
This should mean the reason my new .kl file for the ps4 controller wasnt recognized because of this.
Any idea what I do now? How do I get it to recognize the files? How do I get at least the generic back if that is not possible?
And yes, I do use pspad.
Kylistar said:
It looks like my shield wont recognize the files im putting in there, I tried replacing the Generic file with a modified one, after that the ps4 controller wont work at all, Before it just had the wrong buttons, then i tried changing back to the original file and the shield wont read it.
This should mean the reason my new .kl file for the ps4 controller wasnt recognized because of this.
Any idea what I do now? How do I get it to recognize the files? How do I get at least the generic back if that is not possible?
And yes, I do use pspad.
Click to expand...
Click to collapse
If you replace the generic file and it didn't work this mean the file is something wrong, the first thing I come in my mind is the file still using windows (CRLF) not Unix (LF), but as you said even you copy the original .kl back to shield it still didn't work then may be the dm-verity kick in
if it is dm-verity kick in the best and easiest way to recovey is flash the firmware again, as it is hard to modify the current system block to have the same hash as original one
I am having the same issue as above. My Shield doesn't recognize the changes made to the .kl file I edited.
I have a rooted Shield running on the latest Shield software 7.0.2 and a Fire TV Stick Remote connected.
I used cat /proc/bus/input/devices to see the remote uses vendor 1949 product 0404 key layout.
I went to system/usr/keylayouts, navigated to that kl file and then modified the 2 keys I wanted to change. Rewind and fast forward. I changed them to VOL_DOWN and VOL_UP.
I saved the changes and rebooted.
However they still act as MEDIA_REWIND and MEDIA_FAST_FORWARD.
I have verified the changes are still showing in the key layout file. I don't understand why it's not working.
The last time I rooted my Shield, I was using another Fire TV remote (the Alexa Voice Remote), which uses 1949 0407.kl file.
I modified that one to make the same changes and it worked. I could control the volume.
Since then though, I've factory reset the Shield am rooted onced again and this time I am using this fire tv stick remote, but can't seem to get the changes to the key layout file to actually take affect and I don't understand why it's not working. What is different than when I modified the other remote? Makes no sense.
EDIT: Ok so I figured it out basically right after making this post. I was trying to use VOL_UP and VOL_DOWN, which I could have sworn was the correct key code and what I used with my other Fire TV remote before I factory reset. However I tried again, this time though using VOLUME_UP and VOLUME_DOWN and it worked properly.
Damn, I'm dumb. Now it's working exactly how I wanted it to.
I am guessing by using the wrong key code, thus rendering it useless, it was falling back to the key code used for the same key ID in the generic.kl file?
thanks, i will try
How do we know the vendor number for external remote? I tried on android box and there is no system under /proc
how do i set the proper chmod when running the push command to put the file onto the device?
Thanks for this, but I am trying to use Mi remote with voice control
Everything works except the Google assistant button, it brings up assistant but doesn't detect any voice from remote.
Can something similar be done with an IR remote?
I'd love to have more buttons that I could use for all kinds of automations.
Thanks!
How to open app using this method? Suppose I want to open google chrome, how would I do that? @DummyPLUG
Related
Hello everyone. I'm not very experienced with Linux but have done some. I want to connect to my Tomato router using GScript and RSA keys. I generated keys with ConnectBot and I can connect to it from there fine, however when I try to connect from GScript using ssh -p port [email protected] 'command', I get an error about the host not being in the trusted hosts file. Is this because the RSA keys are not system-wide and GScript is not using what was created by ConnectBot, or is this a different unrelated problem? Any help would be great, thanks!
I really don't know where to start with this. I seriously recommend you read Wikipedia and experiment more with virtualized Linux computers (VMware Player or Oracle VirtualBox are good starts, running CentOS and Ubuntu).
RSA keys, as you're talking about at first, is the public key encryption scheme used to authenticate you to connect to your router, in this case. BUT. The keys you talk about in the second part? Those aren't keys. Your "trusted hosts file" is a list of unique fingerprints that an SSH server creates when it's first initialized, and are used to "sign" that it's the server you're connecting to.
For example, if every day you connect to the same server, and then suddenly one day, you get told that the fingerprints don't match, and you know that nothing has changed on the server end, it's a good chance that something got messed up, or that someone is attempting to perform some kind of a man-in-the-middle attack.
To get back to your question though, no, the Trusted Hosts file is not shared between ConnectBot and GScript. Odds are, ConnectBot isn't even sharing your SSH key (the RSA key) with GScript, and you haven't even gotten to that error yet. The SSH key can be system wide though (PROTIP: Just put it on the root of your SD card and load it into ConnectBot/GScript by manually adding the key file).
Thanks for your help. So basically I just want these two programs to share trusted hosts files and RSA keys. How does GScript initially come to trust a host, and how come ConnectBot didn't have this issue? I guess I could try to find the trusted hosts file ConnectBot is using, and can I move its key file to the root and then share it with GScript? Or do I need to make a new one (possibly in Cygwin on the desktop) and copy it over to the SD card.
I do plan to read more about this stuff, but that will happen in time. Right now I feel very close to accomplishing what I want (as you can probably tell by me posting this at 4:45 AM ).
Thanks again.
For the trusted hosts issue, you can't really share them, as there's no standardized format to the file (it's like trying to swap an MP3 and an AAC file; they both may be music, and they both may be of the same song, but they're quite different). There should be an option on the GScript error message to just add the host to the trusted list. If not, try running the same command from a terminal (ADB shell, or open ConnectBot and connect to local).
In regards to the key file, you'll just have to hunt down wherever ConnectBot placed it, and move it to the root of the SD card, then re-add it in ConnectBot (Press Menu and then Manage SSH keys to get to the key list. Menu again to select add/import).
Thanks. I'm having no luck finding ConnectBot's key file, so I just made a new one in Cygwin and will put it in my SD card. However I'm still not sure how to add/import that into GScript, or how to get GScript to trust that host (I don't see an option for it with the error message). These are questions I need to direct towards the GScript crowd, unfortunately its thread hasn't received much activity in awhile. Is there any other way you would go about saving a script to run from your home screen?
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.
Someone please explain how to properly decompile the kcm.bin so that it can be edited and recompiled. There are quite a few of us who would like to remap certain hardware buttons (mainly custom user keys) but just using the files from (this thread) leaves us with some broken keys, the "?" key mainly... but some would also like to tweak this layout and don't have a proper tutorial. I will gladly donate a minimum of $10USD to the first person who properly explains the process for both *nix and windows environments.
This is another approach.
(If you have already read this and it is not the way you want it, I am sorry)
According to http://forum.xda-developers.com/showthread.php?t=1285244&page=3
In short:
# Remount
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# fetch Keylayout
adb pull /system/usr/keychars/vision-keypad-wwe.kcm.bin /tmp/vision-keypad-wwe.kcm.bin
# edit Keylayout according to Thread above with a hex editor
For example A 2 a A ! ! that represents:
A: Scancode
2: Does not matter
a: Letter when button connected to the keycode is pushed
A: SHIFT + button connected to the keycode is pushed
!: ALT + button connected to the keycode is pushed
!: SHIFT + ALT + button connected to the keycode is pushed
(for me ALT = FN)
# push it back
adb push /tmp/vision-keypad-wwe.kcm.bin /system/usr/keychars/vision-keypad-wwe.kcm.bin
The first line in every row is the constant value of the keycode.
For example: http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_A
For Button A it is: 29 in decimal, 1D in hex.
With this approach you can change every key, but only the printable characters.
Search button will not work, as it is implemented in another way...
ok, not sure if I missed something, but specifically I need to modify the ? key and the 3 user assignable keys on the g2/dz keyboard... I don't see in the hex editor any line that starts with the ? symbol then has a number and two more chars/symbols after the number (ie: A 2 a A ! ! )
when I load keynumber tracker app the ? key reports "214" the user assignable keys report 183, 184 and 185... I'm just not sure what to do with those numbers, or how they help me modify anything...
I guess I just don't understand what I'm doing...
Ok, so I noticed in hex editor that the only difference between the modded kcm.bin and the stock one where my ? key works (besides the remapped keys) was the last 64 blocks of hex so I copy /pasted that part to the modded kcm.bin then saved and pushed... Now it's working, thanks so much, will PM you momentarily to get your paypal addy. Sooooo happy!!!
Edited w/ a cold press a CNC and a water jet @ 30,000PSI.
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
abacus0101 said:
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
Click to expand...
Click to collapse
Need to go into Settings (from Original AFTV launcher) and System, then Developers Option and turn on Install from Unknown Sources.
If you have an earlier version of AFTV, then you need to do the SQLite method, do a search for it.
abacus0101 said:
So in another thread it gives you the apk files needed to get the ouya launcher. I've gotten into the ouya store, but any game I try to download and install, complains that I need to enable "Unknown sources". My box is rooted which I thought automatically emulates "Unknown sources". I've seen the guy in the video run Bombsquad, and he mentions to "Enable Unknown sources". Anyone has this working, what needs to be done to get games to install and play on Ouya.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53451988 ORIGINAL THREAD
I had this same problem today...I coudlen't get the ADB commands to work...But I found out it's done via SQLITE editing ...so I did another solution
*buy* (or find) SQLIte Editor...(or an app that can edit SQL database files) and sideload it.
Download LanMote Lite from the play store(you need mouse support) and Sideload it. Once done RUN LanMote Lite and start the server (Free version is limited to 30 minutes so act quickly) On your HTML 5 device (preferrably a smartphone or tablet) [PC works but mouse is slow and wonky] connect to the same wifi as the FTV (if you didnt do it already) and open your web browser and put in the address LANMOTE will show on the FTV (example http://xx.xx.xx:9999) also enable different cursor.
Go to FTV home and go to settings>>APPLICATIONS >> your SQLITE editing program.
(in SQLITE Editor) Allow SU permisions and use your amazon remote (it works for simple navigation for now) to go to FILES TAB and go to
DATA>>>DATA>>>com.android.providers.settings >>SETTINGS.DB
go to the GLOBAL folder. You should see a list with different settings (BE CAREFUL)
(now this is where you need a mouse)
on your HTML 5 device (smartphone) go the MOUSE Tab and use the mouse pad to mouse near the entry that says INSTALL_NON_MARKET_APPS you will notice that default for this option is 0 (which means off/ disabled) Mouse over the 0 and tap the "click" button on your HTML device. you will notice the entire row becomes gray.
Use your Amazon Remote and click EDIT RECORD. cursor down to the 0 and change it to a 1
use your remote and scroll below it should give a CANCEL and SAVE button. Click save with the remote.
go back to home and enjoy sideloading unknown sources.
stanleyopar2000 said:
http://forum.xda-developers.com/showthread.php?p=53451988 ORIGINAL THREAD
I had this same problem today...I coudlen't get the ADB commands to work...But I found out it's done via SQLITE editing ...so I did another solution
*buy* (or find) SQLIte Editor...(or an app that can edit SQL database files) and sideload it.
Download LanMote Lite from the play store(you need mouse support) and Sideload it. Once done RUN LanMote Lite and start the server (Free version is limited to 30 minutes so act quickly) On your HTML 5 device (preferrably a smartphone or tablet) [PC works but mouse is slow and wonky] connect to the same wifi as the FTV (if you didnt do it already) and open your web browser and put in the address LANMOTE will show on the FTV (example http://xx.xx.xx:9999) also enable different cursor.
Go to FTV home and go to settings>>APPLICATIONS >> your SQLITE editing program.
(in SQLITE Editor) Allow SU permisions and use your amazon remote (it works for simple navigation for now) to go to FILES TAB and go to
DATA>>>DATA>>>com.android.providers.settings >>SETTINGS.DB
go to the GLOBAL folder. You should see a list with different settings (BE CAREFUL)
(now this is where you need a mouse)
on your HTML 5 device (smartphone) go the MOUSE Tab and use the mouse pad to mouse near the entry that says INSTALL_NON_MARKET_APPS you will notice that default for this option is 0 (which means off/ disabled) Mouse over the 0 and tap the "click" button on your HTML device. you will notice the entire row becomes gray.
Use your Amazon Remote and click EDIT RECORD. cursor down to the 0 and change it to a 1
use your remote and scroll below it should give a CANCEL and SAVE button. Click save with the remote.
go back to home and enjoy sideloading unknown sources.
Click to expand...
Click to collapse
I'll try your method...phew, got tired just listening to all that has to be done...thanks
it seems that while adding non-remappable assistant buttons is a growing trend, solutions aren't easy to find, however the solution is real simple, you just have to modify the keymap file...
I successfully managed to get the button detected by flashing XperiaGAButtonRemap through magisk, and I'm pretty sure the same solution works for a bunch of other phones also, it even has code that should allow flashing through custom recoveries also.
all you have to do is "install from storage" in magisk manager, select the zip, and reboot.
what that zip does, is it adds /system/vendor/usr/keylayout/gpio-keys.kl (overriding /system/usr/keylayout/gpio-keys.kl because /vendor has higher priority) and replaces the ASSISTANT key with PROG_BLUE, which is a dummy key, you can remap that with any remapper app or module, or you could edit the zip, and change it directly to something like CAMERA, if that's all you want.
here's what the file will look afterwards, if you're curious:
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 102 HOME
key 528 FOCUS
key 766 CAMERA
key 457 PROG_BLUE
the original file has copyright notice for The Linux Foundation, from 2013, but all other keys map the same, so it's highly likely most phones (at least the AOSP-adjacent ones) just have hooks for the ASSISTANT key, but still rely on the universal keymap file
thanks a lot!worked just fine,
big ups!!!
Hello, sorry for the question, does this work on Android 12?
SHANOA_zasha said:
Hello, sorry for the question, does this work on Android 12?
Click to expand...
Click to collapse
I've just tested and yes it works in A12