You might need to replace "DE" with the appropriate regdom for wherever you are, i.e. FR for France. Also, don't forget that RPi3 wireless has terrible range. You need to find a way to send us "dmesg" log so we can see what's happening.
Posts by chewitt
-
-
SMB1 is being deprecated and removed throughout the entire Windows ecosystem and "browsing" is an SMB1 feature, so once LE/Kodi and MS things update beyond a certain point you need to learn a new way of adding SMB shares. The 8.2.1 release notes are fairly comprehensive on the topic, but you will have to go read them instead of looking for an easy button to press - because there isn't one.
-
Some of our community developers are burning out from the hassle of trying to support an ever-increasing amount of sh1t hardware that requires over-complex installation hackery and a ever-increasing population of users who are a bit too self-entitled and whiny when their $25 box doesn't deliver the $500 experience they were inappropriately expecting. At the moment I'd estimate that 85% of the support posts in this forum come from devices that represent 8% of our userbase. That's not sustainable.
So we are going to publish a Generic S905 image that community developers can contribute proven changes towards while the core project handle the boring stuff related to building and releasing things. It means the image will have a considerably slower release schedule; but should become more stable over time. To drive stability we will not adopt high maintenance features like "install to internal" storage which are responsible for at least 50% of the installation issue posts in this forum.
Community developers have also decided to bump up to the Android 'Nougat' kernel. However, Amlogic 3.14 kernels are full of crap code so newer doesn't necessarily mean better, and there is a very real risk that this introduces a slew of new bugs. Our challenge is to do as little as possible with this build project as ultimately it will be thrown under a bus the moment a viable mainline kernel option exists. Sadly that will not happen within the Kodi Leia release schedule, so this is a stop-gap. Albeit a stop-gap that will be an important learning experience for the project.
-
It reminds me of issues seen occasionally when people import configuration from other Kodi platforms (e.g. Win to Linux). Best thing to do is use the log upload function in the LE settings add-on, then share the URL so we can see the config of things and what kind of media is being [not] played?
-
If you have an RPi3 it's technically possible to boot from USB media (solely) instead of mSD cards.
-
Either use the USB/SD creator app linked at the top of the downloads page to create a bootable card *or* click the big drop-list link on the same page and select "Raspberry Pi v1 and Zero" and you will see the direct file links for that hardware.
-
I'm interested in the wireless chipset inside the USB dongle. The information you posted about the Ultra2 is irrelevant.
-
Our RK support is focussed on current generation SoC chipsets with ARM Mali GPU's because that's where RK themselves are focussed in their push towards mainline kernel support. From a project perspective it's not "economically viable" to look at older chipsets when current generation boards and boxes can be had for $40.
-
Please report the issue to Kodi developers via Kodi forums.
-
Kodi in LE v8/v9 uses VDPAU for nVidia cards, which is no longer developed, and VDPAU only supports 8-bit HEVC. LE v10 will not support X11, so unless nVidia get their VDPAU replacement sorted in the next year, LE 11 will not support nVidia cards

FWIW, the un-powerful Intel CPU supports 10-bit HEVC today, and the future GBM/V4L2 graphics architecture that will replace X11 in LE.
-
You need to tell us what chipset is in the device. Then (and only then) can we give an answer.
-
Code
<sources> <video> <default pathversion="1"></default> <source> <name>SOURCE_NAME</name> <path pathversion="1">smb://user:password@SERVER/SHARE/FOLDER/</path> <allowsharing>true</allowsharing> </source> </video> </sources>^ that is how something looks in sources.xml .. I find editing the file directly is faster than figuring out things in the GUI.
-
Have a play with a Milhouse/Leia build to see if the issue still exists there. If it does, report to Kodi developers via Kodi forums.
-
The only affiliate link that would make sense for the project is digitalocean.com where we host things.
Good old fashioned cash via paypal is always appreciated, or a tee-shirt via teespring

-
Kodi alpha 1 is probably shortly after new year, but no guarantees. LE will probably release something soon-ish after Kodi, but not for all build projects initially as some of them are still a bit "work in progress" and need more time to settle.
-
If you want to render 3D images all that power is useful. If you simply want to play hardware decoded video, it's irrelevant.
-
You're in the wrong forum for advice on where to download content
stealingacquisition tools. -
The Intel GPU is perfectly good to use, and it works, so why bother with the nVidia one?