Okay, so I modified gscom.cpp and recompiled. I'm no longer getting "invalid client" messages, but I'm still not getting search results. I can't really tell what the problem is, as I never got a chance to see the command line output of a working version of groove.

I am getting a specific fault message citing "invalid token" and am assuming that has something to do with it.

Yeah, still some issue, did you change the hard-coded, differently-formatted version string ("header.insert("clientRevision","20101012.37") ;" in gscom::getSong), which, according to my sniff, is 20110722.11

Are you building on the pandora? Honestly I didn't get a chance to try to sort out the buildep issues today, just looking for pointers if you're already there...

Just a tip, rather than recompiling for that simple string, it's the same length (of bytes and chars), so just use sed on the binary.

sed -i 's/20101012.37/20110722.11/g' groove

bmouring: You're right I missed that. Building on my pandora now and will test it soon.

I'll also be looking into the builddep issue soon. Installing sb2 tonight.

MohammadAG: Thanks for that. Never done it before but I'll try testing on my build tonight.

EDIT: And tested. Now I've got "Error fetching token: did not recognize secret key"

And that bin-replace trick also works when dealing with fewer chars if it's null-terminated (usually), I'd forgotten about that little nugget from back when I'd use a resource editor to modify progs, thanks for the tip MAG

any news ?

Unfortunately I haven't had a chance to compare network grabs of the modified Groove and the online page, but did verify that the modied version, while better than it was (gets furtehr in auth), still doesn't work

Any chance for another API update on this, or did Dotblank give up on it? It hasn't worked for a long time now.

Plan for the n9?

How about a plan to get it working on the N900 again first?