S905X Android 8.0 Oreo (Tested on Mini M8S II. Possibile to work on other GXL/S905X boxes. Testing needed! "WIP")

[soldiaz]

Ok, I wouldLiketo share a Very responsive regular 7.1.2 but Remote codes are hardcoded. Maybe I could try remotecfg from Poison rom to get Remote.conf working....worth trying

but I am not a dev..

[soldiaz]

thanks for the hint!!

[01520717]

If you look at the Poison ROMs, they run remotecfg as a service. If I remember right, it is defined in init.amlogic.rc.

The problem with going this route is that you'll have either find a copy of remotecfg that's compiled for the kernel version used in lewy's ROM or you'll have to find the source code and compile it yourself. I've never looked for the source code so I don't know if it is publicly available.

[lewy20041]

That file is a symlink to vendor partition. Thats how it works in oreo.As to remote.cfg it wont work in this rom. Buttons mappings are hardcoded in dtb.

[soldiaz]

I just unpacked and made a screenshot....this is contents of level 2:

Windows says it is .sys file?

When opening as txt file this is content: !<symlink>&#255;&#254;/ v e n d o r

Curious....I thought I could open it yesterday as txt file and it showed some chinese chars...like this:

xxxxxxx\vendor...weired ..maybe I dreamed of it lol

01520717 any idea how to manage to loadup remotecfg to be able to load old remote.conf?

[sagert]

Thanks! I guess I will try it!

I am still thinking of one thing:

There are Nougat DTBs without customcode (=factorycode) inside BUT with etc\remote.conf....

The DTBs with customcode inside do not have etc\remote.conf but have (in my case) remote_mouse1.tab, remote_mouse2.tab in etc\

...

Maybe, if customcode is missing in DTB then device looksup etc\remote.conf?

In android 8 i have in my /vendor/etc files remote.tab1 , remote.tab2 , remote.tab3 .

[01520717]

It is difficult editing remote configurations in a device tree so some Nougat and newer boxes have a specialized program, e.g. remotecfg, that runs during the box's startup process to load remote configurations from the old-style remote.conf file.

[soldiaz]

Thanks! I guess I will try it!

I am still thinking of one thing:

There are Nougat DTBs without customcode (=factorycode) inside BUT with etc\remote.conf....

The DTBs with customcode inside do not have etc\remote.conf but have (in my case) remote_mouse1.tab, remote_mouse2.tab in etc\

...

Maybe, if customcode is missing in DTB then device looksup etc\remote.conf?

[01520717]

You can find your remote's scan codes by opening up a terminal, e.g. Terminal Emulator for Android, pressing one key on the remote then running
dmesg | tail
and you should see the scan code generated by that key. Then you look up the key code for that key at the link in my last post and find the hex code for the key. In the keymap entry in the device tree, there should be one entry for each key on your remote.

For example, if you press the Home key and you see a scancode of 0x15 in the dmesg output you lookup the Home key in the keycode table and see it is 102 or 0x66. The keymap entry for this key will be 0x150066. Do the same for the next key and separate entries in the keymap with a space, e.g. 0x150066 0x130064 etc.

[soldiaz]

I would like to set like 10 buttons....

Is it then like this?

keymap = <1st_KEY(0x09,115) 2nd_KEY(0x09,115)>

How do you get scancode? With an app?

[soldiaz]

01520717 Thanks! The lighted bit up!

If I understood correctly then

1. Insert factory / customcode to DTB
2. Map buttons

I found an example through your given link but it is not clear to me

In this example there is no "keymap" just the mapping....

map_0{ mapname = "amlogic-remote-1"; customcode = <0xfb04>; REMOTE_KEY(0x01,158) REMOTE_KEY(0x48,102)>;

right here they give it like this:

keymap = <REMOTE_KEY(0x09,115)>

I would like to set like 10 buttons....

Is it then like this?

keymap = <1st_KEY(0x09,115); 2nd_KEY(0x09,115;>

[01520717]

01520717 : I used AML Tools 6.0.0 and with them it was possible to open DTB. There are 2 DTBs inside.

Remote.cfg does have factory code but all I can see is customcode. Is it the same?

Then..in which order is keymap filled??? I mean in remote I guess you could "declare" what happens when pressing key. In those dtbs its like

....but no information what this shall do, understand?

Remote.cfg is like this:

The information in remote.conf is basically the same as a remote custom_map in the device tree.
- customcode in the device tree is the same as the factory code in remote.conf
- the keymaps in the device tree are scancodes and keycodes, e.g.

keymap = 0xc000b 0x540002 0x160003 0x150004
first entry scancode=0xc (this is actually a 16-bit hex code but leading zeros can be omitted), keycode=0x000b (the 0 key on the remote)
second entry scancode=0x54, keycode=0x0002 (the 1 key)
etc.
If you see a keymap entry something like 0x1, this means scancode=0x0000, keycode=0x0001 (the 2 key)

This link gives some background info on how to do this and also shows the keycode table. They use a REMOTE_KEY macro that converts something like REMOTE_KEY(0x01,0x02) to 0x10002.

[soldiaz]

You are confused? :-P

seems like yes factory_code=custom_code

• # factory_code each device has it's unique factory code.
• # pattern: custom_code(16bit) + index_code(16bit)
• # examble: 0xff000001 = 0xff00(custom_code) + 0001(index_code)

https://forum.libreelec.tv/thread/3581-create-remote-conf-from-scratch/

Guess we supposed to open special remote thread, you want to contribute? :-P

[sagert]

factory_code=custom_code.Although i already confused.

[sagert]

Sorry, didnt understand

In the custom code line ,you need to write something in the factory code 0?fe01 line.Then the console should be determined by the prefix.