[jpage4500]

I'm using the FireTV2 with Kodi 16-RC1 and noticing that certain remote button presses will end up doing the action twice. I've never noticed this in past versions using the same configuration which makes me think it's a bug vs something I'm doing.

Anyway, here's more info on my setup and what's happening. I use a Harmony Smart Control remote and map the channel up/down buttons to page up/down commands.

Here's the snippet from my keyboard.xml file:

Code:

<Global>
    <keyboard>
      <rewind>PageUp</rewind>
      <fastforward>PageDown</fastforward>

Here's what I see in the log when I just press channel down button once (PAGE DOWN action):

Code:

20:53:30 T:18446744072295523560   DEBUG: Keyboard: scancode: 0x5a, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
20:53:30 T:18446744072295523560   DEBUG: bool CInputManager::OnKey(const CKey&): fastforward (0xf0c5) pressed, action is PageDown
20:53:30 T:18446744072322339080   DEBUG: Thread JobWorker start, auto delete: true
20:53:30 T:18446744073565527020   DEBUG: Previous line repeats 3 times.
20:53:30 T:18446744073565527020    INFO: Got MEDIA_BUTTON intent: 90, up:false
20:53:30 T:18446744072295523560   DEBUG: Keyboard: scancode: 0x5a, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
20:53:30 T:18446744072295523560   DEBUG: bool CInputManager::OnKey(const CKey&): fastforward (0xf0c5) pressed, action is PageDown
20:53:30 T:18446744073565527020    INFO: Got MEDIA_BUTTON intent: 90, up:true

The result is the list jumps down 2 pages.

This button repeat doesn't happen for other remote keys though.. I'm sure the Harmony Remote setup is correct and not sending multiple keypresses.

Any thoughts? I wonder if this is a side-effect of the new 'longpress' keyboard actions - which I actually love since the FireTV remote is lacking on keys.

[Koying]

Could you share the full debug log via xbmclogs.com, please.
Leave it to us to decide what is relevant and what is not, we need context

[jpage4500]

Sure, I can do when I'm at home.

I was actually expecting that others would have noticed the same problem too. I assumed (but will verify at home tonight) that the same issue would occur with the FireTV2 remote and the page down mapping should be fairly common. I think it's similar to #3 in this link - http://kodi.wiki/view/Alternative_keymap..._TV_remote

The thing about that log snippet that stood out to me is that it appears like 2 keys are pressed - both resulting in a 'PageDown' action. But, each one is followed by that MEDIA_BUTTON log which says the first keypress was a key 'down' and the second was a key 'up' event.

Anyway, I was hoping that would ring a bell for someone.. I remember reading in another thread that the Android key handling was changed in Jarvis which meant that initial builds didn't work very well with the FireTV's remote. Sorry, I can't find that post right now but will keep looking.

[jpage4500]

haha.. that older post I mentioned that I'd look for was from you

http://forum.kodi.tv/showthread.php?tid=...pid2169326

Anyway, I'll update to RC2 and try to reproduce using the original FTV remote. If it still happens, I'll post a log.

thanks again for the help!

[jpage4500]

Ok, full log here: http://pastebin.com/Ug97kG1f

I just turned on debug log and went to the movies library and pressed the FFD key (page down) on the fire tv remote - the entry is at the 18:25:49 timestamp. I then had to go back to the FTV Settings menu to turn ADB debugging off & on again to get the log.

[jpage4500]

It's been a few days and I don't see any other/similar threads reporting this issue.. does it happen (or not) for others?

To test you just need a fire tv 2 and Kodi 16 RC2 - go to any list and press whatever key you have mapped to 'page down' (assuming you have a key mapped to this action).

It also happens on the home screen if you press and hold the BACK key.. you should see the power menu appear and then disappear.

I'm just curious if this is something everyone sees or not..

[Koying]

You're not supposed to see "Got MEDIA_BUTTON" there, because we don't want those at that point.
Maybe an AFTV2 bug/specifics?

[jpage4500]

For what it's worth, I have an AFTV1 too which I can try out as well and report back on.

[jpage4500]

PageDown/Up works find on the AFTV1 running the same Jarvis/RC2.

I'm actually assuming this issue isn't page up/down but the FFWD / RWD keypresses which are mapped to page down/up.

btw - AFTV1 does share 1 similar issue with AFTV2.. long-pressing the BACK key when on the home screen quickly displays the exit menu and then it disappears. Not sure if this comes from the same root cause or not though..

[en0x]

is there a fix for it for ATFV2?

I'm having the exact issue on latest stable v16. Both have the same firetv os 5.0.5

Code:

21:27:27 T:18446744072287790512   DEBUG: Keyboard: scancode: 0x5a, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
21:27:27 T:18446744072287790512   DEBUG: bool CInputManager::OnKey(const CKey&): fastforward (0xf0c5) pressed, action is PageDown
21:27:27 T:18446744073559800812    INFO: Got MEDIA_BUTTON intent: 90, up:false
21:27:27 T:18446744072287790512   DEBUG: Keyboard: scancode: 0x5a, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
21:27:27 T:18446744072287790512   DEBUG: bool CInputManager::OnKey(const CKey&): fastforward (0xf0c5) pressed, action is PageDown
21:27:27 T:18446744073559800812    INFO: Got MEDIA_BUTTON intent: 90, up:true

[jpage4500]

You know the funny thing - this doesn't happen to me anymore. I'm not 100% sure what changed either. I assumed it was fixed in one of the more recent 16 beta versions but I wish I knew exactly what fixed it.

[en0x]

I'm able to "fix" it by adding longpress to my keyboard.xml file but then i need to press and hold

[jpage4500]

I spoke too fast.. it was working in the last beta build but now page up/down moves 2 pages again on both FTV1 and FTV2 running the Kodi 16 release version.

[ellekz]

I have the same issue as OP on my FireTV2. I've just updated from Kodi 16.0 Alpha 4 to the latest 16.1 and PageUp/PageDown gets registered twice.
My keymap.xml:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<keymap>
  <Global>
    <keyboard>
      <rewind>PageUp</rewind>
      <play_pause>ActivateWindow(Home)</play_pause>
      <fastforward>PageDown</fastforward>
    </keyboard>
  </Global>
[...]

Removing the <rewind> and <fastforward> keys results in no button actions at all. Is there any known workaround for this?

Edit: Well, great. I tried installing 16.0 again so I can use the keys.. but it won't let me: "App not installed." *sigh*

[ellekz]

Okay, I've found a workaround. I tried binding PageUp/PageDown to another button to see if the issue was with the command or the button. Turns out, assigning PageUp and PageDown to one more button solved the issue for the original button as well. But since my remote has a limited number of buttons, I couldn't sacrifice two buttons for this. So I tried assigning PageUp/PageDown to a made up button and what do you know - it worked. Here's my keymap.xml now:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<keymap>
  <Global>
    <keyboard>
      <rewind>PageUp</rewind>
      <play_pause>ActivateWindow(Home)</play_pause>
      <fastforward>PageDown</fastforward>
      <fuckup>PageUp</fuckup>
      <fuckdown>PageDown</fuckdown>
    </keyboard>
  </Global>
...

This completely fixed the issue for me.