Specifically for HK I have no official information, but I have official information about such requirements from corelec from another manufacturer. I can send you in PM the details of the official representative, what would you do he got this conversation. He didn't ask me to keep it a secret, but the exact details of the deal, I'm not authorized to divulge.
That's the problem, these are private deals between Khadas, HK and CoreELEC etc. it's not for you or I to discuss them in public.
This forum is not a platform for spreading unsubstantiated misinformation on other operating systems.
I am privy to all CE matters being part of the team and say you are BOTH wrong in the quotes you have made.
Please edit to correct your errors.
Hmmm... you don't want unsubstantiated misinformation on other operating systems to be spread on this forum (when it's about CoreELEC) but you're perfectly happy for it to be spread on your own forum when it's about LibreELEC. Bit of a double standard, wouldn't you say? At the time, we didn't come on to your forum full of righteous indignation (mainly because we knew it would have been pointless, and only lead to unnecessary confrontation) so please don't bother with that here.
And just for the record: LibreELEC has never received $3000 from WeTek (or any other vendor for that matter), nor has - as claimed by Adam elsewhere - LibreELEC ever been paid/funded by any hardware vendor to develop for any platform. Adam knows nothing about LibreELEC finances, which are based entirely on goodwill donations.
But yeah, KyleS / buzzmarshall let's keep it factual, please. And focused on LibreELEC.
Edit: added image of original linked post, taken prior to stealth edit: original wording.
I checked m,y Pi3B+ LibreELEC setup and it says I have an update......however the versioning seems off.
Is that right? Does it go from 9.1.002 to 9.0.2?
No, that looks like a cock-up... 9.1.002 is the 9.2 Alpha2 release which is more recent than 9.0.2, so I'm hoping it's an issue on the backend update server. We'll look into it.
You should upgrade to 9.1.501 (9.2 Beta1) which we released today - you may need to manually apply the upgrade by downloading the tar file to the Update Samba share (as these are alpha/beta releases they're not being rolled out automatically to all users).
Hello,
I parsed the forum about this issue, reinstalled Librelec, add pwds, PC and PI4 are on the same wired network, but I still cannot add smb from kodi. Always "Operation not permitted" so i cannot even access to id/pwd.
For information, i used it without any issue on Zidoo X9S & Kodi 18+ on the same network, with the same configurations;
Thanks for advance,
François
What is the PC - a Windows PC, or a Linux PC? If Windows, is it up to date with all the latest security fixes from Microsoft that disable SMB1, or are you still relying on SMB1 support in the Windows PC? If Linux, have you enabled SMB2/SMB3 support (not normally enabled by default on most current Linux PC installations)?
LibreELEC 9 doesn't support SMB1 out of the box and this insecure protocol needs to be enabled manually in LibreELEC (SMB1 is strongly not recommended).
If the Zidoo is working, have you applied the same SMB Client settings from Kodi > Settings > Services > SMB Client, to the RPi4?
Just noticed you posted a crashlog - you appear to be running an official x86_64 Generic LibreELEC 9.0.2 build so that should rule out zstd as being the cause of the error, but why you were trying to install a "9.0.1 build" that included "t8mini" in the filename baffles me. I would suggest asking on the Droidbox Forums: t8-mini.78
Edit; WTF, the crashlog was from someone else's thread and I thought it was yours. Sorry!
I still don't know how that offending update got into my .update folder and what it is supposed to contain. It has "t8mini" and the number 9.0.1 in the title so it probably originated from Droix, but they have disclaimed any knowledge of it. Don't know what the 9.0.1 indicates, either. But it certainly seems to have a bug in the install script.
It certainly didn't come from LibreELEC!
Without knowing how this 9.0.1 Droix image has been built it's difficult to say what the issue is. My guess would be that whoever built it may have switched to using zstd compression for squashfs - the problem being that zstd decompression isn't supported by pre-LibreELEC 9 kernels meaning a build such as 8.2.5 (or earlier) will not be able to mount the new SYSTEM image.
zstd is supported by all LibreELEC 9 kernels, and (official) LibreELEC 10 releases will be using zstd squashfs.
9.2 Generic download is not updated and links to 9.1.002
Issue with the Wordpress caching server, should be fixed now...
Are there any RPi 4 specific changes between 9.2alpha2 and 9.2beta1? It looks like the notes were mostly copied over from alpha2....
Probably not so you'd notice, but it is using a new 4.19.y kernel with various bug fixes and new firmware for RPi4. Visual issues such as tearing in the GUI unfortunately remain.
event this build also not the latest one i guess, it was uploaded on 2019-09-03
Date when the images were built, not when they were uploaded to the release server - since then they've been undergoing testing, and were only published today.
Is it possible to automatically update from v 9.2 Beta1 to the next (eventually stable) releases without losing the database and settings etc?
Kodi only change database format with each major release, so if you're already on Kodi 18.x then you should not have to update database again until Kodi 19.
Is the version of 9.2 Beta1 = 9.1.501?
Confussing numbering and btw not available over the download_new web page
Yes... and I agree it is a little confusing, but our update process is based entirely on numbers so we have to use something less than 9.2.0 to represent builds that are not yet quite 9.2. Prior to this beta we were using 9.1.001, 9.1.002 to represent the "alpha" builds, so you can see there is a progression towards 9.2 with each release.
Is no one having scraping issues in 9.1.002? Seriously - this is becoming a worry.
I'm not aware of any issues right now - there were some issues a week or two ago because one of the websites updated their API but I believe that is now resolved (API change rolled back). Can you post a debug log of you scraping a movie that is scraped incorrectly? Is it every movie or just some movies?
Good evening, is there a cause/reason the advancedsettings.xml will not work?
Tried with a raspex version/image (kodi 18.3 Git:20190718-b0e4133d0f) and my mariadb is able to connect.
For the w0man acceptance factor i would prefer the libreelc image instead
regards
Mario
advancedsettings.xml is working fine (41,000 users can't all be wrong!) and if it's not working for your then you've probably made a mistake somewhere, or something else isn't working as expected, in which case please post your kodi.log as this typically reveals the underlying issue.
If you're not able to connect to a MariaDB server from LibreELEC then enable "Wait for network before starting Kodi" in Settings > LibreELEC > Network > Advanced Network Settings - this is a common issue as Kodi frequently starts before the network has been brought up.
Broke SMB shares
Not intentionally - SMB shares (smb://) is working fine here. What issues are you seeing, with what server, please post a debug log.
Always test with stock Estuary...
Tried to reinstall, no success.
Tried to reinstall Netflix, or LibreELEC?
I have seen the Netflix settings appear without text, restarting Kodi fixed it.
I formatted the sd card to verify it wasn't a corrupt copy. Same problem. (I haven't verified the .img.gz I downloaded has the right md5/crc. I don't see where that's listed making it hard to check.)
Pastebin as requested:
External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.edit: Also, I'm using a new 3a power plug.
The crash you listed is one I've seen once, but haven't been able to reproduce so far which has made tracking it down difficult (it's somewhere in Kodi). It's odd you are getting this crash so often.
I'm (fairly) sure if you keep trying you should be able to connect to your network. Not ideal I know, but this situation does seem a little unusual (based on local testing and lack of similar feedback so far).
I'm on a Pi 4 and when I try to connect to wifi with the correct password (wpa2, 5ghz) half of the time it gives a Network Error Input/Output Error, and the other half of the time the Pi suddenly reboots without warning.
(I don't see a Pi section to report this. My apologies if this is the wrong location.)
Are you sure your system is rebooting, and that Kodi isn't crashing? If your system is actually rebooting then this might suggest a power related issue (or faulty hardware).
Can you see if you have a crash log in /storage/.kodi/temp/kodi_crash.log (and upload it to a pastebin site if you do). Thanks.
