Anyone know how to disable the suspend on the beelink remote? While LE is running i would like the power button not to do anything, I would still like to turn it on when you power it off but just not to do anything when Kodi is running.I find the suspend feature does not really work and sometimes freezes the box requring me to pull the plug. Build 004 seems to handle well but still freezes but build 005 freezes very often when waking up from suspend.
Change it to something else in remote.conf (in /storage/.config) - or just removing the entry altogether in remote.conf should work.
That won't affect switching on - LE isn't running when it's off, the power-on is hard-coded to the box.
I'm using a Harmony with a pivos remote.conf on my minimxiii - the power-on code is still the one from the original remote and power-toggle on the pivos makes it sleep (which seems to be working reliably for me on 005).
Is it in your flash partition? IIRC the first time I booted one of kszaq's builds it copied my remote.conf from android to /flash.
Hi,
Would it possible to enable a key to shut down Kodi , not LibreELEC, when it freezes, so we won't have to get up and unplug the box? I had a Zoomtak T8 box that could do that.
This would be a nice feature to have on a remote control, I think.
Thank you very much.
It is better to find out why it freezes.
Gerald
I don't quite understand, you want a button to kill the kodi.bin process but keep LE running?
What would be the point of that other than running commands over ssh. When the box freezes for me it recovers after a few minutes or it crashs completely meaning i can't even use ssh at which point the ONLY solution is to get up and pull the cable.
What i have done with the raspi is setup a batch script that would restart the kodi process if kodi hanged and ssh was still accessible.
But you cant remap a key this way even if it where possible coz the keymaps are done in kodi so if kodi is frozen the keymaps mean nothing.
I understand it takes about 8 minutes for the box to recover itself. To me that's a long time. I prefer killing kodi and restarting it. I used to do this under android with a zoomtak box. I don't know if it's possible to do it under libreELEC. It was very convenient, to say the least, but I don't know how the guys at Zoomtak did it. I know it worked.
[hr]
It is better to find out why it freezes.Gerald
That would be the best solution indeed, but not much progress has been made toward finding it. OpenELEC for arm devices has the same problem. Hopefully it will be fixed soon.
My 2gb/16gb boxes very rarely freeze, it's the 1gb ones that freeze all the time.
Change it to something else in remote.conf (in /storage/.config) - or just removing the entry altogether in remote.conf should work.
That won't affect switching on - LE isn't running when it's off, the power-on is hard-coded to the box.
I have Minix A2 lite remote for Beelink MiniMXIII box. Power on from suspend is not working with A2 lite. If it is possible can you give me some advice how to change remote.conf to make power on with a2 lite working? Thank you!
Beelink original remote:
#*********************************************************************************************************
#this file is configuration for each factory remote device
# work_mode 0 [img]https://forum.libreelec.tv/images/smilies/confused.png[/img]oftware mode 1 :hardware mode
# repeat_enable 0 :disable repeat 1 :enable repeat
#
# factory_code each device has it's unique factory code.
# pattern:custom_code(16bit)+index_code(16bit)
# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
#
# release_delay unit:ms.release will report from kernel to user layer after this period of time
# from press or repeat triggered.
#
# debug_enable 0 :debug disable 1 :debug disable
#
# SW MODE:
# bit_count how many bits in each frame
# tw_leader_act time window for leader active
# tw_bit0 time window for bit0 time.
# tw_bit1 time window for bit1 time
# tw_repeat_leader time window for repeat leader
# REG
# reg_base_gen set value for PREG_IR_DEC_BASE_GEN
# reg_control set value for PREG_IR_DEC_CONTROL
# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
#*************************************************************************************************************
#amlogic NEC remote
factory_code = 0xff000001
factory_infcode = 1
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
fn_key_scancode = 0x5c
left_key_scancode = 0x0e
right_key_scancode = 0x1a
up_key_scancode = 0x3
down_key_scancode = 0x2
ok_key_scancode = 0x7
mouse_begin
0 0x0e
1 0x1a
2 0x3
3 0x2
mouse_end
key_begin
0x48 172
0x01 158
0x03 103
0x02 108
0x0e 105
0x1a 106
0x07 28
0x13 139
0x58 114
0x0b 115
0x5c 63
0x14 116
key_end
repeat_key_begin
0x48 172
0x01 158
0x03 103
0x02 108
0x0e 105
0x1a 106
0x07 28
0x13 139
0x58 114
0x0b 115
0x5c 63
0x14 116
repeat_key_endA2 lite remote:
#*********************************************************************************************************
#this file is configuration for each factory remote device
# work_mode 0 [img]https://forum.libreelec.tv/images/smilies/confused.png[/img]oftware mode 1 :hardware mode
# repeat_enable 0 :disable repeat 1 :enable repeat
#
# factory_code each device has it's unique factory code.
# pattern:custom_code(16bit)+index_code(16bit)
# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
#
# release_delay unit:ms.release will report from kernel to user layer after this period of time
# from press or repeat triggered.
#
# debug_enable 0 :debug disable 1 :debug disable
#
# SW MODE:
# bit_count how many bits in each frame
# tw_leader_act time window for leader active
# tw_bit0 time window for bit0 time.
# tw_bit1 time window for bit1 time
# tw_repeat_leader time window for repeat leader
# REG
# reg_base_gen set value for PREG_IR_DEC_BASE_GEN
# reg_control set value for PREG_IR_DEC_CONTROL
# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
#*************************************************************************************************************
#amlogic NEC remote
factory_code = 0xfe010001
work_mode = 0
repeat_enable = 1
repeat_delay = 40
repeat_peroid = 50
release_delay = 100
debug_enable = 0
left_key_scancode = 0x47
right_key_scancode = 0x15
up_key_scancode = 0x46
down_key_scancode = 0x16
ok_key_scancode = 0x55
key_begin
0x47 105 #DPAD_LEFT
0x15 106 #DPAD_RIGHT
0x46 103 #DPAD_UP
0x16 108 #DPAD_DOWN
0x55 97 #ENTER
0x40 1 #BACK
0x04 125 #MENU
0x14 115 #VOLUME_UP
0x10 114 #VOLUME_DOWN
0x0d 102 #HOME
0x18 116 #POWER WAKE
0x12 132 #TV_REPEAT
0x20 131 #ZOOM_OUT
0x21 130 #ZOOM_IN
0x22 217 #SEARCH
0x23 113 #VOLUME_MUTE
0x24 120 #MEDIA_FAST_FORWARD
0x25 121 #MEDIA_REWIND
0x26 119 #MEDIA_PLAY_PAUSE
0x27 128 #MEDIA_STOP
0x28 123 #MEDIA_NEXT
0x29 122 #MEDIA_PREVIOUS
0x30 2 #1
0x31 3 #2
0x32 4 #3
0x33 5 #4
0x34 6 #5
0x35 7 #6
0x36 8 #7
0x37 9 #8
0x38 10 #9
0x39 11 #0
0x41 14 #DEL
0x3a 52 #dot
0x3b 28 #ENTER
0x3c 359 #RECORD
0x3d 94 #prog1
0x3e 95 #prog2
0x3f 514 #prog3
0x41 515 #prog4
0x42 177 #pageup
0x43 178 #pagedown
0x44 358 #info
0x45 362 #guide
0x48 402 #CH+
0x49 403 #CH-
key_endI have Minix A2 lite remote for Beelink MiniMXIII box. Power on from suspend is not working with A2 lite. If it is possible can you give me some advice how to change remote.conf to make power on with a2 lite working? Thank you!
As I understand it the only way you can power-on is to use the original remote - nothing to do with remote.conf.
If you're using a Harmony or other programmable remote you can copy the power signal from the original (which is what I do).
Might be wrong though - I'm still trying to get to grips with amremote.
@troggy On some boxes I've seen u-boot adapting to power key code from userspace somehow and I was able to power on the box by any remote from u-boot sleep. Unfortunately in most of the cases you can only power on by original remote, like you said.
@troggy On some boxes I've seen u-boot adapting to power key code from userspace somehow and I was able to power on the box by any remote from u-boot sleep. Unfortunately in most of the cases you can only power on by original remote, like you said.
Interesting. I've really struggled to find any documentation on how amremote actually works, so lots of trial and error going on here. I have a pivos Harmony profile working pretty well, still struggling a bit with key repeats - I can get around those by mapping <longpress> to the same function as a single press in keyboard.xml, but it's a big faff.
you are right, this was copied directly from Android during install, orgional MXIII 107L1 firmware.
I mounted flash as RW and uploaded by modified conf with the power key disabled in LE. The button is now useless in LE but still powers on the box, shutdown, reboot etc still work from Kodi Power menu.Adding the remote.conf for anyone looking to do the same, I have outlined each button on the remote so people know what each key is.
Could you tell me where to drop the remote conf file please? I've installed le from a screwed nand so now the remote doesn't work 
Cheers
Gaz
Gentlemen,
I just ran through this because I had the same issue but the cause is different. My Toshiba TV had a Viera link that automatically turns off all devices. I needed to turn it off, it had nothing to do with remote.
Many TV's have a similar function to power off HDMI connected device so make sure the function is off.
