File for m8s II mini s905x
LE9.0 remote configs ir-keytable Amlogic devices
-
kostaman -
February 15, 2018 at 6:48 AM -
Thread is Unresolved
-
-
File for m8s II mini s905x
Oh! It's absolutely same remote with same S905X! But codes absolutely different))
Friend, could you please catch your remote scancodes of OK, UP and DOWN keys in the ssh terminal manner, as in my previouse post? Could you share log of this to compare with mine?
I hope, it could help me to find a problem... thank you!
-
Working for Nexbox A95X 2GB. If you use 1GB box, please change dtb to gxl_p212_1g.dtb .
All the best.
My remote is working correctly for the nexbox a95x except for the mouse function. I can't switch the remote to it. I suspect that this is not a standard KODI remote function but an amlogic one so with the switch to the new driver, there is no way to map it to the remote.
Very unfortunate because I used to use it on occasion.
-
Oh! It's absolutely same remote with same S905X! But codes absolutely different))
Friend, could you please catch your remote scancodes of OK, UP and DOWN keys in the ssh terminal manner, as in my previouse post? Could you share log of this to compare with mine?
I hope, it could help me to find a problem... thank you!
0x8025 KEY_LEFT
0x8026 KEY_UP
0x8027 KEY_RIGHT
0x8028 KEY_DOWN
0x800d KEY_ENTER
-
0x8025 KEY_LEFT
0x8026 KEY_UP
0x8027 KEY_RIGHT
0x8028 KEY_DOWN
0x800d KEY_ENTER
So, you just see in terminal exactly like this:
event type EV_MSC(0x04): scancode = 0x8025
And just copy-paste those codes into remote config file?
Hm... thank you... i wonder, why it could not work in my box..?
-
So, you just see in terminal exactly like this:
event type EV_MSC(0x04): scancode = 0x8025
And just copy-paste those codes into remote config file?
Hm... thank you... i wonder, why it could not work in my box..?
yes.. actually check if file loads by executing
ir-keytable -a /storage/.config/rc_maps.cfg -s rc0
if this gives an error delete comment from file..
-
Hi any have files for Z69 s905 remote? Here the picture of remote , thx
-
My remote is working correctly for the nexbox a95x except for the mouse function. I can't switch the remote to it. I suspect that this is not a standard KODI remote function but an amlogic one so with the switch to the new driver, there is no way to map it to the remote.
Very unfortunate because I used to use it on occasion.
No idea though. Anyone with nexbox a95x have a solution?
-
Hello. Guys can anyone with wetek play2 device check one button (this big star called Favourites above TXT button). I do not know why but I can't map only this button in keymap editor app . I see scancode for this button, is added into my rc keymap file but still does not work and I do not know why.
Best regards
-
Hello. Guys can anyone with wetek play2 device check one button (this big star called Favourites above TXT button). I do not know why but I can't map only this button in keymap editor app . I see scancode for this button, is added into my rc keymap file but still does not work and I do not know why.
Best regards
Have the same issue on my VIM2 remote. Seems to especially effect the FAV button but I am also seeing it with the SAT and RADIO/TV button. Scancodes are generated but Kodi fails to recognize them.
It seems to be a generic problem with IR_KEYTABLES because my old PC based system also fails to map the FAV button.
Shoog
-
Yes and also HOME button does not work Prevous with remote.conf file I could map all buttons in keymap editor app. And remote repeats is very bad now. Before it was working good . Now I adjusted it little bit but still sometimes "jumping"
-
Yes and also HOME button does not work Prevous with remote.conf file I could map all buttons in keymap editor app. And remote repeats is very bad now. Before it was working good . Now I adjusted it little bit but still sometimes "jumping"
the first post of this thread says that you can adjust the delay & repeats
-
Yes and also HOME button does not work Prevous with remote.conf file I could map all buttons in keymap editor app. And remote repeats is very bad now. Before it was working good . Now I adjusted it little bit but still sometimes "jumping"
Did you assign this buttons as KEY_FAVORITES and KEY_HOME?
you can try to add only this buttons in Lircmap.xls as in my example LE9.0 remote configs ir-keytable Amlogic devices
-
ABOX A1 Max, same remote as the A95X. Works great, thanks.
LE9.0 remote configs ir-keytable Amlogic devices
Edit: Added the TV control codes (before assigning)
Code
Display More0xdf0c KEY_NUMERIC_0 0xdf54 KEY_NUMERIC_1 0xdf16 KEY_NUMERIC_2 0xdf15 KEY_NUMERIC_3 0xdf50 KEY_NUMERIC_4 0xdf12 KEY_NUMERIC_5 0xdf11 KEY_NUMERIC_6 0xdf4c KEY_NUMERIC_7 0xdf0e KEY_NUMERIC_8 0xdf0d KEY_NUMERIC_9 0xdf06 KEY_ENTER 0xdf1a KEY_UP 0xdf48 KEY_DOWN 0xdf47 KEY_LEFT 0xdf07 KEY_RIGHT 0xdf18 KEY_MENU 0xdf0a KEY_BACK 0xdf5d KEY_VOLUMEUP 0xdf5c KEY_VOLUMEDOWN 0xdf4f KEY_NEXT 0xdf4b KEY_PREVIOUS 0xdf5f KEY_INFO 0xdf01 KEY_EPG 0xdf1c KEY_POWER 0xdf42 KEY_HOME # home 0xdf41 KEY_FAVORITE # planet 0xdf03 KEY_CONTEXT_MENU # mouse 0xdf10 KEY_BACK # back 0xdff1 KEY_SLEEP # TV Power 0xdff2 KEY_SELECT # TV Input 0xdff3 KEY_MUTE # TV Mute 0xdff4 KEY_PAGEUP # TV Vol- 0xdff5 KEY_PAGEDOWN # TV Vol+ 0x07 KEY_PAGEDOWN # TV Vol+ (This is the actual key code I got)
-
bubblegum57 , yes I know. I tested many configurations with repeats and adjusted it little bit . Now is better but still not this same like in older build. I will have to get used to it.
boot2k3 , thx You made my day I added Lircmap with these 2 buttons and after reboot everything is ok and I can map all of them
Best regards
-
Mine isnt working after upgrate anymore. my remote.conf is here:
Code
Display More# MYGICA NEC remote factory_code = 0xBD020001 work_mode = 0 repeat_enable = 1 repeat_delay = 40 repeat_peroid = 39 release_delay = 121 debug_enable = 0 reg_control = 0xfbe40 left_key_scancode = 0x99 right_key_scancode = 0xc1 up_key_scancode = 0xca down_key_scancode = 0xd2 ok_key_scancode = 0xce pageup_key_scancode = 0x9a pagedown_key_scancode = 0xcd key_begin 0xd8 0 ;BROWER 0xd4 0 ;SYM 0x80 66 ;MUTE 0xc6 0 ;PHOTO 0xd5 0 ;MUSIC 0xd1 0 ;MEDIA_RECORD 0x86 0 ;BROWER 0x90 111 ;DEL 0x83 0 ;SYM 0x92 2 ;NUM1 0x93 3 ;NUM2 0xcc 4 ;NUM3 0x8e 5 ;NUM4 0x8f 6 ;NUM5 0xc8 7 ;NUM6 0x8a 8 ;NUM7 0x8b 9 ;NUM8 0xc4 10 ;NUM9 0xd9 24 ;AT 0x87 11 ;NUM0 0x82 46 ;COM 0xdd 13 ;VOL+ 0x8c 12 ;VOL- 0x9c 0 ;ZOOM_IN 0x89 0 ;ZOOM_OUT 0x9a 104 ;PAGE_UP 0xcd 109 ;PAGE_DOWN 0x95 1 ;HOME 0xc5 23 ;NOTIFICATION 0x99 105 ;LEFT 0xca 103 ;UP 0xc1 106 ;RIGHT 0xd2 108 ;DOWN 0xce 28 ;OK 0xd6 46 ;MENU 0xd0 14 ;EXIT 0x96 51 ;PAGELEFT 0xc2 52 ;PAGERIGHT 0xc3 19 ;DEL 0x84 33 ;MEDIA_FAST_FORWARD 0xda 51 ;MEDIA_REWIND 0x88 25 ;MEDIA_STOP 0xc7 52 ;MEDIA_FAST_FORWARD 0x55 45 ;EXIT 0x45 31 ;POWER 0x85 57 ;Pause* 0xe0 20 ;ShowSubtitle* 0xe4 16 ;Queue* 0xe2 17 ;ToggelWatched* 0xd8 70 ;Browser* 0xe5 40 ;SmallStepBack* # 0x86 0x110 ;mouse left click # 0x83 0x111 ;mouse right click. key_end mouse_begin 0x00 0xc6 ;mouse move up 0x01 0xd1 ;mouse move down 0x02 0xd5 ;mouse move left 0x03 0x90 ;mouse move right mouse_end repeat_key_begin 0xdd 115 ;VOLUME_UP 0x8c 114 ;VOLUME_DOWN 0x99 105 ;DPAD_LEFT 0xca 103 ;DPAD_UP 0xc1 106 ;DPAD_RIGHT 0xd2 108 ;DPAD_DOWN repeat_key_end
-
Read the first post!
-
bubblegum57 , yes I know. I tested many configurations with repeats and adjusted it little bit . Now is better but still not this same like in older build. I will have to get used to it.
Another knob you can turn to improve remote response is the idle timeout. By default it's set to 200ms on Amlogic / meson-ir, which is quite long - other IR receiver drivers use 125ms.
This value determines how long it takes until Linux recognizes that you released a button. By lowering this value you'll get faster response to very short button presses and also the repeat delay will work more accurately (and you can set it to lower values, if you like).
As a rule of thumb 50-100ms should be safe, you can also try going down to 20-30ms. Low values can be problematic when the system is loaded and timeouts lower than 20ms will most certainly break IR reception completely. I'd start with 50ms and then test and adjust it to your liking.
You can change the timeout with ir-ctl -t , but note that the value is in microseconds. So, for 50ms you have to use a value of 50000:
so long,Hias
-