S905x support, what is needed?

    Quote from bumperboy


    DTS-HD Master Audio Passthrough: Yes

    My receiver shows only DTS not DTS-HD-MA .. ? So this is because it's no dolby licensed S905X?
    So this cannot work simply? Or do I have to set something else? Everything is marked in audio settings (DTS-HD capable receiver and so on).

    For the brave ones who want to try installing my builds onto the NAND, this might come handy: index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)

    Please be aware, that this TWRP recovery image is rather hacked together (LibreELEC). I have tested the backup feature which seems to produce correct archives but I did not actually try to restore such a backup. It could potentially have issues due to SELinux-Foo. Unlikely, but possible.

    Edit: just tested backup & recovery on my A95X, works fine.

    Edited once, last by pulsar (August 25, 2016 at 5:53 PM).

    Quote from lama0900

    Works for me :)
    Even power off works with this one


    Still not working with mine (Nexbox A95X). But with different error screen, please see Imgur: The most awesome images on the Internet



    [hr]

    Quote from pulsar


    For the brave ones who want to try installing my builds onto the NAND, this might come handy: index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)

    Please be aware, that this TWRP recovery image is rather hacked together (LibreELEC). I have tested the backup feature which seems to produce correct archives but I did not actually try to restore such a backup. It could potentially have issues due to SELinux-Foo. Unlikely, but possible.


    Do I have to flash this TWRP with flashing tool? Or just write image file to sd card and boot from it?

    This is just for backing up android stock firmware for recovery in case of bricking it, right?

    Edited once, last by pawnthep (August 25, 2016 at 3:06 PM).

    Quote from pawnthep

    Do I have to flash this TWRP with flashing tool? Or just write image file to sd card and boot from it?

    This is just for backing up android stock firmware for recovery in case of bricking it, right?

    Rename it to recovery.img, put into the root of a fat32 formatted sd card and reboot with the "av button" pressed.

    Quote from lama0900

    I did not use toothpick again? Is that important? I used toothpick method only once with pulsars image, then dd'd kszaq's image to my sdcard, put it in again and waited to boot again which my box did well.

    My box doesn't has reset button in AV port, so toothpick method is not an option for me.

    But it boots directly from sd card either with Pulsar or kszaq build. Only Pulsar build is working though.

    Just installed my build on my A95X's NAND flash - working great. Did also test power off and power on via IR remote control, no issues here. So it appears to be safe (at least on the A95X) to install that build on the NAND flash.
    [hr]
    kszaq

    LibreELEC-S905.aarch64-7.0-devel-20160825131726-r23297-g5b935ef from SD is working fine on A95X / S905X

    Edited once, last by pulsar (August 25, 2016 at 4:23 PM).

    Quote from kszaq


    3rd test build: s905x-test3

    Tested on Tanix TX5 Pro Amlogic s905x/2GB RAM/16GB eMMC/Ampak AP6255 module for WiFi 802.11 b/g/n/ac and Bluetooth 4.0 LE connectivity

    From SD card it works normaly (From both USB ports hungs and complain about tty...)
    !!! Be patient, first boot after SDCard preparation is 2-3 min !!!

    Here is my findings on this build

    remote - Works normaly (power on and power off of device also work),
    WiFi 2.4 GHz - do not work,
    WiFi 5 GHz - do not work
    Bluetooth do not work,
    Ethernet - works normaly
    USB both ports - works normaly,
    SSH login - works normaly

    PlayBack
    1080p all tested movies Auto refresh rate works normaly
    h265, h264 works normaly
    dont have 4k tv for testing 4k contents


    Is there any possibility to use AP6255 modules from android stock rom ?
    Attached is all BCM roms currently not present in test build

    Great work!
    Big thanks for the build!

    Edited once, last by pm_mickey (August 25, 2016 at 5:32 PM).

    Quote from pulsar

    internal NAND flash (dev/system, /dev/data), eMMC would be SD Card, right?

    No, eMMC is chip on the board that is hooked up to the second MMC controller on the SoC. The 'e' stands for 'embedded'. Have a look at dmesg:

    Code
    m8s:~ # dmesg | grep -i mmcblk[    3.651653@3] mmcblk0: sd:b368 USD   3.75 GiB [    3.770124@1]  mmcblk0: p1 p2[    4.123791@0] mmcblk1: emmc:0001 NCard  7.21 GiB [    4.123918@0] mmcblk1boot0: emmc:0001 NCard  partition 1 4.00 MiB[    4.124046@0] mmcblk1boot1: emmc:0001 NCard  partition 2 4.00 MiB[    4.124162@0] mmcblk1rpmb: emmc:0001 NCard  partition 3 4.00 MiB[    4.193833@0]  mmcblk1: unknown partition table[    4.194948@0] [mmcblk1p01]           bootloader  offset 0x000000000000, size 0x000000400000 [    4.195293@0] [mmcblk1p02]             reserved  offset 0x000002400000, size 0x000004000000 [    4.195466@0] [mmcblk1p03]                cache  offset 0x000006c00000, size 0x000020000000 [    4.195622@0] [mmcblk1p04]                  env  offset 0x000027400000, size 0x000000800000 [    4.195771@0] [mmcblk1p05]                 logo  offset 0x000028400000, size 0x000002000000 [    4.195936@0] [mmcblk1p06]             recovery  offset 0x00002ac00000, size 0x000002000000 [    4.196089@0] [mmcblk1p07]                  rsv  offset 0x00002d400000, size 0x000000800000 [    4.196251@0] [mmcblk1p08]                  tee  offset 0x00002e400000, size 0x000000800000 [    4.196414@0] [mmcblk1p09]                crypt  offset 0x00002f400000, size 0x000002000000 [    4.196571@0] [mmcblk1p10]                 misc  offset 0x000031c00000, size 0x000002000000 [    4.196826@0] [mmcblk1p11]            instaboot  offset 0x000034400000, size 0x000020000000 [    4.197006@0] [mmcblk1p12]                 boot  offset 0x000054c00000, size 0x000002000000 [    4.197165@0] [mmcblk1p13]               system  offset 0x000057400000, size 0x000040000000 [    4.197320@0] [mmcblk1p14]                 data  offset 0x000097c00000, size 0x000136500000

    The microSD card in the slot is 4GB, the eMMC 8GB. I suspect /dev/system and /dev/data are android-isms that are just link to paritition 13 and 14 on the emmc.

    Of course both the microSD card and eMMC are created using NAND flash, but in general saying 'NAND flash' means using it without a translation layer through /dev/mtd*

    I am fighting NAND flash on a different board today and wondered if I needed go through the same frustrating experience with the s905x box :/

    EDIT: dmesg with linebreaks

    Edited once, last by koenkooi (August 25, 2016 at 6:41 PM).

    Quote from koenkooi

    No, eMMC is chip on the board that is hooked up to the second MMC controller on the SoC. The 'e' stands for 'embedded'. Have a look at dmesg:

    The microSD card in the slot is 4GB, the eMMC 8GB. I suspect /dev/system and /dev/data are android-isms that are just link to paritition 13 and 14 on the emmc.

    Of course both the microSD card and eMMC are created using NAND flash, but in general saying 'NAND flash' means using it without a translation layer through /dev/mtd*

    I am fighting NAND flash on a different board today and wondered if I needed go through the same frustrating experience with the s905x box :/

    EDIT: dmesg with linebreaks

    Ah, makes sense now. eMMC then

    Edited once, last by pulsar (August 25, 2016 at 6:56 PM).

    Quote from lama0900

    My receiver shows only DTS not DTS-HD-MA .. ? So this is because it's no dolby licensed S905X?
    So this cannot work simply? Or do I have to set something else? Everything is marked in audio settings (DTS-HD capable receiver and so on).

    I double checked and it shows DTS-HD MA. I was using a different bluray and it showed DTS only so I picked up The Avengers: Age of Ultron and DTS-HD MA was displayed.

    Although it works well with the HD audio, it seems SD audio is not working at all. I tried with a normal rip with AAC audio and nothing was coming out of the speakers. Disabled the passthrough option and still nothing. Did a reset at the audio settings and SD audio started working perfectly.

    Anyone else has the same issue?

    Quote from pawnthep

    My box doesn't has reset button in AV port, so toothpick method is not an option for me.

    But it boots directly from sd card either with Pulsar or kszaq build. Only Pulsar build is working though.

    I think pulsar mentioned somewhere else a quick&dirt workaround for the missing recovery switch: assuming you have a working android running, put a fakeupdate.zip file (empty file is ok) on sdcard, then launch the UPDATE app. The update app will issue a reboot with "update" as argument. Then u-boot will parse reboot arg, for "update" (and for "cold_boot") it will run recovery.img or aml_autoscript. But, you should already have done it at least one time, to launch kszaq image first time, or did you used another method?

    Btw for backup all partitions, i just used the RootBrowser app already installed by nexbox, can't read /dev/block but can read /dev/block/platform/d0074000.emmc/

    Quote from Geremia

    I think pulsar mentioned somewhere else a quick&dirt workaround for the missing recovery switch: assuming you have a working android running, put a fakeupdate.zip file (empty file is ok) on sdcard, then launch the UPDATE app. The update app will issue a reboot with "update" as argument. Then u-boot will parse reboot arg, for "update" (and for "cold_boot") it will run recovery.img or aml_autoscript. But, you should already have done it at least one time, to launch kszaq image first time, or did you used another method?

    Btw for backup all partitions, i just used the RootBrowser app already installed by nexbox, can't read /dev/block but can read /dev/block/platform/d0074000.emmc/

    You're right. I did update with fakeupdate.zip file to try install kazaq's build (7.0.2.006) but with no success. After that I can succeed with Pulsar build. And now with NAND installed as well.


    [hr]

    Quote from pulsar


    Just installed my build on my A95X's NAND flash - working great. Did also test power off and power on via IR remote control, no issues here. So it appears to be safe (at least on the A95X) to install that build on the NAND flash.

    It works for me too. (Nexbox A95X, 2/16 gb version)

    Just installed your build on NAND and it's working great. Booting speed is very good too.

    Thanks.

    Edited once, last by pawnthep (August 25, 2016 at 11:56 PM).