h3x.se spotify remote


Finally – the new release is here!

aReSpot has got a facelift, now supports CoverArt. ReSpot will be continously updated in the near future with more face lifts and feature additions. There's a few kinks to weed out still too I'm sure. Don't hesitate to get in touch if you have bugs to report, features to request or anything else. There are discussion 'groups' available on the ReSpot Facebook page too.
IMPORTANT: Volume adjustment is available by the volume 'hardware keys' on your android. I will re-integrate a volume button on screen but have not decided how/where to put it yet.

jReSpot will soon be released as an EARLY ALPHA. Lot's of things are not working - there are multiple 'paper cuts' in the UI etc. But improvements will be coming down the pipeline soon enough. Stay tuned.

The Servify protocol has been completely re-written and now uses JSON. This has simplified things alot when writing clients.
Servify has been somewhat simplified to start, it's now optional to put login credentials on the command line - if not supplied Servify will ask for them.

Filed under: ReSpot, servify Comments Off
Comments () Trackbacks (0)
  1. I seem to missing the option to activate shuffle and repeat. I know this existed in the last version so it might just be me not finding it in this one 🙂
    Thanks for a great spotify remote though! Seems to a bit more stable now, the server hasn’t crashed so far anyway 🙂

  2. Now not working, says connected to server but client on Android not showing playlist or searching for anything

  3. Johan, the shuffle feature has yet to be re-implemented, sorry! It will be re-appearing soon enough though.
    Hopefully both server and client will be more stable!

  4. Damo, please get in touch with me on email / IM / facebook forum. If you could kindly provide the output from Servify it will help greatly in understanding why it’s not working. Also please make sure you’re running the latest version of the server (should output 2010.07.11).

  5. Great update!!
    I had the same problem as Damo, I reinstalled the client…works great after that.
    Used it 15min…and ticking 🙂

  6. Good stuff.
    I think it was the web server actually sending a cached version of the file! Should be resolved now.

  7. Hi!

    Any plans to make the API against servify public so it will be possible to write clients for other devices?

  8. Yes, the API will be made public, hopefully soon. But it’s probably a couple of weeks….

Trackbacks are disabled.