CoreELEC

Post Reply
User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

slaav wrote:
Thu Feb 27, 2020 4:38 am

The software works stable for some time now. WiFi connection is stable, I also was able to get better transfer speeds (but that might be a result of switching to a newer WiFi dongle). Is there a change your changes will be pushed to nightly and then stable builds? Thanks
I just pushed the updated RTL8812AU driver. So it will be in the next nightly build.
These users thanked the author cdu13a for the post (total 2):
slaav (Thu Feb 27, 2020 5:58 am) • odroid (Mon Mar 02, 2020 11:00 am)

slaav
Posts: 22
Joined: Tue Feb 03, 2015 10:58 pm
languages_spoken: english, polish
ODROIDs: C1
Has thanked: 3 times
Been thanked: 0
Contact:

Re: CoreELEC

Post by slaav »

cdu13a wrote:
Thu Feb 27, 2020 5:38 am
I just pushed the updated RTL8812AU driver. So it will be in the next nightly build.
Thanks a lot! Works like a charm.

Ohcan.md
Posts: 2
Joined: Mon Mar 23, 2020 4:48 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by Ohcan.md »

Hi,

I've asked this somewhere else around here but there's too many boards on this forum so I get confused which is which.

I just wanted to know how the hell do I make the Odroid N2 CE power up every time I want to use it. Right now the only way is unplugging and plugging it again. I don't have an IR remote so I want to know if I can do it maybe with a game controller, a mouse or even my own TV remote.

Thanks

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

Ohcan.md wrote:
Mon Mar 23, 2020 7:52 am
I just wanted to know how the hell do I make the Odroid N2 CE power up every time I want to use it. Right now the only way is unplugging and plugging it again. I don't have an IR remote so I want to know if I can do it maybe with a game controller, a mouse or even my own TV remote.
There are several possibilities, I use WOL (Wake on Lan) and use my phone to wake my N2.
For more details how to, ask here: https://discourse.coreelec.org and https://discourse.coreelec.org/c/single ... roid-n2/27

Ozk649
Posts: 9
Joined: Thu Mar 12, 2020 10:21 am
languages_spoken: english
ODROIDs: None
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by Ozk649 »

Guys... need help.. I want find out if there is a way to get moonlight or steam on CoreElec on N2. Any help is appreciated,

Cheers

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

I think you already asked the same question on the CoreElec forum.
All I can say is that you need to study docker documentation and start to experiment. May try some tutorials to master docker command.
I can't help you because I don't know how to use docker.

slaav
Posts: 22
Joined: Tue Feb 03, 2015 10:58 pm
languages_spoken: english, polish
ODROIDs: C1
Has thanked: 3 times
Been thanked: 0
Contact:

Re: CoreELEC

Post by slaav »

cdu13a wrote:
Thu Feb 27, 2020 5:38 am
I just pushed the updated RTL8812AU driver. So it will be in the next nightly build.
cdu13a - do you know why your RTL8812AU updates were reverted in the latest nightly (20200401)?

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

slaav wrote:
Thu Apr 02, 2020 12:56 pm
cdu13a wrote:
Thu Feb 27, 2020 5:38 am
I just pushed the updated RTL8812AU driver. So it will be in the next nightly build.
cdu13a - do you know why your RTL8812AU updates were reverted in the latest nightly (20200401)?
Some of the CoreELEC developers are trying to make a push to get a new stable build released soon and unfortunately one of the other developers was apparently having severe connection issues related to the new driver when using Hardkernel's WiFi Module 5A in 5Ghz mode. Since the WiFi Module 5A is one of the more common adapters to be used with the N2 and we have a large number of users with N2, it was felt that the driver should get rolled back for the stable release to prevent the potential of a large number of users having an issue with the new stable release.

I spent a few days trying to sort this out and will try again with the updated driver after the stable build.
These users thanked the author cdu13a for the post (total 2):
slaav (Thu Apr 02, 2020 2:32 pm) • odroid (Thu Apr 02, 2020 6:15 pm)

slaav
Posts: 22
Joined: Tue Feb 03, 2015 10:58 pm
languages_spoken: english, polish
ODROIDs: C1
Has thanked: 3 times
Been thanked: 0
Contact:

Re: CoreELEC

Post by slaav »

Thanks for the info

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

The stable 9.2.2 version, with the new kernel and hdr10+ support, is live.
https://coreelec.org/#download

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

Sav wrote:
Tue Apr 14, 2020 12:07 am
The stable 9.2.2 version, with the new kernel and hdr10+ support, is live.
https://coreelec.org/#download
Be ware if you plan to update/install to some Class 10 uSD cards. On N2 there is a very big slowdown compared to v.9.2.1.
Installation time for fresh install is longer than 10 minutes, and update is even longer; it looks as if it's stuck at new blue CE logo.
Also reboot times are much slower, from 30-40 sec on 9.2.1 to 3 min 30 sec on 9.2.2.

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

No problem on sandisk extreme pro (a2)

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

Sholander wrote:
Tue Apr 14, 2020 12:46 am

Be ware if you plan to update/install to some Class 10 uSD cards. On N2 there is a very big slowdown compared to v.9.2.1.
Installation time for fresh install is longer than 10 minutes, and update is even longer; it looks as if it's stuck at new blue CE logo.
Also reboot times are much slower, from 30-40 sec on 9.2.1 to 3 min 30 sec on 9.2.2.
Well, good news, in the mean time it has been fixed with new N2 images, so there should be no problem updating/installing on any uSD card !
All images are found here: https://github.com/CoreELEC/CoreELEC/releases

Pendragon11
Posts: 6
Joined: Sat Apr 11, 2020 1:22 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by Pendragon11 »

Howdy,
I'm hitting a bit of a wall and would appreciate some assistance. I have an n2 running CE (obviously!). I'm trying to build a CE media consumption device that also runs torrents, uses private internet access vpn, and a plex server. Of course, I expect many of these to operate within docker. I'm new to docker though, and it's been a fun learning experience. I've checked out the linuxserver openvpn client, but it's the wrong architecture (2 nights down...). I've found an older vpn image giggio/openvpn-arm, but I can't get the setup down. Would appreciate any recommended images or suggestions.

Thanks!

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

For the vpn, there are many kodi addons and you don't need a docker container. Just check on the kodi forum.
For plex and torrents in a docker container there are many tutorials for raspberry. I can't help you much, but you can learn how to setup docker by following them.

Pendragon11
Posts: 6
Joined: Sat Apr 11, 2020 1:22 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by Pendragon11 »

Thanks Sav! I've got the VPN running through zomboided VPN manager. Do you know if there's a way to test if a torrent client runs through it?

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

All the network traffic of the N2 should be tunnelled trough the vpn if you run zomboided.

Pendragon11
Posts: 6
Joined: Sat Apr 11, 2020 1:22 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by Pendragon11 »

Awesome! How would I go about logging onto a private tracker with this setup? Thanks for all your help

Sav
Posts: 226
Joined: Mon Sep 02, 2019 2:33 am
languages_spoken: english
ODROIDs: odroid-n2
Has thanked: 59 times
Been thanked: 22 times
Contact:

Re: CoreELEC

Post by Sav »

I don't know

feefeechow
Posts: 24
Joined: Sat Feb 15, 2020 12:16 am
languages_spoken: english
Has thanked: 1 time
Been thanked: 0
Contact:

Re: CoreELEC

Post by feefeechow »

I updated to 922 and tons of error displayed in the bootup screen. Mine is 4GB N2 with a USB. Finally I grabbed the 921 back and disable autoupdate. What happens and any fixes available these days ?

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

feefeechow wrote:
Mon Apr 20, 2020 1:52 pm
I updated to 922 and tons of error displayed in the bootup screen. Mine is 4GB N2 with a USB. Finally I grabbed the 921 back and disable autoupdate. What happens and any fixes available these days ?
There was a USB bug that was missed, since it only happens when using the bottom USB port closest to the power adapter.

There is a fix coming soon. As a temporary fix If you have a USB device plugged into that bottom USB port beside the power adapter, move it to one of top ports instead.

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

cdu13a wrote:
Mon Apr 20, 2020 3:46 pm
feefeechow wrote:
Mon Apr 20, 2020 1:52 pm
I updated to 922 and tons of error displayed in the bootup screen. Mine is 4GB N2 with a USB. Finally I grabbed the 921 back and disable autoupdate. What happens and any fixes available these days ?
There was a USB bug that was missed, since it only happens when using the bottom USB port closest to the power adapter.

There is a fix coming soon. As a temporary fix If you have a USB device plugged into that bottom USB port beside the power adapter, move it to one of top ports instead.
I think that this refers only to USB drives, as I have my USB-WiFi adapter, for my mini keyboard, in that port since I first installed CE on N2 ( a year ago) and never had any problem with that, not even when updating or fresh installing v9.2.2.

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

Sholander wrote:
Mon Apr 20, 2020 7:40 pm
cdu13a wrote:
Mon Apr 20, 2020 3:46 pm
feefeechow wrote:
Mon Apr 20, 2020 1:52 pm
I updated to 922 and tons of error displayed in the bootup screen. Mine is 4GB N2 with a USB. Finally I grabbed the 921 back and disable autoupdate. What happens and any fixes available these days ?
There was a USB bug that was missed, since it only happens when using the bottom USB port closest to the power adapter.

There is a fix coming soon. As a temporary fix If you have a USB device plugged into that bottom USB port beside the power adapter, move it to one of top ports instead.
I think that this refers only to USB drives, as I have my USB-WiFi adapter, for my mini keyboard, in that port since I first installed CE on N2 ( a year ago) and never had any problem with that, not even when updating or fresh installing v9.2.2.
It was just easier to just say USB in general then being specific, since it's not just USB drives that will encounter this issue and I did not want to get bogged down in details, when the important message was if it happens just use a different port until it's fixed.

bright_plastik
Posts: 27
Joined: Tue Apr 21, 2020 9:22 am
languages_spoken: English, Italian, some French.
ODROIDs: N2
Has thanked: 12 times
Been thanked: 7 times
Contact:

Re: CoreELEC

Post by bright_plastik »

Hello everyone.
New member here, with a brand new N2 on hand.
Dual boot with CoreELEC 9.2.2 and tobetter's Ubuntu 20.04 on a 32Gb emmc, so the selector is always set to SPI, to choose OS by petitboot.

I hope someone can help me with a problem I'm experiencing. I set up my phone with a working simulation of the Odroid IR remote and can use the IR blaster to control both the petitboot (ver 20200224) and navigation in CE. All good till here. The config I used is this
odroid-amremote.conf.txt
(887 Bytes) Downloaded 27 times
My problem is I can only boot the box with reconnection of the power jack.
First I tried to modify only "config.ini", as I read it is the only one that should be modified. I added these lines

Code: Select all

remotewakeup='0x3BC4'
decode_type='0x0'
and

Code: Select all

gpiopower=476
to try to boot either by remote or by GPIO pins. Unfortunately none worked.
Then I tried modifying "boot.ini" with these lines

Code: Select all

setenv remotewakeup "0x3BC4"
setenv decode_type "0"
setenv remotewakeupmask "0xffffffff"
and

Code: Select all

setenv gpiopower "476"
setenv bootargs ${bootargs} gpiopower=${gpiopower}
Same behaviour. Does not turn on, both by remote and GPIO.

This is my second night tinkering with the code, and I'd be very happy if someone could tell me what is going on, and what I'm missing! :lol:

edd--
Posts: 9
Joined: Wed Jan 08, 2020 10:27 pm
languages_spoken: english
ODROIDs: C2 N2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: CoreELEC

Post by edd-- »

Sholander wrote:
Tue Apr 14, 2020 12:46 am
Sav wrote:
Tue Apr 14, 2020 12:07 am
The stable 9.2.2 version, with the new kernel and hdr10+ support, is live.
https://coreelec.org/#download
Be ware if you plan to update/install to some Class 10 uSD cards. On N2 there is a very big slowdown compared to v.9.2.1.
Installation time for fresh install is longer than 10 minutes, and update is even longer; it looks as if it's stuck at new blue CE logo.
Also reboot times are much slower, from 30-40 sec on 9.2.1 to 3 min 30 sec on 9.2.2.
I'm noticing freezes since 9.2.2, could be caused by the slower SD cards ? Is someone working on this ? Should I downgrade (if possible) ? Or buy a new SD card ?

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

edd-- wrote:
Sun May 03, 2020 5:09 am
Sholander wrote:
Tue Apr 14, 2020 12:46 am
Sav wrote:
Tue Apr 14, 2020 12:07 am
The stable 9.2.2 version, with the new kernel and hdr10+ support, is live.
https://coreelec.org/#download
Be ware if you plan to update/install to some Class 10 uSD cards. On N2 there is a very big slowdown compared to v.9.2.1.
Installation time for fresh install is longer than 10 minutes, and update is even longer; it looks as if it's stuck at new blue CE logo.
Also reboot times are much slower, from 30-40 sec on 9.2.1 to 3 min 30 sec on 9.2.2.
I'm noticing freezes since 9.2.2, could be caused by the slower SD cards ? Is someone working on this ? Should I downgrade (if possible) ? Or buy a new SD card ?
If you updated to 9.2.2 on the first day it was available, try downloading the update tar for 9.2.2 and manually updating to it again. The original update files had a couple issues, but got replaced with corrected ones.

phaseshifter
Posts: 3549
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 47 times
Been thanked: 46 times
Contact:

Re: CoreELEC

Post by phaseshifter »

can somebody give me help setting video mode for n2 core elec and the vu7 display..
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

phaseshifter wrote:
Sun May 10, 2020 5:53 pm
can somebody give me help setting video mode for n2 core elec and the vu7 display..
I can't remember if the original vu7 actually advertised anything via edid or not, but 800x480p60hz is in the kernel so you should be able to:

create a file called
.kodi/userdata/disp_add

then add the following to it.
800x480p60hz

This should add 800x480p60hz to the list of available resolutions in kodi. If the display doesn't advertise any resolutions then this will become the default resolution, and be used automatically by kodi.
These users thanked the author cdu13a for the post:
phaseshifter (Mon May 11, 2020 5:29 am)

phaseshifter
Posts: 3549
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 47 times
Been thanked: 46 times
Contact:

Re: CoreELEC

Post by phaseshifter »

i dont know you but from what i have shortly browsed over seems your the person to talk too...i had it running with some success..on my own back...
it would be good if you could have the menu in kodi 90 degrees but the pic`s as normal..that would be handy

what i did was in the code line that lists the display for 1080p and for v-out .

i changed the values to 800x480 i left the P in there maybe that was a problem "P60hz" i dunno but i have not tried your code i will ..

pls excuse my typos i cannot see the screen atm..lack of space i guess..lol..lol
thankyou...

my head is in other stuff atm
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
odroid
Site Admin
Posts: 35846
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 1299 times
Been thanked: 907 times
Contact:

Re: CoreELEC

Post by odroid »

As far as I know, CoreELEC supports only standard wide TV resolutions like 1280x720, 1920x1080 and 3840x2160.

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

VESA modes are supported by CoreELEC, though they are disabled/ignored by default.

They can be enabled in the Hardware section of CoreELEC settings addon or by creating a file in the flash partition /flash/vesa.enable to enable all VESA modes that are advertised by the display.

Individual Modes can be enabled by adding them to a .kodi/userdata/disp_add file. Which will add them to the list of modes advertised by the display.

You can also do the same with a .kodi/userdata/disp_cap file. This however replaces modes advertised by display with the ones in the file.

In addition to your standard 480p/576p/720p/1080p/2160p at standard refresh rates, the following modes are also supported by CoreELEC

Code: Select all

640x480p60hz
800x480p60hz
800x600p60hz
852x480p60hz
854x480p60hz
1024x600p60hz
1024x768p60hz
1152x864p75hz
1280x600p60hz
1280x768p60hz
1280x800p60hz
1280x960p60hz
1280x1024p60hz
1360x768p60hz
1366x768p60hz
1400x1050p60hz
1440x900p60hz
1440x2560p60hz
1600x900p60hz
1600x1200p60hz
1680x1050p60hz
1920x1200p60hz
2160x1200p90hz
2560x1080p50hz
2560x1080p60hz
2560x1440p60hz
2560x1600p60hz
3440x1440p60hz

User avatar
odroid
Site Admin
Posts: 35846
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 1299 times
Been thanked: 907 times
Contact:

Re: CoreELEC

Post by odroid »

@cdu13a,
Thank you for the detail instruction.
We will test 800x480 and 1024x600 modes on the latest CE with our Vu7/5 series display devices.

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

The 20200512 nightly build of CoreELEC will have the touchscreen drivers for the Vu5/Vu7/Vu5a/Vu7a plus enabled.
These users thanked the author cdu13a for the post (total 3):
tobetter (Tue May 12, 2020 10:11 pm) • odroid (Wed May 13, 2020 10:00 am) • rooted (Wed May 13, 2020 10:15 pm)

joshua.yang
Posts: 464
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 31 times
Been thanked: 124 times
Contact:

Re: CoreELEC

Post by joshua.yang »

Hi.

I have tested with Vu5, Vu5A, Vu7, Vu7A Plus, using CoreELEC 20200512 nightly build.
- Vu5: Not working. The screen shows up but very weird. Shows cropped and bigger scaled screen. The touchscreen looks working but useless due to the screen malfunction.
- Vu5A: Touchscreen working. (1920x1080p)
- Vu7: Not working. White screen.
- Vu7A: Touchscreen working. (1920x1080p)

We need to know how to force the HDMI output to the Vu series native resolution 800x480 and 1024x600.
Should I edit boot.ini file?

I also played 4K 60fps h.265 video on confirmed Vu screens, and it plays very well.

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

joshua.yang wrote:
Wed May 20, 2020 4:56 pm
We need to know how to force the HDMI output to the Vu series native resolution 800x480 and 1024x600.
Should I edit boot.ini file?
Since boot.ini gets overwritten with every update, to get custom video modes (or any other change) you have to edit/modify "config.ini". At the bottom of config.ini there is a section for setting "HDMI custom mode "

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

joshua.yang wrote:
Wed May 20, 2020 4:56 pm
Hi.

I have tested with Vu5, Vu5A, Vu7, Vu7A Plus, using CoreELEC 20200512 nightly build.
- Vu5: Not working. The screen shows up but very weird. Shows cropped and bigger scaled screen. The touchscreen looks working but useless due to the screen malfunction.
- Vu5A: Touchscreen working. (1920x1080p)
- Vu7: Not working. White screen.
- Vu7A: Touchscreen working. (1920x1080p)

We need to know how to force the HDMI output to the Vu series native resolution 800x480 and 1024x600.
Should I edit boot.ini file?

I also played 4K 60fps h.265 video on confirmed Vu screens, and it plays very well.
I unfortunately only have a Vu5a for testing, and since not many users have asked about supporting these display I had forgot that the original non A versions needed a little extra to get working.

give the following a try

For the 800x480 devices create
.kodi/userdata/disp_cap
with the contents of
800x480p60hz

Which isn't perfect by itself since this doesn't cover the boot splash.

In the boot.ini file following line
setenv displayopt "hdmimode=1080p60hz logo=osd0,loaded,0x3d800000 vout=1080p60hz,enable"

for testing this can be changed to
setenv displayopt "hdmimode=800x480p60hz logo=osd0,loaded,0x3d800000 vout=800x480p60hz,enable"
or possibly
setenv displayopt "hdmimode=800x480p60hz vout_mode=dvi logo=osd0,loaded,0x3d800000 vout=800x480p60hz,enable"

Let me know the results of this. I can make the required changes to CoreELEC once we have a confirmed working solution for each display.

Edit: I have made the changes to support having hdmimode and vout_mode be configurable via the config.ini file on the N2 and the C4. I just need to know if manually setting these values as I suggested above has the desired effect. Once I get feedback I can push the changes so that it can be easily configured by the average user. I can also make an easy to follow guide on how to configure CoreELEC on the N2 and C4 for use with the Vu series displays once we have a solution that works for all of them.

Edit: For the original Vu7 I think you needed to use a usbhid quirk to get the touch input to work. This can be done by creating a file .config/modprobe.d/vu7.conf with the following contents

Code: Select all

# Enable vu7 touch input
options usbhid quirks=0x0eef:0x0005:0x0004

joshua.yang
Posts: 464
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 31 times
Been thanked: 124 times
Contact:

Re: CoreELEC

Post by joshua.yang »

cdu13a wrote:
Fri May 22, 2020 4:47 am
I unfortunately only have a Vu5a for testing, and since not many users have asked about supporting these display I had forgot that the original non A versions needed a little extra to get working.

give the following a try

For the 800x480 devices create
.kodi/userdata/disp_cap
with the contents of
800x480p60hz

Which isn't perfect by itself since this doesn't cover the boot splash.

In the boot.ini file following line
setenv displayopt "hdmimode=1080p60hz logo=osd0,loaded,0x3d800000 vout=1080p60hz,enable"

for testing this can be changed to
setenv displayopt "hdmimode=800x480p60hz logo=osd0,loaded,0x3d800000 vout=800x480p60hz,enable"
or possibly
setenv displayopt "hdmimode=800x480p60hz vout_mode=dvi logo=osd0,loaded,0x3d800000 vout=800x480p60hz,enable"

Let me know the results of this. I can make the required changes to CoreELEC once we have a confirmed working solution for each display.

Edit: I have made the changes to support having hdmimode and vout_mode be configurable via the config.ini file on the N2 and the C4. I just need to know if manually setting these values as I suggested above has the desired effect. Once I get feedback I can push the changes so that it can be easily configured by the average user. I can also make an easy to follow guide on how to configure CoreELEC on the N2 and C4 for use with the Vu series displays once we have a solution that works for all of them.

Edit: For the original Vu7 I think you needed to use a usbhid quirk to get the touch input to work. This can be done by creating a file .config/modprobe.d/vu7.conf with the following contents

Code: Select all

# Enable vu7 touch input
options usbhid quirks=0x0eef:0x0005:0x0004
Hi.

Thanks for your detailed description. I have tested with your guide and can write the result like the below.

How I understand it is, in a simple sentence, .kodi/userdata/disp_cap is for in Kodi UI resolution and boot.ini is for the boot splash image.
So I changed those 2 files to the proper values to set to 800x480 and 1024x600.

In my test, at the boot splash time the screen is shown properly as I intended. But in Kodi, the UI screen shows the contents like 1080p but scaled all fonts/images down to the target resolution. It gets very hard to read, 800x480 is further worse.
And if I played 4K 60Hz H.265 video with resolution-set mode, the video is not played well. The screen is broken like the attached photo. The Vu product on the photo is Vu7A Plus.
I think the Kodi GUI layer as well as video play layer are optimized for TV resolutions like 1280x720 and 1920x1080.
2020-05-25-11-31-21.jpeg
2020-05-25-11-31-21.jpeg (137.66 KiB) Viewed 3353 times
This is played flawlessly with the default 1080p settings. UI also shows clearly too.

Thanks.

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

joshua.yang wrote:
Mon May 25, 2020 4:58 pm
cdu13a wrote:
Fri May 22, 2020 4:47 am
...

Edit: I have made the changes to support having hdmimode and vout_mode be configurable via the config.ini file on the N2 and the C4. I just need to know if manually setting these values as I suggested above has the desired effect. Once I get feedback I can push the changes so that it can be easily configured by the average user. I can also make an easy to follow guide on how to configure CoreELEC on the N2 and C4 for use with the Vu series displays once we have a solution that works for all of them.

Edit: For the original Vu7 I think you needed to use a usbhid quirk to get the touch input to work. This can be done by creating a file .config/modprobe.d/vu7.conf with the following contents

Code: Select all

# Enable vu7 touch input
options usbhid quirks=0x0eef:0x0005:0x0004
Hi.

Thanks for your detailed description. I have tested with your guide and can write the result like the below.

How I understand it is, in a simple sentence, .kodi/userdata/disp_cap is for in Kodi UI resolution and boot.ini is for the boot splash image.
So I changed those 2 files to the proper values to set to 800x480 and 1024x600.

In my test, at the boot splash time the screen is shown properly as I intended. But in Kodi, the UI screen shows the contents like 1080p but scaled all fonts/images down to the target resolution. It gets very hard to read, 800x480 is further worse.
And if I played 4K 60Hz H.265 video with resolution-set mode, the video is not played well. The screen is broken like the attached photo. The Vu product on the photo is Vu7A Plus.
I think the Kodi GUI layer as well as video play layer are optimized for TV resolutions like 1280x720 and 1920x1080.

This is played flawlessly with the default 1080p settings. UI also shows clearly too.

Thanks.
I will make a test build with the changes I have made, and post it with instructions for you to try. So that you can give me feedback about the what works with it, and what still needs some extra attention for each specific vu display.

The issue with the playback of some 4K videos is known. There was a fix made a while back to solve playback issues for some 4k files. This fix unfortunately doesn't take into consideration display resolutions below 720p. The developer who made the fix probably didn't think anybody would be trying to play back 4k content at 480p. It's also known that there are a few other places were resolutions other then the standard TV resolutions were not considered during initial development. Changes may be possible to improve the experience at lower resolutions.

I don't think anybody considered that somebody would try to do the following when they were doing the initial development of Kodi, or any other part of CoreELEC.
vu5a.jpg
vu5a.jpg (160.51 KiB) Viewed 3311 times
I know it's a really bad quality picture. It actually looks much better in person, but this is a Vu5a attached to a C4 that is playing 8k content.

User avatar
rooted
Posts: 8106
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 727 times
Been thanked: 270 times
Contact:

Re: CoreELEC

Post by rooted »


cdu13a wrote:... this is a Vu5a attached to a C4 that is playing 8k content.
First time in the world 8K @ 5 inches :)

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

@joshua.yang

Here is a test build that should give a better experience with the vu displays. (I only uploaded the update tar file, place it in the .update folder and reboot to manually update an existing install)
https://drive.google.com/drive/folders/ ... 7g7DsL3YQ8

You will still need to create the .kodi/userdata/disp_cap with the correct mode for the vu display that you are using.

But instead of editing the boot.ini file which does get replaced when CoreELEC is updated, you now add the following line to the /flash/config.ini file to specify the video mode to use at boot.
hdmimode='800x480p60hz'

joshua.yang
Posts: 464
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 31 times
Been thanked: 124 times
Contact:

Re: CoreELEC

Post by joshua.yang »

cdu13a wrote:
Tue May 26, 2020 5:18 pm
@joshua.yang

Here is a test build that should give a better experience with the vu displays. (I only uploaded the update tar file, place it in the .update folder and reboot to manually update an existing install)
https://drive.google.com/drive/folders/ ... 7g7DsL3YQ8

You will still need to create the .kodi/userdata/disp_cap with the correct mode for the vu display that you are using.

But instead of editing the boot.ini file which does get replaced when CoreELEC is updated, you now add the following line to the /flash/config.ini file to specify the video mode to use at boot.
hdmimode='800x480p60hz'
Thanks a lot. I will test with that image and let you know as soon as I finish the test.

p3numbra_3
Posts: 1
Joined: Mon Apr 27, 2020 9:56 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 0
Been thanked: 0
Contact:

Re: CoreELEC

Post by p3numbra_3 »

Hi,

Is there a way to set up pulseaudio server on CoreElec and output to 3.5mm while kodi is active (or inactive for that matter, i cant get it to work anyhow).

pactl only shows hdmi output (from kodi i can output to 3.5mm) and while kodi is active i can output to 3.5mm with `aplay -D "hw:0,1" myfile.wav` but still cant locate 3.5mm;

My main goal is to have N2 connected to my amp and have "network audio output device" on my other computers. I've managed to do this before on other computes but not on N2 running core elec (https://wiki.libreelec.tv/pulseaudio)

P.S. Is there any working spotify agent plugin (like librespot or something, cant get one from repo to work) for current version of coreelec?

Chris Oi
Posts: 61
Joined: Tue Aug 04, 2015 5:56 pm
languages_spoken: German, English
ODROIDs: Odroid XU4
Odroid N2
Has thanked: 17 times
Been thanked: 16 times
Contact:

Re: CoreELEC

Post by Chris Oi »

The update to 9.2.3 broke the HDR10+ support on my N2. Does anyone else have this issue?
When downgrading to 9.2.2 it's working again

User avatar
rooted
Posts: 8106
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 727 times
Been thanked: 270 times
Contact:

Re: CoreELEC

Post by rooted »

Chris Oi wrote:The update to 9.2.3 broke the HDR10+ support on my N2. Does anyone else have this issue?
When downgrading to 9.2.2 it's working again
I can't find any HDR10+ content to test.

Sholander
Posts: 156
Joined: Wed Jun 05, 2019 1:02 am
languages_spoken: english
ODROIDs: ODROID N2
Has thanked: 0
Been thanked: 19 times
Contact:

Re: CoreELEC

Post by Sholander »

Chris Oi wrote:
Fri Jun 12, 2020 3:09 am
The update to 9.2.3 broke the HDR10+ support on my N2. Does anyone else have this issue?
When downgrading to 9.2.2 it's working again
With 9.2.3 set HDR to SDR to Auto not Off, and reboot.
These users thanked the author Sholander for the post (total 3):
Chris Oi (Fri Jun 12, 2020 7:50 am) • rooted (Fri Jun 12, 2020 8:41 am) • cdu13a (Fri Jun 12, 2020 2:32 pm)

Chris Oi
Posts: 61
Joined: Tue Aug 04, 2015 5:56 pm
languages_spoken: German, English
ODROIDs: Odroid XU4
Odroid N2
Has thanked: 17 times
Been thanked: 16 times
Contact:

Re: CoreELEC

Post by Chris Oi »

Thanks, that worked :D

edd--
Posts: 9
Joined: Wed Jan 08, 2020 10:27 pm
languages_spoken: english
ODROIDs: C2 N2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: CoreELEC

Post by edd-- »

I have a strange issue after migrating from SD card to eMMC: 4K resolutions (at higher framerates) show a very scrambled screen when there is movement in the GUI. I disabled GUI scaling. Weird thing is that this worked perfectly with an SD card install, but since I migrated to eMMC I've had this issue. It does work at lower framerates (4K @24Hz). Any ideas from anyone ? Would be stupid to have to migrate back to SD because of this ...

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

edd-- wrote:
Fri Jun 19, 2020 8:22 pm
I have a strange issue after migrating from SD card to eMMC: 4K resolutions (at higher framerates) show a very scrambled screen when there is movement in the GUI. I disabled GUI scaling. Weird thing is that this worked perfectly with an SD card install, but since I migrated to eMMC I've had this issue. It does work at lower framerates (4K @24Hz). Any ideas from anyone ? Would be stupid to have to migrate back to SD because of this ...
I just tried to recreate the issue you described with an install of CoreELEC 9.2.3 on an 16gb eMMC module, with the GUI set to 3840x2160p, disabled GUI scaling. tested at both 50hz and 60hz refresh rate.
I wasn't able to recreate the issue based on your description.

The issue you describe does it happen during video playback or just when browsing the GUI?

What version of CoreELEC are you using?

How did you migrate your install to the eMMC? did you do a fresh install on the eMMC and restore a backup over it or did you use the installtoemmc utility?

edd--
Posts: 9
Joined: Wed Jan 08, 2020 10:27 pm
languages_spoken: english
ODROIDs: C2 N2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: CoreELEC

Post by edd-- »

I'm running 9.2.3. I just tried with a clean install from SD, even when booting from the SD with the eMMC (32GB) plugged in I get the tearing.
As soon as I boot without the eMMC plugged i don't have the issue. I created a small video to illustrate:

https://youtu.be/ztJPe4DHIlk.

So far I have not seen the issue while playing video's, but I don't have any high framerate 4K video's to test with ...

User avatar
cdu13a
Posts: 321
Joined: Tue Jan 20, 2015 3:33 pm
languages_spoken: english
ODROIDs: C1, C2, XU4, HC1, N2
Has thanked: 13 times
Been thanked: 100 times
Contact:

Re: CoreELEC

Post by cdu13a »

edd-- wrote:
Sat Jun 20, 2020 7:52 pm
I'm running 9.2.3. I just tried with a clean install from SD, even when booting from the SD with the eMMC (32GB) plugged in I get the tearing.
As soon as I boot without the eMMC plugged i don't have the issue. I created a small video to illustrate:

https://youtu.be/ztJPe4DHIlk.

So far I have not seen the issue while playing video's, but I don't have any high framerate 4K video's to test with ...
Are you using petitboot(boot switch in SPI position) to boot or booting directly from eMMC or sd card.

Post Reply

Return to “Other OS”

Who is online

Users browsing this forum: No registered users and 1 guest