IssueTracker

This issue does not reproduce with dev preview 4.

Closing this issue as per comment #2 from reporter.

wipe + factory reset didn´t work. Bluetooth is not able to start.

[Comment deleted]

I'm also having this issue, as are a lot of others (http://forum.xda-developers.com/showthread.php?t=1988998&page=3). Suggested fixes have been to reflash the device using the commands mentioned in the prior thread.

I have the same problem, i have 2 galaxy nexus with the same problem.

Same here. Saw the possible solution, but I would like to keep my phone locked and everything. There should be a solution for this ASAP.

[Comment deleted]

Updated to 4.2 two days ago and BT hasn't worked since.  Unable to enable the BT in Settings or with Widgets.  Hope a fix is coming soon!  Tried to report to Samsung, but couldn't figure out their support site.

Fix that worked for me (thanks to xda-developers thread): *must have unlocked bootloader* Copied the update file to root of SD card (found on the xda-developers thread). Used Wug's Galaxy Nexus Toolkit to reboot into temporary CWM recovery. Flashed the update file. Rebooted.

Bluetooth working fine. Everything's intact. Lost root, but restored using Voodoo OTA Rootkeeper.

Same problem for me.

I have reflash de radio of google source 4.2 but no effects.

Same here, please fix it as soon as possible...

Yes my yakju galaxy nexus also can't turn on bluetooth after OTA to 4.2..
I would say this is a showstopper issue as I need the bluetooth handsfree when driving... I hope Google fix this ASAP

Add me to the list. Bluetooth not working at all after 4.2 on my Galaxy Nexus. Also, the phone was bought in July from the play store if that helps at all.

Had this problem, but reflashing the radio and 4.2 update fixed it for me

What is going on here google, Lot of people are having the same problem included myself, as I really need to bluetooth while driving so Please FIX IT ASPS. Do you guys even test your build first before release?

I think priority should be high on this one, BT is essential for many people

Same here. Bluetooth is completely gone after OTA to 4.2. The check bar is at off, and when I try to move it to on, it just reverts to off again. Tried to reboot, clear the Bluetooth Share app cache, force stopped it, killed some bluetooth services too, rebooted again, well, I tried several things to no avail.

Mine too!

[Comment deleted]

was same problem.
burned again OTA image with CWM and now it is okay
please refer to http://code.google.com/p/android/issues/detail?id=40126#c22

Still not fixed after 4.2.1 update. Can somebody at Google at least acknowledge this issue please? It is a real show-stopper.

Is there any information, or a video of the problem occurring or anything else I can provide which will speed up resolution?

In most countries it is illegal to use the phone while driving.  The only and best workaround is bluetooth, which now doesn't work.  So who's the doorknob or Apply spy working for Google?  I assure you leave the jokes for April and please do some QC testing before issuing.  Many thanks!

Bluetooth broken in 4.2 and 4.2.1 for my gnex. Step up your game, Google.

same here, please solve this problem ASAP.

Bluetooth on broken since 4.2.1 for my Gnex. It worked fine on 4.2

Bluetooth won't turn on on my galaxy nexus as well on 4.2.1. Fix this please!

[Comment deleted]

Bluetooth was working fine, got the 4.2.1 update and it was still working fine.

Added another Bluetooth device (so there were now 3 total bluetooth devices on the phone), the last device (headphones) was working fine.  Turned off the headphones, charged the phone off the charger and noticed that bluetooth was off for some reason, now it won't turn back on.  It instantly switches off when trying to enable it.

What the hell?

[Comment deleted]

Update: Factory Reset allows me to turn bluetooth on again, but who knows when it will "magically" go back off and I don't intend to spend my days doing factory resets and setting up everything all over again every time.  This needs to be fixed.  4.2 & 4.2.1 = worthless, give us a downgrade.

I've also now learned that the Factory Reset deletes EVERYTHING - including your PHOTOS ... nice one Google, thanks for not giving the Nexus 4 a micro-sd slot.

This issue is also present on the Nexus 4, but it is fixed with a simple reboot.

When the bluetooth remains in a inconsistent state (grayed off), go to Settings -> Application -> all application and terminate the "bluetooth sharing".
This works for me.

Galaxy Nexus i9250 with Android 4.2.1

4.2.1 Yakju GNEX. Bluetooth is constantly showing as "on". Unable to turn off. No devices are able to connect to the GNEX or even see it in visible mode. reboots does not solve it.

As for comment 31: I learned that the hard way. You are supposed to sync everything to Drive or other cloud based services. For good and bad.

When will google fix this?

Can we get some response from Google on this matter? I do need to use bluetooth...

Did a adb full backup, then downgraded to 4.1.2. Next upgraded to 4.2 and then 4.2.1.
Finally restored the Adb backup and all works fine again.

[Comment deleted]

On my Galaxy Nexus, I did also a full adb backup, then flashed directly the 4.2.1 factory image (taken there: https://developers.google.com/android/nexus/images#instructions) with full wipe (formatted the data partition)

Bluetooth problems where still there!

After that, I downgraded to 4.1.2 (again with a full wipe), bluetooth is now working perfectly.

I would not be suprised that that allowing the phone  take the 4.2 then 4.2.1 upgrade would not let blueetooth issues reappears (after all what's the difference with my install if 4.2.1 factory image from scratch?)

Got tired of waiting and rolled back to 4.1.2 last week, BlueTooth again working perfectly. Shame about having to constantly dismiss Update notifications though (#41117).

It's been a month Google, how about acknowledging the issue at least?

To get rid of update notifications, follow the instructions given there: http://www.chargeforums.com/forum/droid-charge-hacking-guides/2089-how-disable-popups-ota-update-very-easy-but-requires-root.html#post22592

Additional step required: after having suppressed the update file from the cache folder, accept the request to update, it will fail and after no more popups.

Worked fine for me

I know that different projects have different teams assigned, but it's none the less frustrating to see a ( better than Android's version) Google Maps release for ios while faithful users with the latest version of Android are left (blue)toothless.

Same situation of LTE variant galaxy nexus Verizon. Come on Google - fix this  quickly.

Up until yesterday, Bluetooth tethering was my primary way of connecting to internet while outside the office and home.  I've now devolved to using the WiFi tethering option on my phone, which draws considerably more battery compared to Bluetooth.
Nexus 7, v4.2.1.  It worked fine for at least a week after the OTA update.  This must be a problem with file permissions.  Someone said the new stack is contained within the user space, not relying on system space for the Bluetooth stacks.  Gotta be specific files that can be replaced to fix this, even if just short term (though perhaps overwriting may require root access).

Same problem hoping it will be resolved in a few days by now.
Connectivity has to remain google strengh !
Thanks

Same problem with Bluetooth here - waiting for a fix...

I couldn't turn Bluetooth on after the 4.2 update on my Galaxy Nexus. I changed the file permissions (requires root) as outlined in this post: http://forum.xda-developers.com/showthread.php?p=35889721#post35889721 and restarted the phone and I can now turn it on. I haven't tried connecting yet.

I can 2nd the above regarding permission changes, my bluetooth is now working again.

I just tried it here too and it works fine.  So why has Google left us with broken bluetooth for so long, without so much as an acknowledgement of the issue (that I've seen), when the fix is this simple?

My galaxy Nexus have bluetooth problem since OTA 4.2.1
Please help me,because i can't use xda developpers or Root...

Got my N4 a week ago. Did the update without question and BT doesn't work after it (4.2.1). Sucks, its like the ICS BT issues before. Looks like android is has a history of Bluetooth issues.

Problems here too where I'm unable to turn Bluetooth off.... It randomly disconnect and I have to reboot the device to let it go again. It's damn frustrating...

While obviously an android problem, I'd bet if millions of N7 were being returned Google would get a sense of urgency about it.

The solution from comment #47 worked for me. Bluetooth working fine again. Took me about 1min. Shame on you Google.

Comment 47 worked for me too.

Had to manually flash images as outlined in this forum: http://forum.xda-developers.com/showthread.php?t=1988998&page=3.

Worked like a charm. I can now turn bluetooth on and off.

Worked like a charm for me as well.
Thanks a lot!
Em 10/01/2013 07:15, <android@googlecode.com> escreveu:

I have the Galaxy Nexus and bluetooth is super unstable since 4.2. It randomly crashes so i can t turn it on or of. Only a restart fixes this. It is annoying as hell.

Yes, I went back to CM10 (4.1.2 based) to make Bluetooth stable again.  It would randomly disconnect from Car receiver with 4.2 and 4.2.1.

same problem, waiting for fix!! - Max -Italy

#47 worked for me. You will need to root your phone and use root explorer to change the permission of the file as listed in the link.

I checked the libbt-vendor.so file on my Galaxy Nexus and it was already rw-r--r-- but bluetooth wasn't working. I then changed permissions to rw-rw-rw- and now I can switch bluetooth off and on as much as I want. I don't have a bluetooth device handy but I'll try later if it works.

It is not mandatory to root the phone to change file permission (but bootloader must be unlocked):

1) boot using unsecure boot image
2) execute adb remount (to make "/system" read/write)
3) execute adb shell chmod a+r /system/vendor/lib/libbt-vendor.so (or a+rw if you think you need  "rw-rw-rw-" file mode)

Same problem on nexus 4 running 4.2.1. Only a reboot fixes it.

For me rw-r--r-- didn't work but rw-rw-rw- solved the problem (two days without problem now).

I'm running 4.2.1 on a GNex and have had this issue since 4.2 JB update

I use BT for all of my headphone uses (music, video & calls), so use it not only while driving but during other journeys too (on train/bus/walking)

This is annoying since it will randomly drop BT connections, and once I start a turn off/on it gets "stuck" in a state (either turned on or half way through turning off) and only a reboot fixes it

I REALLY don't want to have to reboot my phone 2-3 times per day as I try to turn off BT when it's not needed, or when I'm switching my headphones to my N7

Another semi-related issue is that when connecting on either device to my BT headset it gets only a media connection and not a "Phone" connection, no matter how much disconnecting and reconnecting it doesn't solve it, only a reboot allows the headphones to be used fully again

The big question is why haven't Google commented on this at all as BT is REQUIRED for a phone these days!

While this is obviously an android issue, one would think Google would be throwing as much of their talent as possible to such a critical degradation of their products, I.e.nexus 7, Motorola phones, etc. It may be too, that since apple's true value is coming to light Google is not too concerned, however since being crapped on with the promised ICS upgrade to my Photon 4g that was basically a 'bait and switch' job and now owning a crippled Nexus 7, Google may want to remember that RIM and Microsoft are surely willing and possibly able to provide the expected service Google/android are taking for granted.

Unfortunately this is what I've come to expect from Google *customer support* after recently having problems with their wallet and shopping platforms its pretty obvious that they either dont give a crap or are just too stupid to understand the concept of support. Although I have no experience of MS support, those Lumia phones are certainly appealing!

libbt-vendor.so was rw------ after the OTA update to 4.2 here, too on a Nexus Galaxy. Bluetooth could not be turned on. Fixing the permission to rw-r--r-- and a reboot fixed the problem.
What a shame for Google that they introduced such a bug and don't fix it and after such a long time of several bug reports discussing the problem. Not even a reaction from Google in the bug reports. Thank's Google :-|

Setting the permissions didn't work for me. The problem  arose again after a few days.

It s a bug. Simple as that. Google has to fix this asap. I can t believe it takes so long to fix such a crucial part of the phone like bluetooth.

The OP is from Nov 14, 2012. Today is Jan 29, 2013. Google just ignores it. It might have been solved on 4.2.2, but Google don't talk with its customers. Since I *really* need a working Bluetooth, I re-flashed my galaxy nexus with the stock 4.2.1 takju firmware back in December.

Google has no respect whatsoever for the people who bought his branded smartphone. It's a shame. In a year or so I will get another smartphone, and it will not be an Android powered smartphone, thats for sure.

Also having this problem on two different stock Nexus 4 with 4.2.1 update.

logcat while turning on is attached, which clearly shows that bluetooth is failing to turn on due to services not being setup correctly.

Killing bluetooth services in apps doesn't help.
Changing permissions on libbt-vendor.so doesn't help.
Clearly something else is wrong here.

Please FIX Google!

Same crap on LG nexus4
M$-like bug... Real shame.

A full factory reset resolved the problem on the two Nexus 4s so this is clearly a software configuration problem.

I having following bluetooth issues in my Galaxt Nexus

1. My Car bluetooth device failed to import contacts & call history.
2. Bluetooth connection disconnect & reconnects and my car activation voice navigation keeps saying "phone connected" again & again.
3. bluetooth sound value is too low

I didn't have any issues with another phone using the same car.


Android Device:
==========
Android 4.2.1
Build Number JOP40D
Model Galaxy Nexus GSM
Up to date with system updates

I find this unbelievable I can no longer use my Bluetooth devices. I will warn all potential purchasers off Android devices on the four websites I run. Google react

Update seems to be on its way.
https://android.googlesource.com/device/samsung/maguro/+/android-4.2.1_r1.2

Bluetooth fixes are included, so lets hope the OTA Update is released soon.

Just got 4.2.2 and still can't turn on bluetooth. Haven't been able to since 4.2 came out. This is ridiculous.

I've got 4.2.2 OTA this morning. I still can't turn on bluetooth!  
It's very dissapoint me, because a have a lot of bluetooth device and i can't use them from november  with my galaxy nexus! Please FIX THE BUG.

Have you tried a factory reset? Might be the only option.

I couldn't turn on bluetooth (it immediately turned off) on my Sprint Galaxy Nexus when I updated to 4.2.1 until I fixed the permissions on libbt-vendor.so (as suggested above and in the similar issue http://code.google.com/p/android/issues/detail?id=40126).  Since then, it's worked fine.

That didn't work for me on my Nexus 4. The permissions on libbt-vendor are already as they should be. I still have the problem that when the BT issue appears, the only way I can solve it is with a reboot.

4.2.2 OTA update and no issues here! Perfect BT connectivity on my galaxy
nexus and Volvo.

Robertso, what version of the volvo bluetooth are you using?

@Robertso: can you confirm you had issue when using version 4.2.1 ?

Absolutely I had issues with 4.1...

Had the BT software updated on the v50 when it was serviced. But the 4.2.2.
Hasn't presented a problem..all is working as it was on 4.0
 On Feb 16, 2013 12:00 PM, <android@googlecode.com> wrote:

I think 3 months is long enough. One would think that with 10s of millions
of that broken devices out here there would be some sense of urgency.
Perhaps if google starts receiving 10s of millions of RMA requests the
seriousness of not fixing the problem will become more apparent.

Factory reset fixed it for me, and and still working after 4.2.2 update

Problem still persists on 4.2.2. The only workaround I have found is to never turn off the bluetooth radio.

Problem still exists on 4.2.2. Factory reset didn´t fix the problem for me.
Bluetooth does not activate sometimes.
Only a reboot solves the problem.

It won't be turned on after tuned off after turn-on and turn-off worked for a few days, same problem as before (currently it is 4.2.2).
My Nexus 4 Wifi and bluetooth are tuned on and off on demand manually. Never-turn-off is only solution? Disappointed on slowness in fixing must-have feature.

Having the same issues with the Nexus 4 running the 4.2.2 update ... Google, give us some hope!

After upgrade to 4.2.2 OTA, bluetooth is working slightly better, but that
makes it even more irritating as malfunctioning has now become
unpredictable. At least before I knew it wouldn't work, now I can't help
but get my hopes up and be disappointed.

Device: Samsung Galaxy Nexus UNROOTED, un-messed with for now (but I'm
tempted)
Android version: 4.2.2
I9250XXLJ1
Build JDQ39

Problem description: bluetooth switches on, paired with Audi MMI handsfree,
able to make calls most of the time but the car will lose the phone
sometimes after a call, sometimes even without making a call. Most of the
time (but again not always) I need to restart the phone to be able to
switch off bluetooth, otherwise it stays in a sort of half on-half off
state - and then I can't use bluetooth anymore, obviously.

Google, is this linked to the permissions for file
"/system/vendor/lib/libbt-vendor.so"? Switching to "755" seems to work fine
for some of us.

Please, just get this fixed. What's keeping you so long?

Same issue. For me it will only not turn on if I turn it off. A reboot clears it.

O had same problem but I've solve it. On my Nexus 4 and Nexus 7 enough turn off device with pressed volume down and power off key (out was about 6 seconds). When I turn on my devices I can start Bluetooth normally.

I also have a problem when trying to pair with a bluetooth datalogger using the SPP profile.
My Nexus 7 3G cannot find the device. The android version on the nexus 7 is 4.2.2
This same datalogger works perfect with android devices that have android version 4.1.2 installed.

Holding the volume down and power off key for 6 seconds, let the device reboot itself worked a treat!!!

Thanks so much!!

The same problem here: BT won't turn on with Android 4.2.2.
Could someone at Google address this major issue, please?

This is a big drawback on the nexus 4 great features.
Soon is already late for a solution.

Thanks

[Comment deleted]

Still happens in 4.2.2 on Nexus 4
Related bug: https://code.google.com/p/android/issues/detail?id=42520

I spent a good long while trying to get this fixed!  Thankfully someone at XDA figured it out.  Apparently the file permissions on one bluetooth software component are set incorrectly, as discussed here in this thread:

http://forum.xda-developers.com/showthread.php?p=35889721#post35889721

/system/vendor/lib/libbt-vendor.so was set to  rw-------

I used a file manager (and root access) to set the permissions to rw-r--r--

Rebooted the phone.  And voila! Works again.

Google, doesn't that seem like an easy fix?  Think of those who aren't going to dig into code (or frequent XDA) to get help!!

[Comment deleted]

The problem is that if the only way to modify the permissions on that file is to root the phone voiding the warranty this is inacceptable....!

Solved for me too changing permissions! Thanks so much for this solution

Mine was already on rw-r--r-- still doesnt work, continues to turn off as soon as I turn it on. Somebody help!!!

I've 4.2.2, mine was already rw-r--r-- too, i tought I had solved with this fix but now I see it's the same as before, sometimes it works and connects to my car, sometimes it doesn't, usually if it disconnects, when I enter the car again it can't connect and I need to disable and re-enable bt....

Well done Google.

Been following these threads (there are about 30 on this bug tracker, tracking similar BT issues) for about 8 weeks now and I keep seeing the same trends:

Google won't take responsibility for the fault. One developer implies it will be fixed in Key Lime Pie.

Now, I would happily wait 6 months for that to happen, perhaps even plumping for an N5, but judging by Googles complete inability to recognise, communicate and fix the issue, I've just ordered a Galaxy S3 for £20 more than an N4. Google have simply failed to instil faith in their competence at fixing this and this is seen among other users on these threads.

So congratulations Google. Your incompetence is now not only losing existing customers, but also potential new ones. Which is a shame because the N4 seems like a great piece of kit, save for this one minor bug (I played on a friends N4).

I'll be unsubscribing from all trackers soon. Come Thursday, I just won't give a shit about the Nexus as a brand anymore.

For reference, I have borrowed an old HTC Wildfire (after my Nokia E5 gave up) and now want to give the phone back and get something a bit quicker. N4 was in the spotlight, but now I've voted with my wallet. 8 weeks is frankly, long enough and in fact, this issue has gone on MUCH longer than this.

I'm not advocating others jump the Nexus ship. Google may well get their act together. But for me personally, I'll be moving into a job role soon where reliability of features on a phone is more important than anything else.

Settings,apps,swipe to all, find sharing bluetooth and then remove cache...

[Comment deleted]

[Comment deleted]

[Comment deleted]

[Comment deleted]

[Comment deleted]