Closed GoogleCodeExporter closed 9 years ago
The current player is always shown on the "Now playing" screen.
On the other screens that section shows other information (e.g., if your
browsing by folder it shows the folder name, if you're looking at songs
(whether by artist, album, and so on) it shows you the number of items you're
looking at.
There's a "Players" option on the overflow menu (the three dots at the top
right) which lets you switch between players. On tablets that option is
generally always available, as the screen is wide enough to always show it.
It would be possible to always show the player name in the top left, with a
drop-down menu to select between different players (something like this
screenshot -- http://developer.android.com/images/ui/actionbar-dropdown@2x.png)
but then the other information couldn't be displayed. Well, not without taking
up another block of horizontal space to show that as well.
I don't have a strong opinion on which information is more important to show.
Original comment by n...@ngo.org.uk
on 8 Jan 2014 at 10:04
Thank you for responding.
Personally, I'd give up other information to see which player I'm controlling.
IMHO, it needs to be displayed in bright flashing neon. (just kidding about the
flashing...)
There have been a number of times when I've started a stream, and wandered why
nothing was happening, only to realize I was controlling the wrong device.
And the drop-down menu you showed would be perfect to switch between players.
Thanks
Original comment by timothy....@gmail.com
on 8 Jan 2014 at 10:17
I do this all the time. Main reason being that every single time I start the
app, it always auto-selects the second of my (five) players - the one I don't
use much. The only way I can see to modify this behaviour is to try to figure
out why this one is second (player ID? IP address? who knows?!), and make a
different player second in the list instead.
So one thing is this request:
steal some screen space for a "select player" drop-down.
The second point I'd make is that the app should remember which player it was
controlling last time whenever you restart it (however it exited).
Original comment by drdocm...@gmail.com
on 15 Mar 2014 at 8:48
@#3
I think you have found a bug. Squeezer is supposed to remember the player is
was controlling. I'll try to reproduce, and see if I can fix it.
Original comment by kaaho...@gmail.com
on 25 Mar 2014 at 4:12
I figured this was not intentional behaviour because the android programming
bible implores developers to retain state across suspend/resume and restarts.
My thoughts on a cause (haven't determined a distinct pattern yet):
- sleeping phone causes wifi to shut down?
- squeezer seems to be getting killed in the background if I run something heavy, even though the notification is active (player is playing) when I restart...
Original comment by drdocm...@gmail.com
on 26 Mar 2014 at 8:59
Also the squeezer app doesn't survive being backgrounded while playing
(notification stays active), then pausing playback by another means.
Notification goes away and ultimately won't come back if you don't go back into
the app. This isn't the app's fault and I'd expect this behaviour. From this
point on you're susceptible to the phone sleeping and disabling wifi.
I can't seem to reproduce the problem unless squeezer is forced to run for even
a very brief time with wifi link down.
Original comment by drdocm...@gmail.com
on 26 Mar 2014 at 1:10
Bingo. I can't reproduce it because I wasn't running my Joggler.
Facts:
- joggler running squeezeplayer application:
Player Model: SqueezePlay
Firmware: 7.7.2-r1821:9626MS
- Logitech Media Server Version: 7.7.2 - r33893 @ Wed Mar 14 05:46:46 PDT 2012
Steps to reproduce:
- Start squeezer, select ANY player (apart from the joggler)
- back to home screen
- hit "running apps" menu, kill squeezeplayer app
- restart squeezer - now it's controller the joggler...
Original comment by drdocm...@gmail.com
on 26 Mar 2014 at 1:30
I meant "kill squeezer app", obviously..!
Original comment by drdocm...@gmail.com
on 26 Mar 2014 at 1:31
Actually, I was wrong when I said it forgets "any" player - in fact it's only
if I select the first player in the list it won't be remembered - the app
always defaults back to the second (currently the Joggler). If I select the
joggler itself or any of the subsequent players in the list then those will be
remembered at the next restart.
It just seems to have a mental block on remembering the first player..
First player in the list is a Sqbox Touch:
Player Model: Squeezebox Touch
Firmware: 7.7.2-r9663
Player MAC Address: 00:04:20:22:d9:70
This player is always reported first on any query of player list from LMS, the
Joggler always comes second. Don't know what the sort order is based on.
Original comment by drdocm...@gmail.com
on 27 Mar 2014 at 1:47
I have found the problem now. Your comment that it is the first player which is
not remembered got me on the right track.
I will create a fix for it, and discuss with Nik how to get it released.
The request that "Every screen should show player being controlled" remains.
Original comment by kaaho...@gmail.com
on 28 Mar 2014 at 10:54
"The current player is always shown on the "Now playing" screen."
That's right, but when I start the app the overview screen is shown. Therefeore
I first have to check which player is selected, before I start playing music.
So in my opinion the currently selected player should be shown on this screen,
too.
Original comment by thenk...@gmail.com
on 12 Aug 2014 at 7:37
This is done in the upcoming release, which is in beta now.
If you'd like to sign up for the beta version:
1. Join the Squeezer Beta tester community on Google+, at
https://plus.google.com/communities/104836508948545556562.
2. Once you've joined you should see an opt-in link at
https://play.google.com/apps/testing/uk.org.ngo.squeezer. Go there and opt-in
to become a tester, and you'll receive beta versions of the app (basically,
release candidates for the next release).
Original comment by kaaho...@gmail.com
on 13 Aug 2014 at 7:40
Version 1.1.0 and above include the currently controlled player in the action
bar.
Original comment by n...@ngo.org.uk
on 4 Nov 2014 at 3:10
Original issue reported on code.google.com by
timothy....@gmail.com
on 7 Jan 2014 at 4:44