Okay, it's happened a handful of times and I didn't really think about it until it happened again last night...
My phone was not on vibrate, so obviously in the event of a call or text, it should ring.
I received a call, the caller ID showed name and picture, but all it did was vibrate.
Then I attempt to answer, I slide and the screen goes black, I'm talking, and it keeps vibrating.
I hit the Sleep/Wake button and the screen came back on, showing the "Slide to Unlock" with the caller ID name and picture still showing. I slide again, this time it prompts me to enter my password. I do. It goes to the normal home screen with the green bar at the top that you touch to return to call.
I tap that, and it goes to the call, like normal. The timer is at 0:00, so I hit "End Call." It ends the call and the screen goes black.
Biggest problem here: The vibration did not stop the entire time, even after I successfully ended the call. It was so odd.
The vibrate didn't end until I powered it off. I restarted and it was fine. It hasn't happened a lot, about three or four times since before even 2.0 came out. Maybe it's my phone.
Anyone else have this happen?
My phone was not on vibrate, so obviously in the event of a call or text, it should ring.
I received a call, the caller ID showed name and picture, but all it did was vibrate.
Then I attempt to answer, I slide and the screen goes black, I'm talking, and it keeps vibrating.
I hit the Sleep/Wake button and the screen came back on, showing the "Slide to Unlock" with the caller ID name and picture still showing. I slide again, this time it prompts me to enter my password. I do. It goes to the normal home screen with the green bar at the top that you touch to return to call.
I tap that, and it goes to the call, like normal. The timer is at 0:00, so I hit "End Call." It ends the call and the screen goes black.
Biggest problem here: The vibration did not stop the entire time, even after I successfully ended the call. It was so odd.
The vibrate didn't end until I powered it off. I restarted and it was fine. It hasn't happened a lot, about three or four times since before even 2.0 came out. Maybe it's my phone.
Anyone else have this happen?