Finding the problem should be easy because there's only been a few commits since the last release. I'll put out a new build soon.
EDIT: 20170626 uploaded for the RPi, please test. Only downgraded kernel.
As for your ps3 controllers, they should just work. libevdev is just a library it has nothing to do with the kernel or bluetooth.
Hey escalade,
Just tried 20170626 and still have no bluetooth adapter unfortunately.
Hi kszaq,
Is it possible for you to arrange your directory tree without the folders for each build?
Similar to milhouse. - Index of /builds/master/RPi2/
This allows us to use the site as an update channel within Libreelec.
Unless there's another way I don't know about?
Thanks
HOW TO:Provide Logfile - LibreELEC (this could be found by putting "Libreelec logfiles share" in the address bar)
BNEP is not needed and has never been included with RPi builds official or otherwise. There is 0 difference in kernel configuration from my previous release. Not excluding the kernel as a possible cause but it seems strange as it's a minor release.
You have a RPi or RPi2? In that case you have an external bluetooth adapter? Always provide full details about your hardware and full logs.
Apologies, I didn't realise Kodi logging enabled system logging in Libreelec.
RPi3 and only using the internal adaptor.
Thanks
Kodi has nothing to do with hardware support. Upload the logs from the "Logfiles" share.
I'm not sure what you mean by "Logfiles" share, however here is the output from the journal when restarting bluetooth.
Jun 23 01:45:28 LibreELEC systemd[1]: Stopped Bluetooth service.
Jun 23 01:45:28 LibreELEC systemd[1]: Started Bluetooth service.
Jun 23 01:45:28 LibreELEC bluetoothd[893]: Bluetooth daemon 5.44
Jun 23 01:45:28 LibreELEC bluetoothd[893]: Starting SDP server
Jun 23 01:45:28 LibreELEC bluetoothd[893]: kernel lacks bnep-protocol support
Jun 23 01:45:28 LibreELEC bluetoothd[893]: System does not support network plugin
Jun 23 01:45:28 LibreELEC bluetoothd[893]: Bluetooth management interface 1.14 initializedHopefully this is okay? Looks like a problem with the kernel bump to .6?
No logs no problem.
Fresh install and problem persists.
The logs really aren't giving any information. (That I can see.)
Have tried this on 2 RPi's now.
Hi escalade
20170621 build for rpi appears to have broken bluetooth. Libreelec is showing no adapter found. Nothing appears in logs.
Rolling back to 20170615 and bluetooth is fine.
Probably because libevdev isn't included in the RPi image. I've added it as a dependency to reicast and a 20170615 image is uploading try that
Thank you! (Except I need to disconnect my keyboard before I pair my PS3 controller otherwise it wont work??)
Got Crazy Taxi running great!
Is there anyway to launch directly from Retroarch rather than emulation station? Or does reicast need to be compiled for libretro for this to work?
Hi escalade,
I notice you now have reicast in the RPi builds, it runs very well however I can't get it to recognise any bluetooth controllers. Namely PS3. It does however work fine over USB with joystick_device_id = 0 enabled.
Any ideas how to get this to work? I'm getting a libevdev error when launching.
Cheers
Saves me the trouble. Thanks 
Thanks, didn't even realise there was a test branch.
Will compile later and have a play around.
Hi escalade,
Any chance of updating Retroarch to 1.6.0?
Cheers
Hi bite_your_idols,
Love what you've done, every emulator seems to run very smoothly without much hassle.
Just wondering if you have plans on compiling the reicast core into this one?
There are a few dream cast titles that do run pretty well on the rpi.
Cheers
Is anyone else having issues running psx on a rpi3?
Every other emulator runs fine, however psx rearmed just lags, audio stutters and runs very slow in general. Have tried a handful of different bios files and no difference. Very strange. Recalbox and Retropie on the same system runs absolutely fine.
Thanks,
This makes sense however the exact same streams do not have this issue when accessing them on another device within the network. It seems to be a specific problem to the rpi3 only. This is why I am convinced it is a local problem.
Faster I/O on the card will always help the overall LE/Kodi experience, but the "slow" I/O on the card is still many times faster than your ISP connection so buffering issues are about ISP/latencies not hardware. The read-ahead setting in the buffer can be increased, but cache tweaking only ever solves local network performance issues, i.e. bursty wifi and drop-outs, not "my internet connection isn't fast enough" type issues. As a broad rule unless your internal network is crap (in which case the solution is fixing your network) cache tweaks should not be needed.
Thanks, i've just done a speed write test on the card and am getting 10mb/s so I don't think that is the problem. I've got a 100mb/s connection and am getting close to these speeds on the rpi so I am at a loss as to what is actually causing this.
Is there a reason that even with the advanced settings my cache is still not filling the ram as it is meant too?
These are my current settings.
<advancedsettings>
<cache>
<memorysize>139460608</memorysize>
<buffermode>1</buffermode>
<readfactor>4.0</readfactor>
</cache>
</advancedsettings>
They seem to be what Krypton dictates as the new requirements in their wiki yet these are not making any difference whatsoever. It just seems odd that it's only the initial cache causing problems and then the streams works flawlessly for hours on end afterwards.
The only difference I can see in the connection between the rpi and any other device connected in the house is that the ping rate on the pi is somewhat higher. I am unsure what is causing this because even when wired it stays higher.
Hi,
I'm having problems with video streams on 8 with a RPi3. When I initially open these streams for the first 30seconds or so the streams are struggling to build up a cache and causing stuttering. After this initial period the stream then works flawlessly and will run fine for hours on ends. This is happening across all streams and formats regardless of server.
I have tried using WiFi and ethernet connections but am having the same results.
I have edited my advancedsettings.xml as per the Kodi 17 tags but this has made no change. Cache does not appear to be filling the RAM whatsoever no matter how I edit the XML file.
I'm starting to think this problem may be due to the fact Kodi is caching to my SD card which has a slow write speed. ~2mb/s. (Yes I need to replace it). Is this a likely cause?
Can anyone suggest why the advanced settings are not caching to RAM or alternatively. Is it possible to redirect the Kodi directory which caches these streams to a USB flash drive which has a much higher write speed?
Thanks
