I am trying to setup my Flirc with the Nexus Player, for both native NP keys and the full spectrum of XBMC/kodi keys. I have all of the kodi keys working properly and the UP, DOWN, LEFT, RIGHT, SELECT and PLAY/PAUSE buttons work just fine on the main Nexus Player interface. However, the mapped BACK and MENU keys are not working. For those that don't know, a Flirc USB devices presents itself as a standard keyboard to the Nexus Player and can be programmed on your PC to learn remote control commands to activate specific generic keyboard combinations.
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Thanks.
Elrondolio said:
I am trying to setup my Flirc with the Nexus Player, for both native NP keys and the full spectrum of XBMC/kodi keys. I have all of the kodi keys working properly and the UP, DOWN, LEFT, RIGHT, SELECT and PLAY/PAUSE buttons work just fine on the main Nexus Player interface. However, the mapped BACK and MENU keys are not working. For those that don't know, a Flirc USB devices presents itself as a standard keyboard to the Nexus Player and can be programmed on your PC to learn remote control commands to activate specific generic keyboard combinations.
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Thanks.
Click to expand...
Click to collapse
I haven't tested this yet, but typically the Windows key + ESC = HOME (or, depending, sometimes the HOME key itself on a keyboard). BACK is typically the ESC key by itself.
My FLIRC arrived yesterday -- just haven't configured it yet. I'll give it a whirl and get back to you!
PearcePowers said:
I haven't tested this yet, but typically the Windows key + ESC = HOME (or, depending, sometimes the HOME key itself on a keyboard). BACK is typically the ESC key by itself.
My FLIRC arrived yesterday -- just haven't configured it yet. I'll give it a whirl and get back to you!
Click to expand...
Click to collapse
Thank you. I got the back key working correctly (and, in the NP, it is indeed ESC), but you'll have to go in to XBMC/kodi and add in the keymapper in programs then globally change ESC to be BACKSPACE and BACKSPACE to be ESC. Otherwise the NP back key would be "previous menu" in kodi. Make sure to update your Flirc with the full keyboard template to change the ESC key to your remote button you wish. Once done, both the NP and kodi see ESC as the back key.
I still haven't figured out the HOME key yet... I have a "HOME" special button atop my wireless keyboard that works, but I can't scancode it properly so I'm not sure what it is yet (I've read it may be scancode 57, but thats normally "space", so not sure and haven't tested it yet) I'll see if WIN+ESC works from my keyboard when I get home tomorrow. Hope to hear your experiences as well... thanks.
Elrondolio said:
I'll see if WIN+ESC works from my keyboard when I get home tomorrow. Hope to hear your experiences as well... thanks.
Click to expand...
Click to collapse
I tested the following three keyboard commands -- WIN + ESC, ALT + ESC, and HOME -- and none work in the Nexus Player to take you home. Grr. I've got everything working but the HOME key as well.
PearcePowers said:
I tested the following three keyboard commands -- WIN + ESC, ALT + ESC, and HOME -- and none work in the Nexus Player to take you home. Grr. I've got everything working but the HOME key as well.
Click to expand...
Click to collapse
There is a topic about this over on the Flirc forums that you may want to follow:
http://forum.flirc.tv/index.php?/topic/1219-flirc-and-android-tv-adt-1/
I have a wireless keyboard that has extra media keys including a Home key (not the regular Home, End, etc). It works just like the Home key on the NP remote. I'm not at home right now, but had hooked it up to one of my laptops and that special Home key sends key code 172.
We just need to figure out how to teach Flirc that key code then map one of our remote buttons to that key.
Elrondolio said:
There is a topic about this over on the Flirc forums that you may want to follow:
http://forum.flirc.tv/index.php?/topic/1219-flirc-and-android-tv-adt-1/
I have a wireless keyboard that has extra media keys including a Home key (not the regular Home, End, etc). It works just like the Home key on the NP remote. I'm not at home right now, but had hooked it up to one of my laptops and that special Home key sends key code 172.
We just need to figure out how to teach Flirc that key code then map one of our remote buttons to that key.
Click to expand...
Click to collapse
Any luck with the home key and Flirc? I noticed no one has responded over in the Flirc forums yet.
PearcePowers said:
Any luck with the home key and Flirc? I noticed no one has responded over in the Flirc forums yet.
Click to expand...
Click to collapse
Not as yet. It seems more complicated than I first thought... the record_api function of flirc_util.exe can map HID commands to remote control buttons, but finding the correct HID for "Home" is difficult. There are thousands of HID commands as referenced in this document:
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
We're looking at the ones in the Consumer Page starting on page 75. There is a special modifier in the second argument of Firc's record_api, 102, that supposedly tells the Flirc to reference that Consumer Page, but finding the "Home" key for the first argument of record_api is difficult. In other words: no. No luck yet, but still trying.
It'd probably be useful if you were to post a thread over there asking for help with the Home key on the Nexus Player as well. I'd imagine the higher the request for it the more eyes it'll receive.
Could be something that could be setup in llama or tasker? Set NP to listen for XYZ key command and then "Go Home". Just a thought.
Elrondolio said:
Not as yet. It seems more complicated than I first thought... the record_api function of flirc_util.exe can map HID commands to remote control buttons, but finding the correct HID for "Home" is difficult. There are thousands of HID commands as referenced in this document:
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
We're looking at the ones in the Consumer Page starting on page 75. There is a special modifier in the second argument of Firc's record_api, 102, that supposedly tells the Flirc to reference that Consumer Page, but finding the "Home" key for the first argument of record_api is difficult. In other words: no. No luck yet, but still trying.
It'd probably be useful if you were to post a thread over there asking for help with the Home key on the Nexus Player as well. I'd imagine the higher the request for it the more eyes it'll receive.
Click to expand...
Click to collapse
Did you manage to map a true home function to your Flirc device, Elrondolio? The ALT + ESC key combination works okay for me in most cases although it doesn't work when I use Kodi. It's still better than no home functionality at all, though, so at least I won't always have to use the original Nexus Player remote when I need that feature. There's another thread at the Flirc forum which discusses this topic at http://forum.flirc.tv/index.php?/topic/1462-flirc-with-android-tv/.
ALT + TAB seems to be the ideal key combination to use for the home button. It works no matter which app you're in and although it causes the Nexus Player to display "your recent screens appear here" when you use that key combination, the on-screen message disappears as soon as you release the button.
Now if I can just figure out how to use the Nexus Player's Leanback keyboard with my universal remote so that I can select on-screen keys for searches instead of having the ENTER button close the keyboard off, that would make things just about perfect.
I was the one that posted in Flirc forum about the alt+tab for home.
For search using on-screen, map flirc to window key using command. then combine this key with navigation right key using your universal remote, such as logitech. so WIN + Right will launch search with on screen keyboard to type.
Thanks for posting your solution in the Flirc forum. I'm not trying to map a command to launch an on-screen keyboard but I'm trying to see if I can find a way to press the keys on the Leanback keyboard using my universal remote. This isn't a problem with some apps like Netflix or Kodi that have their own keyboards but for the Leanback keyboard that's used in apps like Google Play and YouTube, pressing the ENTER button on a universal remote causes the keyboard to close off. This problem does not exist with the original Nexus Player remote's select button because it is context-sensitive.
Elrondolio said:
If anyone has a standard keyboard hooked up to their NP either via Blutooth or USB OTG, can you tell me which keys correspond to the BACK and HOME functions on the Nexus Player or if those functions are working at all on your keyboard?
Click to expand...
Click to collapse
Back: Esc
Home: Alt+Esc
Unfortunately, the ALT + TAB key combination is not an ideal option for use with Android 6.0 Marshmallow. It actually brings up the recent apps screen and doesn't give the user easy access to the home screen (unless the recent apps screen is empty). I'll have to reprogram my Flirc back to ALT + ESC for the home screen function until someone finds a better solution for Android 6.0.
I don't have a nexus player but these issues sound similar to the shield tv.
To fix the Enter key issue with the onscreen keyboard, us the flirc_util to record the keypad's enter key (a different dev id than the other enter/return key):
HTML:
flirc_util.exe record_api 0 88
To record the Home button (that works from Kodi too), record Windows Key + Enter (the main Enter key works fine for this). Again, I don't have a nexus player but I assume it will work for it as well.
whiskaz77 said:
I don't have a nexus player but these issues sound similar to the shield tv.
To fix the Enter key issue with the onscreen keyboard, us the flirc_util to record the keypad's enter key (a different dev id than the other enter/return key):
HTML:
flirc_util.exe record_api 0 88
To record the Home button (that works from Kodi too), record Windows Key + Enter (the main Enter key works fine for this). Again, I don't have a nexus player but I assume it will work for it as well.
Click to expand...
Click to collapse
I tried out these key combinations with my Flirc on the Nexus Player and am happy to report that everything now works perfectly! Thank you kindly for sharing that useful information here with the rest of us.
GabbyWC said:
I tried out these key combinations with my Flirc on the Nexus Player and am happy to report that everything now works perfectly! Thank you kindly for sharing that useful information here with the rest of us.
Click to expand...
Click to collapse
Great! Happy to help. I'm glad it worked. Thanks for reporting back!
Windows Key + Enter => Home worked for me too!!! Kodi, Netflix and other apps now behave fine. Thanks a lot @whiskaz77
Related
So I got my Nexus 7, and think its awesome! I got mine so I can install it in the dashboard of my car to use as media player/navigation, all that good stuff.
I thought it would be great to use a bluetooth media remote attached to the steering wheel to control basic functions. I purchased the Satechi Media Remote, and for the most part it works perfect! There is only one main issue and one minor issue.
Main Issue:
The remote has a button on the bottom middle that has a square on it. It works just like pushing the Home button.
While it is in my dashboard, it will be rare that I need to go to the actual home screen, and instead i would like it to take me to the car dock app I use. I have been trying many things to get it to work and I can not get it to function as anything else!
I tried using the app "External Keyboard Helper" and it worked for remapping the other 2 lower buttons on the remote (which is part of question 2), but I can not get it to remap the middle button. When I use the degugger in External keyboard helper, if I push that button it doesnt log the keypress and goes to the home screen like it is supposed to. I tried manually setting the keycode (102) to run an app and it still just goes to the home screen.
The next thing I tried was to edit the actual keylayout files like what is outlined here:
http://forum.xda-developers.com/showthread.php?t=695936
Doing it this way I can not seem to get it to change any of the three buttons to anything else. At first I couldnt figure out which .kl file to edit, so I searched and replaced all instances of HOME and MOVE_HOME in all the files, and moved them back to the device, still no change.
Do I need to make a cutom .kl with the vendor name and id in the title?
Where do I get that information from?
I tried editing the file Vendor_05ac_Product_0239.kl since in its comments it says its for a "Apple Wireless Keyboard", which this device is supposed to emulate to work with ipods/ipads, still nothing.
I am at my witts end trying to find the right way to remap this one button on this little remote hahaha
The second issue which is very minor, which might not be solved in here. I want to map one of those other lower buttons to google voice search. When I run the setup for "External Keyboard Helper" it has a section for mapping the running of an app to a key, which worked for car dock and a car music player. The problem is, when I go to the Application shortcuts portion of the app, the only thing I see listed in there is "com.google.android.voicesearch". If I set that as the app to run when I press a key I see this..
"com.google.android.voicesearch is not installed"
Is there a way to launch google voice search without having to click on the microphone in the search bar?
I got the thing working! I had to make a new KL file for the "keyboard"
I found this thread that told me how to get the vendor and product id, that seemed to be what was missing.
http://www.thriveforums.org/forum/toshiba-thrive-development/9626-how-create-customized-keylayout-any-usb-bluetooth-keyboard-rooted.html
The file name needs to match those.. its information is
Vendor ID 05ac
Product ID 023c
so the kl file is named
Vendor_05ac_Product_023c.kl
The scan codes for the three lower buttons are
161 (bottom left with the keyboard logo)
172 (middle bottom with the square)
113 (bottom right with the mute logo)
I changed the one for the bottom middle to SEARCH, and from that point on I could remap the key with the app External Keyboard Helper.
Next thing I need to do is figure out how to run a app from a keypress without using that remapper.. and how to start google search from a keypress
ShreddinPB said:
I got the thing working! I had to make a new KL file for the "keyboard"
I found this thread that told me how to get the vendor and product id, that seemed to be what was missing.
http://www.thriveforums.org/forum/toshiba-thrive-development/9626-how-create-customized-keylayout-any-usb-bluetooth-keyboard-rooted.html
The file name needs to match those.. its information is
Vendor ID 05ac
Product ID 023c
so the kl file is named
Vendor_05ac_Product_023c.kl
The scan codes for the three lower buttons are
161 (bottom left with the keyboard logo)
172 (middle bottom with the square)
113 (bottom right with the mute logo)
I changed the one for the bottom middle to SEARCH, and from that point on I could remap the key with the app External Keyboard Helper.
Next thing I need to do is figure out how to run a app from a keypress without using that remapper.. and how to start google search from a keypress
Click to expand...
Click to collapse
have you made any progress on this? i'm interested in this as well...
I got one of these remotes as well to use as a music/gps remote in my vehicle mounted Nexus 7. It works well, but let's hope a smart developer will make a better "external keyboard helper".
Hi can someone share his .kl file.
The Satechi device doesn't work at all with my MK888b box.
Interesting in this too
Sent from my Nexus 5 using XDA Premium 4 mobile app
Know this is an old post, but this helped me immensely. Got a Satechi remote and this quick tutorial helped me a ton. Seemed a little pain in the ass-ish at first, but realistically only took 5 minutes to get situated. Now to figure out how to bind a key to a specific app.
You probably don't even have this device anymore, if you change the keycode for whatever button you want to have open Google search to look like
key XXX VOICE_ASSIST
It'll open up Google voice search for you.
Hi everbody,
I was playing with a USB keyboard that I connected to my fireTV and I have noticed something that I haven't read in the forums yet.
- The key used by the FireTV remote control for Home button is the Multimedia Key for "ZoomOut" in the browser.
- And the Key that is used to trigger the Microphone corresponds to the "ZoomIn" in the browser.
Maybe these ones are useful to @rbox (I know that he has already the Xposed module to overwrite the Home button), but maybe the mic can be associated with Google Search instead. Or with the voice search in kodi. That way we get rid of the keyboard.
Or maybe they are useful to @elmerohueso to create another addon to map them.
On my side I just connected a flirc and I am programming it with power button, volume from my AVR, subtitles search, etc.
However, I love the fireTV remote and I believe that there is no real need for a keyboard if the voice funcionality can be replaced by a voice keyboard.
Recently I bought this remote from ebay after seeing some review in youtube.
Link to the picture
https://www.dropbox.com/s/2ayzhrxwp4pfmjx/remote_shipped.jpg?dl=0
https://www.dropbox.com/s/qb0gvydypsrp9wq/2015-05-01%2014.50.39.jpg?dl=0
bought this from this ebay seller. seller sees very nice and answered lot of my question before order. Shipping was fast too. Got item less than 10 days
http://www.ebay.com/itm/151463742596?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
Out of the box, the gyro mouse works great in fire tv with safa luncher. menu button and all drictional button, keyboard works great. but Home button and back button does not work.
for some reason home and back button does not show any number in fire tv key scan app.
Anyway, I liked the gyro mouse so much I made a fix for it and like to share with you. Good thing of this remote is you can disable mouse operation any time by pressing a key or flipping the keyboard side up.
I remap the home button to vol- button and back button to vol+ button. Now everything works fine. But still have Play/Pause, FF, RW button missing but I can live with that.
Play pause can be done on the keyboard side by spacebar.
This remote also works in recovery mode too.
https://www.dropbox.com/s/otb7dp1y0yl9etb/Vendor_24a7_Product_2402.kl?dl=0
to remap it please copy the attached .kl file to the /system/usr/keylayout folder.
Do not rename this file.
for copy procedure follow this link
http://www.aftvnews.com/fix-ps4-dualshock-4-button-mapping-on-the-fire-tv/
I basically used the Generic.kl file and did some modification for these two button.
let me know if you have any issue.
Where is the file? and what do I search for on eBay to see this?
http://www.amazon.com/Multi-function-Keyboard-Wireless-Receiver-Installation/dp/B00D8119EO
goggles99 said:
Where is the file? and what do I search for on eBay to see this?
Click to expand...
Click to collapse
file link added.
How difficult would it be to modify the Leanback keyboard so that it could be used with universal remotes? My Nexus Player is connected to a Flirc USB infrared dongle which I use with a Philips SRP5107 universal remote. I have my universal remote's main OK button mapped to emulate the ENTER key on a keyboard and this works fine in most cases but not with the Leanback keyboard. It isn't a problem with some apps like Netflix or Kodi that have their own keyboards but for the Leanback keyboard that's used in apps like Google Play and YouTube, pressing the OK button on a universal remote causes that on-screen keyboard to close off. This problem does not exist with the original Nexus Player remote's select button because it is context-sensitive. Can the Leanback keyboard somehow be modified to *not* close but rather type the selected on-screen key when it detects an external ENTER key / OK button being pressed?
I have a Samsung TV and I want to use my TV remote to control Shield TV (over HDMI-CEC). This mostly works with one inconvenient problem. Android Back button is mapped to Samsung Exit button. Regular Samsung remotes have Return and Exit buttons and if you are using this remote then it's ok. But higher end Samsung TVs have Samsung smart remote and it only has Return button. The Return button also works as a Exit button if you hold it down for 2 seconds, but that's really inconvenient.
For me it would make a lot more sense if the Android Back button would be mapped to Samsung Return button and if possible then Android Home to Samsung Exit.
I have no idea why or who (Google, Nvidia or Samsung?) mapped the buttons as they are, but it is not usable for me. So is there any chance we can remap HDMI-CEC buttons?
I'm also looking at this thread. Interested to know if its possible.
if u can block the IR sensor, and just get a FLIRC, u can remap any or all functionality
I did some research and it seems it's Samsung's fault. Samsung has mapped it's Exit button to HDMI-CEC KEY_BACK. And the Return buttun is mapped to HDMI-CEC KEY_EXIT (it appears only Samsung is using it). Some manufacturers have added this Samsung specific button to their devices (PS3 for example) and considering that Samsung has the biggest TV market share, I think Nvidia should have added it too.
It seems it is possible to remap HDMI-CEC buttons by editing .kl files in /system/usr/keylayout/. It appears to be using Generic.kl file if there is no hdmi_cec_keys.kl file in that folder. I don't have root, so i cant test this at the moment.
Unfortunately it seems that we can't map Samsung Return button to anything, because Samsung specific KEY_EXIT is missing in kernel. So we would need to find someone who knows how to modify kernel and compile it for us Samsung TV users. Someone has done this for some other Android box there > https://github.com/hardkernel/linux/pull/178/commits/96e8846f78b077add5fdc8a93235deefd262f71b
Any devs here who could make this fix?