Database Users

[Q] Bluetooth woes ,, opinions needed

Have a stock unrooted N4 running the new 4,4,3.
Updated to 4,4,3 solely in the hope it would solve the bluetooth disconnects experienced. Note I did not have 'stuttering' or the like, just solid disconnects which would then auto reconnect in 30-60 sec unfortunately stopping my music app which would then need to be restarted and since I primarily use the BT on my bike or motorcycle it is obviously a pain ....
!!!!!!!!!!!! the update not only has not stopped the disconnects it has now introduced stuttering on occasion (not all the time) ....
Here's where I am at:
1. Live with it until Google finally realizes IT'S A PHONE not a camera or whatever and solves the BT problem or gets the BT folks to do it. (really can't believe they can't solve this or is it just an N4 problem?)
2. Root the phone, install TiBU, backup, wipe and install 4.4.3 factory images, reroot and recover stuff from TiBU ... all this in the hope the BT problem goes away ... chances of this?????
3. Give up and install CM which people say does not have this BT problem ... true??????
Thanks in advance to all for your help and opinions ..........

Could it be
Could it be the BT device itself? Does it work like a charm with other devices?

Electrospaz said:
Could it be the BT device itself? Does it work like a charm with other devices?
Click to expand...
Click to collapse
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4

zdrifter said:
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
Click to expand...
Click to collapse
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..

Electrospaz said:
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Click to expand...
Click to collapse
Yup ... always stock ... when new on whatever version was current then (can't remember) did not have this problem and BT worked fine ........ when they went to the 'low power' BT solution it started.

Was really hoping this update would solve the disconnect problem.

Bluetooth issues for 4.4

I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.

Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?

Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.

BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !

Mine is also a rev11, 303k. I guess that rules out hardware issue

Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.

I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !

paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:

Strange bluetooth problem after upgrading to 6.0

Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.

DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
Click to expand...
Click to collapse
Simple
6.0 Rom bugs.
Wait until they are fixed

They all are based on the same code. So if one roms has it they all have it.
Keep in mind that MM is brand new so you just have to be patient for it to be fixed.

DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect
Thanks.
Click to expand...
Click to collapse
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).

mr.b00tl00p said:
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
Click to expand...
Click to collapse
same here, but now i have new one's like connecting my mi band at all :/

I also had problems with BT with the CM13 Official Nightlies, and also with the Resurrection Remix.
But I now use the JDCTeam 6.0.1 ROM, and I don't have BT issues, I only use my BT in car, but I can send and receive phone calls, and also stream my music via BT.
Furthermore, almost everyone complains about the no sound with the calling issues.
I also had those issues back to the official CM13 and the RR 6.0.1 versions.
For me, this ROM is really good, you would maybe give it a try.
I use an old bootloader, the FNB8, but it seems to work pretty fine.

Any ROM/KERNEL/RADIO/Combo that will guarantee stable WiFi and Bluetooth?

I've been using Nexus 4 for 4 years now and only last year I began to need bluetooth in it for BT Keyboard and a mouse. That's when I discovered problems with this phone.
Using bluetooth and Wifi at the same time was impossible - WiFi would disconnect and I'd have to reconnect it manually each time - so I used a WiFi watchdog-reconnecter app for that, but still it was really annoying and caused few seconds internet outage each minute.
Then few months ago I've started using a smartwatch with smart notifications via bluetooth - and Nexus had problems with pairing and then with keeping the connection with the watch - it would randomly disconnect or I'd have to reboot the phone to try and connect the watch again. Watch automatically scans for the phone and tries to autoconnect to it - but Nexus is so terrible at it. I've tested the watch with other smartphones and none had these issues - all was flawless.
These problems all occured for me on all ROMs I've used with Android 4.4+ and I've tried stocks, EuphoriaOS, Chroma, PureNexus and now DirtyUnicorns. If I remember well, I had better bluetooth times with Chroma, but that I'll have to test again to make sure.
So guys here are my questions:
1. Do you know if Nexus 4 WiFi/Bluetooth problems were ever finally solved with a patch?
2. If you can relate your position to mine (using a smartwatch or something else that needs to reconnect to the phone automatically) then do you have these problems? If not, which ROM are you using and which kernel?
3. I've read that kernels don't matter in bluetooth and that it's mostly ROM based issue? Is that true, or maybe a specific kernel helps for these problems?

I'm using bluetooth to play music.
In the past I've had issues with audio cutting out over bluetooth on the official firmware. At some point it got fixed but I cannot remember when exactly.
Right now I am using PureNexus 6.0.1-20160311 and the audio problems came back.
That's all I can say but I did have a reliable ROM in the past.
Edit : I just installed the latest CM13 snapshot (2016-04-29) with Hellspawn r12 and Bluetooth audio stopped skipping.

I'm on the Resurrection Remix ROM, with no problems but I only use Bluetooth for the occasional file transfer.

Android q beta 5 no wifi and bluetooth

Hello i've downloaded the new beta 5 of Android q. Since this update whenever i'm connected with wifi it tells me no internet connexion i have to be connected through lte. Bluetooth doesn't work aswell whenever i try to listen to music with my earphone the bluetooth crash.

No issues with Beta 5 on mine. You might want to nuke and pave and see if it fixes it.
Stock phone.

SirDigitalKnight said:
No issues with Beta 5 on mine. You might want to nuke and pave and see if it fixes it.
Stock phone.
Click to expand...
Click to collapse
The wifi issue was actually with my router so it's ok but thé bluetooth is a problem. I saw a Reddit post about it i'm not the only one with this issue. The bluetooth earphone only works when aptx is disabled.

Disable aptx and try

trash for me.
weird QR code on first boot
bluetooth app crashes every 10 seconds
no wifi at all

kevp75 said:
trash for me.
weird QR code on first boot
bluetooth app crashes every 10 seconds
no wifi at all
Click to expand...
Click to collapse
Fastboot flashed the last PIE, then did the adb sideload of Q 5
Everything now works fine

Tested Bluetooth audio with q5 and it works with my pioneer head unit, my HD JBL headphones and my MC Helmet Bluetooth.

How's the battery compare to Pie? is it the same or better?

chanh2018 said:
How's the battery compare to Pie? is it the same or better?
Click to expand...
Click to collapse
so far? seems a tad better.. but i also atsrted wothout 100% and flashed elementalx once done... ill know mire for sure tomorrow