Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
rm83855 said:
Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Konsstantine34 said:
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Click to expand...
Click to collapse
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
rm83855 said:
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
Click to expand...
Click to collapse
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
rm83855 said:
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Click to expand...
Click to collapse
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
rm83855 said:
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
Click to expand...
Click to collapse
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Konsstantine34 said:
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Click to expand...
Click to collapse
Yeah its a strange one, have you made any progression towards a fix? I can't live with a phone that can't make calls lol
rm83855 said:
Yeah its a strange one, have you made any professional towards a fix? I can't live with a phone that can't make calls lol
Click to expand...
Click to collapse
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Konsstantine34 said:
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Click to expand...
Click to collapse
Did your issue just solve itself? i replaced the mixer_path with no luck
rm83855 said:
Did your issue just solve itself? i replaced the mixer_path with no luck
Click to expand...
Click to collapse
When I flash a Tmobile based rom, I use this way to fix it and it works ok. Present days Im using Note 5 rom which is n920G.. based. Havent replaced anything but no problem with calls. If you havent had that issue before the custom rom or something you flash which causes this issue, its probably a software issue. Otherwise Im gonna think your mic has broken down..
Same problem here. Did you manage to fix it by any chance?
Related
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
I have you seen s you. Have you found a solution yet? When I use a bluetooth headset it works Fine
You need to update your radio
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I was having this issue as well, and that worked perfectly! Thanks man!
*system error* said:
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I tried that and that app and messed with different settings and it didn't work. I'm gonna try updating the radio and see what that does.
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
That worked actually. Thanks!
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
Huge thanks for this one. I had been searching google for a solution to this one for a week or so now. I will have to say, the most annoying thing I've had to deal with in quite some time. I should have just come to XDA first like an adult.
T-mobile s4
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Try the T-Mobile S4 Forum
ptsite said:
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Click to expand...
Click to collapse
Sorry, but I don't know if this applies to the Samsung S4. I would try posting over in the T-Mobile Galaxy S4 forum.
Hi all,
Had this problem for about a week now.
When I make an out going call, I hear the other side for 3 seconds and then the speaker cuts out. They can hear me fine.
The only way I found to fix this is to reboot the phone, it then works for a while before the problem come back.
I'm running a completely stock rom on 4.4.2 I haven't even rooted it yet (in case it has to go back).
I've had the G2 a few months and this started just over a week ago.
Any thoughts? Root and custom rom, or send it back and try a new unit??
Thanks.
Bro em having same problem did you got any solution for this ??
ratedadorable said:
Bro em having same problem did you got any solution for this ??
Click to expand...
Click to collapse
Are you running the stock kernel?
tangnt said:
Are you running the stock kernel?
Click to expand...
Click to collapse
i was using cloudy kernal, then tried dorimax can you give me the link to stock kernal and
my problem is that everybody hears a distortion from my side during call but i can hear them fine, n after that call all the system sounds goes down no sound from any app media it happens mostly. :crying:
Hello everyone,
When I try to answer a call the ringtone volume will spike for a very short of time. The spike will make the volume peak at it highest. Anyone has this problem?
very annoying
Anyone
I've bought the note 4 just 5 days ago and I've just recently noticed this particular sound issue too. I'm wondering if it's just a software bug... It's so weird that just you and me are having this issue that I'm really thinking that it could be a hardware issue...
My friend also has the same problem. He use N910c as well
Yathani said:
My friend also has the same problem. He use N910c as well
Click to expand...
Click to collapse
Do you still have this problem? Do you think that it's software related or hardware related? Does flashing a newer rom stones this issue?
davi_ssilva said:
Do you still have this problem? Do you think that it's software related or hardware related? Does flashing a newer rom stones this issue?
Click to expand...
Click to collapse
I would love to have answer as well, but i'm in the same boat. However, I tried to set the same ringtone as an alarm with max volume and when i try to stop/snooze it doesn't do that. I even tried the MOD that is on the app section which change the volume on the note 4. It did increase my speaker volume but i didn't do anything in fixing the issue. I also tried to install an app called "Disable Increasing Ring" which remove the low volume on the first ring but it didn't help either.
I tried to post this on another forum looking for help and one guy said "Check the setting that maximizes the volume on ringing." I don't know what does that mean.
Yathani
Yathani said:
I would love to have answer as well, but i'm in the same boat. However, I tried to set the same ringtone as an alarm with max volume and when i try to stop/snooze it doesn't do that. I even tried the MOD that is on the app section which change the volume on the note 4. It did increase my speaker volume but i didn't do anything in fixing the issue. I also tried to install an app called "Disable Increasing Ring" which remove the low volume on the first ring but it didn't help either.
I tried to post this on another forum looking for help and one guy said "Check the setting that maximizes the volume on ringing." I don't know what does that mean.
Yathani
Click to expand...
Click to collapse
I tried the "Disable Increasing Ring" app too, because I initially tought that it was a bug of the increasing ringtone feature that is present since Android v.4.3... But it didn't work. I've also flashed another rom and the issue persisted.
I don't know... What drives me crazy is that some people have this problem but the majority just don't! Of it is a firmware problem, it should happen with everyone that has the same rom...
I'm also worried because this spike in the ringtone volume may damage the loudspeaker through time...
To be honest, I'm just about to return my phone!!!
Same here. 910c version.
davi_ssilva said:
I tried the "Disable Increasing Ring" app too, because I initially tought that it was a bug of the increasing ringtone feature that is present since Android v.4.3... But it didn't work. I've also flashed another rom and the issue persisted.
I don't know... What drives me crazy is that some people have this problem but the majority just don't! Of it is a firmware problem, it should happen with everyone that has the same rom...
I'm also worried because this spike in the ringtone volume may damage the loudspeaker through time...
To be honest, I'm just about to return my phone!!!
Click to expand...
Click to collapse
What rom did you try on your Note 4? I think I will wait until the SC810 Note 4.
Yathani said:
What rom did you try on your Note 4? I think I will wait until the SC810 Note 4.
Click to expand...
Click to collapse
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
davi_ssilva said:
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
Click to expand...
Click to collapse
SO you installed another Samsung rom? that won't help to identify the issue.
Yathani said:
SO you installed another Samsung rom? that won't help to identify the issue.
Click to expand...
Click to collapse
Why not??? The point is that people running the same Samsung rom that I have simply don't have this problem. The fact is that every note 4 unit should be able to run a stock rom and not present this particular bug. I mean, it must be a hardware issue because my method excluded all the particular changes in the sistem that could be caused by apps or some configuration options... So, after excluding all those factors, if two identical models are running the same identical roms, the only reason that one unit has a bug and the other don't is that they aren't really identical, i.e. because one of them has a hardware problem/difference.
The other point is that if I want to use my warranty rights, I must not have root access nor use a custom rom, because I don't wat to trigger my flash counter or my knox counter...
So it makes absolutely no sense that I must loose my warranty and use a coustom rom to get rid of a problem that doesn't even exists in the vast majority of note 4 units that are able to run the stock rom without presenting this issue.
davi_ssilva said:
I've tried 02 official stock roms: ZTO (Brazil - International Unlocked) and ZTA (Brazil - Claro Branded).
I did the Factory Reset and wiped the Cache Patition using the Stock Recovery, and then flashed these roms using Odin 3.09
Then I started the phone, didn't logged in my google account nor in my samsung account, and so I did'd download nor intalled any app. I didn't make any changes on the phone's configuration menu.
Then, with the phone like this, I've called myself using my girlfriend's phone and, unfortunately, when I swiped to answer the call the damn sound bug was still present!!!
Since I know many other users that run these roms and don't have this problem, I'm assuming that it's a hardware issue particular to my note 4 unit.
So I have no other choice: I'll return my phone as soon as possible!
Click to expand...
Click to collapse
davi_ssilva said:
Why not??? The point is that people running the same Samsung rom that I have simply don't have this problem. The fact is that every note 4 unit should be able to run a stock rom and not present this particular bug. I mean, it must be a hardware issue because my method excluded all the particular changes in the sistem that could be caused by apps or some configuration options... So, after excluding all those factors, if two identical models are running the same identical roms, the only reason that one unit has a bug and the other don't is that they aren't really identical, i.e. because one of them has a hardware problem/difference.
The other point is that if I want to use my warranty rights, I must not have root access nor use a custom rom, because I don't wat to trigger my flash counter or my knox counter...
So it makes absolutely no sense that I must loose my warranty and use a coustom rom to get rid of a problem that doesn't even exists in the vast majority of note 4 units that are able to run the stock rom without presenting this issue.
Click to expand...
Click to collapse
I feel like people have this problem but they don't pay attention to it as much as we do. But let me know please how it goes with you. If a replacement worked with you or not.
Thanks
Well, it bother me, but I believe Samsung will fix it. Let wait for lollipop update.
https://play.google.com/store/apps/...+ring&pcampaignid=APPU_BSSmVKC9CsTZoASSpIHACQ
ohbreeeezy said:
https://play.google.com/store/apps/...+ring&pcampaignid=APPU_BSSmVKC9CsTZoASSpIHACQ
Click to expand...
Click to collapse
We're already using this app, but it didn't solve our problem.
Same issue on a SM-N910C in Bulgaria. Phone taken from operator Telenor. I hope that there is a solution.
Sent from my Galaxy Note 4
Any update ?
solution
Hey guys, fb messenger causes such problems.
Just disable it and you'll be fine.
Tried that after reading... I disabled the app and uninstalled the updates... same sh*t...
Sent from my Galaxy Note 4
So I'm on a ported s6 rom (aurora) for note 3 (n900w8).
I've been noticing this problem, where a phone call would come, but no vibration with it even though the mode was set as vibration mode.
I have missed many phone calls because of this.
At first I thought I simply failed to notice the vibration, but yesterday I witnessed it not vibrating during the incoming phone call. Screen comes on, incoming call screen pops, but no vibration.
This problem persisted ever since lollipop (I think). Had the same problem in the previous roms (other note 3 lollipop roms).
Oh and it happens when the phone is in idle. If a phone call comes while i'm using the phone, it vibrates just fine.
So I was suspecting it might be blocked wakelock or alarm issue. But then again, the only app i'm using for that purpose is Servicely (by chainfire), and I only have a couple apps checked (ie. facebook, google play services, keep, mega, supersu...etc).
TW 5.0.2.
No xposed framework installed.
Rooted/deodexed.
Anyone experiencing the same problem? Any fixes? Help plz. This is starting to bother me a lot...
anybody at all ?
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
ithehappy said:
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Click to expand...
Click to collapse
celderic said:
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
hm... The last rom I was on was Note 3 LP 5.0 rom built on official note 3 firmware (Vision X from Tmobile Note 3 xda forum), and I still saw that happening.
so yea it wasnt a problem of being ported rom or not...
and I dont want to go back to stock odex rom..
Thx for the replies anyways guys
IEAL said:
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Click to expand...
Click to collapse
and no I dont have them on
Hi, i'm encountering a problem with the microphone of my one plus 2 that occured right after installing this custom ROM :
http://forum.xda-developers.com/oneplus-2/development/6-0-x-cyanogenmod-13-oneplus-2-t3292436
What happens is that the mic doesn't work when making a normal call, but works just fine with audio notes/skype/whatsapp etc.
I'm thinking about 3g/4g problems since the mic works with wi-fi services as i see. Does anyone have the same problem? It's preatty annoying...
FUN FACT: my girlfriend called me 4 times today and couldn't answer because of this... needless to say she got angry at me :crying: sooo it's urgent :silly:
On OxygenOS I had Cortana and when I was using Google now microphone and others apps which requires microphone I didn't work but for calls it worked for me and I don't know if there is Cortana is CyanogenMod 13 but if you disable/uninstall it I think i'll work (for me it worked)
scratur said:
Hi, i'm encountering a problem with the microphone of my one plus 2 that occured right after installing this custom ROM :
http://forum.xda-developers.com/oneplus-2/development/6-0-x-cyanogenmod-13-oneplus-2-t3292436
What happens is that the mic doesn't work when making a normal call, but works just fine with audio notes/skype/whatsapp etc.
I'm thinking about 3g/4g problems since the mic works with wi-fi services as i see. Does anyone have the same problem? It's preatty annoying...
FUN FACT: my girlfriend called me 4 times today and couldn't answer because of this... needless to say she got angry at me :crying: sooo it's urgent :silly:
Click to expand...
Click to collapse
Enable root, go to File Manager, /system/build.prop
change true to false in "persist.audio.fluence.voicecall"
credits to the person who shared,.
If it doesn't work, revert to Oxygen, clean flash again. Take backup though!
krishna442 said:
Enable root, go to File Manager, /system/build.prop
change true to false in "persist.audio.fluence.voicecall"
credits to the person who shared,.
If it doesn't work, revert to Oxygen, clean flash again. Take backup though!
Click to expand...
Click to collapse
i'm having same problem. So i edited TO ro.qc.sdk.audio.fluencetype=none, FROM ro.qc.sdk.audio.fluencetype=fluence
Now i'm having very low voice of opposite party during the call.
Any fix to this?
Thanks