Main Issues

Please report any problems or requests in the Github Issue Tracker

Crashes

Sometimes it crashes. No idea why. The log file may help finding the problem. It is located in /home/phablet/.cache/upstart and called application-click-hutspot.wdehoog_hutspot_<version>.log

Device Discovery

The list of devices to play music on is managed by Spotify so Spotify needs to know the device exists. The official apps and applications discover new devices using zeroconf and some http requests. Hutspot cannot do this.

Network Disconnections

Hutspot cannot detect network disconnections of your phone.

Meta data on Indicator panel is not updated

The Meta data on the Indicator panel is not updated when Hutspot is suspended (app is in the background or the display is off).

No Player Queue

The Spotify Web-API does not support a player queue. You will have to use Playlists to have some of sort of queue functionality.

Playlist Snapshots

When you play a playlist you are in fact playing a specific snapshot of that playlist. This means that any modification to that playlist will not be reflected in the list being Played. For example added tracks will not show up until the playlist is restarted.

As Hutspot uses a playlist for playing seperate tracks this is a problem. Currently Hutspot, when reaching the end of the last track, tries to determine if the playlist has been modified and then to load the fresh snapshot and continue with the new tracks. Unfortunately this is not working correctly.

Repeat State

The web-api allows for three Repeat states: ‘off’, ‘context’ and ‘track’. Sometimes the repeat state can not be set to ‘track’ and is reverted by Spotify to ‘context’. In that case press the button twice to skip to ‘off’.

Spotify WebAPI

The Spotify web-api has some limitations:

• No support for podcasts
• Played tracks seem not to be added to the Recently Played list
• Not all Players are visible