Quote:
Originally Posted by 640k
Hey R-Capi, I've noticed sometimes, when the app gets hung up buffering, it disappears from the "task manager" (in my case, x-button). If the app is focused, it is unresponsive, If it isn't, you can't get to it. If you try to end it while it's locked up, say with the X (x ends applications), it doesn't actually close. It will suddenly come back to life.
BTW it's pretty hard to log these incidents since I'd have to pick a point where the stream suddenly starts buffering.
|
Who wrote this piece of crap application? Sounds like a typical windows application doesn't it?
I don't remember if you were Sirius or XM, but that information actually matters to me. I handle the streams completely different based on the provider. I can't imagine XM is causing you these problems because the implementation is fairly simple, so I'm guessing you are using Sirius.
This is relevant because I intercept the stream from Sirius and pull song information from it. Maybe something is going awry with that and causing you these headaches. It's possible there is a special situation in the stream that occurs every once in a great while that I'm not handling correctly. I may provide a build that disables this feature to see if your problem disappears.
The reason why it disappears from your Task list is because the app is unresponsive to receive notification events from the system. The system is pinging all of the apps to display them in the task list and C-ApiSRO is not responding, so it doesn't show. I need to understand why it locks up in the first place and fix that problem. All of the others will disappear.
The best thing you can do for me is take notes about your environment when this happens. Tell me things such as:
- Time of day
- How long it's been streaming
- Provider
- Channel you're listening to
- Network strength (EVDO, 1x, Edge, etc)
- Other programs running
- Available RAM memory
- How long it goes out to lunch
- Were you doing something else on the phone (Call, SMS, etc)
As much as you can tell me about what was going on when this happens the better chance I have of reproducing the problem.
You can also enable your log file, but you MUST make sure you delete it every so often. The log will grow every time you change a channel. If you are willing to maintain the file then enable logging and hopefully we'll get lucky catching this problem. YOU MUST DELETE THAT FILE every so often or it will eat your file storage up.
Before I go I have two questions for you: how often does this happen? Is it something that is making this app unusable for you?
Holy cow, I should get this published; it's freaking huge.