Posts by wrxtasy

    I think someone will probably develop another solution to get it onto the emmc.

    Worked fine after two passes for me and recovery using USB Burn tool makes it low risk.

    Shoog

    Until some Newbie ticks the "Force Erase All" or some other ungodly option and completely wipes HDCP keys from a dual boot MECOOL box or a more expensive MINIX U9. Those are not recoverable.

    It happens often and that is why it's not "low risk" for everyone.

    Using my Beelink MXIII II 2G/16G box running 8.2.2.3 build from a Class 10 SD card. Have recently got a new TV a LG Super UHD set and have set my KODI system to the UHD resolution 3840 x 2160 and all is well playing some 4K streamed content too.

    Why are you doing this ?

    All it does is heat up the GPU portion of the Chipset unnecessarily drawing 4K pixels onscreen. The user interface is likely slower as a result as well.

    AML 4K LE Kodi Krypton is designed to run at a 1080p Kodi user interface, so your 4K TV with it's superior 1080p > 4K picture upscaling hardware produces a sharper picture when viewing anything 1080p on a 4K TV.

    If Kodi refresh switching is set to Start/Stop any 4K content you watch will trigger an auto resolution switch from 1080p to 4K anyway for true 4K output.

    I removed it for a number of reasons, I will not be supporting this any more.

    I agree with this decision.

    Install to internal will no longer be supported when we get to official AMLogic LE Leia releases either.

    User need to use the much safer option of:


    [HOWTO] Boot from SD card, use internal memory for data

    DO NOT use the Android Low Level USB burning tool to flash alternate Android Firmware after copying the LE data partition to internal storage.

    A simple Android Update App - Firmware .zip file update is fine as it does not touch the Data partition.

    S912's cannot software decode even 720p Netflix streams and play them back smoothly because of the non optimal Hybrid Android/Linux GPU video drivers used. Hardware decoding of video is unaffected.

    Boxes like the MINIX U9, WeTek Play2 and certain MECOOL's can dual boot and run the easy to use Android TV Netflix App in 1080p with an unofficial Android TV ROM, because they have Widevine L1 and HDCP 1.x

    4K HDR high bitrate video streaming really needs a device with Gigabit Ethernet (1000M).

    If you can find a S905X with Gigabit you will cover all bases and avoid the possible Subtitles rending problem on the S912.

    Do not watch video with Subtitles or need 720p Netflix with Kodi Leia then get a S912 box with Gigabit Ethernet (1000M) such as a MINIX U9, Tanix TX92 & others.

    Non HDR - then an eMMC, Gigabit equipped ODROID C2 rules the roost - it's a bit faster than the S912 MINIX U9 especially when used with a Bluetooth Xiaomi minimal remote. Great combo. ;)

    It's a U-boot issue and there is nothing LibreELEC can do about it because none of these cheap Chinese sellers supplies U-boot source code.

    Best bet is to update the Android Firmware, which will update the U-boot code.

    Such Android Firmware updates for the M8S Pro+ are done using the inbuilt Android Update app for a local update using a OTA update.zip file (save to a USB stick) found over on the Freaktab website:

    Firmware - ROMs - Tools - FreakTab.com

    Remove the LE SD card first.

    Now another problem is that developers are dropping like flies for different reasons and there are very few people now working on the Amlogic project, kernel modification isn't particularly my strong point either.


    Given the Alpha status of Kodi Leia and these builds I would advise you to use kszaq 8.2 release which is very stable until things have matured a little more as it's very much 2 steps forward 1 step back at the moment with Leia builds.

    Gotta agree with GDPR-2 here.

    My quick and dirty patch was basically to get the new Kernel to compile so the 4:2:2 green screen video output bug could be tested.

    That and the S905X flickering/OLED bug is pretty much the only outstanding issue I could see with the old kszaq  johngalt Kernel. (excluding Play2 issues)

    Bug busted 4:2:2 output is needed because you cannot use 4:4:4 for 4K@50/60Hz which is outside of HDMI 2.0 specs.

    Sam Nazarko of Vero 4K fame who has some AML Kernel experience will very likely find the 4:2:2 bug and we can patch the old LE Kernel again and move forward.

    Those CPU Software upscalers will never usually be activated with AMLogic LE Kodi.

    You need decent Intel Iron to use Software upscaling.

    If you set a resolution of 2160p, AML hardware does the 1080p > 4K upscaling. But in my experience the picture on my 4K TV then appears a bit soft and dull. Leave the GUI at 1080p and let the 4K TV use it's superior upscaling hardware.

    There is simply no need to run the Kodi GUI at 2160p anything, all it does it heat up the Chipset necessarily. Plus your 4K TV will have better quality user interface 1080p > 4K picture upscaling vs pretty much any media player. Then to also really annoy you it causes black screen and HDMI issues.

    Set the Kodi GUI to 1080p60Hz or 50Hz and also set:

    in Kodi settings > Player > Video > Adjust display refresh rate > Start/stop

    Sync Playback to Display > Off

    If you play 2160p material AML LE Kodi will auto refresh AND 1080p <<<--->>> 2160p auto Resolution switch.

    Set and forget. ;)

    All 4K AML LE or OSMC Kodi Krypton media players operate the same.

    GDPR-2 you will be interested in these two patches if you are still running the old Linux Kernel:

    this ONE cleans up HDR picture artifacts that some users have with OLED TV's and S905X's (GXL)

    There was an in depth Vero 4K discussion about the S905X AML OLED combo flickering issue....

    HDR Slight flickering (Workaround available) - Vero 4K - OSMC Forums

    That above code is already in the new AML Linux Kernel which I'm using.

    and this ONE is trying to reduce color banding, again for S905X's, and the interesting discussion for that is....

    HDR Banding issue - Vero 4K - OSMC Forums

    You can see the S912's (GXM) have a greater number of bit depth dithering and rounding options.

    Another test release.

    This one fixes the Audio silence problem with the new Linux Kernel when you go from PCM Audio to Passthrough, back to PCM which then used to result in a total loss of audio output.

    Also reverted a small new Kernel change for h264 video decoding.

    As well as adding an option to turn off - AMLogic deinterlacing picture post processing completely.

    mule try doing a .tar update and see if there are any H264 improvements out of the box.

    If not go into Settings > Display > Disable AMLogic hardware deinterlacing and try again, you may have to reboot.

    All my h264 TV viewing is 1080i streamed in a .mkv container.

    Sometimes a .mkv container from TvHeadend is more compatible with various media players.

    LibreELEC-S912.arm-8.2-Chroma-422.Audio.fix.deinterlace.bypass.tar

    LibreELEC-S912.arm-8.2-Chroma-422.Audio.fix.deinterlace.bypass.img.gz


    Wizzi07 just be aware, if you are running a Kodi user interface at 2160p50 or 60Hz at a Chroma and bit depth of 444,10bit you will have issues as that combo is Not supported by HDMI 2.0 standards. See the table in THIS link.

    If 4:4:4 is used then you must run the Kodi user interface at a 1080p resolution and let LE Kodi auto switch to 2160p when watching 4K 24p movies.

    Yes it sounds like you need a high speed or premium certified HDMI 2.0a cable.

    The "Amazon Basics" and Monoprice ones work and are good value.

    This audio issue has nothing to do with kernel version. There were changes in Krypton. Kodi developers decided disable audio passthrough for liveTV by default and there is no option to enable it.

    Already using that patch for Krypton live TV and audio passthrough. It's unrelated.

    It's definitely the new (Leia) AML linux-kernel causing audio issues.

    EDIT: this audio issue is confirmed because I've fixed it in the new AML Linux Kernel with a bunch of audio reverts. Will do a Kernel Pull request for wider community bug busting.

    kostaman - straight from the LE Rockhip developer Kwiboo ....

    Quote

    there is no current support for deinterlacing on (linux) rockchip, there is post-process support for deinterlace in the VPU IP that handles up to 1080p video,

    .... the issue is that we have no post-process support in (rk)mpp library, it is only implemented in the android version to my knowledge