Squeeze Control for Android (support thread)

[MrMennens]

This is visible when i have the phone app opened on my phone...
So what would be the best option:
- Delete the android wear app --> only use the notifications bar controls
- Keep the android wear app --> only use the notifications bar controls
- re-install the android phone app --> reinstall the android wear app --> use the full controls?

I haven't seen these options on my watch (For your information):

 

[wayne@angrygoat]

From your description, the problem is likely a connection/pairing problem between your phone and your watch.

I've seen the same thing with my LG Sport Watch and a reboot of the watch and/or phone would usually fix it. Once in a while the watch seems to require a re-pairing and not just for Squeeze Ctrl.

Those options will only show up once the watch app successful connects with the phone app.

 

[wayne@angrygoat]

Also I assume you are using the latest version of Squeeze Ctrl on your phone (2.0.3).

 

[motoxen]

Hi Wayne, I've been using Squeeze Ctrl 2.0.3 with Android 6.0 for over a year, no problems at all.

Now I'm experiencing a podcast issue where I always get a message "Connect timed out: [podcast name]" on certain feeds but not all feeds. For example Mac Power Users http://www.relay.fm/mpu/feed is causing that problem right now. I've double checked the feed name at Home - Welcome to mysqueezebox.com! and it is correct, and tried deleting and re-entering the feed name, same result.

Can you think of anything I can do to troubleshoot this issue? Thanks!

UPDATE: The podcasts that time out are all hosted on relay.fm. I tried adding other podcasts from relay.fm and they also timeout.

UPDATE2: This problem is in SqueezeBox software not allowing https for podcast streams. Nothing can be done with Squeeze Ctrl to fix it.

 

[Yirg]

Is there a way (or any plan) to support changing Previous and Next buttons to move back 10 seconds and and forward 30 seconds (like PocketCasts app)? I think this would be more useful when listening to podcasts than move back / forward a whole episode.

I'm using SB Player with Squeeze Ctrl and, other than than this aspect, I love them both.

Thanks for helping!

 

[streifenleopard]

Hi,
I have a problem that i think was dealt with before but I can't find the post any more.
In SB Player on my Moto G the last 15 or so seconds of a song are played with increased volume. after Saturnring the volume, the next track displays the same behaviour. Hofweber, this happens only on my Moto G but not on my Raspberry Pi.

 

[wayne@angrygoat]

Hi,
I have a problem that i think was dealt with before but I can't find the post any more.
In SB Player on my Moto G the last 15 or so seconds of a song are played with increased volume. after Saturnring the volume, the next track displays the same behaviour. Hofweber, this happens only on my Moto G but not on my Raspberry Pi.

Never heard of that problem before. I can't think of anything in SB Player that would cause that. Does it show a volume increase in the controller too? In the debug screen, when it happens, any "audg: volume" messages in the server messages section?

 

[wayne@angrygoat]

Is there a way (or any plan) to support changing Previous and Next buttons to move back 10 seconds and and forward 30 seconds (like PocketCasts app)? I think this would be more useful when listening to podcasts than move back / forward a whole episode.

I'm using SB Player with Squeeze Ctrl and, other than than this aspect, I love them both.

Thanks for helping!

Main problem is, there's no way to tell if the audio being played is a podcast or a song so there's no way to automatically switch the behavior depending on what's being played.

 

[streifenleopard]

Never heard of that problem before. I can't think of anything in SB Player that would cause that. Does it show a volume increase in the controller too? In the debug screen, when it happens, any "audg: volume" messages in the server messages section?

No the controller (the slider you get when pressing volume up/down) remains the same. The debug screen does not show anything. Actually I never knew that there was a debug screen at all. Am I supposed to do anything with it? (High quality resample is ticked)

 

[streifenleopard]

Hi this is a debug screen screenshot, I don't really know what to make of it.

The behaviour remains unchanged and all suggestions are welcome!

 

[wayne@angrygoat]

No the controller (the slider you get when pressing volume up/down) remains the same. The debug screen does not show anything. Actually I never knew that there was a debug screen at all. Am I supposed to do anything with it? (High quality resample is ticked)

You don't have to do anything at all. That screen just lets me see what's going on with the app and what commands it's receiving from the server.

Your screenshot shows me that everything is normal. Whatever problem you're experiencing is not caused by the server.

Since I've never heard of this problem before, it is likely specific to your phone. Does it happen with music formats other than mp3? Do you have app set to control the device's volume? What "Output Sampling Rate" is the app set to?

 

[markm9999]

Sorry to post here. I didn't see link on your main site to a forum for the new Windows 10 Store version.

Anywhoo, I've got SqueezeCtrl on my Android (love it!) and figured I'd check out the version that runs on a Windows Desktop.
My question - why do the main panels appear to be swapped?

What I mean is, I guess I was expecting it to work & look more like 'tablet mode' in the Android version.

One additional nit, the Previous-Play/Pause-Next buttons being located against the right edge - to my eyes they are hard to spot - maybe they could be placed next to the player selector or centered within the app?
This especially apparent on a large screen when the app is maximized.

Just my 2 cents...

 

[wayne@angrygoat]

The forum for the windows app is here: Annouce: Squeeze Control is now available as a UWP app for Windows 10.

The layout is swapped because the standard way a UWP toolbar is laid out from right to left and the buttons make more sense to be on top of the main menus and playlist, than the now playing panel.

Part of the reason the controls is not in the middle is that with no controls on the right, the layout will look unbalanced. The other part is that the control bar needs to smoothly stretch from narrow to wide and it's just simpler to have the middle stretch. In Android, tablet mode is completely separate from phone mode so it never had to deal with an expandable window.

 

[HankDee]

Been using this great app on my Samsung tablet for a long time but now suddenly the screen orientation that I had locked for 4 screens changes everytime I start the app. And I have to do 3 back-buttons to reach my favorite view. Tried to lock the orientation but no change. Hmmm....

 

[redsandvb]

Posted this in the Squeezebox forums, didn't know if it was better to post there or here so...


While playing a track then browsing an album, the pop-up menu (when you tap on a track) does not appear for any tracks past the first 20. Same with multi-disc sets (I group them together as one album), the pop-up menu only works on the first 20 tracks...For example Disc1 tracks 1-15 and Disc2 tracks 1-5 work, beyond that it doesn't.

Again, this is only while playing something. After stopping playback (and maybe browsing to another album or waiting a bit, I don't recall exactly) the pop-up menu works for all tracks.


This is on a Google Pixel 2 w/ Android 8.1



Also happens browsing by artist-->all songs


Thanks!

 

[wayne@angrygoat]

Been using this great app on my Samsung tablet for a long time but now suddenly the screen orientation that I had locked for 4 screens changes everytime I start the app. And I have to do 3 back-buttons to reach my favorite view. Tried to lock the orientation but no change. Hmmm....

What do you mean the orientation changes every time you start the app? What's your favorite view and why would you need 3 back presses to get to it?

The app hasn't been updated for a while, so any new issues are not caused by changes to the app.

 

[bvanaerde]

Recently bought a Nokia 7 Plus. Here, the Squeeze Ctrl app gives me the following error, mostly right after putting the screen back on.

Animator Disabled
Animator Duration Scale in Developer Options has been set to Off. This app cannot operate correctly with this setting. Please change it to any value other than Off.
(button to developer options)

Strange thing is: I didn't even have the Developer options on. So I enabled it, only to find that the value is not set to "Off". It's set to 1x, and changing the value did not help.

I was only able to test this on Android 8.1, as this update was immediately installed upon receiving the phone.



edit: this seems to be working fine again, after Android's latest security update (may 2018).

 

[HankDee]

What do you mean the orientation changes every time you start the app? What's your favorite view and why would you need 3 back presses to get to it?

The app hasn't been updated for a while, so any new issues are not caused by changes to the app.

I emailed you with some screenshot /Henry

 

[HankDee]

What do you mean the orientation changes every time you start the app? What's your favorite view and why would you need 3 back presses to get to it?

The app hasn't been updated for a while, so any new issues are not caused by changes to the app.

I emailed you with some screenshots/Henry

 

[wayne@angrygoat]

I emailed you with some screenshots/Henry

Did you get my email reply a couple of weeks ago? If not, Go to Preferences > General and disable "Now Playing at Show"