ATV9-MOD-(P212)AMPERE-V3

[firmtech]

I have a lot of buttons for daivietpda atv9 v6 firmware.Including right and left.My remote code is 0×fe01 .

The TX5 ROM on daivietpda?

[superceleron]

superceleron is your preinstalled Wallpaper a 4K image? Was having issues using alternative launchers with that Wallpaper, uninstalled it and the launchers worked fine now. So, was thinking maybe it was a 4k image and it conflicting with the standard UI resolution or framebuffer.

No its 1080p

[sagert]

Still no luck with this. Installed meson1.dtb, Installed the above file in vendor/etc. I had to reflash Redpoison back to the box so it would boot off sdcard to run coreelec and grab the remote codes. After getting the codes from coreelec i rebooted into redpioson. The remote works fine in that rom, so I grabbed the remote.conf from there it is factory_code 0x40400001 . Interestingly enough, I copied that remote.conf to remote1.tab after reflashing ampere, and still see the same results. Right, Left not working. Same output in terminal. Attached is the remote.conf in Redpoison rom. Something is still wrong.

[ 689.882275] meson-remote c8100580.rc: scancode 80 undefined
[ 689.882402] meson-remote c8100580.rc: no valid key to handle
[ 699.339118] meson-remote c8100580.rc: scancode 81 undefined
[ 699.339274] meson-remote c8100580.rc: no valid key to handle

I have a lot of buttons for daivietpda atv9 v6 firmware.Including right and left.My remote code is 0×fe01 .

[RiCkLaR_atvX]

superceleron is your preinstalled Wallpaper a 4K image? Was having issues using alternative launchers with that Wallpaper, uninstalled it and the launchers worked fine now. So, was thinking maybe it was a 4k image and it conflicting with the standard UI resolution or framebuffer.

[bumerc]

firmtech
You still don't know which factory (manufacturer) code you have and as I suspected you have the wrong remote.conf file. In another ROM it could also run via dtb, it does not necessarily have to be remote.conf with 40400001 manufacturer code. You have to look at the log from the other ROM or CE.

[firmtech]

firmtech
Replace the dtb again and copy remote1.tab to /vendor/etc/
meson1.dtb

Still no luck with this. Installed meson1.dtb, Installed the above file in vendor/etc. I had to reflash Redpoison back to the box so it would boot off sdcard to run coreelec and grab the remote codes. After getting the codes from coreelec i rebooted into redpioson. The remote works fine in that rom, so I grabbed the remote.conf from there it is factory_code 0x40400001 . Interestingly enough, I copied that remote.conf to remote1.tab after reflashing ampere, and still see the same results. Right, Left not working. Same output in terminal. Attached is the remote.conf in Redpoison rom. Something is still wrong.

[ 689.882275] meson-remote c8100580.rc: scancode 80 undefined
[ 689.882402] meson-remote c8100580.rc: no valid key to handle
[ 699.339118] meson-remote c8100580.rc: scancode 81 undefined
[ 699.339274] meson-remote c8100580.rc: no valid key to handle

[bumerc]

wesley123
There is a small bug in ssv6051 driver, I will fix it and compile a new IMG. In all three builds this wifi chip will not work without the tricky manipulations..

[bumerc]

firmtech
Replace the dtb again and copy remote1.tab to /vendor/etc/
meson1.dtb

[firmtech]

there is a way to check this. Install CoreElec on the SD card and create a new remote.cfg file, compare the key codes of this file with the original file

Ok, I got CoreElec up and running. I scanned all buttons, here are the results.

[bumerc]

there is a way to check this. Install CoreElec on the SD card and create a new remote.cfg file, compare the key codes of this file with the original file

[firmtech]

OK, everything is right.
Are you sure you have a correct remote.conf file? The remote control works for other users..

I'm pretty sure, the remote.conf was taken from the original stock rom. It was the only one in the /etc folder from a twrp backup, found it here system.ext4.win /etc folder. remote did work with the stock rom. I cannot find the original rom anywhere its a leelbox q1 plus.

[bumerc]

OK, everything is right.
Are you sure you have a correct remote.conf file? The remote control works for other users..

[firmtech]

show the dtb installation log

Copied file to sdcard, then...

login as: root
#################################
* * * * * * * * * * * * * * * * *
* Welcome to ampere SSH-server! *
* *
* * * * * * * * * * * * * * * * *
#################################
Authenticating with public key "imported-openssh-key"
Passphrase for key "imported-openssh-key":
:/vendor/etc/dropbear # dd if=/storage/C0E4-7E0C/meson1.dtb of=/dev/block/dtb bs=262144
0+1 records in
0+1 records out
174080 bytes transferred in 0.013 secs (13390769 bytes/sec)
:/vendor/etc/dropbear # reboot

[bumerc]

show the dtb installation log

[firmtech]

firmtech

download meson1.dtb
and install it..

SSH install(ccopy meson1.dtb to sdcard)


ADB install

reboot

Did not work, remote still working the same way it was. Thanks for your efforts. Here is output from SSH on right and left buttons of remote. File did install in SSH.

:/vendor/etc/dropbear # dmesg -c
[ 689.882275] meson-remote c8100580.rc: scancode 80 undefined
[ 689.882402] meson-remote c8100580.rc: no valid key to handle
:/vendor/etc/dropbear # dmesg -c
[ 699.339118] meson-remote c8100580.rc: scancode 81 undefined
[ 699.339274] meson-remote c8100580.rc: no valid key to handle