Bugzilla – Bug 16332
Proximity: Disable not used IR LEDs
Last modified: 2012-03-12 23:50:22 UTC
Unfortunately proximity detection isn't as reliable as we hoped. Especially when approaching the SB Touch screen from the right or left side there is a big difference due to the IR receiver being on the left side. Therefore it has been decided to disable the two IR LEDs used for proximity. If that becomes permanent we probably should consider not to populate the two IR LEDs in future SB Touch builds.
== Auto-comment from SVN commit #8915 to the jive repo by fmueller == == http://svn.slimdevices.com/jive?view=revision&revision=8915 == Bug: 16332 Description: - Disable proximity LEDs after startup (They are still on during startup because that is the default in the mcu code - to prevent that a mcu code change would be needed.)
Update hours.
== Auto-comment from SVN commit #9072 to the jive repo by fmueller == == http://svn.slimdevices.com/jive?view=revision&revision=9072 == Bug: 16332 Description: Disabling proximity from within lua can cause IR to fail alltogether. We need to do this from within the microcontroller code itself.
Turning off proximity from within lua has a potential to fail and even to disable IR completely since it can happen before the microcontroller is ready and therefore kill i2c communication with the microcontroller. Seen at least on one Fab4 - see bug 16475 The correct way to disable the IR LEDs for proximity is in the microcontroller code itself as mentioned in comment #1. Vahid - I guess you could change that the next time you need to touch the microcontroller code in Fab4 anyways. Thanks
Vahid is no longer working for us.