How to install CoreELEC on the U22-XJ

Hello again. I have Coreelec installed on an sd card and it works great except for one thing. Analog audio output 3.5mm jack does not work for me in Coreelec on android yes. In U1 it works. I don't know if it only happens to me or is it generalized. If it works for someone I appreciate suggestions.
Regards.
 
Hello again. I have Coreelec installed on an sd card and it works great except for one thing. Analog audio output 3.5mm jack does not work for me in Coreelec on android yes. In U1 it works. I don't know if it only happens to me or is it generalized. If it works for someone I appreciate suggestions.
Regards.
This is a known issue that Minix and CoreELEC are working on, @Portisch can you confirm this is the case please.

I am a developer at CoreELEC and currently have some time to take a look again to the U22XJ device.

2. Analog audio jack amplifier
The U22XJ is using an Realteak ALC5651 audio amplifier. As this is not like a "simple" audio amp it needs to be pre configured by the driver. As we do not have a path of the analog audio signal we do not know how to setup the SoC correctly. The Minix Android firmware show us some adjustments by dmesg in the source files:​
rt5651.c
rt5651.h
They are located in the kernel folder: /sound/soc/codecs​
If you do not mind it would be much easier for us if you can provide those changes to the rt5651 codec.​
 
This is a known issue that Minix and CoreELEC are working on, @Portisch can you confirm this is the case please.

Ok thank you very much we will have patience. I use the audio output to listen to the sound, without disturbing, with a Wireless Sennheiser headphones. Reason why I need the 3.5mm jack.
 
@Portisch @Marty

do you have any information on why Multichannel AAC files will not play properly on the U22 with CoreELEC, and any possible solution ?

I get unlistenable slurry/dropped audio in PCM 2.0

Using CoreELEC 9.2.3 using HDMI passthrough to an AVR

thanks :)
 
Well, I didn't start to configure it because for me its unacceptable to wait 5 min to start the box. Anyway, it sounds it survived to the reboot, so I'm planning to buy a brand new Kingston DataTraveler USB Stick and retry the process

Was your startup time for the very first boot or is it that slow on all subsequent reboots?

I almost gave up waiting on that initial boot. In fact I did stop it a couple of times, as I was waiting long past the 120 seconds of the screen message. But on one boot attempt, I had to leave the room to take care of some business. I was away for 5 or 10 minutes, but when I returned I was in CoreElec. And subsequent reboots are much much faster.

That initial boot is VERY slow.
 
Was your startup time for the very first boot or is it that slow on all subsequent reboots?

I almost gave up waiting on that initial boot. In fact I did stop it a couple of times, as I was waiting long past the 120 seconds of the screen message. But on one boot attempt, I had to leave the room to take care of some business. I was away for 5 or 10 minutes, but when I returned I was in CoreElec. And subsequent reboots are much much faster.

That initial boot is VERY slow.

I was talking about the first (initial) boot after installation. I used a very old USB stick to give it a try, then I changed the memory support (I checked with a faster USB Stick and microSD) and both initial and following boots are fast.
 
Hi... I am new to CoreELEC but have managed to install it on my U22 but I cannot successfully connect to the internet. The Network page shows my WiFi but when I enter the key it does not connect, remains "idle". I am using the latest FW and most recent CoreElec fir U22. I have tried changing the "Firewall" setting but still no success. Has anyone else had this problem? Any suggestions? Thanks.
 
Hi... I am new to CoreELEC but have managed to install it on my U22 but I cannot successfully connect to the internet. The Network page shows my WiFi but when I enter the key it does not connect, remains "idle". I am using the latest FW and most recent CoreElec fir U22. I have tried changing the "Firewall" setting but still no success. Has anyone else had this problem? Any suggestions? Thanks.
After many more attempts it just connected! Wierd, but all good now...

One more thing... when I power off the blue light on the MINIX turns to green and stays lit, the box I presume is in standby mode. How do I get it to power off completely?
 
After many more attempts it just connected! Wierd, but all good now...

One more thing... when I power off the blue light on the MINIX turns to green and stays lit, the box I presume is in standby mode. How do I get it to power off completely?

Other users have mentioned the same issue with CoreELEC if you read through some of their comments :).
 
After many more attempts it just connected! Wierd, but all good now...

One more thing... when I power off the blue light on the MINIX turns to green and stays lit, the box I presume is in standby mode. How do I get it to power off completely?
As @ArcticWolf has mentioned this is a known issue and a limitation of CoreElec, the only work around is to reboot to NAND from the CoreElec menu and shut down from Android or pull the lead if you don't have MCU enabled.
 
the only work around is to reboot to NAND from the CoreElec menu
do you know the custom command for this option as if you use a different skin then this isnt present and i would like to add to my power menu.
 
Surely you mean "if it is enabled" .
Nope, I mean if you don't have MCU enabled, if it is enabled then it will auto power on when you plug the power lead back in and boot back into CoreElec, unless the media is ejected prior of course.
 
do you know the custom command for this option as if you use a different skin then this isnt present and i would like to add to my power menu.
No idea unfortunately, I guess it would be buried a .py file in the system default skin folder. I will have a dig around.
 
Nope, I mean if you don't have MCU enabled, if it is enabled then it will auto power on when you plug the power lead back in and boot back into CoreElec, unless the media is ejected prior of course.
Surely you mean "if it is enabled" .
Yeah couldn't quite work out why it mattered?! :unsure:

So it doesn't really matter whether MCU is enabled or not then! ;)
Pull the plug switches off the device. If MCU is enabled, do not re-connect!!! :p
 
Hey guys, first post on this board.
I have a Minix Neo U22-XJ, just updated to the 006A rooted firmware.
Seems that I can boot up to emuelec (lets just say coreelec) only with the 32gb Sandisk- but when using a 128gb it fails to boot.
I had a similar issue with the A9 box (905x with 2gb), and I found that using a dtb file with a *slow emmc* affix worked, whilst the standard one did not.
Could it be a similar issue with the U22? A slow microsd reader?

Many thanks,
Tim
 
Hey guys, first post on this board.
I have a Minix Neo U22-XJ, just updated to the 006A rooted firmware.
Seems that I can boot up to emuelec (lets just say coreelec) only with the 32gb Sandisk- but when using a 128gb it fails to boot.
I had a similar issue with the A9 box (905x with 2gb), and I found that using a dtb file with a *slow emmc* affix worked, whilst the standard one did not.
Could it be a similar issue with the U22? A slow microsd reader?

Many thanks,
Tim
Hi Tim, welcome to the forum.

I use a Samsung 128gb SD Card (here) with CoreELEC on my U22 without issues so I suspect it is either an EmuELEC problem or somethings up with the SD Card you are using.
 
Back
Top