Related
Hi,
I have a Nexus 4 running CM11.
I am not getting any audio during calls. In the earpiece or speaker. Music, notifications, Skype, etc are working fine.
Tried using Soundabout, but that did not make any difference.
Sometimes when I boot the phone, I am getting audio in the first 3-4 calls that I make. But when I close the dialer and open it again, I don't get any audio
Thanks in advance!!
GandaBaccha said:
Hi,
I have a Nexus 4 running CM11.
I am not getting any audio during calls. In the earpiece or speaker. Music, notifications, Skype, etc are working fine.
Tried using Soundabout, but that did not make any difference.
Sometimes when I boot the phone, I am getting audio in the first 3-4 calls that I make. But when I close the dialer and open it again, I don't get any audio
Thanks in advance!!
Click to expand...
Click to collapse
I'm experiencing the same issue with my nexus4/CM11...
Not found the cause nor the solution yet :crying:
I just made an update from nightly 20141024 to 20141031 and this issue is still present.
Exactly the same problem on Nexus 4. Manifested in snapshot M11.
I've been having the same issue.
I'm trying different basebands now but still no luck.
I'm using CyanogenMod 11 11-20141009-UNOFFICIAL-mako with baseband 2.0.1.1701.03 and I don't have this issue.
Flash the latest radio, try a clean flash then try again. Stay with the stock CM kernel too !
I already have the latest baseband and I am using the official CM kernel. The issue started somewhere during last week's nightlies and it is very likely that even the upcoming M12 build has this issue on Nexus 4 devices.
Not a hardware problem
I wiped and flashed back to a factory 4.4.4 last night and the problem seems to be fixed. So at least we know it's not a hardware issue. I was also able to make calls through hangouts just fine.
I had already flashed the latest 1.03 radio as well as the original stock radio and most of the ones in between and that didn't work. Clearing data for the phone app didn't seem to do anything at all.
Try doing a clean install of the latest nightly or monthly and see if that works.
I bet that if you uninstall and reinstall the phone app that it would start working again.
I just created an issue on the bug tracker: https://jira.cyanogenmod.org/browse/NIGHTLIES-324
If you have any additional information please add them to the issue to improve the chances of a fast bug-fix.
still working
I knew I couldn't stay on stock very long.
Flashed 20141102 and in call audio is still working.
Did anyone try a clean install of the latest nightly?
Try to reset only the telephone app (com.android.phone) and reboot.
Worked for me.
EDIT: Doesn't work anymore.
Downgrade to google play services v6.5.86 fixes incall audio for me.
Code:
adb install -r -d Downloads/com.google.android.gms.apk
3563 KB/s (29005798 bytes in 7.949s)
pkg: /data/local/tmp/com.google.android.gms.apk
Success
@ ivanich:
thanks, my solution doesn't work since the google play service update.
Another solution should be to install the gapps again, but I didn't try it.
Greetings
https://jira.cyanogenmod.org/browse/CYAN-5728
This has been an issue for some time.
The evidence leads us to believe that google play services is the culprit at this time. But why does it plague only the Nexus 4's running CM?
(25 OCT) - When this issue was identified initially. The issue can be temporarily resolved by disabling wifi and restarting the phone. With WIFI off the phone will make and receive calls for at least 2 day without regressing(i personally tested this) as soon as you turn on the wifi, 1 - 4 calls in the audio is gone.
(10 NOV) - Two weeks passed since the initial reporting and the issue went away, assuming because google play was updated. At this time I was able to make and receive calls normally for a week or two. Then out of the blue, no audio. I disabled wifi and rebooted, the audio was back. The difference this time was the phone kept working normally for another two weeks.
(12 DEC) The issue has resurfaced, assuming google play was updated again and we are back to experiencing the issue with the initial levels of severity.
It looks like Google Play Services 6.5.87 will cause the issue. 6.5.86 works fine. 6.5.88 is unknown, 1 report says it doesnt.
Saml01 said:
https://jira.cyanogenmod.org/browse/CYAN-5728
This has been an issue for some time.
The evidence leads us to believe that google play services is the culprit at this time. But why does it plague only the Nexus 4's running CM?
(25 OCT) - When this issue was identified initially. The issue can be temporarily resolved by disabling wifi and restarting the phone. With WIFI off the phone will make and receive calls for at least 2 day without regressing(i personally tested this) as soon as you turn on the wifi, 1 - 4 calls in the audio is gone.
(10 NOV) - Two weeks passed since the initial reporting and the issue went away, assuming because google play was updated. At this time I was able to make and receive calls normally for a week or two. Then out of the blue, no audio. I disabled wifi and rebooted, the audio was back. The difference this time was the phone kept working normally for another two weeks.
(12 DEC) The issue has resurfaced, assuming google play was updated again and we are back to experiencing the issue with the initial levels of severity.
It looks like Google Play Services 6.5.87 will cause the issue. 6.5.86 works fine. 6.5.88 is unknown, 1 report says it doesnt.
Click to expand...
Click to collapse
6.5.88 and 6.5.94 are broken too .
ivanich said:
6.5.88 and 6.5.94 are broken too .
Click to expand...
Click to collapse
6.1.88 is broken for me aswell, even with the latest 1.04 radio version it doesnt work
ivanich said:
6.5.88 and 6.5.94 are broken too .
Click to expand...
Click to collapse
Actually I just installed 6.5.94 (over 6.5.87) and my in call audio is working, at least for now.
Reboot to recovery and clearing cache resolved issue for me.
Thanks,
turning wifi off helped.
How can I force google not to update the Google Play Services ?
It is not an regular app from the market.
I've tried to disallow all automatic updates, this doesn't help.
Greetings
Clearing cache
Rebooting into recovery and formatting the cache partition worked for me as well.
Situation
Bought Nexus 4 refurbished, works great except for this issue. Back speaker works great, Google Search works with mic (Ok Google). Updated via OTA all the way to 5.0. Am using phone on a carrier in Ecuador.
Problem
When making a phone call over the local carrier, call connects (you can see the counter on screen), music, if playing, pauses as it should. But no audio from the earpiece, and the other side does not hear anything from my side. Tried putting call on speaker, nothing. Tried with headphones, nothing. However, when making a Hangouts call over data, mic/earpiece work fine. To me, this means the hardware functions, so it must be software related. The phone sends SMS without issue, so it works with the local carrier. Also data works without any issue.
What I've done so far
Searched high and low, and it seems this is a somewhat common problem that some have fixed in many different ways. Please let me know if you know of another that I may have missed.
Downgrading to 4.4.4
Upgrading back to 5.0
Factory Reset
Flash 5.0 Factory image
Upgrade to 5.0.1
Flash complete 5.0.1 Factory image
Flashed latest CM11 nightly
Tried several "solutions" found on Google Group forum, such as pluging headphones in and out
Flashed Hybrid modem with included audio fix
Switched SIM cards
Installed SoundAbout, and tried many different options - redirecting Phone Audio, even changing options for Headset detection (thought the phone was confused, thinking the headphones were in)
Tested mic with recording apps and by recording videos, all work fine.
Installed PAC-ROM without Gapps to see if it was the Google Play Services issue
Disabled the CheckInService
I think I've tried more, but can't remember them all. It's been over a week, and can't answer or make phone calls.
Coming to my wits end, and it's extremely frustrating since it doesn't seem to be a hardware issue, and I hate giving up on something I can fix. Any suggestions?
(Edited and added a couple more tests to the list)
yep, you are not the only one with this issue, it started to plague users just recently, including me and from what i've learned so far it has got something to do with google play services.
however for me, flashing 5.0/5.0.1 resolved it (i only encountered it on CM4.4.4 )
here is another topic bout this. good luck
http://forum.xda-developers.com/nexus-4/help/audio-call-nexus-4-cm11-t2924589
ps. this thread i linked above acutally contains some solution/workaround involving disabling one of the google play services. just read through the whole thread
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
I too had the exact same problem. I was on CM 4.4.4 nightlies. Moving to stock lollipop5.0 solved the problem.
Shooting Star Max said:
If this is really about Google Services, try installing a ROM without adding GApps. You can then state if they are really the culprit here.
Click to expand...
Click to collapse
I tried that too. I installed PAC-ROM, the latest nightly, without GAPPS. Booted fine, all seems to be working except sound in calls.
I also tried disabling the CheckIn Service, as was mentioned in the other thread, still no luck. So frustrating!!
I'll try them all again...
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
BitteredBro said:
HijoProdigo,
+1 on flashing a 5.0 ROM.
Same thing happened to me a couple of weeks back. After messing with the phone for three days, flashing a Lollipop ROM solved the issue (I used CM12 unofficial nightlies)
Click to expand...
Click to collapse
I'll give it a try. I had tried with the official CM11, both with and without Gapps, but no luck.
So when I bought my Nexus 6P I knew I was going to get the latest updates as soon as Google released them. I also expected to find minor bugs because we are getting updates much faster as well.
What I was not expecting is to both, bugs that make for a nearly unusable device and minor annoying ones. For my device the bugs that hit me hard are;
Max Volume Bluetooth Speaker Bug - Most bluetooth speakers are stuck in max volume mode and can't be turned down. Distorts the audio and creates a situation were you could blow out the speaker. Not all speakers are effected.
No LTE On Boot - Annoying to have but "fixable" by putting the device in Airplane mode. Otherwise no Data or SMS until you do and hope your phone doesn't reboot in you pocket while waiting for an important message.
No Phone Calls - You can't make or receive calls. As a result you can't check VM either. No amount of Airplane mode or rebooting will fix it. Neither will the phone service menu.
My concern here is that Google hasn't patched these bugs yet, even after releasing another update to 6.0.1 M. For now I'm fine with downgrading to 6.0.0M but I'm missing out on updates.
To add to insult any ROM build with the 6.0.1 source is effected by these bugs, so I can't even use most ROMs unless I find an older version.
I guess my main question here is this:
Is this normal? Does Google usually go so long without patching the bugs?
Seems really silly to have a phone, but not be allowed to make or receive calls at all and not be able to send SMS or email unless you do a few tricks first. It's a phone. Don't they test these things?
Disclaimer: I already know not all 6P or Nexus devices are effected. That does add to my confusion as they all should be the same exact device.
EDIT: I also wanted to add that when I got the device I could do all these things however even downgrading will no longer allow phone calls. Something is retaining.
Well that's weird mate. I'm on 6.0.1 and have none of these problems.
I was experiencing awful battery life after the latest update but clearing the cache has made a huge difference
Have you tried reaching out to Google? It would be helpful if you could share how you upgraded to 6.0.1? As mentioned above did you clear cache? The more info you can provide; the faster someone can help you.
The Bluetooth volume issue is the only one I have and only on one of my speakers. The others with fine.
Huh, ya 6.0.1 here too and none of these issues are present.
Hi there,
On Snapchat, I noticed that all the recorded videos, with both cameras, are extremely laggy. I have this issue from the 9.25.0.0 version to the latest 9.26.1.0. I reverted back to 9.24.0.0 so no anymore problem, but it's a bit annoying because I don't have the latest version. I noticed aswell the mic a bit noisier than before (such a typical MM problem while recording on every camera app)
Tried to fix it with the AwesomePlayer trick, but nothing. Also wiped the cache and it didn't solve the problem.
Tested it on CM12.1, CM13 and 6.0.1 stock.
Has anyone faced this problem?
I got the same issue since I updated to 9.25. I got a month emailing to support team with no answer
lelapincretin8 said:
Hi there,
On Snapchat, I noticed that all the recorded videos, with both cameras, are extremely laggy. I have this issue from the 9.25.0.0 version to the latest 9.26.1.0. I reverted back to 9.24.0.0 so no anymore problem, but it's a bit annoying because I don't have the latest version. I noticed aswell the mic a bit noisier than before (such a typical MM problem while recording on every camera app)
Tried to fix it with the AwesomePlayer trick, but nothing. Also wiped the cache and it didn't solve the problem.
Tested it on CM12.1, CM13 and 6.0.1 stock.
Has anyone faced this problem?
Click to expand...
Click to collapse
If you have root then try changing the model number from build.prop :good:
http://forum.xda-developers.com/general/xda-assist/snapchat-low-fps-night-darkness-t3448114/page1
Check this link for the workaround
http://forum.xda-developers.com/not...how-to-consistent-30-fps-night-t3449317/page1
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
arcticphoenix said:
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
Click to expand...
Click to collapse
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
strongst said:
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
Click to expand...
Click to collapse
Yeah it is part hardware and part software. A couple of months ago I used the cracked unbrick tool found here at XDA and I regained most functionality which was lost after upgrading from 9.0.4 - 9.0.5, though I do still get system freeze ups and reboots. But that is from a faulty unit not any of the ROMs.
I apologize for reviving an old post so any mods may close this thread.
arcticphoenix said:
...
I apologize for reviving an old post so any mods may close this thread.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP.