Closed GoogleCodeExporter closed 8 years ago
Happened again today. Here are the logs. The event was around 9:13.
I was updating some apps when the phone rang. At the second call (around 9:14)
all went OK.
I have updated to 7.2.0 RC0a before the calls.
PS: I have a custom ring tone for that caller.
Original comment by justc...@gmail.com
on 23 Feb 2012 at 7:51
Attachments:
Issue 755 has been merged into this issue.
Original comment by kabal...@gmail.com
on 27 Mar 2012 at 12:58
Thanks for the logs. Unfortunately, I can't find anything going wrong there...
I'll repeat here what I posted at #755 so it's more visible:
As I said elsewhere, I'm not able to reproduce this issue, which is rather
unfortunate.
If this issue would be specific to 7.2 RC builds, then there would be an
obvious suspect - the updated libaudio.so that enables call recording.
But if the issue appears already in 7.1.5, then it has to be caused by
something else...
Anyway, as a first take on this issue, I attach an update package for
OpenRecovery that will revert the libaudio.
Please let me know if it makes any difference.
I can imagine other possible causes of this issue, so lets test them one after
another :) .
Just one additional question for now: does it happen mainly for some particular
contacts? Especially the ones that are using some specific ringtone?
Original comment by kabal...@gmail.com
on 27 Mar 2012 at 8:51
Attachments:
It happened with other contacts also. I'll install the downgrade of libaudio
and see if this repeats.
I am suspecting the call recording feature (actually, an initialization in that
library).
Original comment by justc...@gmail.com
on 27 Mar 2012 at 8:58
Issue 747 has been merged into this issue.
Original comment by kabal...@gmail.com
on 27 Mar 2012 at 9:02
I updated to 7.2.0-RC1 yesterday, reverted libaudio and everthin g works
perfect!
No more mute calls so far!
Thanks!
Original comment by redriver...@gmail.com
on 28 Mar 2012 at 4:15
Status after 3 days: no muted calls
Original comment by justc...@gmail.com
on 30 Mar 2012 at 10:08
4th day without mute calls, reverting libaudio worked flawlessly
Original comment by leonardo...@gmail.com
on 31 Mar 2012 at 3:24
No more issues also for me with old libaudio
Original comment by enrsil1983@gmail.com
on 20 Apr 2012 at 4:00
Had the same problem, I am on a Latam xt720 with CM 7.2.0 RC1 and came from a
stock 2.2 rom, I applied the libaudio update kabal provided and have been
receiving calls normally today.
Original comment by sanchop1...@gmail.com
on 22 Apr 2012 at 9:11
No audio problems since downgrading libaudio
Original comment by justc...@gmail.com
on 23 Apr 2012 at 5:55
I updated to 7.2.0-RC1 + reverting libaudio.
And for me still no solution for the issue.
Please help.
Original comment by ariel.it...@gmail.com
on 15 May 2012 at 12:24
Hi Pavel,
I have been on 7.2RC1 and am enjoying an advanced, if aging, phone. My info: I
also had those 'mute calls' but my workaround was to press the 'hold' and then
'unhold' - then the call was OK.
/d
Original comment by dror.harari
on 16 May 2012 at 7:57
I've included a possible workaround in CM 7.2.0 RC2.
Please let me know if you still experience this issue when running RC2.
Original comment by kabal...@gmail.com
on 5 Jun 2012 at 3:08
It happened again just now. (CM 7.2.0 RC2)
Original comment by justc...@gmail.com
on 7 Jun 2012 at 10:00
i also experianced mute call issue and i downgraded the rom to its previous
build now i'm going to try the latest build thanks for the builds.
Original comment by anish...@gmail.com
on 9 Jun 2012 at 7:11
I have this issue in rc2 again too.
Original comment by pane...@vaelka.cz
on 10 Jun 2012 at 11:55
Thanks for the reports. I hope that this patch will finally fix it for good:
https://github.com/nadlabak/android_packages_apps_Phone/commit/527d999331af58437
976e15936e6cf9136ca9782
Btw., has any one from you who encounter this issue frequently set the
ro.telephony.call_ring.delay to some low value? Because that would cause higher
probability of this bug manifestation.
Original comment by kabal...@gmail.com
on 10 Jun 2012 at 8:14
Please test this build: http://d-h.st/5HH
Original comment by kabal...@gmail.com
on 11 Jun 2012 at 1:12
I never changed that value and it happens very often (2 out of 5 or something).
I'll try that new build and I'll keep you posted.
Original comment by justc...@gmail.com
on 11 Jun 2012 at 6:26
No problems so far.
Original comment by justc...@gmail.com
on 15 Jun 2012 at 5:47
As the fix is based on careful second inspection of the provided logs (I didn't
spot it the first time I checked them - it was not that easy to get what is
going on), I'm pretty sure the issue is indeed finally fixed.
Thanks for the feedback and the logs.
Original comment by kabal...@gmail.com
on 15 Jun 2012 at 6:00
Original issue reported on code.google.com by
justc...@gmail.com
on 21 Feb 2012 at 11:28