Related
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!
Hi there
I bought a Moto X 2014 last week, and I have the stock, unrooted 5.1 update (23.16.1).
Today, I had an issue where the phone was not automatically connecting to my car's bluetooth stereo. Tried manually reconnecting to the Moto X through the car's system but it kept saying "unable to connect". I decided to switch the bluetooth on the phone off and back on again - it switched off OK, but when trying to switch it back on, it would move to the "on" position for a second or two and then go back to "off". Tried it a few times but the only thing that got it working again was a reboot.
Just wondering if this is likely to be a one off or a common issue on the handset? I have read about people having issues with skipping audio but this was just bluetooth not working at all.
Thanks
James
I've run into this on my Moto X and my wife has seen it on her Nexus 5. It just seems to happen if you keep Bluetooth on for a long time and then toggle it. I've found that rebooting every few days avoids a number of issues in Android in general.
raptir said:
I've run into this on my Moto X and my wife has seen it on her Nexus 5. It just seems to happen if you keep Bluetooth on for a long time and then toggle it. I've found that rebooting every few days avoids a number of issues in Android in general.
Click to expand...
Click to collapse
Thanks for the feedback. I've come from a Nexus 5 where I'd not ever had this happen despite leaving Bluetooth on permanently. Perhaps it's an isolated thing so I'll just see how things go for now.
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
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.
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
smo69 said:
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
Click to expand...
Click to collapse
Of those links, only the last one is relevant to the 3T.
What specific Bluetooth devices do you have the problem with?
I've use the phone feature with 3 different headsets, my car head unit, and a BT speaker, all with no issues with calls.
I have a problem with every Bluetooth device that uses phone features. This includes a Gear S3, Car Dongle and ear phones.
I have tried 2 BT SPEAKERS, 2 BT headset,.1 smart band and 1 smartwatch (moto 360).
No issues at all
Unleashed by my rooted OP3T on 8.0
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
smo69 said:
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
Click to expand...
Click to collapse
Any Magisk modules being used? I haven't seen this Bluetooth issue specifically (from Magisk modules) but they can sometimes cause random bugs, and it is a good enough place to start as any.
I think the Samsung gear watches in general, do not play well with a lot of non-Sammy phones. At least from other threads I've seen around. But it is suspicious that you are having the issue on multiple Bluetooth devices (although you don't name the other brands). So I think you are on the right track, that it may be an app or something else peculiar to your device setup.
I've had the phone functions work just fine with Motorola, Plantronics, JBL headsets, JBL speaker, Subaru head unit (Kenwood made stereo, from what I understand).
smo69 said:
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Click to expand...
Click to collapse
I have the exact same issue. I've tried nougat/oreo.....official OOS....different roms also. Clean flashed the 3T but no luck.
Media audio works perfectly fine. As soon as somebody calls and I answer, the line becomes mute to whatever it is connected to. I've tried both with my car and BT speaker.
I then have to route the call to the ear pierce on the phone to be able to continue with the call.
Everyone I have found with this issue have sent their phones back for repairs.
OnePlus 3Ts seem to face an issue where if you're in a voice call using your SIM card, and also connected to some Bluetooth device at the same time, the WiFi seems to just s**t itself. It can't give more than 0.10 Mbps ever. It left me confused for a long time until I figured it was due to me calling on my Bluetooth headset/speaker. Truly annoying imo.
I finally figured it out. As I stated earlier, I was sure it was software based because music worked just fine, so I was looking for a culprit app that might have been hogging the phone audio/mic. Oddly enough, it was the T-Mobile Visual Voicemail app. I went ahead an uninstalled it. That app was not worth being unable to use Bluetooth hands-free in my car.
I take that back. Suddenly, it's not working anymore, so I'm more inclined to believe there's something wrong with the phone speaker/mic suddenly hanging with apps other than the actual phone app. The Visual Voicemail app only exposed that there was an issue with this, but the app itself did not seem to be the problem.
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
DIOmenik said:
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
Click to expand...
Click to collapse
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I am not at any stable version.
And have tried many different bt sets.
Also never had battery problems at Oreo
Sent from my ONEPLUS A3003 using Tapatalk
DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I'm on stable OOS 5.0.6 (and multiple/sequential stable OOS builds before that) and never had issues with BT calls, using a headset and my car stereo.
2020, OnePlus 3T rooted magisk, android Pie, same bluetooth problem.