ATV9-MOD-(P212)AMPERE-V3

[firmtech]

Ok successful flash of this Rom. Got SSH working, still not joy with remote. Took my original remote.conf and copied to /vendor/etc/remote.cfg still only up and down buttons working. Then I copied remote.conf to /vendor/etc/remote1.tab still only up and down working. I'm probably doing something wrong. Here is my original remote.conf. Any help would be great. Thanks! Nice ROM!


#************************************************* ************************************************** ******
#this file is configuration for each factory remote device
# work_mode 0 :software 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 = 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
pageup_key_scancode = 0x55
pagedown_key_scancode = 0x54

mouse_begin
0 0x51
1 0x50
2 0x16
3 0x1a
mouse_end

key_begin
0x01 11
0x4e 2
0x0d 3
0x0c 4
0x4a 5
0x09 6
0x08 7
0x46 8
0x05 9
0x04 10
0x13 97
0x19 15
0x42 14
0x16 103
0x1a 108
0x51 105
0x50 106
0x18 102
0x11 104
0x4c 109
0x10 125
0x5a 119
0x59 122
0x52 128
0x58 123
0x54 120
0x55 121
0x40 116
0x41 113
0x45 130
0x49 134
0x0a 133
0x48 138
0x4d 70
0x0e 136
0x0f 186
0x43 183
0x03 127
0x06 139
0x44 140
0x00 63
0x02 395
key_end
repeat_key_begin
0x01 11
0x4e 2
0x0d 3
0x0c 4
0x4a 5
0x09 6
0x08 7
0x46 8
0x05 9
0x04 10
0x13 97
0x19 15
0x42 14
0x16 103
0x1a 108
0x51 105
0x50 106
0x18 102
0x11 104
0x4c 109
0x10 125
0x5a 119
0x59 122
0x52 128
0x58 123
0x54 120
0x55 121
0x40 116
0x41 113
0x45 130
0x49 134
0x0a 133
0x48 138
0x4d 70
0x0e 136
0x0f 186
0x43 183
0x03 127
0x06 139
0x44 140
0x00 63
0x02 395
repeat_key_end

[hannah]

replace the vendor partition
repack the aml_package _ *. img and try again

edit: or update via vecovery: vendor.zip

Hello, I now have updated the vendor.PARTITION and can confirm that Wifi is NOT working.

Work Done:
- My TV Box: Nexbox A95X 2GB/16GB S905X WIFI AP6330
- Unpack Level 1
- copied updated vendor.PARTITION
- repack
- Burn with USB Burning Tool and it was a success

Attached is the combined diagnostic output of following commands

C:\opt\adb>adb connect 192.168.0.101:5555
C:\opt\adb>adb root
C:\opt\adb>adb shell dmesg > dmesg1
C:\opt\adb>adb shell lsmod >> dmesg1
C:\opt\adb>

[bumerc]

ok guys, thanks for the tests, tomorrow will continue..

[hannah]

ok guys, thanks for the tests, tomorrow will continue..

Your effort is highly appreciated.

[sagert]

I have ddr3 2gb 16gb.I have not bought a uart adapter yet.

[bumerc]

sagert
how does your device behave with working Frinware, does it slow down over time? What is the CPU temperature? The maximum clock frequency of your RAM memory is 800Mhz, I have set u-boot to 792Mhz for DDR3.
Did you test the FE with a new kernel?

[bumerc]

hannah
Your WiFi chip will now be recognized properly, but there is still a problem with the FW, I will check the new changes more closely

firmtech
use remote.tab files, if you've created a working remote.tab, post it here, I'll add it to the next build

[hannah]

hannah
Your WiFi chip will now be recognized properly, but there is still a problem with the FW, I will check the new changes more closely

Appreciate your effort and shall wait patiently.

[sagert]

sagert
how does your device behave with working Frinware, does it slow down over time? What is the CPU temperature? The maximum clock frequency of your RAM memory is 800Mhz, I have set u-boot to 792Mhz for DDR3.
Did you test the FE with a new kernel?

I'm on Android 10 now. this is the port from Phhusson and daivietpda.Android 10 is faster for Android 9 and it does not slow down.Of course you need to finish it a little.I will test your firmware a little later.

[dsm150]

hannah
Your WiFi chip will now be recognized properly, but there is still a problem with the FW, I will check the new changes more closely

Do I need to try flashing the device? I have exactly the same nexbox as hannah

[freakbox]

I'm on Android 10 now. this is the port from Phhusson and daivietpda.Android 10 is faster for Android 9 and it does not slow down.Of course you need to finish it a little.I will test your firmware a little later.

can you send me a link please?

[firmtech]

Still no luck with remote. I tried all combinations renaming my original remote.conf to remote.tab, remote1.tab via ssh using mount -o rw,remount /vendor first. I am seeing this when I press the right remote button (this is a button that is not working) in the terminal window.

[ 671.611492@1] meson-remote c8100580.rc: scancode 80 undefined
[ 671.611599@1] meson-remote c8100580.rc: no valid key to handle

Buttons that work, even though some are mapped wrong have no output in terminal.
HDMI CEC works great with Samsung TV so remote is not a huge issue.
Pic of remote attached if someone is familiar with it.

[sagert]

can you send me a link please?

Here on the site there is an Android Q theme for amlogic s905x.

[bumerc]

Still no luck with remote. I tried all combinations renaming my original remote.conf to remote.tab, remote1.tab via ssh using mount -o rw,remount /vendor first. I am seeing this when I press the right remote button (this is a button that is not working) in the terminal window.

[ 671.611492@1] meson-remote c8100580.rc: scancode 80 undefined
[ 671.611599@1] meson-remote c8100580.rc: no valid key to handle

Buttons that work, even though some are mapped wrong have no output in terminal.
HDMI CEC works great with Samsung TV so remote is not a huge issue.
Pic of remote attached if someone is familiar with it.

activate debugging in your remote.cfg file

debug_enable 1

start the SSH session, press the buttons of your remote control one by one and then enter the command

dmesg -c

note the codes of each button. Also write a comment on each key code, which key it belongs to, post this note here

[alex161rus]

factory_code = 0xfe010001

need to check.

changed. Most buttons should work