Related
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
I am rooted but still using the stock ROM. I have two Bluetooth-enabled Pioneer head units and a Bluetooth adapter for my home stereo system with this issue, so I know it's not the other Bluetooth device that's the problem.
When I pair the other Bluetooth device, everything works fine until the Bluetooth device disconnects. I either leave the area with my One, or turn the car off. When I come back home or turn the car on, the One will not reconnect unless I manually turn Bluetooth off and turn it back on again. I don't have to redo the pairing, just cycle Bluetooth off and on. This gets really, really annoying with the car stereos because I have to do it every time I make a stop.
The weird thing is, I had the problem before and it went away when the KitKat update was released. Unfortunately it only worked for a few weeks because I sent my One in for the pink camera issue. I did a hard reset before sending it off and rooted it got back, and now the Bluetooth problem has returned even though it's still on 4.4.2.
Anyone know how to make this go away?
No one is having a similar problem or knows how to fix this?
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
Anyone else haing issues here with bluetooth? I can connect to everything bluetooth, wireless speakers, car, headsets, watch etc. The only thing I can get to work reliably is the headset, everything else randomly cuts out or has issues. For example both cars have bluetooth for phone calls, one has bluetooth for media, I can get both to work for a short time but it either 1. Cuts out and reverts back to phone, freezes the system in the one car, or jumps back and forth between the 2. Similar results when connected to bluetooth speakers, can get it to work for about 10-15 minutes then nothing, phone shows it still connected and playing music but no sounds from speakers. LG G Watch R also randomly looses connection. I'm beginning to regret my switch from the S5.
Anyone having similar problems or a fix?? I really want to keep the phone but not sure I can deal with this flaw...........
I have no such issues with the bluetooth. I can tell you that I had bluetooth issues with one of my other android phones. I had to get it warranty replaced. My suggestion is that you get the phone replaced since its brand new.
Mine has been fine so far. I just wish that android was more like apple, as much as I hate to say that. Both my S6 and M7 will play phone audio fine when in a call, but to use maps I have to turn the radio to Bluetooth mode. Makes it kinda boring to ride with no radio just to get turn by turn nav.
Sent from my SM-G925V using XDA Free mobile app
I haven't had any issues with my smart watch (moto 360) but I have had some weird issues with my car's Kenwood media deck. The phone will connect to the unit, but 75% of the time no sound will come from the speakers on the first try. Sometimes just waiting about a minute does the trick, other times I turn BT off/on and it'll work fine the 2nd time. However because I haven't had any issues connecting with my watch, ear piece, or laptop I am willing to bet it's it an issue with the Kenwood and not the phone.
Thanks guys. Don't want to have to warranty swap it but looks like that's going to be my first step.
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".