Database Develop

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

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

Bump

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Wifi turning off when phone idle or sleeping

I've got an annoying problem with my phone where the Wifi turns off when my phone is idle or asleep. This means my WhatsApp for Web disconnects and also my Moto Connect plays up too.
I've got the same problem at home, work and parents house so can't be an issue with all 3 networks. The keep wifi on during sleep option is set to Always before anyone mentions this to me.
Phone is running Lollipop 5.0 in the UK and is NOT rooted.
I noticed it doesn't happen when the phone is charging though.
Any ideas?

Right I've now tried changing the Sleep setting to Never but get the same problem.
Also tried connecting to the router via WPS but no luck.
Router is a Superhub 2. I've ruled out that it's the Superhub as I have a Samsung Galaxy S4 Mini that is running fine without a single drop out.
Definitely something Moto X related.

I've also tried on both the 2.4GHz and 5GHz bands with same results!

Try looking within the WiFi settings on the phone. Mine has this
. Added photo
Sent from my HTC One using XDA Free mobile app

Mine is identical to yours other than the fact that I don't have the wifi optimization option.

Right I've just cleared the cache as instructed by Motorola support.

Still have the same problem even after clearing cache.

Ok I can confirm that the issue goes away when in safe mode.
This is starting to piss me off as I don't have any way of checking if it's an app affecting my wifi disconnections!!!

I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.

Wutang200 said:
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Click to expand...
Click to collapse
It's a known bug of 5.0, and already fixed for 5.1. Source, at the "Bug fixes section".
Great that you found a workarround.
Cheers!
Manuel.

Hey glad to know it's a well known bug. The work around still doesn't work. It still keeps disconnecting all the time! Driving me mad!! If the 5.1 update doesn't fix it for me, I'll need to try and get a refund and go for something else. Shame as I really like the Moto X but I can't live with an issue as stupid as this!

I'm not sure Motorola are aware of this issue at all. See their comment below from one of their support staff I'm speaking to now:
Santhosh: We have not received any reports regarding Wi-FI issue after the Android Lollipop update but please give me a moment I will provide the solution for this issue.

His solution for the issue was to get me to do a factory reset lol. I already did this when I first got updated to Lollipop!!
Going to try doing another one now to see if it actually makes any difference. Then will install a few apps at a time or something.

I am connected to WiFi just about all of time, and I have never experienced this.

Right I've done a factory reset and started completely afresh with none of my data or apps restored. WiFi has been solid; I've not had a single drop out!
I'm going to install just a couple of apps at a time and keep an eye out if the issue comes back until I find the culprit.

Hi
My phone was perfect (until now) with the WIFI since november 2014 even after I upgraded it to 5.0
But today, it suddenly starts with this problem by itself. so I restored it to factory defaults with no luck, I installed a new firmware, and still has the bug.
So, why it shows up until now by itself without any mod, app or update?
Sorry for my English.

Today I upgraded it to 5.1 and the issue persists

I had to back to stock 4.4.4. and now my wifi has been fixed so far, working good without interruption until now.
I hope this has fix the problem from sourse, and I'll wait a few days to upgrade it again.
EDIT: Has been a month since my downgrade to 4.4.4. and my WIFI still rocks.

Just want to say that I'm having the same issue since the update to 5.1. Wifi is set to be always on during sleep, but I regularly wake up my phone only to find it connected to 4G, and switching to wifi a few seconds after waking up.
I'm on a locked bootloader (unrooted of course). I did a full reset after the update...
I'm sorry to say that I've seen more little glitches since 5.1 than anything I noticed on 5.0.
EDIT: another issue I'm having is the stock mail client not syncing saying that there is no network connection. My exchange account (push) works fine however...

Just to say the issue has started for me too since the update to 5.1.
I've done 2 factory resets but no luck trying to fix this very annoying problem.
Motorola have asked me to send my phone in for repair so I'll try that and see what happens.

Nexus 6 Marshmallow Bluetooth not operating correctly

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.

Are major problems solved in the latest firmware? (Restarts, wi-fi & BF dropping...)

Are major problems solved in the latest firmware? (Restarts, wi-fi & BF dropping...)
Hi,
I want to buy XZ1 compact but I am reading this phone is restarting on its own, and has wi-fi and bluetooth problems. Can anybody please say, if those or other "critical" bugs are solved? I searched but it is hard to say for sure...
Basically I am quite depended on the phone and I really want it to be reliable. My current Motorola restarted maybe once in three years, so I am bit nervous about this.
Thanks

I'm on the latest firmware and I don't have any of that.
That said, I was on the November one for the last few months and also never had any of that.
That's the problem with forums like that, you're likely to only see the rare negatives of any device.

No issues for me.. smooth as butter.. great battery life.. LDAC working flawlessly with Sony headphones etc
Just wish I could turn the charging LED off

Also keep in mind if you unlock bootloader and load custom rom you're on your own. I havent gone that route this time and have had literally 0 issues in months

Okay, thank you, it seems it will be fine. I won't do custom rom but yeah root + xposed is a must for me.

I also got dropping WIFI. Really annoying and nothing seems to fix it.

xPandamon said:
I also got dropping WIFI. Really annoying and nothing seems to fix it.
Click to expand...
Click to collapse
Wifi working fine here. Check the settings on your router.

The restarts seem to be fixed. I think it was a regression with the previous one or two versions. The phone was fine, then it went from one or more a day, to none with the latest update. Wifi hasn't improved, but I did not find it that bad to begin with. Once it connects, it stays connected. It's that original connection where it sometimes decides "wifi? I don't have a wifi radio." Bluetooth is still terrible - works fine with a BT speaker, but is nearly useless with a car stereo.

Only 1 problem persists - Smart Lock don't work, it just a blank page. Can be resolved by restarting the device.

Bluetooth Phone Calls Don't Work

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.