2013-12-07, 13:35
Hi all,
I have noticed some threads concerning the mis-handling of BACKSPACE and ESCAPE keys in the Android version of Frodo, and it appears these have been addressed in the upcoming Gotham release. But did you know:-
"F1" & "F4" keys (and maybe others) also have problems in Frodo Android, which Frodo Windows handle correctly. Example:-
I have XMBC 12.2 installed on both an Android K9 tv stick, and on Win7 PC. I control both systems with Justop F20 wireless remote.
The remote has a "Menu" button,which Showkey identifies as follows:-
Windows: Key id:112 (0x70), Sym: "F1", VK_F1
Android: Keycode: 131 , Symbol F1
XBMC (Win), Debug text:
12:47:46 T:8736 DEBUG: CApplication::OnKey: f1 (f090) pressed, action is
12:47:46 T:8736 DEBUG: ------ Window Deinit (Pointer.xml) ------
12:47:46 T:8736 DEBUG: ------ Window Init (Pointer.xml) ------
XBMC (Android), Debug text:
07:57:08 T:1738930456 DEBUG: Keyboard: scancode: 83, sym: 0000, unicode: 0000, modifier: 0
07:57:08 T:1738930456 DEBUG: : Trying Hardy keycode for 0xf200
07:57:08 T:1738930456 DEBUG: Previous line repeats 1 times.
07:57:08 T:1738930456 DEBUG: : 0 (f200) pressed, action is firstpage
The remote has a "Home" button,which Showkey identifies as follows:-
Windows: Key id:115 (0x73), Sym: "F4", VK_F4
Android: Keycode: 134 , Symbol F4
XBMC (Win), Debug text:
12:47:46 T:8736 DEBUG: CApplication::OnKey: f4 (f093) pressed, action is
12:47:46 T:8736 DEBUG: ------ Window Deinit (Pointer.xml) ------
12:47:46 T:8736 DEBUG: ------ Window Init (Pointer.xml) ------
XBMC (Android), Debug text:
07:57:13 T:1738930456 DEBUG: Keyboard: scancode: 86, sym: 0000, unicode: 0000, modifier: 0
07:57:13 T:1738930456 DEBUG: : Trying Hardy keycode for 0xf200
07:57:13 T:1738930456 DEBUG: Previous line repeats 1 times.
07:57:13 T:1738930456 DEBUG: : 0 (f200) pressed, action is firstpage
As can be seen from the above, both Windows & Android O/S seem to agree that F1 & F4 keys are being sent, however Frodo correctly interprets these in its Windows version, but fails to process them at all in the Android version.
Are the Dev's aware?
In the meantime, is there a plausable workaround I could implement on my Frodo Android installation to force these keys to be processed by XBMC?
I have noticed some threads concerning the mis-handling of BACKSPACE and ESCAPE keys in the Android version of Frodo, and it appears these have been addressed in the upcoming Gotham release. But did you know:-
"F1" & "F4" keys (and maybe others) also have problems in Frodo Android, which Frodo Windows handle correctly. Example:-
I have XMBC 12.2 installed on both an Android K9 tv stick, and on Win7 PC. I control both systems with Justop F20 wireless remote.
The remote has a "Menu" button,which Showkey identifies as follows:-
Windows: Key id:112 (0x70), Sym: "F1", VK_F1
Android: Keycode: 131 , Symbol F1
XBMC (Win), Debug text:
12:47:46 T:8736 DEBUG: CApplication::OnKey: f1 (f090) pressed, action is
12:47:46 T:8736 DEBUG: ------ Window Deinit (Pointer.xml) ------
12:47:46 T:8736 DEBUG: ------ Window Init (Pointer.xml) ------
XBMC (Android), Debug text:
07:57:08 T:1738930456 DEBUG: Keyboard: scancode: 83, sym: 0000, unicode: 0000, modifier: 0
07:57:08 T:1738930456 DEBUG: : Trying Hardy keycode for 0xf200
07:57:08 T:1738930456 DEBUG: Previous line repeats 1 times.
07:57:08 T:1738930456 DEBUG: : 0 (f200) pressed, action is firstpage
The remote has a "Home" button,which Showkey identifies as follows:-
Windows: Key id:115 (0x73), Sym: "F4", VK_F4
Android: Keycode: 134 , Symbol F4
XBMC (Win), Debug text:
12:47:46 T:8736 DEBUG: CApplication::OnKey: f4 (f093) pressed, action is
12:47:46 T:8736 DEBUG: ------ Window Deinit (Pointer.xml) ------
12:47:46 T:8736 DEBUG: ------ Window Init (Pointer.xml) ------
XBMC (Android), Debug text:
07:57:13 T:1738930456 DEBUG: Keyboard: scancode: 86, sym: 0000, unicode: 0000, modifier: 0
07:57:13 T:1738930456 DEBUG: : Trying Hardy keycode for 0xf200
07:57:13 T:1738930456 DEBUG: Previous line repeats 1 times.
07:57:13 T:1738930456 DEBUG: : 0 (f200) pressed, action is firstpage
As can be seen from the above, both Windows & Android O/S seem to agree that F1 & F4 keys are being sent, however Frodo correctly interprets these in its Windows version, but fails to process them at all in the Android version.
Are the Dev's aware?
In the meantime, is there a plausable workaround I could implement on my Frodo Android installation to force these keys to be processed by XBMC?
