Fixed
Status Update
Comments
fr...@gmail.com <fr...@gmail.com> #2
Please search, this sounds very similar to several other issues already reported. Thanks.
iz...@gmail.com <iz...@gmail.com> #3
Search for what?
The problem was also reported for 5.0, now after the upgrade i too have the same problem
The problem was also reported for 5.0, now after the upgrade i too have the same problem
rd...@gmail.com <rd...@gmail.com> #4
[Comment deleted]
[Deleted User] <[Deleted User]> #5
tu...@gmail.com <tu...@gmail.com> #6
Hi,
I can confirm that, as I was just going to post the same issue. Since 5.0.1, I can't hear anything both on received calls and sent. This is a grave bug which needs immediate fixing.
I can confirm that, as I was just going to post the same issue. Since 5.0.1, I can't hear anything both on received calls and sent. This is a grave bug which needs immediate fixing.
en...@gmail.com <en...@gmail.com> #7
I agree, this is really a serious bug: the phone lost it's core and mission-critical feature.
Do you know any way we can increse the priority of this bug ?
Do you know any way we can increse the priority of this bug ?
tu...@gmail.com <tu...@gmail.com> #8
I am facing the same issue..I have nexus 4.. And after upgrade cannot take or receive calls..the audio just stopped working..this is serious
tu...@gmail.com <tu...@gmail.com> #9
I unfortunately have the same problem. :-(
I "upgraded" my Nexus 4 to 5.0.1 yesterday and made my first call a moment ago. The call seems to have connected, but there was neither an audible 'beeping' when waiting for the other person to pick up, nor could I hear that person.
After a reboot I could hear the beeping but then only the other person could hear me...
Very critical issue indeed! :-[
I "upgraded" my Nexus 4 to 5.0.1 yesterday and made my first call a moment ago. The call seems to have connected, but there was neither an audible 'beeping' when waiting for the other person to pick up, nor could I hear that person.
After a reboot I could hear the beeping but then only the other person could hear me...
Very critical issue indeed! :-[
en...@gmail.com <en...@gmail.com> #10
I am having this same issue. It is somewhat periodic and seems to be fixed temporarily by rebooting. When it occurs my phone will not emit or record any audio during a phone call (other audio apps are unaffected). This state will persist until reboot at which point calls will work normally until some unknown change causes the next call to be silent. I have never encountered the issue in the middle of a call. Nexus 4, 5.0.1 stock, unrooted.
we...@gmail.com <we...@gmail.com> #11
I have exactly the same Malcolm.
This is frustrating, and since I use the phone for work, it causes me trubles... I had to switch to an old phone :my nexus 4 is not reliable enough to be used.
This is frustrating, and since I use the phone for work, it causes me trubles... I had to switch to an old phone :my nexus 4 is not reliable enough to be used.
bo...@gmail.com <bo...@gmail.com> #12
I have the same issue, Nexus 4 with stock android on. Rebooting fixes it for a while, but then a call will come through (or I'll make one) and no audio once again. They can't hear me and I can't hear them, headphones isn't the answer either.
we...@gmail.com <we...@gmail.com> #13
I am facing the same issue after 5.0.1 update. After rebooting it happened again after a few hours.
xa...@android.com <xa...@android.com>
kr...@gmail.com <kr...@gmail.com> #15
Same here :-/
ch...@google.com <ch...@google.com> #16
Same problem, no Voice call audio on nexus 4 after ota lolopop upgrade, neefs a reboot which doesn't cure it for long.
Other apps like csipsimple unaffected. Critical bug
Other apps like csipsimple unaffected. Critical bug
ch...@google.com <ch...@google.com> #17
I also have the same problem with my Nexus 4 after 5.0.1 update. It's a critical bug.
Description
Hi, when I updated my build.gradle file to 'com.android.support:appcompat-v7:21.0.3' I got some warnings and my ActionBar doesn't work as expected (It get's the default appearance and the custom color and logo are gone), I don't know if this is intentionally or if some code got deprecated and doesn't work anymore and I have to change it, the warnings I get are these:
12-29 11:21:34.207 29421-29421/
12-29 11:21:34.207 29421-29421/
12-29 11:21:34.207 29421-29421/
12-29 11:21:34.207 29421-29421/
12-29 11:21:34.207 29421-29421/
12-29 11:21:34.208 29421-29421/
12-29 11:21:34.209 29421-29421/
12-29 11:21:34.210 29421-29421/
12-29 11:21:34.210 29421-29421/
12-29 11:21:34.215 29421-29421/
12-29 11:21:34.215 29421-29421/
12-29 11:21:34.215 29421-29421/
12-29 11:21:34.217 29421-29421/
12-29 11:21:34.217 29421-29421/
12-29 11:21:34.217 29421-29421/
If I get back to 'com.android.support:appcompat-v7:20.0.0' this warnings disappear and I can see my custom action bar again.