So, BLE doesn't work for me at all. 3 devices so far, all of them fails to connect. Am I the only one with this problem, which means my phone is faulty, or this a common problem with this phone?
Well, I can confirm that it's a bug in the firmware, confirmed by Moto Support here.
Man, that sucks. Might have to cancel my order because of that. I use smartwatches and stuff. Motorola isn't exactly known for their expediency when releasing bugfixes.
That said, they released 2 updates within the first few weeks of the G5 Plus' release, so maybe they'll do the same for the G5S Plus.
sensi277 said:
Man, that sucks. Might have to cancel my order because of that. I use smartwatches and stuff. Motorola isn't exactly known for their expediency when releasing bugfixes.
That said, they released 2 updates within the first few weeks of the G5 Plus' release, so maybe they'll do the same for the G5S Plus.
Click to expand...
Click to collapse
I've got a feeling they're waiting and pushing it all with the 8.0 update, instead of fixing it in 7.1.1, and then pushing 8 soon after that.
The_Hamster said:
I've got a feeling they're waiting and pushing it all with the 8.0 update, instead of fixing it in 7.1.1, and then pushing 8 soon after that.
Click to expand...
Click to collapse
That would suck, since the 8.0 update isn't due until December.
I just got my Moto G5S Plus in the mail and it doesn't seem to have any Bluetooth LE issues. US retail model on the NPS26.166-45 firmware.
Can confirm that BLE is working. Got a Mi band 2 yesterday and BLE has been working fine.
BLE works here too. Hooked up Fitbit Charge successfully last night.
Hi guys ... How do you know that BLE is working? I have a garmin fenix with which seems to connect correctly to my G5S plus. But the bluetooth on my phone is really using lots of power (last 12 hours 832 mAh, or like 2,3% of my battery per hour). The question I ask myself is wether it's using a regular BT connection instead of BLE?
On my previous phone (moto x style) didn't seem to consume so much energy for bluetooth (during nights my battery graph was a flat line).
BLE is working with both my ZenWatch 2 and ZenWatch 3 as well for the past week that I've had the phone .
@blondie99: You can tell when BLE is working rather than regular BT if your Garmin is shows it's connected to the phone, but the BT icon doesn't change like it would if you were connected to your car, speaker, wireless headphones, etc.
I know that is an old thread but recently I had a problem with connecting to one of the devices with BLE. Device was visible by the phone but was unable to pair.
Activating GPS helped - device was able to pair
I'm on stock Oreo 8.0
PS:For comparison Wiko Fever with MM connected to the same device without GPS activated
Related
I've had my Nexus 6 since Jan. 1, upgrading from an HTC One M7 GPE running 5.0 Lollipop. I experienced Bluetooth connectivity issues with the HTC One after upgrading to 5.0L from 4.4KK, and I knew they were 5.0 related, so I expected somewhat of the same when getting the N6. My problem is, even after upgrading my N6 to 5.01 and then 5.1, most of my Bluetooth issues still exist. I'm trying to figure out if they are indeed software related, or if maybe I have a defective BT radio. I'm rooted, running stock 5.1 LMY47M, with ElementalX Kernel and Nova Launcher. Here is a list of the issues I'm having with my N6 and Bluetooth:
1. Constant dropped connection to my car's bluetooth. Will connect when car is first powered on, then drops connection after about 20 seconds only to reconnect 30 seconds after that, then drop again within 30 seconds. Sometimes it will connect and stay connected for hours. This issue didn't exist with my HTC One running 4.4KK, but did happen intermittently after upgrading it to 5.0L. This issue also doesn't seem to exist when connecting my wife's N5 running 5.1 LMY47D.
2. Problem #1 also seems to exist when connecting my N6 to my Nvidia Shield Tablet running 5.0L, but not as persistent as with Car BT.
3. When my N6 does connect to my Nvidia Shield Tablet, I can send messages using joaoapps' AutoRemote over Bluetooth from my N6 to my Tablet, but not from my Tablet to my N6. Both phone and tablet are configured correctly. This one has me completely stumped and I've spent hours troubleshooting it before just giving up.
3. Audio stuttering when connected to my BT headphones. Again no issue when using said headphones with HTC One 4.4KK or wife's N5 5.1 LMY47D.
3. Bluetooth seems to turn off randomly. At first I thought it was one of my Tasker profiles, but problem still exists even after uninstalling Tasker.
4. My N6 will not connect to my BT OBDII adapter. N6 pairs with adapter, but adapter does not work with Torque or any other ODBII app. HTC One 4.4KK, wife's N5 5.1 LMY47D, and my Nvidia Shield tablet running 5.0L all connect with no issue.
I have tried every suggestion on threads (Reboot, clear Bluetooth Share cache, clear Bluetooth Share Data, forget all connections and re-pair, Bluetooth Auto Connect app) with no luck. I love my N6, but I've hated these BT issues since day one and I've crossed my fingers with every Lollipop update that they would be resolved, to no avail. I'm wondering if anyone (or everyone) is experiencing similar issues with BT, or is it just my N6, and I should return it for a new one before warranty expires. Thanks.
I only use my N6 Bluetooth with my car (ford sync) and occasionally my home phone. I haven't had any issues. Use it everyday on my commute to and from work.
Since you're experiencing this with multiple devices id assume its you phone too. Maybe contact google for warranty replacement?
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Bluetooth is different on the Nexus 6 for sure.
lords8n said:
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Click to expand...
Click to collapse
I also use Ford Sync system. For years it has been reliable and worked flawlessly. But starting with the Nexus 6, some of the common applications I use when mobile started crashing the bluetooth stack and giving the error, "Bluetooth Sharing as stopped working."
Before the Nexus 6 which is the first device I've owned with Lollipop, this never happened. The developer of the SMS texting app that is the main one affected by this, has tried everything to resolve the issue but he and I are now beginning to believe it is something baked either into the phone or lollipop, but before this device I never had any problems with bluetooth. I even went as far as to replace my HU in the car with the new pioneer that supports Android Auto, but to my chagrin, it still crashes on that head unit whenever the SMS reader trys to log off and switch back the stream to media. And unfortunately Android Auto currently does not support Pandora which is a must have for me. Pandora runs perfect on the new HU as it did on the Ford Sync as well, but the SMS reader causes BT sharing to error on both devices since the Nexus 6 and Lollipop, so there is something going on with the bluetooth stack and unfortunately no one I can find has any information about what has changed. Hoping Android Auto will soon add Pandora, but Pandora has not given any time estimation about when that will happen.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
Funny that you mention that. Previously used my Nexus 6 in the car with no issues. Only thing that changed is that I started pairing with a smartwatch in addition, and now my Nexus 6 crashes a few minutes into using Spotify over bluetooth. Complete automatic reboot.
EDIT: Yep, can definitely confirm the combination of the smartwatch and bluetooth audio device kills my phone. Had no trouble without the smartwatch.
EDIT 2: Turns out Google just sucks at bluetooth. Phone can crash regardless, it's just more likely with the smartwatch.
EDIT 3: RMA'd the phone and the new one works perfectly. Turns out it wasn't the software after all, or maybe the watch update helped.
I don't know if this is the same issue or not, but....
Ever since I got my Nexus 6 I have had bluetooth issues with both my cars. One has a Pioneer headunit (2014 model, not Android Auto), the other is a 2014 Subaru Forester with stock head unit.
In both cases there are days when it works perfectly. Then there are other times when it's a nightmare.
With the Pioneer headunit, bluetooth audio will be playing for a brief period (maybe 30 seconds?) and then something will happen and the headunit will play a repeated beep (bing bing bing bing bing bing) till I turn off bluetooth on the phone, wait a minute or two and reconnect.
With the Forester's headunit, similar situation - i'll be playing audio and it will just drop out. Maybe 60 seconds later it may come back (sometimes). Same applies to telephone calls via the headunit with bluetooth.
The same 'issue' appears with both headunits with one playing a beep when it happens the other dead silence, but both dropping in and out whether it's bluetooth audio or a call.
N6 running latest firmware. Problem has existed since I got it last year. Recently unlocked and rooted, but hasn't made a difference.
I don't know if this is the same as my problem, but it is the closest thread I could find, so I'll post here.
I've had my Nexus 6 about a week. Running 5.1.1, unlocked bootloader and rooted. I've been using a bluetooth headset for phone audio and media audio. It had been working, though I have experienced some audio dropout and stuttering with media audio. I had not been able to determine if that was a bluetooth problem or an app problem, but now I am leaning towards thinking it was a bluetooth problem because of what is now happening.
Today, media audio just stopped playing through my headset. Phone audio is working. I've tried rebooting, I've tried forgetting and re-pairing, I've tried a different headset and I cannot get media audio to play over bluetooth.
I am having the same problem with Nexus6 I have tried two different Plantronics voyager bt headsets and a Motorola Sliver. Motorola said it may be a bluetooth antenna problem
Did a resit on phone and Motorola Bluetooth
I really need bluetooth connectivity so I am stuck
Only other option is either find someone to open up the phone and check the antenna or do it myself maybe replace it myself or look for another phone and use this one as a backup
What would you all suggest?
Thanks
Hi - new here on the site. Thanks in advance for any help and or advice.
I just picked up an NIB unlocked N6 off swappa loaded my sim from my Droid Turbo and everything is going good EXCEPT for the bluetooth. I have the latest Lollipop update and still having issues.
The phone does not sync with any of my bluetooth devices. It's not even "discoverable". I performed some of the troubleshooting methods; clearing cache, factory reset, etc.... and still no luck.
The seller on swappa said it may be because it's on CDMA (Verizon). But that doesn't make sense to me??
Any help would be greatly appreciated!!
@Motivated1,
There is no such thing as a "Verizon" CDMA version. They are all the same. So when you go to Setti ngs/Bluetooth and enable it, it's not visible to other decides, and it doesn't discover other devices?
Thank you for the clarification Cam30era.
Yes, that is correct. I'll turn on the bluetooth toggle and it's not discoverable nor does it discover my BT devices. I tried to pair it with my Bose Colorsound speaker, my Droid Turbo, and some bluetooth headphones...all unsuccessful.
I have had a new Nexus 6 from the Play Store. for 3 days (Activated on Sprint, but I think that is irrelevant.) I am running 5.1.1, build LMY47Z.
My one issue is that the N6 Bluetooth, which I have successfully paired with my 2012 Subaru Forester, does not automatically connect. Also, sometimes it will connect to the car, but only for audio, not for phone functionality.
I usually have to fiddle with it to force a good connection. The easiest method I have found is to toggle Bluetooth on/off on the Nexus. It sometimes takes several attempts.
Thanks boomerbubba for the response.
So, I took it to a friend of mine with a moto watch and a Note 4, the N6 connected with both of them instantly. I went home and tried to pair it with my Bose Color Soundlink and once again was unsuccessful. Since I knew the bluetooth had the capability of working, I just messed around with the speaker, holding down the bluetooth button for several seconds, turning it off and on, toggling my N6 bluetooth, and sure enough it worked!!!
So I tried to pair it up with my Droid Turbo and that worked as well.
So I really don't know what the actual problem was...maybe just a finicky unit. But all is good now!
In my experience with my previous phone (a Galaxy S4), and the same car, the Bluetooth discovery "just worked" automatically. Once I had the initial pairing set up, I never had to do anything but bring the phone into the car and it connected.
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
boomerbubba said:
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
Click to expand...
Click to collapse
I now attribute this to pilot error. I must have screwed up the initial pairings between my car and my Nexus 6. I deleted those pairings and redid them. Now my phone connects automatically when I start the car.
So, in the words of the late, great Gilda Radner on SNL: "Never mind."
I have the same problem. PITA!
My new (10 Dec 2015) 6P will not discover any of my Bluetooth device, must less connect
I use BT at home daily for listening to music and netcasts. I have a couple of different BT speakers as well as the awesome Panasonic Link-to-Cell phone system for those who have dropped their home hard-wired phone lines. I also use BT constantly when I am in my car.
With my LG G2, BT connection was seamless and immediate, all the time, for years now. It connected to multiple devices as soon as I walked in the door and with my car audio as soon as I started my car.
With the N5, it always needs to be re-paired manually - especially at home where there are two devices waiting to pair with it as soon as I come home. It'll pair with the Panasonic phone, but when I select a speaker, the N5 disconnects from the Panasonic and then I have to re-pair with it. It will work once I spend a moment managing connections. In the car it often pares immediately, but sometimes not.
Another observation is that the N5's BT range is short, and it will drop if a line-of-sight gets interrupted momentarily.
In an attempt to fix, I have wiped the cache for both Bluetooth apps that come with the VZW N5 - that didn't help. Then, I wiped the system cache, also no dice. I wonder if this is carrier-dependent (I am on VZW) or something to do with older BT devices and the newer BT protocol that the N5 uses. I've read that the N4 has similar BT issues.
Overall, it's usable, but not as good as my old G2. Anyone else have these issues? Fixes??
This issue persists to this day. I can accommodate it with some manual intervention when I want to connect to my BT speakers.
Looking to get a BT 4.x speaker to see if it's just a BT version issue.
I only use Bluetooth in my car and I haven't had any issues whatsoever. Always connects as soon as I start the car and never drops the connection or anything. It syncs my contacts and everything just fine as well. I don't use Smart Lock however. Maybe try turning that off?
billykxda said:
or something to do with older BT devices and the newer BT protocol that the N5 uses. I've read that the N4 has similar BT issues.
Click to expand...
Click to collapse
I think that's the case. For some reason samsung's 4.1 Bluetooth protocol is not backwards compatible. Ever since the s4 Bluetooth meta data has stopped working in my 2012 Mazda. Works fine with my N5 (nexus 5) and my LG G4. If I had to bet I think that's the issue with you. I could be wrong. Just thought I'd share.
mrnovanova said:
I think that's the case. For some reason samsung's 4.1 Bluetooth protocol is not backwards compatible. Ever since the s4 Bluetooth meta data has stopped working in my 2012 Mazda. Works fine with my N5 (nexus 5) and my LG G4. If I had to bet I think that's the issue with you. I could be wrong. Just thought I'd share.
Click to expand...
Click to collapse
Note 5 always works with my car, does not drop or anything but it has an unstable connection to my samsung gear circle headphones. I believe it is the 5.1.1 update, because they work with my wife's note 3 just fine and they used to work fine before the 5.1.1 update.
Did you ever resolve your issue? looks like some are successful after getting their device replaced and others are not and say the problem comes back. All seems to be related to the 5.1.1 update..
Bluetooth and Note 5, horrible combination
IceCreaMan said:
Did you ever resolve your issue? looks like some are successful after getting their device replaced and others are not and say the problem comes back. All seems to be related to the 5.1.1 update..
Click to expand...
Click to collapse
Thanks for writing. I found out that if I disable wifi, it connects a little better, though not as good as my wife's phone, Note 3 (my previous phone)
I tried to find ways to change the frequency it connects, but google was not helpful. Maybe some of the experts here could be helpful, I do not know.
Anyways, I tried to connect to our smart bulb yesterday. It would pair, but would never connect, wifi or not. On the other hand, the Note 3 connected to it immediately.
They keep updating the gear circle software but it is the phone fault, since gear circle is able to connect to my laptop from even another floor!
It's not the BT device... I have terrible luck with expensive purchases and my note 5 was no exception. I upgraded from a galaxy S relay (love keyboards) and about 1 month later my Bluetooth stopped working from all through my house to needing a DIRECT line of sight and max range of about 2 feet. Netflix, hulu, audible all pretty much useless with this issue.
I returned it and got a new one (not referbished) and I noticed a slight lag in key strokes. About 2 weeks go by and the bottom half of my screen is going haywire. Trying to scroll a Web page and it would click everywhere. Typing like I am now would result in 100s of extra letters I was never close to pressing. I returned it and got a referbished one and same thing... my 4th one which I'm using to type this just started doing the Bluetooth thing and I'm so mad.
It's not the Bluetooth device because I tried my old Plantronics I used for 5 years, my new Plantronics, my car, and these weird speakers that have water pumps in them and the issue was the same. I love this phone but it seems to hate me...
Android version
time4my5thnote5 said:
It's not the BT device... I have terrible luck with expensive purchases and my note 5 was no exception. I upgraded from a galaxy S relay (love keyboards) and about 1 month later my Bluetooth stopped working from all through my house to needing a DIRECT line of sight and max range of about 2 feet. Netflix, hulu, audible all pretty much useless with this issue.
I returned it and got a new one (not referbished) and I noticed a slight lag in key strokes. About 2 weeks go by and the bottom half of my screen is going haywire. Trying to scroll a Web page and it would click everywhere. Typing like I am now would result in 100s of extra letters I was never close to pressing. I returned it and got a referbished one and same thing... my 4th one which I'm using to type this just started doing the Bluetooth thing and I'm so mad.
It's not the Bluetooth device because I tried my old Plantronics I used for 5 years, my new Plantronics, my car, and these weird speakers that have water pumps in them and the issue was the same. I love this phone but it seems to hate me...
Click to expand...
Click to collapse
Quick question, do you have android 5.1.1 or 6? I still have 5.1.1 and thats when it started with the problems. It was all fine and dandy with android 5.0.
My wife has a Note 3 with 5.0 and the same headphones are just fine with it.
I have been waiting for android 6 to see if it works out.
My Note 5 upgraded itself to Android 6.0 and all my bluetooth problems are solved magically. I cannot believe how they can manage to screw up things for so many months and we have to wait for the new OS to have it solved. For Samsung Gear Circle none the less. I know I am not buying bluetooth watches or anything in case they screw up bluetooth again in an "update".
I just noticed that phone is not connected to my bmw car kit most of the time, because BT keeps stopping. Now this is a show stopper for me. This seems like yet another cheap Chinese device which has nothing to do with Nokia.
Sent from my TA-1004 using Tapatalk
zdravke said:
I just noticed that phone is not connected to my bmw car kit most of the time, because BT keeps stopping.
Click to expand...
Click to collapse
Any other people who have the same problem? I do need BT all day for headset and connection to an OBD-device..
Gesendet von meinem EVA-L19 mit Tapatalk
I'm connected all day and night to a Xiaomi Mi-Band 2. BT never disconnects from it.
Also when I'm driving, I connect to a 2nd device which is an MPOW bluetooth receiver connected to the car's aux port. Also never experienced the BT stopping or dropping the devices (2 simultaneously, yes, using Oreo beta).
Dunno if this helps or qualifies to compare what you're experiencing.
I experience the same Bluetooth disconnections while using my Parrot carkit. Unusable for now. Running on Nougat oct security update
People report about car connection in other phones too, I think it's might be a OS problem. For me I use bluetooth headphone, never get disconnected. But sometimes have audio drop out when moving.
I have a slightly old ford kit.
Yes Bluetooth on it seems a hit or a miss. Connects and the audio comes for a few seconds and then just stops. Calls or audio just stops to work
I would like to blame the phone since my old Nokia 808 and galaxy S6 work fine but my brother's one plus 3 has the same problem.
Bluetooth audio plays just fine over my Volkswagen stereo BUT the play/pause/skip doesn't work and the song info (metadata) doesn't display.
Really frustrating as it was working so well before on my Huawei P9.
I'm running 7.1.1, really hope Oreo comes quick to fix this ?
shiggs1988 said:
Bluetooth audio plays just fine over my Volkswagen stereo BUT the play/pause/skip doesn't work and the song info (metadata) doesn't display.
Really frustrating as it was working so well before on my Huawei P9.
I'm running 7.1.1, really hope Oreo comes quick to fix this
Click to expand...
Click to collapse
This was the not very useful advice from Nokia support.
You may have guessed that it didn't work and I'm back using my Huawei... Looks like this phone will be going back to the seller by the end of the week.
Unless Oreo magically comes to save the day. Anyone want to place a bet?
Nokia implemented Bluetooth version 5 so maybe there is a compatibility issue.
PanNet said:
Nokia implemented Bluetooth version 5 so maybe there is a compatibility issue.
Click to expand...
Click to collapse
Thanks but it was my understanding that Bluetooth versions are backwards compatible? It's a 2012 car stereo and I've tested 2 other Nougat 7.1.X devices which work perfectly.
Music does play from the Nokia but it's the controls and song info that is missing.
I'm back to using my Huawei P9 as my daily driver because of it
So it seems as if there are mostly problems when running Nougat, while it's working under Oreo.
Will watch this thread before going for a new handset. Quite unsure between Mate 10 non-pro, Nokia 8 and OnePlus 5/5t. Dual-SIM is absolutely necessary for me, in Germany they use band 20 (800 MHz) in many areas. As I'm using a Samsung Gear S3 and that OBD-device in my car and furthermore a BT headset, a bigger battery or more efficient device is what I'm looking for.
Seems as if this is getting hard to decide...
sent directly from my mind using my upper extremities..
I'm seeing issues on Nokia 8 with Ford audio in my van. It's not that it disconnects, but when skipping to next / previous song in Play Music, progress indicator continues to move, but no audio comes out unless turn off Bluetooth and back on. Happens when using onscreen skip button, or steering wheel skip buttons. Same worked fine with Nexus 6.
shiggs1988 said:
Thanks but it was my understanding that Bluetooth versions are backwards compatible? It's a 2012 car stereo and I've tested 2 other Nougat 7.1.X devices which work perfectly.
Music does play from the Nokia but it's the controls and song info that is missing.
I'm back to using my Huawei P9 as my daily driver because of it
Click to expand...
Click to collapse
I am using my Nokia 8 for about a week with Ford Ranger (about one year old) and completely there is no any issues.
Regards
A workaround (of sorts) for me is to cycle through the inputs in the car dash (bluetooth, aux-in, fm1, fm2, dab, then back to Bluetooth) which brings audio back and the skip/next buttons work as intended.
Should also clarify that it is not just Play Music. Same issue in Castbox, so not app specific.
Fired up the Nokia 8 last night and see there's a November security patch being rolled out.
This seems to bring my kernel version up to Nov 9 - hopefully this might have an effect on the Bluetooth compatibility and stability?
Haven't had a chance to test it yet but it's going back on Saturday morning if not fixed...
shiggs1988 said:
Fired up the Nokia 8 last night and see there's a November security patch being rolled out.
This seems to bring my kernel version up to Nov 9 - hopefully this might have an effect on the Bluetooth compatibility and stability?
Haven't had a chance to test it yet but it's going back on Saturday morning if not fixed...
Click to expand...
Click to collapse
I have only connection problems with my Parrot 3100 carkit. Connection drops when calling. Bluetooth connection drops randomly. Stays connected when not calling. No issues with other Bluetooth devices.
The November update did not solve the carkit issue. Unfortunately. My hopes are on Oreo..
Renejo said:
I have only connection problems with my Parrot 3100 carkit. Connection drops when calling. Bluetooth connection drops randomly. Stays connected when not calling. No issues with other Bluetooth devices.
The November update did not solve the carkit issue. Unfortunately. My hopes are on Oreo..
Click to expand...
Click to collapse
My problems are still persistent on the new November kernel.
I feel like this will be a forgotten device once the Nokia 9 is released in the New Year...
Would any of these Bluetooth developer options help those having issues?
mitchst2 said:
Would any of these Bluetooth developer options help those having issues?
Click to expand...
Click to collapse
I believe these are Oreo specific and despite the fact the rollout began yesterday it's yet to hit my phone. Fingers crossed, I've extended Nokia's deadline until Monday ?
shiggs1988 said:
I believe these are Oreo specific and despite the fact the rollout began yesterday it's yet to hit my phone. Fingers crossed, I've extended Nokia's deadline until Monday ?
Click to expand...
Click to collapse
I'm on official Oreo release so you are correct.
Hi guys,
I'm experiencing some odd issues getting bluetooth to work on my BMW Series 5, 2011. I've already used multiple devices over time, including most iPhones, Xiaomi, Pixel 2XL, etc, without any issues. My Note 9 is able to find my car's bluetooth device and apparently connects just fine, however, after requesting a couple of permissions it seems to struggle to maintain connection and then seems to keep frequently connecting/disconnecting.
I've already tried using a different "AVRCP Version" under Developer options, but it doesn't seem to make any difference. This is my first Samsung device, are there any frequent issues I may not be familiar with?
SM-N960F - Exynos
No root - up to date software
Cheers
elmemyself said:
Hi guys,
I'm experiencing some odd issues getting bluetooth to work on my BMW Series 5, 2011. I've already used multiple devices over time, ...
Click to expand...
Click to collapse
Try to remove previously paired devices from your car, including this one and repair it.
You should leave the BT dev settings on their default as the phone is choosing the best based on the car's system.
Try also to go to Location's settings, improve location and disable always scanning of BT and Wifi.
mmuntean2 said:
Try to remove previously paired devices from your car, including this one and repair it.
You should leave the BT dev settings on their default as the phone is choosing the best based on the car's system.
Try also to go to Location's settings, improve location and disable always scanning of BT and Wifi.
Click to expand...
Click to collapse
Thank you, but unfortunately it didn't help. I even though it was due to being BT 5.0, but the Pixel 2 XL which I used before also had BT 5.0 and worked flawlessly. So weird
You might have to get a new car to go with the new phone
clone1008 said:
You might have to get a new car to go with the new phone
Click to expand...
Click to collapse
Don't be that person lol thats not helpful. I had these same issues when I owned the LG V20 and the only thing people did was mock my Bluetooth issues and told me to buy a new truck.
BigMosely said:
Don't be that person lol thats not helpful. I had these same issues when I owned the LG V20 and the only thing people did was mock my Bluetooth issues and told me to buy a new truck.
Click to expand...
Click to collapse
Lol... I'm sorry. If it makes you feel better I am having similar issues with my 2017 Audi A6. I have to constantly turn off my Bluetooth and turn it back on every time I get in my car to make it work.
I am having exactly the same issue with my 2011 330i. Connects then drops out. Phone says it is connected sometimes yet the signal strength icon on my car display flashes with no bars lit. I have unpaired and deleted the phone from the car but still will not work. I don't want to buy a new car either!!