What controls the voice / sound settings when making a call over apps like Facebook messenger?
Currently i am running the emotion rom v16.1 and calls over messenger work great. I switched to the noble rom,which runs great... but I was unable to use messenger to make calls. When I made a call,the call "dialed out" then connected and the recipient was able to hear me but I could not hear them. It worked for a short period of time on speaker but stopped when the screen timed out and I was unable to regain it. When I hit the speaker button you could hear the other end for a split second then gone again. I even tried using earphones and had the same results... split second then gone.
I am running the emotion 6.0.1 rom, v3b of Lou's data fix and stock kernel .
Is there a specific file to alter... change... etc?
Related
My phone wont ring though, BIZARRE, this is not to do with the rom though as i think it was happening with schaps, really really strange.
Any ideas, I just get a phone icon where the signal strength bar is showing handset. No callerid flashing up, not even an option to accept the incoming call. I go to phone options and test the ring tone and it plays just fine.
maybe i should reflash the radio, on 1.50 at the mo which i recently flashed to downgrade from 1.51, any ideas?
maybe i miss something totally obvious.
bumppppp? anyone?
same happening to mine on ultra ultra lite re-furbished
i had to flash another rom, then it worked. when i flashed back to same rom it didnt work again. the problem started after i added some cabs and did my regular tweaks. even with the fresh install of the same rom after flashing another rom it still didnt work.. i even changed radios
i'm on ultra lite, and it seems nice. So you saying i should flash another rom then come back to ultra lite?
Ok,
I just reflashed schaps, then flashed ultra lite.
I STILL have this wierd problem, what's going on?
Is my fone knackered? Not much good if it don't ring!
the rom has been discontinued and he is fixing it
known bug.....wait until new relase
shame it's a nice ROM, nice un' quick. fixed yet ?
same here..
I noticed that no sound was coming out of the phone when i did a soft reset and the Schap's Rom boot up with the animation + sound didnt sound. Also my speaker phone does not work. Basically and audible sound does not work!!!! i tried flashing it with dutty's rom, still same problem.. any ideas?
Hope this helps in resolving this issue!
Hi. I've run into this issue myself too. Here's my environment:
Cooked ROM via Pandora's Kitchen 7.1 with 3.61 OS
Using Dutty's Touch Dialer (2G) option in BuildOS
Everything was fine with the ringer for a whole week. I then decided to be a bit adventurous and went to look for a 3g dialer because the Touch one is only 2G. I then settled for Schen's 3G dialer 2.0 and followed his instructions in installing it (install OEMSign2007cert.cab first, then the dialer, which was the one with the dialer directory option). I didn't install any colored background cabs as provided by his package.
When I tested the dialer (outgoing portion), it seemed fine. I couldn't test the 3G option because we don't have 3G here yet. The problem began when I received my first call.
I was able to hear the incoming call beep through my BT headset, but that was the only indicator of an incoming call, in addition to the phone icon above the signal meter in the top bar signifying an incoming phone call. Besides that, there were no other indicator such as a pop-up window showing incoming caller's info, phone ringing, or even the vibrate function. I have my phone set to vibrate and ring with the Ringer-Vision.wma as the default ring tone.
I tested the vibrate and ring setting in the phone configuration panel and both the vibration function and ring tone worked. I tried several configurations such as vibrate only, ring only, etc, in addition to other various ring tones of different format (wma, mid, wav). All resulted in success in the phone configuration panel, but in failure when an incoming call came in.
To test the phone function, I used a land line, a cellular line, and SkypeOut. All three resulted in the same failure observed above.
Given that the only thing changed after that week was the 3G dialer, I proceeded to remove it and reboot. It reverted back to the Touch 2G dialer. When the phone rebooted, I retried the above tests and all resulted in the pop-up dialog with incoming caller information (plus the two softkey functions), vibration function, and the proper ringtone.
With the above results, would it help you guys in further diagnosing and fixing this problem? We are slated to have 3G within the next few months and I would like to be able to use this function.
Thanks!
Edit update: One other thing is that I tested the above both with and without my BT headset on.
Quakie
I do understand what you are talking about how you tested out the ringers in the phone options menu.. but for me any type of sound does not work, i ran tests there no sound, speaker phone does not work, MP3 do not sound. The sound only works through a head set. And when im on a call i could hear the other person and vise versa. So the problem is the speaker just went out after a couple of days of having Schap's rom. I tired flashing another rom a couple of days after. No luck. Any ideas?
-thanks
I posted this question on a CM 11 Nightly forum with little success and was hoping to find a solution in this general forum. I am on CM 11 d2lte and have sound issues with my speaker when running my voice-mail. I historically would long press #1 on my dialer and access my messages that way, but no when I do that I get the "no messages" voice. I have left myself messages as a test to see if it works and it doesn't.
Here's what happens:
Get a message, go to v-mail app, press play, message starts out fine, but at the end of the message, then sounds turns into a very loud, scratchy, distorted static sound that cannot be turned off or turned down. When the sound stops on it own after about 7-10 seconds, i am not able to access the next message, cannot replay the same message, cannot do anything with the app. I am forced to reboot my system in order to get the next message and then I have to reboot after listening to the same garble...message after message.
1. I see others have had this issue
2. I have seen whacky solutions to this like disabling sms features
3. Does anyone have a real solution to this?
I have tried other Vmail apps and they all create the same sound in the speaker when checking v-mails, which tells me it is a communications issue with the vmail app and the speaker. Thoughts?
I don't necessarily care for a v-mail app...I'd like to be able to get my messages by long pressing #1...anyone?
Solved
TheQuicken said:
I posted this question on a CM 11 Nightly forum with little success and was hoping to find a solution in this general forum. I am on CM 11 d2lte and have sound issues with my speaker when running my voice-mail. I historically would long press #1 on my dialer and access my messages that way, but no when I do that I get the "no messages" voice. I have left myself messages as a test to see if it works and it doesn't.
Here's what happens:
Get a message, go to v-mail app, press play, message starts out fine, but at the end of the message, then sounds turns into a very loud, scratchy, distorted static sound that cannot be turned off or turned down. When the sound stops on it own after about 7-10 seconds, i am not able to access the next message, cannot replay the same message, cannot do anything with the app. I am forced to reboot my system in order to get the next message and then I have to reboot after listening to the same garble...message after message.
1. I see others have had this issue
2. I have seen whacky solutions to this like disabling sms features
3. Does anyone have a real solution to this?
I have tried other Vmail apps and they all create the same sound in the speaker when checking v-mails, which tells me it is a communications issue with the vmail app and the speaker. Thoughts?
I don't necessarily care for a v-mail app...I'd like to be able to get my messages by long pressing #1...anyone?
Click to expand...
Click to collapse
I had handcent and got rid of it and now using stock CM sms. No more bad speaker sounds.
I'm currently using an LG G3 Vs985 on Sky Dragon 5.0
I'm also using T-mobile on the LG G3
I use my phone for work a lot and the most annoying thing is happening. While I am using my bluetooth headset and talking on a call, if somebody tries to call me and my screen is telling to either accept or deny the incoming call, my bluetooth speaker drops to handset volume. I have to deny the incoming call, then quickly tap to turn off bluetooth and bluetooth again to get the call back to my bluetooth.
While already on a a call if somebody is talking to me while an incoming call comes in, I miss an entire sentance or two before i can do all of the above to get the audio back to bluetooth.
Is this a wrong setting I have on the phone or simply a bug with either Lollipop or Skydraggon?
"Edit" I got so annoyed I went to my wired headphones and I noticed the issue is not happening on my headphones. I didn't expect to happen but i wanted to note that the audio does not drop to handset speaker while using wired headset.
I appreciate the help.
I wanted to update the post that either it was a phone reboot or possibly of me flashing the Skydragon 4.2 kernal to the phone that fixed the issue. So far as of right now the audio is not dropping when talking or listening on an active call with another incoming call requesting to be accepted or denied.
Edit: The issue has returned. This is goofy !! lol
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
Hi,
I just got a OnePlus 7T HD1907 for my wife that I'm setting up. I've got the bootloader unlocked and LineageOS 18.1 20211121 installed (with latest open_gapps and Magisk). Everything works except for a problem during phone calls and other interactive voice type calls.
Here are the symptoms:
When I have an incoming or outgoing phone call, or a Skype call or Signal call, the person on the other end hears a squealing noise. I can hear the person on the other end normally, but they just hear this screech that goes on and on for the duration of the call, and cannot hear anything coming through the
If I change to speakerphone mode during the call, the sound of the screeching changes on the other end but still is definitely there.
When I use a bluetooth headset for the calls instead, the problem does not occur.
When I record audio using a sound recorder app, the recorded audio does not have the screech in it.
Any suggestions?
Thanks,
Elliot
Go back to stock or try another rom
Found https://gitlab.com/LineageOS/issues/android/-/issues/3752 and
https://www.reddit.com/r/LineageOS/comments/on3u7q
One suggestion on the reddit thread was to go from T-Mobile stock -> Global stock -> LineageOS. I went directly from T-Mobile stock to LineageOS.
I just tried going to global stock (problem gone) and then back to LineageOS and the problem seems gone for good.