Database Develop

[Q] Bluetooth and Android OS bugs,am I crazy?

Disclaimer: I've searched the forums day after day and have found nothing that helps me in any way.
Hey guys, I'll get right down to this:
I've got a Moto X VZW MM 32GB, initially shipped with 4.2.2 and running 4.4 as soon as I got it activated.
Everything on the Moto X works great, fluid graphics, fast app opening, battery (for the most part). But I've got a bone to pick with bluetooth, as well as Android OS.
First off, the bluetooth bugs, or what I'd like to call, The Blues.
Problems
- I have Pioneer Premier FH-P800BT, running great for the past 6 months or so. I originally had a Galaxy Nexus from VZW, with CM10.2 on it and bluetooth worked flawlessly, save for an obvious quality issue with phone calls/echo cancellation. A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
- On all bluetooth devices with A2DP, sometimes the quality is great, sometimes it does what I like to call a "stucho" aka a stutter/echo. The best way I can explain it is if you've ever heard a record skip back and keep playing the same part, multiply that by like 100x. Or better example, for you Galaxy Nexus users (other phones too, if they do it) when your phone would freeze from being overloaded, and it ultimately crashed (non responsive to anything, screen won't come on, or maybe stuck on) and the audio get's hung. The sound does that on the Moto X, but it continues playing the track without pausing/skipping. It's extremely annoying, and mostly occurs when surfaceflinger is active (I'd assume that's what it is), as it's when anything animation-wise caused by user input occurs. I've also had the audio deteriorate in the same manner, but after it does the weird stucho effect, the audio slows down a bit, noticeable, like, listening to "We Found Love" by Rihanna sounded like a man singing it, and then it will speed up and go too fast after about a minute, and then resume normal playback. Despite completely pausing on my Galaxy Nexus, that phone never did have the audio issues this Moto X does, and it occurs on every A2DP device I've tried (BMW iDrive, Hyundai Sonata factory radio, Philips SBT series, my Pioneer headunit).
Second issue I'm having: Android OS
- I've tried ART and running Dalvik as the runtime, and on both, after weeks of running them, I notice that throughout the day, 3-4% battery drain per hour, with nothing in recent apps, wifi on, and all VZW software except for backup assistant disabled. I'm not complaining because I tend to make it to the end of the day with 2 1/2 hours SOT and and about 10% left on battery, but I'm curious as to why it's not making it any further. I don't have much installed. Dropbox, Facebook, Exchange account, Wallet, and other programs that don't run in the background (OS Monitor, Dots (game), etc). While my SOT can show 2 1/2 hours, it's only taking like 35% of the battery while Android OS shows like 20% or more, and shows CPU time around 1:45 hrs.
Any insight on either of these issues would be appreciated. I love the phone, everything else is perfect, but these 2 things are kinda irking me because I know this isn't the way the phone should be operating, moreso with the bluetooth bug.

Bump

My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...

Glad to hear that yours is working great, mine usually does. I'll also add that call quality is top notch over bluetooth, much cleaner than on my Gnex. It's just A2DP sometimes will do the above mentioned, and it's so annoying. Using the headphone jack it is fine, it's specific to bluetooth.
As for battery tips, I've tried a good portion, short of rooting the device and greenifying it. I ran my Gnex forever, and I kid you not, swapped/flashed at least 60 roms, so I know what I'm doing in terms of de-bloat and rooting and such, but if not for these bugs, I'd be happy with the phone itself.
Thanks for the tips though I'll look, but in the mean time, anybody else ever noticed what I'm talking about?
kj2112 said:
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse

I don't have stutter/echo problems but after taking a call on it and trying to go back to music the app acts like it is playing but no music is heard. I have to cycle BT on/off or cycle the power on the adapter. This is on a car adapter, the Kinivo BTC450. The adapter was flawless with an iPhone 5s and pretty good with a nexus 5. I am hoping it is 4.4 bugs and 4.4.2 will clear it up. It is supposed to launch Feb. 1 in Europe with 4.4.2 so hopefully we'll all see an update. I'm tinkering with the idea of going back to 4.2.2 to see if it is any better.
Sent from my XT1053 using Tapatalk

Well, I've solved 2 of the 3 problems I was having. Android OS no longer takes over my battery, and thankfully, more people today had posted that Snapchat was a battery hog on 4.4 (or on any OS version for that matter). And I wasn't just hallucinating, considering at 50% battery, SOT was ~ 1 hr while Android OS showed like almost 2 hours of being active, and percentages were like 33-35% for SOT, and 20-25% for Android OS. So I think now that 33mins of SOT at 90% battery and Android OS only showing 5% usage, issue's resolved
Bluetooth stuttering was seemingly with all audio services on my phone, but after I tinkered, I found anything that passed through the built-in EQ was stuttering when surfaceflinger was active. And oddly enough, only with bluetooth, and not even all the time. So in short, disabling the EQ on the phone seems to have fixed the weird jerking/echo/stucho sound period. I'll test a bit further, but so far that seems to be good.
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.

So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk

I can confirm that for the past 2 days, with the Audio Effects/EQ disabled, I have no stutter with audio over bluetooth, it plays much smoother now. Also, uninstalling Snapchat has 100% resolved my Android OS battery drain. I was only getting an hour and a half of SOT with 30% battery left before, and now I successfully hit 50% battery with right at 2 hours SOT, so it's definitely made a huge difference. That's with dropbox, exchange account, facebook, and a few other random apps running. Worth a shot to see if it really does it for you, but YMMV
murso74 said:
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse

balleron24z said:
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
Click to expand...
Click to collapse
Any resolution on this? I have the exact same problem with my Pioneer head unit. So annoying having to repair every time!

Only problem I'm having with Bluetooth in my car is that incoming phone calls break my audio connection. Instead of resuming, the audio ceases and i have to unpair and repair to get my audio back.

balleron24z said:
A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
Click to expand...
Click to collapse
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.

Se7enLC said:
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Click to expand...
Click to collapse
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices. My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.

JoeSchmoe007 said:
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices.
Click to expand...
Click to collapse
It was actually 4.2 where Android switched from BlueZ to BlueDroid. In 4.3 and 4.4 there were significant developments to "finish" that implementation. On my Nexus, 4.2 was worthless, but 4.3 and 4.4 worked great. It's certainly possible that Motorola botched something with their upgrade to 4.4 - or maybe Motorola had their own Bluetooth stack separate from AOSP.
My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
Click to expand...
Click to collapse
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!

Se7enLC said:
...
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Click to expand...
Click to collapse
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Here is another quote from now deleted thread:
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
If you have tested and working instructions on how to downgrade from 4.4.2 to 4.2.2 on 1053 I really would like know them.

JoeSchmoe007 said:
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Click to expand...
Click to collapse
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.

To answer a few questions regarding this:
1: You most certainly CAN flash any ROM you wish to a DE Moto X, you just need to unlock the bootloader. When the BL is unlocked, it allows you to flash whatever you want. Look it up and do your homework, it's essentially a Nexus, without the AOSP out of the box.
2: The if 4.4 had so many bluetooth bugs, then why did my Gnex running AOSP 4.4 (the hacked together one that had driver bugs) work PERFECT, and I mean legit PERFECT with bluetooth on all devices I used? The point is moot with the bluetooth stack being bugged. Obviously Google tested this on MANY of their internal devices before releasing to Nexus devices and the AOSP branch. Y'all have no logic if you believe otherwise. I DO, however, agree that it's possible that Moto is using a non-standard or non-AOSP bluetooth stack, or they have modified the bluetooth config to the point where it doesn't work.
4.4.2 for the Moto X didn't fix my problem, although it supposedly did fix some bluetooth bugs. I can still use the phone with a 2013 Hyundai Sonata Limited's bluetooth, and it pairs perfectly every time. This seems to be a hardware-specific issue, as I see people with older model Pioneer/Kenwood/etc. Bluetooth 2.0 headunits having issues, as well as with some hands-free BT units too. But on newer vehicles, some radios don't have the problem. I'm gonna file another ticket with Moto and see if I can provide proof to the problem.

Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
No moto x is a nexus. There is no downgrading the bootloader without heavy risk. The stories you've read here about downgrading bricks WILL happen to the dev edition just like the other unlocked moto's. Mark my words.... please.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------
Careful who's advice you follow here guys....unless you have money to burn.
And yes...totally agree with the above.....do your homework.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:39 PM ----------
Se7enLC said:
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
Click to expand...
Click to collapse
No. Downgrading is a HUGE brick risk. Trust me.
Moto x's are nothing like a nexus when it comes to the bootloaders.
Dev edition is like the rest....but you keep warranty. That's all!
Sent from my Nexus 5 using Tapatalk

kj2112 said:
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
Click to expand...
Click to collapse
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
Click to expand...
Click to collapse
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
Click to expand...
Click to collapse
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.

Se7enLC said:
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Click to expand...
Click to collapse
I can't speak for what dev edition means on other phones....but for the Moto x, Dev edition means you can unlock bootloader, same as many other models....though your warranty is still good......and once unlocked, its EXACTLY the same as any other unlocked Moto x as far as flashing rules and RISKS.
I don't claim to be an expert on precisely why and what causes a brick, but I've read more than enough on here lately to know that downgrading from 4.4.2 is playing with fire. LOL
Funny....I just went to flash a 4.2.2 rom on my Nexus 7 the other day and got an error about incompatible boot loader (I was on 4.4.2 at the time) and I remembered, crap...that's right! So I flashed the previous bootloader version....then the 4.2.2 rom. Done ...10 minutes and zero issues. LOL. Not sure why Motorola had to make things harder/different.
Sent from my Nexus 5 using Tapatalk

Back to the original topic - I took the upgrade to 4.4.2 last night:
- Disabled things like XPosed
- Re-flashed stock recovery (using fastboot)
- Applied update
- Re-flashed CWM recovery
- Re-applied root and xposed
I didn't do anything else, apart from app upgrades that happened to come in. When I got in my car this morning it immediately automatically connected. Could be a coincidence, or maybe that upgrade fixed the bug.
EDIT: I was in and out of the car probably half a dozen times today, works perfectly now, auto-connected every time!

[Q] No earpiece sound on stock KitKat 4.4.2

I "upgraded" to KitKat through PC Companion and can't get any sound from the earpiece. I tried the service tests and still nothing. I tried installing KitKat again, this time using an ftf on flashtool and wiping everything; still no earpiece sound. I then flashed another rom (Carbon), and the sound is fine there so it shouldn't be a hardware issue. Does anyone know what the cause could be? Better yet, how can it be fixed?
I gave up on KK for now and just went back to stock 4.2.2 where everything works for me... Would it possibly work right if I update OTA to KK?

I also have the same problem...

Hi guys,
Mine is working correctly after 4.4.2. But I installed it with full wipe and flash pre root, not PCC...

ryotaru said:
I "upgraded" to KitKat through PC Companion and can't get any sound from the earpiece. I tried the service tests and still nothing. I tried installing KitKat again, this time using an ftf on flashtool and wiping everything; still no earpiece sound. I then flashed another rom (Carbon), and the sound is fine there so it shouldn't be a hardware issue. Does anyone know what the cause could be? Better yet, how can it be fixed?
I gave up on KK for now and just went back to stock 4.2.2 where everything works for me... Would it possibly work right if I update OTA to KK?
Click to expand...
Click to collapse
Hi, this is an unsolved bug of the latest stock rom updates. I found a solution:
1. go to Settings --> Apps --> all --> sound enhancements ---> clear data and force stop
2. clear data and force stop Walkman or other music app.
3. restart your cell phone.
But this is not a final solution. The sound bug "comes back" after some days. So, if it appears again you have got to do the same steps.
excuse me if i don't speak english well, I just speak spanish.

This application may be of little help you
Sent from my C5502 using XDA Premium HD app

Claudio, I'll give it a shot, thank you for the tip. If that doesn't work, hopefully that app Iana recommended will! :good:

lanahonest said:
This application may be of little help you
Sent from my C5502 using XDA Premium HD app
Click to expand...
Click to collapse
ryotaru said:
Claudio, I'll give it a shot, thank you for the tip. If that doesn't work, hopefully that app Iana recommended will! :good:
Click to expand...
Click to collapse
I installed SoundAbout. This App told me that my cell phone detects earphones and bluetooth device, but I didn't connect anything.
So, I thought there was a bug in smart connect app, and i was right. I cleared its data. Later, smart connect detected a "phantom" earphones.
It's annoying to make everytime the steps that I posted you, or configuring SoundAbout. I think I'll go back to stock 4.2.2 (the better stock rom for me)

ClaudioAndres said:
I installed SoundAbout. This App told me that my cell phone detects earphones and bluetooth device, but I didn't connect anything.
So, I thought there was a bug in smart connect app, and i was right. I cleared its data. Later, smart connect detected a "phantom" earphones.
It's annoying to make everytime the steps that I posted you, or configuring SoundAbout. I think I'll go back to stock 4.2.2 (the better stock rom for me)
Click to expand...
Click to collapse
I do not have any problem with this Soundabout really helped me this time
you can use the pro version...
complete all recommendations with bluetooth voice once...!!!!

The steps Claudio provided only seemed to work for a matter of minutes, but now I have been using the phone problem "free" for over 24 hours with SoundAbout installed. So when will we get a REAL fix from Sony? It seems like it should be an easy fix for them since it's just something in the software detecting a phantom headset connected. Should I just forget about that and buy a pro license for this app. Maybe Sony will reimburse me for it, haha
Thank you both for the input!

Well, my SoundAbout trial ended and the problem is back. I'm wondering if there is something in the android script or whatever that would "fix" this before ponying up for the Pro version of SoundAbout. Sucks to have to pay to fix Sony's problem

ryotaru said:
Well, my SoundAbout trial ended and the problem is back. I'm wondering if there is something in the android script or whatever that would "fix" this before ponying up for the Pro version of SoundAbout. Sucks to have to pay to fix Sony's problem
Click to expand...
Click to collapse
use blackmart for pro version...!!!
:good:

ryotaru said:
Well, my SoundAbout trial ended and the problem is back. I'm wondering if there is something in the android script or whatever that would "fix" this before ponying up for the Pro version of SoundAbout. Sucks to have to pay to fix Sony's problem
Click to expand...
Click to collapse
have you tried HF button widget?
A friend with an xperia ZR just had this issue also, so i was looking for an alternative to SoundAbout and came across this app.

Thanks for the tip. Right now, I'm frustrated with 4.3 and above, so I went back to 4.2.2. I had another sound problem on KK too; when using my bluetooth headset, if the back of the phone got a little pressure (even from me bending down with the phone in my pants pocket), the bluetooth would disconnect. I would then have to tap or press on the back to get it to reconnect. I was thinking it could be a hardware issue, but I don't have the problem at all on 4.2.2

[Q] Flashed Official 4.4.2 unbranded (C6616) onto C6606...Car Bluetooth issues....

As the title says, I bought a preowned C6606 and immediately flashed 4.4.2 ( I came from a Nexus4 Google Play Edition)
Got everything the way I wanted and went outside to connect and set up BT in my '13 subie stock system. Everything appeared to work fine.
Took a drive later on and BT didnt connect, turned BT on and then off again on the phone and it connected. Started Pandora and the volume was super low. I did check higher quality audio, turned up all the volumes on the phone, to no avail.
So, I accpeted this as a fluke. Parked, got out and later returned and BT wouldnt connect at all this time. Unpaired and reset up BT. Worked fine, left car, later came back and wouldnt pair again........(BTW none of the above gave me the loud volume my N4 produced, it just gave me mediocre levels)
After reading, I see others have had issues with 4.3....I was going to flash back to that, but if there is no fix...then.....
Please. Any and all ideas are greatly appreciated. I live on Pandora in the car, and cannot listen to FM radio for the life of me
Thank you.

Jasonator said:
As the title says, I bought a preowned C6606 and immediately flashed 4.4.2 ( I came from a Nexus4 Google Play Edition)
Got everything the way I wanted and went outside to connect and set up BT in my '13 subie stock system. Everything appeared to work fine.
Took a drive later on and BT didnt connect, turned BT on and then off again on the phone and it connected. Started Pandora and the volume was super low. I did check higher quality audio, turned up all the volumes on the phone, to no avail.
So, I accpeted this as a fluke. Parked, got out and later returned and BT wouldnt connect at all this time. Unpaired and reset up BT. Worked fine, left car, later came back and wouldnt pair again........(BTW none of the above gave me the loud volume my N4 produced, it just gave me mediocre levels)
After reading, I see others have had issues with 4.3....I was going to flash back to that, but if there is no fix...then.....
Please. Any and all ideas are greatly appreciated. I live on Pandora in the car, and cannot listen to FM radio for the life of me
Thank you.
Click to expand...
Click to collapse
Just for clarity sake, did you flash C6616 rom on C6606?

Correct. I flashed stock android 4.4.2 for a C6616 onto my US. T-mobile C6606...... I am not Rooted, nor is the bootloader unlocked. I flashed it 2 times using flashtool....the first time I didn't wipe my data and it was very slow/laggy....after doing it the 2nd time......perfection. Everything else works beautifully. I had 30% battery still by the end of the day. WiFi has 0 issues. I have full LTE and got 50 some odd mbps on speed test. It's just the darned bluetooth in the car. It won't consistently connect and that's a big deal to me.
Thanks.

Jasonator said:
Correct. I flashed stock android 4.4.2 for a C6616 onto my US. T-mobile C6606...... I am not Rooted, nor is the bootloader unlocked. I flashed it 2 times using flashtool....the first time I didn't wipe my data and it was very slow/laggy....after doing it the 2nd time......perfection. Everything else works beautifully. I had 30% battery still by the end of the day. WiFi has 0 issues. I have full LTE and got 50 some odd mbps on speed test. It's just the darned bluetooth in the car. It won't consistently connect and that's a big deal to me.
Thanks.
Click to expand...
Click to collapse
Try flashing your model specific firmware from here and see

That is exactly where I got it from....at the bottom of that article it reads
About the Torrents files:
Also, I would like to notify you that the download link to the torrent is not from me and is provided by Flashtool.net . I have seen the issue with C6606, when you download the file it says it is for C6616. I don’t know if it is really for C6616 or C6606, but as to my knowledge there is not much of difference. I would like to ask you readers from T-mobile from US to make a ftf file for C6606 and upload it to some website and provide the link to me in Comment box. So that it will be useful for others users also. Is there anyone who could help me?
All of that said, what would really help, and I have searched, is a Google Play Edition Firmware for 4.4.2
I dont want to root or unlock the bootloader, so I am not looking for a custom ROM, but the official one that I can flash using Flashtool. If yu can point me int he right direction for that, then I would be a very happy person!

Jasonator said:
That is exactly where I got it from....at the bottom of that article it reads
About the Torrents files:
Also, I would like to notify you that the download link to the torrent is not from me and is provided by Flashtool.net . I have seen the issue with C6606, when you download the file it says it is for C6616. I don’t know if it is really for C6616 or C6606, but as to my knowledge there is not much of difference. I would like to ask you readers from T-mobile from US to make a ftf file for C6606 and upload it to some website and provide the link to me in Comment box. So that it will be useful for others users also. Is there anyone who could help me?
All of that said, what would really help, and I have searched, is a Google Play Edition Firmware for 4.4.2
I dont want to root or unlock the bootloader, so I am not looking for a custom ROM, but the official one that I can flash using Flashtool. If yu can point me int he right direction for that, then I would be a very happy person!
Click to expand...
Click to collapse
the stock firmware for c6606 is still jellybean 4.2.2

I know this....
mymeatb18 said:
the stock firmware for c6606 is still jellybean 4.2.2
Click to expand...
Click to collapse
I am not sure I am being clear..............
I have C6606 Tmobile U.S. Variant.
I flashed Stock ROM for 4.4.2 made for a C6616 Canadian Version. Using Flashtool......
EVERYTHING works perfectly....LTE WIFI Battery etc......
EXCEPT....My bluetooth wont connect automatically in my car.

Right I did the same thing to my wifes phone, c6606 on tmobile. We don't have Bluetooth in our cars so couldn't comment on that.
If something is not working properly its inevitable since you are modifying the phone. There is nothing that u can do but deal with it. It could also be a compatibility issue as well. Some Bluetooth devices are more compatible to certain devices than others.
Sent from my GT-P3110 using Tapatalk

I went the other way around, I have a C661 and flashed a C6603, which I understand is just another variant. Everything works perfect for me. Here's the link for it; http://www.mediafire.com/download/an6lccyaa4lw96i/Stock_Rooted_Deodexed_4.4.2_XZ.zip
It is a pre-rooted if you are interested on that, and I do suffer from the google play services batter drain, I'm waiting on an update.

Jasonator said:
I am not sure I am being clear..............
I have C6606 Tmobile U.S. Variant.
I flashed Stock ROM for 4.4.2 made for a C6616 Canadian Version. Using Flashtool......
EVERYTHING works perfectly....LTE WIFI Battery etc......
EXCEPT....My bluetooth wont connect automatically in my car.
Click to expand...
Click to collapse
I had the same problem but I flashed a generic 4.4.2 C6603 from the UK. It was driving me crazy. Now I have issues where it will connect to my car but the audio won't trasnfer. It dosen't happen often. I didn't have the issue when I tried the generic 4.4.2 C6603 journalism software. Everything worked perfect then and my connections to the network for normal data and tethering are more responsive than the just released 4.3 T-Mobile software. Now that a root method has been found for KitKat I'll be going back to the jurnalism software. If you are willing to play with the software versions you might find one that works fine.
Maybe it has something to do with the audio software of the car and not the phone itself? Just a thought.

Bluetooth is driving me nuts! Need help please.....

Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-

Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues

So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?

As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.

I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk

@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.

@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.

Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.

I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks

This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.

My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place

You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.

Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post

I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.

I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks

Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.

It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.

@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.

larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.

@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.

Bluetooth media - unknown on Sync

Not sure if this is a nougat issue or a Franco kernel issue, but when using Ford MySync or whatever it's called I show unknown artist unknown song as my display on my car audio screen. This same configuration was working fine on MM with France r10 but once I moved to Nougat it's been unable to give me artist and song info.
I've cleared cache, reinstalled apps, removed and added my car back as an audio source all with no luck in resolving. I have also looked through the Franco thread so I don't think it's related to his stuff. I am also updated to the latest kernel he released, no fix there. Not really anything else special on my device except magisk for root.
Is anyone else having this issue? It's kind of driving me crazy. I almost want to revert to factory and see if that changes anything but don't want to re-root etc.
I have searched this forum and others for a fix but everyone says it's app specific, which mine is not. It won't work in sound cloud, play music, YouTube, or any other media apps it was known working in before the update.

I have the same issue in my Mustang...

Budwise said:
I have the same issue in my Mustang...
Click to expand...
Click to collapse
Are you rooted or using any non stock kernel? If rooted, what method? If kernel which? Thank a for the reply. Its nice to know it's not just me.

Rooted yes. I've tried stock kernel and Franco.

Budwise said:
Rooted yes. I've tried stock kernel and Franco.
Click to expand...
Click to collapse
Took out my wife's 2015 explorer today and it has the same problems. I wonder if 4.10 will fix it? I'm holding off for a while before taking it...

I had the same problems with my car ( VW Passat 2014). I have the Sony Xperia ZX and HTC 10 and no problems with Bluetooth. I am using original rom and Nougat. It seems the is only Oneplus phones.

I've tried 4.10 and also now Lineage and it doesn't fix it on any of them. I'm guessing its firmware related then.

I'm having trouble connecting media on my kia!! Can receive calls but no media! Wtf tried to enable it and didn't work
Sent from my ONEPLUS A3000 using Tapatalk

I believe someone said it's OOS 4.0.3+ so 4.0.2 was fine. I can confirm because I experienced this after updating to 4.0.3.
This bug is actually a pretty big peeve of mine. I'm considering going back to 4.0.2 because of it

7.0 update fixed this for me but when I tired the 7.1.1 update it broke it again and also added a noticialbe lag when using the controls on in my car. I have since reverted back to using the 7.0 software.

Alaris said:
7.0 update fixed this for me but when I tired the 7.1.1 update it broke it again and also added a noticialbe lag when using the controls on in my car. I have since reverted back to using the 7.0 software.
Click to expand...
Click to collapse
So you are saying it does not work with OOS4.1?

PaKii94 said:
So you are saying it does not work with OOS4.1?
Click to expand...
Click to collapse
It does not work on mine, unfortunately. It DID work for a day or two though.

I'm running daily Lineage OS using default kernel (usually Fusion kernel, however not right now since it's not updated for latest source) and working beautifully with my Volvo Sensus Connect, both bluetooth internet connection for car and Bluetooth audio with audio track text working. So probably some Ford mumbo jumbo. ?