I'm looking into making changes to the .kl file for the diNovo Mini so I can wake my device with a keypress (I'm lazy =P) but there are several .kl files listed (more so than on my TB) and while there are individual files for the Logitech Revue keyboard, Apple Wireless and Motorola Xoom keyboard, there is one that is simply labeled Generic.kl which is listed as "Generic key layout file for full alphabetic US English PC style external keyboards"
I am at work and don't have the diNovo here to test with, so I wondered if anyone else uses the Mini with their Xoom and if they could test to see if they can add the WAKE function to a key and see if it works for them?
I expected another file for the diNovo to have been created when it was connected but maybe it just uses the Generic file, or maybe the one for the Revue keyboard?
If you get this going would love to hear how you do it. Have a mini myself would love to use.
It uses the Generic.kl file. I used a combination of adb logcat and the KeyTest.apk programs to figure out the correct file and key codes to edit in the file to allow the Windows button to wake and unlock the xoom as well as serve as the menu button. Mapped the Home and Back functions as well.
Once I get home I can update with which keys are what and what changes specifically I made to get it to work. When I get home and grab the dinovo mini, it takes just a couple clicks on the pad to get the xoom to recognize it is connected and to start typing.
Switching applications and generally moving about on the home screen is clumsy and somewhat random, but eventually you get there. I can sometimes get the app drawer to open by using the arrow keys in conjunction with ok/enter but there is no highlighting on the icon to indicate it is selected so sometimes you'll open another app or widget instead. Meh, I can typically get into googe voice to text easily and that's all I'm concerned with =)
Any update on this? I've got a diNovo coming and with the mouse support in 3.1 this would be excellent!
Hi,
has anyone achieved changing the keyboard layout of hardware keyboards without root?
I have a german(QWERTZ) variant of the Logitech K830 and unfortunately lots of keys are mapped incorrectly.
Already tried a couple of apps which claim to fix this problem but unfortunately none of them work.
Apps I have tried so far from Play Store:
RS - Hardware Keyboard Layouts
External Keyboard Helper DEMO
Swiftkey (sideloaded from my mobile) - just crashes while trying to do first run setup
Logitech Keyboard Plus - only supports BT keyboards which do not work at all without root on the FTV.
All of these apps either rely on the default android settings or a software keyboard which both are not available on the FTV.
Any hints?
I know it's a old post but https://exkeymo.herokuapp.com/ should help with external keyboard layout modification.
quick question...
is it possible to assign additional IR keys/commands (beyond that of the standard fire tv remote buttons) in the native fire tv gui, not kodi.
i would like to assign shortcuts on my remote that tell fire tv to open hbo, netfllx, etc...
ziff73 said:
quick question...
is it possible to assign additional IR keys/commands (beyond that of the standard fire tv remote buttons) in the native fire tv gui, not kodi.
i would like to assign shortcuts on my remote that tell fire tv to open hbo, netfllx, etc...
Click to expand...
Click to collapse
You can make it send any keyboard key you want.
rbox said:
You can make it send any keyboard key you want.
Click to expand...
Click to collapse
yeah i know, but how do i tell fire tv to then launch an app after it receives XXX key. is this doable in llama?
I'm using a replacement launcher (Firestarter) and a 3rd party wireless keyboard /mouse (Mele F10 Deluxe) -- things are working well, but one issue is that the "home" button on the Mele acts like the "HOME" key on a QWERTY keyboard. Instead of returning to the home screen, it sends keyboard event "KEYCODE_HOME" (Constant Value: 3 - 0x00000003).
On a (rooted) AFTV2, is there a way to assign a keyboard event (in this case, "KEYCODE_HOME") to launch a particular app (in my case, firestarter) regardless of what else is open?
Alternatively, is it possible to have the keyboard event "KEYCODE_HOME" perform the system "home" event?"
Thanks in advance for your thoughts!
http://www.mobileread.com/forums/showthread.php?t=159538
Thats five minutes on google.
The way I have solved this was to remap the keyboard layout of my Macbook Air to adb commands - whenever I run a script that can only be exited by clicking a button on a prompt. I actually remapped the entire MBA's keyboard to send the corresponding keys to the Fire TV as adb keyevents.
Code:
adb shell monkey -p your.app.package.name -c android.intent.category.LAUNCHER 1
does what you want in that case (de.belu.firestarter is the package name btw).
I dont think every button press will show up in the Fire TVs logs the same way HOME does ("nice little keylogger you sell there, A."), so instead you might have to do the remapping at another point. Your keyboard itself is too dumb to even know what being scripted means - that leaves you either messing with the OS itself - or forfeiting the keyboard in favor of an Ultrabook. Which by the way - allows you to actually work, or browse the net - and still control the Fire TV in the background.
But people seem to be happy with their Bluetooth keyboards - because, single purpose = neato.
On my k900 plus keyboard it has a home button, why not Just map Firestarter to start up when you press home twice, then you just press the home button twice on your keyboard?
Hope this helped press thanks button
harlekinrains said:
http://www.mobileread.com/forums/showthread.php?t=159538
Click to expand...
Click to collapse
Thanks for the links. For anyone else using a media airmouse such as the Mele F10 (with a "home" button that does not send the same code as the amazon remote), it's very straightforward to create a custom keyboard map that makes it function like the Amazon remote:
1) For each button that you would like to remap, use Ketest App to discover its ScanCode (for example "102" is the "Home" button on the Mele F10 Deluxe).
2) Determine the Product ID and Vendor ID for your input device with "cat /proc/bus/input/devices" and create a copy of /system/usr/keylayout/Generic.kl with the name Vendor_XXXX_Product_XXXX.kl. This custom key layout file contains your new mapping (for example, I changed the entry next to "Key 102" to "HOME" instead of "MOVE_HOME").
3) Set ownership (chown system.system) and permissions (chmod 644) for your custom key layout file.
deanr1977 said:
On my k900 plus keyboard it has a home button, why not Just map Firestarter to start up when you press home twice, then you just press the home button twice on your keyboard?
Hope this helped press thanks button
Click to expand...
Click to collapse
Thanks for sharing your experience. The issue is that on the Mele F10 Deluxe (and other combo devices that aren't designed specifically for the Fire TV box), the home button does not send the same key code as the Amazon remote -- requiring that the user create a custom key map file.
harlekinrains said:
http://www.mobileread.com/forums/showthread.php?t=159538
But people seem to be happy with their Bluetooth keyboards - because, single purpose = neato.
Click to expand...
Click to collapse
Thanks! Given the cost difference (plus, portability, and the fact that it lasts longer on a charge), I can understand why people might choose a media remote instead of a script-friendly keyboard with a screen (like an Ultrabook). Fortunately, if your 3rd party remote doesn't work like the Amazon remote out-of-the-box, it is easy to create a custom keymap. Unfortunately, this still means that, by default, FireStarter has to use ADB to listen for the home key. I was hoping that if I use a different button instead of the home key on the amazon remote, I can have the OS "listen" in a simpler way (that doesn't tie up ADB), and simply have the OS launch firestarter when this button is pressed.
Bluetooth keyboards are less clunky - thats right. So portability and also price are valid arguments for them.
But - there is also a lot that you "lose" by not using an ultrabook (beside the remote which at some point becomes just an easy to use muscle memory extension).
The argument here goes as this way -
1. Screen Mirroring is a very, very, stupid idea. Let the battery powered device do all the processing, then let it encode a video feed on top of that, and then let it transfer...
2. Link sharing on the other hand is "where its at". So for the Fire TV this means, you use the Chrome Plugin "Play to Kodi", which covers youtube and a few other sources - and you also use Video Download Helper (Chrome Plugin available as well) to get any direct video link that isnt a rtmp stream and heavily segmented and a little script that launches http://www.multilinkr.com/ in your browser, then you paste the url in your clipbord into that, use the site to generate a clickable link and then use rightclick and Play to Kodi to cast the direct video link to the Kodi Box.
Which brings me to -
3. Discoverability is pretty lousy on remote based interfaces (Kodi has the best interface for it there is out there.). Its also pretty bad on phones (which is part of why more and more content becomes facebook native and why you are so dependent on content surfacing within an app "you like") or tablets. Its actually pretty excellent on laptops. So in some sense - I see the ultrabooks as the last bastion of non curated content and real discoverability out there.
Kodi with keyboard at that stage simply doesnt cut it. Also if you are more than a novice user you need a device you use to do maintenance on Kodi - so again - why not an Ultrabook...
-
Regarding your previous question - I know that the adb way of Firestarter noticing "that the Home button was pressed" depends heavily on certain lines within a log that only indicate that _that_ button is being pressed. I dont know how its dev handled the non adb implementation - you have to ask him. It is very unlikely - that you'd find the same or an equivalent "event indication" when you press a random key on a connected keyboard.
Remember that the watcher routine has to look for something occurring, and that in the case of Firestarter this preferably has to show up on non rooted devices also. In fact - that Firestarter (and its predecessor) exist is a little miracle in its own right - because Amazon could make a very small change and it would never be able to work again. In that sense its a hack - that relies on a very specific pattern showing up in something the OS is reporting and that is accessible by any app (userspace).
Its not based on a featureset, its based on a hack.
Hi,
I have a new TCL C715 running AndroidTV 9 and a german Logitech K380 bluetooth keyboard.
I can pair my keybord with the TV and it works, however it always behaves as if an american layout would be used, but I want to use a german layout.
This happens regardless of which language the TV is set to and there are no options to change the keyboard layout.
I have now tried to use the "External keyboard helper" app but even when I use that and set the layout to german in the app, the keyboard bahaves as if it were an american one.
Is there anyhing I could try to get a german layout?
Many thanks!