Originally Posted by PsychDoc
I believe it has something to do with a lack of compatibility between the phone's bluetooth and the car's. I had the same problem, with the same error message coming up on the phone (i.e. "Unfortunately, the process.com.android.phone has stopped") and I got Verizon to replace the phone for me. After an hour or two in the car, it started doing it again. Since then (about three weeks) it's generally been fine even in the car but every once in a while it will start acting wonky in the car and cycle though holding a BT connection and then losing it. When that happens I get the same error message but the phone eventually sorts itself out over a period of a minute or two and reestablishes a 3/4G connection. There seems to be no rhyme or reason to when this will happen and it's only when connected to the car's BT. I have a wireless home phone that has a BT connection feature and the DNA links up perfectly with that without a glitch. So it is obviously some [intermittent] incompatibility issue between the DNA and the car's BT.
As two DNA's have now had this issue I've now just resigned myself to the fact that it's one of those things that will happen every so often. I figure a software fix/OTA patch could take care of this if HTC gets enough complaints but I'm not holding my breath.
Any idea what blue tooth version your car is? Are you downloading contacts/call history?
When I was doing the downloading contacts/call history I could get it to crash every single time. Answering "no" on the phone did not correct it. I had to set the car to NOT ask at all and it would pair up and not crash. This is a work around as I would really like it to work but like you I am not holding my breath for HTC/Verizon to release a proactive fix.