2014-10-14, 17:17
I don't think it passes along the raw IR code like it would any other normal command, so much as self-interprets it and then sends the USB wake command... which sounds like a very different process that may not impact in-progress transmission of normal commands. Don't get me wrong - almost certainly a firmware issue, but as far as I can tell there are only two possible reasons for what I'm seeing:
!) after successfully powering on the system, something causes the IR receiver to enter a state whereby it can no longer send commands to the system
2) something is confusing the IR receiver prior to or during sleep, whereby its first communications after wakeup is causing the software to no longer be able to interpret its commands
Since I can see no signs that the device itself is crashing or otherwise requires resetting, I'm almost willing to bet it's scenario #2. And again, I'm sure it's a firmware glitch... but it might be one that's aggravated by an already non-ideal situation.
And so far so good with 4.2.1.
!) after successfully powering on the system, something causes the IR receiver to enter a state whereby it can no longer send commands to the system
2) something is confusing the IR receiver prior to or during sleep, whereby its first communications after wakeup is causing the software to no longer be able to interpret its commands
Since I can see no signs that the device itself is crashing or otherwise requires resetting, I'm almost willing to bet it's scenario #2. And again, I'm sure it's a firmware glitch... but it might be one that's aggravated by an already non-ideal situation.
And so far so good with 4.2.1.
