[Obelix1]

I tried to use a "Fire TV Stick Remote" on my RPi2 with openelec 6.95. But not inputs are recognized within Kodi. I did, what's written in Post 28. But it doesn't work. But if i kill the kodi.bin and use evtest .

Code:

Available devices:
/dev/input/event0:      Amazon Fire TV Remote
Select the device event number [0-0]: 0
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x1949 product 0x404 version 0x11b
Input device name: "Amazon Fire TV Remote"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 96 (KEY_KPENTER)
    Event code 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
    Event code 139 (KEY_MENU)
    Event code 158 (KEY_BACK)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 168 (KEY_REWIND)
    Event code 172 (KEY_HOMEPAGE)
    Event code 208 (KEY_FASTFORWARD)
  Event type 3 (EV_ABS)
    Event code 40 (ABS_MISC)
      Value      0
      Min        0
      Max      255
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value   1000
    Repeat code 1 (REP_PERIOD)
      Value     33

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.05.15 14:06:41 =~=~=~=~=~=~=~=~=~=~=~=
Event: time 1463314004.290502, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
Event: time 1463314004.290502, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1463314004.290502, -------------- SYN_REPORT ------------
Event: time 1463314004.291769, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70050
Event: time 1463314004.291769, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1463314004.291769, -------------- SYN_REPORT ------------
Event: time 1463314005.377068, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70052
Event: time 1463314005.377068, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1463314005.377068, -------------- SYN_REPORT ------------
Event: time 1463314005.534697, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70052
Event: time 1463314005.534697, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1463314005.534697, -------------- SYN_REPORT ------------
Event: time 1463314006.681408, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
Event: time 1463314006.681408, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1463314006.681408, -------------- SYN_REPORT ------------
Event: time 1463314006.839007, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004f
Event: time 1463314006.839007, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1463314006.839007, -------------- SYN_REPORT ------------
Event: time 1463314007.716736, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
Event: time 1463314007.716736, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1463314007.716736, -------------- SYN_REPORT ------------
Event: time 1463314007.851947, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70051
Event: time 1463314007.851947, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1463314007.851947, -------------- SYN_REPORT ------------
Event: time 1463314008.954545, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70058
Event: time 1463314008.954545, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 1
Event: time 1463314008.954545, -------------- SYN_REPORT ------------
Event: time 1463314009.112157, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70058
Event: time 1463314009.112157, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0
Event: time 1463314009.112157, -------------- SYN_REPORT ------------
Event: time 1463314010.236184, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700f1
Event: time 1463314010.236184, type 1 (EV_KEY), code 158 (KEY_BACK), value 1
Event: time 1463314010.236184, -------------- SYN_REPORT ------------
Event: time 1463314010.416359, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700f1
Event: time 1463314010.416359, type 1 (EV_KEY), code 158 (KEY_BACK), value 0
Event: time 1463314010.416359, -------------- SYN_REPORT ------------
Event: time 1463314011.361664, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0223
Event: time 1463314011.361664, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 1
Event: time 1463314011.361664, -------------- SYN_REPORT ------------
Event: time 1463314011.541764, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0223
Event: time 1463314011.541764, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 0
Event: time 1463314011.541764, -------------- SYN_REPORT ------------
Event: time 1463314012.532027, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0040
Event: time 1463314012.532027, type 1 (EV_KEY), code 139 (KEY_MENU), value 1
Event: time 1463314012.532027, -------------- SYN_REPORT ------------
Event: time 1463314012.689635, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0040
Event: time 1463314012.689635, type 1 (EV_KEY), code 139 (KEY_MENU), value 0
Event: time 1463314012.689635, -------------- SYN_REPORT ------------
Event: time 1463314013.656147, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b4
Event: time 1463314013.656147, type 1 (EV_KEY), code 168 (KEY_REWIND), value 1
Event: time 1463314013.656147, -------------- SYN_REPORT ------------
Event: time 1463314013.836281, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b4
Event: time 1463314013.836281, type 1 (EV_KEY), code 168 (KEY_REWIND), value 0
Event: time 1463314013.836281, -------------- SYN_REPORT ------------
Event: time 1463314014.804192, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
Event: time 1463314014.804192, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1463314014.804192, -------------- SYN_REPORT ------------
Event: time 1463314014.961798, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
Event: time 1463314014.961798, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1463314014.961798, -------------- SYN_REPORT ------------
Event: time 1463314015.907067, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b3
Event: time 1463314015.907067, type 1 (EV_KEY), code 208 (KEY_FASTFORWARD), value 1
Event: time 1463314015.907067, -------------- SYN_REPORT ------------
Event: time 1463314016.042202, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00b3
Event: time 1463314016.042202, type 1 (EV_KEY), code 208 (KEY_FASTFORWARD), value 0
Event: time 1463314016.042202, -------------- SYN_REPORT ------------

autostart, udev rule and mount is working, but no inputs are recognized. Debug logging doesn't show anything. Any suggestions?

[Bahndit]

Not sure if I can make it much clearer..
Just run the below (and reboot) and you should be ok.

Code:

# Copy eventlircd.d to storage
cp -r /etc/eventlircd.d/ /storage/.config/eventlircd.d

# Create evmap for the remote
cat << EOF >> /storage/.config/eventlircd.d/aftvsremote.evmap
KEY_KPENTER      = KEY_OK
KEY_UP           = KEY_UP
KEY_LEFT         = KEY_LEFT
KEY_RIGHT        = KEY_RIGHT
KEY_DOWN         = KEY_DOWN
KEY_MENU         = KEY_EPG
KEY_BACK         = KEY_EXIT
KEY_PLAYPAUSE    = KEY_PLAY
KEY_REWIND       = KEY_REWIND
KEY_HOMEPAGE     = KEY_MEDIA
KEY_FASTFORWARD  = KEY_FASTFORWARD
EOF

# Add bind mount of /etc/eventlircd.d to autostart
echo "mount --bind /storage/.config/eventlircd.d/ /etc/eventlircd.d/" >> /storage/.config/autostart.sh

# Create udev rule
cat << EOF >> /storage/.config/udev.rules.d/99-eventlircd.rules
SUBSYSTEMS=="bluetooth", GOTO="begin-bluetooth"
GOTO="end-bluetooth"
LABEL="begin-bluetooth"

ATTRS{name}=="Amazon Fire TV Remote", \\
  ENV{eventlircd_enable}="true", \\
  ENV{eventlircd_evmap}="aftvsremote.evmap"

LABEL="end-bluetooth"
EOF

Thank you Whiterat!

[Skates]

Was anyone able to get the remote working on Windows? This would be great for my mother-in-law who needs a simple remote.

[meccs]

What keymap setting is the Fire TV remote using as default? It already knows that hamburger button = CodecInfo when fullscreen etc. How does he know that?

[wrxtasy]

Use a simple Addon:
http://kodi.wiki/view/Add-on:Keymap_Editor

Go to Fullscreen Video > Playback > Stop and remap your back button to Stop.

[meccs]

If I don't use the remote it takes a while to connect. Is there a way to change the Standby time of the remote devices to make it a bit longer?

[LongMan]

@ned Scott. I know you were strong supporter of improving the user experience with "limited button" remotes such as the fire tv remote. I think you might know where to look, or who to speak to about the fire tv stick remote and the raspberry pi 3. I want to use a Pi 3 and openELEC or LibreELEC, whichever works. Initially it paired, but pressing the buttons had no effect. I then used whiterat's procedure outlined earlier in this thread, and got it to work. However, the remote function is just basic compared with the same remote paired with my NUC. On the NUC I can edit the keyboard.xml to take advantage of, that beautiful feature that you championed, the long press. It would be wonderful to have this on the Pi 3. Is this a limitation of the Pi 3? Any help would be greatly appreciated.

Cheers,
LongMan

[Ned Scott]

I'll see what I can find out. It would be a shame if it couldn't use long-press.

[LongMan]

Thanks

[Ned Scott]

I see. Whiterat's fix is to use lirc, and lirc behaves differently than if the remote is just seen as a keyboard. So the real question is why the direct bluetooth connection isn't working.

I think lirc could still be used as a workaround, but I don't really know much about it. I'm assuming we would need to adjust something with keyrepeat rate to make long-press behave correctly.

[LongMan]

Why does it behave differently on the NUC. You pair it, it works. Edit the keyboard.xml and the customization is honored. It would suggest there is a difference in implementation between the two devices.

[Shane1]

I have this remote as well and will be getting the Bluetooth dongle later today.
But, the KODI I have is on a Odroid C2 and running Android OS. Anybody used it on a Android ??
Should I expect problems?

[Ned Scott]

Why does it behave differently on the NUC. You pair it, it works. Edit the keyboard.xml and the customization is honored. It would suggest there is a difference in implementation between the two devices.

I would guess it's a Pi3 specific issue, like the Bluetooth driver used for Pi3.

[LongMan]

Thanks Ned. So we have to wait for it to be resolved upstream. Hopefully it get resolved soon. A Pi3 and a Fire TV Stick remote is perfect to use in my family van. Fingers crossed.

Cheers,
LongMan.

[DashDevil]

I purchased a Fire TV Stick remote for use with an Asus Chromebox running OpenElec. With a quick mapping change it's almost perfect. But for some reason, every time I put my box into suspend the remote immediately wakes it back up. Not an issue with other remotes I've tried.

I have the same problem with the Amazon Fire TV Remote on my brand new Asus Chromebox running LibreElec: If I put the box into suspend the remote wakes it up immediately, so there is no way to put the box to sleep with having the Amazon Remote connected to it. Does anybody else have this problem? Is there a solution?

Thx!