CoreELEC - MINIX U9-H

barbarisca said:
Hi.I am running the CoreElec 9.2.0 release on my U9-H and have been having issues with incorrect decoding of multi-channel E-AAC.
Any suggestions on how to resolve my E-AAC decoding issues?
Click to expand...

allmankind said:
I also have problems with AAC. 2 channel audio is fine, but multi channel (more than 2) often results in the center channel getting lost in the surround channels and playing at a significantly lower volumn, thus making dialog difficult to hear.

I use audio passthrough to my Denon AVR.
Click to expand...

I don't use CoreELEC but the number of channels you have Kodi's audio set to has the same effect on multi-chan AAC in Android too. (Settings -> System -> Audio.)

If currently set to the default 2.0 try setting 5.1 or 7.1 to match your number of speakers, hopefully it'll shift the vocals back to the centre. (The number of channels you set will have NO bearing on passthrough.)

You may also need to cycle through the available options for surround or auto decoding on your AVR too.

If that doesn't resolve it, it's an issue with the latest CoreELEC.
 
I'm having some sound issues. I can't get Dolby Atmos to work anymore as i just installed Corelec - I watched an Atmos movie last night before the switch.
I go to Audio, 2 channels is selected
I've tried all the audio output devices:
1. AML analog PCM
2. AML PCM
3. ALM HDMI (which i would assume is the one i need)
4. bluetooth audio
I've turned passthrough on for each one and no Dolby Atmos.
Without corelec using plain ole Kodi/Minix when i select passthrough it will give me all the sound codec options (Atmos, True HD etc), now those options do not come up and i can't get those sounds.
 
I have an older (~7 years) Samsung 5.1 receiver. I believe I have some Atmos movies that get mixed down to 5.1 OK.

I can say that the surround has been the biggest challenge for me - especially when I had a Z-84 running Windows. Nothing seemed to work consistently until I got a "smart splitter" with EDID. Part of the problem I think was that the Samsung was only good up to 1080P 60 Frames and maybe couldn't hack 4k going through it.

The splitter I have now senses the capabilities of attached devices and will convert the 4k down to 1080P on the port with the connected surround system.

In addition the splitter allows the source to "see" what capabilities are downstream - especially important for Windows/Z-84. The downside is that the splitter depends on a specific power sequence - splitter, audio receiver, TV, then source (U9-H).

My Kodi setup is to set the ACTUAL channels I have - 5.1 - and select "optimized" setup and then edit the capabilities in the passthrough section for my system where I only have Dolby AC3 and DTS capable receiver. These I found by trial and error turning each on and if the sound was like a helicopter was above my home I would turn that option off.

I don't know much about Atmos though I read people raving about it. Doesn't it just come as part of a 7.1 setup? I do notice there is no "Atmos" option in the passthrough section, but would think it would be passed through if 7.1 was selected for channels.
 
ArcticWolf said:
I don't use CoreELEC but the number of channels you have Kodi's audio set to has the same effect on multi-chan AAC in Android too. (Settings -> System -> Audio.)

If currently set to the default 2.0 try setting 5.1 or 7.1 to match your number of speakers, hopefully it'll shift the vocals back to the centre. (The number of channels you set will have NO bearing on passthrough.)

You may also need to cycle through the available options for surround or auto decoding on your AVR too.

If that doesn't resolve it, it's an issue with the latest CoreELEC.
Click to expand...

I do use passthrough. I only recently realized that passthrough can be turned off while watching a movie. I will have to give that a try next time I encounter a bad AAC track.

I have tried the different options on my AVR, but there were no cures. Also not a recent issue, this has been going on for a while, even with Kodi 17.

Thanks for the response, as you made me think of a possible fix.
 
klapa said:
I am the same as you - I will turn off the TV and leave the U9 and Surround on. I have not seen the issue you refer to but have only been using CE 9.2 about a week or two. I also still have the "red" skin not having much luck with the other skins.

For skips, hesitations, etc. in videos I have experienced such many times and always tracked it down to a data source speed issue. I just had a severe problem with 4k movies after switching to CE 9.2 and thought that or the U9 box to be the culprit, but found that my file server had witched IP on the ethernet interfaces and I was feeding the video through a 100M instead of 1G ethernet. Perhaps there is a speed issue using the disk on the U9?

I wait to see if I have the same problems as with 9.0.3 - in some cases, especially when skipping forward in a movie, the box would reboot and come back up with the video all wonky, set for low resolution 50Hz, and it would take a couple of reboots and setting changes to get things right again.
Click to expand...

On my system, my hard drive is connected directly to the Minix U9H via USB.

While the occasional hesitation could be a buffering/source speed issue, those are generally few and far between, plus being very short in nature, more like a skipped frame. They really don;t bother me too much, although I would definitely like them gone. The other problem that has suddenly arisen is the skip back of half a second or so and this repeats throughout the movie maybe once or twice a minute. Very annoying and pretty much makes watching the movie unwatchable.

It is not something in the file itself, as far as I can tell. The video plays flawlessly on my desktop computer. No skip backs, hesitations or anything. If I re-encode the movie, using handbrake, the re-encoded version plays without skip backs on CoreElec.

This is something I have never encountered before 9.2.0.
 
regismaltais33 said:
Hi,

How to install CoreElec in the Minix Neo U9-H ?

I mean not in a USB stick nor Micro SD

Thanks
Click to expand...
Hi. Please read this:

https://theminixforum.com/index.php?threads/coreelec-minix-u9-h.261/

See Post 2

Be aware if you install in internal storage and you don't like you must flash again the device (if you want again official firmware ROM).

I don't know if you already tried first dual boot (external storage).

Read step by step post 2 (be aware of the risk, if installed in eMMC)
 
Last edited:
As i said before i don't use and never installed coreelec but the speed of your external storage counts (in your case a microSD).
 
olive069 said:
Short CoreELEC installation tutorial (for advanced user only)

  • Download Rufus (https://rufus.akeo.ie/)
  • Download last *.img.gz CoreELEC release S912 Soc (https://github.com/CoreELEC/CoreELEC/releases)
  • Download S912 dtb file (https://github.com/CoreELEC/device-trees-amlogic). For Minix U9-H : gxm_q200_2g_minix_neo_u9.dts
  • Format an microSD card with FAT32 filesystem.
  • Create with Rufus an bootable card with *.img.gz image file. When it’s done, copy/paste .dts file to SD root and rename it dtb.img.
  • Turn off your Minix U9-H. Insert SD card, Plug power cord while pressing power button for several seconds until CoreELEC boot screen appears. It will reboot once and it’s done!
  • Now you have two choices :
    • You can stay on external/SD card installation : every time you’re booting, you have to do the power button trick to boot CoreELEC from your SD card or standard Android MINIX OS will start. It’s the safest way.
    • You can install it on internal NAND : log on your box with SSH (Putty for example) and type installtointernal. Reboot when asked. If you have a corrupted systemfile message on boot : turn off, boot from SDcard (hold power button) and install to internal once again. It should solve the problem. Do this only if you know what your’re doing !!
Click to expand...
please revise those steps something is missing...may be boot loader files ?
 
Hi,

Can someone can rewrite the steps, something is missing and the end result, I cannot make it work if you follow the actual steps to create a MicroSD

Like why formatting the MicroSD with Bootable Fat32, then you use an image (img) to overwrite it which is not bootable I believe, by example

Also it may be need some 3rdparty/bootloader files from the CoreELEC-Amlogic.arm-9.2.0.tar, but which of them ?

The img file I used is CoreELEC-Amlogic.arm-9.2.0-Generic.img, may be it is the wrong img file

Note, I was using Rufus, can you details the config to use in Rufus ?

Thanks

Regis
 
Last edited:
I use the LibreElec SD Creator Tool to make the bootable SD. Works for LibreElec and CoreElec.

Although I do use Rufus for Windows and other PC Bootable tools, I have never tried using it with Minix.

When I created an SD Card trial of CoreElec, I used a FULL size SD card, not a microSD. I then used an SD to USB adapter and attached it to one of the Minix USB ports.

The current dtb files should be on the SD card after you create it. Just copy the correct file to the root of the SD card and rename it to dtb.img.

Nothing is missing. The SD card, once created IS bootable. The only thing you need to do is select the correct dtb file for your system.
 
Last edited:
allmankind said:
I use the LibreElec SD Creator Tool to make the bootable SD. Works for LibreElec and CoreElec.

Although I do use Rufus for Windows and other PC Bootable tools, I have never tried using it with Minix.

When I created an SD Card trial of CoreElec, I used a FULL size SD card, not a microSD. I then used an SD to USB adapter and attached it to one of the Minix USB ports.

The current dtb files should be on the SD card after you create it. Just copy the correct file to the root of the SD card and rename it to dtb.img.

Nothing is missing. The SD card, once created IS bootable. The only thing you need to do is select the correct dtb file for your system.
Click to expand...

Which options you use in LibreElec SD Creator Tool, in order to make the SD ?
 
 
Honestly there few steps here and there but now I'm completely lost!

Those steps are done

I did figured out to use the LibreElec Tool to create the image on the microSD but after I make the dtb.img and try to boot nothing happen just Minix logo with green robot
 
You must log in or register to reply here.
Back
Top