BT calling - LG G6 Questions and Answers

It seems like every custom ROM - Oreo and Pie - has BT calling broken. Obviously, there is something about our device that makes this function dependent on something stock.
Can anyone please explain why this is? Better yet, is this fixable? BT calling is a must for me.
Thank you.

Got the same issue here https://forum.xda-developers.com/lg-g6/help/g6-h870-bluetooth-call-issue-t3821048 but looks like it might have been fixed on lineage. It does work with a brand new Kia Rio, bur I haven't yet had the chance to try my phone on some other cars, so I'm not sure if lineage was finally fixed or it's just the Kia being able to make things work.

Related

All Bluetooth device Mic's dead

I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its speaker works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
CJSnet said:
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its output works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
Click to expand...
Click to collapse
I do have exactly the same problem. After flashing XDA Mobile 6 Release 3, microphone has worked for couple of days, and then suddenly died. Interesting, microphone is working with Notes but not with phone. I went back to
XDA Mobile 6 Release 2 for some other reasons (read: 2MB more free memory for critical application) but the problem with Bluetooth microphone remains. Radio is 2.25. Any advice?
--
Pogo
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is sometimes temporarily resolved for a short time. It always comes back though
I have been asked to join this thread. Per a PM:
We love the ROM you have provided, and are very thankful, however it was not until installing it that this issue arose. It does not seem fair to leave a number of people with a phone that is unusable for 'phone calls'.
Click to expand...
Click to collapse
(Bolding added by me)
I don't know what to tell you. If the rom doesn't work for you, then don't use it... Don't tell me its "not fair". I use MS Voice Command, and XM6r3 and have never seen this issue with my Bluetooth headset (Jawbone). I've also tested this out with a Plantronics Explorer 210 headset that I have and it has not problems with XM6r3 either. My A2DP headset (Spider) also works fine on XM6r3 with MS VC. I've stated this in the past when people have said they have BT issues on my rom. Sorry, but I can't reproduce it, so its hard for me to fix something that isn't broken for me.
Try this... Do a hardreset on your device (take a backup first if you want), then leave it as the base rom with NOTHING extra added. Run that way for a few days (how ever long it has taken before) and see if the problem happens again. If it doesn't then its not my rom but something being added to it (probably screwing with the registry someplace). If it does happen, then as I've stated before, I've seen a number of BT devices be flakey on WM6 (especially car kits). Try a different rom then. If someone with the problem can pin it down, I'll be happy to do what it takes to fix this issue if its something in the rom that is causing it.
Thanks mfrazz. What wasn't fair was not the bug, but that you had not responded to previous mentions of it, i.e. not fair to leave us with it. We love the ROM and put a lot of our life in your hands in a way, as we rely on our device so much for work and play. Hope you understand.
Now then, I have already tried a hard reset and the problem never occurs, until WM6 is put back on. Sure, 'use another ROM' is all very well, but we love yours - again, hope you appreciate the sentiment. If you're in a relationship, are you the kind of guy who tells a girl who loves you, 'find another boyfriend', or do you try to make it work
SO, I am wondering if this is related to the glitch you mention where sometimes when switching out of vibrate mode, the ring tone becomes muted. For that, your solution is to play the ringtone again, then it becomes unmuted.
Similarly, our Bluetooth devices mic's are being muted, and if we mute then unmute them again, then they become unmuted. A link that helps point you in the right direction?
Please note, this is not certain bluetooth devices being 'flaky', this is ALL devices. 4 at the latest count, including rock solid Nokia CARK7W car kits and Jabra headsets.
Some people put it down to MS Voice Command, which I have never installed. What does that program do, do you know, to cause the bug? Again I hope that might help point you in the right direction.
Please don't dump us Let's try to fix what is wrong in this relationship
BT problem solved?
CJSnet - not sure if you have resolved this. I was having the same problem and noticed people with reTouched dialer were not, so I loaded that dialer and the problems went away. I am using a Plantronics Voyager 510. Seems the problem might be with the standard dialer.
Hope this helps
CJSnet said:
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is temporarily resolved for a short time. It always comes back though
Click to expand...
Click to collapse
Thanks, I'll give that a try. However WM6 has pretty much finished the Wizard for me, and I'm hoping to get a TyTN II soon as a replacement. Shame.

08 Altima Bluetooth

We just bought an '08 Altima with the bluetooth option. I can pair the XV6800 with no problem, but quality sucks. It is super choppy on my end and the person on the other end can't hear me at all. I tried my wifes XV6800, same thing. I can pair my old E815 and it works perfectly, so it's not the car. I tried a hard reset, no difference.
I tried loading dcd's clean rom 1.6.7, no difference. Is the BT stack upgraded in this rom?
Is there a newer BT stack out there that I could try?
Its worth downloading and trying the Jetware BT Extensions and see if that helps....but usually it does not change quality so much as enable functionality.
http://www.jetwaremobile.com/
Brad
Thanks for the suggestion, but it didn't help.
Developer help with Infiniti/Nissan Bluetooth?
I've got the exact same issue with an '07 Infiniti G35 w/navigation. I've been doing lots of reading on the xv6800's bluetooth, have tried DCD's and Custel's roms, and was just about to start my own thread, but I'll bet our cars are the same bluetooth/rom wise.
Jetware didn't help me either.
Here's the best fix I've found and it works for me consistently.
-Whence the option's available depending on whether you're dialing out or receiving, click the "use handset" button (transfers call to the xv6800).
-Shortly after press the "phone" button (transfers call back through car).
-Should work as expected after that.
Anyway, at this point I'm hoping one of the kind devs on this forum (DCD or Custel to name just two of many) might find a sec to help us out, although I'm aware and appreciate the fact that many other users are keeping them very busy on their own projects.
I'm assuming the xv6800's hardware would be most similar to other HTC pda phones (not sure what happens between GSM and CDMA devices), so here's a list of their phones who's bluetooth does work with my car (from here). It supports the bluetooth in 144 phones total.
Kaiser (wasn't working with stock rom, but works after this patch from HTC)
Hermes
Atlas
Wizard
Apache
Magician
Harrier
HTC pda phones that don't work with my car (at least not 100%).
Vogue
Elf
Titan
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
In addition to the stock Verizon rom I've tried DCD's 1.6.1, 1.6.7, and Custel's 1.1 with no change in the symptoms.
It's my understanding the dev community thinks modding the Vogue's bluetooth for the Titan shows the most promise. I found this thread mentioning an alternative, but it seems to have gone stale on another forum. I'd prefer not to use that forum.
I understand the Vogue's bluetooth might show the most promise for general bluetooth applications (which would satisfy the most users), but becuase I plan to use bluetooth solely through this car, does anyone know if I might be able to go an easier route given the information I've provided?
I'm using radio 1.40.00, could 1.47.01 make a difference?
Can anything be learned through HTC's Kaiser update patch?
Are there any bluetooth alternatives being tested that I haven't found?
Thanks for any help anyone can provide.
OK. I tried what you said and confirm the same results on the '08 Altima. If I switch to handset and back to Bluetooth, the sound is clear (weird). The only problem is, I can't switch until a call is in progress. This is a work around, but not a good one. We need a BT stack that fixes this. Or maybe firmware upgrade from the auto manufacturer.
I know this is going to sounds like a cheap shot, but it sounds to me like something needs to be fixed on Nissan's side. I've tried mine in an Accura without any problem, however both of your stereos are manufactured by Nissan.
A word of advice: I always found that auto makers should stick to what they do- namely, make cars. If Nissan were so great at BT stereos, you'd see nissan headsets.
I never bother with factory Bluetooth anymore- I swapped my stereo right away for a decent Sony Xplod system that supports A2DP (wireless stereo) as well as phone calls. The aftermarket stereo not only sounds great, but I play all my music from my phone without taking it out of my pocket. Last I checked, no stock car stereos supported this. Sony is good at stereo and bluetooth (been around the block a few times).
Complain to Nissan. Or swap your stereo for something decent.
My Sprint 6700 with BigJ Rom works great with the 08 Altima. In the fact the audio quality is better than the Sanyo Katana that I also have paired. I am dispointed that I cannt answer calls from both phones on the car headset without first selecting the phone that has an incoming call. Even my At&T home phone with bluetooth can do that although it does require you to select a cellphone for outgoing calls.
I was able to upload a contact entry from my 6700 to the car Download phonebook. However, I can not get that into the more usable phonebook directory. Anyone succeed in doing that?
shannl said:
My Sprint 6700 with BigJ Rom works great with the 08 Altima.
Click to expand...
Click to collapse
You might be in the wrong forum. The Titan is a 6800, not a 6700.
yes, but this thread is discussing the Altima BT stereo. Truthfully, this whole thread should go in a more general BT forum, since I don't think it pertains to the 6800 exactly.
08 altima bluetooth
Just wanted to say thanks to Park City for posting the name of the web site with the bluetooth extentions (jetwaremobile.com). I have just recently purchased an 08 Altima with the Nav system and bluetooth. I have an Tmobile MDA with a cooked ROM running WM6 and I could not get the entire outlook phone book to download to the car. Once I installed the jetware mobile extentions everything worked just fine. I even got some additional functionality I was not expecting like signal strengh and battery status on the nav srceen. As for voice quality, it's never been an issue for me. So far anyway
As I can see, they are currently testing the Mogul with both of your cars. I don't know what they mean by 'testing', but that's what is going on right now.
http://www.nissanusa.com/bluetooth/...gation+System&mfg=All+Manufacturers&x=51&y=16
http://www.infiniti.com/bluetooth/t...igation+System&mfg=All+Manufacturers&x=42&y=9
arcanecho said:
As I can see, they are currently testing the Mogul with both of your cars.
Click to expand...
Click to collapse
I saw that too, but I don't have a lot of confidence they'll be releasing a bluetooth update any time soon. That's why I was hoping the Titan's bluetooth hardware might be similar enough to the hardware in one of the devices that DO work with our cars (Kaiser, etc., list in my earlier post) that their bluetooth software could be ported "easily" to the Titan. I'm sure the devs here are trying to get the Titan's bluetooth to work as well as possible for everyone's devices, which makes sense. However, with California's new "handsfree driving" law starting July '08, I'm only concerned with getting the Titan to work with my car.
Apparently no one's too sure if that's possible.
1. have any of you verified first hand that the kaiser does in fact work?
2. could someone research and identify the bt hardware in the kaiser, and the titan?
3. has anyone run the kaiser bt fix on their titan and tried it?
i suppose i never thought to look at the kaiser's bt. mine still functions after applying that kaiser patch..
the kaiser patch is a replacement TIInit_4_2_38.bts file
this file did not exist in any titan roms prior to 2.16
2.16 introduced this file (i compared md5 and its not the same data)
2.17, htcs supposed 'fix', does NOT contain this file
all vogue roms i have seen DO contain this file, but again its different data
maybe you guys are on to something
i will throw something together tomorrow probably...drinking time.
dcd, thanks for the help, enjoy those drinks!
1. Not first hand, I'm going off this post. That thread's also why I believe the Kaiser wasn't working with the car before the patch.
2. I've spent a lot of time trying, but have come up empty on any detailed hardware specs.
3. I just ran the Kaiser patch and the bluetooth functions the same as it does without the patch.
I'm using a rom from your 1.6.7 kitchen with nothing else added (rom's working great, btw). I had the same issue with the stock Verizon rom.
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
FZ1 said:
this post
Click to expand...
Click to collapse
good enough for me
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
Click to expand...
Click to collapse
maybe...i dont know how the file functions and ties into the others yet
FZ1 said:
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
Click to expand...
Click to collapse
i take it they are completely different head units?
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it. I have been just using my Platronics Discover 640 for the BT these days... It'd be nice if someone can come up with a solution for this...
dcd1182 said:
i take it they are completely different head units?
Click to expand...
Click to collapse
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
riDuh7 said:
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it.
Click to expand...
Click to collapse
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
Click to expand...
Click to collapse
Once connected, I get a really static noise from my end while in the conversation. Of course, it'a really not usable at all....
I'm going to try the reconnecting method that was mentioned above today. I'll come back and report the outcome. And thanks for the help BTW.
EDIT: BTW, my Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to
Click to expand...
Click to collapse
whoa, someone hook me up with a G35 to uh, test
Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
Click to expand...
Click to collapse
well, peices of it maybe. i would blindly guess that the kaiser is closer to titan than hermes, but we need to exactly identify the bt chip in each. plus its still shady then, ie the kaiser has tnetw1251 for wlan same as the titan and I cannot get their newer wlan driver to work on my device.
what we really need to look at is previous bt stack modifications for other devices. i need a better understanding of tiinit_blah. I've also noticed that the devices that work have a more extensive, or a 2nd audiopara file that sets values for some bt devices. to be completely honest right now i dont know what im looking at and i need to figure out how it all fits together before i know where to start.
Well, I tried reconnect method from both phone and the car, but neither did anything at all. The quality is still crappy as heck. Man... I reallly wish this works.
EDIT: Actually my side of the speaker was complete static, and the other side could not hear what I was saying AT ALL. This efing blows.

My Continued Bluetooth Nightmare

OK,
So I'm trying to get some help regarding this issue. I will continue to try different ROM's and what not to see if it can be resolved. I'm simply at a loss to where the issue lies though, however as of today, every custom ROM has been giving me trouble. My plan for today is to flash a stock ROM via Odin and then if that works go for Imperium, however I'm hoping with your help I may be able to solve it on something like CM12 or what not because I prefer the flexibility of a proper custom ROM.
OK, so the issue I have:
I have a car head unit which has bluetooth built-in. Music plays fine through Bluetooth, no jitters or issues. However, when I try and call someone and I'm listening to the radio or something non-Bluetooth, the phone does not send the signal (?) to the head unit to switch to Bluetooth. This means the call will be made via the dialer app and while the audio IS being routed through the bluetooth channel, the head unit does not know about it because it hasn't received the signal to switch to Bluetooth. I can switch it manually to Bluetooth and make and receive calls, but this isn't convenient at all and probably quite dangerous when I'm driving a car. The same applies when receiving a call.
Here's the thing, if I go into Bluetooth, select CAR KIT and go configuration, if I disable Media Audio, then it works fine! The phone correctly sends the signal to switch to Bluetooth and the head unit does so. The call goes through and it all works fine. This is repeatable.
Therefore, the issue I'm having lies in the fact both Media and Phone Audio are enabled at the same time. Has anyone else had this issue and does anyone have a suggestion to fix it?
Before someone suggests "just disable media audio". My answer is no, this isn't convenient at all. I use Bluetooth media quite a lot, and simply disabling and re-enabling it everytime simply isn't an option.
So far, I've had this issue on:
CM12.1 Optimized
CM12.1 Nightly
Mokee ROM
DirtyUnicorns
CM12 Nightly
I'm yet to try a stock Lollipop ROM. I know for a fact however, that stock KitKat DOES work.
I really could do with some help here, so any suggestions would be awesome.
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
DSA said:
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
Click to expand...
Click to collapse
The Bluetooth itself is fine. Audio quality is fine. Call quality is fine. It just seems like a tiny little thing that's causing all these issues for me, because if it could trigger my car head unit to switch, I wouldn't even dream of stock. Also the camera seems fine to be fair?
I'm not keen on going back to stock.... at all, so I'm thinking Imperium. It's a shame though because apart from this BT issue, CM12 is fantastic on this device. Takes a 2 year old phone and makes it feel like a brand new phone.
I really hope someone can fix that Bluetooth bug in CM12.1. I may even look myself, it must be something pretty small from a coding perspective because as I said, the functionality is clearly there as evidenced by the fact it works with Media audio turned off.
Regardless, thanks anyway
Changing the modem did not solve my problem.
When did you try the Optimized and the nightlies? There have been a lot of fixes lately regarding bluetooth.

Bluetooth Cuts off In Car

I have a new issue, and need some ideas...
I have a Mazda 3 2014 with built in Infotainment system, and I can of course place calls from it over bluetooth. My Nexus 5 would dial, and as you expect the car remains connected and the audio and dialling occurs through the car system. With my Nexus 6P, the car talks to my phone, and then immediately cuts off the bluetooth, a bit like a failure to communicate, but the phone will then carry on calling, and only if I try to dial from my car, and if the person has answered does it then lock on and maintain the call via the car system.
I can not find anything in either settings to explain it.
So, anyone have any ideas crutually why the 6P fails me where the 5 worked.
I have the exact same issue. I have a Mazda CX-5.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
Would be the same system if yours is the current model too. Guessing it was fine on your previous phone too?
Yes, I think so. It is a 2016, so it is the latest system I suppose. I had a Samsung Galaxy S5 previously and it worked perfectly. This is my first Nexus, so I thought it was a Nexus thing at first, however it is really annoying. It is hard to explain because the bluetooth kinda works, it just has this thing that it drops and picks up again...
Bluetooth working fine with my 2013 kia forte. Maybe something to do with Marshmallow and Mazda Bluetooth system?
Yea, it is kind of hard to explain. Only found out today, so not been able to test it over and over, but seems that unless the other person answers, you have no idea it is dialling. It is like it (Mazda system) is being told it an not carry on. I once had the same issue (Nexus 5) when there was another phone option and it was waiting for a default to be set on the phone before it dials. It did not do it today, but I wonder if I make sure it is set in settings as the default right....
... nope, only app for calls is the inbuilt.
It seems like some people are having similar issues? --> http://forum.xda-developers.com/nexus-6p/help/bluetooth-phone-completely-borked-t3241196
I had the phone for a couple days and tried some things like upairing/re-pairing with no results. I discovered it when I called my wife, the call dropped (or the car did the call drop sound) but all of the sudden my wife answered. I tried calling different numbers and it's the same deal. I haven't tried receiving a call.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
And I have the same issue with a 2015 Honda Accord Hybrid. I don't have the issue with any of my other phones. Google Support doesn't know why it's happening.
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
AllyGraham said:
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
Click to expand...
Click to collapse
Nice find. I'll chime in in that thread. I hope Google can solve this soonish since it is kinda a major annoyance at the moment.

G6 H870 bluetooth call issue

I'm having troubles using my G6 (lineage 14.1 installed) with my car Bluetooth. Music plays fine but phonecalls are a nightmare, I can hear the person I call but he/she can barely hear me because he/she does hear a lot of noise (just like when you blow on the microphone). I'm going to test it with my friends cars as well; mine is a Mazda and is working perfectly with a old LG G3, few One+, few Samsung Galaxy and a Lumia.
Anyone else having the same issue? Any tips?
Thanks
How did it work with the stock O/S?
Cnstb said:
I'm having troubles using my G6 (lineage 14.1 installed) with my car Bluetooth. Music plays fine but phonecalls are a nightmare, I can hear the person I call but he/she can barely hear me because he/she does hear a lot of noise (just like when you blow on the microphone). I'm going to test it with my friends cars as well; mine is a Mazda and is working perfectly with a old LG G3, few One+, few Samsung Galaxy and a Lumia.
Anyone else having the same issue? Any tips?
Thanks
Click to expand...
Click to collapse
I.m pretty sure all the custom roms for H870 have calling over BT broken so far.
This is the only reason why I'm still on stock Oreo rom. I need my BT calling working.
Apparenttly it's a driver issue as US version of G6 doesn't have this problem on custom roms.
patruns said:
How did it work with the stock O/S?
Click to expand...
Click to collapse
Good question; honestly, I don't know. I just bought the phone last week, turned it on just to see it worked, did shut it down and installed Lineage.
-Arturo- said:
I.m pretty sure all the custom roms for H870 have calling over BT broken so far.
This is the only reason why I'm still on stock Oreo rom. I need my BT calling working.
Apparenttly it's a driver issue as US version of G6 doesn't have this problem on custom roms.
Click to expand...
Click to collapse
Damn, is there anything we/I can do to try help lineage developers fix this thing?
Cnstb said:
Good question; honestly, I don't know. I just bought the phone last week, turned it on just to see it worked, did shut it down and installed Lineage.
Damn, is there anything we/I can do to try help lineage developers fix this thing?
Click to expand...
Click to collapse
Head over to Aquarius rom thread as there are a few guys claiming the BT calling issues have been fixed.
https://forum.xda-developers.com/lg...ios-8-1-0-live-support-theming-t3808498/page3
Any working solution? I tried viper4android but It did not solve the issue.
I noticed many bluetooth options on rom menu settings, working somewhere gives good response?
Seems like car bluetooth phonecalls with my H870 running lineage 14.1 20181221 nightly do work on a brand new Kia Rio owned by a friend of mine. I'll give it another try with my cars as well and also few other friends cars and see if bt calls have been finally fixed or it's just the Kia the lucky one

Categories

Resources