[ROM] S905x Android 7.1 regular - pretty responsive - just 690MB - need help finalising

[soldiaz]

Dear folks I grabbed a pretty nice rom from Nexbox which was very fast. I debloated and removed further stuff, then changed some thing.

Now I need contribution...

Remote does not work.

There were 2 files in system\etc

remote_mouse1.tab
remote_mouse2.tab

No further remote.conf....

What I tried so far:
opened remote.conf and copied out factory_code and pasted it into remote_mouse1.tab where there was custom_code set.

Additionaly I pasted original remote.conf to system\etc

Does not work...

Then I removed nexbox launcher and launcher 2 from rom. Added new one but it says launcher crashed @startup...

RedPoison runs with that box I try to flash regular Android on.

So maybe regarding the remote it depends on bootloader? May I just coy over Poison's bootloader and repack?

Someone kindly can bring light into dark?

[minixfreak]

Won't work it's hard coded into dtb .. plus remote.cfg in bin folder would be different ... So yea that's why I didn't use as a base but I have a 1gb version of poisonatv ... and very fast as well abandon this firmware

[soldiaz]

Did you try in this? Is really dam fast....possible to backup poison bootloader and change bootloader??

[soldiaz]

OK, what I tried so far..

1. Extracted uboot and bootloader from Poison cause box works with Poison fw.

2. saved uboot and bootloader

3. Unpack fw with non-working remote

4. Copied over saved uboot / bootloader

5. Repack/flash

6. Device boots up..but remote still not working..

[soldiaz]

I tried several scenarios...not working....

Anyone can assist in linking system? I guess that is the issue. Even copying over system does not work....

[soldiaz]

I just unpacked an OREO image and there was dtb1 inside. I opened it and found this:

rc@c8100580 {
compatible = "amlogic, aml_remote";
dev_name = "meson-remote";
reg = <0x0 0xc8100580 0x0 0x44 0x0 0xc8100480 0x0 0x20>;
status = "okay";
protocol = <0x1>;
interrupts = <0x0 0xc4 0x1>;
pinctrl-names = "default";
pinctrl-0 = <0x21>;
map = <0x22>;
max_frame_time = <0xc8>;
};

custom_maps {
mapnum = <0x3>;
map0 = <0x23>;
map1 = <0x24>;
map2 = <0x25>;
linux,phandle = <0x22>;
phandle = <0x22>;

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 0x39000a 0x58001c 0x44000e 0x510074 0x4d0071 0x260067 0x28006c 0x250069 0x27006a 0x1b009e 0x49008b 0xd001c 0x4e0073 0x560072 0x530066 0x9018e 0x11018f 0x540190 0x4f0191 0xbd00a5 0xbb00a3 0x520088>;
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 0x15008b 0x16000f 0xc0192 0xd0193 0xe0073 0xf0072 0x110066 0x1c006a 0x1b0069 0x190067 0x1a006c 0x1d001c 0x170071 0x4900db 0x43009e 0x1201d5 0x1401d6 0x1801d7 0x590166 0x5a00a6 0x100074 0x4200a5 0x4400a3 0x1e00a8 0x4b00d0 0x5800a4 0x460082 0x400083 0x380046 0x5701d0 0x5b01d1 0x54018e 0x4c018f 0x4e0190 0x550191 0x5300ed 0x5200ee 0x3900d4 0x4100d5 0xb00d6 0xd8 0x1300d9>;
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 0x890083 0x9c0082 0x9a0078 0xcd0079>;
linux,phandle = <0x25>;
phandle = <0x25>;
};

Someone knows how to manage this?