15
Jan
1

While Android 4.2 may have brought a number of enhancements, it also brought its fair share of issues to the platform. Among those, there has been a real problem with Bluetooth – especially when it comes to A2DP streaming audio. Basically, audio lags and cuts out constantly, making a streaming experience far more frustrating than enjoyable.

Good news, though – Google has just confirmed that this issue will be fixed "in the next release," which should be Android 4.2.2. Here's to hoping this fix also has a positive effect on other Bluetooth devices – like game controllers and the like (most of which simply don't work on 4.2).

image

Naturally, there's still no word on when this update could hit the scene, but I'm going with "the sooner, the better" as my mantra.

[Android Bug Tracker via Joaquín Fernández Carvajal]

Cameron Summerson
Cameron is a self-made geek, Android enthusiast, horror movie fanatic, and musician. When he's not pounding keys here at AP, you can find him spending time with his wife and kids, plucking away on the 6- or 7-string, or watching The Texas Chainsaw Massacre on repeat.

  • soylent

    the kernel battery drain on the N4 would be a lot more important than some Bluetooth fixes...

    • http://twitter.com/yokuyuki Ed Chen

      Use a custom kernel. At least you can't fix the Bluetooth issues with a new kernel.

      • soylent

        I never had any Bluetooth issues so far, but my phone running out of juice after a few hours in standby is a big one. Franco kernel had it fixed, but then he ran into quite some trouble with data drops and so on, he has now reverted all hsic wakelock fixes. faux123 seems to help a bit, but not entirely.

        • Patrik

          Is battery life better in CM?

        • http://twitter.com/yokuyuki Ed Chen

          He didn't revert all of them.

    • Michael Panzer

      For a Nexus 7 owner this is very important to me. But you are right. My nexus 4 needs some bug fixes.

    • QwietStorm

      I have no idea why you got the disagrees, but that kernel fix is said to be in 4.2.2.

      • soylent

        source?

    • deltatux

      Time to flash custom kernels? From reading the Franco kernel changelog, this has been fixed....

    • dcdttu

      Bluetooth or not, streaming downloaded songs on Spotify for 20 minutes sometimes causes Mediaserver to drain the absolute sh_t out of my phone's battery. This morning it was 20 minutes, 25% of my battery.

  • http://twitter.com/yokuyuki Ed Chen

    I wonder if it also fixes the inability to turn on Bluetooth sometimes.

    • http://www.facebook.com/profile.php?id=898440028 Michael Ruocco

      You took the words right out of my mouth. I have the same issue especially when i shut my Bluetooth off and it never really fully shuts off

      • flight13

        I had that same issue after the update. I did a factory reset and haven't had it since. I also didn't reinstall a couple of those widget apps and now just use the native widget to control Wi-Fi, Bluetooth, etc.

        • http://www.facebook.com/profile.php?id=898440028 Michael Ruocco

          I should point out that I'm having this issue using a Galaxy Nexus purchased through the Play Store

          • flight13

            Mine is a Galaxy Nexus from the Play store as well. I also don't have any issues streaming or voice choppiness since the reset.

          • http://twitter.com/mjmdroid Mawdo

            I have that issue too, and have done more than 15 resets ( moving from custom ROM to stock ) but always having this annoying bug, Galaxy Nexus from Vodafone Spain

  • Scott

    That would explain the voice choppiness when on the phone in my car connected via bluetooth to my headunit.

    • mrribbits

      It's an N7 issue. Are you using your Nexus 7 to make voice calls? If not, then no, this does not explain it.

      • Razormike

        Actually there are reports on XDA of it also effecting the Nexus 4.

  • http://danielbrierton.ie Daniel Brierton

    Saw just "Google Confirms Bluetooth" in Feedly, and really really hoped it was gonna continue with "Low Energy for Next Release". :(

  • Robert Alex Kibler

    For what it's worth, I've never had issues with bluetooth on my Galaxy Nexus or or my Nexus 7.

    • mrribbits

      Are you running stock 4.2.1 on your N7 ? Try streaming music to a bluetooth speaker for 10 minutes, and let us know how that works out for ya. It's an issue specific to the N7 running stock 4.2.1.

      • m faisal

        Well its a google issue bud if u use blustooth constantly youll understand how big is the issue I have note 2 if u receive call while on third party app bluetooth automaically dcs and you have switch back on and off and select device again and again quite frustating its on all android device google doesnt care they just keep on making cheapass stuff and throw out to people

    • http://www.androidpolice.com/ Artem Russakovskii

      I hear it manifests itself while streaming and using Wi-Fi specifically.

  • mgamerz

    It's only on the N7? I've been angered by the 4.2 update prompt on my gnex forever. If it didn't F with my SD card I'd be okay with it... I'll keep my 4.1

    • mrribbits

      The bluetooth streaming issue is just an issue with the N7 running the stock 4.2.1 OS.

      • http://profiles.google.com/tim.glaser Tim Glaser

        Although AOSP doesn't have AVRCP 1.3 or higher, which means that although other AOSP devices can stream bluetooth, none of them send metadata to the player, which is really frustrating.

        • http://twitter.com/Twitteninja Zargh

          Hopefully the new stack will enable that, given they took the trouble to completely replace it and (initially) break some things in the process.

  • elias iseid

    I've had problems streaming to a Bluetooth receiver when holding and moving the phone around, but it works fine when it's not moving.
    It's kinda frustrating, I hope they fix it

  • McLean Riley

    This fix will seriously unclog the threads at XDA. Every single 4.2 thread is covered up with OMG my bluetooth suxorzzz.

  • https://steamcommunity.com/id/m-p-3 m-p{3}

    Kinda wierd, I never experienced this bluetooth issue on my Galaxy Nexus on 4.2.1.
    I often use my A2DP bluetooth headset and a bluetooth speaker at home and never experienced stuttering.

    Oh well, I hope it will fix the problem of those affected.

  • Lucas Nicodemus

    I've experienced this on 4.2 on my Nexus 7 alone - the Nexus 4 doesn't have this issue for me.

  • Stephen

    Here's hoping they fix the NFC not working on Nexus 7, as well as the "low storage space = unusably slow tablet" issue.

    • skeeterfood

      Low storage space = unusably slow tablet was fixed in 4.1.2 I believe. If it gets slow, as you pass 3 GB free, you may need to fill it up completely to get the fix to kick in. Worked for my 16 GB N7.

  • http://profiles.google.com/tim.glaser Tim Glaser

    I hope this also fixes AVRCP 1.3+.

    Why can't my N4 send meta data to my head unit while on stock AOSP? You have to flash CM to get AVRCP working. Huge oversight.

    I have a few friends who switched from iPhone to Android on the N4 and they are really disappointed in this. Makes Android seem sloppy.

    • itlnstln

      This. While CM is a great ROM, I prefer rooted stock, personally (Nexus 4). iOS has had this for ages, it's time to catch up.

  • chilly

    Funny. I had flashed cm10 two days ago on my note 2 and had this problem. It was bugging the hell out of me. Thought it was my S11. Then took it back to touchwiz. No problems at all. Guess samsungs doing something right

    • clayton

      touchwiz is not 4.2. Furthermore, I have a slight suspicion that they would not release 4.2 with these bugfixes in place.

      • clayton

        bugs, not bugfixes*

  • Gustav Gansted

    Has this the reason why I haven't been able to get audio through my Novero Rockaway headphones? I'm running CM 10.1 on a Galaxy S 3

  • Aaron Stevens

    I hope they'll fix more than just Bluetooth. Stock 4.2 has been a terrible release overall, compared to stock 4.1, but franco kernel sorted some of the responsiveness.

    There's still the odd things like notifications flickering when you switch screen on as it attempt to displays new icons such as gmail/calendar events, and the Recent Apps button taking a bit longer than usual to open.

  • http://twitter.com/ToysSamurai Toys Samurai

    That kind of point release bug fixes are unbearable -- if you are not using a Nexus that's directly updated by Google, it could take months before you see the bug fixes. You know they are fixed, but you can't have it.

    • Tyler

      Maybe even years? *Looks at Verizon Nexus*

      • http://twitter.com/ToysSamurai Toys Samurai

        Sadly, that's what I have and I am still waiting for 4.2 ... actually, I am waiting for Bugless Beast 4.2. Gave up on the official update long times ago.

        • Tyler

          I'm still sitting on 4.1.1 stock rom rooted, just havnt gotten around to going back to factory 4.0 factory backup and letting it update then flashing either JellyBelly 12.0 or Xenon HD 2.0 Stable. Any recomendations for what to flash while I backup 15gb of clockworkmod backups?

        • http://www.facebook.com/rob.dallara Rob Dallara

          aokp 4.2 finally came out like a week ago...

    • Matthew Fry

      More likely than not, the phone manufacturer will manually merge the fix into their 4.2.1 release. Google is the only one that can get away with crippling bugs like this for so long.

  • http://twitter.com/mike_freegan Mike

    What about the horrible compression? I really, really hope that gets fixed too.

    • CBMC

      That is the biggest problem with blue tooth on 4.2 and 4.2.1 because it affects every device. The people who don't notice it obviously don't realize it is there. The bit pool is lower which causes distortion especially in higher frequencies. I haven't been able to move to 4.2 on my gnex because of it.

  • http://www.lukeharper.co.uk/ Luke Harper

    Isn't 5.0 coming soon?

    • http://www.facebook.com/lanejasper Lane Jasper

      source? never heard that yet.

    • Tyler

      Pretty sure your wrong, If it is coming it will be shown at Google IO in May. Just from what I've seen with releases during IO (been watching since Android 2.2ish), I think we will see a sneak peak of 5.0 if its coming and 4.3 will be released. If 5.0 is truly coming we wont see it till the end of the year at earliest. These are my predictions take them with a grain of salt.

  • http://www.facebook.com/lanejasper Lane Jasper

    All good and well but my note II on ATT only has 4.1.2 so no worries, works great. I'd love to run 4.2 though. anyone know of a compatible 4.2 ROM for ATT Note II? I haven't found one except a pre-release of CM 10 but it has phone audio issues thus far....TIA!

  • http://twitter.com/sam1am John Samuel αΩ

    Hooray I can finally get bluetooth working in a year when I buy a new phone with this OS on it!

    • Declan MacInnis

      Use a custom ROM. I have no sympathy for people who complain about this kind of stuff. There's no excuse not to. If you say "I don't want to void my warranty", just unroot it if you need to use your warranty.

      • Danny Holyoake

        Are you seriously suggesting that people buying phones are expected to know how to hack their phones in order to revert to a less stable version of the operating system and get updates *that fix bluetooth-breaking bugs*? If you think that's how it should be, then Android is a fucking awful platform.

        • http://www.facebook.com/jayzi44 Jonathan Zambrano

          You can always NOT use Android... weird how people complain about products they do NOT HAVE to use. The flexibility that Android allows it's users unfortunately can also come with hiccups. Bluetooth is broke in 4.2.1 period, custom ROMS will not fix that unless it is based on 4.1 or if they get a hold of 4.2.2. If you hate the platform then leave the platform!

      • Paul

        Its not fixed in any custom rom. I've tried many different ones and the problem is always there. Its very intermittent, so its easy to think you've fixed it when you have not.
        And suggesting that someone "just use a custom rom" is bogus. Do you think the average n7 user has any clue how to use a custom rom? Really?

      • http://twitter.com/sam1am John Samuel αΩ

        Hey jackass - there is no rom with working bluetooth. I have no sympathy for assholes who don't know what the hell they're talking about.

      • http://twitter.com/sam1am John Samuel αΩ

        Ugh, why not just program your own phone OS. I have no sympathy for people who have problems but won't just write their own competitor to Android. UGH!

        • Bruce.0

          What an idiotic response. The whole point t is that Bluetooth is not some cutting edge feature. It's a decade old tech in its fourth iteration which has worked fine in android OS and now it is broken and 3 months later not one of Google's 50,000 employees has released a point fix. Bluetooth is basic functionality listed on the retail box. Telling someone to program their own OS if they don't like a basic feature being broken for this long is just plain adenine.

  • bakashrimp

    AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP AVRCP 1.4+ OR GO TO HELL.

  • http://www.themmteam.com RealtorRyan

    Sooner please! My N4 needs some love...

  • Alternet

    Oh man would I be so happy that they would include AVRCP 1.3+. I just bought a brand new headunit and I would love having stock ROM to display my music on my HU :D

    PLEASE SOMEONE SAY IT WILL HAVE IT!

  • Roland

    I can't get my Google Wallet to work

  • Matthew Fry

    Uh... what about the crippling N10 crash/reboot cycle all the friggin time despite people claiming disabling this or that will fix it. I've got location services unchecked, I've got HD Widgets uninstalled. I've got Chrome and Currents uninstalled. Still happens while browsing, while playing games, while typing.

    edit: I just want them to admit the damn problem, not necessarily have the fix 'rite nao'

  • http://www.facebook.com/people/Jamie-Robinson/1403495182 Jamie Robinson

    I never have problems when playing music that is on my N7, but trying to stream anything, Pandora, NPR, etc....it is HORRIBLE. It constantly stutters, stops, restarts....It is a real pain in the ass. I hope they fix it soon.

  • PeteK

    My Galaxy Nexus has issues connecting with my car. Bluetooth worked without issue before December, and has been VERY inconsistent since.

  • Carlos

    Hi!
    I ave Galaxy Nexus with OTA JB 4.2.1 (JOP40D) and I have Bluetooth audio streaming issue on my Nexus, I don't know where can I post that issue to get it fixed, once I posted somewhere about languages on Nexus but now I don't remember that page name so I can't post information about this issue to Google Developers! :/

    This must be fixed on the next release for Nexus too!

  • ruby

    If this will fix the Bluetooth game controller issue then I will keep my nexus 7, if not it goes back to the store.

  • inno

    My android has crashed , gallery and other appl are not working

  • Joshua Cremeans

    I fixed my problems with bluetooth. I turned off my A2DP and now i can use both wifi and bluetooth at the same time. I have a jawbone era. I do miss the streaming music but it was more important for me to talk and surf using wifi and bluetooth. I think if someone can change the fuequency of the A2DP that would solve the issues.

  • PNITR8R

    I have the Note 2 and that bitch skips like a scratched CD only while streaming Bluetooth

  • Franc012

    Update. Nope, it didn't fix the issue with Jellybean 4.2.2.