Posts by Elicity
-
-
HiassofT Thank you very much, you guys are too fast
edit:
So I updated to latest LE12 (2025-04-04), Immediately for some constructive feedback.
The black screen problem has been fixed, yay!
However the other issue i still present:
Everything works fine except for Zoom Mode, when I cycle to that nothing happens. If I do it from the video-menu it does work, but I have to increase or decrease the percentage and set it back.
(afaict the zoom value is not applied when switching to zoom mode)
-
Its working fine for everything else, just not x265. The GUI-colors are off too while playing, its weird
Something isn't right with x265, but it does not really matter. I'm happy its playing at all. I'll report it once I have some more time on my hands.
-
Thanks, that saves me the trouble
edit:
still broken on nightly-20250328-47483e0 (RPi5.aarch64)
-
I dont know if this is related, but I have reported some issues with x265 here
-
I tried doing this and there were some issues. I just unpacked the .kodi/userdata folder. That seemed to have worked fine. However the guisettings.xml caused my 4k screen to display as 1080p, leaving me with 25% to work with. I fixed that with:
Codesystemctl stop kodi cd /storage/.kodi/userdata mv guisettings.xml guisettings.xml.bak awk '/<resolutions>/ {print " <resolutions />"; next} /<\/resolutions>/ {next} {print}' guisettings.xml.bak > guisettings.xml cd $OLDPWD systemctl start kodi
Oh, and don't forget to extract your .ssh folder, almost locked myself out
Also deleted the Addons33.db, to prevent x86 plugins to reinstall.
That was it for me
-
Well this problem does also appear on the rpi5.
And there is an additional issue where by changing the zoom percentage on x265 video will black out the entire screen (while playing the video). Stopping/Starting/Restarting KODI service does nothing to get video back. So I'm forced to reboot the rpi5 or powerdown/poweron.
Can someone confirm ?
-
but HDMI needs to be reliable.
I looked at mainline again and I think the earliest would be 6.15, now that would be somewhere in July which also includes audio support. But to be honest I think if 26th of December presents us with an image we are very lucky. I'm sure they are working very hard to get it all in before 6.18 which afaict will become the latest stable.
All n All, patience is key
-
I bound a remote key to switching Display Modes, its easier than to go into the menu all the time.
Now when I press a button on the remote I can easily cycle to the mode I want for a particular video.
Everything works fine except for Zoom Mode, when I cycle to that nothing happens. If I do it from the video-menu it does work, but I have to increase or decrease the percentage and set it back.
I'm using the generic x86/64 image.
-
So, yes it is a workaround, but not for a design flaw that the Pi created.
That makes sense, preventative measures do not work after the fact. Nice I learned something today
-
Thank guys, a 2GB it is then.
Can I change the eeprom option from LE itself or do i need to boot into rpi-os or raspbian ?
It is by design
Like buying a car that intentionally leaks gas, just for those that want to pull a trailer. Seems like a design flaw workaround to me.
Thanks for the advice, it really helped me
-
Hi,
I read somewhere that 2GB is enough for running LE, does that still hold up?
Is there any reason to spend $15 extra on a 4GB ?
And has this fix been applied ? Just curious.
Reducing Raspberry Pi 5's power consumption by 140x | Jeff Geerling
All thoughts are welcome, especially when you run LE on an RPI5
Thanks in advance
-
-
My cousins wife is Flemisch and I setup two language profiles one English one Flemish/Dutch.
She could not find Movie sets/Film sets. After some quick phone support it appears to be mislabeled as "Instellen".
So where to report this translation error ?
Is there a way to rename it manually ?
-
Just read the rk3588 status from collabora, I saw audio being added in 6.15 which is kind of a big deal. That only leaves CEC afaict to get a functional kernel. Now I'm not planning to get into this until 2026 as I expect development to slow down and support to pick up.
Nevertheless , thank you for your work and I might be tempted if a NanoPi-r6c-r6s or NanoPC-T6 build shows up by then.
-
Would it possible to add more profiles? One for VPN users for example.
And would this go into the LE-backup/restore ?
The unit file in LibreELEC (official): 12.0.1 for WireGuard is different compared to the wiki.
The one from the wiki works, the one in LE 12.0.1 unfortunately does not. I updated mine to be variable, however it is limited to the first VPN connection found. This way I do not have to edit
[Unit]
Description=WireGuard VPN Service
After=network-online.target nss-lookup.target wait-time-sync.service connman-vpn.service
Before=kodi.service[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/sh -c "connmanctl connect $(connmanctl services|awk '/vpn_/{print $NF;exit}')"
ExecStop=/usr/bin/sh -c "connmanctl disconnect $(connmanctl services|awk '/vpn_/{print $NF;exit}')"[Install]
WantedBy=multi-user.target -
LE has 3 firewall options: off, home and public.
The home option blocks everything incoming except private networks:
- 192.168.x.x
- 172.16.x.x
- 10.x.x.x
However the 10.x.x.x is also used by WireGuard, and would leave it potentially open to access from your VPN provider.
Is that a correct assessment ?
-
Hi,
For some reason I cannot get WireGuard to work. I did the following:
1. Copied wireguard.config.sample to wireguard.config
2. Changed Host, WireGuard: Address, PrivateKey, PublicKey, DNS from VPN Provider Config (proton)
3. Deleted WireGuard.PresharedKey because it is not provided.
4. Config:
Code
Display More[provider_wireguard] Type = WireGuard Name = WireGuard VPN Tunnel Host = 185.107.56.*** WireGuard.Address = 10.2.0.2/32 WireGuard.ListenPort = 51820 WireGuard.PrivateKey = *** WireGuard.PublicKey = *** WireGuard.DNS = 10.2.0.1 WireGuard.AllowedIPs = 0.0.0.0/0 WireGuard.EndpointPort = 51820 WireGuard.PersistentKeepalive = 25
5. Listed connections:
Code# connmanctl services *AO Wired ethernet_000000000000_cable * d WireGuard VPN Tunnel vpn_185_107_56_*** #
6. Connected to tunnel:
7. Ran some tests:
Code
Display More# ip route default dev wg0 scope link 10.2.0.1 dev wg0 scope link 185.107.56.*** via 192.168.1.1 dev eth0 192.168.1.0/24 dev eth0 scope link src 192.168.1.2 192.168.1.1 dev eth0 scope link # ping -c1 10.2.0.2 | grep ttl 64 bytes from 10.2.0.2: seq=0 ttl=64 time=0.248 ms # ping -c1 10.2.0.1 | grep ttl # ping -c1 1.1.1.1 | grep ttl #
8. In conclusion: it does not work.
Please enlighten me: what am I doing wrong ?