Bluez for Nexus 6? - Nexus 6 General

In my quest to resolve my Bluetooth issues (mainly interference issues between my moto 360 which is BT le and my car not being able to connect when the watch is on and in range). I've found many people complaining that many bluetooth issues popped up after Google switched to using BlueDroid for the Bluetooth stack around android 4.4. I came across this project https://code.google.com/p/aosp-bluez/https://code.google.com/p/aosp-bluez/ which attempts to build Bluez (the previous default Bluetooth stack) back in to android 4.4 & 5.0 (and above possibly).
Any ROM devs care to chime in on whether they'd be willing to try this in their build? I'm not against trying to build it myself but it sounds as though I'll need some drivers that may or may not be available for the N6 as it is for the N5. Any help, advice or a point in the right direction would be greatly appreciated. Thanks!
Sent from my Nexus 6 using XDA Free mobile app

bump

Related

Bluetooth A2DP issues w/ 2.1

So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.

Bluetooth not showing track info

This is driving me mad. Installed a new car stereo to get Bluetooth up and running (Pioneer AVH-2400bt, 2012 model). The streaming works fine, but the track info simply doesn't display on the head unit. My wifes older Android phone displays this info, but the N4 doesn't.
I have heard CM10.1 has a fix so I flashed it a few nights ago...still nothing.
I am assuming this is an 4.2.1 issue...but does anyone else have the same issue. Does anyone have a fix?
Just an update: So far none of the 4.2.1 ROMS offered any improvements (not their fault...google just decided not to include this in jellybean).
I was hoping the 4.2.2 update would bring fixes. Once again complete disappointment. Google still hasn't managed to get track info up and running.
So the "bluetooth fixes" in 4.2.2 don't include any track data info sent via bluetooth. Frustrating.
y0bailey said:
Just an update: So far none of the 4.2.1 ROMS offered any improvements (not their fault...google just decided not to include this in jellybean).
I was hoping the 4.2.2 update would bring fixes. Once again complete disappointment. Google still hasn't managed to get track info up and running.
So the "bluetooth fixes" in 4.2.2 don't include any track data info sent via bluetooth. Frustrating.
Click to expand...
Click to collapse
y0bailey, i feel your pain. someone in my pioneer stereo thread (http://forum.xda-developers.com/showthread.php?t=2115864) said it has something to do with google using some crappy windows bluetooth stack protocol which is apparently pretty crummy and basic.
edit: nevermind, that was the MTP protocol for USB..not bluetooth..that is based on Microsoft on the N4.
check pioneer's website; they updated the firmware for your radio a couple weeks ago..i have the 9400 but i think its the same firmware patch. (nevermind..looks like you got a new firmware update on Jan 10 http://www.pioneer.eu/eur/support/software/AVH-2400BT/page.html#download_310)
i updated mine to the latest and crossed my fingers this would allow our little nexus to display track info on the head unit..but alas..no love.
i'm definitely watching this with interest as well.
edited: i just recieved the 4.2.2 update as well..i'll go check my car radio again in a few minutes just in case the combination of the new pioneer update plus 422 makes a difference.
Weak!
Been awhile dealing with this issue, can't seem to find a fix. Apparently everyone spent all their monies on phones and only a few of us first world problemers have car stereos with bluetooth media streaming
My LCD in my car looks so empty when listening to music now

Who doesn't have Bluetooth issues?

I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Sent from my Nexus 4 using xda app-developers app
I got my N4 in the first batch from play store back in November
I have never had any issue with Bluetooth
Granted I don't use it often (once every couple weeks on average) but each time I have its never failed in any way.
I have used in my car for hands free and also to send pics to my GF's phone and a couple times to transfer files from my laptop
Started out stock and then last few months been on custom ROM's with no change
Day 1 N4 here too - never had bt problems. Pairs with my car, Motorola headset, and Moga Pro just fine. Fiancée's stock unrooted N4 pairs with her car and jawbone speakers fine. Hoping 4.3 brings LE bt support for my fitbit flex, but besides that haven't had to do anything but turn on bt and pair.
What problems are you having? Haven't heard of people really having issues...
Sent from my Nexus 4 using xda premium
To my knowledge from researching the problem myself people claim it's a hardware issue based on some of the responses they get back from google I guess? I knew right away it wasn't just me when someone else I know has a N4 as well and when I use my LG Tone with his while connected via WiFI it pulls a dubstep and drops.
Other than that it's the only issue I have with BT that I can replicate. Hands-free while connected via data works like it should.
No Bluetooth problem here.
pshaww said:
I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Click to expand...
Click to collapse
Stock 4.2.2 doesn't work properly with my car (BMW E61 5-series). Basic phone works, but no contact sync due to bugs in the N4 bluetooth stack. Moved to CM10.1 which contains various fixes for this and it's worked perfectly since then.
Honest truth - if the first device didn't work and the second was the same, why on earth would you assume that this was a hardware problem and keep sending the phone back? Either request a refund, switch ROMs or put up with it!
Oh sure I guess I have heard people mention that... BT and both 2.4ghz and 5ghz wifi coexist just fine on both N4s here. I just wish it could take advantage of my ac router.
Sent from my Nexus 4 using xda premium
No problem here, using it everyday in my car
Tapatalk 4 beta via Nexus⁴
hi!
the problem is there, that's a fact, and i have it too...
https://code.google.com/p/android/issues/detail?id=42255
http://www.youtube.com/watch?v=Ipud-wAAE0E
i wonder why this isn't fixed by google? maybe really a hardware related problem?
Yesterday I had the same problem with bluetooth like this one in the video.
Sent from my Nexus 4 using xda app-developers app
I have no issues with Bluetooth, it syncs with my laptop and headset. Also I have a December nexus.
Sent from my Nexus 4 using xda app-developers app
pshaww said:
I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try matr1x kernel. I also had the same bluetooth problem since the first day. I installed d matr1x kernel v10 and now it's solved. Les changelog.
I have had zero Bluetooth issues. I pair with my pioneer in dash for pandora , Bluetooth Google play music, hands free and so on.
Cm10.1
Faux kernel
Sent from my Nexus 4 using xda app-developers app
No Issues
Bought my N4 a month ago and I have used Bluetooth hands-free headset, transferred files from my old phone and from my netbook without any problems. Haven't tried stereo audio, though.
Got my N4 in the second batch of those available and have no issues pairing with my vehicle. I don't use Bluetooth for anything else, though
Bluetooth generally works, it only screws up from time to time for things like pairing with a new device. It's been more or less this way since JB and generally if you have a regular bluetooth setup of headset, in-car radio etc, it 9/10 works just fine.
Introduce some complications and it does wonk out sometimes. I've had plenty of times where it wouldn't want to pair right to my laptop or desktop after I factory reset my device. Sometimes it just won't get picked up either when BT is on, visible and another device is looking for it.
I believe I remember reading that there was a legit explanation for this regarding drivers and or some security thing but it's been long enough that I don't remember what the details were or where I even read it on XDA. May have even been the GN forums.
I've seen the exact problem indicated by the video on CM 10.1. I just restarted, wiped dalvik and all was well again.
Other than that my BT has been perfect. I use it daily in my car for audio streaming and phone. At home I pair it to my PC for audio streaming and it works perfectly.
Sent from my Nexus 4 using xda app-developers app
I actually haven't run into many issues with Bluetooth. I use it mainly with Jawbones Jambox and it pairs up just fine. I think it may have dropped connection a couple times but less than a handful. I do run into problems when I miss a call from someone though. The audio quits playback though the devices remain paired.
Sent from my Nexus 4 using xda app-developers app
I guess I have issues. I leave BT on all the time and only randomly does it automatically connect when I get in my car. I generally have to go in to the BT settings and click the device to pair with. It identifies the device, but doesn't connect automatically.
On stock 4.2.2, I had issues with BT not connecting at all and it would get stuck in an on/off post ion (it would never fully turn off or turn on when I toggled the switch). I would have to reboot to get it to work. I have yet to see this happen on cm10.1, I just have the automatic connect issue with cm10.1
Sent from my Nexus 4 using xda premium
I usually have no issues pairing and using. But I definitely have these two issues:
1. BT won't turn on at all (like in the video).
2. I notice my phone hot and draining battery. I look at the BT indicator and it is blue indicating a connection but I'm not connected at all. I only use BT in the car and I'm nowhere near my car. Yet the indicator is blue and my phone is hot.
Either is resolved with a quick reboot. I'm not troubled by it but is annoying at times.

Android 4.3 Bluetooth Audio Quality Fix for Nexus 7 Flo

cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Install
random_n said:
cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Click to expand...
Click to collapse
Thanks for this post I am having issues with Audio when listening to Netflix movies. Can I just flash this using TWRP?
comptech81 said:
Thanks for this post I am having issues with Audio when listening to Netflix movies. Can I just flash this using TWRP?
Click to expand...
Click to collapse
Yes, just flash with TWRP. Note that this only affects A2DP Bluetooth audio (ie: wireless headphones and stereo receivers) in situations where it sounds like Internet radio from the year 2001 and won't do a thing for the static noise when using the onboard speakers at low volume.
328K did seem to help with Netflix + BT but it certainly wasnt perfect. Its rather disappointing that such a powerful tablet cant even BT + netflix properly.
Thanks much for sharing.
Aren't any Android Tablets/Phones out there which support BT-MP3/AAC Codec? Maybe those can be ported to Nexus devices?
volwrath said:
328K did seem to help with Netflix + BT but it certainly wasnt perfect. Its rather disappointing that such a powerful tablet cant even BT + netflix properly.
Click to expand...
Click to collapse
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
random_n said:
cbaronne has posted a set of compiled binaries to change the default bitrate of the Bluetooth SBC codec to increase A2DP audio quality on the Nexus 4 over on this thread. It seems that the 2013 Nexus 7 suffers from the same issues, but can also be fixed with the same binaries.
I've very lightly modified itlnstln's update script to work on the Nexus 7 and have tested these files as flashable under TWRP. The binaries in the flo-4.3-BTFix-googledefault.zip file are from the ParanoidAndroid 3.94 ROM (which I would highly recommend) should you experience troubles with your Bluetooth devices.
I would recommend trying the 328kbps version first, and would expect it to provide the best quality in most situations since it matches the sampling rate of most MP3 files. Most Bluetooth stacks for other devices have 328 as the maximum quality. Of course, test with your devices and ears.
For device testing, I've used it to great success with a BlackBerry Music Gateway (still stuck at low volume, but that's an AVRCP volume control issue) and a Philips AEA2000/37 Bluetooth receiver. I also have an eBay/Chinese receiver which identifies itself as DMZmusic where this change causes continuous popping noises from both my Nexus 4 and Nexus 7. That device is perfectly fine when paired with my other devices that stream at full quality with A2DP SBC (BlackBerry Playbook, WP7 phone, and Windows PC using the Toshiba stack), so clearly Google still has some work to do. Until then, hopefully these files prove to be useful.
Click to expand...
Click to collapse
I don't know if this is related to the problem of BT keyboards working properly (interference on the 2.4 Ghz band between WiFi and BT), but if it is, would you know how to fix that problem as well? Only reason I ask is that I was under the impression that BT audio also suffered from the interference issue, and would especially make sense if paired up with netflix streaming (which would be sending data over WiFi simultaneously).
SubMatrix said:
I don't know if this is related to the problem of BT keyboards working properly (interference on the 2.4 Ghz band between WiFi and BT), but if it is, would you know how to fix that problem as well? Only reason I ask is that I was under the impression that BT audio also suffered from the interference issue, and would especially make sense if paired up with netflix streaming (which would be sending data over WiFi simultaneously).
Click to expand...
Click to collapse
I haven't dealt with that issue specifically on the Nexus 7, but I have had nothing but terrible luck with most Bluetooth HID devices for PCs and now just recommend using sets from Logitech or Microsoft with proprietary RF USB dongles. Apple's devices tend to work OK though. As for interference, I have no trouble streaming BT audio while also pulling HD video over my 2.4GHz WLAN, but then again I'm not in a very RF saturated area and also have automatic channel hopping disabled on my WiFi AP. If you're in a highrise or something like that, the only possible solution is going to be to get your WLAN onto 5.8GHz to try and free up some spectrum.
I don't think I've heard of any Android devices that do MP3 or AAC BT audio, but there are quite a few that can do AptX. As far as I know, only the manufacturer ROMs provide the codecs for this (ie: flashing CyanogenMod to an SGSIII will kill AptX), and receiver compatibility is pretty low. It's a shame that there are so many cooks in the Bluetooth kitchen that we end up with this metaphorical beef and Cheetos stew.
gramig said:
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
Click to expand...
Click to collapse
Ill have to try that. Nonetheless there are some bt issues relating to 4.3. I was attempting to watch a youtube via bt headphones and my vz hotspot on my SGS3 and it stuttered along, but when I turned off bluetooth it streamed fine. This is rather aggravating.
tried btfix 328kbps didn't help me i use my sony nfc headphone but doesn't work properly when using Netflix sounds get cut. well anyone mind sharing old version of Netflix apo please
Sent from my GT-I9505 using xda premium
gramig said:
I don't think you can blame the Nexus 7. I reverted to the previous version of the netflix app and the audio is fine. It appears netflix broke something with the latest update.
Click to expand...
Click to collapse
Thanks posting your fix. I just reverted to a previous version of netflix and now I have absolutely no audio issues over bluetooth.
Old neflix can be found here: http://forum.xda-developers.com/showthread.php?t=2305091
:good: Huge thank you to OP. Ever since I got my nexus 4, it always had crappy bluetooth audio playback. For a while I wondered if my speakers in the car were damaged also but I tried your fixed and it worked flawlessly. Crystal clear and rich sound now. This is confirmed working on the latest stock nexus 4 jwr66y
-- Post deleted -- web site didn't load that other people had asked my question. It just did and I see it. Can't find 'delete' option here.
You know, I downloaded a Beats Audio APK and that did the trick. Just google BeatsAudio07.02.zip and the first link will where you can download it. I noticed a big difference on my N7 I use at home and definitely the N7 I have installed in my car. The sound thru my Infinity System sounds like crap. Once I downloaded and flashed this zip, it was a huge improvement. :good:
Just got a netflix update last night (3.0.1 build 1016,) fixes the bt issues I had with it =]
Can't update
Does anyone have the default audio.a2dp.default.so, after applying this fix I can no longer OTA.
SireSalty said:
Does anyone have the default audio.a2dp.default.so, after applying this fix I can no longer OTA.
Click to expand...
Click to collapse
Same here...
Error: Unfortunately, Bluetooth share has stopped
Hi Guys, I'm new to N7 and first thing I wanted to do is to upgrade BT audio q. After causing endless bootloop (X), I had to restore device to factory settings using Nexus Root Toolkit v 1.7.8 and loading Android 4.4.0 - Build: KRT16S. Only after that, I tried again to flash "flo-4.3-BTFix-328kbps-2013-08-18.zip" and everything looked ok until boot when there was a pop up message with an error: "Unfortunately, Bluetooth share has stopped". Same with other zip (345kbps). Any idea where might be the problem?
EDIT: Obviously I was trying to use 4.3 fix for 4.4. build When I realized it, I loaded again 4.3 system, flashed zip and seems to be ok now!
So anyway @random_n, could you please update this fix so it would work for 4.4 as well. It would be greatly appreciated!
Has anyone found a kitkat audio fix yet? I justvtried my BT headphones with my n7, and the sound is ungodly bad compared to my galaxy s3.
Since the tablet gets longer battery life, I'd prefer to use it for my wireless audio instead of the s3.

Wifi and Bluetooth fixed in Kit Kat?

As far as I'm aware there are two major issues with Jellybean:
1. Bluetooth and Wifi won't work side by side.
2. Wifi isn't properly connected when the screen is off. (Notifications lag and some apps say there is no connection and won't perform automatic tasks, such as Titanium Backup uploading to Dropbox or news downloading)
What I want to know is, have these been fixed in 4.4 Kit Kat?
I've been searching in vain for the answer to this. Most news articles seem to be about new features or 'getting the Kit Kat look' and all I really want to know about is basic functionality! If anyone out there knows, I would greatly appreciate an answer.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I don't have any of your issues on 4.3, although I occasionally see reduced wifi speeds when bluetooth is on. Toggling wifi usually clears it up.
Perhaps your issues lie elsewhere other than just jellybean.
Really? It's quite a well documented issue, even logged with Google. I've experienced it on stock, liquid smooth and various iterations of cyanogenmod:
http://forum.xda-developers.com/showthread.php?t=2072930
http://productforums.google.com/forum/m/#!msg/mobile/0GtATb0vzEE/p2yYlD3baRsJ
Sent from my Nexus 4 using XDA Premium 4 mobile app
Really. I use three different bluetooth devices with my N4, one of 2 bluetooth headsets when I am on voip calls over wifi, and occasionally one of those along with a logitech bluetooth receiver connected to an audio system.
No problems, and I've had this stock, unrooted N4 since last November.

Categories

Resources