Is Rhapsody/VZW music holding up 6.5 on TP2s?

[constitutionalist]

Please forgive if someone else has touched on this - I ran a search but didn't see anything.

That said, I read an interesting post from 11/19 on wmexperts suggesting that if there is a hold-up on the Verizon Touch Pro 2 upgrade to Windows Mobile 6.5, it may be that Vzw is having trouble getting the Rhapsody To Go service to work on the upgraded device:

zcarman: I can tell you one major sticking point right now is that the builds for 6.5 are not working correctly with Rhapsody/VZW music service (the software doesn't recognize the device as something that can carry the Rhapsody to Go licenses) so even though VZW isn't saying it's a "RTG" capable phone, users that are already on the service will blow up if they can't get it working with the "update"...]

Of course, this is an interesting story, so I'm wondering if anyone else has heard something similar to corroborate it.

[zcarman]

I hate to kill my own rumor-mill sources off, but, officially, no, VCast is not holding up WinMo 6.5 for the TP2...

The 6.5 thought is from the fact that VZW's own version of Rhapsody isn't supporting the OS in the Device Manager section. I'm sure this will be fixed quickly with the O2 launching tomorrow with 6.5 and Vcast Music, Song ID and the rest of the Vcast package!

Let's hope for a quicker solution for the TP2 and maybe a Manilla 2.5?

[santod]

Vcast Rhapsody is working on the Imagio already. Which is WM 6.5. Just thought I'd mention it!

[who?]

I've been told (I can't confirm it) that Rhapsody To Go will sync with the new 6.5 Verizon TP2 ROM. There must be some way to use that ROM to fix Rhapsody in cooked ROMs. Anyone?

[who?]

Does Rhapsody To Go sync with the new 6.5 Sprint TP2 ROM?

I'm offering a bounty if someone can extract what is necessary to enable custom ROMs to sync with Rhapsody. More info:
http://forum.ppcgeeks.com/showthread.php?t=114878