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.
Related
The new google play music keeps crashing, I tried uninstalling and reinstalling. It just says Google Play Music has stopped working. Anyone else getting this or know a fix?
bluesfear said:
The new google play music keeps crashing, I tried uninstalling and reinstalling. It just says Google Play Music has stopped working. Anyone else getting this or know a fix?
Click to expand...
Click to collapse
Me too ,, same prob.
bluesfear said:
The new google play music keeps crashing, I tried uninstalling and reinstalling. It just says Google Play Music has stopped working. Anyone else getting this or know a fix?
Click to expand...
Click to collapse
If it makes you feel any better, this is a cross platform, cross ROM issue. I am having the same problem with a Samsung Galaxy Note 2, and I have seen the same problem reported on S3s, S4s, Droid Bionics, etc.
I keep looking to see if Google is providing an update, but no apparent response despite the growing chorus of complaints and reports.
I had this issue when I flashed the latest Paranoid Android alpha update and their new gapps.
I flashed previous gapps and updated everything and I'm good now.
bluesfear said:
The new google play music keeps crashing, I tried uninstalling and reinstalling. It just says Google Play Music has stopped working. Anyone else getting this or know a fix?
Click to expand...
Click to collapse
I had this problem out of nowhere yesterday morning. I removed extensions, etc. Nothing had changed since it had worked the day before, other than their new "listen" rollout, or that pandora competitor.
It would immediately crash with an "aw, snap" every time, within a millisecond.
So I went here: support.google.com/googleplay/?rd=1#contact=1
and filled that out. Got the auto response email with some pat, boilerplate problem solving stuff.
But I didn't do ONE THING, and it fixed itself.
I have a hunch that they get receipt of that, and check your account and fix it behind the scenes. That's the only thing I can think of, because I didn't do a thing, and it stopped working.... and started working again after I didn't do a thing (other than try to remove extensions).....
that support troubleshooter may have done the trick. I am back up and running.
I had the same problem when upgrading to Play Music 5.0.something; what I did to overcome the FC's:
1. Clean cache Download Manager
2. Clean cache Play Music
3. Clean cache Media Storage
4. Reboot
I had the same problem and uninstalled updates to roll back to the prior version. Then on Friday, I saw the update pending and decided to try again. Somehow, it did indeed fix itself. However, what I notice now is that it likes to un in the background on its own from time to time -- enough that it seems to be interfering with battery life . . . .
Works fine for me, never had an issue. I don't use it though as I don't listen to music on my phone
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.
I am experiencing random cut outs of audio during media playback through the speaker. Bluetooth and headset working fine. Notifications and other sounds working fine. Mainly during video playback, streaming and video stored on device, the sound plays for a few seconds then cuts out. I didn't have this issue before the most recent OTA update. I have tried factory resets, rebooting, wiping cache, even custom roms. Does anyone else have this issue? What is the solution?
I have the same issue as you. GS7 Edge Verizon. I can't find any solutions out there yet :crying:
Same issue. The only thing that I can add is that when the speaker cuts out, if I switch to phone, make a call, and then put the call on speakerphone, then hang up, the problem is fixed for a few minutes.
Does anyone have a solution for this? Surely its a common issue. Unless my phone is on charge I can't use apps like spotify, listen to podcasts or radio unless I keep the screen on.
Any luck?
I have the issue on a sm-g930F. Samsung support just says i should send them my device but thats not my plan. I called them and sayed i want a update of the firmware but they refused me and just sayed i have to send it to them because they can not make a update without my device is seen. I really hope someone sends his device to them that we can get a new firmware . Iam on android 7.0 official samsung update but this bug is in 6.0 the same .
Anyways i need a soöution for this. Its a softwarebug i know, because nexus 6p users and nexus 5 users expirienced the same ****in error. Please help out.!!!
I was experiencing audio pause or stopping after an OTA upgrade to Nougat on my stock S7 Edge Duo (G935FD), when using Pocket Casts podcast app to play files stored locally on internal memory. This seemed to happen primarily when using wired headphones or bluetooth speaker, and some minutes after the phone screen turned off.
I tried wiping the app cache, reinstalling the app, wiping phone cache, full phone wipe, reinstall stock Nougat via ODIN, TWRP & rooting phone, disabling Samsung App Power Saving via Titanium Backup (com.samsung.android.sm / com.samsung.android.devicesecurity). Only when I booted into SAFE MODE did the problem go away. So I used TB to disable pretty much everything I could recognise as an app I had installed.
Eventually, after much tinkering I seem to have narrowed it down to some combination of Quick Connect, Google Chrome and Android System Webview. I have disabled QC and Chrome and I no longer have any audio issues. When I unfreeze/freeze Chrome or Android System Webview I get an audio issue as the app freezes/unfreezes.
I had same problem and ı thought this problem can be related to an app ı installed. And it was. When i uninstalled Sputnik news. My problem had gone. If u have it, uninstal. If u dont have, may be one of other app causes. Try uninstalling each app, and find the app causes this problem
Okay so I'm gonna describe my problem as clearly as possible and will hope someone can find a fix for this.
Device: Nexus 6P
OS: Android 6.0.1 (latest vendor & security patch - June 2016)
Bluetooth devices used: Sony MDR 600BT, SOL republic tracks air, jbl synchros earphones, jbl flip 2 speaker.
1) pair earphones/speakers
2) start playing music on earphones/speakers
3) works fine on first run and when screen is off
4) when I switch on my screen to change the song the music stutters for 10 full seconds, then stuttering stops.
5) I change the song and again put screen off, works fine.
6) i put my phone in my pocket and suddenly my phone audio stops skipping??? Wtf???
7) so I change my pocket and put it in my hoodie pocket. (Nearer to earphones - maybe distance is the problem I thought)
8) audio still skips............:crying:
9) put my screen on to change song, audio starts stuttering again like crazy and then stops.
10) I request anyone here to heed this request and tell me how to workaround this problem
Currently running latest android MM 6.0.1 and no improvement .....:crying:
I don't understand one thing - top of the line flagship device and still these problems? Not getting value for my hard earned money. This is wrong.
I tried it with my iPod and it works like a charm. No stutters. No skips. Nothing.
Tried different Bluetooth headphones too in case my Sony earphones were the problem. NO IMPROVEMENT SAME PROBLEM PERSISTS.
TRIED USING IT ON ANY BLUETOOTH SPEAKER THE ABOVE THINGS KEEP HAPPENING AND I AM GETTING REALLY ANNOYED WITH THIS PHONE WHEN IT COMES TO BLUETOOTH.
I'm sorry for agonizing so much. But I hope you'll can understand my problem. And hopefully there's a fix somewhere in the world.
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
blackwrx02 said:
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
Click to expand...
Click to collapse
I can't speak for Zapjack12345, but I notice it with PowerAmp, Pandora, Spotify, YouTube, basically any app that is pushing audio through bluetooth. Audio is fine when the screen is off, but as soon as I pick up the phone, and turn it on to check notifications, things get screwy with the audio
Strange. I just checked with Pandora, YouTube, and IheartRadio and all seem fine with screen off and turning it on, using the pulldown menu, or changing songs. I'm using a cheap set of bluetooth earbuds from Amazon (no-name brand), and am stock with the phone, not rooted (yet) and on June updates. Phone was purchased in May new from Best Buy.
Same issue for me as well. I'm specifically using Amazon and Pandora most of the time. Its very annoying. On Chroma and franco kernel.
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
uodii said:
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
Click to expand...
Click to collapse
I'm currently on Pure Nexus 5/6/16. Nothing out of the ordinary installed. Tried clearing the Bluetooth cache, as the issue I am noticing was similar to issues that the Samsung S5 was having, but there was no difference.
I am going to look to go back to stock and see what happens, but looking at what OP posted, it looks like they're on stock, and having the same issue.
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
krakerx said:
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Click to expand...
Click to collapse
I had a little less issues when using the Dev Preview 3 but there was another issue that arised that I hope gets fixed.
If you're using bluetooth when driving around when you lose signal or drop/gain data connection the audio skips for a quick second. Through past testing I've done working with kernel devs on 2 phones, the issue is related to how the hotplugging works for the cores. If only one core is running when the connection drops there is an issue with how the cpu ramps up and/or turns on another core to handle the workload. I thought this regression was pretty interesting seeing as one the things they were boasting about at the Google conference was how android would fix slow downs and issues when losing/gaining network connectivity with N. Hopefully it'll be fixed before final release.
akarol said:
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You and me both. I am on my 3rd 6P and my BT problems are still the same. If the BT problems were only effecting one particular device I could understand but my Microsoft band, BT earbuds and car all seem to disconnect continuously on a bare/stock phone.
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Does anyone else have any updates regarding this issue? Literally wanted to throw my phone out of the window during the morning commute.
Zapjack12345 said:
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Click to expand...
Click to collapse
Don't use cm based roms
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Yep, this is 100% the reason. It is a CM issue. AOSP roms like Paranoid Android and Pure Nexus don't have this issue. I love Resurrection Remix, but this is starting to bug me. I may jump to PA rom soon...
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Thanks. Was about to ask this question. It is a CM issue.
I have had issues with BT dropping randomly in my car on 2 different 6P's. No rhyme or reason, and it doesn't happen often, but annoying when it does. Happened on MM and DP4 currently.
On the flip side, my audio quality went down on my S7E over BT when my smartwatch was connected. Somehow, that doesn't happen with the 6P meaning I can keep my watch on in the car, so I am happy.
Hey, I just found this thread and surprised it took me this long considering I've been having this issue since I got my phone in November.
My 64gb 6P was stock until earlier this week, when I finally rooted and flashed xposed. The issue stopped the day I rooted my phone, and I was thrilled.
After reinstalling most of my apps and getting back into my routine, the problem came back. I've tried booting my phone into safe mode several times before rooting so I'm fairly confident the issue doesn't exist because of a specific app interaction, but I can't figure out what it is to save my life. I might backup again and restore to the backup I made right after rooting to see if I can narrow down the problem.
Other than that, I am very new to this stuff and honestly just thrilled to have found other people having the same issue.
I only experience the problem while connected to my car (2015 Chevy Cruze), and not any other bluetooth device.
Let me know if you guys find/have found anything I suppose?
I kinda have up on trying to narrow down the issue. I tried PureNexus, Paranoid Android, I tried different kernels, different cases. Still kept skipping and jumping, no matter how far, or close it was to my Bluetooth device (car stereo, speakers, home audio system). I went back to stock, no root, no Xposed, pure and simple Android, and I have not had a single issue, it's beautiful.
Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again.
Thanks in advance for your help
ilininja said:
Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again. Thanks in advance for your help
Click to expand...
Click to collapse
The 6P has two speakers, and they wouldn't both fail at the same time. Sounds like he's damaged the phone somehow. The audio jack and speaker output both not working seem to back this up. I've seen the headphone jack part available separately, and there are guides available to replace it. Before flagging it as a hardware issue and opening the phone up, you want to make sure you wiped the phone completely by formatting the partitions (system, userdata, cache) and use the flash-all.bat included with the full Google image. There is a remote chance it is software related, but I doubt it.
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
jhs39 said:
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
Click to expand...
Click to collapse
You mean disabling the big CPU ?
ilininja said:
You mean disabling the big CPU ?
Click to expand...
Click to collapse
Yes. You can always turn it back on but turning it off apparently fixes the permanent boot loop problem on the Nexus 6P. If the problems you are describing are related to the same build problem then turning it off might make them go away. Sometimes people's phones would start acting odd before going into the permanent bootloop. That phone could be on its way there.
this is purely a guess but the problem may be hardware related with the headphone jack. it could have a physical short somewhere. if thats the case the device may think a headphone jack is being used and wont play through speakers because its being told its plugged in. But wont play because of some physical short or an open.