![flirc android flirc android](https://cdn.shopify.com/s/files/1/0176/3274/files/Raspberry-Pi-3-FLIRC-Box_large.png)
Now to make the analyse complete, I have noticed that some Android applications like netflix or kodi will bypass the keychar file, and only the "Android key codenames" called in the layout file will be triggered. Those additional actions are specified in the keychar file. Again, Android will use the Generic.kcm keychar in our case, and we could create our own keychar file using the device "Vendor ID" and "Product ID". Most of the "Android key codenames" can result in a different action when used together with a key-modifier such as ctrl, alt, numlock, etc. When an "Android key codename" is triggered, it will also be interpreted according to the keychar file, which is stored in the "/system/usr/keychar/xxxxxxx.kcm" files. I recommand you to have a look a this sample " Generic.kl" to better understand what. Later on, we will see that we can create our own layout file for any input device by using its "Vendor ID" and "Product ID". An other example is the original remote of the nexus player which uses the "Nexus_Remote.kl" layout. Each "Linux key code" will trigger an "Android key codename". In our case, Android will use the Generic.tl layout for the flirc because there is no specific file for it. So the first thing Android does is to match a HID codes it receives to the related "Linux key code" (also called "scan code"), using the appropriate layout file which is stored in the "/system/usr/keylayout/xxxxxxx.kl" files.
![flirc android flirc android](https://m.media-amazon.com/images/I/512s5ou23NL._AC_SL1500_.jpg)
I investigated how the Android key triggering system works, and I think that I pretty much understand why combinations like alt+esc works only in some programs, why it always work with the nexus remote, and what we need to achieve to have a fully working remote (even if I am not there yet). I am facing the same situation as you guys, trying to take the most of my flirc to control my nexus player.
![flirc android flirc android](https://botland.store/img/art/inne/15204_5b.jpg)
combing window key and right navigation key into one search button on my URC-880, I can launch search globally from anywhere (no matter what app you are in). The workaround above is working but not as seemless as using ONE home Nexus button (or keyboard media home key). to create an one-click button to exit Netflix, I combine F12 and right navigation key (to select 'yes' using URC-880). I have a workaround for this home button:ġ) Alt + Esc take me to Nexus home screen for all app (youtube, Kodi), except NetflixĢ) To exit Netflix, I use F12 key but it has a confirmation pop-up (No/Yes). Logitech keyboard Media home key can also work the same as Nexus home button. I just bought Flirc and Nexus player and integrate them with my universal remote URC-880. I got every keys mapped and working on my URC-880 except Nexus Home button, which can exit any apps and go back to Nexus home screen. Yawor/Jason, do you have a command line to map to Media home key? The home button on the remote is somehow detected differently when in an app. I tested this with the flirc as well as with a keyboard. So if the app doesn't have a way to exit within the menu you may be stuck. When you are within an app it only sends a back keypress. *I found something interesting in that the keyboard shortcuts for home (alt+esc) will not exit apps. If someone could help me map the home button this will be perfect. Just for reference, here's the Nexus Player's remoteĪnd here's a quick picture of the adapter + flirc Is there a way to manually map a remote button to the media home button? I can't exit some apps (XBMC) and can't easily jump between apps.
#FLIRC ANDROID BLUETOOTH#
Search isn't really needed because it only accepts voice search by default so it looks for a bluetooth mic to activate which I don't have. I got everything working except for search and home. A USB keyboard works just fine with a microUSB adapter. I'm got my Flirc working with Android TV. If your systems are any more sensitive, take a pass, or get the vendor to open up the sources so we can see everything and compile it ourselves.*UPDATE* Final key mappings I found below
![flirc android flirc android](https://i.ytimg.com/vi/N2CukaATuh0/maxresdefault.jpg)
My application is not networked or security sensitive so I don't worry too much about runtime security. I endded up running the programmer on an isolated system, and then blew away its disk and reinstalled the OS-quicker than studying the tens of megabytes of strace logs. Its one thing to trust Logitech or Microsoft with such a device, but another to trust a company whose support forum seems to be moribund and opsec seems to be dismal.
#FLIRC ANDROID SOFTWARE#
Afaict, the programming software is only distributed as an unsigned binary (not even https download)-then you must run it as root! The firmware for the device also seems to be closed source, so in effect, you are hooking up an autonomous keyboard that can inject any keystrokes it cares to emit. My major caveat relates to the security aspects of the device. As advertised, FLIRC USB was able to easily learn the keys for arbitrary remotes I tried, and the device could then be used deliver standard media keys in the target system.