I downloaded Groove yesterday and all the existing features are working beautifully. This is most definetely a very neat app.

This is super-awesome! Best thing by far on this phone.

For you who have problems with GS, I've been using GS for a long time and the servers have been far from stable. So this is something to keep in mind. I don't think there's a great risk for getting your IP's banned and if it is then you would only need to reconnect to your APN to get a new one. At least my operator scrambles IP's quite well. What could cause problems is that if you play mamy songs in a row without a premium account you will be prompted to say that you are listening, if you don't the music halts.


I've been using this app solely on 3G and it works well. Apart from the 4 sec issue allready reported.

I have two requests.
1. A "play all" button.
2. Pause-button.

Looking forward to the nexr release!

Hi,

Noticed a slight problem with how you're doing memory allocation. Sent you a patch to your gmail account.

Just uploaded a new version with some added features and fixes some bugs.

Updated Again. Finally fixed the seg-faulting when downloading songs (version 0.4-3)

Are you actually using/passing Unicode properly? Search works fine only for Latin characters. E.g. try "аквариум" - gives reasonable results in web interface while producing weird list on N900.

Thank you,

Leonid

What's the status with the playlist feature? That would bring the experience to a whole new level.

One (really) small improvement idea: pause-button could change to a play-button after a click.

-timothies

Suggestion (related to unicode in Qt)..

Web services (like Groove) often want their input in utf8. QString however is utf16. To get to utf8, you want QString::toUtf8().

To convert from utf8 back to utf16 QString (e.g. parsing input from Groove) see, QString::fromUtf8().

Then, you have C strings (char*) which don't actually have a predefined encoding, they are just strings of bytes - so you need to keep an eye on what you put into them.

Generally speaking, they're latin1 encoded (ASCII), to put them into a QString.. QString::fromLatin1(). If they aren't latin1, see QTextCodec::setCodecForCStrings().

QLatin1String class is also helpful - in particular, this will allow you to compile when using QT_NO_CAST_FROM_ASCII (which itself is helpful to make sure you explicitly give encodings for all of your strings).

Hope this helps!

can't get this to work anymore.

tested different networks.
updated uninstalled installed
can't find any tracks.

Works for me, does going on listen.grooveshark.com work?