Help DNA Started Acting Wonky Saturday.

kmurph said:

I had the PUK error (and a loss of service) after only 4 days of ownership. If I recycled the power, it went away but came back within a day.

I had the SIM replaced, but within 15 minutes, I had no service, and it would not sync with my car's bluetooth...this time I was receiving another error - "Unfortunately, the process.com.android.phone has stopped".

I stopped by another Verizon store, and they gave me a new DNA and put in the same SIM (my second one)...so far, so good, but it's only been a day.

Click to expand...

PsychDoc said:

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.

Click to expand...

Bearcats said:

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.

Click to expand...

PsychDoc said:

Not sure what version of BT it is. It's a 2011 BMW 535xi so I would imagine it's whatever version was around then. I will try to disable the "office" portion of the car as it attemps to transfer contacts and emails from the phone to the car and see how this works. My only fear is that if I do this I may not be able to use the BT to call my frequent contacts (e.g. wife, home, office, etc.) If that's the case then it's almost a question of why bother having BT at all.

Click to expand...

honda95freek said:

I had the same issue with the sim card acting up. Looked just like the screen shot in the start of this thread. Mine has also had an issue charging. While on the charger, orange led on, screen off, I'll unplug it and the phone is locked up. led stays on and the screen will not come on. I have to do a hard reset. anyone else have that happen?

Click to expand...

NightAngel79 said:

Just wanted to say that since that post I quoted one had zero issues. It was the system id

So calling vzw = good

Click to expand...

PsychDoc said:

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.

Click to expand...