Quote:
Originally Posted by labboypro
Yeah, some I've seen aren't CAPTCHA (which, BTW is actually Completely Automated Public Turing test to tell Computers and Humans Apart)... they're more like CAPTCFGA... where FG is Fricking Geniuses.
As for my ongoing issues with C-ApiSRO... I'm going to give up. It's a great LOOKING app, but it's never worked for me... ever. So it doesn't meet my most basic need in an app. I hope R-Capi continues to work on it, and will check back from time to time, but for now... I'm out.
|
Well, this is most unfortunate. I did what I could to help. I'm extremely swamped with my real job right now, which is why a new version hasn't been produced yet. I would still like someone to perform the steps I've listed in post
#97. That may produce some valuable information, but no one has done this.
The next version of C-ApiSRO will have the following:
1. Power Save features. It will allow you do disable the screen either manually or at a set interval. The backlight is a huge battery killer, so this will improve battery life.
2. Fixed issue with the Sirius Proxy server that in some instances would cause you not to connect with Sirius. This may fix some peoples problems with Sirius.
3. Added better messaging when things fail. Hopefully this may help diagnose the problems quicker going forward.
4. Since the latest XM channel page updates many of you are experiencing problems immediately after login. This is when I attempt to retrieve the channel lineup. I believe it's either a DNS or HTTPS issue that has caused problems. The following two items are an attempt to correct this:
- Added a configuration option to use the physical IP address of the channel list HTML page rather than the host name. The IP address will fix any DNS issues people are experiencing.
- I'm going to keep a cached copy of the lineup page locally on the phone. I will attempt to get the latest, but use the cached version if the latest fails. Some were reporting things worked fine before XM did their update, so hopefully this change will get them back up and running.
I'm not sure these changes will fix your problems, but it's a step in that direction. Without knowing the exact problem you are having I will just be taking a stab in the dark. You have to understand, I'm dealing with hundreds of people using different phones, screen resolutions, operating systems, .NET versions, service providers, data plans, and provider subscriptions. It's a lot to get around, which is why I need the most information I could possible get when troubleshooting these issues.
Thanks for giving it a try anyway.