ATV9-MOD-(P212)AMPERE-V3

[superceleron]

I can’t say anything about khadas sdk since I don’t use it, but in other amlogic sdk compilation with the multiwifi option also works great in both versions

Ye typically it always works fine, dunno really what is wrong with their sdk from where they got it, i believe it's directly from amlogic but maybe a dev one?!? who knows...

[bumerc]

I can’t say anything about khadas sdk since I don’t use it, but in other amlogic sdk compilation with the multiwifi option also works great in both versions

[superceleron]

This is not only the case with VIM1 sdk, but generally with amlogic pie sdk, but only if you compile it with atv = true suffix, in this or that case multiwifi is set by default, both in yours and in other builds

Yes Khadas sdk have some issues, i fixed lots the issues like the multiwifi.
Now it compiles fine in ATV mode or regular with multiwifi enabled and i also added some missing modules source to the mix

[bumerc]

This is not only the case with VIM1 sdk, but generally with amlogic pie sdk, but only if you compile it with atv = true suffix, in this or that case multiwifi is set by default, both in yours and in other builds

[superceleron]

superceleron
With Bluetooth there are no problems, with WiFi apparently only with ap6330, but this was not part of your build. I have now built a new build for ap6330 devices and sent it to the guys and wait for the test results

Ye i know i forgot to make it multiwifi, since multiwifi in khadas sdk is broken but i fixed it my internal sdk.
But ye... since i made this for VIM1 i only did it with 1 wifi chip support...
Anyway if you guys want i will then post here the other one, i think is way better than that one.
Is a pity i can't share this ATV10, since i made mutiwifi and multibt

[bumerc]

superceleron
With Bluetooth there are no problems, with WiFi apparently only with ap6330, but this was not part of your build. I have now built a new build for ap6330 devices and sent it to the guys and wait for the test results

Regarding multiwifi support, this is actually not so good with an ATV build, WiFi drivers and FW have to be started with additional entries in *.rc files. This problem does not occur with a normal build (not ATV)

[superceleron]

i see to many problems with wifi and bt drivers... hmm i did a "generic" android 9 build for the s905x a while ago (like 3 or 4 months ago) but never rls it.... (not in the mood.... lol)
I think that build was better for you guys to work on, since the multi-wifi support is way better on that one also i use a more generic DT... same for uboot.
Also is a another private SDK and not khadas based.
I also have a ATV10 for s905x build i did but that one i can't share it unfortunately
Once i have a bit more time i will leave the A9 build here.

[alex161rus]

factory_code = 0xfe010001

need to check.

changed. Most buttons should work

[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

[sagert]

can you send me a link please?

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

[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.

[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?

[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

[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.

[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.