Posts by grael

Cpu clock is dynamic.

It changes depending on cpu activity.

600 MHz is idle speed, not max speed.

For music, I don't use tv screen to browse on my Pi.

I use yatse on an android tablet, much smoother and efficient.

Quote from MoonKid

Keep in mind there are other types of users - you are not the center of the universe.

Ok...

So my own personal universe has just been convinced not to answer your questions anymore.

Ahem... This is not a bug, and it's not a Kodi thing...

It "could" be done in libreelec, but really, putting the sd card on your computer to edit config.txt is not that complicated. And there, you can copy/paste the keys, setting them with a tv remote would be painful

Mpeg2 is the standard used in dvd and dvb sd. There is a software codec in libreelec, but the hardware codec is better (and put less strain to the pi2)

VC1 is used in a few percentage of bluray discs. VC1 files are unwatchable on the pi without hardware codec...

You should be able to manualy update on your rpi1 b with a rpi2/3 image (image file in the update repository then reboot).

After second reboot, the rpi1 will hang but the same micro sd will then work fine on a rpi 3.

Information read on the third "additional testing note" on milhouse testbuilds thread here:

LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

Please notice "Note: Prior to migration I would recommend disabling all overclocks, as a Pi1 overclock may not work successfully on a Pi2, and vice versa."

But making a backup before is still a good idea.

Quote from Draega

My question would be is it just a prank? Or are they trying to make a point?

You are probably right.

"See what could happen if you continue to promote illegal use of kodi system"

Try to set the mixer on the command line:

./spotify-connect-web -u USERAME -p PASSWORD -m PCM
Or
./spotify-connect-web -u USERAME -p PASSWORD -m 0

It is complaining about alsa mixer.

Check your config.txt, then try aplay -l and amixer commands

And it can be a specific issue in milhouse build. You should first try with the stable libreelec build

I just downloaded the LibreELEC-Generic.x86_64-7.0.0 tar file.

Check the size (212 029 440 bytes)
I see 4 files under target :
- SYSTEM
- KERNEL
- SYSTEM.md5
- KERNEL.MD5

Refresh your browser

Quote from newphreak

Hmm, this looks fun and Spotify connect seems to be dockerized.. time for me to find out what that is and how it works.

ps: i have no clue what I'm doing

sent from my phone, typo's expected

Docker not required.
This package contains all that is needed for Rpi2 and Rp3, and works fine:

Releases · Fornoth/spotify-connect-web · GitHub

Just uncompress this archive, add your spotify_appkey.key and start:
./spotify-connect-web -u USERAME -p PASSWORD

You need alsa for it to work, so
dtparam=audio=on
in /flash/config for jack and hdmi

For hifiberry and likes, you just need to activate the according overlay
Config.txt - OpenELEC

Et voila, your Pi (2 or 3) is a spotify connect device

Good luck with this project, I'll be following closely