CJS wrote:
> Yes, that is also what I see.
and are they the translations you expected?
CJS wrote:
> With unplug I suppose that you mean unplug the power supply.
yes that's what I meant.
CJS wrote:
> If I navigate to a track in my library and press the PLAYPAUSE key then
> indeed the track starts to play, both before and after installing the
> test jivelite. If this means that you can't map KEY_PLAYPAUSE to
> KEY_PAUSE without breaking other remotes than I agree that we can better
> stop our attempts to make the PLAYPAUSE key functional.
Yes I won't be able to change the mapping in the official builds,
however.....
CJS wrote:
>
> Observations after updating to the test jivelite extension:
> * Behaviour of PLAYPAUSE button of my remote control has not changed, it
> still behaves like a PLAY button
> * I can't enter the piCorePlayer menu item anymore
> * Behaviour of POWER button has changed. Pressing first time => Power
> off, playback stops; pressing second time => playback starts for a
> fraction of a second but then almost immediately stops again.
> After selecting a screensaver for "When off", after pressing POWER for
> the first time playback stops and the screensaver is shown. After
> pressing POWER for the second time the Now Playing screen is shown for a
> fraction of a second (and sometimes I hear a very short audio glitch)
> but then the screensaver is shown again.
I think the POWER button changes are a side effect of the picoreplayer
applet not loading, because the code in the repository jivelite build is
the same. Otherwise, I've introduced an issue that I need to resolve
before starting on the next release.
I've uploaded a new test jivelite extension that should fix the
picoreplayer applet and as an added incentive to try it, I've remapping
the PLAYPAUSE key to PAUSE just for the test build. Use my previous
instructions to install it.
CJS wrote:
>
> I am not sure why the test jivelite works different in my environment
> than in yours. Maybe it is because I have a different Raspberry Pi Model
> (ZeroW) that uses different kernel modules? I am just guessing now.
> For now the "normal" jivelite version that comes with pCP 6.1.0 works
> better for me, so I will revert to the configuration that I had before
> updating to the test jivelite.
> Thanks for your time and let me know if you have additional questions.
Very unlikely that different kernel modules armv6 vs armv7 would cause
the problem.
To switch back to the jivelite package in the repository, if the new
test build still has issues, without having to reinstall jivelite.
Code:
--------------------
tc@rpi27:~$ *ceo*
tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz
http://repo.picoreplayer.org/repo/10.x/armv7/tcz/pcp-jivelite.tcz*
tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz.md5.txt
http://repo.picoreplayer.org/repo/10.x/armv7/tcz/pcp-jivelite.tcz.md5.txt*
tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *pcp br*
--------------------
Ralphy
*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
