Reply to thread

Message

<blockquote data-quote="Retired2k" data-source="post: 248232" data-attributes="member: 62045">Aaron,I looked at all the logs and I don't see anything suggesting an error of any kind. Like I said it does change thechannel on my STB while in this state but takes a long time to do so.I feel that your first analysis at this issue is spot on but how do I go about proving it. As far as I know GBPVR doesn't have any references to USB-UIRT while I'm testing your app. except via your app. I can get it working as it should by the following steps.1. Open Input Service Config. app. remove checks on both xmt and rcv for USB-UIRT plugin. close Input Service app. and allow&nbsp; the to reset. This can sometimes take several seconds.2. Open the GBPVR app. At this point normal CPU usage.3. While it's open, open Input Service Config. app. check both xmt and rcv for USB-UIRT plugin. close Input Service app. and allow&nbsp; the to reset. Again, this can sometimes take several seconds and at times immediate.After this is complete, CPU usage is normal and changing the channel on my STB via GBPVR works as it should. The signals sent to the STB are quite fast but accurate everytime, this is great and considerabily faster than HIP when HIP does work.The bad part about all this is when I either manually put the system into S3 power state (standby) or it's automatic, when resuming I have to go through the steps above to get GBPVR back to normal CPU usage. This also happens with either a re-boot or cold start. To add just a bit more to this, I can leave the GBPVR app. open and put the system in S3 standby, upon resuming your app., IR Server and GBPVR both work as they should and CPU usage is normal.Any Idea's?</blockquote>

[QUOTE="Retired2k, post: 248232, member: 62045"] Aaron, I looked at all the logs and I don't see anything suggesting an error of any kind. Like I said it does change the channel on my STB while in this state but takes a long time to do so. I feel that your first analysis at this issue is spot on but how do I go about proving it. As far as I know GBPVR doesn't have any references to USB-UIRT while I'm testing your app. except via your app. I can get it working as it should by the following steps. 1. Open Input Service Config. app. remove checks on both xmt and rcv for USB-UIRT plugin. close Input Service app. and allow the to reset. This can sometimes take several seconds. 2. Open the GBPVR app. At this point normal CPU usage. 3. While it's open, open Input Service Config. app. check both xmt and rcv for USB-UIRT plugin. close Input Service app. and allow the to reset. Again, this can sometimes take several seconds and at times immediate. After this is complete, CPU usage is normal and changing the channel on my STB via GBPVR works as it should. The signals sent to the STB are quite fast but accurate everytime, this is great and considerabily faster than HIP when HIP does work. The bad part about all this is when I either manually put the system into S3 power state (standby) or it's automatic, when resuming I have to go through the steps above to get GBPVR back to normal CPU usage. This also happens with either a re-boot or cold start. To add just a bit more to this, I can leave the GBPVR app. open and put the system in S3 standby, upon resuming your app., IR Server and GBPVR both work as they should and CPU usage is normal. Any Idea's? [/QUOTE]

Verification