Hi guys,
I had issues with viber and mobile voip ( voip application ) on the original sense rom when i got the phone new last time. Because of that and the advantages of custom roms, i went to CM based roms. It was great. Thing is i missed the sense look and feel....Long story short, i now have Renovate Rom with the kernel supplied with it. I am facing the same problems again. People on the other end cant hear me, and call connection is poor. A friend of mine said its due to sense 4+. Please do help me solve this, as i love the sense, just that this is whats putting me off...Thanks guys.
Hi,
This is Viber's rep. I'm here to help.
It sounds like the typical Custom ROM issue - some custom ROMs alter the microphone definitions of your phone, causing Viber not to recognize the phone's microphone properly. That is the reason that Viber cannot transmit your sound to the other side. We discussed this issue in detail with our users in this thread on XDA Forums: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
Please note that in that thread, a workaround was suggested *by a user* that seemed to have solved the problem for Galaxy S+S2 users.
Let us know if the issue persists.
Thanks,
Viber
Viber Team said:
Hi,
This is Viber's rep. I'm here to help.
It sounds like the typical Custom ROM issue - some custom ROMs alter the microphone definitions of your phone, causing Viber not to recognize the phone's microphone properly. That is the reason that Viber cannot transmit your sound to the other side. We discussed this issue in detail with our users in this thread on XDA Forums: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
Please note that in that thread, a workaround was suggested *by a user* that seemed to have solved the problem for Galaxy S+S2 users.
Let us know if the issue persists.
Thanks,
Viber
Click to expand...
Click to collapse
Hi, and thanks for the link...checked it out....well, i was having the same problem earlier with the original htc rom when i bought the phone...thats the reason i was soo eager to change to custom roms....Its working excellently on cm based roms, so is my mobile voip....My friend also said, he had issues with bad internet/wifi when he updated his old one x to sense 4+, and everything was fine on sense 4.0......The link u suggested says to change some stuff which it says for samsung galaxy.....It would be really great if you would be able to point me to the right direction on this, as i believe its not just because its a custom rom as i had the exact same issues with original HTC rom....Thank you very much...Hope to hear a solution from u soon...
Hi again,
I apologize for my late response.
Unfortunately there is not much we (Viber) can do to help, as official representatives
The fact that the problem was solved on CM, but is now present again on the new ROM you're using, suggests that it is indeed a problem with the ROM (and not Viber). We recommend that you contact people on that thread, or in other threads here on XDA, who might have had similar issues. At this stage we (Viber) will not be able to suggest a solution for this problem, caused by the Custom ROM
Viber Team said:
Hi again,
I apologize for my late response.
Unfortunately there is not much we (Viber) can do to help, as official representatives
The fact that the problem was solved on CM, but is now present again on the new ROM you're using, suggests that it is indeed a problem with the ROM (and not Viber). We recommend that you contact people on that thread, or in other threads here on XDA, who might have had similar issues. At this stage we (Viber) will not be able to suggest a solution for this problem, caused by the Custom ROM
Click to expand...
Click to collapse
Its alright...Thank you very much...i hope someone else on standard htc rom can help, or maybe if sense 5 comes out for one x, it would be solved.....I love viber on CM10.1.....like a regular call..best off all, free.....support you guys all the way....
Hello. I recently (today) installed Lineage OS 14.1 for my A3 2016.
I have a really big microphone problem. When e.g recording voice it has a very awkward robot noise, which is really annoying. But it isnt there in calls. Is there like any Magisk Module to fix this or?
lordjbs said:
Hello. I recently (today) installed Lineage OS 14.1 for my A3 2016. I have a really big microphone problem. When e.g recording voice it has a very awkward robot noise, which is really annoying. But it isnt there in calls. Is there like any Magisk Module to fix this or?
Click to expand...
Click to collapse
I don't have this device but, seeing the Official LineageOS, unfortunately, being discontinued, the following threads reflect the Unofficial LineageOS 14.1 & 14.2 for your device and maybe this issue has been resolved on one of them.
https://forum.xda-developers.com/showthread.php?t=3632682
https://forum.xda-developers.com/showthread.php?t=3532574
You can always ask about it on one of them regarding this issue and if it was resolved.
If you've got questions regarding Magisk, the following is the General Q&A thread for it.
https://forum.xda-developers.com/showthread.php?t=3432382
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I have installed Lineage OS 14.1 android 7.1.1 custom rom for my Samsung Galaxy E5 SM-E500H running android 5.1.1.
There are many things that are not good with this software like when I want to unlock the phone after turning the screen on, the screen freezes and starts doing many things that I don't. It means it's like that I am clicking on the screen but actually I am not. And an other thing is that the phone doesn't read the SIM card contacts. The phone can read the SIM, make and receive calls and messages. But the contacts on the SIM don't appear in the contacts list. And also one other thing, sometimes the screen does not respond to touches.
Does anyone have solutions for these problems?
And thanks in advance.
unknownnnn said:
I have installed Lineage OS 14.1 android 7.1.1 custom rom for my Samsung Galaxy E5 SM-E500H running android 5.1.1. There are many things that are not good with this software like when I want to unlock the phone after turning the screen on, the screen freezes and starts doing many things that I don't. It means it's like that I am clicking on the screen but actually I am not. And an other thing is that the phone doesn't read the SIM card contacts...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following thread for the Unofficial LineageOS for this device (since there's no Official release).
https://forum.xda-developers.com/showthread.php?t=3585887
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
your best bet is to post this question within the following thread for the Unofficial LineageOS for this device (since there's no Official release).
https://forum.xda-developers.com/showthread.php?t=3585887
Click to expand...
Click to collapse
It's like doing nothing. Still no reply.
unknownnnn said:
It's like doing nothing. Still no reply.
Click to expand...
Click to collapse
I, personally, give posts 7-10 days for a response before taking other avenues.
I know that it seems like a long time, depending on the urgency but, I've been off the XDA Grid for a week or so and I always felt that this time frame was a fair one.
You can always edit your post and add a callout to the OP Developer.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Firstly, Thank you XDA community for helping me with my new first android device.
Secondly, I would love to thanks the developer who worked on really awesome custom ROMS for the devices, they worked really flawless.
Now my Question is: Is it only me or anyone else having problem with tmobile variant device, that have no audio and mic on phone app and in-call.
It only happens with custom ROMS. I did search for solution, before posting this thread.
I came up with two zip files under the name audio fix for tmobile on 7.0 OS. But those didn’t work. instead one of the zip caused boot loop. SO, that being said, is there an ANGEL!!!! to help me with this problem. I really want to use custom ROMs or atleast cleanest / lightest STOCKED ROM.... thank you in advance for reading and responding to my thread.
Ruuh said:
Firstly, Thank you XDA community for helping me with my new first android device.
Secondly, I would love to thanks the developer who worked on really awesome custom ROMS for the devices, they worked really flawless.
Now my Question is: Is it only me or anyone else having problem with tmobile variant device, that have no audio and mic on phone app and in-call.
It only happens with custom ROMS. I did search for solution, before posting this thread.
I came up with two zip files under the name audio fix for tmobile on 7.0 OS. But those didn’t work. instead one of the zip caused boot loop. SO, that being said, is there an ANGEL!!!! to help me with this problem. I really want to use custom ROMs or atleast cleanest / lightest STOCKED ROM.... thank you in advance for reading and responding to my thread.
Click to expand...
Click to collapse
Your not the only one having this issue. Apparently the call libraries (or something like that) are different for T-Mobile variants of the s6 edge plus. I ran into the same issue when I first got this phone. What you need to do is look for custom ROMs who offer explicit support for SM-G928T. I started a thread on the issue a few months ago. On there I put a list of ROMs that have working call audio with no add ons. Feel free to check it out if you'd like.
Custom 7.0 ROM for the Galaxy s6 edge Plus!
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
Rehvix said:
Your not the only one having this issue. Apparently the call libraries (or something like that) are different for T-Mobile variants of the s6 edge plus. I ran into the same issue when I first got this phone. What you need to do is look for custom ROMs who offer explicit support for SM-G928T. I started a thread on the issue a few months ago. On there I put a list of ROMs that have working call audio with no add ons. Feel free to check it out if you'd like.
Custom 7.0 ROM for the Galaxy s6 edge Plus!
Click to expand...
Click to collapse
P.S. We can also run ROMs build for the TMO Note 5 (SM-N920T)
When placing or receiving a voice call (LOS 14.1, Samsung Galaxy S6, current build) the other party hears their own voice echo back in approximately 1.5 to 2 seconds. It depends on what is being used on the S6 to make the call. If the built-in microphone and speakers are used, the echo is very problematic. It is less noticable with a Bluetooth headset, and it is completely not there if one uses a wired headset (in this case a pair of Samsung wired earplugs). With the stock ROM, this does not occur. Perhaps there is a set of build.prop entries or other yet-to-be-documented settings to address the noise cancellation issue ? An otherwise rather excellent ROM, it would be a shame to not be able to use it if it required earplugs for voice calling. An extensive search through the other Galaxy S6 forum postings and the forum specific to the ROM reveals nothing of particular value, but maybe something was overlooked. Suggestions, anyone?
nezlek said:
When placing or receiving a voice call (LOS 14.1, Samsung Galaxy S6, current build).......
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3738447
I did come across the following thread that may be helpful for what you are looking for.
https://forum.xda-developers.com/showthread.php?t=3795558
If all else fails, and you don't receive any support from the above threads, then your next best bet is to post this question within the following Q&A thread that's specific to your device and variants as well.
https://forum.xda-developers.com/showthread.php?t=3110220
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Thanks
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3738447
I did come across the following thread that may be helpful for what you are looking for.
https://forum.xda-developers.com/showthread.php?t=3795558
If all else fails, and you don't receive any support from the above threads, then your next best bet is to post this question within the following Q&A thread that's specific to your device and variants as well.
https://forum.xda-developers.com/showthread.php?t=3110220
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Thanks again for the interesting and useful suggestion(s). I thought I had exhausted the possible S6 support locations on XDA, so it a always a pleasant surprise to find even more. Unfortunately, no news was to be found there, either. I suspect that some "out of the box thinking" might be required to address this one, which is why I have floated this inquiry beyond what might be thought of as the usual places. Lots of other device owners (e.g. One Plus, etc..) seem to have reported echo problems on voice calls using LOS, with a variety of suggestions about how to address the problem. I can't believe that everyone uses headphones (which do make the problem go away) for all of their voice calling, so somewhere there is an answer. What I have found most peculiar is that MY device has no echo issues. It is the device on the other end of the connection that is exhibiting the echo, regardless of who makes the call. As the saying goes: "curiouser and curiouser..."
nezlek said:
Thanks again for the interesting and useful suggestion(s). I thought I had exhausted the possible S6 support locations on XDA, so it a always a pleasant surprise to find even more. Unfortunately, no news was to be found there, either. I suspect that some "out of the box thinking" might be required to address this one, which is why I have floated this inquiry beyond what might be thought of as the usual places. Lots of other device owners (e.g. One Plus, etc..) seem to have reported echo problems on voice calls using LOS, with a variety of suggestions about how to address the problem. I can't believe that everyone uses headphones (which do make the problem go away) for all of their voice calling, so somewhere there is an answer. What I have found most peculiar is that MY device has no echo issues. It is the device on the other end of the connection that is exhibiting the echo, regardless of who makes the call. As the saying goes: "curiouser and curiouser..."
Click to expand...
Click to collapse
Same here. I still wondering what causing the problem on my Note 5 (RR&Lineage). Have you found any solution other than using a wired headset to receive and make call?
I'm still thinking about this answer from https://forum.xda-developers.com/general/help/echo-problem-callers-phone-t3550550: "It seems to me that your mic is picking up the sound that your speaker is emitting and then feeding back to their phone. If you are on stock, try turning the in call volume down so that your speaker isn't so loud."
And I'll try to reduce the in-call volume and will report it later.
Echo
Same here with Samsung A15 and Lineage 16 custom ROM
Caller hear a strange echo
I tried change in build prop the value setting of fluence.speaker = false with no succes
Anyone found a solution yet?
I'm having the same problem.
Same problem.
So evidently this is a source problem propagated all over the all kind of ROM based on this project
Brignoud said:
So evidently this is a source problem propagated all over the all kind of ROM based on this project
Click to expand...
Click to collapse
Where can I find more info about that?
Same thing for me on my SM-G920F using 15.1.2019022-UNOFFICIAL-zerofltexx.
Call if fine for me, but other person can hear themselves with a couple of seconds delay. Doesnt matter who starts the call or what method for me. Did the same using bluetooth setup in car.
Brignoud said:
So evidently this is a source problem propagated all over the all kind of ROM based on this project
Click to expand...
Click to collapse
Exactly my thoughts, because in have 3 different devices on Lineage 15.1 and 16 that all exhibit this behavior.
Seems like it would be an easy and IMPORTANT fix to the base/source. Just correcting the issue somewhere in the base code should correct it for everyone...
KeepingItCuttingEdge said:
Exactly my thoughts, because in have 3 different devices on Lineage 15.1 and 16 that all exhibit this behavior.
Seems like it would be an easy and IMPORTANT fix to the base/source. Just correcting the issue somewhere in the base code should correct it for everyone...
Click to expand...
Click to collapse
Yeah, this is affecting me on three different devices all running 16.0. Sad, I had to go back to the stock firmware because I cannot talk to loved ones.
Hello, i have the same problem with Samsung Galaxy S7 edge (SM-G935)
I found a video on youtube "How to fix mic and speaker in custom ROMs ?"
Use BUILDPROP EDITOR to edit and add "ro.qc.sdk.audio.fluencetype=none"
but don't work for me
Tonio0 said:
Hello, i have the same problem with Samsung Galaxy S7 edge (SM-G935)
I found a video on youtube "How to fix mic and speaker in custom ROMs ?"
Use BUILDPROP EDITOR to edit and add "ro.qc.sdk.audio.fluencetype=none"
but don't work for me
Click to expand...
Click to collapse
YouTube? Really? I guess the download link for your ROM was from YouTube also. Without telling you, who actually built it? Thats the person you shouting ask for a fix.
kurtn said:
YouTube? Really? I guess the download link for your ROM was from YouTube also. Without telling you, who actually built it? Thats the person you shouting ask for a fix.
Click to expand...
Click to collapse
Hi kurtn, i just try to fix a problem, I sought "ro.qc.sdk.audio.fluencetype" and i found a video that explain how to edit the prop .. i don't understand your reply ?
Tonio0 said:
Hi kurtn, i just try to fix a problem, I sought "ro.qc.sdk.audio.fluencetype" and i found a video that explain how to edit the prop .. i don't understand your reply ?
Click to expand...
Click to collapse
Do you have a custom ROM insalled? What exactly?
kurtn said:
Do you have a custom ROM insalled? What exactly?
Click to expand...
Click to collapse
Yes, lineage OS 16.0 + magisk.
The echo is only with the speaker on, the caller hears himself speak
Tonio0 said:
Yes, lineage OS 16.0 + magisk.
The echo is only with the speaker on, the caller hears himself speak
Click to expand...
Click to collapse
Maybe you should post there https://forum.xda-developers.com/s7-edge/development/beta-lineageos-16-0-s7-edge-hero2lte-t3842464
Or downgrade to 15.1
Possible solution? Confirmation needed
Hello, I'm new as a poster here.
I had the problem with my Galaxy S4 VE (jfvelte). I had ResurrectionRemix (Marshmallow) for years and found LineageOS 16 for my device, so I installed it successfully and all seemed to be better, Camera is much more stable, better battery drain. After two days I noticed the problem with the echo for caller on two different devices (Modem I9515XXU1BPK4).
I didn't find any solution, only an open issue on GitHUB.
I downgraded to 15.1, same Problem.
I downgraded once more to 14.1. Problem fixed. All fine, but I didn't want to stay with this old sticky nougat stuff .
From the audio fix patch from sombree i knew that the problem is somewhere into the two files "audio_platform_info.xml" and "mixer_path.xml", but his fix is for 14.1, and not for 16.
So I tried to reinstall 16, and replaced the two files with the ones from 14.1 (the path have been modified from /system/etc to /system/vendor/etc).
NOW I HAVE 16 WITH NO ECHO PROBLEM. Other sound devices seem to work (Tested Speaker, Bluetooth and headphones/headset).
Being a Windows developer and no Android/Linux expert, I have no real idea from what I've done, so I wanted someone (maybe a real expert) to tell me:
Is my solution working (seems to be so)?
Why didn't someone had the Idea before?
Why have they (LineageOS devs) broken it?
Maybe I could help, and please fix it directly in ROM.
I've build a flashable patch with the "ZIPme" app. Should I upload it?
DarthNAL said:
Hello, I'm new as a poster here.
I had the problem with my Galaxy S4 VE (jfvelte). I had ResurrectionRemix (Marshmallow) for years and found LineageOS 16 for my device, so I installed it successfully and all seemed to be better, Camera is much more stable, better battery drain. After two days I noticed the problem with the echo for caller on two different devices (Modem I9515XXU1BPK4).
I didn't find any solution, only an open issue on GitHUB.
I downgraded to 15.1, same Problem.
I downgraded once more to 14.1. Problem fixed. All fine, but I didn't want to stay with this old sticky nougat stuff .
From the audio fix patch from sombree i knew that the problem is somewhere into the two files "audio_platform_info.xml" and "mixer_path.xml", but his fix is for 14.1, and not for 16.
So I tried to reinstall 16, and replaced the two files with the ones from 14.1 (the path have been modified from /system/etc to /system/vendor/etc).
NOW I HAVE 16 WITH NO ECHO PROBLEM. Other sound devices seem to work (Tested Speaker, Bluetooth and headphones/headset).
Being a Windows developer and no Android/Linux expert, I have no real idea from what I've done, so I wanted someone (maybe a real expert) to tell me:
Is my solution working (seems to be so)?
Why didn't someone had the Idea before?
Why have they (LineageOS devs) broken it?
Maybe I could help, and please fix it directly in ROM.
I've build a flashable patch with the "ZIPme" app. Should I upload it?
Click to expand...
Click to collapse
Could you please post there?
https://forum.xda-developers.com/galaxy-s4/unified-development/official-lineageos-16-0-t3954912
I think that issues are device specific.