[Ed Zachary]

Couple of "obvious" tips, but, hey, doesn't hurt to have a reminder:
- Make sure you have the latest version (2.0.5) from the bottom of the first post in this thread. There are other versions floating around out there. Be sure yours is "official".
- Make sure you soft-reboot (I always do it TWICE) after an install. Especially when dealing with CF3.5. Installing anything in a Windows environment can cause dll conflicts.
- Make sure you can currently listen to XM over the internet. Many of us got bit by the "usta-could-listen-online-but-now-I-can't" deal.
- Make sure your logon ID is not logged on thru your browser (logoff and shut down your brwoser) on your PC. Sirius used to bounce the logged-on session if you logged on using a different machine. Don't know about XM.

This same error has been reported before. See post #136. Had to do with someone using a Smartphone trying to listen to XM. Which brings up another "I wonder" situation: I wonder if you phone not having a touch screen has anything to do with it.

The nature of the error would indicate that the app has created an object, the creation of which included a request to the provider. The request did not result in an error code being returned so a subsequent statement in the app attempted to use the object. If the app requested something from XM and XM did not return data nor an error code, the app would attempt to use an object that does not exist. Hence the error.

Other possibilities: if you wend your way through all the problems people have had streaming from XM you will see that the service from XM has a reputation for stopping suddenly, leaving client apps, such as this one, hanging.

Sorry I couldn't give a definite solution, but it sounds as if the issue is somewhere outside the app itself.