Can anyone help? I am trying to get a fix for an Android OS bug and it seems Google doesn't care. The BUG (not a feature, not a well thought out design) creates a problem if you put any text for a notation after a phone number in the contact list. The problem is that the Droid dials a 011 in front of the number if their is text after the 10 digit phone number. This 011 does not show on the display; it just does it in the background. (FYI Assisted dialing is turned off, current country is USA, reference country is USA). This Android problem happens even though the number in the contact list shows the area code and local city/state.
For example "(760)555-1212 mikes cel" in Oceanside CA dials Russia. This is a Major design flaw!
I spent a very frustrating hour on the phone yesterday with Verizon Wireless customer service with absolutely no resolution other then to go through over 4000 phone numbers in my database and manually remove text after each one and thus lose the info in my notations. The Verizon Wireless rep told me this is just how the Android OS is designed and it just doesn't do what I expect it to do. And that I should be ok with this.
Well ... Every (and I mean every) other phone including office systems, cell phones, smart phones, home phones do not work this way and never have. With all other phones, if your contact phone number has more then 10 digits the extra digits are just dialed or ignored (typically this is not a problem, the Droid OS converts the text to numbers which I'm fine with). However, I do have a problem with the Android OS changing local calls to misplaced international calls. Maybe when Verizon has to start refunding international charges they will address this problem.
The Verizon Wireless service rep's reasoning is similar to this: if I buy a car and turn the wheel left and the car goes right then this is ok, as long as it was designed that way. NOT OK! Please help. Google does not seem to listen to users, and the only hope of getting this Android bug fixed is if the carriers tell Google this is making it's users "displeased" with the Android OS. Once a bad reputation is out there it is extremely difficult to overcome.
What will it take to get Verizon (or anyone) to convince Google that this is a problem and a bug; and not just spout out lame excuses.
I hope someone can help. This is not an isolated problem because it is easy to find on different Droid forums and easy to replicate. Any help would be greatly appreciated.
For example "(760)555-1212 mikes cel" in Oceanside CA dials Russia. This is a Major design flaw!
I spent a very frustrating hour on the phone yesterday with Verizon Wireless customer service with absolutely no resolution other then to go through over 4000 phone numbers in my database and manually remove text after each one and thus lose the info in my notations. The Verizon Wireless rep told me this is just how the Android OS is designed and it just doesn't do what I expect it to do. And that I should be ok with this.
Well ... Every (and I mean every) other phone including office systems, cell phones, smart phones, home phones do not work this way and never have. With all other phones, if your contact phone number has more then 10 digits the extra digits are just dialed or ignored (typically this is not a problem, the Droid OS converts the text to numbers which I'm fine with). However, I do have a problem with the Android OS changing local calls to misplaced international calls. Maybe when Verizon has to start refunding international charges they will address this problem.
The Verizon Wireless service rep's reasoning is similar to this: if I buy a car and turn the wheel left and the car goes right then this is ok, as long as it was designed that way. NOT OK! Please help. Google does not seem to listen to users, and the only hope of getting this Android bug fixed is if the carriers tell Google this is making it's users "displeased" with the Android OS. Once a bad reputation is out there it is extremely difficult to overcome.
What will it take to get Verizon (or anyone) to convince Google that this is a problem and a bug; and not just spout out lame excuses.
I hope someone can help. This is not an isolated problem because it is easy to find on different Droid forums and easy to replicate. Any help would be greatly appreciated.