If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
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..
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
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.
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.
Last edited by RiCkLaR_atvX; 05-04-2020, 09:01.
Reason: typo
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 .
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.
firmtech
I tested your remote.tab config on my X96Mini test device, all the buttons worked perfectly You need to find out the correct factory_code for your remote control..
I have managed to flash V3 to my old Mecool M8S Pro+ 2/16GB
WiFi appears to be 9082xs chip and does not work. Tried available patches.
One USB port is functioning.
Remote control is not working.
i have trouble , i cannot download the ATV9-IMG-DEBUG-AMPERE-V3 img its google drive download always fail in half way, can please share it in mega ?
thanks in advance
bullghost
Your device is currently not supported, read the first post (SpecTek MLC Nand), I could build an extra build for this type of memory, but I won't start without a test device because the bootloader has to be reconfigured
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment