Posts by Nofan Tasi

    The is no gxbb_p200_1G_mxq_pro_4k.dtb for 7.0.2.008, so I thought I'd have a better chance of success with a tree that has been labelled for that particular device. What is the equivalent for mxq_pro_4k at version 7.0.2.008?

    7.0.2.008 might very well work with 7.0.2.007 gxbb_p200_1G_mxq_pro_4k.dtb
    Equivalent at version 7.0.2.008, I would guess one of
    gxbb_p200_1G_100M.dtb
    gxbb_p200_1G_100M_RealtekWiFi.dtb
    gxbb_p200_1G_1Gbit.dtb
    gxbb_p200_1G_1Gbit_RealtekWiFi.dtb
    depending on if you have 100M or 1G ethernet, and, depending on if you have RealtekWiFi or not.


    HI,

    I try LE on a NexBox MXQPRO 4k.
    I put the last dev on SD and gxbb_p200_1G_100M.dtb from 008 (as dtb.img of course).
    LE boots correctly but after a while of streaming a french tv replay (20 min or very quickly) KODI freeze with continuous sound or just black screen.
    I also tried 007, 008, realtek dtb... and others and same result.

    Thanks

    I wonder if it could help to have, say, 2GB swap space partition on SD.


    I think this may be due to increased coherent_pool_size. I have re-uploaded .008 with that change reverted. Yes, source code is uploaded to my GitHub, links in the first post.

    Thanks for looking into this. I am not sure I figure out what you mean by coherent_pool_size increase.
    I notice linux-48d3a2f and media_build-6931070 use smp_mb__after_clear_bit and smp_mb__after_atomic respectively in dvb_usb_core.c.
    Such seems to correspond to the symbol mismatch.
    note: (not sure if it matters)
    projects/S905/patches/media_build/media_build-fix.patch
    seems to have commented out
    #define smp_mb__after_atomic smp_mb__after_clear_bit

    Thanks for releasing 7.0.2.008 on my birthday :)

    I want to report a kernel module symbol issue
    [ 15.729319@2] dvb_usb_v2: Unknown symbol smp_mb__after_atomic (err 0)
    as a consequence, my USB DVB-T no longer works.

    I hope this can be fixed easily.
    Is your git repository up to date? Then I can try to fix it myself as well.

    have a nice day

    yes aqnd im asking if i have the correct files and no one as said anything all im asking for is some guidance so i dont brick my device

    You should not brick your device if you follow the procedure to boot and run LE from external SD.
    Depending on how much RAM and how fast your Eth is you should choose between
    gxbb_p200_1G_100M.dtb
    gxbb_p200_1G_1Gbit.dtb
    gxbb_p200_2G_100M.dtb
    gxbb_p200_2G_1Gbit.dtb
    There are also RealtekWiFi variants if that's your WiFi chip.

    Success


    So managed to get to the end of my manic MXQ PRO 4k Clone journey.

    Congratulations and thanks for story.
    And yes, flashing using USB tool can be daunting. I remember once doing it and trying various orders of plugging in/out USB/power cables and pushing/releasing reset button (on another type of MXQ PRO 4k Clone). In fact I forgot the right order.
    [hr]


    You just never know, you might want Android in the future, for apps like skype?

    Skype? Does your device have a microphone and a camera?

    I ask here on behalf of someone else:

    Does anyone have 7.0.2.007 (or previous) build for S905 working on 'NEXBOX MXQ Pro',
    and, if so, using which dtb.img?

    Here are some relevant details kindly gathered and provided by owner:
    (note that build.prop fingerprint does not mention p200 or p201)...

    In case of no match I also asked for original dtb.img

    build.prop:

    Code
    ro.build.fingerprint=Android/mxqpro_nexbox/mxqpro_nexbox:5.1.1/MXQ-Pro-NEXBOX/20160309:userdebug/test-keys
    ro.product.model=Mxq-Pro-NEXBOX
    ro.board.platform=gxbaby

    chipsets:

    Code
    LAN: H1102NL - 1610
    RAM: SKhynix HSTQ4G63 AFA RDC 516A
    AV/SPDIF: MXT8234 158
    FLASH: San Disk x428107001 sdinrgama - 008G WB20160220 Taiwan
    WIFI: 8189ETV (RTL Realtek) G2033G2 GG07
    SD: GL850G (Genesys USB controller)

    For all clarity, I do not have a SPDIF capable audio system.
    Instead, I have a 'SPDIF to 3.5" jack' converter and I plug the jack end into the 'UE Boom 2' loudspeaker.
    This gives nice audio in Android but, somehow, not in 006-007 LibreELEC.
    It did work nicely in 005 LibreELEC.
    maybe some settings need to be adjusted (I tried some of course).
    Still very much at your disposal for testing/troubleshooting.

    UPDATE

    Believe it or not, but now SPDIF suddenly works !
    I wish I could tell why. I tried so many things...
    For one thing the audio output is ALSA:AML-M8AUDIO,HDMI now.

    I can say, I did toothpick boot another time, reboot several times, even turned on/off audio and debug log and also un-paired re-paired 'UE Boom 2' loudspeaker bluetooth. So not sure what exactly did the trick.
    In any case : sooooo happy now