Posts: 31,445
Joined: Jan 2011
From the logs posted, tt sees it as a keyboard, so a keyboard.xml file with the following button presses:
1-2: ignored
3: <up>, <down>, <left>, <right>
4: <return>
5:
6: <menu>
7:
8: <play_pause>
9: <backspace>
10:
We already know that 5 is the Android home button and isn't accessible to XBMC yet. 7 and 10 are the FF and RW buttons, but they didn't seem to record any actions in the logs. Do they work in XBMC?
Posts: 31,445
Joined: Jan 2011
(2014-04-06, 06:46)elmerohueso Wrote: My desired setup would be:
1. (not a button) Microphone
2. Ignore (it's tied directly into the Amazon search. Once rooted, hopefully this could be opened up to voice typing or something)
3. Up/Down/Left/Right, Short/Long Skips (during playback)
4. Select, Show OSD (during playback)
5. Ignore (it's tied in the Fire TV Home screen. Once rooted, hopefully could make it go to the XBMC home screen)
6. More Info, Show Codec Info (during playback)
7. Fast forward, Skip Track on Hold (can XBMC interpret button hold duration?)
8. Play/Pause
9. Back, Stop (during playback, that's how ATV2 did it, and I sort of liked that)
10. Rewind, Previous Track on Hold (can XBMC interpret button hold duration?)
For me, volume could be ignored as I'd rather change the volume on the TV/receiver itself, rather than XBMC.
Anyone have desired changes/additions for a keymap?
Not sure about the holds. For everything else, this should be all you need:
save as
keyboard.xml to
userdata (wiki)/keymaps/ :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<keymap>
<FullscreenVideo>
<keyboard>
<menu>CodecInfo</menu>
<backspace>Stop</backspace>
</keyboard>
</FullscreenVideo>
</keymap>
Posts: 31,445
Joined: Jan 2011
Posts: 332
Joined: Feb 2010
Reputation:
7
I am also willing to help donate a box to koying. Best, fastest and cheapest method would be to get someone from this forum to send a box. send it as used box, and lower the value, and it should go through fine.
This is an amazing box.
Posts: 538
Joined: Sep 2010
Reputation:
21
thanks a lot Ned! will be very useful
Posts: 31,445
Joined: Jan 2011
If Koying thinks it would help him then I'm sure the XBMC Foundation's Board of Directors would trust his judgment and invest in a box on to send to him. We have lots of Team members in the US that would be happy to relay the package, too. That's up to them, and for all we know Koying might not want or can't invest time specifically into the Fire TV. Google just announced their new relaunch of Google TV as Android TV, after all.
Posts: 31,445
Joined: Jan 2011
Fire TV is Android with a custom launcher. Maybe they might have the marketing power to make it the best choice, since it will be able to catch on and get support from others, etc, but from a development standpoint, it's just another Android box.
Posts: 191
Joined: Dec 2012
Reputation:
1
so, in comparison (and i know that the xbmc isnt nearly done to be optimized for the fire tv) how much faster than the ouya can one expect this to be?
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Let's give the Fire some time to settle down.
It's day one of its existence, and we all know a tech product is rarely bug-free on launch, those days.
The mediacodec/libstagefright code is working perfectly on dozens of devices, so my assumption right now is that a firmware update or two might solve the current issues by itself.
It seems the "XBMC on OUYA" 12.3.2 or SPMC 12.3.3 (those are Frodo) are viable backup solutions for now.
If, after the next firmware update or two, the issues are still there, then it might be worth to somehow have one shipped to me for deeper debugging.
Posts: 122
Joined: Aug 2010
Reputation:
1
I've read about people replacing the FireTV remote with another one, I wonder though... Do USB remotes/keyboards work only once inside XBMC or do they work as well for the FireTV interface? 'Cause it would be a pain having the use the oficial remote to get to XBMC and then switch.
)
