having call problems with cm10.1

**talelorm** · 03-08-2013, 04:38 PM

Ever since the nightly of cm10.1 of February 20 to march 8. Every time I update my phone using the cm updater with clockworkmod bysk8 14.4.6

Well when I update once or twice when I call it goes through but no ringing I can't hear them and they can't hear me is it the noise suppression or what? When I do a full wipe and install the new update all is fine . I haven't tried manually using cwm to update the nightly
Please help

**MrGriffdude** · 03-08-2013, 09:22 PM

Originally Posted by talelorm

Ever since the nightly of cm10.1 of February 20 to march 8. Every time I update my phone using the cm updater with clockworkmod bysk8 14.4.6

Well when I update once or twice when I call it goes through but no ringing I can't hear them and they can't hear me is it the noise suppression or what? When I do a full wipe and install the new update all is fine . I haven't tried manually using cwm to update the nightly
Please help

Its a known issue a clean reflash works until a couple reboots and then the issue comes back. My suggestion is to use the last nightly that works for you (for example mine is 2/26) until an official fix is implemented.

Sent from my SAMSUNG-SGH-I727 using Android Central Forums

**talelorm** · 03-08-2013, 11:08 PM

So if I never let the battery die or reboot I should be ok ? Flashing an older nightly would work too

**MrGriffdude** · 03-08-2013, 11:27 PM

Originally Posted by talelorm

So if I never let the battery die or reboot I should be ok ? Flashing an older nightly would work too

Well it breaks during upgrades too.

Sent from my SAMSUNG-SGH-I727 using Android Central Forums

**DanoNH** · 03-10-2013, 12:12 PM

It's been fixed.

Look at and .

Should be in one of the next Nightlies.

Sent from somewhere in Galaxy S2...

**Jacques** · 03-10-2013, 03:48 PM

To add to what DanoNH said, it's the 3/9 CM build, but it doesn't include a commit in the system/core that causes a break in the call audio. I reverted back to the 2/26 build when this bug was first appearing, but when I have a moment, I'm going to flash roger_n's fix.