The new Sametime client is interacting with the operating system in some strange and unexpected way. :: email :: twitter :: qr code :: comments (6) Odd system interaction in Sametime 7.5.1 by Volker Weber Just as I am getting acquainted to the Treo. In related news: somebody at RIM was annoyed that I did not yet receive a replacement for the broken Pearl so he is sending one tomorrow. So we ended up with a phone switched off and lost a few calls that way. I know that you may only tap the red button shortly, but Ute did not. Plus a sound you can't hear if the phone is on vibrate. Your only indication is a small icon at the top of the screen. If you hold the red receiver button too long, it will shut down the phone. I have one more annoyance that hit me yesterday, when Ute returned the phone after terminating a call. It is the last option in Settings/Voice Command/Telephone/Options: Anyway, that was not so easy to spot, but easy to switch off.

Thus the delay when you are fighting over control. If you pick it up quickly, then you want to say something, but Voice Command apparently also wants to grab the audio interface. If you pick up the phone late, you will hear a ring and then the phone calls out the name of a known caller. It lets you interact with your phone, and there was one option which lead to a race condition. As it turns out, Voice Command was the culprit. So typically they would not hear me accepting the call and there were all sorts of 'Hello, hello, do you hear me' confusions. I have resolved one major annoyance I had with the Treo 750: when accepting a call, the calling party would not hear the first second or two of what I said. :: email :: twitter :: qr code :: comments (10) Treo 750 annoyances, one resolved by Volker Weber

Ebin icq and jabber