Win Functional USB Remotes for Windows
#16
(2018-05-24, 07:49)Jeycop Wrote:
(2018-05-24, 06:54)Verdana Wrote: I DO NOT have this problem with the DoCooler H1

Please notice that if you turn the remote on the keyboard face, it will default to mouse mode.

but if i set the remote on it's proper face during the hole movie, then i do not have the airmouse function.
 Big thanks for your reply.

Maybe there are new versions of this remote on the market.
Or do you use a secret function to disable the airmouse even after stand by of the remote?
Press some button for longer or something like that?

If I put the remote on the table for 4-5 mins (keyboard is down side), the OK button and the BACK button are not working. If I press then the Mouse button , then they are working again.

But, this remote feels so good in hand and has so many features (5 IR-btns, keyboard, LED,  ...) so it is still the best I tested, and I tested many of them ^^
So thanks for your tip. 
 I really don't see any secret functions, mine just works. Maybe if you hold it and press something else than ok. Does the airmouse still activate ?

I think that if i press the ok button, it goes into airmouse mode. have you tried any other key ? like the down key ?

send me a picture of your remote

Here is a list of remotes I have made, not tried all of them :
MINIX NEO M1 (too few buttons)
FireTV Voice Remote (too few buttons)
Measy RC11 (no remote, only very big keyboard)
MINIX A2 (has audio port)
Tronsmart TSM-01 (too few buttons)
iPazzPort KP-810-19R (not available wildly, very colory buttons)
Mele RF05 (mic and speaker)
Mele RF03 (non removable battery, no IR Learning)
Rii i13 4 in 1 (has audio port, pops as sound card when connected)
rii i25a (has audio port, auto wake air mouse)
rii i25 V1 (has little infra red buttons, look for V2)
ipazzport KP-810-30 (not multiple devices)
ipazzport KP-810-30HS (too few buttons)
iPazzPort KP-810-18R (too few buttons)
iPazzPort KP-810-23 (too big receiver and too few buttons)
Mele F10 (Rechargeable, concentration on airmouse middle button, no numpad, enough buttons, no trackpad, very good airmouse)
FM5S (cheap chinese, not many buttons, internet explorer button)
iPazzPort KP-810-27R (same as mx3 variant)
MX3 (there is a version with voice input on the blue button)
MX3-M From Rii same as mx3 from aerb
MX 3 from rii (has many copies) MX3 is sold by several manufacturers including Vigica and Aerb (Good air mouse, aaa batteries, unable to change buttons mapping)
One for all Essence 4 (can't update on internet)
One For All Simple 4 (update on interenet, learn, can assign individual button to remote)
Meliconi Gumbody Digital 5 web (programmable via audio port)
Superior Electronics Freedom 4 in 1
Superior Electronics Superior 4 in 1

Rii i25 v2 (Azerty, IR Learning, airmouse, very good, all the buttons ok, sometimes the air mouse has to be disabled all the time depending on version)
DoCooler H1 Air Fly (qwerty, has touchpad very big, airmouse, touch keyboard, not the backlit version for play pause)
MINIX Neo A2 Lite (too few buttons, very good air mouse, no infrared for learning)
Reply
#17
(2018-05-24, 22:14)Verdana Wrote:
(2018-05-24, 07:49)Jeycop Wrote:
(2018-05-24, 06:54)Verdana Wrote: I DO NOT have this problem with the DoCooler H1

Please notice that if you turn the remote on the keyboard face, it will default to mouse mode.

but if i set the remote on it's proper face during the hole movie, then i do not have the airmouse function.
 Big thanks for your reply.

Maybe there are new versions of this remote on the market.
Or do you use a secret function to disable the airmouse even after stand by of the remote?
Press some button for longer or something like that?

If I put the remote on the table for 4-5 mins (keyboard is down side), the OK button and the BACK button are not working. If I press then the Mouse button , then they are working again.

But, this remote feels so good in hand and has so many features (5 IR-btns, keyboard, LED,  ...) so it is still the best I tested, and I tested many of them ^^
So thanks for your tip.       
 I really don't see any secret functions, mine just works. Maybe if you hold it and press something else than ok. Does the airmouse still activate ?

I think that if i press the ok button, it goes into airmouse mode. have you tried any other key ? like the down key ?

send me a picture of your remote

Here is a list of remotes I have made, not tried all of them :
MINIX NEO M1 (too few buttons)
FireTV Voice Remote (too few buttons)
...    
Wohooow, impressiv compilation.

In Kodi while a movie is running and the remote stands still for ~5 minutes, the "Back" and the "OK" button are not working for me.
After pressing the "airmouse" button they work again.

But if I start using the remote after these ~5 minutes with pressing the "Down" instead of "Back" or "OK", the the airmouse-mode will be disabled and "OK"-btn works.
This also happens when Airmouse is active -> pressing "down" or "up" -> Airmouse is dissabled. very strange.

I think I found the difference. 
Mine has backlight...
This will maybe cause into a different "stand by"- mode and after wake up it forgets the " dissabled airmouse".
H1 Backlit

Now I ordered the version without backlight for testing.

And again, big thank you to you.
Reply
#18
I don't have backlite (I REALLY wanted a play pause button directly acessible, I think it's the most important button of all, quick bite to eat, phone call, it saves you three button clicks, ok then move to pause, then ok)

There is also a version with internet explorer button

I am still searching and compiling a list of remotes for your to go through, and me. I think I found the one we are looking for. It has NO Airmouse,
KP-810-19RS
Also the KP-810-30

What's weird, is that if you go to ipazzport site, they won't be displayed, you have to go to unisengroup website, the mother company, to get them to be displayed.

http://www.unisengroup.com/en_productinfo.asp?id=302
http://www.unisengroup.com/en_productinfo.asp?id=215  (this one is available in both sites)
Reply
#19
(2018-05-25, 14:48)Verdana Wrote: I don't have backlite (I REALLY wanted a play pause button directly acessible, I think it's the most important button of all, quick bite to eat, phone call, it saves you three button clicks, ok then move to pause, then ok)

There is also a version with internet explorer button

I am still searching and compiling a list of remotes for your to go through, and me. I think I found the one we are looking for. It has NO Airmouse,
KP-810-19RS
Also the KP-810-30

What's weird, is that if you go to ipazzport site, they won't be displayed, you have to go to unisengroup website, the mother company, to get them to be displayed.

http://www.unisengroup.com/en_productinfo.asp?id=302
http://www.unisengroup.com/en_productinfo.asp?id=215  (this one is available in both sites)
 Hihi, really impressiv. You should post this in other forums or maybe do an acrticle in some hardware websites xD

I use this remote only for Kodi. So I have no problems with missing buttons like play/pause or others.  Just too few buttons is a problem Wink
I simply use the addon "keymapper" and map, for example for the H1:
mute -> play/pause"
pageup ->  change language 
pageDown -> change  subtitle.
0 -> stop

If this remote without backlight is like you tell, then I will stay at the H1.
Reply
#20
Hehe, fame is not my goal ! Smile

I am getting mixed reviews from the rii i25. a lot of people say that the airmouse doesn't default back on.

Also, I tried pushing another button on the H1 and I have the same weird scenario as you do. I usually only press the down key first so haven't encountered the bug.

the KP-810-19RS doesnt have that problem because no airmouse i guess.

I just ordered this remote off ebay : the G7 (whatever brand here) i'll see how it looks
https://www.ebay.com/itm/G7-3-Gsensor-Ai...2cd2d11ac8
Reply
#21
(2018-05-25, 15:17)Verdana Wrote: Hehe, fame is not my goal ! Smile

I am getting mixed reviews from the rii i25. a lot of people say that the airmouse doesn't default back on.

Also, I tried pushing another button on the H1 and I have the same weird scenario as you do. I usually only press the down key first so haven't encountered the bug.

the KP-810-19RS doesnt have that problem because no airmouse i guess.

I just ordered this remote off ebay : the G7 (whatever brand here) i'll see how it looks
https://www.ebay.com/itm/G7-3-Gsensor-Ai...2cd2d11ac8
 Today I got the H1 without backlight, like you said, it is the same with standby -> re enabled airmouse...

So now I'm switching between these two remotes at home, can't decide which one is better.

H1:
- Airmouse enabled after standby (in airmouse mode, OK and BACK don't work because left and right click)
- no backlight on keyboard
- keyboard typing is hard to master 
+ small design, very comfortable in hand
+ nice button feeling
+ 5 IR-buttons

T6C:
- only 1 programmable IR-button
- keys a bit soft -> no fast clicking
+ backlight with 7 different colors and dimmable
Reply
#22
(2018-05-28, 13:42)Jeycop Wrote:
(2018-05-25, 15:17)Verdana Wrote:  
 Today I got the H1 without backlight, like you said, it is the same with standby -> re enabled airmouse...

So now I'm switching between these two remotes at home, can't decide which one is better.

H1:
- Airmouse enabled after standby (in airmouse mode, OK and BACK don't work because left and right click)
- no backlight on keyboard
- keyboard typing is hard to master 
+ small design, very comfortable in hand
+ nice button feeling
+ 5 IR-buttons

T6C:
- only 1 programmable IR-button
- keys a bit soft -> no fast clicking
+ backlight with 7 different colors and dimmable 

Have you tried just pressing the DOWN button, under OK ? this usualy doesn't turn the airmouse on, then you can press any button you like
Reply
#23
(2018-05-28, 21:42)Verdana Wrote:
(2018-05-28, 13:42)Jeycop Wrote:
(2018-05-25, 15:17)Verdana Wrote:  
 Today I got the H1 without backlight, like you said, it is the same with standby -> re enabled airmouse...

So now I'm switching between these two remotes at home, can't decide which one is better.

H1:
- Airmouse enabled after standby (in airmouse mode, OK and BACK don't work because left and right click)
- no backlight on keyboard
- keyboard typing is hard to master 
+ small design, very comfortable in hand
+ nice button feeling
+ 5 IR-buttons

T6C:
- only 1 programmable IR-button
- keys a bit soft -> no fast clicking
+ backlight with 7 different colors and dimmable  

Have you tried just pressing the DOWN button, under OK ? this usualy doesn't turn the airmouse on, then you can press any button you like 
The DOWN button does in Kodi a big jump backwards in video play progress, so I can't press this one xD

Example:
- While video playing I want to check how long the movie is still going. Normally I have simply to press the OK Btn. Now first the Airmouse btn before the OK.

- Or If the movie is over and the credits are running. Pressing DOWN -> step backwards and Kodi don't recognize the movie as watched if I stop the movie now. OK and BACK not working -> so I have to press Airmouse first.

But yeah, this remote is so nice, I think I am going with the H1.
Reply
#24
(2018-05-29, 08:21)Jeycop Wrote:
(2018-05-28, 21:42)Verdana Wrote:
(2018-05-28, 13:42)Jeycop Wrote:  Today I got the H1 without backlight, like you said, it is the same with standby -> re enabled airmouse...

So now I'm switching between these two remotes at home, can't decide which one is better.

H1:
- Airmouse enabled after standby (in airmouse mode, OK and BACK don't work because left and right click)
- no backlight on keyboard
- keyboard typing is hard to master 
+ small design, very comfortable in hand
+ nice button feeling
+ 5 IR-buttons

T6C:
- only 1 programmable IR-button
- keys a bit soft -> no fast clicking
+ backlight with 7 different colors and dimmable  

Have you tried just pressing the DOWN button, under OK ? this usualy doesn't turn the airmouse on, then you can press any button you like   
The DOWN button does in Kodi a big jump backwards in video play progress, so I can't press this one xD

Example:
- While video playing I want to check how long the movie is still going. Normally I have simply to press the OK Btn. Now first the Airmouse btn before the OK.

- Or If the movie is over and the credits are running. Pressing DOWN -> step backwards and Kodi don't recognize the movie as watched if I stop the movie now. OK and BACK not working -> so I have to press Airmouse first.

But yeah, this remote is so nice, I think I am going with the H1.  

I have finaly received and tested the G7 Remote. And I can comfirm, without a doubt, that my remote DOES NOT default back to the air mouse. I used it, then let it rest for more than 5 minutes, then picked it up again, and I know it's been in sleep mode because the first button press did not work, the second one did, and the air mouse was off.

Also, the keyboard is better than the H1. I think it's my prefered remote. here is the aliexpress link : https://goo.gl/iyBS5F

best
Reply
#25
(2018-05-24, 07:49)Jeycop Wrote:
(2018-05-24, 06:54)Verdana Wrote: I DO NOT have this problem with the DoCooler H1

Please notice that if you turn the remote on the keyboard face, it will default to mouse mode.

but if i set the remote on it's proper face during the hole movie, then i do not have the airmouse function.
 Big thanks for your reply.

Maybe there are new versions of this remote on the market.
Or do you use a secret function to disable the airmouse even after stand by of the remote?
Press some button for longer or something like that?

If I put the remote on the table for 4-5 mins (keyboard is down side), the OK button and the BACK button are not working. If I press then the Mouse button , then they are working again.

But, this remote feels so good in hand and has so many features (5 IR-btns, keyboard, LED,  ...) so it is still the best I tested, and I tested many of them ^^
So thanks for your tip.  
 I'm looking for a remote for a RPi running Kodi but ideally one that will also work for Kodi on a Windows 10 laptop as well. I was considering the MINIX NEO A2 Lite but the lack of backlight put me off a bit.

The DoCooler H1 looks like it might be better, although if the airmouse is going to keep enabling itself that's going to be annoying enough to cancel out the benefits for my brother who I'm getting it for.

It's fairly cheap though, so I might buy one and hope for the best. Does anyone know if it works with both the RPi and Windows 10 and if the buttons can be reassigned via lircmap.xml and keymap.xml?

Also, how does the IR learning function work? I mean can functions from my TV remote be learnt onto any of the keys or just certain ones and are they then unavailable to Kodi or can I switch between IR/TV mode and Kodi mode?
Reply
#26
Get flirc and use any remote
Reply
#27
already tried and not worked properly.

can't type text with flirc, limited functionality.

Meehhh... returned !
Reply
#28
(2018-12-14, 22:16)Verdana Wrote: already tried and not worked properly.

can't type text with flirc, limited functionality.

Meehhh... returned !

I usee my keyboard remote with flirc everyday. Now it works with macros as well. You can map all 12 function keys from a windows keyboard. Did you try the latest programming gui?
Reply
#29
So I bought the DoCooler H1 and most of the keys work except for the four coloured ones.

With debug logging on, I see these entries in the log:
Code:
16:13:53.953 T:1938110864   DEBUG: Keyboard: scancode: 0x0e, sym: 0x0008, unicode: 0x0008, modifier: 0x0
16:13:53.953 T:1938110864   DEBUG: HandleKey: backspace (0xf008) pressed, action is Back

16:14:02.489 T:1938110864   DEBUG: Keyboard: scancode: 0x6a, sym: 0x0113, unicode: 0x0000, modifier: 0x0
16:14:02.489 T:1938110864   DEBUG: HandleKey: right (0xf083) pressed, action is Right

16:14:03.182 T:1938110864   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
16:14:03.182 T:1938110864   DEBUG: HandleKey: left (0xf082) pressed, action is Left

16:13:58.333 T:1938110864   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
16:13:58.333 T:1938110864   DEBUG: HandleKey: down (0xf081) pressed, action is Down

16:13:59.009 T:1938110864   DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
16:13:59.012 T:1938110864   DEBUG: HandleKey: up (0xf080) pressed, action is Up

16:14:04.197 T:1938110864   DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
16:14:04.197 T:1938110864   DEBUG: HandleKey: return (0xf00d) pressed, action is Select

16:14:05.128 T:1938110864   DEBUG: Keyboard: scancode: 0xac, sym: 0x00ac, unicode: 0x0000, modifier: 0x0
16:14:05.128 T:1938110864   DEBUG: HandleKey: browser_home (0xf0b6) pressed, action is ActivateWindow(Home)

16:14:06.445 T:1938110864   DEBUG: Keyboard: scancode: 0x7f, sym: 0x013f, unicode: 0x0000, modifier: 0x0
16:14:06.605 T:1938110864   DEBUG: HandleKey: menu (0xf0d8) pressed, action is ContextMenu

16:14:07.356 T:1938110864   DEBUG: Keyboard: scancode: 0x71, sym: 0x00ad, unicode: 0x0000, modifier: 0x0
16:14:07.356 T:1938110864   DEBUG: HandleKey: volume_mute (0xf0b7) pressed, action is Mute
16:14:07.529 T:1938110864   DEBUG: Keyboard: scancode: 0x71, sym: 0x00ad, unicode: 0x0000, modifier: 0x0

16:14:08.677 T:1938110864   DEBUG: Keyboard: scancode: 0x72, sym: 0x00ae, unicode: 0x0000, modifier: 0x0
16:14:08.677 T:1938110864   DEBUG: HandleKey: volume_down (0xf0b8) pressed, action is VolumeDown
16:14:08.845 T:1938110864   DEBUG: Keyboard: scancode: 0x72, sym: 0x00ae, unicode: 0x0000, modifier: 0x0

16:14:09.101 T:1938110864   DEBUG: Keyboard: scancode: 0x73, sym: 0x00af, unicode: 0x0000, modifier: 0x0
16:14:09.101 T:1938110864   DEBUG: HandleKey: volume_up (0xf0b9) pressed, action is VolumeUp
16:14:09.217 T:1938110864   DEBUG: Keyboard: scancode: 0x73, sym: 0x00af, unicode: 0x0000, modifier: 0x0

16:14:10.477 T:1938110864   DEBUG: Keyboard: scancode: 0x68, sym: 0x0118, unicode: 0x0000, modifier: 0x0
16:14:10.477 T:1938110864   DEBUG: HandleKey: pageup (0xf084) pressed, action is PageUp
16:14:10.669 T:1938110864   DEBUG: Keyboard: scancode: 0x68, sym: 0x0118, unicode: 0x0000, modifier: 0x0

16:14:11.402 T:1938110864   DEBUG: Keyboard: scancode: 0x6d, sym: 0x0119, unicode: 0x0000, modifier: 0x0
16:14:11.403 T:1938110864   DEBUG: HandleKey: pagedown (0xf085) pressed, action is PageDown
16:14:11.549 T:1938110864   DEBUG: Keyboard: scancode: 0x6d, sym: 0x0119, unicode: 0x0000, modifier: 0x0

16:14:15.727 T:1938110864   DEBUG: Keyboard: scancode: 0xa8, sym: 0x00ba, unicode: 0x0000, modifier: 0x0
16:14:15.727 T:1938110864   DEBUG: HandleKey: rewind (0xf0c4) pressed, action is Rewind
16:14:15.727 T:1938110864   DEBUG: Keyboard: scancode: 0xa8, sym: 0x00ba, unicode: 0x0000, modifier: 0x0

16:14:15.728 T:1938110864   DEBUG: Keyboard: scancode: 0xd0, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
16:14:15.728 T:1938110864   DEBUG: HandleKey: fastforward (0xf0c5) pressed, action is FastForward
16:14:15.835 T:1938110864   DEBUG: Keyboard: scancode: 0xd0, sym: 0x00bb, unicode: 0x0000, modifier: 0x0

16:14:17.049 T:1938110864   DEBUG: Keyboard: scancode: 0xa5, sym: 0x00b1, unicode: 0x0000, modifier: 0x0
16:14:17.049 T:1938110864   DEBUG: HandleKey: prev_track (0xf0bb) pressed, action is SkipPrevious
16:14:17.238 T:1938110864   DEBUG: Keyboard: scancode: 0xa5, sym: 0x00b1, unicode: 0x0000, modifier: 0x0

16:14:14.529 T:1938110864   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0
16:14:14.529 T:1938110864   DEBUG: HandleKey: next_track (0xf0ba) pressed, action is SkipNext
16:14:14.718 T:1938110864   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0 

but nothing when I press the coloured keys.

For my CEC remote the coloured keys work and show in the log like this:
Code:
16:13:37.395 T:1938110864 DEBUG: HandleKey: 251 (0xfb, obc4) pressed, action is FullScreen
16:13:38.089 T:1938110864 DEBUG: HandleKey: 252 (0xfc, obc3) pressed, action is CodecInfo
16:13:39.589 T:1938110864 DEBUG: HandleKey: 253 (0xfd, obc2) pressed, action is AspectRatio
16:13:39.609 T:1938110864 DEBUG: HandleKey: 254 (0xfe, obc1) pressed, action is AudioNextLanguage

and I've created a remote.xml in the keymaps folder to keep this behaviour consistent
Code:
<keymap>
<global>
<keyboard>
<key id="251">FullScreen</key>
<key id="252">CodecInfo</key>
<key id="253">AspectRatio</key>
<key id="254">AudioNextLanguage</key>
</keyboard>
</global>
</keymap>

How do I get the coloured keys on the H1 working and how do I identify them to re-map them (or any of the H1 keys) in remote.xml?
Reply
#30
(2019-01-01, 18:40)doveman2 Wrote: So I bought the DoCooler H1 and most of the keys work except for the four coloured ones.

With debug logging on, I see these entries in the log:
Code:
16:13:53.953 T:1938110864   DEBUG: Keyboard: scancode: 0x0e, sym: 0x0008, unicode: 0x0008, modifier: 0x0
16:13:53.953 T:1938110864   DEBUG: HandleKey: backspace (0xf008) pressed, action is Back

16:14:02.489 T:1938110864   DEBUG: Keyboard: scancode: 0x6a, sym: 0x0113, unicode: 0x0000, modifier: 0x0
16:14:02.489 T:1938110864   DEBUG: HandleKey: right (0xf083) pressed, action is Right

16:14:03.182 T:1938110864   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
16:14:03.182 T:1938110864   DEBUG: HandleKey: left (0xf082) pressed, action is Left

16:13:58.333 T:1938110864   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
16:13:58.333 T:1938110864   DEBUG: HandleKey: down (0xf081) pressed, action is Down

16:13:59.009 T:1938110864   DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
16:13:59.012 T:1938110864   DEBUG: HandleKey: up (0xf080) pressed, action is Up

16:14:04.197 T:1938110864   DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
16:14:04.197 T:1938110864   DEBUG: HandleKey: return (0xf00d) pressed, action is Select

16:14:05.128 T:1938110864   DEBUG: Keyboard: scancode: 0xac, sym: 0x00ac, unicode: 0x0000, modifier: 0x0
16:14:05.128 T:1938110864   DEBUG: HandleKey: browser_home (0xf0b6) pressed, action is ActivateWindow(Home)

16:14:06.445 T:1938110864   DEBUG: Keyboard: scancode: 0x7f, sym: 0x013f, unicode: 0x0000, modifier: 0x0
16:14:06.605 T:1938110864   DEBUG: HandleKey: menu (0xf0d8) pressed, action is ContextMenu

16:14:07.356 T:1938110864   DEBUG: Keyboard: scancode: 0x71, sym: 0x00ad, unicode: 0x0000, modifier: 0x0
16:14:07.356 T:1938110864   DEBUG: HandleKey: volume_mute (0xf0b7) pressed, action is Mute
16:14:07.529 T:1938110864   DEBUG: Keyboard: scancode: 0x71, sym: 0x00ad, unicode: 0x0000, modifier: 0x0

16:14:08.677 T:1938110864   DEBUG: Keyboard: scancode: 0x72, sym: 0x00ae, unicode: 0x0000, modifier: 0x0
16:14:08.677 T:1938110864   DEBUG: HandleKey: volume_down (0xf0b8) pressed, action is VolumeDown
16:14:08.845 T:1938110864   DEBUG: Keyboard: scancode: 0x72, sym: 0x00ae, unicode: 0x0000, modifier: 0x0

16:14:09.101 T:1938110864   DEBUG: Keyboard: scancode: 0x73, sym: 0x00af, unicode: 0x0000, modifier: 0x0
16:14:09.101 T:1938110864   DEBUG: HandleKey: volume_up (0xf0b9) pressed, action is VolumeUp
16:14:09.217 T:1938110864   DEBUG: Keyboard: scancode: 0x73, sym: 0x00af, unicode: 0x0000, modifier: 0x0

16:14:10.477 T:1938110864   DEBUG: Keyboard: scancode: 0x68, sym: 0x0118, unicode: 0x0000, modifier: 0x0
16:14:10.477 T:1938110864   DEBUG: HandleKey: pageup (0xf084) pressed, action is PageUp
16:14:10.669 T:1938110864   DEBUG: Keyboard: scancode: 0x68, sym: 0x0118, unicode: 0x0000, modifier: 0x0

16:14:11.402 T:1938110864   DEBUG: Keyboard: scancode: 0x6d, sym: 0x0119, unicode: 0x0000, modifier: 0x0
16:14:11.403 T:1938110864   DEBUG: HandleKey: pagedown (0xf085) pressed, action is PageDown
16:14:11.549 T:1938110864   DEBUG: Keyboard: scancode: 0x6d, sym: 0x0119, unicode: 0x0000, modifier: 0x0

16:14:15.727 T:1938110864   DEBUG: Keyboard: scancode: 0xa8, sym: 0x00ba, unicode: 0x0000, modifier: 0x0
16:14:15.727 T:1938110864   DEBUG: HandleKey: rewind (0xf0c4) pressed, action is Rewind
16:14:15.727 T:1938110864   DEBUG: Keyboard: scancode: 0xa8, sym: 0x00ba, unicode: 0x0000, modifier: 0x0

16:14:15.728 T:1938110864   DEBUG: Keyboard: scancode: 0xd0, sym: 0x00bb, unicode: 0x0000, modifier: 0x0
16:14:15.728 T:1938110864   DEBUG: HandleKey: fastforward (0xf0c5) pressed, action is FastForward
16:14:15.835 T:1938110864   DEBUG: Keyboard: scancode: 0xd0, sym: 0x00bb, unicode: 0x0000, modifier: 0x0

16:14:17.049 T:1938110864   DEBUG: Keyboard: scancode: 0xa5, sym: 0x00b1, unicode: 0x0000, modifier: 0x0
16:14:17.049 T:1938110864   DEBUG: HandleKey: prev_track (0xf0bb) pressed, action is SkipPrevious
16:14:17.238 T:1938110864   DEBUG: Keyboard: scancode: 0xa5, sym: 0x00b1, unicode: 0x0000, modifier: 0x0

16:14:14.529 T:1938110864   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0
16:14:14.529 T:1938110864   DEBUG: HandleKey: next_track (0xf0ba) pressed, action is SkipNext
16:14:14.718 T:1938110864   DEBUG: Keyboard: scancode: 0xa3, sym: 0x00b0, unicode: 0x0000, modifier: 0x0 

but nothing when I press the coloured keys.

For my CEC remote the coloured keys work and show in the log like this:
Code:
16:13:37.395 T:1938110864 DEBUG: HandleKey: 251 (0xfb, obc4) pressed, action is FullScreen
16:13:38.089 T:1938110864 DEBUG: HandleKey: 252 (0xfc, obc3) pressed, action is CodecInfo
16:13:39.589 T:1938110864 DEBUG: HandleKey: 253 (0xfd, obc2) pressed, action is AspectRatio
16:13:39.609 T:1938110864 DEBUG: HandleKey: 254 (0xfe, obc1) pressed, action is AudioNextLanguage

and I've created a remote.xml in the keymaps folder to keep this behaviour consistent
Code:
<keymap>
<global>
<keyboard>
<key id="251">FullScreen</key>
<key id="252">CodecInfo</key>
<key id="253">AspectRatio</key>
<key id="254">AudioNextLanguage</key>
</keyboard>
</global>
</keymap>

How do I get the coloured keys on the H1 working and how do I identify them to re-map them (or any of the H1 keys) in remote.xml? 

Try the G7
Reply



Logout Mark Read Team Forum Stats Members Help
Functional USB Remotes for Windows0
This forum uses Lukasz Tkacz MyBB addons.