Hi!
Hey Tomas, you will find the option when you expand the Now Playing bar to full screen, however you do indeed need to have a beta also of 3.2 running. The update is due to release imminently, so may be best to wait for full release rather enrolling in the beta as the beta process has largely completed now.
What stations are you playing and are you playing from presets or have you specifically searched for and played these back?
No presets, instead I have been searching and trying various (around ten) stations based in the geographical location like the Algarve, Luxembourg, Stockholm, San Francisco etc.. None gave me any sound.
This will be an eco settings on a per-device basis, so there is not much the server can do in this regard.
It seems that Chromecast has something called doze mode that can be bypassed from a casting app or server. Maybe this is an avenue of exploration? https://stackoverflow.com/questions...ecast-session-alive-when-the-device-is-asleep
I believe on iOS in the Settings - Apps -Apps Management, there is a way to view all apps and build versions of the app should be displayed there.
There can be different reasons why this message might appear erroneously - i had a look through your original ticket and can see this could easily be brought about by a previously aborted backup attempt which might lead to redundant files/folders that give the illusion a bigger backup than library. As Dan said per his last response on that point, you should proceed with performing a backup now. It is not a bug related to the Sense Client App beta.
I don't find any Apps Management under Apps, or anywhere else (I used the search facility in the iOS Settings). The nearest I could see something is the "Previous build" in Test Flight, but it doesn't show the currently installed version. Maybe you can consider enhancing the client app with a way to view the installed version of the client app itself (along with the firmware of course)?
Fine, but I have had this prompt every time I'm backing up since December, and no backup has been aborted since then. One could be excused for thinking that a successful backup should clear the condition for this prompt... ;-)
Indeed that's true - we may need a closer look to determine why this is as there must still be something present in the backup that gives the illusion of being larger. Normally performing an up to date backup would clear this message, so something must remain. Doing a brand new backup from scratch and erasing the previous backup folder would resolve it I am sure, but would also take quite awhile to complete to would refrain from that for the time being.
