Posts by infinity85

    After seeing this thread, I was curious whether my OLED 20x4 would run on LibreELEC (Krypton) v7.90.008 ALPHA for Odroid C2.

    Well.. it doesn't... it starts already with the missing i2c-2 address :D :

    1. HD44780: I2C: open i2c device '/dev/i2c-2' failed: No such file or directory

    On wrxtasys 7.0.x / 7.1 builds it works for i2c-2 and i2c-1. Unfortunately it is wired for i2c-2 right now, so I cannot check i2c-1 easily.

    Besides the question why i2c-2 is not present?, I still have two more questions:

    • I have to use a custom compiled HD44780 because my controller (SSD1311 is not fully compatible to HD44780). On my Raspberry Pi's and on my Odroid C2 with 7.0.x builds I simply had to put the modified driver and config files (, LCDd.conf) into .config directory and LCD.xml into userdata directory. The display worked then right away after enabling HD44780 displaydriver in LibreELEC Configuration / Services. LCDd.conf contained the path to my custom "/storage/.config/"
      Where do I have to put those files now. LCD.conf in .config seems to be ignored?
    • There are no settings left in lcdproc (no dimming, no scroll speed, no alternative character choice). Is it coming back, or did you dig those configuration options somewhere else?

    Sweet! The wireshark info is nice to see. Didn't know that wireshark also lists this info, thanks for this hint!

    Well yeah, then it's indeed solved. I'd say allocation = 0 is a good setting as future default.

    Already marked it as solved ;)

    Regarding the passwords issue with special characters like ! and * that I mentioned in my Post #15: If somebody has a clue, feel free to share it :)


    thanks vpeter  :)

    Then it's more of a bug in Windows 7 and a rather bad linux default setting of 1MB.

    I'd say the actual Issue is solved then ;)

    I guess your VM has a filesystem Blocksize of 1024 bytes, right?
    Just asking, because my Windows 10 Laptop has 4096 bytes (If I believe the "size on disk" propertiestab of a <1KB file).

    Here we are...

    Tried allocation roundup size = 4096
    Windows explorer showed me then 4KB instead of 1MB (for files below 4KB size)

    Then tried allocation roundup size = 0
    Windows explorer showed me then 1KB instead of 1MB (for files below 1KB size)

    So I guess for a default smb.conf in the future allocation roundup size = 0 would be the best.

    After reading your links and googling, my conclusion is that the actual "issue" is Linux default allocation roundup size = 1048576, whereas Windows 7 simply ignores it (I would call this a bug) and Windows >8.1 respects it (unfortunately).

    Perhaps you have the time to test allocation roundup size = 0 and allocation roundup size = 4096 with your Windows 7 machine? Who knows... may be the value =0 always results in 1KB (as a bug) or may be your system will simply ignore either setting. Just asking because I would like to know whether allocation roundup size = 0 corresponds to the filesystem (which is on my Odroid 1024 Byte as you stated) and on your Raspberry 4096 bytes then. If allocation roundup size = 0 shows 4096 on your raspberry (instead of 1024 like on my C2), then this setting is confirmed to be the best default solution :)

    And while we're talking about samba... noticed that setting samba-passwords containing special characters like ! or * in LibreELEC are somehow not working if trying to connect with windows explorer. Don't know whether this might be a windows bug, or a LibreELEC bug.

    Thanks milhouse, simpsons have always been one of the best out there :)

    Thanks a lot to pointing to these facts! I feel reassured again somehow ;). Weird... then this might really be some new weird bug in Windows 10. I know that it is showing these big blocksizes since at least may, where I discovered it because I wanted to know how large a backup of my library could get. And I almost couldn't believe this discrepancy.

    Is the SMB.conf of v7.90.008 ALPHA for C2 the same as on your RPi and NUC then?


    have a look at this: Linux Performance - SambaWiki
    The third paragraph (from this URLs position) says that 1MB is default.


    ...if the allocation size is set to 1MB (the default in Samba) then...

    I don't really understand that. Do the other systems use a different samba version then, so that your systems show the correct size?

    thanks a lot for the mini guide :)

    Good question and point!
    Here's the output: NcXX
    It shows 1024, so this means it is bytes then?

    I was seeing it via SMB. Whenever I tried to make a manual backup of some folders I noticed that the size of lets say the thumbnails folder on my main installation is like this:


    Contents: 3.212 Dateien, 18 Ordner
    Actual size: 212 MB (222.312.844 Bytes)
    Size on disk: 3,13 GB (3.369.074.688 Bytes)

    Thats like 14 times the filesize on the disk.

    Here's a screenshot of the by you suggested new v7.90.008 ALPHA installation on my C2:

    It implies that Blocksize is 1MB for every file. If I display those properties for one file, it will show 1MB respectively a multiple of 1MB.

    So does that mean that samba makes also some kind of abstraction for displaying and calculating filesizes (I know that it abstracts the actual filesystem)? That'd mean that I got fooled by samba :D :rolleyes: Is there any explanation for this?

    It's not a recommendation, rather an observation, but I've been using mini-toolPW for years to format for openelec and libreelec with no issues.

    Thanks! I've tried it, but I don't get it working. LibreELEC can't boot as soon as I reformat the second partition.

    I tried these two scenarios:

    1. Flashed the current v7.90.008 ALPHA and booted it the first time. LibreELEC expanded the second partition as expected. Then I reformatted this partition with MiniTool Partition Wizard Free to ext4 with 4kb blocksize. Put the card into my odroid c2 again and it refused to boot (I expected it, because .config etc. was also on this second "storage" partition before reformatting)

    2. I flashed the sd card from scratch with v7.90.008 ALPHA and then I reformatted the (now) unallocated space for the second partition (which is to be expanded during first boot) with ext4 4kb blocksize. It refuses to boot again.

    What is the correct way to get a new installation of LibreELEC onto a manually formatted disk? Or how do you reformat only the second partition as suggested by escalade in the first reply?

    Probably no thought behind it at all, as they just go with the default: at master · LibreELEC/ · GitHub

    You can simply backup your /storage, overwrite the filesystem with the block size you want and then restore.

    Thank you for your reply :)

    Do you happen to know whether this will be changed somewhen as default?

    If I understand it correctly, you suggest I put the card into my Laptop (Windows machine), use e.g. MiniTool Partition Wizard or similar to reformat the second partition with some other blocksize, yes?

    Any recommendation which blocksize / filesystem would be best?

    Thank you very much escalade!

    I've noticed, that the blocksize on the storage partition is 1MB.

    I'm aware that this is not a bug, but on the other hand it would also not be a feature request, as this big blocksize is a drawback, which I'd strogly suggest to get changed. Kodi mediascraping stores a lot of tiny <1KB files to the storage partition, which is good so far, but every single file consumes 1MB of storage. So even a 16GB SD card, which is only there for the Library files (Coverart, MetaData, etc.), can get full if the movie library is a bit bigger. And if you start having a music library as well, then every single of those small 4MB mp3's consume the same amount of actually 1KB small coverarts getting inflated to many MegaBytes.

    I can understand that some SD-Cards (Raspberry, Odroid C2) don't like writing a lot of small files from performance point of view. But 1MB per file for a 1byte file (it's blown up by the crazy factor of 1.000.000) is not necessary at all I think. I can't believe that the performance can benefit from this blocksize.

    Also making a backup of the library or restoring the backup takes unproportionally long because of the pure filesizes which get generated here without a reason I could get behind of :/

    Could you please change the blocksize to something like 128KB or even less? Or if not, could you explain then why it is as it is? Perhaps there is a way to change this default behavior?

    Thanks a lot in advance for some statements about this :)

    Just tried this addon on my RPi2. Absolutely great :) Thank you very much!

    Do you happen to know whether it will be possible somehow to integrate this addon as some kind of music player? I mean.. that it displays the cover and the controls (which I can see in Webinterface IP:4000) in LibreELEC GUI? So that perhaps even music visualization would be possible, just like as if it is with the kodi music player?

    Also I tested it with Yatse remote, and here it's the same: Media controls are not visible, so Yatse and Kodi doesn't seem to notice that music is running actually.

    This is not some kind of demand ;). Just want to know if it is/will be possible in the future :).

    Also... On my Odroid C2 it is not working, although the Odroid C2 has similar hardware as the Wetek Core/Play. I tried it with this preview release: LibreELEC

    Anyways, thank you very much for bringing spotify finally to kodi :)

    I didn't know that filenames are different between separate and single file export.

    Your Airwolf example confirms it. The filename "Airwolf:_The_Movie_1984-fanart.jpg" is generated out of the scrapers database (in this case apparently you aren't using movie name. It is understandable that it takes this name, but it should not do it for exporting the library backup.

    Well, I've written about this some weeks ago in the forum. But nobody paid attention and theres also no bug/issues section in at and none at their github either. How can I submit them this issue?

    Thank you both for your quick replies :)

    But hmm... I'm not sure about this... I think we misunderstand each other.

    The actual video files (e.g. mkv) are in directories which do not have colons in their names.

    After the scraping, the scraper adds all my movies and tvshows to the database/library. As I cannot find those directories in any folder of kodi after the scraping process, I guess that they are written directly into this file:

    So the issue might occur whenever I export my library to file (for backup reasons). Then those names (containing colons) are written out of this MyVideos99.db to file, thus also strictly overtaking the colons into file names. So if my assumptions are correct, there is nothing I could "rename" to follow your suggestion.
    If it is like I described, then LibreELEC should simply exchange all colons with dashes or "%3A" before writing to disk. And then it should obviosly also support those dashes / %3A when importing the library again on another machine, thus exchanging them into colons before writing/importing in the new MyVideos99.db.
    Or simply do always dashes/%3A after scraping and simply exchange the output/displaying in GUI to colons (would be safest and cleanes solution).

    So it is not about the actual directories containing the video files, which I always transfer myself from windows to the external drive connected to my odroid/raspberry (obviosly not containing any colons in names).

    How do you get these links on the SD card then back to rasberry PI? Or do you do it from the PI? Please help, I'm about to fly this thing against the wall. It's been so hard trying to get a VPN on Libreelec.

    There you go, if still necessary
    OpenELEC Mediacenter - OpenELEC Forum - VPN Manager for OpenVPN (46/63)

    But be aware of this possible security issue if using vpn services on LibreELEC and if you aren't familiar with VPN and Iptables: OpenELEC Mediacenter - OpenELEC Forum - Massive security issue:certain VPN providers on OE (1/1)


    I'm not sure whether this is a kodi related or a LibreELEC related issue, but as LibreELEC is responsible for the filesystem as the underlying OS I want to describe the issue here as well.

    When I export the video library (single file) to SD Card (ext 4) on my Odroid C2 everything is fine at first. If you then try to copy this directory for backup reasons - which contains fanart, coverart and so on of tv shows and movies - this fails. It fails via SMB, but I'm not sure if this affects also NFS or so. The same happens if I export the Library to my external NTFS USB drive.

    The issue is that some library directories have names like:


    This is only one of at least 10 directories which have colons in its filenames, thus I cannot copy the Backup off the system to another system.
    As filenames containing a colon are not allowed on NTFS and in windows (are they allowed on ext4 drives?), this behavior damages the filesystem on my NTFS HDD (connected to Odroid C2 running LibreELEC). At first I didn't notice it, because the directories were build during library export process on my SD-Card. But when I connected to the drive via SMB and tried to copy the backup before formatting the SD-Card, it was not possible. And it is also not possible to rename these directories :/. Hence (at first I thought) I could only get rid of this directories if I format the drive (NTFS drive with 3TB of data).

    Later I noticed this:
    The faulty directories are there directly after exporting... I can see them in Kodi file manager and via SMB. But I get an error if I try to access them via SMB. But then suddenly when I connect this usb-device again to my windows Laptop afterwards, these directories are missing. I'm not sure what happens to them. Also a lot of other directories from this exported library-backup were not there anymore. I assume that all directories, which were written after the faulty one (containing this colon), are broken then and not visible or corrupted. I'm not sure if they occupy space on the disk, but I think they do, even though they cannot be accessed or found anymore, but they could be seen at first before remount of the drive.

    The result of this is: The library backup (export) is always broken/incomplete immediately after doing the export because those colon-library entries are gone and some other folders which were written afterwards are also gone.

    All this sounds a bit confusing (colon directories there at first, but not accessable and not deletable; then gone completely and taking other folders with them), but something strange is happening because of these colons in filenames, which should be avoided during creation of library (and backup) in the first place.

    So... is it possible to prohibit LibreELEC doing filenames, which contain colons?

    These filenames originally come due to overtaking the series names during scraping with the default scraper addon. The above example shows:
    Tron: Der Aufstand TRON: Der Aufstand: Series Info
    Tron: Uprising Tron: Uprising: Series Info

    So LibreELEC could do some kind of validity check while making a library (to not even start doing such filenames). And then again a validy check while exporting a library for cases like these, thus it could then do a substitution for signs like colons. Windows for example substitutes a "colon" with "%3A".