The OS name can be changed in LE settings > System. The Kodi name can be changed in Settings > Services. Use the GUI and stop fiddling with xml files before you break something.
Posts by chewitt
-
-
16GB is enough for the largest of Kodi libraries so 250GB is a little overkill unless you also want to store/play media from the same drive; but if it's a spare go use it. If you add another ext4 drive it should show up automatically.
-
Pivos XIOS XS - Official Kodi Wiki has basic spec details so I've moved the thread to the Amlogic support area.
-
No idea. Having seen a wide variety of issues in the aftermath of the SMB changes nothing surprises me anymore. Some devices just have crap default configurations.
-
Yes, we're aware.
-
You need to ask droidbox. Their home-grown version of LE is nothing to do with us.
-
In 8.2 the kernel default mounts with SMB2. If you needed "sec=ntlm" before it is probably an SMB1 share, so add "vers=1.0" to the options.
-
If you want to be insecure, set Kodi smb client to max SMB1 and reboot. However I suggest you make the effort to remember how to enter a server and share name, because once Leia arrives it will probably have new SMB code (i.e. existing crap is ripped out) and there will be no browse option.
-
I have RPi3 and LibreElec installed. How do I add either VLC or MXPlayer as a default player for kodi?
Uninstall LE and install Android. It is not possible to use 'external' player apps in LE. It's not necessary either..
-
The connections screen GUI reports what connman (the connection manager) tells it, and connman polls the kernel which reads current values from the device driver. So the root cause will be (as normal) in the driver code. I have no knowledge of your wireless hardware, but if it an 802.11ac device there is a 99% chance it uses a Realtek chipset, so the driver code is out-of-kernel and considered to be low quality. LE has no bug to fix.
-
The OVA for vmware exists for functional testing within the developer team and is not intended or supported for real-world use and playback. If it works, that's great. If things aren't perfect we don't really care because it works 'enough' for our needs, and mouse support isn't essential on a non-Desktop OS. Keyboard navigation works fine.
-
nickr sadly it's too simple for people to comprehend
-
It's hard to comment without being a little rude. There is no actual dependency on git for compiling .. but if you have chosen to ignore a sensible workflow for cloning our source code *and* you cannot figure out the build command from the simple instructions in the wiki; the chances of your customisations resulting in a working image are low, and the developers/staff around here will be shy of getting involved. What are you actually trying to achieve with customisations?
-
Quote
Q1. How this can happen? My Windows10 PC still can browse the complete network and show all SMB network shares both on the NAS and on the LE 8.2.0 HTPCs. Browsing is a very basic operation. It should work in any SMB version.
It can happen because Win10 does something new and different from SMB1 era browsing which (whether you choose to believe it or not) was exorcised from the SMB2/3 protocol and is very very definitely not supported under SMB2/3. Basically you are not special and your issue is the same everyone else's issue.
QuoteSMB sources from Samba/NAS devices can normally be browsed via the “ZeroConf network browsing” alternative.
Q2: Unfortunately this does not fly. I can see the SMB and sftp shares of the other LE 8.2.0 HTPCs but not my legacy NAS.
Note the carefully chosen and deliberate choice of the word "normally" in the statement. "Normally" does not equal "always" so it appears your NAS is an exception to the norm and doesn't advertise shares over ZeroConf/Avahi. Most modern/recent NAS 'do' advertise, and for the lucky users with a NAS that does, it works great. It may not 'fly' for you, but there is no bug or problem to be investigated here.
QuoteI understand the security aspects of these improvement, however form usability point of view this is not an acceptable way of operation
We have prioritised security and basic functional support of SMB2/3 for users who MUST use SMB2/3 as the result of MS decisions. There is nothing stopping you from setting up things to use an insecure SMB configuration that works exactly the same as it did under 8.0. Fixing the browse function to use whatever new process Win10 uses (which again, is not how it worked under SMB1) is not an LE issue it is a Kodi issue, so you are complaining to the wrong audience.
-
I must have been half asleep -as the txt file is in /usr/lib/firmware not the brcm subfolder
Download again, the test image is updated.
-
Full debug log please - clean boot and demonstrate the problem
-
Code
dtoverlay=pi3-disable-wifiadd ^ that to config.txt and the internal wifi is disabled and won't interfere with connections etc.
-
Update to LibreELEC-Generic.x86_64-8.2.1.tar and see if it works. It's the 8.2.1 release with the extra .txt file
