Posts by VLouis

Quote from jazzlpunk

In fact, I did a reinstallation where everything looked as it should on the monitor untill I added video=HDMI-A-1:1280x720@60D to cmdline.txt. After that, I got no picture at all, not even after removing that line, so this is the point where I did another reinstallation. I did not try vc4.force_hotplug=1 at any point though.

Hi, What kind of monitor did you use for RPi4 setup, and what is the max. supported resolution? The 720p resolution is something standard for TV's. Something very strange happening with your RPi4 setup. Could be the HDMI cable, was few cases with poor quality HDMI cables what isn't supported higher resolutions (the monitor resolution?). Or the power source, I had something similar with my RPi3, when I connected something to RPi, after reboot wasn't had picture. Or TV EDID detection, could you try with another TV? Or after fresh TV setup, when the screen setup is done, try to send thru SSH the "getedid create" command. That will save the TV display parameters (EDID data) and will use it at every startup.

Quote from wyup

Havent gone to 11 stable to rule this out, I think I should, but too much work to undo.

That's the nice thing in the case of RPi, the all system is installed on an SD card, what is easy to replace.

Why you don't simple use an another SD card to try another versions?

I have a card with the latest LE 11 stable (in the case if the LE12 beta have any serious bug - doesn't got any yet...) and another card for playing with the new beta versions.

Quote from permheaddamage

Another thought: Since that user "petrel-p1" in serial console of stock fw has root previlege, maybe I can compile a Linux executable to play with efuse there.

If the efuse can be written again, I can write secure boot control bit 0 to disable it.

Hi, usually the e-fuse is OTP type ("Electrical Fuse, A one-time programmable memory"), can be write only once. I don't have the documentation of that Allwinner SOC, is not impossible to be in this case is something different, but usually this is the way how the e-fuse works.

Hi, maybe try this: After the LE installation finished, run a live linux from USB (Ubuntu...), use a partition manager (gparted) to resize the LE "user" partition to free up some space and create a new partition... About the NTFS partition... If that partition do you want to use with the LE too, perhaps you should use EXFAT instead, the NTFS sometimes isn't handled well in case of linux OS. Or if that PC will be used only for LE, the EXT4 is the best choice.

Quote from HiassofT

Random write speed is also important, especially if you use PVR which regularly updates the EPG database.

After the upgrade to LE10 - 11 I observed, the EPG update at every boot takes anoying seconds while was writen to SD card.

In LE9 was option to disable the caching of EPG data, removed in the next versions.

As I don't need any persistent EPG database (and to take care of my SD card life), I changed the path of the EPG database file to /tmp/ (advancedsettings.xml). Now the EPG is loading almost instantly (writing to RAM is always faster than any SD card)...

Quote from Operations8

will be also noticable slower?

Hi,

Not too many people have both devices to be able to compare for you... and the "noticable slower" is not an exact measurement...

Install the latest LE11 stable or the latest LE12 beta to a not too old (to not have slow read speed) SD card, insert in your RPi4 and check it. Will took for you less than one hour and you will have the answer...

Quote from LybsterKodi

The way Kodi on the RPi4 and v12 calculated the timestamp and the way Windows calculated it were different so it looked as though I have a LOT of files to copy.

Hi,

Files have some date-time properties, creation, last write, last access... probably that synchronization tool, in case of exfat partition doesn't use the proper timestamp pairs. I had some issue when I created a small program and needed to check the time when files where created. I used the last write time instead of creation time to avoid the issues.

I had too many issues with accessing ntfs partitions on linux, in my dual boot (W11 and Xubuntu) PC I'm using an exfat partition for "common files". If we talking about a media what need to be accessed with linux and windows too, the simplest solution is the exfat partition (it's not a common thing to use file synchronization tools with linux-windows devices). For "only linux", always the ext4 is recommended. And if really need, reading an ext4 partition on windows, isn't an impossible task too...

Hi,

Probably isn't an LE issue. But what you can try...

First try to reboot all devices, the Fritzbox and the device/devices (if the TVheadend server and client running on separate devices). And use the "hard reset" method, power off all, wait, and power on. I had same issue once, when my USB tuners remains blocked after strange power issue.

Check if the issue coming from TVheadend server or client side. Install Kodi on another device (Android, PC), add and configure the TVheadend client and try if working. Or you can save the channel list from TVheadend server ( http://TVheadendServerIP:9981/playlist ) and open in VLC...

Disable the TVheadend server 4.2 addon and try to install the 4.3 version.

Quote from utdrmac

I'm confused about the update messaging on the main downloads area and am seeking clarification. I have a RPi3B1.2. I don't have any 4K content; everything is either 720p or 1080p. No content is h265. I wanted to get the new TheTVDB v4 plugin but it was not available for Libreelec v9.

The update notes seem to indicate I should not upgrade to v10/v11 because I'll lose hardware h264 decoding? Is that correct? If I upgrade to v10 or v11, my Pi will perform worse?

Thanks for clarifying.

Hi, I'm using 3x RPi3 with LE, two with the LE.11.0.1 stable and one with LE12 beta (20230612 - now). I'm not a "heavy user", net-radio, some live TV, watching movie sometimes, and didn't noticed any significant issue compared with the "old" LE9. The early versions (LE10 and 11 too) had some issues, almost all fixed till now. This is my experience, you should proceed as "HiassofT" recommended, install to a spare SD card and try it. If you don't have another SD card, create a backup image with installed LE9 (search for "win32diskimager") before to install the new one.

Quote from ansey

Thanks a lot to both of you; the Audio Profiles add-on works perfectly for me! Thank you also for the additional recommendation to improve the audio quality, VLouis, which was also mentioned in the thread shared by Da Flex. Not being a pro, I suppose the best solution for me is the USB Audio Adapter. Do you know if it will just appear among the audio output devices which can be selected in the system settings, or if some additional changes have to be carried out in config.txt or elsewhere?

I'm using this, but needs some wiring and settings in the config.txt. Before to switch to I2S DAC, I tried a cheap USB adapter (what I already had it), after reboot appeared in the Kodi audio settings as a new audio output. As that Adafruit USB Audio Adapter is recommended for RPi, should work in the same way.

Quote from ansey

Hello,

I recently moved from LE9 to 11 on my Raspberry pi 3 and realised that unfortunately it is not possible any more to set the audio output to both HDMI and the 3.5mm jack (which I have connected to my HIFI amplifier). Do you know if there is any solution or workaround for this or plans to enable this option again? I use Kodi for listening to music via the hifi-system as well as watching movies using the TV speakers, and constantly changing the audio output in the system settings would be a bit cumbersome.

Best regards and thank you, Ansgar

Hi,

I'm in the same situation, LE11 installed on RPi3, sound to HDMI for video and to HiFi amplifier for listening music.

The best solution what I found is the one recommended by Da Flex, the Audio Profiles add-on.

As addition, the audio quality on the RPi3 jack output is poor (simple PWM output), if you want something better, try to use an I2S audio DAC module (ex. HiFiBerry), or at least an USB audio module (ex. this).

Quote from MatteN

Even booting from ssd connected to usb2 is faster than any sd-card.

I's not about if is faster or not. It's about if worth to gain few seconds boot time (3-5 seconds or more?) when lose the safety of keeping the boot/system separated from personal/media data. After an bad update or reinstall, the time lose will be definitively more than few seconds in the case of booting from SSD what contains few tons of media files too... Also the boot time can be reduced by limiting some writes to card (disabling the log files, in the case of PVR redirecting the EPG database to ram-disk...).

Quote from kosmonaut_75

Hello,

my plan: to connect my SSD (Samsung EVO 870) with Libreelec 10.04 image on it via SATA adapter to the USB port of my Raspberry Pi 4 and use the SSD as boot medium.

Unfortunately this does not work, nothing is displayed on the TV.

Can anyone help me?

Hello,

I have a question: what do you want to gain using that SSD as boot media?

As the LE is a very slim OS, I don't think to be a significant boot time difference (USB - USB-Sata adapter - SSD vs. SD-card reader) if you use a good quality high speed SD-card.

Always is a good idea to split in two different device the "boot/system" and the "user/personal" data. That can save a lot of time in the case of new install (or when an update going wrong...). I recommend to you to get a good small SD-card for LE, and the SSD keep it for media and other data.

Quote from gbonawitz

100% CPU utilization + jittered playback on my BluRay rips.

Hi, I suppose your hardware is working in software-decoding mode for that videos and don't have enough power for that.

You should check the media (video) codec info, maybe the recent version of LE don't have HW decoding support for it.

"Permission deniede 3: can't create /sys/class/gpio/export"

Should be checked the owner and permission of that autostart.sh file.

Try with SSH: ls -l ~/.config/autostart.sh

Hi,

As first step, you should try these commands one by one in a SSH terminal. Maybe you will get some error message (what's not visible when run from autostart.sh)...

Quote from twilightened

This happens to me all over the board, rpi3, rpi4, different power cables and sources. Doesn't matter. It is not a power issue. Streams do get interrupted and only the audio returns. It started after the big update which is called Matrix. Leia did not have this problem.

I think two "things" lead to that "picture freezing", the imperfect stream (from RPi powered HDD or TVheadend server with interlaced video and limited antenna signal) and the mediaplayer/codec changed after Leia (probably far more sensibile to stream issues).

Quote from LybsterKodi

Looks like you are right - put a 3TB powered drive in and things seem fine. Shame the Pi can't handle more power but I don't suppose plugging USB HDDs into each USB port was a design consideration.

It's a "grey zone" between powered enough and no enough power. The current consumption not "flat", it's dinamic, and sometimes, for short time, can be insufficient, leading to strange issues. I had some strange freezing issues with my RPi3B, after changed the power source, no more freezing...

And why only the picture freezing... probably it's something with media player or the codec, when in the stream some issue occurred, sometimes the video part can't be recovered, remaining blocked, meantime the audio part continued... that can explain why with a skip forward the video started working again.