|
Andrew, I think #6 is about as good as you can expect to get. I don't think that having your PPC always connected to your phone via BT but with the screen off is going to be practical any time real soon due to battery life issues. I would imagine that it would drain your PPC's battery way too fast. What is reasonable to expect is for your PPC (or phone) to be smart enough not to hang up an existing call and, instead, wait xx minutes to try again (or just wait for the next scheduled interval). Now, I'm wondering whose fault this is? Is it...
a) The PPC blindly killing the phone connection so that it can do it's thing.
b) The phone not being smart enough to disregard the PPC's request to connect.
c) An inherent weakness of the Bluetooth protocol.
d) The application that you're using.
Hopefully, the answer is (d) as this could be addressed by the developer coding the app to ignore the scheduled interval if a phone call is in progress and try again later.
So, does anyone know the answer? I might be able to provide some insight later. In addition to my iPaq h4155, I also have a Tapwave Zodiac (Palm OS for those that don't know). I own a copy of SnapperMail for the Palm OS which can do scheduled interval checking of email. I'll simulate the example you provided and let you know what the results are.
Scott
__________________
Tapland
|