IssueTracker

Hi there,

Thanks for reporting this. Do you mind attempting to install again? If there's no bin/ folder, that suggests an incomplete installation.

I installed again and again, uninstalled, installed for all users, not just me, everything. Doensn't help.

Maybe this helps:

Output folder: C:\Users\Paul\AppData\Local\Google\Cloud SDK
Checking for Python 2.7...
Create folder: C:\Users\Paul\AppData\Local\Google\Cloud SDK\google-cloud-sdk
Extract: google-cloud-sdk\install_google_cloud_sdk.py... 100%
Downloading Google Cloud SDK and installing components...
Traceback (most recent call last):
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 99, in <module>
    main()
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 83, in main
    archive_path = DownloadArchive(t, url)
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 63, in DownloadArchive
    req = urlopen(url)
  File "C:\Python27\lib\urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "C:\Python27\lib\urllib2.py", line 431, in open
    response = self._open(req, data)
  File "C:\Python27\lib\urllib2.py", line 449, in _open
    '_open', req)
  File "C:\Python27\lib\urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "C:\Python27\lib\urllib2.py", line 1240, in https_open
    context=self._context)
  File "C:\Python27\lib\urllib2.py", line 1197, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>
Adding C:\Users\Paul\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin to the PATH.
Unsetting CLOUDSDK_PYTHON environment variable.
Google Cloud SDK has been installed!

Thanks for the additional information.

Looks like your Python installation is having a hard time connecting securely to Google. What Python version are you using? What happens when you run

    > python -c 'import urllib2; print urllib2.urlopen("https://dl.google.com/").read()'

using that Python installation.

We need to do a better job of detecting when the installation fails.

I'm using python 2.7.10.

As far as I can tell, it is the same error.


>>> import urllib2; print urllib2.urlopen("https://dl.google.com/").read()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python27\lib\urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "C:\Python27\lib\urllib2.py", line 431, in open
    response = self._open(req, data)
  File "C:\Python27\lib\urllib2.py", line 449, in _open
    '_open', req)
  File "C:\Python27\lib\urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "C:\Python27\lib\urllib2.py", line 1240, in https_open
    context=self._context)
  File "C:\Python27\lib\urllib2.py", line 1197, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>
>>>

Okay, then it's a problem with the way Python is hooked up to your computer's certificate store, or a problem with the certificate store itself.

Can you try connecting to that URL using a web browser (one that's not Chrome would be great, since I think Chrome does some funky stuff with its certificate stores). IE or Edge would be great.

Well, I'm not really good at reading or writing code, so the only thing I can see it should download https://dl.google.com/dl/cloudsdk/channels/rapid/google-cloud-sdk.tar.gz

I downloaded this file using browser, extracted it and tried executing install.bat because I'm on windows.
This happens:

Welcome to the Google Cloud SDK!

To help improve the quality of this product, we collect anonymized data on how
the SDK is used. You may choose to opt out of this collection now (by choosing
'N' at the below prompt), or at any time in the future by running the following
command:
    gcloud config set --scope=user disable_usage_reporting true

Do you want to help improve the Google Cloud SDK (Y/n)?  Y


This will install all the core command line tools necessary for working with
the Google Cloud Platform.

ERROR: (gcloud.components.update) Failed to fetch component listing from server. Check your network settings and try again.
Google Cloud SDK installer will now exit.
Drücken Sie eine beliebige Taste . . .

Upon further research, it looks like you're hitting this OpenSSL bug: http://stackoverflow.com/questions/27804710/python-urllib2-ssl-error/27826829#27826829

We'll take a look at ways that we can work around this bug on our end. You may be able to use a solution like the one here: http://stackoverflow.com/a/31915123/4922212

I just downloaded Python 2.7.9.
It worked! Thank you!

Doesn't work for Python 2.7.10 & 3.5.0
Works fine for Python 2.7.9

We've added a workaround for systems with incorrectly-configured certificate stores for Python and we're targeting Cloud SDK release 0.9.88.

0.9.88 is out. Please let us know if you can still reproduce this issue.

This issue is still happening with a download i tried few mts back. Can you please help?

What's the error message you're getting? Can you paste it here?

Output folder: C:\Program Files (x86)\Google\Cloud SDK
Checking for Python 2.7...
Create folder: C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk
Extract: google-cloud-sdk\install_google_cloud_sdk.py
Create bat file: C:\Program Files (x86)\Google\Cloud SDK\cloud_env.bat
Downloading Google Cloud SDK and installing components...
Traceback (most recent call last):
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 99, in <module>
    main()
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 83, in main
    archive_path = DownloadArchive(t, url)
  File "google-cloud-sdk\install_google_cloud_sdk.py", line 63, in DownloadArchive
    req = urlopen(url)
  File "C:\python27\lib\urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "C:\python27\lib\urllib2.py", line 431, in open
    response = self._open(req, data)
  File "C:\python27\lib\urllib2.py", line 449, in _open
    '_open', req)
  File "C:\python27\lib\urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "C:\python27\lib\urllib2.py", line 1240, in https_open
    context=self._context)
  File "C:\python27\lib\urllib2.py", line 1197, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>
Failed to install.

Windows 10
Python 2.7.10

Trying "urllib2.urlopen("https://dl.google.com/").read()" directly yields:

print urllib2.urlopen("https://dl.google.com/").read()
  File "C:\Python27\lib\urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "C:\Python27\lib\urllib2.py", line 431, in open
    response = self._open(req, data)
  File "C:\Python27\lib\urllib2.py", line 449, in _open
    '_open', req)
  File "C:\Python27\lib\urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "C:\Python27\lib\urllib2.py", line 1240, in https_open
    context=self._context)
  File "C:\Python27\lib\urllib2.py", line 1197, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>

I installed from the zip/archive and this *worked*. So, it appears to be a problem with the Windows installer.

Thanks for letting us know. There shouldn't be any differences between the Windows installer and the zip/archive installation method, so something's a little fishy. We'll investigate.

Is there any chance that you're using different Python installations in the installer vs. when installing from the archive?

It is possible (and I will check). The python installation on the Windows machine is updated (since I installed the Cloud SDK previously was working) and I don't recall doing it. This was my motivation for upgrading.

It used to be in c:\python27_x64 (2.7.9) and it is now in c:\python27 (2.7.10). Gcloud was working. When I tried to use it yesterday (before upgrading), it threw errors at being unable to find the python interpreter and, when I checked c:\python27_x64, the directory contained neither python.exe nor pythonw.exe (?) and I assumed this was because the previous version had been uninstalled.

After I installed from the archive, I had to  manually set CLOUDSDK_PYTHON to the new directory in order to use gcloud.

I checked the Windows machine and am confident (not certain) that there's only one (2.7.10) python installation on it. As I recall the installer logs that it found a python interpreter but doesn't (?) provide specific information on where/which python interpreter.

Now that you have one fixed version of python, can you please try installing using the installer to see whether it still encounters an error? Thanks.

same-same

and... I didn't fix anything. The check appeared to prove that I only had one version of python installed 2.7.10

I am too getting the same error.
I logged in to Cygwin
run the command curl https://sdk.cloud.google.com | bash
it first asks for installing in my home directory - I Enter
then a bunch of files get downloaded

$ ls -lrt google-cloud-sdk/
total 91
-rw-r--r--  1 USER Domain Users 63916 Apr 21 13:56 RELEASE_NOTES
-rw-r--r--  1 USER Domain Users   684 Apr 21 13:56 README
-rw-r--r--  1 USER Domain Users    31 Apr 21 13:56 path.zsh.inc
-rw-r--r--  1 USER Domain Users   308 Apr 21 13:56 path.bash.inc
-rw-r--r--  1 USER Domain Users   980 Apr 21 13:56 LICENSE
-rwxr-xr-x  1 USER Domain Users  3509 Apr 21 13:56 install.sh
-rwxr-xr-x  1 USER Domain Users  1581 Apr 21 13:56 install.bat
-rw-r--r--  1 USER Domain Users  1945 Apr 21 13:56 completion.zsh.inc
-rw-r--r--  1 USER Domain Users  2338 Apr 21 13:56 completion.bash.inc
drwxr-xr-x+ 1 USER Domain Users     0 Apr 21 13:59 platform
drwxr-xr-x+ 1 USER Domain Users     0 Apr 21 13:59 lib
drwxr-xr-x+ 1 USER Domain Users     0 Apr 21 13:59 bin


/home/USER/google-cloud-sdk/install.sh
Welcome to the Google Cloud SDK!
/home/USER/google-cloud-sdk/install.sh: line 128: C:\python27\python.exe: command not found

Tried so many times but still getting same error. Using WINSOWS 7 Enterprise. Cygwin Setup Exe version 2.874 ( 64 bit ).
I had Python installed on my system and the Path was also updated. Again I tried to install Python from Cygwin. that didn't work. Now I uninstalled Python from my system and removed from Path still the google-cloud-sdk installation fails.
The only thing I have changed above is from my userid to USER.

$ python
Python 2.7.10 (default, Jun  1 2015, 18:05:38)
[GCC 4.9.2] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
[3]+  Stopped                 python

I have the right version of Python for Cygwin. No other python sw on my system.

gcloud comes as a Windows native application and set of commands. You do not need Cygwin to get it to work. Simply install Python for Windows and the gcloud SDK for Windows. It should work simply using the Windows command prompt.

If you must use gcloud with Cygwin for some reason, please describe why as some hacks are possible but not favorable.

Is anyone here still encountering issues when installing Python >= 2.7.10 for Windows to C:\python27 and the gcloud SDK for Windows with the installer[1]? There's also an installer for Windows that comes bundled with Python should someone need the convenience.

This issue is due to close in a few days.

[1]: https://cloud.google.com/sdk/downloads#versioned

As there has been no new activity on this thread for some time, I am closing it as Obsolete.

Should you still be encountering this issue and none of the above solutions/workarounds work for you, please open a new issue linking back to this one for context.

Be sure to include the output of 'gcloud version' and any other information you think might be relevant to the issue.

@28 - I was thinking the same thing.  It makes me wonder if it's a universal issue with 4.2, or if we are just the "lucky" few.

If I were an Android developer, and I drove home from work the day 4.2 came out and I had to listen to static and crackling over the music in my car, I'd have to turn around and try to fix it that night.

It does it on both my Nexus 7 and my gnex. Highs are terribly distorted. Don't want to go back to 4.1.2, but might have to.

I had to revert back to 4.1.2. I tried to get used to over compressed a2dp, but I just could not stand it. After pushing 4.2 camera and keyboard I hardly miss the "real" 4.2.

@29. It does on both my Ford sync and logitech receiver on both my Nexus 7 and gnex. I would lean towards there being a significant number of people with this issue. Unless both of my devices are effected by the same 4.2 defect. Had to go back to 4.1.2 on my phone because of it. Can deal with the sound on my tablet since the only bluetooth I use is for tv/vocal.

poor bluetooth audio on Nexus 4 4.2.1.   Also... no track info for car display.  Please fix, aux cable is sooooo 2008.

The question remains....Does Google acknowledge any of our problems?

After the upgrade to 4.2.1 on my Google Nexus 4 phone the voice quality with an bluetooth earbud has become very poor.  Have gone back to a wired earbud until issue is addressed.

Commenter 35 - Don R, and others with a Nexus 4, if you I read you correctly, BT voice quality on your Nexus 4 was working satisfactorily prior to updating to 4.2.1 -- can you confirm?  I ask because the BT voice quality on my just-received Nexus 4 with 4.2.1 is terrible, rendering it basically unusable (with voice recognition over BT completely broken), but I didn't try it prior to the upgrade.  I'd like to be sure it is a software issue & that I didn't receive a lemon, since BT voice is a critical feature for me, and most of the reports I've seen about BT voice with 4.2.1 have seemed to be with other devices, not the Nexus 4.

@36. See my comments 25 & 27. I received a replacement N4 that had several other issues besides A2DP settings. If the issues you describe match the ones I listed above, you might have a lemon too.

My original N4 (the one I'm using now and keeping) has no other issues besides Bluetooth audio playback. All phone conversations sound fine, and voice recognition is fantastic.

@37 - Thanks -- so to confirm, on your original N4 BT phone conversations & VR are working well *after* an upgrade to 4.2.1?  That is disappointing :( -- with all the BT issues around the update, I'd been hoping that this was a manifestation of that; but I guess now I do need to worry about the possibility of faulty BT specific to this device (which seems to be fine in other respects).  It's rather frustrating that the BT software in the current release is so problematic at the same time, really muddies the waters.  Any other device, if it's faulty, np, get it replaced but with the N4 it sounds like good luck getting another functioning one before next July.

@35 For you, though, your comment implies that BT voice on your N4 was working well prior to 4.2.1 and then became problematic after the 4.2.1 upgrade.. is that correct?

Correct, everything on my original N4 works fine except Bluetooth audio playback.

Google Play does have devices for warranty replacements. I got my replacement within 3-5 business days.

@40 - Thanks. It doesn't sound like the replacement device they sent you was terribly satisfactory to you, though.. :(  Maybe just bad luck.. But I wonder if it might be "refurbished" (i.e.: recycled to other customers) devices starting to make the rounds.

I BOUGHT THE NEXUS7 FOR ITS' BLUETOOTH ABILITY AND IT WAS GREAT.THEN THE UPDATE MADE THAT FEATURE THE WORST PART OF THE TABLET.MY QUESTION IS:DID ANYBODY THINK TO TRY OUT BLUETOOTH DURING THE UPDATE PROCESS(ENGINEERS,SOFTWARE DEVELOPERS,ETC.)FOR AT LEAST 30 SECONDS?..AND WHAT DOES THIS SAY ABOUT GOOGLES' FUTURE UPDATES.I'VE BEEN A MAC USER FOR OVER 30 YEARS AND I HAVE NEVER SEEN SUCH A BLATANT OVERSIGHT SUCH AS THIS IN THEIR PRODUCTS.THE LEAST I WOULD EXPECT IS AN ACKNOWLEDGEMENT OF THE PROBLEM WITH A SMALL APOLOGY AND AN ASSURANCE THE PROBLEM IS BEING ADDRESSED.T.RUSSELL

You're probably not helping at all. All caps and pointing fingers
accomplishes nothing.

This is not a place to yell about issues, but rather show the
developers that it's widespread. If you want to rant, start a blog.

The issue is being looked at (see @2). The Android devs have accepted
it as a case. Done. Now we wait, as expected for software development
of this nature.

I'VE JUST STARTED.

I have the Samsung Galaxy Nexus 4.1.1. Bluetooth phone calls have been unusable for 4.1.1 and the previous release. Bluetooth worked fine until I upgraded to ICS. Problem continued with JB.
I can barely understand what the party I'm speaking to is saying using any of the three Bluetooth headsets I've tried. A wired headset works fine and is what I'm using until this gets fixed.

@45 - I don't know for sure, but yours might be a different issue.  We are having issues with Bluetooth audio on Android 4.2.  I think 4.1 was working fine for those of us who are experiencing bad audio quality with 4.2.

Galaxy nexus w/ 4.2.1 Just got a new car w/ BT audio. Same issue with minor but noticeable distortion for high frequency sounds. Generally happy with my phone/software, but this needs to be dealt with!

Well also report on my Nexus 4 with 4.2.1 I have having issues with high frequency ranges. Lows and mids sound ok abut highs and some vocals can be heard to be compressed more.

I've had the LG HBS-700 bluetooth headphones with my previous phone, HTC Inspire, and they sounded great without noticeable 'compressed' sound. My Galaxy Nexus also worked and sounded fine until the OTA update to 4.2. That is when the music had a very compressed sound, specifically on high frequencies (especially percussion instruments). I have tried replacement bluetooth headphones. Cheap wired headphones do not have this issue. Different audio players, including Google Play Music have the audio issue over bluetooth.

#49, this really makes me wonder if this is on all 4.2 devices and people are just not noticing it. I have a Nexus 7 along with a galaxy nexus and they both do it on my logitech receiver and my Ford sync. So, I guess my question is if anyone is having the problem on one bluetooth receiver and not on another. Or, last possibility, are only certain devices effected by this? Something in the actual hardware that is different in certain devices?

My nexus 4 and galaxy nexus both have distortion on my factory head unit in my subaru Sti. Very annoying.

I just switched from a Blackberry device to the SG3 and getting crackling on all voice calls through my brand new Silverado. Didn't have this problem with the Blackberry. Any have any info on a fix?

#52. The problem people are talking about on this thread is the distortion in the upper frequencies on 4.2 and 4.2.1. The s3 hasn't been updated to that yet. As for your problem I am not sure if there is a fix. You could try different rooms, though I am not sure that would help. You could also see if it does it through another bluetooth device/car. Sorry I couldn't be of more help.

If it is just the static and crackling distortion to the audio, the fix is to just raise the bitpool back to where it was in 4.1.x.

How do you edit the bit pool?

The bitpool that the device uses is set in the android source code itself.  There would need to be an OS update to fix this.  They did this before if I recall when Android was updated to 2.2 or 2.3.  I don't understand why it regressed back.

#50. My Samsung Galaxy Tablet 2 7.0 with Android 4.1.2 works just fine with bluetooth headphones.

#56, so that would indicate that everyone using bluetooth is experiencing this on 4.2 and 4.2.1. So everyone saying that their bluetooth is fine on 4.2 and 4.2.1 just had a tin ear? Or is it device specific? I was leaning towards the former, though it is really hard for me to believe more people aren't complaining about this if it effects every device running 4.2+.

Joey...  4.1.2 works well...Upgrade to 4.2, that's another story, a bad story actually. That's where the problems lies.

I too have the same problem with clipping in the high frequencies, primarily audible in cymbals and orchestration. There is also noise and other artifacts in quiet passages. At first I was convinced that it was a problem exclusive to Bluetooth being broken in 4.2 and 4.2.1, since I first noticed the problem when I got the update on my Galaxy Nexus and Nexus 7. However, I am also hearing the same artifacts on my Motorola Xoom, which is still on 4.1.1. so I think there might be a problem with the Google Play Music App as well. It was also updated around the same time to support gapless playback, and I think something might have been broken in the app when they added this feature. Does anyone have an old version of Google Play Music they can roll back to to test this out?

#60, I didn't notice till 4.2. When I rolled back to 4.1.2 it went away. That is not to say that the audio quality ever was audiophile material, however it was fine on my ear in my car on 4.1.2 even with the most recent Google Music app.

I cannot even connect to my wireless speakers anymore.

The new bluetooth stack is a jumbled mess.  Google should really be doing better than this.  What a mess.  It's back to wires or 4.1.2 until they fix this garbage

Have had issues in my Acura TL on horrible BT call quality. Paired up my brothers Galaxy Note (4.0.3) and it sounded perfect. I was beginning to think it was my HF system in my car as I have had issues ever since 4.1 on my gnex and now nexus 4. Any other people having issues in their acura ??

I was so happy with Bluetooth audio when it finally became listenable in 4.0. Now it is back to this horrible, compressed, low-bitrate junk. Just when people have started making Bluetooth android docks too. Shame on you, Google.

I just can't believe that this sound quality could get past everyone. I guess all the programmers were listening through their monitor speakers.

Nexus 7 with Android 4.2 and BT Creative T12 bluetooth speakers same issue

Same issue here...it sucks listening to BT Audio in my car now using my Nexus 4 =( Galaxy nexus 4.1 was excellent

Is there any way to edit the title of this issue to remove "with Galaxy Nexus", since this is an issue with Android 4.2, and not phone-specific?  There could be other users out there who are not starring or replying to this post, simply because of the title.

For me, Bluetooth works fine if the screen is on but cuts out every few seconds if the screen is turned off.

Comment 70. The problem people have in this forum is distortion in the high range. Listen to a cymbal heavy piece and I would assume that yours does it too. Though I am not sure if it effects all 4.2 devices.

Comment 71:
Problem that peopla has is A2DP being transferred to receiver with lousy quality (bitpool value is low) even the receiver supports direct streaming without re-encoding the stuff.

Those who cannot hear this bug have tin ears, or they have used to listen lousy quality mp3's for their entire life and they cannot hear the compression artifacts.

I have the same issue with my GNex since 4.2.
I remember equally bad sounding a2dp from my HTC Desire with 2.3.
Why is this such a recurring problem?
As for not using direct MP3 streaming:
Am I right to think that this has something to do with the muxing off all the audio sources in the system (input sounds, music, message sounds)?

Comment 72. I think you might be right. It surprises me a bit that so many people don't hear this. Some source material make it painfully obvious. To me it is un listenable.

Same for me with my Bose BT speaker, needed to reactivate my 5 years old HTC phone to  listen to music.
Really bad exoerience , please fix this obvious problem!

Same problem on my Nexus 4. Static on higher frequencies when listening via bluetooth in my car.
I was so happy with my new phone. Everything seemed to work like a charm until I paired it with my cars bluetooth. Very disappointing...
Google please fix this ASAP. It should not have passed quality control.

It's been a month and a half and this still isn't fixed? It worked in the previous version - just copy the code!

This is really harming the Android brand a it is fundamental to those 'universal' speaker docks that people seem to love buying.

at Comment 77: (someone correct me if I'm wrong) From what I read, the Bluetooth "Blue Z" stack was completely replaced in Android 4.2 with "Bluedroid" stack that Broadcomm just released to Android right before 4.2 came out. It's supposed to support smart BLE = Bluetooth Low Energy. But there's one problem - not all of the files of the new stack were pushed to the repository! So I think we are waiting on Google to wait on Broadcomm since the stack is incomplete. So much for open source eh? Search "Bluedroid implementation missing GAP" and "Android 4.2 JB MR1 Bluetooth" in Google Groups.

Same problem here with 4.2.1.
In CM 10.1 same issue of course :(

I bought the nexus7 as soon as i found out it had bluetooth.I teach guitar and thought what a great way to teach with the app irealb.So i buy fedelios' speaker system(around $90)and everythings going so good i talk 5 students into getting the tablet.Along comes 4.2 and after months of bluetooth bliss there's an unmistakable stutter in the sound.I set up some MACKIE POWERED SPEAKERS and ran directly into them and now I've found a way around the stutter.Every now and then i glance over at my useless fedelio speakers and think what's going on here?But here's where I lose it..google emails telling me i must have a bad unit.How can i ever trust a company that denys there's an obvious problem.For now i'm telling everyone i teach or meet,don't buy this ..not because of the update glitch but because of the way they are handling it.The mini pad is my next purchase.In the future google ,face up to a mistake,admit it,tell us there's a fix in the next update and move on.This IS BAD PUBLIC RELATIONS and whoever in your company decided this was the best way to handle this should be looking over his shoulder.

This should be a high priority defect, one the major features I use my android phone is for music via bluetooth.   I just upgraded to 4.2.1, but unless this issue is resolved is a few weeks, I'll be migrating back to 4.1.2.

FIX THIS!

Comment 81. It is shocking to me that more people don't complain about this. I think that most people don't even notice it. I don't understand how they don't. But unfortunately, until a ton of people start complaining it probably won't get fixed. The other thing to consider is just because developers are good with programming doesn't mean that they don't have a tin ear.

@79 All Roms on 4.2.1 are also affected. Best to wait until 4.2.2 or stay on 4.1.2 Shortage on Nexus 4 is understandable. This issue is completely unacceptable.

Could we please have a status update on the fix for this issue?

Priority-Medium ???

FFS Google! This should be prioritized as high or critical!

At least give some feedback to your users if you are working on this and/or when you plan to have a fix available.

Same here on my Nexus 4 4.2.1. The low bitpool issue seems to be a wide spread issue on android devices. Never had this in my iPod or iPhone.

Cmon Google, fix this! 90% of what I use my phone for is music.

Get your shit together Google. This is something that obviously alot of people use everyday. This should have been fixed...

In my case, it got fixed by a factory reset. I had played with multi user
support using some 3rd party root app before it got in 4.2 and I had 4 user
profiles. I was hit by another issue, my nexus7 was very slow and laggish.
after factory reset, speed is restored, so is the smooth audio.
Le 10 janv. 2013 16:14, <android@googlecode.com> a �crit :

@89 What do you mean by smooth audio? No stuttering? That is not discussed here, at least it't not the main point.
The Problem is the lower quality since the update. You can hear it very well if with hich pitched complex songs.
I am very dissapointed that there is no response from google here. Could someone tell me if it's not possibe to add an Option for direct MP3 streaming?

Actually...the stuttering issues was mentioned originally weeks ago as soon as or even earlier than the quality issue and it is discussed here regularly as well. I went back to 4.1.1 on my 7" Nexus because the update created stuttering every 5 seconds or so. This has been a major theme of the 4.2 update problems.

But it is not the issue described in this ticket. I was just answering because 89 made it seem like the quality issue was fixable with a factory reset. Which it is not.
The stuttering also seems to be dependent on source and/or target device.
My GNex has no bluetooth stuttering at all with the current Version.
The low quality seems to be an issue on all 4.2.1 devices.

Apparently, Google is going to be addressing the stuttering issue with 4.2.2, based a few articles I've read recently. No mention of the distortion issue, though.

@ zprew...@gmail.com

Can you provide the articles that your referencing?

I've had the clipping at high frequencies issue since day one. Hope to see that fixed and maybe Google gets with it and adds avrcp 1.3 support :)

[Comment deleted]

I have the same problem in 4.2 using my Nexus 7. Static and clipping at high frequencies. I bought this tablet to run through my car's bluetooth stereo, and it sounds awful! My old chinese tablet running 2.3.3 sounds perfect by comparison!

@98. Though not an ideal solution.  You might want to go back to 4.1.2 on the Nexus 7.  At least then the bluetooth will sound ok.  Unfortunately for the Nexus 4 owners there is no rollback version to fix this problem.  I can't believe Google missed this. Hopefully, they realize it is a problem now.  Sadly, it doesn't look like too many people are complaining about the problem. Though I believe that it effects everyone. That would mean that either people don't use Bluetooth audio or just don't hear the clipping in the high frequencies.

Not sure if it's the same problem or not, but the Bluetooth call quality between my Galaxy Nexus (Verizon) and my vehicle is horrible. Calls constantly fade in and out. I haven't tried the music yet via BT, but I will today.

Same Exact issue as #100, Galaxy Nexus , verizon, 4.1.1.  Quality between Nexus and Vehicle is horrible.  I tried iphone 4, Galaxy S, They work fine.

Same issue.  High end sucks.  FIX!!!!

Just replaced an iPhone 4S with Nexus 4 thinking the Bluetooth link would be an acceptable alternative to the 30-pin Dock Connector for my car's audio system.  Really sucks that I'll have to eat the restocking charge to return it, but I'm not paying this kind of money to step-down to an aux-in jack without playback control or charging, when I already have a device that'll do both as well as content browsing directly through the head unit over one cable.

It looks like this has been an issue since November that still hasn't been resolved.  If adding one more comment will help move it forward, there he is one more comment: please figure this one out.  It feels like a memory management problem, but what do I know?  The exact symptoms I'm experiencing are:
1. Music & in-coming call audio stutter.  It may be significant that my preferred audio book player (Morte) actually skips back 5 sec. each time as if I had deliberately paused the book.
2. Outgoing voice over Bluetooth cuts out (two different headsets)

When playing music there is a noticeable presence of static when playing non-quiet songs.  It's most present when a 'high-hat' instrument is played.  It is not a user controlled volume issue, nor is it the bluetooth receiver's issue.  I have verified that it is only an Android issue by comparing the audio quality from an iPhone4, which sounded fantastic.

It seems that the audio is clipping when being sent to the bluetooth receiver.  But as stated before, no changes in any volume settings solves the problem.  

In total agreement with #105's description of the problem.  I noticed the same thing recently when I tried out a friends Jabra Clipper.  I was pretty excited when I heard the sound quality using his Galaxy S3 with his Clipper and my Ultimate Ears 10.  So much so that I almost ordered one from Amazon with next day shipping.  Good thing I said "wait a second, let's try this on my phone".  Things seemed okay at first until I noticed that sizzling, gritty, distortion like quality when the high frequencies kicked in, especially if the passage was a bit complex.  Oddly enough, the bass was very strong and detailed, the midrange was very clear and pretty neutral sounding for a phone using bluetooth audio, and the stereo seperation wasn't any worse than when using my headphones connected directly to my GN.

Forgot to include that I'm running LiquidSmooth 4.2.1 on my Verizon Galaxy Nexus.  I never had issues with Bluetooth audio using 4.1.x ROMs.

Experiencing this on my GS3 running CM10.1 nightlies as well.  Worked perfectly on stock rom.

Stock 4.2.1 on Nexus 4 here. Notice it most in my car with Chimes (Blink 182 =)

Still a noticeable tinny sound with stock 4.2.2 on both my Galaxy Nexus and Nexus 7. Never encountered it with 4.1.

#110...not what I wanted to hear. Is there still compression in the upper frequencies on 4.2.2.

#110.... bad news!  I was really looking forward to 4.2.2 to have this resolved.  Seriously Google?  

I don't think this is as highly reported simply because people probably don't know what good quality sound is.  It's seriously frustrating.

#110 - i'm gonna flip my shit if this isn't resolved in 4.2.2.  I was hoping all I had to do was wait for CM to merge 4.2.2 to fix this issue.  I'm hoping you're mistaken!

I tested with a bluetooth adapter and the Nexus 7 with 4.2.2 in my car.  I can confirm that this issue still exists.  It is not as bad as before, but it is still there.

Unfortunately, distortion in the high frequencies has not been fixed with 4.2.2. Sound quality still sounds like shit. This is really upsetting. I miss streaming music through Bluetooth. I also have to ask, how have Google engineers not noticed the poor sound quality? It used to sound fantastic before.

I guess I am stuck on 4.1.2 a little longer. Come on Google!

Has anyone upgraded to 4.2.2 and noticed an improvement?

[Comment deleted]

Can verify that Bluetooth still sounds distorted in 4.2.2. Don't notice an improvement.

Updated to 4.2.2 yesterday, and everything seems to have been fixed.

Updated to 4.2.2. Don't notice an improvement.

#120 This issue is with the quality of sound. Not the dropping the connection. I updated to 4.2.2 and didn't notice any improvement. Still clipping in the high frequencies. Hook your phone/tablet up to a decent stereo and you will notice it. Listen to something with a lot of high frequencies. Cymbal crashes and splashes along with high hat work really accentuate the distortion.

with nexus 7, android 4.2.2 and creative bluetooh speaker the issue don't fixed :(

Galaxy Nexus, 4.2.2, still disappointing bluetooth audio streaming quality. I was sure that this issue would be fixed with this update. I miss my neo v. Is there any way to fix this?

Just upgraded android to 4.2.2 on Nexus 4, having same issues - crackling sound from speaker during phone calls (without bt headset). Disappointing - hope it's fixed soon. What is the best way of getting Google's attention on this?

Urgh, 4.2.2 on GN still not fixed. Audio still sounds terribad.

124. The only way that I know is to revert to 4.1.2,which isn't even an option for Nexus 4 users.

I just upgraded my Galaxy Nexus to 4.2.2 and can also confirm that high-frequency clipping and distortion is still present. I love Bluetooth streaming in my car but 4.2 has made it unusable. No amount of volume leveling on either phone or stereo resolves the issue either.

Just got a nexus 4. The quality of music via bluetooth is really bad. Please help us google! It sounds like certain frequencies crackle.

Just installed a 4.2.2 ROM. I can confirm what the others have said.... the crackle/distortion is still present.  It doesn't seem better to me, unlike what a few others have said.  You've got to be kidding me Google.

Come on....this should be fixed by now!!!

Un frikkin believable. I waited for this update on my N4 and the bluetooth audio static is still there. I guess I just pissed away $375. Looks like Apple that I despise is my only alternative or revert to an android device that will run 4.1.2. Sad sad sad for a multi BILLION dollar company.

How is the priority level raised with issues like this one. Of the bugs in 4.2.2, I have to imagine this is fairly high up the list.

WTF! I thought 4.2.2 would fix this!

Come on Google!!!!!

Why oh why did I replace my iphone with this crappy android shit. Well, maybe you are not supposed to listen to music on your android smartphone?

It stills disconnect also at least after turning on/off airplane mode. Tried now for 2 days. Turn on airplane mode for the night turning off in the morning. Connect BT headset with phone it disconnects randomly and have to turn/off/on both the headset and bt on the phone in order for it to work again until the next time..:( I didn't have any of these problems with 4.1.2. (Galaxy NExus 4.2.2 with Nokia BH-218)

I have updated my Galaxy NExus from 4.2.1 to 4.2.2 but while I had no problems with 4.2.1 connecting and using it with my car (a 2012 Renault Megane), now i do and the bluetooth stack seems to hang. Usually I have to disable bluetooth and enable it again to make ik connect. Sometimes I lose connection, and other times I still appear to be connected even though I'm miles away from my car.
Biggest problem ( apart from not being able to properly using bluetooth) is this bluetooth stack hanging seems to be related to wakelocks (12 hours and only 20% battery left. This is with only 1,5 hours screen time but with android OS wakelocks for close to 9 hours.

#136 This thread is about the bluetooth quality. More specifically, the clipping in the high frequencies that seems to effect every 4.2+ device. People who aren't complaining simply don't notice it. (aka. Having a tin ear)

On my Nexus 7 on 4.2.2 the Bluetooth audio in the car still does the hiccup/hesitation, but I would say it's not as frequent as before...I can go 5 or 10 minutes in between hiccups.  with 4.2.1 it was every few seconds.  On 4.1 it was rare when the sound did this hesitation/hiccup.

JF

[Comment deleted]

The same issue here after flashing 4.2.1 rom on ONE X. I miss BlueZ BT stack, the new one - rewritten by Google is cr*p :(( Come on Google, my 8 years old Nokia streams cristal clear audio! :(

This thread is about problems with audio QUALITY! Please report your stuttering issues in the respective thread ( http://code.google.com/p/android/issues/detail?id=39633 ) and do not flood this one.

Cymbals are terrible splashing. Tought 4.2.2 would solve the problem, but it didin't.

I was hoping this was fixed with 4.2.2 as well, and still no go.

I've found a situation that makes the problem worse than music: my wife's bluetooth headset lets road noise through, and that ends up getting amplified so much that it sounds as if she's talking through a walkie talkie she swallowed, drowned out by lots of static.  It sounds fine if I listen through the phone speaker.

This isn't a mere inconvenience, and it needs to get fixed.

My Nexus 4 has been updated to 4.2.2. I cannot connect to my toyota camry. I am highly inconvenienced as I cannot take phone calls.

I have this Issue on a SGS2 running 4.2.2
(CM10.1 nightly as of 16.2.2013)

The issue is there since quite some time, I can't remember exactly when it started.

Symptoms:

Several Persons I talked to through my bluetooth headset reported that they receive very low voice quality. "as if it comes from a 1970s transistor radio" describes it best.

Also "my wife's bluetooth headset lets road noise through, and that ends up getting amplified so much that it sounds as if she's talking through a walkie talkie she swallowed" sounds like an appropriate description.

Galaxy Nexus user confirms the 4.2.2 did NOT fix the quality issue with A2DP streaming.

Restoring (again) back to 4.1.2...

HTC One XL with Samsung HS3000 apt-x bluetooth headset and Shure SE215s, sounded as clear as a wired connection on 4.1.2. Updated to 4.2.1 and it's now unlistenable.

Given that 4.2.2 on my Nexus 7 has the same problem, and seeing how long it takes for even minor Android updates to filter down non-Nexus devices, even via custom ROMs, I'm not optimistic about seeing a fix any time soon.

4.2.3, please?

Distorted high frequency in music, like in high vocals and cymbals. Using Galaxy Nexus 4.2.2 with Skoda Superb car audio (Amundsen+). E.g., Boston - More Than a Feeling at 0:50 when the chorus starts.

My Nexus 4 was out for repairs for the past few weeks, so I only got to upgrade to 4.2.2 last night.  I can also confirm that Bluetooth Audio quality still has the same distorted sound for high frequency music such as high vocals & cymbal crashes.

Matthew Xie, this defect has been assigned to you for over 3 months.  Could you maybe get around to fixing it at some point?

Same problem here with LG Nexus 4, distorted sounds on my car (Peugeot)
Please fix! :(

I grew tired of this issue keeping me from retiring my Android 4.1 ROM, so I started looking into it.  There seems to be *2* problems with bluedroid A2DP when compared with Android 4.1's blue-z implementation.

The first is the calculation used for the bitpool size. bluedroid is reverse engineering this value based on a default and quite arbitrary quality level, which is set to MEDIUM (229) instead of HIGH (328) for the 44.1Khz sample rate.  This can be seen in the external/bluetooth/bluedroid/btif/src/btif_media_task.c file [android-4.2.2_r1 branch] -- find "DEFAULT_SBC_BITRATE".  Blue-Z would use a bitpool of 53 for stereo A2DP, bluedroid ends up using 31, and the sound quality suffers greatly .. just like the old days.

Based on the A2DP spec, the bitpool for JOINT_STEREO "Medium Quality" at 44.1Khz should also be 35 rather than 31, but that's not really important :)  My proposed fix for this part is to change that DEFAULT_SBC_BITRATE value in btif_media_task.c to 328.  This will cause the resulting bitpool calculation to become 53, which is now correct for the default 44.1Khz sample rate.  [This of course doesn't help anyone that isn't compiling from AOSP ... sorry]

The second part is the gain/output volume. It's notably higher than it was in Android 4.1, which causes clipping and distortion, at least on my A2DP receiver.  I've found that setting the A2DP volume (which will be remembered by Android) to around 80% will provide the same output levels as Android 4.1 did at maximum volume.  I haven't really looked into this part any further yet, but my guess is that it's either a limitation of my A2DP receiver and not really a problem OR it's another very simple fix once somebody smart at Google looks into it.

The big big big improvement comes from changing that simple quality constant, though.  The secondary issue is quite easy to work around ... just turn the volume up until it clips, then back it off!

@ #151:

I changed it in the source for AOKP.  I used Task's build for my i747 device, and he builds from AOKP.  I'm still trying to get used to github..... but hopefully I submitted the patch correctly.

Google you need to fix this. Audio quality is unbearable. Can't make car calls anymore.

Another victim here.  Resorting to my CDs now while I'm driving.  Looking to downgrade to 4.1 just for this.

Re #151 (also me)

I bought a new A2DP receiver (Rocketfish RF-BTR212) today and tested both my custom 4.2.2 ROMs (Verizon Fascinate and Verizon Galaxy Nexus) with the quality set to 328 and they both sound really good.  It seems my statement about the gain was erroneous and it was indeed my old receiver not being able to handle whatever bluedroid is doing as compared with Blue-Z.  Still a hint of scratchiness at max volume, but one tick down and it cleared up.

Anyway, I'm still pretty convinced that one setting is the ticket to resolve the bulk of the quality issue here.  It's too bad that bluedroid doesn't seem to be as compatible with A2DP receivers as Blue-Z was, maybe in time.

Good luck to everyone, I hope this information has been useful and helps to lead to a real and verifiable fix from Google/Broadcom in the near future.

@ #151 and #155: Would you be able to provide a link to your Galaxy Nexus ROM? I'd like to test it out.

Re: #156 .. certainly.

** NOTE FOR FUTURE READERS AFTER 2013-03-03: VOLATILE DOWNLOAD LINKS THAT WILL NOT EXIST FOREVER! **

Here's my latest VZW Galaxy Nexus build "kit".  It's generally private and I only share for a couple co-workers, but you are welcome to it to do what you want.  It's a huge download (> 500MB) since it includes the stock 4.1.1 image so they can back it out (noobs, what can you do? LOL).  It's the same AOSP baseline as my "GeeWiz 4.2" baseline for the Fascinate (find on XDA if you care), just compiled for Toro.  Buyer beware, ok?  This isn't Cyanogenmod here, it's a fastboot-based full-wipe setup, so it may not be what you're looking for ...

http://www.mediafire.com/file/5ul18qfkmgesyda/galaxynexus-lte-djp952-20130301.zip

Given that I don't share that ROM with the public and is intended for a full-wipe scenario with fastboot over Windows, you may be happier with just the /system/lib/hw/bluetooth.default.so file itself from that build, so I zipped that up and posted it for you.  Provided the ROM/build you are running is based from am AOSP 4.2.2/JDQ39 Toro build, this may be sufficient.  Put the file in /system/lib/hw and then chmod it to 0644 and reboot.

http://www.mediafire.com/file/ujll8gtbhxnz32b/4.2.2-toro-aosp-bluetooth.default.so.zip

I hope this is enough to be of assistance, but I fear it may not be since every build/ROM is different.  Please feel free to point the developer/compiler of the ROM you use to this very simple 1-line commit on github: https://github.com/djp952/android-platform-external-bluetooth-bluedroid/commit/2ee778598e3b2e3f826e3f6b4eeafbb11005b21b.  If we're lucky, that's all they need to do to restore A2DP to its former glory.  I have no delusions that this will work for every device/receiver, I just think it's a step forward.

Good luck my friend!  I've been cranking A2DP on my GNex build for hours now and it's been phenomenal.  I truly hope your results are the same.

#157 Thank you for your post.  I set up a build environment for 4.2.2-r1 for the Nexus 4 and built an entire AOSP image with the DEFAULT_SBC_BITRATE adjustment just to get to that file.  I pushed it into the path you listed on my Nexus 4, changed the permissions, and now my bluetooth no longer has the distortion at high frequencies.  Sound quality is very much improved.  Is it the best it can be?  Who knows since Google has not released an official fix, but it sounds way better now.  

I have attached the file to this post for anyone else to push to their Nexus 4.  If anyone wants to try it feel free, it should work on any Nexus 4, but I am not guaranteeing that.  If there is a better way to get the file out there, please let me know.

@ #157 & 158:

I pasted each of your files (one at a time, obviously) to where they should go, verified correct permissions, and definitely noticed a change.  However, I get a 'popping' sound during playback (like popcorn).  The audio also seems slowed down for some reason.  I'm still messing with it, so I'll report back if I can fix it.

However, I am on an ATT GS3, not a nexus, so that's likely why....

I'm running an AOKP ROM (based on AOSP).

Re #159: I looked and AOKP changed the Bluetooth code to use 48Khz as their default sampling rate rather than 44.1KHz, that's causing it to sound slow when you replace the bluetooth library file.  You would need to get an unmodified A2DP audio HAL library (/system/lib/hw/audio.a2dp.default.so) to match it, or wait until somebody has a bluetooth.default.so file with the same 48KHz sampling rate set.

It sounds like this is a generally positive change, I'm sure it won't be long at all before it becomes available for various ROMs.

#158 I just tried your file into my N4, running lastest Paranoid ROM. The sound quality is better, but the 'popping' it's still there.

#158
To clarify: do we need to rebuild the ROM or is it okay if we just replace the file (bluetooth.default.so) and set the correct permissions?

Thanks heaps to everyone working on this!

#161, #159, #160, #161.  I built it from AOSP using the full_mako lunch target (profile), so I suspect this would work best running on a stock or AOSP Nexus 4 (I am running stock, not AOSP).  I'm not sure what, if any, differences Paranoid ROM or AOKP would have to cause the popping. I'm posting the audio.a2dp.default.so file that I ended up building with bluetooth file, but if this does not help, then I suspect #160 is right.  The bluetooth file would need to be built with that sampling rate in mind, or just make a similar bitrate adjustment in the Paranoid and AOKP sources.

#162, if you're running AOSP or stock N4, it should be enough to just replace the file and set the permissions.  That is what I did.

Side Note: if AOKP or CM10.1 are using 48khz as the default sampling rate, I would definitely ask to see if they would switch it to 44.1khz from now on.  Most music is in 44.1khz and resampling to 48khz would degrade sound quality unless a high quality resampler was used (I highly doubt it is).  I have found that resampling removes some of the power and impact from snare drum hits and shrinks the stereo image a bit.  That's my experience at least on other devices.

@ #160 I swapped in your bluetooth.default.so and it sounds great. Thank you! I had been trying to find how to modify the bitpool settings everywhere, but nobody was diving deep enough to modify the .so files. I don't have that knowledge myself, so I'm glad you were able to find it. I can't understand why Google would put a lower-than-maximum value as the default.

I haven't listened enough to be able to notice a speed difference due to the sampling rate, but it the high-end distortion is completely gone.

@ #162 Replacing the file worked fine for me.

@yuxu
Thanks for your effort, your files work like a charm on my Samsung SII (AOKP 4.2.2)!
CPU usage is also in line with what it used to be on my previous ROM (ICS), and as a far as my non-musician ears can tell, there's no degradation in sound quality.

@Thread
The change seems to be pretty device-independent, so give the files in @158 and @163 a try.

Alright AOKP Users:

I have created a zip file with instructions to revert the 48khz based .so audio files back to 44.1khz so the posted bluetooth.default.so files will work properly with no popping and no slowing down of the audio.  However, THERE ARE ISSUES.

I have had the A2DP audio get really distorted after a few minutes of playback.  This may be related to CPU settings, though I'm not sure yet.  

Also, turning off bluetooth has locked up my phone.  Just hold the power button and restart.  Not sure why it's ocurring....

This is a really dirty way of fixing it because I'm not terribly familiar with android yet.  The original issue of distortion is gone though.  I'll post back if I can fix the issues I presented that are associated with this change.

The ZIP file is posted, please read the instructions!

FYI, I'm running Task650's i747 (ATT GS3) ROM.  

[Comment deleted]

To add to my above post..

To fix the issue of the distorted audio, increase the buffer size on your music playback application.  I also increased my minimum CPU freq, but I think the increase in buffer size fixed it.

It may also help to increase the priority of the audio stream.

I user PowerAmp, and I set the buffer size to "Huge (+750ms)".  I haven't had any distortion since that change.

To yet again add to my above post:

I spoke to soon.  I'm still getting distortion after a few minutes of playback.  Pausing for at least 5 seconds and playing again temporarily fixes it.  It seems like a buffer issue, but I can't increase the buffer past 750ms in power amp.

It isn't app specific either.  WinAmp does the same.  I think it has to do with the higher bitrate implemented by the change to the bluetooth file in the first place.

[Comment deleted]