Squeeze Control for Android (support thread)
- Thread starter wayne@angrygoat
- Start date
- Sep 18, 2012
- 29
- 0
- 1
Hello,
Same problem here (Galaxy S6 android 6.0.1). Each time I open the app, it automatically connects to chromecast and show just a big picture on my TV.
I try to uninstall Google home without success, automatic casting still working.
Can you provide a option to disabling chromecast support in your app ? I agree that is a chromecast bug. But a chromecast support without sound for a audio app does not make sense.
Thanks !
- Sep 18, 2012
- 29
- 0
- 1
Chromecast support was added at the request of a user, so it makes sense to at least one person.
Chromecast support is hooked into the code in multiple places and putting a switch to turn it off is more difficult than it seems. Since the bug seems to be triggered merely by initializing code that has to do with Chromecast, the switch will have to stop the app from even touching the Chromecast code. In addition, the bug does not occur on any of my devices, so I can't pinpoint which particular routine is causing the problem. Quite frankly it would be easier to completely remove Chromecast support than to put in a switch.
I'm just going to wait it out. I'm guessing that when Android Wear 2.0 is officially released (which is any day now), there will be a slew of updates to all the Google support code which would hopefully fix this problem.
Hello,
I have a problem with the 3rd Party Spotify Plug-In from Triode. When I search e.g. for an artist, click on the artist and want to play a mix of the artist or of similar artist, clicking on it doesn't work very often. And if I click the "+" button, there is written "loading" on the pup up window and nothing is happening. I think it is in some way not a problem of your app, but also of the Server (latest version 7.9 running on a qnap NAS x86) or the plug-in. But I think it could be handled by having a "play" button instead (or in addition) of this "+" button. 'Cause when I do it like that from the web interface, (just clicking the play button that is coming up when I am hovering over the entry), it's working.
So my question is: Could you make it possible in your app to just send the "play" impulse to the server in addition to show all possibilities over the "+" button?
Best regards,
Joern
I have a problem with the 3rd Party Spotify Plug-In from Triode. When I search e.g. for an artist, click on the artist and want to play a mix of the artist or of similar artist, clicking on it doesn't work very often. And if I click the "+" button, there is written "loading" on the pup up window and nothing is happening. I think it is in some way not a problem of your app, but also of the Server (latest version 7.9 running on a qnap NAS x86) or the plug-in. But I think it could be handled by having a "play" button instead (or in addition) of this "+" button. 'Cause when I do it like that from the web interface, (just clicking the play button that is coming up when I am hovering over the entry), it's working.
So my question is: Could you make it possible in your app to just send the "play" impulse to the server in addition to show all possibilities over the "+" button?
Best regards,
Joern
- Sep 18, 2012
- 29
- 0
- 1
First, having the tap gesture perform two different functions at the same time is just a bad design. Second, the problem you're experiencing is probably because you're using the old Triode plugin. Spotify made some changes to their service a while back and the old Triode plugin no longer works correctly. Instead you should delete that plugin and install the new Triode one called Spotify Protocol Handler. This plugin allows you to use the official Spotify app for Squeezebox.
The automatic activation of Chromecast desperately needs a fix. I thought that hiding the Chromecast icon would also disable the behaviour, but it doesn't. Which means that my TV automatically switches to Chromecast input everytime I use the SqueezeCtrl App.
Imagine my spouse's reaction when she is watching TV!!!
it's a nice feature but when it cannot be turned of it is better removed completely. IMO
Imagine my spouse's reaction when she is watching TV!!!
it's a nice feature but when it cannot be turned of it is better removed completely. IMO
- Sep 18, 2012
- 29
- 0
- 1
Automatic casting is not a feature. It's a bug in Android that Google introduced sometime in the fall of last year.
https://productforums.google.com/forum/#!topic/chromecast/00b79rIKacA
Last edited:
In that case I suggest disabling the Chromecast feature until the Android bug is fixed.
It is a nice feature when it works and can be disabled manually. But since that is impossible, it takes over tv control at unwanted moments, every time the App start. Which is a bad thing and causes trouble at home.
For me it will mean I cannot use SqueezeCtrl any longer until the issue is fixed. Which is sad because I really liked this app.
(BTW your link is incomplete)
It is a nice feature when it works and can be disabled manually. But since that is impossible, it takes over tv control at unwanted moments, every time the App start. Which is a bad thing and causes trouble at home.
For me it will mean I cannot use SqueezeCtrl any longer until the issue is fixed. Which is sad because I really liked this app.
(BTW your link is incomplete)
- Sep 18, 2012
- 29
- 0
- 1
Try following the directions at this link: How to Remove Chromecast’s New Network-Wide Android Notifications
It help another user.
It help another user.
Thanks for your suggestion but sorry this didn't help. The app keeps making a Chromecast connection as soon as it it started.
I'm on Android 6.01
(BTW - I guess your suggestion would turn off ALL notifications, for other apps also, eg Netflix etc, but that is not what I want.)
I still think the Chromecast feature in SqueezeCtrl is a pain. No single other app starts casting automatically, casting always has to be triggered manually to avoid unwanted behaviour like this.
I'm on Android 6.01
(BTW - I guess your suggestion would turn off ALL notifications, for other apps also, eg Netflix etc, but that is not what I want.)
I still think the Chromecast feature in SqueezeCtrl is a pain. No single other app starts casting automatically, casting always has to be triggered manually to avoid unwanted behaviour like this.
- Sep 18, 2012
- 29
- 0
- 1
In fact that is how it's supposed the work, and is how it still works for the majority of users, myself included. This is the main reason why I can't fix it, I don't experience it on any of my devices. I have some guesses at what might be the cause, but without a device that experiences the problem there's no way to test it.
I think it mainly affects Android 6 (Marshmallow) on certain devices.
Oh, I understand now, didn't know it affected only some devices. Looks like I'm f*ed then with my Samsung A3 2016 on Android 6 :-(
Hello.
I have the same problem with my Samsung Galaxy s5 mini (Android 5.1.1) and Sony Xperia Tablet Z (also 5.1.1), but on Sony Xperia Z3 Compact (6.0.1) it seems to work fine. This issue is really annoying, because my TV turns on every time I try to start the app on my Tablet
I'd rather not to have this feature at all, because I don't need to see the title of actual track on 49" screen...
I have the same problem with my Samsung Galaxy s5 mini (Android 5.1.1) and Sony Xperia Tablet Z (also 5.1.1), but on Sony Xperia Z3 Compact (6.0.1) it seems to work fine. This issue is really annoying, because my TV turns on every time I try to start the app on my Tablet
I'd rather not to have this feature at all, because I don't need to see the title of actual track on 49" screen...
I second that. It also uses extra energy having a TV on all the time so it's bad for the environment too...
- Sep 18, 2012
- 29
- 0
- 1
Chromecast support was a feature requested by a user, so I can't just remove it. Someone is using it.
Google seems to have rolled back the version of the one of the support libraries that developers need to use to support Chromecast, probably because of this problem. I'll publish an update in the next few days that uses this older version, after I make sure it doesn't break something else. Hopefully that will fix it.
I understand that. But then it should also behave like it is implemented in every other app, which means the connection is only initiated with a user command (pressing the Chromecast Connect icon).
I really hope the rollback will solve this problem!
- Sep 18, 2012
- 29
- 0
- 1
As I have mentioned above, it is supposed to only work when the user initiates it and it was working that way until Google changed something that causes it to auto connect. If you don't believe me that other apps, including Google apps, had the same problem, look at this thread: https://productforums.google.com/forum/#!topic/chromecast/00b79rIKacA
I DO believe you, and I really hope this problem will be fixed soon (by Google)!
It's only confusing that - unlike many others in the other threads - every other cast-enabled app on my phone works fine. Also, the other threads also often mention unwanted popups or notifications on their phone which is not my problem at all.
It's only confusing that - unlike many others in the other threads - every other cast-enabled app on my phone works fine. Also, the other threads also often mention unwanted popups or notifications on their phone which is not my problem at all.
Facebook
Twitter
Instagram