mherger wrote:
> Having them separated is how the system was designed from
> the ground up.
Ok. Then I will try it.
If I install it on Raspbian directly and not via piCorePlayer, I think I
will have to do the LMS configuration (the one page in piCorePlayer
website) by hand anywhere else.
Will I have slower reactions in Jivelite on the Pi 3B+ as the data will
have to be send now through WIFI because LMS is not locally available?
I'd say no. Having them separated is how the system was designed from
the ground up.
--
Michael
___
unix
Hello!
I am using a Pi 3B+ with the 7" Display, a Hifiberry DAC+ Pro and an USB
SSD in a SmartiPi Case with piCorePlayer and activated LMS, so I have
everything in one case.
I am interested in putting the LMS outside of this onto a Pi 4B/4GB with
the USB SSD attached there.
The Pi3B+ is only
That part is perfectly normal. Most headphones/speakers will only try
to connect on when you power them on. The part that Is unusual is that
you have to repair after a reboot.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> I wonder if Jivelite is doing something. Do you have a spare SD card
> that you can start from a fresh image and just install Bluetooth.
> Otherwise, I'll have to work through to see what might be going on with
> the installation.
>
> Does everything work if you don't
I wonder if Jivelite is doing something. Do you have a spare SD card
that you can start from a fresh image and just install Bluetooth.
Otherwise, I'll have to work through to see what might be going on with
the installation.
Does everything work if you don't reboot?
piCorePlayer a small
paul- wrote:
> Gearhardc,
>
> That all looks perfectly normal and correct. So if you do a reboot at
> this point, then the paired device disappears?
>
> The only thing that I can think is that something got messed up during
> the install. Perhaps try to remove the bluetooth stuff, reboot,
There is not a network manager in pCP.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you
There can be 2 devices, but then you have to figure out the event
numbers for the touchscreen vs the mouse. And there is a chance that
they get a different number during a reboot, so some extra scripting
would need to be done.
piCorePlayer a small player for the Raspberry Pi in RAM.
Gearhardc,
That all looks perfectly normal and correct. So if you do a reboot at
this point, then the paired device disappears?
The only thing that I can think is that something got messed up during
the install. Perhaps try to remove the bluetooth stuff, reboot, then
re-add it. Is
paul- wrote:
> It's because running headless, the linux kernel doesn't have the many
> sources for entropy, so it takes time. If you are really bothered by
> it, you can install a rng daemon, that will use the rpi processor
> hardware entropy generator to fill the random pool.Personally,
H34dl3ss wrote:
> Nobody???
>
> Where is /etc/network/interfaces in pCP?
In Tinycore Linux I believe its done that is static stuff in
/opt/eth0.sh
maybe this is of some use:
https://iotbytes.wordpress.com/assign-persistent-static-ip-address-to-microcore-tiny-linux/
Nobody???
Where is /etc/network/interfaces in pCP?
H34dl3ss's Profile: http://forums.slimdevices.com/member.php?userid=69595
View this thread: http://forums.slimdevices.com/showthread.php?t=111284
paul- wrote:
> Sounds like something is not getting backed up, When you pair your
> headphones, you should see
>
> [ INFO ] Pairing Successful
>
> Followed by some messages about a backup being done.
>
> I can add a screen shot this evening.
This is my screenshot after pairing:
28742
14 matches
Mail list logo
