Related
Phone will connect but when making a call it acts as if it hung up, doesn't ring, but then eventually connects to the call. Also, it seems that it freezes. Didn't have this issue on 5.1.1
I have a few questions and thoughts about this.
1. I assume it is an issue with Honda's iMid. I've had issues with bluetooth and my phones since I got the civic.
2. If I buy an aftermarket headunit the problem should go away, right?
3. Is it possible for me to take the bluetooth files from 5.1.1 and put them into 6.0, and will this fix the issue?
4. Has anyone else had this issue. It's possible that a factory reset could fix it, but I'm doubting it.
Thanks.
Tried using 5.1.1 files and it breaks bluetooth. Any other ideas?
Seems that HD calling/4G Enhanced is what is causing this. There is a delay in the phone connecting to activate HD. When I deactivate HD it rings through my car speakers like normal. Turn it back on and there is a delay in the call. I doubt there is a fix, but I'm curious if this is happening to anyone with aftermarket headunits in their cars.
theycallmerayj said:
Seems that HD calling/4G Enhanced is what is causing this. There is a delay in the phone connecting to activate HD. When I deactivate HD it rings through my car speakers like normal. Turn it back on and there is a delay in the call. I doubt there is a fix, but I'm curious if this is happening to anyone with aftermarket headunits in their cars.
Click to expand...
Click to collapse
I don't have a car with a head unit, and I'm still on 5.1.1, but I have noticed long delays with HD Voice and WiFi calling on, and have had complaints about long delays for my phone to start ringing when people call me. I have turned off HD Voice for now to see if it helps me, and good luck to you!
Never ran into this on LP and yet have to on MM.
I use a Kinovo BTC450 kit in my GTI.
I have the exact same problem on my Mazda after updating to 6.0 (worked fine on the 3 previews). How do you disable HD calling?
shadowxm said:
I have the exact same problem on my Mazda after updating to 6.0 (worked fine on the 3 previews). How do you disable HD calling?
Click to expand...
Click to collapse
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
theycallmerayj said:
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
Click to expand...
Click to collapse
My BT is not working in my Pioneer head unit with 6.0. I don't have enhanced 4G LTE in my settings, so it may be an issue with the kernel
byrdcfmma said:
My BT is not working in my Pioneer head unit with 6.0. I don't have enhanced 4G LTE in my settings, so it may be an issue with the kernel
Click to expand...
Click to collapse
Are you having the same issue I'm having or just straight up doesn't work? I'm using the stock rooted kernel that I got from xda. I'm going to try hellscore to see if maybe that makes a difference.
theycallmerayj said:
Settings, wireless and network, more, Cellular networks, uncheck enhanced 4G LTE. The only issue I have with this is that I want simultaneous voice and data. As far as I know, HD Voice/Sim. Data are backed into the same option so turning this off will fix the issue, but you won't have simultaneous data over LTE.
Click to expand...
Click to collapse
Thanks but I don't see that option on Cellular Network Settings, so I guess the issue must be something else, or maybe I just can't turn that off
theycallmerayj said:
Are you having the same issue I'm having or just straight up doesn't work? I'm using the stock rooted kernel that I got from xda. I'm going to try hellscore to see if maybe that makes a difference.
Click to expand...
Click to collapse
It connects, but no sound. Not the same issue as you exactly. I also don't have the option of turning off the HD calling ii nn settings.
shadowxm said:
Thanks but I don't see that option on Cellular Network Settings, so I guess the issue must be something else, or maybe I just can't turn that off
Click to expand...
Click to collapse
http://www.droid-life.com/2015/03/1...e-and-data-now-works-on-nexus-6-with-verizon/
Read down through it. You may have to turn it on in the deeper phone settings.
"In order to enable the setting on your phone, head into the dialer and type in *#*#4636#*#*. When you hit that last *, your phone will jump into the hidden settings menu. Choose “Phone info” and then scroll down until you see an option for “TURN ON VOLTE PROVISIONED FLAG.” Tap that and then reboot your phone (I had to reboot twice for some reason to get it to work). "
theycallmerayj said:
Phone will connect but when making a call it acts as if it hung up, doesn't ring, but then eventually connects to the call. Also, it seems that it freezes. Didn't have this issue on 5.1.1
I have a few questions and thoughts about this.
1. I assume it is an issue with Honda's iMid. I've had issues with bluetooth and my phones since I got the civic.
2. If I buy an aftermarket headunit the problem should go away, right?
3. Is it possible for me to take the bluetooth files from 5.1.1 and put them into 6.0, and will this fix the issue?
4. Has anyone else had this issue. It's possible that a factory reset could fix it, but I'm doubting it.
Thanks.
Click to expand...
Click to collapse
This is the exact same issue I am having with 6.0 on my Acura. I did not have the issue on 5.1.1. The issue on 5.1.1 was constant connect/disconnect if WiFi was active.
artiemon said:
This is the exact same issue I am having with 6.0 on my Acura. I did not have the issue on 5.1.1. The issue on 5.1.1 was constant connect/disconnect if WiFi was active.
Click to expand...
Click to collapse
Out of curiosity, does your Acura have the imid? Apparently Honda doesn't update the old models to play nice with Android. I think the 2015+ has adjustments to make it work correctly.
theycallmerayj said:
Out of curiosity, does your Acura have the imid? Apparently Honda doesn't update the old models to play nice with Android. I think the 2015+ has adjustments to make it work correctly.
Click to expand...
Click to collapse
I am not familiar with imid. My Acura is a 2015 & I am using the factory phone interface.
artiemon said:
I am not familiar with imid. My Acura is a 2015 & I am using the factory phone interface.
Click to expand...
Click to collapse
Oh okay, its the software/interface for the audio of civics. I've had issues with it before with certain Android phones. I want to get a touch screen head unit, but not going to rush into it if it won't fix the issue anyway.
byrdcfmma said:
It connects, but no sound. Not the same issue as you exactly. I also don't have the option of turning off the HD calling ii nn settings.
Click to expand...
Click to collapse
Same here. It connects, but no sound, no option to "turn off HD". Phone is nexus 5, originally bought from google, on tmobile
network. Car is 2014 Honda CRV, factory unit. Never had any problem with this phone or any other phone with this car.
Very annoying.
Glad I found this thread. Since clean flashing from 5.1.1 to 6.0, I've had the same issues with my 2013 Cadillac ATS: when I make a call, the call goes through but there is no sound through Bluetooth. It seems like the person on the other end cannot hear me and I cannot hear them. Same problem receiving calls with Bluetooth connected. I have to manually change the output from Bluetooth to headset/speaker and then the call resumes fine...so there's definitely no problem with the call connecting.
I did notice that one issue has been FIXED: when I control my Bluetooth audio (play, pause, ff, rw), my screen no longer turns on. This was very annoying but certainly not as bad as the new bug!
On a side note, a week or two ago I began having significant battery drain from "Bluetooth Share" even when no devices were connected. I can no longer leave Bluetooth on all day like I used to. I made a post about it here:
http://forum.xda-developers.com/nexus-6/help/bluetooth-share-draining-battery-wipe-t3224863
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Add me to the list of people whose Bluetooth connectivity has suffered after upgrading from Lollipop to Marshmallow (on my Nexus 5). All was working perfectly in my 2015 Honda Accord, connecting to their HandsFreeLink software to make and receive calls. Now calls do go out, but you cannot hear the phone "ringing", and the radio comes back on again until the call is completed, when you suddenly hear the caller say "hello." Also many instances of poor call connection (unusable screeching sounds or very garbled speech). Did everything except reset to factory settings: wiped cache, reset the phone to the car's bluetooth, etc. Waiting hopefully for the 6.0.1 update to save the day….
Click to expand...
Click to collapse
Is anyone else experiencing this? How can I fix?
Me too
I have the same exact problem with my kia.
It is really annoying, can anyone help?
arsenik13 said:
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Is anyone else experiencing this? How can I fix?
Click to expand...
Click to collapse
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
poncespr said:
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
Click to expand...
Click to collapse
This must be a very widespread issue, I wonder why it's not getting any coverage here?
arsenik13 said:
This must be a very widespread issue, I wonder why it's not getting any coverage here?
Click to expand...
Click to collapse
OK. I finally got it working right.
I will tell you what I did in case you want to try it, if you are comfortable flashing a CM13 alpha.
While on 5.1.1 lmy48y, I flashed CM13 Alpha cm-13.0-20151124-UNOFFICIAL found here.
And gapps found here.
I kept the 5.1.1 bootloader and radio, and have not had any issues.
I am using Elemental kernel 3.06.
And I also formatted my device to remove encryption.
So far so good. No more weird behavior on my CRV blue-tooth.
I don't think that the kernel makes a difference, but that is what I am using and have not tried with any others after getting this working combination.
Hope this helps.
6.0.1 Stock fixes bluetooth issues.
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
poncespr said:
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
Click to expand...
Click to collapse
I am running stock 6.0.1 and my bluetooth doesn't work. At all. Annoying.
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Am getting 100% bluesleep / msm_serial_ds wakelocks on various ROMs using a pebble watch. This makes using Bluetooth and my watch unusable due to radically reduced battery. Any ideas?
Sent from my Nexus 6 using Tapatalk
Chahk said:
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Click to expand...
Click to collapse
True. I had not noticed the bluetooth volume bug, but it is there.
They finally fixed it in N Preview. Hopefully this rolls out as part of monthly security updates for 6.0.1 as well.
I am on N, and Since Marshmallow, i have not been able to pair in my Acura TL bluetooth. Same issue with N. Every other phone before or after has or is working well with my Acura TL. So I KNOW it's not the Vehicle, and I know it's not the phone. I can pair my Nexus 6 with a bluetooth speaker, a bluetooth headset, a NON factory bluetooth DIN radio, and a Bluetooth NON factory In vehicle hands free (GROM) without any issues. Somehow, there is a slight change that is affecting CERTAIN devices prior to marshmallow, that is present now.
I have read about activating the GPS, and trying to sync the phone to the Acura Bluetooth... this has made NO difference. Bluetooth will eventually timeout.
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.
Hello All,
I am having a strange issue with bluetooth, all of my connected devices are not reconnecting if I came back to range or on/off bluetooth,
Its happening for my CAR Bluetooth and Gear Sport watch. every then and now and I have to do pairing. I am super frustrated with watch need to reset and reinstall everytime.
I also have swift install does it have anything to do with it.
prashant.saraf said:
Hello All,
I am having a strange issue with bluetooth, all of my connected devices are not reconnecting if I came back to range or on/off bluetooth,
Its happening for my CAR Bluetooth and Gear Sport watch. every then and now and I have to do pairing. I am super frustrated with watch need to reset and reinstall everytime.
I also have swift install does it have anything to do with it.
Click to expand...
Click to collapse
Did you force update? also which version are you on? CSB3 or CSAA?
I have CSAA and I don't think it's force update as it's through ATT.
prashant.saraf said:
I have CSAA and I don't think it's force update as it's through ATT.
Click to expand...
Click to collapse
I'm on VZ and I did the firmware.science forced update to CSAA and it would loose my bluetooth devices all the time for no reason. So I went back to 8.1 until VZ does there update. Some told me, that he had the same problem and had to factory reset his phone just to get that issue resolved.
Not sure if this helps. I had a somewhat similar issue and read somewhere that doing a "reset network settings" fixes the issue. I tried it and it seemed to clear up the reconnecting problems I was having.
Let me try network reset. I will post update
prashant.saraf said:
Let me try network reset. I will post update
Click to expand...
Click to collapse
I've already seen multiple folks state that the CSB3 update has solved lots of Bluetooth issues as well as the compass problem, for what it's worth! There's a CSAA to CSB3 update file out there...
Even with the latest update as of May 2022, my new Tab A8 exhibits Wi-Fi stability issues not seen on the old Tab A7.
After leaving a connected tablet to sleep, Wi-Fi for some apps won't work and only a WiFi OFF + WiFi ON reset will restore connectivity.
Anyone else encountered this problem?
Same - it just won't stay on any network for long at all. It won't connect at all to my VirginMedia router saying 'couldn't get ip number'
Doesn't happen to me from what I've seen... Have Xfinity cable internet together with a Netgear router/modem.
Have you guys done all the system updates?
Yup, up to the latest from April. Tested on 2 devices and it's the same. Factory reset doesn't help.
I'm hoping that if not before, at least the Android 12 update will resolve this.
I just updated to Android 11 firmware update from last week - X200XXU1AVG1 - but the issue remains the same
On Build number RP1A.200720.012.X200XXU1AVC1, no updates I'm aware of. When this happens to me and I toggle wifi off and back on, no networks display. If I toggle airplane mode it they will appear again.
II'm in the USA, using an asus blue cave router.
What's everyone else using?
Anyone know what wifi chipset this tablet uses?
Got the update to Build number RP1A.200720.012.X200XXU1AVG1 it still occurs, and I'm also noticing bluetooth connection issues, both are cured by cycling airplane mode on and off.
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
KoMarCek said:
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
Click to expand...
Click to collapse
I reported the issue via Samsung members app with a bunch of screenshots,
SM-X205 is now getting Android 12 but nothing available yet for SM-X200. Will probably take a couple more days
OK now SM-X200 also got the first Android 12 update and the results are... BAD! Still the same issue and I'm quite done with Samsung for now. Unbelievable that they do not test the basic functionality well enough. I expected some WiFi driver updates under the hood but it seems they are oblivious to the fact Tab A8 has issues.
Had the issue one time since the 15th it's not solved but less frequent at least
What I notice now is that the wifi will turn off randomly. If turned back on it reconnects but shortly thereafter bluetooth dies and cycling airplane mode is required