Database Develop

Confused with Lollipop builds! Please help me select..

Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.

Bump..

abhi.eternal said:
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Click to expand...
Click to collapse
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.

@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.

Tripple-c said:
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
Click to expand...
Click to collapse
That issue you discribed above would only happen if you did a dirty install and didn't install gapps. The newer version backs up gapps so you only have to install. I recommend a clean install(factory reset and format system) to get the camera to detect the only way and then reinstall with gapps use the newest nightly.

abhi.eternal said:
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Click to expand...
Click to collapse
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.

pekcle said:
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
Click to expand...
Click to collapse
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated

abhi.eternal said:
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
Click to expand...
Click to collapse
It's all cool. There's no harm in that. But Android 4.1 to 4.4 was fairly mild and incremental. Lollipop was a hefty change in concept and usage. I tried it on my N7 2013, and it was just harder to use. Buttons were smaller and closer together, more taps and swipes just to do something, etc. It feels like they compromised ease of use just to adhere to the material design. Seriously made me consider going to an Apple product. No joke!

No notification sound through bluetooth??

Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.

Nurmi_CEO said:
Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.
Click to expand...
Click to collapse
Okay, I just thought I had this problem... here the same, after the latest update to 5.1.1.
I'm try with 2 bluetooth headsets (Plantronics - Jabra) and a full factory reset but no notifications for text messages (sms, chat, whatsapp ect ect ect)
Italian Sony Xperia Z3C (Vodafone) Android 5.1.1 - 23.4.A.1.200

I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!

Nurmi_CEO said:
I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!
Click to expand...
Click to collapse
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232

qmaxmobile said:
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232
Click to expand...
Click to collapse
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.

Nurmi_CEO said:
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.
Click to expand...
Click to collapse
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't

qmaxmobile said:
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't
Click to expand...
Click to collapse
Well I decided to flash a 4.4.4 ROM because the battery life is supposedly better (althought my 5.1.1 had great battery life, almost 7 hr SOT). However same thing, no notification through bluetooth.
qmaxmobile, what rom were you running on 5.0.2 to have notifications play through through bluetooth? I only found one 5.0.2 rom and I couldn't get it to boot, and seems like others in the thread had the same problem.
I really need bluetooth notifications. Seems like a simple app would do the trick, but haven't found much except a thread on a forum saying Xperia phones don't support it.

So I posted on the Sony Xperia forum, and a sony rep confirmed that Sony firmware does not support this feature (why????). I tried high and low to find an app in the play store to get it to work, but no dice.
Supposedly the rep also said that if you get a Sony bluetooth headset you can get the sony app to control that feature. I'm not so sure....
If anyone can confirm a sony bluetooth headset will in fact work with stock xperia firmware, please post!
The only option I was able to think of was to unlock the bootloader and flash a custom rom. I just did that and it worked. My DRM keys are backed up in case I decide to relock. So now I'm running Ressurrection Remix rom. It's a shame, as I didn't mind the Sony interface.

Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!

Nurmi_CEO said:
Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!
Click to expand...
Click to collapse
Well, I don't know about you, but notifications go out when using Bluetooth for me on the latest Sony stock room.
You may try the apps SoundAbout, or Mono Bluetooth Router, though.

That's so weird. No idea how it works for you. I found a few threads on other forums complaining about the same thing. I even posted on the Sony forum and support said I need a Sony app and a Sony headset because this "feature" isn't supported.
I did monkey with SoundAbout, no luck. There are so many options, and I didn't see a specific one for this feature.

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.

zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.

Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!

aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.

anyone ever come across a fix for this?

nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)

Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

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.

Oreo for AT&T out now!

It's about time

What's the build number? did you receive any update, share the screenshot

Got it

Download link????
---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------
simonb255 said:
Got it
Click to expand...
Click to collapse
Is this for Moto Z2 or Moto Z2 Force?

Moto z2 force

You should be able to get the ota soon. They are probably rolling it out

It looks like AT&T has formally announced the upgrade. https://thematridox.com/2018/02/23/moto-z2-force-on-att-getting-android-8-0-oreo-upgrade/

I just got the update and phone is now using Android 8.0.

works well
Update was smooth, no wi-fi issues, and fast boot time! Very pleased thus far. AT&T...about time!! Now, when will we get 8.1? Just saying...

Any way to receive the update overseas? Thanks!

Ever since the update, my bluetooth has been incredibly unstable/buggy, anyone else experiencing this or know what I should do?

MaddSpazz said:
Ever since the update, my bluetooth has been incredibly unstable/buggy, anyone else experiencing this or know what I should do?
Click to expand...
Click to collapse
Same here with BT issue. My car is now taking long time to connect to my phone. Sometimes, it does not connect at all. Before update to 8.0, connection with car was fast and worked all the times.
I submitted a question to AT&t forum about this issue, no response. I came across posts in Google forum, releases 8.1 will fix BT issue. So, just live with it .... until 8.1 update.

Must be AT&T only. Been running pure stock Sprint for reference on my kernel builds for the week and haven't run into that issue.

What is the download link?
Someone uploading the download link of android 8 par z2 force at & t to install manually

lcc014 said:
Same here with BT issue. My car is now taking long time to connect to my phone. Sometimes, it does not connect at all. Before update to 8.0, connection with car was fast and worked all the times.
I submitted a question to AT&t forum about this issue, no response. I came across posts in Google forum, releases 8.1 will fix BT issue. So, just live with it .... until 8.1 update.
Click to expand...
Click to collapse
Did you factory reset after update? I just got my force last week and sat through all the updates until I got to Oreo and promptly did a factory reset. No bluetooth problems to speak. Actually it works MUCH better than my Moto X Pure that it replaced.
FYI my car has two BT connections, one for phone and one for media. It connects to both quicker than the MXP connected to even one so I'm happy with the BT performance.

anyway to get this for those of us not on AT&T? download and toss on the phone ?
Thanks

please someone to upload the ROM stock 8.0 to update manually from

​
7bolt said:
Did you factory reset after update? I just got my force last week and sat through all the updates until I got to Oreo and promptly did a factory reset. No bluetooth problems to speak. Actually it works MUCH better than my Moto X Pure that it replaced.
FYI my car has two BT connections, one for phone and one for media. It connects to both quicker than the MXP connected to even one so I'm happy with the BT performance.
Click to expand...
Click to collapse
Just tried your suggestion this morning. I will report back later.
Thanks.