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....
Related
i have dell xcd 35 the viber app in the play store (market) is not working normal on the stock froyo. The app installs fine but after calling somebody the incoming voice stops after 30-40 seconds of call.
plzz help..
viber gave me similar problems when using stock rom and i switched to whatsapp same with my friends last time we used viber it did not give us any problems on gingerbread
i dont like whatsapp and plzz tell me how can i made viber made work on stock 2.2 as i have to give my set to service center in some days and cant install custom rom... plzz help.
Kannibalism said:
viber gave me similar problems when using stock rom and i switched to whatsapp same with my friends last time we used viber it did not give us any problems on gingerbread
Click to expand...
Click to collapse
i dont like whatsapp and plzz tell me how can i made viber made work on stock 2.2 as i have to give my set to service center in some days and cant install custom rom... plzz help.
when viber gave me similar problems i stopped using it i could not find a fix for it :/ but then i upgraded to 2.3.7 and it worked fine so the problem i think is with android 2.2 but like a said i am not 100% sure
Kannibalism said:
when viber gave me similar problems i stopped using it i could not find a fix for it :/ but then i upgraded to 2.3.7 and it worked fine so the problem i think is with android 2.2 but like a said i am not 100% sure
Click to expand...
Click to collapse
its not 2.2 it only works perfectly on cm
Viber
Hi,
This is a member of the Viber Development Team!
If you are running Viber on a customized ROM, it may result in side effects. At this stage, due to the large variety of customized ROMs available, we support only the basic ones, such as CM7 and MIUI.
Our recommendations to you would be to either uninstall and reinstall Viber , or to find the proper customization which works best with Viber..
If you have any question about Viber - please feel free to ask.
Thank you,
Viber Team
Viber Team said:
Hi,
This is a member of the Viber Development Team!
If you are running Viber on a customized ROM, it may result in side effects. At this stage, due to the large variety of customized ROMs available, we support only the basic ones, such as CM7 and MIUI.
Our recommendations to you would be to either uninstall and reinstall Viber , or to find the proper customization which works best with Viber..
If you have any question about Viber - please feel free to ask.
Thank you,
Viber Team
Click to expand...
Click to collapse
actually it doesn't work properly on stock rom
@saaransh9 -
What device and Android version are you using?
I see in your details that it says CM7.
@nitin kumar -
And you?
Viber Team said:
@saaransh9 -
What device and Android version are you using?
I see in your details that it says CM7.
@nitin kumar -
And you?
Click to expand...
Click to collapse
YEAH I USE CM7 AND IT RUNS WELL but the problem is with stock 2.2 as the OP said
I'm waiting for more information from the thread OP.
Is "dell xcd 35" the exact same thing as "ZTE Blade" ?
Yes. It's the same phone. Dell just rebranded it in India
Sent from my Supernatural Blade
Please note that Viber does not officially support your device yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/rqbZEw
We are continuously working to adapt Viber to more and more devices, and we hope to attend to the problems with your device soon. We apologize for the inconvenience.
However:
@nitin kumar -
I invite you to contact our support team and give them the details of this issue. You can open a ticket here: http://bit.ly/ukGVJ0
Thanks in advance
U know, my phone was a Gen1 and viber was working fine. After dell converted it to Gen2, then viber started giving issues
Sent from my Supernatural Blade
@viber team
i have used cm7 and other roms too and i am getting similar issue with all. that is when i call to some one its fine but after 20-30 sec i.am not getting voice of other person but he is getting mine... plzz sort out this issue..
Sent from my Blade using xda premium
@nitin kumar -
I have already answered to you.
Please see my post above (#13)
Viber Team said:
Please note that Viber does not officially support your device yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/rqbZEw
We are continuously working to adapt Viber to more and more devices, and we hope to attend to the problems with your device soon. We apologize for the inconvenience.
However:
@nitin kumar -
I invite you to contact our support team and give them the details of this issue. You can open a ticket here: http://bit.ly/ukGVJ0
Thanks in advance
Click to expand...
Click to collapse
Wow, I thought most of the companies are just lazy sloths. Btw, i-m facing terrible battery drain using it
Sent from my ZTE Blade using Tapatalk 2
k1ngkang said:
Wow, I thought most of the companies are just lazy sloths. Btw, i-m facing terrible battery drain using it
Sent from my ZTE Blade using Tapatalk 2
Click to expand...
Click to collapse
Well, we feel like it's our duty to find out users out there across the Web and provide direct support
About the battery drain issue - please make sure that Viber is the cause for the problem by isolating Viber (having no other apps running) on a device with stock ROM (custom ROMs may cause this problem).
We conduct strict testings in our labs with several devices and other than when making a call (when it is natural for the battery to be used), we did not come across any significant battery drain when Viber was simply running in the background. Furthermore, over the course of over 15 hours, on average the battery use was only 2%.
You can find additional information on tests performed by Viber users themselves, which show similar results, at:
http://whrl.pl/Rc0APn
Viber Team said:
Well, we feel like it's our duty to find out users out there across the Web and provide direct support
About the battery drain issue - please make sure that Viber is the cause for the problem by isolating Viber (having no other apps running) on a device with stock ROM (custom ROMs may cause this problem).
We conduct strict testings in our labs with several devices and other than when making a call (when it is natural for the battery to be used), we did not come across any significant battery drain when Viber was simply running in the background. Furthermore, over the course of over 15 hours, on average the battery use was only 2%.
You can find additional information on tests performed by Viber users themselves, which show similar results, at:
http://whrl.pl/Rc0APn
Click to expand...
Click to collapse
viber shows error msg "viber has crashed" on agreeker MIUI for blade know any possible reason... although Tango (another calling app like viber) is working fine.
aman.droid said:
viber shows error msg "viber has crashed" on agreeker MIUI for blade know any possible reason... although Tango (another calling app like viber) is working fine.
Click to expand...
Click to collapse
Oh god. I had the worst experience with ageeker's Miui. It was laggy as **** and good god Instagram and Viber were not working at all.
Viber devs have been since January been getting complaints from Miui community. The only thing I can recommend is that you switch to the most stable rom called FishandCrips and get QQLauncher for MIUI design. It is superior to other roms.
i cant install viber on my wildfire i had cm7 rom updated it to cm9 but still this problem
Not any answer ?
Sent from my Wildfire using xda app-developers app
Where's the problem ? When you start viber, it stops ?
no when installing
not when installing in progress >>> said that viber cannot be installed
Hi,
This is a member of the Viber R&D Team.
@nima.sharon - Unfortunately custom ROMs are not fully supported by Viber yet... :/
However, please try to download Viber akso from this link: http://bit.ly/xqfTBt
Let us know if the issue persists.
Please feel free to let us know your thoughts, questions and comments, we'd be happy to assist.
Thanks,
the Viber Team
Viber Team said:
Hi,
This is a member of the Viber R&D Team.
@nima.sharon - Unfortunately custom ROMs are not fully supported by Viber yet... :/
However, please try to download Viber akso from this link: http://bit.ly/xqfTBt
Let us know if the issue persists.
Please feel free to let us know your thoughts, questions and comments, we'd be happy to assist.
Thanks,
the Viber Team
Click to expand...
Click to collapse
Viber must support Custom Roms
We (Viber) can guarantee that Viber is fully compatible with phones that we thoroughly tested in our labs. The list of devices we've tested is found in our HelpDesk: http://bit.ly/Hm5k9pWe've tested these devices with their original Stock ROM (one that comes from your factory, with no substantial modifications to the OS itself). This, by the way, is the case of the huge majority of Android phones across the world today - in other words, phones who have been "ROM'ed" are a tiny percent of all Android phones out there.
* And by the way, it's not true that Viber simply "does not work" on Custom ROMs. On the contrary - it actually works with them most of the time. However, sometimes some Custom ROMs collide with *some* feature of Viber, and when this happens unfortunately there is not much we can do to help, since we cannot afford to adapt Viber to all Custom ROMs out there, and all of their versions. This requires development, testing, etc, and we simply don't have these resources. We usually recommend those users to contact the ROM developer for further support - they may be able to resolve this issue.
nima.sharon said:
i cant install viber on my wildfire i had cm7 rom updated it to cm9 but still this problem
Click to expand...
Click to collapse
I can confirm that Viber is running perfectly on CM 7.2 Stable.
yeah when i used cm7.2 also viber worked fully without any bug or issue:good::laugh:
I've been using viber for past many months. Works nomal to send msgs n pictures but calling never worked on wildfire.recently I installed ics roms n viber never installed on my device on ics
Sent from my Sony Tablet S using Tapatalk 2
@mani16985 -
Please note that Viber does not officially support your device yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/Hm5k9p
We are continuously working to adapt Viber to more and more devices, and we hope to attend to the problems with your device soon. We apologize for the inconvenience.
Yup i know that but still i LOVE your software. Thanks for keeping it free for all
mani16985 said:
I've been using viber for past many months. Works nomal to send msgs n pictures but calling never worked on wildfire.recently I installed ics roms n viber never installed on my device on ics Sent from my Sony Tablet S using Tapatalk 2
Click to expand...
Click to collapse
Are you using nightly ?Try that on stable release.
optimusodd said:
Are you using nightly ?Try that on stable release.
Click to expand...
Click to collapse
It worked on all roms like froyo based n gingerbread. Only txt n photo sharing. Calling never worked
On all ics roms I tried, it never installed.
Sent from my HTC Wildfire using xda premium
mani16985 said:
It worked on all roms like froyo based n gingerbread. Only txt n photo sharing. Calling never worked
On all ics roms I tried, it never installed.
Click to expand...
Click to collapse
That's weird.It's working for me.
Viber Team said:
@mani16985 -
Please note that Viber does not officially support your device yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices:
We are continuously working to adapt Viber to more and more devices, and we hope to attend to the problems with your device soon. We apologize for the inconvenience.
Click to expand...
Click to collapse
I'm using Galaxy Note II 7102 and it doesn't support. Do you have any plan to support this model?
Thanks
Hi there,
As some of you have already noticed, we have released a new version of Viber - 2.3.0 !
What's new?
- Use your own ringtones from Android as your Viber ringtones!
- Include cool emoticons in your Viber text message.
- Reply to cellular (regular) SMS using Viber.
- Share Stickers with your Viber contacts.
- Add a custom location to your Viber texts.
- Many other enchancements and improvements.
So, make sure you download the latest version!
Please feel free to let us know your thoughts, questions and comments, we'd be happy to hear from you.
Viber Team
@GeorgeMike -
We are continuously working to adapt Viber to more and more devices, and we hope to attend to the problems with your device soon. We apologize for the inconvenience.
Have you tried the new update?
Hey Guys,
I've been reading of a forum to this problem I've been having with any Cyannogenmod after 10.1-20130226. There seems to be this problem where when I make or receive a call, I can't hear anything but the other party can hear me talking. I've kept updating to newer and newer versions only to figure out all of them have this problem, and that the last working one is the 10.1-20130226 version. Is there something the devs messed up on?
This is of course for the SGH II T989.
And here's the link with other people with the same problem:
This is on the forum for cyannogen mod. copy and paste it into the forums.
topic/69560-101-20130302-nightly-phone-calling-is-broken/
If anyone knows a solution to this, that will be great, otherwise I have to stick with this version till the newest update fixes that problem.
mikloish said:
Hey Guys,
I've been reading of a forum to this problem I've been having with any Cyannogenmod after 10.1-20130226. There seems to be this problem where when I make or receive a call, I can't hear anything but the other party can hear me talking. I've kept updating to newer and newer versions only to figure out all of them have this problem, and that the last working one is the 10.1-20130226 version. Is there something the devs messed up on?
This is of course for the SGH II T989.
And here's the link with other people with the same problem:
This is on the forum for cyannogen mod. copy and paste it into the forums.
topic/69560-101-20130302-nightly-phone-calling-is-broken/
If anyone knows a solution to this, that will be great, otherwise I have to stick with this version till the newest update fixes that problem.
Click to expand...
Click to collapse
There's also about 10 threads here too. Same fix for everyone. Flash a different kernel, or a different ROM. Cerux kernel fixed it for me. It's in the development forum.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hello guys,
I'm experiencing a weird problem on custom roms (except for the oxygen based custom roms) when having a call while my earphones are plugged in.
Indeed, both mics, from the earphones and from the phone itself, are fonctionning. This is pretty annoying as usually my phone is in my pocket when making that kind of call so i hear the friction noise of the phone against my pocket.
Does anyone else experienced it or have a solution ?
Thanks in advance for helping me guys, have a nice day !
Pikoon said:
Hello guys,
I'm experiencing a weird problem on custom roms (except for the oxygen based custom roms) when having a call while my earphones are plugged in.
Indeed, both mics, from the earphones and from the phone itself, are fonctionning. This is pretty annoying as usually my phone is in my pocket when making that kind of call so i hear the friction noise of the phone against my pocket.
Does anyone else experienced it or have a solution ?
Thanks in advance for helping me guys, have a nice day !
Click to expand...
Click to collapse
Yes I am facing the exact same issue on 8.1 liquid remix ROM
This issue arise when I flashed 5.1.1 firmware file to fix headphone sound issue while playing YouTube and other videos
Fix that issue correctly but now the other issue arise which you described above...
Still finding the solution
If you get 1 please share
sauaditi said:
Yes I am facing the exact same issue on 8.1 liquid remix ROM
This issue arise when I flashed 5.1.1 firmware file to fix headphone sound issue while playing YouTube and other videos
Fix that issue correctly but now the other issue arise which you described above...
Still finding the solution
If you get 1 please share
Click to expand...
Click to collapse
I used to install liquid remix, franken-rom and many others but they all have that problem. The only custom roms that don't have it are theone5tos and Zoe rom which I'm currently running as they are based on oxygen os...
I guess we need for a fix to come out...
Anyway, thanks for your answer, at least I know I'm not the only one facing this problem
sauaditi said:
Yes I am facing the exact same issue on 8.1 liquid remix ROM
This issue arise when I flashed 5.1.1 firmware file to fix headphone sound issue while playing YouTube and other videos
Fix that issue correctly but now the other issue arise which you described above...
Still finding the solution
If you get 1 please share
Click to expand...
Click to collapse
Acoording to a comment in AOSPExtended rom thread the headphone issue is fixed.
I haven't tried it yet, I'll try it tomorrow. And then give a feedback if it's really gone or not.
We'll see!
Pikoon said:
Acoording to a comment in AOSPExtended rom thread the headphone issue is fixed.
I haven't tried it yet, I'll try it tomorrow. And then give a feedback if it's really gone or not.
We'll see!
Click to expand...
Click to collapse
OK so I've just tested the rom I was talking about and sadly for me, the issue is still there...
But according to this post in the AOSPExtended thread , the issue is gone. So I guess it depends on phones...
Anyway I hope one day it will be good for everybody...
A quick read over this thread says one thing to me: Update your firmware to the latest 5.1.2.
Edit: Grammar is important.
pinnekeshaar said:
A quick read over this thread says one thing to me: Update your firmware to the latest 5.1.2.
Edit: Grammar is important.
Click to expand...
Click to collapse
Unfortunately each time I wrote those messages I was on the latest firmware available (5.1.1 when I started this thread and 5.1.2 now) so I guess this not the problem...
But still, thanks for according interest to my problem !
By the way I'm now on Treskmod rom wich is based on Omnirom and I don't encounter this problem ! If it can help other people with the same issue...
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.