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

[soldiaz]

Those codes that are in the new from the old.

Sorry, didnt understand

[soldiaz]

No, there was no VENDOR directory...

[bigthinks]

Sorry for asking again...

I have unpacked several DTB now....

A. OREO (8.0.0)lewy DTB (1 inside): no remote.conf, customcode, keymap in DTB
B. Poison (7.1.2) DTB (2 inside): remote.conf, no customcode, no keymap in DTB

This is old remote.conf:



This is OREO DTB:



In OREO there is no factory_code, instead customcode? Is this equal?

Old remote.conf has factory_code and assigns values to keys: 0x44 266 #SHORTCUT_AUDIO

How do I continue? like this?

map_1 {
mapname = "amlogic-remote-2";
customcode = <0xfe010000>;
release_delay = <0x50>;
size = <0x35>;
keymap = <0x10002 0x20003 0x30004 0x40005 0x50006 0x60007 0x70008 0x80009 0x9000a 0xa000b 0x1f01d2 >;
linux,phandle = <0x24>;
phandle = <0x24>;
};

Tried to make it clear with colors...

Did you replace /vendor/etc remote.conf in OREO rom by your remote.conf?

[sagert]

Cant edit prior post...



Or just paste the values from old remote?

keymap= <0x08 0x11 0x4c> ? ....

Those codes that are in the new from the old.

[soldiaz]

Cant edit prior post...

0x11 102 #HOME
0x19 158 #EXIT
0x4c 125 #SETUP(MENU)
0x40 116 #ON/OFF
0x18 115 #VOL+
0x10 114 #VOL-
0x4e 2 #1
0x0d 3 #2
0x0c 4 #3
0x4a 5 #4
0x09 6 #5
0x08 7 #6

Or just paste the values from old remote?

keymap= <0x08 0x11 0x4c> ? ....

[soldiaz]

Sorry for asking again...

I have unpacked several DTB now....

A. OREO (8.0.0)lewy DTB (1 inside): no remote.conf, customcode, keymap in DTB
B. Poison (7.1.2) DTB (2 inside): remote.conf, no customcode, no keymap in DTB

This is old remote.conf:

#amlogic NEC remote
factory_code = 0xfe010000
work_mode = 0
repeat_enable = 1
repeat_delay = 40
repeat_peroid = 39
release_delay = 121
debug_enable = 1

fn_key_scancode = 0x00
left_key_scancode = 0x51
right_key_scancode = 0x50
up_key_scancode = 0x16
down_key_scancode = 0x1a
ok_key_scancode = 0x13

mouse_begin
0 0x51 //mouse key left
1 0x50 //mouse key right
2 0x16 //mouse key up
3 0x1a //mouse key down
mouse_end
key_begin
0x11 102 #HOME
0x19 158 #EXIT
0x4c 125 #SETUP(MENU)
0x40 116 #ON/OFF
0x18 115 #VOL+
0x10 114 #VOL-
0x4e 2 #1
0x0d 3 #2
0x0c 4 #3
0x4a 5 #4
0x09 6 #5
0x08 7 #6
0x46 8 #7
0x05 9 #8
0x44 266 #SHORTCUT_AUDIO
0x0f 255 #MAIN_MENU f7
0x12 269 # F9
key_end

This is OREO DTB:

map_0 {
mapname = "amlogic-remote-1";
customcode = <0x7f80>;
release_delay = <0x50>;
debug_enable = <0x1>;
fn_key_scancode = <0x52>;
fn_key_scancode_other = <0x5b>;
cursor_left_scancode = <0x25>;
cursor_right_scancode = <0x27>;
cursor_up_scancode = <0x26>;
cursor_down_scancode = <0x28>;
cursor_ok_scancode = <0xd>;
size = <0x1f>;
keymap = <0x30000b 0x310002 0x320003 0x330004 0x340005 0x350006 0x360007 0x370008 0x380009 >;
linux,phandle = <0x23>;
phandle = <0x23>;
};

map_1 {
mapname = "amlogic-remote-2";
customcode = <0xfe01>;
release_delay = <0x50>;
size = <0x35>;
keymap = <0x10002 0x20003 0x30004 0x40005 0x50006 0x60007 0x70008 0x80009 0x9000a 0xa000b 0x1f01d2 >;
linux,phandle = <0x24>;
phandle = <0x24>;
};

map_2 {
mapname = "amlogic-remote-3";
customcode = <0xbd02>;
release_delay = <0x50>;
size = <0x11>;
keymap = <0xca0067 0xd2006c 0x990069 0xc1006a 0xce0061 0x450074 0xc50085 0x800071 0xd0000f 0xd6007d 0x950066 0xdd0068 0x8c006d >;
linux,phandle = <0x25>;
phandle = <0x25>;
};

In OREO there is no factory_code, instead customcode? Is this equal?

Old remote.conf has factory_code and assigns values to keys: 0x44 266 #SHORTCUT_AUDIO

How do I continue? like this?

map_1 {
mapname = "amlogic-remote-2";
customcode = <0xfe010000>;
release_delay = <0x50>;
size = <0x35>;
keymap = <0x10002 0x20003 0x30004 0x40005 0x50006 0x60007 0x70008 0x80009 0x9000a 0xa000b 0x1f01d2 >;
linux,phandle = <0x24>;
phandle = <0x24>;
};

Tried to make it clear with colors...

[sagert]

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:

Edit this file.Select values from your remote.conf from the old version.

[neomode]

When you press a Key on IR Remote it will be received as Code for example 0x40 116
In remote.cfg you put that code and what should happen.

That's all.

[soldiaz]

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

keymap = 0xc000b 0x540002 0x160003 0x150004

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

Remote.cfg is like this:

down_key_scancode = 0x1a
ok_key_scancode = 0x13

mouse_begin
0 0x51 //mouse key left
1 0x50 //mouse key right
2 0x16 //mouse key up
3 0x1a //mouse key down
mouse_end
key_begin
0x11 102 #HOME
0x19 158 #EXIT
0x4c 125 #SETUP(MENU)
0x40 116 #ON/OFF
0x18 115 #VOL+
0x10 114 #VOL-
0x16 103 #UP
0x51 105 #LEFT
0x13 97 #DPAD_CENTER

[sagert]

Ahhh thanks!

Then I place in vendor\etc...and try...

System UI crashes as well....any idea?

And what about launchers? May I remove them in AML tools and add new one? I experienced issues in another rom. There are 2 launchers.....

Is launcher being recognized automaticallly? Or do I have to "set" anywhere if replaced within AML tools?

It is necessary to prescribe and establish the root rights.

[soldiaz]

Ahhh thanks!

Then I place in vendor\etc...and try...

System UI crashes as well....any idea?

And what about launchers? May I remove them in AML tools and add new one? I experienced issues in another rom. There are 2 launchers.....

Is launcher being recognized automaticallly? Or do I have to "set" anywhere if replaced within AML tools?

[sagert]

I know...but it is BGA chip....

Hope there wil be a build for 1GB S905x :-P

I will make for android 8.1 v29 vanila.It can be suitable for boxing with 1 gb.I think you do not have enough memory for android 9.0 .You need to change in /vendor/etc remote.conf only there it is called differently.The bluetooth can be frozen by any program.For example Root Uninstaller.

[soldiaz]

Alright, I tried the 1GB OREO mod MiniM8S_Oreo_8.0.0_By_Levy_1Gb_mod.img ...and it is pretty impressive!!!

cons:

- remote seems to be recognized but power button not working and other buttons too. Where is the remote .conf? Couldnt find it in system\etc

- SystemUI keeps stopping, Bluetooth keeps stopping

Overall it is not that slow!!!

How can I get remote working? In cause of apps keep stopping maybe I remove BT...

[soldiaz]

I know...but it is BGA chip....

Hope there wil be a build for 1GB S905x :-P

[sagert]

Today came the next build phhusson.I made them for android 9.0 .And now it seems to me better in v 111 than in v110.Also came out v29 for android 8.1 .I'll post it later on github.