Bugzilla – Bug 2768
no response to IR when playing
Last modified: 2006-01-01 10:42:48 UTC
It seems that in the latest svn, there is no longer any response to IR in any mode once music starts playing. 2005-12-30 19:33:33.3336 irCode not defined: 2005-12-30 19:33:33.3339 trying to execute button: 2005-12-30 19:33:33.3341 button not implemented in this mode 2005-12-30 19:33:33.4389 7689b04f 2784.2851552 1136000013.43897 2005-12-30 19:33:33.4396 irCode not defined: 7689b04f.repeat 2005-12-30 19:33:33.4398 irCode = [] timer = [2784.2851552] timediff = [0.107864000000063] last = [] 2005-12-30 19:33:33.5885 irCode not defined: 7689b04f.single 2005-12-30 19:33:34.0762 7689b04f 2784.9224544 1136000014.0762 2005-12-30 19:33:34.0771 irCode not defined: 7689b04f 2005-12-30 19:33:34.0773 irCode = [] timer = [2784.9224544] timediff = [0.637299199999688] last = [] 2005-12-30 19:33:34.0774 irCode: , 00:04:20:03:02:ce 2005-12-30 19:33:34.0784 irCode not defined: 2005-12-30 19:33:34.0787 trying to execute button: 2005-12-30 19:33:34.0788 button not implemented in this mode 2005-12-30 19:33:34.1841 7689b04f 2785.0302928 1136000014.18414 2005-12-30 19:33:34.1847 irCode not defined: 7689b04f.repeat 2005-12-30 19:33:34.1849 irCode = [] timer = [2785.0302928] timediff = [0.107838400000219] last = [] 2005-12-30 19:33:34.3365 irCode not defined: 7689b04f.single
reverted as far as r5000 and this didn't fix it. However, part of the process was to rebuild the local binary modules. This brought about a different symptom that still blocked IR but showed that down.repeat was being recieved many times per second. As it turns out, this ended up being something coming from an IR blaster for my RF remote. Moving this out of the way cleared things up. Then moving back up through revs, I was unable to repeat these symptoms. Now at 5488, everything appears ok. The IR blaster doesn't even seem to cause the unknown IR codes in the log above. I can't even explain why being in playback made a difference. I guess this was a false alarm. Marking invalid for now. If it comes up again, the notes above may help.
I suspect that there was a LOT of IR coming into the player and causing some kind of cpu saturation when decoding. IR jamming...