I've been participating in a discussion about the Nissan/Droid compatibility problem since I got my Droid the first day. I had my new Altima for a month before buying the Droid. My previous phone happened to be on Nissan's "Recommended" list and worked fine. Obviously, the Droid was too new to test. I bought it anyway and was disappointed in the bad sound as others have pointed out. Since then, I have seen other responses from Nissan and Infiniti of the same problem.
Today, I posted on the Motorola discussion my observation that there are many devices in many vehicles over years and different manufacturers and that I suspect the hardware used was contracted by the manufacturers and probably not designed to updated. Realistically, the only thing I expect Nissan to do once they get around to testing the Droid is to put it on the "Not Recommended" list along with a lot of others. I doubt that "fixing" the car is EVER going to happen. In my mind, I imagine this as a programming issue that can, realistically, only be fixed by the programming on the phone. According to "Goat" who wrote the last post, this is not an Android problem. You may be right. If so, it sounds pretty hopeless to me. I would like to know from someone who actually works on Android and/or someone who is an expert on Bluetooth, whether this problem is or is not fixable. If there is ANY chance it is fixable on the programming end or even with the device hardware, I figure it's just a matter of who has the time, skill and motivation to address it. Or, if Goat is right, I'd like to know that for sure. Anyone? On Dec 22 2009, 5:34 pm, Goat <[email protected]> wrote: > From someone who worked for Nvidia for 2 years on the 2009 Audi's for > DVD?navigation/BT I can say for a FACT that this is not a Android > problem but the vehical manufactures problem. > > -Goat > > On Nov 7, 9:31 pm, dataro <[email protected]> wrote: > > > I have a 2007 infiniti G35 Sedan and even with Android 2.0 on the > > motorola droid it will not work. Since the update of android 1.5 on > > any google phone the bluetooth will sync with the car but the sound is > > completely garbled and the person on the other side hear no sounds. > > Tmobile and Verizon blame the car dealer, but the bluetooth was > > working with the car prior to 1.5 firmware. There are multiple open > > discussions and there is a mass of people having this issue. I know > > that this issue is not just with infiniti/nissancars, it is with > > other cars and devices. I have owned every device that has the google > > os installed and the same issue arises with every single one. The > > iphone 3gs, palm pre, and blackberry storm works fine so it has > > nothing to do with the ad2p profile screwing it up. People have stated > > it was HTC's hardware fault but with motorola's phones not working > > this is definitely the android os issue. Can someone please look into > > this. Thanks in advance. > > > note: 2009+ infinitis have this issue resolved but anything prior to > > that still has issues.
-- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
