Hey folks, I installed Lineage OS 16 on my HTC U11 recently (unofficial version as the phone isn't officially supported) and had the known issue that there were no sounds in voice calls (I couldn't hear anyone and nobody could hear me). I successfully fixed the issue by editing two lines in the build.prop ("persist.vendor.audio.fluence.voicecall=false" and "ro.vendor.audio.sdk.fluencetype=none") as suggested by some threads in this forum.
Lately while my phone was connected to my car via bluetooth and I got a call (speakerphone), I had the same issue as mentioned above, no sound at all. After that I disconnected my phone from my car, deactivated bluetooth and called back, but the problem persisted and there was still no sound. Then I restarted my phone, called again and everything worked fine.
This happened a few times now and only when I called somebody or received a call while the phone was connected via bluetooth to an external device. It's very annoying that I can't use my phone via speakerphone anymore and that I have to restart the phone everytime after I received a call while I sat in the car.
I hope anyone has a solution for this and hopefully one that doesn't include the reinstallation of Lineage OS
Thanks in advance.
Anyone?
push
push
Someone gave me a solution here https://forum.xda-developers.com/u1...oice-calls-speakerphone-t3994433#post80829083
Related
Hello,
after I've updated my Xperia ZL to Lollipop (first 5.0 and now 5.1) I had an issue with bluetooth headsets. When I receive a call and I'm connected to headset, I push answer button on the headset but the phone still ring in the headset 3-4 sec more. Another strange thing is when I push the answer I get for one short moment a sound from the caller and after it still ring in the headset but not on the phone. Even if I answer from the screen with the bluetooth connected it happend the same.
I noticed that sometimes it goes normal but other times go wrong like I said before. Another noticed is that not all the BT do the same. On my BT's car is OK, in my house I use 2 BT headsets, and both do the same. Before updating to Lollipop with the same headsets was OK, never had this problem.
First update to 5.0 I made OTA but second I made trought PC with PC companion and was a fresh install from 0. The problem persist. I decided that is a bug in Lollipop version for my ZL.
It's very annoing this problem.
What can I do to fix this?
Hello everyone,
My LG G3 is giving me a hard time, when I connect a headset, its microphone isn't working or it does but it's barley audible compared to the device's own mic.
The headphones part is working as usual and when the headset is connected sounds goes only through them like it should.
I've started using this headset a few days ago and it worked like a charm but then it's suddenly stopped working like it had been.
Fortunately I have another LG G3 on hand, so first I checked the headset with it and it works perfect.
So then I've replaced the 3.5 audio jack from the other G3 into my own to figure out if it is causing the problem and it is NOT,
since I got no improvement in my own phone and I also put MY jack in the other G3 and it worked there flawlessly with two different headsets.
I've been trying to record into / monitor with two different apps (lg audio recorder and another another one).
I've killed all apps running in the background. I've restarted numerous times, ran CCleaner to clear cache memories and whatever.
At one point a few days ago, maybe it was just before it started (and this might be a clue) the "plugged device" icon or "headset" icon on the notification bar stayed even after I've disconnected the headset and I think I needed to restart the phone but if i'm not wrong the headset kept working after that.
I was trying to find any kind of audio service to restart or anything like that but I didn't find any, I just killed them all to see if it helps.
I've also tried using "soundabout" app to try to force the audio path to the headset and played with some settings but to no avail (I disabled soundabout service after that attempt).
Right now I see no other option but a hard reset and I'm pretty sure it will solve the issue. but I hate going through backing up and restoring everything. and even so, who said this issue won't happen again? I've tried to search for an answer but found nothing like my problem on the web.
I just read something old from 2013 that mentions a bug in android audio. not sure it's related. something about "AudioPolicyMangerBase" (it seems I can't post links yet) from an app that had a switch to switch between headset mode or phone mode. but in any case it's no longer maintained. again, not sure it's related.
Update: Now I got no sound with two different headsets on the SECOND LG G3 as well. it seems messing with it around, plugging and unplugging messes with it's software somehow and maybe it locks the audio route in a way that it's can't work.
Any way to reset all audio ins/outs routes in the device?
I'll appreciate your help. Thanks a lot!
Roy.
Hello All,
I have had a strange problem with bluetooth calling on my phone that has popped up in the last few weeks. If I attempt to make or receive a call using any sort of bluetooth headset, or the hands free radio in my car, I am unable to hear the other person, but they can hear me. This issue only is related to calls. I can use my phone for streaming bluetooth music, to both my car and various speakers. Another thing about this that is strange is that I can listen to music with my Jaybird Bluebuds X, but if it were a call I would not hear anything. I have tried using another phone with my car's hands free system, and that phone works correctly. This is what leads me to believe that this is a phone issue.
About my phone. I have the Verizon Note 4, and have been running Jasmine ROM v6 since late May or early June maybe. My phone has worked fine until sometime in the beginning of August. Last night I decided to update my phone to Jasmine ROM v7, thinking that this is somehow a software issue (I had already tried wiping cache, deleting bluetooth devices etc.). I was able to update, but the issue is still there. I am now lost.
Has anyone experienced this before? This seems strange to me, that music works correctly, but call audio does not. I assume that the bluetooth hardware is working correctly, or else nothing would work and that the issue is somehow related to the software bluetooth profiles. Any ideas?
TL;DR; Bluetooth call audio on my end does not work, but music does. I'm not sure why.
Hey there,
I'm currently running a OP3 with the OmniDragon 8.1 ROM and previously the ResurrectionRemix ROM. However, I do not believe this issue to be a ROM issue so that's why I'm posting here instead.
I've recently been having some issues with bluetooth and was hoping someone could help. I can connect my phone to my cars handsfree system perfectly fine and it works correctly. I can play music via Spotify and any other music player fine.
However, as soon as I make or receive a phone call I'm left where the person can't hear me, and I can't hear them. I can't even hear the ringing tone when phoning someone. However, as soon as I turn it from bluetooth back to the phone or just regular speaker, it works fine.
This previously was not the case when I was running Nougat.
But as soon as I upgraded to 8.1 this issue started happening.
I don't think it has anything to do with the ROM and is actually something to do with perhaps OP3 Firmware/Modem or something similar.
Car hands free works fine with other phones like an iPhone, so that's out of the question.
I've attached a catlog to this post from when this issue was happening in the car, so hopefully someone can narrow it down for me.
Any help is appreciated!
Actually many roms have been having issues with BT calls. It's due to some of the changes in the telephony package.
Hello, did you manage to find any Oreo rom that fixed this issue for you? Would appreciate any tips.
I too have had similar issues with Oreo and OnePlus 3. Using an handsfree Jabra Freeway and the microphone often does not work when I answer or phone someone during a drive. Which is extremely annoying and dangerous.
I had hopes that with the release of some alpha Android Pie roms, these BT issues would be fixed. But the issue seem to persist, at least for my device.
My only fix was to go back to nougat. The most stable rom i've found is the unofficial lineage 14.1 by sultan. This have been my daily driver for awhile now and seems to work fine.
Hi, I tried to find something about the issue, which I have, but nowhere is the same problem, so I tried to create the new thread...
I have the company phone Samsung Galaxy A5 2017 (SM-A520F) with the stock ROM (now with Oreo) and I got the new company car with build-it bluetooth (Volkswagen). I tried to pair the phone with the car and everything looks good. A few first calls were without any trouble. But now happens very ofter (almost in 99% attempts), that I have connected phone to car and
- somebody call me
- I call to somebody (via touch on contact in infotainment in car)
- I call to somebody (via touch on phone application on mobile phone)
the call is starting and in the same time is the BT connection interupted. And there are two possibilities:
- BT on SGA5 is still turned on, but disconnected from car
- BT on SGA5 is turned off (somehow)
You can say, there is trouble with your car, but I tested is with the other mobile phone (Nexus 5X) and everything works properly.
That's why I think, that the trouble isn't in car, but in the phone. And of course I did the wipe of whole phone and after that I tried it again, but with the same results.
Does somebody the same/similar experience? Is there some solution? Because no possibility to call in car is horrible for me and I can only get a new phone in the summer (it is too long time without call from car).
Thank you in advance