Related
Is anyone else having issues with the bluetooth connectivity with their HTC Inspire? It pairs with my car with no issues. The bluetooth drops in and out. It says bluetooth headset connected... then 1 minute later it says bluetooth headset disconnected... and so on.
The car doesn't recognize that it is gone so the sound stops on the speakers in the car but the phone doesn't switch the source to the phone. I have to switch it manually to get back to my call.
Anyhow, I see a lot of articles on google where people are complaining about this but I have been unable to find any resolution. Has anyone here had this issue and resolved it?
Any advice would be greatly appreciated.
Same is happening with mine. I paired my inspire with the car and it connects. But if I use it no connection or doesn't dial. When I receive a call and disconnect, my car will stop the connection but the phone stays on.
I might be restoring to stock to see if it's just an inspire thing or bug with different ROM's
zerocalories said:
Same is happening with mine. I paired my inspire with the car and it connects. But if I use it no connection or doesn't dial. When I receive a call and disconnect, my car will stop the connection but the phone stays on.
I might be restoring to stock to see if it's just an inspire thing or bug with different ROM's
Click to expand...
Click to collapse
I am using my phone stock and was thinking about rooting it if it would fix it. I am new to Droid phones so I have not read enough to be comfortable with rooting quite yet...
Have you found any solution to this issue? I've just bought a BT headphone (Plantronics 903+), and as a I put it in my left pocket (where it is supposed to be placed since the headphone antenna in the left side), connection dropping starts and never stop happening. The movement seems to stress the connection quality and it gets really annoying, I can't listen to music without having this chopped streaming all the time.
I thought to post this question here since this is the only post I found about the same issue, but I will put a specific one about Plantronics and Inspire if I can't come out with a solution. I'm really very disappointed now with the headset, the phone or I don't really know which one is the guilty one.
Thanks in advance
it will not work. since after rooting, my phone cannot pair with my Garmin GPS, but it did with the stock rom.
greatzt said:
it will not work. since after rooting, my phone cannot pair with my Garmin GPS, but it did with the stock rom.
Click to expand...
Click to collapse
I still have the stock rom
I've been having bluetooth problems with this phone since day 1 & I'm wondering if it's just my phone or if anyone else is having the same experience. No matter what rom or headset I use, I get a craptastic connection. I don't have any problems pairing devices, but I can't get 10 feet away from the phone without it disconnecting and I can't even turn my head without the audio cutting out. It also randomly disconnects for no reason & sometimes won't reconnect until I reboot. This has happened with every rom I've tried & every headset too. I've bought & returned multiple headsets thinking it was just my Blueant, but it happens with every one.
Could I have a faulty unit or does the bluetooth on this phone really suck this bad? I listen to podcasts & music all day long at work so I need to have a decent connection. Opinions needed please.
I think it may be a bad phone.
I have and used the following bluetooth devices:
Plantronics 590A
Jawbone Icon and Era
BlueAnt S4 which I use in the car. And auto connects before I sit down to drive when I have it on.
Sony Ericsson MW600
And Jabra Pro 9470 (office phone setup that connects to my phone via bt)
All connects without a problem. Have you done a titanium backup and perform a factory reset? And after the reset use titanium backup to restore app and data only and leave the system settings alone. You can restore the wifi stuff if you like. From there that's like a fresh install. Hope that works for you.
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
kabuk1 said:
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
Click to expand...
Click to collapse
Well before leaving the store...if you are going to a brick and mortar to do the exchange, bring the bt headset with you and try it out there and try to replicate the problem with a new phone.
I do not have range problems but I don't usually have my phone more than 5 ft way from me when talking on it via bt.
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Macklessdaddy said:
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Click to expand...
Click to collapse
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
rosedog said:
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
Click to expand...
Click to collapse
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
kabuk1 said:
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
Click to expand...
Click to collapse
No you will have to call T-Mobile and do a warranty exchange. I have no problems with BT on my phone at all.
http://androidforums.com/htc-sensation-4g/375199-white-noise-bluetooth-htc-sensation-4g.html
http://community.htc.com/na/htc-forums/android/f/133/p/12494/52795.aspx
http://forum.xda-developers.com/showthread.php?t=1184936
a few threads about bluetooth problems
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
rosedog said:
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
Click to expand...
Click to collapse
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
kpjimmy said:
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
Click to expand...
Click to collapse
You've been running what and what?
MIUI / Sense-o-maniac 3.5?
I'm running the latest ARHD w/sense 3.5
horrid bluetooth sound quality
it seems a lot of people have been having issues with the bluetooth sound quality. i have mine paired with a motorola HF850 car kit, which has bluetooth v1.1, or something like that. i wonder if the problem is with backward compatibility, as people seem not to have as many issues with newer devices. would flashing a different radio potentiall help this problem? is it possible to downgrade the bluetooth version with a custom ROM? any other thoughts on ways to address this issue?
I am wondering if any of you fellow Verizonites would be willing to help me test this out, as I have already asked my friend with the AT&T version if his does this, and it does not:
When connected to the aux in (very common on cars and stereos nowadays, you know, so you can listen to music off your phones and iPods and MP3 players, etc.) I now have the SAME incredibly aggravating problem I could never resolve with my Fascinate. As usual, I have my bluetooth connected to take the call. When I answer the call, I hear NOTHING over my bluetooth unless I disconnect the audio cable out of the headphone jack!!! This is a huge safety hazard, as it takes your hands and eyes off the road, requiring you to disconnect a cable every time you get a call!!
I called Verizon and complained about this with my Fascinate to no avail. I never had this issue with my Droid X, HTC Eris, or my Galaxy Nexus, another dual core Snapdragon based Verizon LTE phone made by Samsung.
Not to mention the SGS III is laggier and less responsive than my Nexus, although not as bad once you disable S Voice (S is for stupid, by the way, at least in my opinion ... I can't get it to work worth a darn!! Could be that I'm the stupid one, but I've certainly given it a lot of effort in a very quiet environment.)
This is horrible because the screen is incredible, and the battery life far outpaces every other smartphone I've ever had by a ridiculous margin, so PLEASE, fellow Verizon SGSIII friends, help me out if you can!! I don't want to have to return this phone, but reasons to do so are stacking up.
If there's no fix for the audio cable thing, that is a definite deal breaker, and enough to make the phone "defective" in my opinion. That is such a blatant safety hazard. I do NOT want a "Fascinate 2". The other issues pale in comparison to the audio cable issue.
Here is a video of the AT&T version NOT having this glaring safety and functionality issue:
http://www.youtube.com/watch?v=A37p4fF-h-k
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
I tested it with Bose Bluetooth earpiece and that works, somewhat. If you have the Aux plugged in and get a call, the phone picks up your voice from the Bluetooth and plays the other guys voice through the Aux. Unplugging the Aux mid-call will route the other guys voice back to the Bluetooth. In both cases both me and my friend could hear each other.
There is a problem though. When the Aux is plugged in, with Bluetooth our not, the call quality will drop significantly. It will sound as if you're in a horrible signal area and will cut out every other second or so making it impossible to carry on a conversation. Funny thing is as soon as I unplug the Aux the call is back to normal and we can hear each other just perfect. It's as if with Aux the noise cancellation kicks in and starts cancelling out everything, including your and the other guys voice, lol. Not sure if that's just my phone or SGS3 in general. I actually intentionally used this "glitch" to avoid taking to annoying person. Just tell them "I'm in a bad area and can't talk" and plug in the aux mid-call and they will stop bugging you as soon as they hear the voice glitch up
My bluetooth headset works fine with the audio out through the "dock" connector.
macdroid01 said:
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
Click to expand...
Click to collapse
Same here
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
same here too
I upgraded from a fascinate to a s3 and have the same problem on both phones. It is really annoying and I'd love to find a fix for it.
adsbar said:
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
Click to expand...
Click to collapse
I think I am having the same problem with the Bluetooth in my 2010 G37. It seems like if u connect via Bluetooth for media audio, I can't get calls and vice versa. Plus when I connect to media audio and try and switch back to just phone, it doesn't auto connect when I get in the car.
My Rezound didn't seem to have any of these issues.
Sent from my SCH-I535 using xda app-developers app
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
sinman02 said:
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
SirKronan said:
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
Click to expand...
Click to collapse
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
CIPuyleart said:
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
Click to expand...
Click to collapse
Does the S3 fit into the dock ok? Any stability problems? And you get proper 3.5 inch output for your car's input, plus your bluetooth call works? I have the same kind of deck in my Freestyle. Installed it myself. It does bluetooth for calls but not A2DP. Thanks for your responses so far! I am willing to buy a dock if it works like that. I would just appreciate any reassurance you could give me that it will work out ok ...
but that's a really nice idea that i didn't consider. I would really like to get this thing working and willing to apply any dev fix. what's interesting is that skype calls work fine, yet regular phone calls do not i'll give this doc a try.
Ok, I have the dock now, and wanted to update everyone on this. Audio quality is good, better than bluetooth, but an ever so slight downgrade from just plugging straight into the headphone with an audio cable, but it's certainly good enough.
The one thing that is annoying enough to prevent me from using it is that there is an audible click between each song. I haven't a clue how to get rid of this!! ARGHH!!! I haven't tested the dock with video or pandora output to see if the clicks persist, but as of right now, it's a bit annoying on a long trip. Otherwise, this would work really nicely, and is a pretty cheap fix for $18, not to mention getting a fully functional windshield/dash mount to use your phone as a GPS with.
Hoping my new ROM I installed might solve the audio issue. It has a custom kernel, and possibly improved car dock compatibility. We shall see...
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
misterpat1975 said:
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
Click to expand...
Click to collapse
SoundAbout Pro is an app that will override Samsung's stupidity when it comes to BT/AuxJack audio routing. Well worth the price of admission.
Hi all,
I have successfully rooted and flashed Paranoid Android 2.54 onto my ATT HOX and it is a wonderful ROM for sure. I love the options that it provides and the silky smooth, almost stock interface. The only real issue that I have come across is when I try to use a headset for calls. I am defining a headset as a 3.5mm plug in set of earbuds with mic (Klipsch S4i to be exact). When I listen to music, be it on Pandora, Google Music or Apollo all is well. As soon as I try to use the phone, no sound comes through the earbuds and the mic does not function. In fact you can see a noticable slow down in the dialer app when the headset it even plugged in. If I make a call, then plug in the headset, everything goes silent and the other side can't hear me until I unplug the headset from the phone.
Here is the real kicker though! I have my car stereo modded with an aux 3.5mm plug for listening to music and if I plug the phone into that it works just fine in phone mode! Now, I do realize that the Klipsch is setup as a TRRS and the car aux is just TRS (so when using the car stereo I am effectively bypassing the mic portion of the 3.5mm plug and using the phone's mic), but I cannot for the life of me understand why the headset will not work.
I am hoping that someone can enlighten me or least tell me that they to are experiencing this same issue. I will gladly provide any more info that someone might need to help diagnose the issue, and thanks in advance!
Update so far...
So, up to this point here is what I've found. If I plug in a normal set of earphone (read buds only no mic inline) then I will get sound through them no matter what I am doing (youtube, music or phone). Also, in this configuration anyone I am talking to on the phone can hear me just fine as I am using the phone's mic. However, when I plug in an earbud/mic combo the phone will not function. I get silence and the other side cannot hear me speaking either. It's as if the software has somehow told the headphone jack to act differently than it used to with earbud/mic combos. I am stumped as to why the OS would not allow this type of use when it is so standard. Anyone have any thoughts?
I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me
sourshin said:
I actually have the same headset and I started having problems with it on the stock rom before I even rooted and flashed a custom one. I honestly just thought it was because they're really made for apple phones. Sometimes I'll just unlplug and plug them back in for them to register. Other than that I haven't seen a fix for them.
P.S. Klipsch control from the play store seemed to make things worse for me
Click to expand...
Click to collapse
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...
guitarman710 said:
Thanks for the response! Yeah, I think I am going to try another ROM just to see if it will help, but I have the distinct feeling it might be a hardware issue. I just can't understand why this would all the sudden malfunction right after rooting for me. Maybe just a coincidence. I will definitely respond here though if flashing to a new ROM helps...
Click to expand...
Click to collapse
I've never tried paranoid but King kang(which has paranoid elements) works fine for the most part. nocturnal'd dirty rom, miui, and cm10 have all worked for me tho. I'm currently on the unofficial cm10.1 4.2 and that's working for me as well, except when I have the headset plugged in while booting.
Final Update....And SUCCESS
So, it appears that it was some sort of ROM specific issue. I flashed CleanROM 5.1 to my phone and "wah-lah"! The headset works perfectly in all modes. I am not sure what it was about Paranoid Android 2.54 that would not allow the headset/mic combo to work with the phone, but I am free of it now I guess. I will miss the interface of PA, but boy does CleanROM run FAST!!! I am in awe of the speed and responsivness. I hope the battery life holds up like PA did for me and I also think that the quick settings on CleanROM basically RULE.
In my corvette and my cadillac my bluetooth wont stay connected for music after i leave the car and return back into car, Ill have to delete it and repair to stream music bluetooth. anyone having these same issues with there Tmobile Lg G5? because if not ill return mines
I have a similar issue. I have Bluetooth headphones I always wear. And I have a Bluetooth connection in the car. When I get in the car it tries to play over the car (said it would play audio over the last Bluetooth audio connection connected the first time it paired) but I hear nothing. If I change the connection between either Bluetooth connection I get no audio. I can only get audio if I play it directly on the phone or I turn the headphones off, then restart whatever app I was using to play music. It is quite a pain.
Sent from my LG-H830 using XDA-Developers mobile app
try in your rolls royce and your aston martin and see if you can replicate the problem, OP.
[jk but we need more info: factory or aftermarket bluetooth receivers in these vehicles? how did they behave with connecting to different devices via bluetooth? mine is an aftermarket stereo and it connects automatically in about 30-60 seconds or i can just open bluetooth settings and select my stereo's name and its instant. never have to re-pair.]
RiverdALIEN said:
try in your rolls royce and your aston martin and see if you can replicate the problem, OP.
[jk but we need more info: factory or aftermarket bluetooth receivers in these vehicles? how did they behave with connecting to different devices via bluetooth? mine is an aftermarket stereo and it connects automatically in about 30-60 seconds or i can just open bluetooth settings and select my stereo's name and its instant. never have to re-pair.]
Click to expand...
Click to collapse
In my car I am using a cheap usb Bluetooth dongle connected to audio in port. I connect fine. It actually connects very quickly and from much further distances as my previous phones. Main issue is the sound seems to go nowhere if I have more than one Bluetooth device connected at once.
Sent from my LG-H830 using XDA-Developers mobile app
I have the same issue with my JVC Bluetooth car radio... What I have done to resolve the issue soo far is turn the bluetooth off through the quick menu then start my vehicle, turn bluetooth back on and it works properly then.
I have my radar detector connected via Bluetooth and my car , stock radio 2012 camaro .. I will be listening to music then randomly it goes blank forcing me to wait for a disconnect and reconnect again to hear anything
Sent from my LG-H830 using XDA-Developers mobile app
Had This Issue With My Car and the LG V10 & G4 But not G5
Maybe just maybe there are 2 different chipsets for bluetooth. I had this issue you're talking about in my 2016 Honda HRV with both of LG previous phones, LG V10 & G4. Typically, they do fix this issue with updates however I think it might be "deeper" than that... if there's 2 different bluetooth chips being put into phones it might explain the issues that some people get and others do not. I know when I planned on getting the LG G5, I made sure it was not at the store where I would have to give over my Jump On Demand phone immediately, my S7 Edge, before I confirmed this issue was not present with the G5. At any rate, I lucked out I guess because knock on wood, no issues. Don't know if would could ever confirm different chips but hopefully they release a bug update to fix soon. :good:
mahst68 said:
Maybe just maybe there are 2 different chipsets for bluetooth. I had this issue you're talking about in my 2016 Honda HRV with both of LG previous phones, LG V10 & G4. Typically, they do fix this issue with updates however I think it might be "deeper" than that... if there's 2 different bluetooth chips being put into phones it might explain the issues that some people get and others do not. I know when I planned on getting the LG G5, I made sure it was not at the store where I would have to give over my Jump On Demand phone immediately, my S7 Edge, before I confirmed this issue was not present with the G5. At any rate, I lucked out I guess because knock on wood, no issues. Don't know if would could ever confirm different chips but hopefully they release a bug update to fix soon. :good:
Click to expand...
Click to collapse
Mine worked fine for the first day or soo then started having issues....Weird thing is that I never had issues with my V10 and the same radio
I have this exact issue... can't quite figure out who to talk to about it (ex. Marshmallow Android or LG support) I've tried more than 1 LG G5 phone and the same thing occurs across what appears to be all GM manufactured vehicles (of which I'm assuming doesn't necessarily have to do at with any manufactured GM vehicle, just coincidental.) Odd part of it is, when making calls through Bluetooth, that always works, no having to pair/unpair.
I too have wondered if this is primarily with GM vehicles. Had a rental Suburban that had the exact issue as OP. Luckily my '16 Canyon does not but then the reason I had the Suburban was because the dealer was doing the Android Auto update on my truck (among other things). Not sure if the issue would have existed previously in the truck since I didn't have the phone at that point. I've had no issue with Bluetooth on any other device though. On a truck forum I frequent though, others are having the same issue but with different phones.
Sent from my SHIELD Tablet using Tapatalk
the issue I have is when I have two bluetooth devices connected... so I have my hbs800 already on and streaming and I get to my truck and turn it on. At this point my phone now sees the Pioneer deck and connects to it, however randomly like 1 a week it will connect only call audio, not media. I've tried power cycling the deck, my headphones, basically everything but the bluetooth on the phone and it will never connect to media only call audio. I power cycle just the bluetooth on the phone and with no issue it will connect through media.
Having the same issue with my G5 connecting to my 2015 Colorado. Initial pairing music streams fine. Shut the truck off and turn it back on, everything reconnects, but no audio is heard. Have to completely unpair and delete connections and start over to get it back working. I hope this gets fixed soon!
Works fine in my Acura ILX stock radio
Seems to be a compatibility issue with GM products. Have the same issue with both my '16 GMC Canyon and a rental Suburban. Very irritating. At least with my Canyon I can plug the phone in and use Android Auto, which works well.
Sent from my SHIELD Tablet using Tapatalk
The BT is total garbage on the G5. I use LG tones at work. I'll be walking around the shop which can be noisy and music will just stop. After the machinery quiets I'll realize the music is playing from the phone speaker. On my way to work this morning I'm getting into The Sickness and it's just picking up and all the sudden the music stops and starts playing through the phone speaker. I pulled over and restarted my car, it reconnected so I took off again and 30 seconds later it did it again. It happened once before while playing Let It Go for my kids so I wasn't even mad about that but today I almost lost my ****...
How fo i connect my LG G6 to my Kenwood...it asks for passkey and o put in 0000 and say wrong passkey