Originally Posted by andy80 (Post 766331)

Let's try to understand better your problem, but please do these tests I tell you:

1) Test both LastGo and Vagalume and tell me if this error happens with both clients.

2) open a terminal on your N900 and try this: mv /home/user/.config/LastGo/LastGo.conf /home/user/.config/LastGo/LastGo.conf.bak

shortly: this renames the configuration file, so you'll have to import api key again, insert username/password again and a NEW SESSION KEY will be requested.

Originally Posted by Lake (Post 766710)

Ok - I copied and pasted your text into XTerm and renamed the file. I then went to LastGo and I got a request to re-import the API Key. I did this and was prompted to enter my username and password (which I did). I then got the message "server error - please try that again".

I have repeated the process for Vagalume and I just get "network error".

Many thanks

Originally Posted by andy80 (Post 766819)

You followed my instruction in a perfect way. The only thing I cannot explain is: why it still doesn't work?

If, for some reason, you had some problem with subscription, the client would say "You need to be subscribed ecc...". But it says "server error" that is not something I explicitly write in the status.

I cannot explain.... do you have any connection problems with your N900? How much signal UMTS/WIFI do you have when you click Play button?

Originally Posted by Lake (Post 767023)

The WiFi signal is at 100% but interestingly I get the same issue if I use the provider network (I think you call this GPRS) but not if I access the website and play the tracks from there.

Could it be that LastFM has a means to prevent mobiles accessing content in this way which has not been considered? I see there are others for whom this works, so if any of them are reading perhaps they might offer an explanation?

Originally Posted by andy80 (Post 767039)

I don't know if Last.fm has a way to prevent users from using a mobile connection for last.fm streaming.

All I know is that I can use LastGo (or Vagalume) both with my home's wifi connection and with my "3" ThreeHG UMTS connection (even if it's not allowed by them).

Are you having this problem both with wifi and with umts? Or just with UMTS?

Originally Posted by Lake (Post 767058)

I am having problems with both

Originally Posted by andy80 (Post 767061)

at the moment, the only way for me to understand why you have that problem is trying to insert more debugging code (and maybe let LastGo to log it into a .txt file) into the application and make a new "experimental" release as soon as I can.

I wish I had more feedback from other users, to understand if this is only your problem or if it's a common one.

Originally Posted by Lake (Post 767084)

Ok well thanks for your support so far - one question though, can you generate a new API key somehow on lastfm? Maybe I can try that?