[TechniSol]

It's nice to hear confirmation, if unpleasant that there's a problem at all... I've been waaaaaay out on a limb here theory-wise without the data sheets. I've always maintained that if by any chance I'm correct more than most dealing with sparse data, it's because I've also been wrong more than most, just willing to take the risk.

The freezing up has me wondering if when you power back up it might have a queue full of data to transmit or some other communication/sync problem between the neonode and the processor since the processor was likely asleep and blissfully unaware of the neonode probably pushing out data the whole time it had beam(s) blocked, or maybe something else entirely if there is just an I2C interface or the like and it's just out of sync, or whatever.

Have you tried giving it a while once you pull it out of sleep mode? Or tried sleeping it again and waking after removing the interrupter to see what it does? I guess it doesn't really matter, I'm just curious. I'm going to have to try duplicating your results here and confirm them too. I have a later model Touch(internal SDHC card) and a Glo to play with, but have a couple other projects going here too.

I think the most important thing that's been accomplished, and I give the full credit to Mrs_Often, is that a way has been found to eliminate the discharge if it's just coming about as a result of something interrupting the IR prior to sleep mode getting the IR shut down. Hopefully, now that the issue is exposed Kobo will be able to put a bandaid on it. Unfortunately, it may not be the only power drain problem they need to fix according to others. At least it doesn't seem to be a huge across the board problem, based on how many are discussing it here. Then again, one wonders how many might not be bothered by it, or just so accepting of charging portable devices like phones so often they ignore it?

I wonder if they might just limit their problem by displaying a screen prior to the final sleep screen that warns customers to be sure the screen is untouched for a couple seconds? That is, if they are unable to shut the IR down sooner or ensure it shuts down no matter what. It seems to me there would be a way to confidently ensure the neonode shuts down no matter what unless someone screwed the pooch big time.

However, what they're going to do when shut down occurs due to a sleep cover is going to depend more on getting that IR shut down.