Nexus 4 - cannot sync contacts or control calls via bluetooth?


Recommended Posts

I recently jumped over to android having most recently been on WP8 and iOS. I figured the Nexus, being googles own device, would be a great one to start with.

I can pair my phone with my car bluetooth system, but it will not sync contacts. At all. No matter how often I try. Additionally, I cannot use the car controls to start/end calls, the only thing I can do is get audio so I have to initiate/end calls by the handset.

This is an absolute deal breaker. The most I can find is a lot of other users having the same problem but no solution. Had anyone been able to get around this?

If I cannot do such a basic thing such as this I am afraid the Nexus will have to go back, I rely too much on this feature for work.

  • 4 weeks later...

I contacted Google about this and they ended up sending a replacement device. Doesn't work. In fact if you search for Nexus 4 Bluetooth issues or Android 4.2.2 bluetooth issues there are many many reports of issues so it seems to be software related rather than hardware.

I will contact google again and see if I can get a refund. Unfortunately this device is pretty much useless to me if they can't even get bluetooth working right :/

What a mickey mouse operating system. Back to WP8!

What a mickey mouse operating system. Back to WP8!

Before you start with opinions like this, make sure it's not your car. FWIW, my Volvo can sync contacts from my Nexus just fine.

Which car do you have? For some reason, contact syncing is something that's always been really finicky - certain combinations of cars and phones work, others don't. Sometimes it's the phone's fault, sometimes it's the car's fault. It might be worth looking up the compatibility tables for your car.

  • 2 weeks later...

Since 4.2 they switched they switched to Broadcom Bluetooth stack which doesn't have AVRCP 1.3 (yet). It should be coming in he new 4.3. If you downgrade to 4.1 you should have AVRCP which then will allow some more advanced stuff, either that or wait till 4.3 comes out which should be in June.

Sounds to me like the OP can't figure something out that he should be able to do and has decided to blame Google for his failures, and he also now wants to troll Google, one more strike left looser

Since 4.2 they switched they switched to Broadcom Bluetooth stack which doesn't have AVRCP 1.3 (yet). It should be coming in he new 4.3. If you downgrade to 4.1 you should have AVRCP which then will allow some more advanced stuff, either that or wait till 4.3 comes out which should be in June.

Thanks, been doing some research into this and it seems to be confirmed the new Bluetooth stack is at fault.

From what I can gather a fix has been implemented in the opensource android but not in googles releases yet. Thanks for the info on 4.3, hopefully it will resolve all these issues. I relied so heavily on Bluetooth calling on all my other phones the Nexus for me is almost crippled without it.

Sounds to me like the OP can't figure something out that he should be able to do and has decided to blame Google for his failures, and he also now wants to troll Google, one more strike left looser

I take it you didn't read any of the other posts where it is clearly discovered to be an Android/broadcom software fault? Read them and try again troll.

Interesting to note - I have a HTC One running JB 4.1 and it syncs contacts with BMW. In fact, it was automatic, first thing that happened when I paired the phone with the car. I hope this is still the case w/ 4.2, but my hopes aren't there.

All reports of problems i've seen are issues using 4.2, with 4.1 having been OK, so matches up with the bluetooth stack having been changed.

I installed Cyanogenmod 10.1 RC2 and it fixes the bluetooth issue. Shame the clowns at Google haven't fixed it and its been up to the mod community to do their work for them.

Its a shame that Cyanogenmod doesn't fix the Nexus 4 washed out screen, where as Paranoid android does but doesn't fix bluetooth. Can't have everything I guess.

Certainly doesn't seem to be the premium experience its made out to be. Strongly considering moving back to WP8.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
    • It is clear from this aricle that "Time Is On My Side" no matter which direction it is flowing., https://noai.duckduckgo.com/?i...m%2Fwatch%3Fv%3DsEj8lUx0gwY
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!