2009-12-12, 22:05
kitlaan Wrote:I uploaded a new patch; same place as before. It uses seconds now, as well as making some tweaks to the timer handling. Let me know if you still see the assert.
Thanks for the new patch. The assertion is still present, however bluetoothd doesn't seem to be crashing anymore. At least, I haven't been able to get it to crash after ~40 connect-timeout cycles.
The seconds-based timeout is working well. I have my remote on a 15s timeout, which is great for the batteries. (Admittedly, it did take me about 5 minutes to figure out why my bluetooth keyboard was sluggish and unresponsive.. until I realized that the timeout change applies universally, not just to the PS3 remote. Once I increased the keyboard timeout from 2 to 120, things were better
One question: if I use the remote to Suspend, the machine goes to sleep faster than 15 seconds, which means that the remote won't get timed out. Does that mean the remote is going to sit there broadcasting for a long time and drain its batteries? (If so, how long I wonder? 30 minutes Ruff might have mentioned?)
This makes me wonder if a command-line util to forcibly timeout/disconnect the remote is warranted. Such a util could then be used by the suspend/hibernate script to make sure the remote is off prior to sleep state.