complaints from caller that they hear echo during calls in samsung galaxy s4 GT-I9500...please fix this issue in new update
I have cyanogemmod 12.1-20151104-nightly rom.
NO echo is heard when i call using internet calling apps like whatsapp or messenger.
Hello,
To better assist you, your thread will be moved to your device Q&A forum in the link below.
http://forum.xda-developers.com/galaxy-s4/help
The experts there may be able to help. Good luck.
Droidriven said:
Hello,
To better assist you, your thread will be moved to your device Q&A forum in the link below.
http://forum.xda-developers.com/galaxy-s4/help
The experts there may be able to help. Good luck.
Click to expand...
Click to collapse
Where's the thread? And what's the solution?
What do you mean where is the thread? You're posting in it, this is your thread.
---------- Post added at 05:50 PM ---------- Previous post was at 05:48 PM ----------
Your device forum is where you will find your solution.
Look around in that forum, post questions, other users there that know your device will have the answers you need.
The link below takes you to the main forum for your device, on that page you will find all the forums for your device on that page, you will find the most help in the Q&A thread there, the Android Development and the Original Android Development forums are where you will find ROMs, firmware, kernels, recoveries and other mods for your device.
http://forum.xda-developers.com/galaxy-s4
Look through all those subforums listed on that page, post your question in whichever threads you think apply to you.
Just another thread in top of google search list with no solution, but advice to go look somewhere else. Still didn't find the fix after searching for days. Nothing to see here, move along.
Moto G 2013, CyanogenMod 13
This worked for my Galaxy S4 I9505 with CM13:
Modify the following settings in build.prop to read:
--ro.qc.sdk.audio.fluencetype=fluence
--persist.audio.fluence.speaker=false.
Whenever I speak with someone in a call, they hear their voice back as an echo. This is with the normal speaker against your ear (not tried it with the speakerphone).
My build.prop file doesn't have the persist.audio.fluence.speaker=false line. I just altered the other line and it fixed the issue! The build.prop file can be found in the root\system folder
I would post the URL to properly credit the person who posted this fix, but as a new forum user I'm not allowed to post URLs yet :-/
I already wrote explanation and solutions to fix this problem here, wrote really long post, but this stupid forum script cleared the form, because it logged me out in meantime. TL;DR:
For me it was a HARDWARE PROBLEM.
Couldn't figure it out, because I first changed broken screen and immediately installed CyanogenMod. Why would the screen be responsible for an echo? Ridiculous, I thought. Especially when echo was present only when using PHONE app, but not HANGOUTS app. I was sure Cyanogen was bugged.
After longer time I discovered seller actually sold me Screen + frame, that was missing a small rubber, which after assembly to rest of phone, covered the mic. So all the problems with echo was caused by lack of small rubber.
When you use android phone app and GSM, sound quality is usually low, also people set volume to max. This causes whole phone body to vibrate from the top (ear speaker) to bottom (mic), causing the echo that only other person can hear.
Hangouts app didn't cause this echo, because quality of voice is better and it's quieter, thus doesn't make phone vibrate.
Other solutions I found:
- take off the case if you got one, some cover second mic used for sound cancellation
- disable TalkBack app (by Google)
- disable/enable sound cancellation in phone settings (I don't have that option on my phone)
And here is very useful thread:
https://www.ifixit.com/Answers/View/81829/Why+do+callers+hear+an+echo+during+phone+calls
Here how to make your own sound isolation, if you're missing part like I was (fortunately I kept my broken screen for 2 months and just took rubber from it):
https://youtu.be/FkcxzmCPFWw
I've had this echo problem on my i9500 ever since I installed CyanogenMod 12.
Today I finally decided to install GearCM custom ROM (based on CyanogenMod 13), and I'm very happy with it so far. Just tried talking to someone and they didn't hear themselves anymore. And of course, Android 6 is a nice bonus.
Related
I thought I'd start my own post, since some incorrect information has been going around. The libaudio.so file that has been linked to is only to fix the wonk on the Nexus One and has nothing to do with the Gingerbread call delay. It is hardware specific, and may cause issues in other phones. If you don't have a Nexus One, you probably shouldn't install this file. It is already in the CM nightlies, and will be in 7.0.4 when it is released.
I have submitted a patch to gerrit that reduces the call delay in my testing. I've posted a test build in the Nexus One nightlies thread, and fitsnugly has cherry-picked it for his Nexus One and G2x builds. Several others have said that it is working for them.
The patch is here:
http://review.cyanogenmod.com/#change,5420
Thanks for your patch! This is great work.
My change has been merged into Cyanogenmod.
thanks for your brilliant findings!
Thanks jyxent for working on this! This has been the most annoying bug (to me) that I've had to deal with.
I am correct, in my understanding of the comments at review.cyanogenmod.com, that what you did essentially restored the code to how it was in Froyo? Just curious.
Not exactly. Google changed PhoneUtils to use CallManager to set the audio mode, instead of setting it to MODE_IN_CALL directly. There is some delay before a call becomes active once it is answered. CallManager checks this state when setting the audio mode, and was not setting MODE_IN_CALL, since it thought the call was still ringing. I just added a check to make sure that MODE_IN_CALL is set if a call was just answered and the call is still considered ringing.
This makes the behavior similar to froyo, but it wasn't just restoring the original code.
I think it works when answering from the handset but not when you answer using the earphone..is this possible????
got a problem today using this patch
phone was ringing: went to answer and slided...
in the meantime an SMS arrived (when I was sliding to answer)
result: the phone call hanged & audio output was set to loudspeaker + phone app freezed (black screen)
the other party could not hear me
hmm sorry for posting a dumbass question but
I need to download the callmanager.java right?
How should I install it, can I just replace the existing file using e.g. Super Manager (maybe making a copy beforehand)?
And if so, where is this file stored? I did a search on my phone but no results
thx
B
berre said:
hmm sorry for posting a dumbass question but
I need to download the callmanager.java right?
How should I install it, can I just replace the existing file using e.g. Super Manager (maybe making a copy beforehand)?
And if so, where is this file stored? I did a search on my phone but no results
thx
B
Click to expand...
Click to collapse
It isn't possible to just replace a file to get this fix. The ROM has to be compiled with the added patch.
This patch is included in the CyanogenMod nightly builds, as well as the 7.1 release candidate. As for other ROMs, it might be best to just ask in their respective threads.
I contacted spearoid via PM to respond to a post of his on the development forum, because at that time, I didn't have enough posts to post in the dev forum... Anyhow, his issue was with Google Navigation. He would switch to another app, say the messaging app (because I don't actually remember his example, and I can't find the post from him on this issue), and then switch back to the Google Navigation app and it was as if he hadn't launched it just a few seconds ago. He had to wait for GPS the lock and then enter the navigation information again... Yeah, I agree, what a PITA (pain in the arse).
I sent him the PM to check out my post on fixing the launcher respawning as I thought the issue was similiar. Well, it is, however, I can't figure out what line to enter to replace the ro.HOME_APP_ADJ... Dang! I then went back to zepplinrox OP here in XDA (http://forum.xda-developers.com/showthread.php?t=991276). I paid special attention to the The Nitty Gritty... For Geeks! and the history sections where he talks about the default minfree values. Bingo!
Using AMM (Auto Memory Manager), I looked at my memory settings, but I had already done this, so I don't know what the defaults are. Using AMM, I used the advanced settings in the menu and manually put in 6, 12, 45, 60, 80, 90. If you are wondering, "Why so high?", check out the thread by androcheck, rather than reinvent the wheel, and post the majority of his post here, I'll just link to it. http://forum.xda-developers.com/showthread.php?t=622666.
I have found that when I need to switch to an app for a few moments, and come back to the one I was just running (I did try this with Google Navigation and it works), it seems to work. Now, the only flaw I found was if I stay on the second app for a longer period of time, say 2 minutes or so, Google Navigation was killed. Then, why are you sending a text message while driving?!?! (Just kidding.)
Hope this helps. When I find information, I prefer to share it and help others!
Ciao!
I have an issue that is making me crazy. Starting about 1 month ago, my N7 plays a very annoying "tune" for about 1-2 minutes precisely at 12:35 AM every day.
Some specifics:
- volume cannot be controlled or muted
- the "tune" that is played is not one of the normal choices. It is kind of crude sounding (like MIDI).
- does not provide any notification of any kind or show up as a running app
- does not appear to be associated with clock or calendar
- the only way to stop it is to power off
Steps I have taken to try to kill this thing (leaving out the obvious)
- "soft" factory reset/restore from N7 Settings menu - fail
- "Hard" facory reset using power/volume controls. Did not do a restore.. Only logged onto wireless and into my Google account . - fail
- complete wipe/reflash using adb/fastboot/nakasi image from Google developer page instructions. - fail
I'm a complete Android noob, but not a software/hardware noob. This defies logic to me. I found reference to a very similar problem on another forum, but the post was never answered. I have several other Android devices and none have this issue. I'm convinced that this is something malicious. Where is this thing hiding that it can survive a reflash? Please help, I'm beginning to think my N7 is haunted.
Bump for help
Sorry to bump this but it appears that the views have stopped and so far no replies. As noted in my original post I have seen this issue reported elsewhere but not solved. I even tried loading Cyanogenmod and it's still there! I realize that asking for help on you first post is asking a lot, but I really could use some help/suggestions. Is there somewhere in the file system I should look for the code that is running this? Are there monitoring tools I could use to identify the process that is running? Are there log files somewhere I could look at?
Besides being really annoying, it's hard to feel secure when something like this keeps coming back after the device has supposedly been wiped multiple times. If I can't solve it, it's probably going to get beaten to a pulp with a sledgehammer! Thanks for any suggestions.
gdbbcmi said:
I have an issue that is making me crazy. Starting about 1 month ago, my N7 plays a very annoying "tune" for about 1-2 minutes precisely at 12:35 AM every day.
Some specifics:
- volume cannot be controlled or muted
- the "tune" that is played is not one of the normal choices. It is kind of crude sounding (like MIDI).
- does not provide any notification of any kind or show up as a running app
- does not appear to be associated with clock or calendar
- the only way to stop it is to power off
Steps I have taken to try to kill this thing (leaving out the obvious)
- "soft" factory reset/restore from N7 Settings menu - fail
- "Hard" facory reset using power/volume controls. Did not do a restore.. Only logged onto wireless and into my Google account . - fail
- complete wipe/reflash using adb/fastboot/nakasi image from Google developer page instructions. - fail
I'm a complete Android noob, but not a software/hardware noob. This defies logic to me. I found reference to a very similar problem on another forum, but the post was never answered. I have several other Android devices and none have this issue. I'm convinced that this is something malicious. Where is this thing hiding that it can survive a reflash? Please help, I'm beginning to think my N7 is haunted.
Click to expand...
Click to collapse
Solved!
This is solved. I'd like to say I know exactly what worked, but apparently after the umpteenth wipe/re-flash, the poltergeist got bored and moved on. Thanks for thinking about it.
gdbbcmi said:
Sorry to bump this but it appears that the views have stopped and so far no replies. As noted in my original post I have seen this issue reported elsewhere but not solved. I even tried loading Cyanogenmod and it's still there! I realize that asking for help on you first post is asking a lot, but I really could use some help/suggestions. Is there somewhere in the file system I should look for the code that is running this? Are there monitoring tools I could use to identify the process that is running? Are there log files somewhere I could look at?
Besides being really annoying, it's hard to feel secure when something like this keeps coming back after the device has supposedly been wiped multiple times. If I can't solve it, it's probably going to get beaten to a pulp with a sledgehammer! Thanks for any suggestions.
Click to expand...
Click to collapse
Hello,
I'm experiencing an issue with the Loop VR headset and my OnePlus Two.
When I use t the two halves of the images doesn't converge and hence it is almost unusable.
I've tried it with my OnePlus One and the LoopVR is perfectly working.
Comparing the two images (see attachments) I can see that on the OPO the image is split in two perfectly symmetric circles while on the OPT the two halves are not symmetric.
I'm using CM 13 nightlies.
Does anyone have any idea how to fix it?
Screenshots:
OPO: http://i64.tinypic.com/9gii3d.jpg
OPT: http://i64.tinypic.com/2njae7c.jpg
Thank you!
EDIT: Sorry, this should probably be in the "ONEPLUS 2 Q&A, HELP & TROUBLESHOOTING" section. Please move it there if it is the case
yes, I have the same problem.
I tried to get the engineer code * # 808 # in the dialer (seen here https://forums.oneplus.net/threads/re-calibrating-accelerometer-magnetometer-gyroscope-sensor.405894/"]https://forums.oneplus.net/threads/re-calibrating-accelerometer-magnetometer-gyroscope-sensor.405894/ ) but cyanogen does not recognize!
I decided to reinstall oxygen os to enter the engineer code, I then have to recalibrate the sensors but when I pass under cyanogen, settings are lost and her again the problem.
I tried with remix os but I do not think because this rom is based on cyanogen.
should we know how to recalibrate the sensors in cyanogen.
ps: sorry for my english, this is the first time I post in xda simply to say you're not the only one to have this problem
EDIT : with remix os, the sensors is not good. The same with cyanogen 13. BUT with the paranoid aospa, IT'S GOOD.
Hello shousky,
thank you for your reply!
Glad to hear I'm not alone
Then I will try to fill a bug report to CyanogenMod when I have time.
Does anyone know how to ricalibrate the sensors?
Hello,
could you please move this to the "ONEPLUS 2 Q&A, HELP & TROUBLESHOOTING" section?
Hello,
a quick update.
I have tried the Google Exploration app and it allows you to chose another cardboard type than the standard. Using this one the experience is much better but the alignment is still not perfect.
I would like to try generate the correct profile but the dedicated site (https://vr.google.com/cardboard/viewerprofilegenerator/) doesn't work for me. After opening the link on the smartphone I have only a blank page.
Has anyone been able to generate a cardboard profile using the cardboard website?
Thank you,
Daniele
Well, hello everyone, as I don't have that many posts. I cannot create a new thread in the Development Section. So yeah, sorry about that.
But I decided to create this thread to make some people's life easier when it comes to find this fix. So, here it is!
Edit this line in the Build.prop file (better with Root Explorer) and then, reboot the device:
persist.audio.handset.mic.type=digital --> replace digital with analog
Hope you have fixed everything! I'll be here to respond to any comment or issues you may have. Theoretically you should not have problems, but no one knows. If I don't answer quickly, sorry, I have a life and I'm most of my time busy.
Have a nice one!
FYI - this isn't something that would be for the Development Fora - it's therefore fine here in General
PabloMSDN said:
Edit this line in the Build.prop file (better with Root Explorer) and then, reboot the device:
persist.audio.handset.mic.type=digital --> replace digital with analog
Hope you have fixed everything! I'll be here to respond to any comment or issues you may have. Theoretically you should not have problems, but no one knows. If I don't answer quickly, sorry, I have a life and I'm most of my time busy.
Have a nice one!
Click to expand...
Click to collapse
I did this. Video recording noise is fix. But im unable to switch to loudspeaker.
Switch it back to digital, loudspeaker work fine. Do you have any solution for this?
Sent from my Moto X using Tapatalk
hey, snapchat won't record videos frontal neither rear camera, what to do, CM13, Moto x