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.
I'm using the latest LP nightly (3/27/15) and have had problems RECEIVING texts only since about the 3/19 build. Sending them works out fine, and I do eventually get the texts either later in the day or when I reboot the phone. I do use Textra, but seems irrelevant, as the stock google messaging app isn't receiving them in a timely fashion either. I'm on a Google Nexus 5 (hammerhead). I do notice upon boot and intermittently the warning at "unfortunately com.phone.android has stopped". Wondering if this is related. I WAS using ElementalX kernel for a bit, and thought that might be the problem. So this morning I flashed the nightly without flashing the custom kernel. Still the same problem. I also use Xposed framework, however left that off as well just for a test. Same results. Is this a known bug? Any other information that I could provide to help?
In case a list of the xposed modules I use would be helpful, here they are.
enable ambient display xposed
force pandora rich notification
pandora patcher
greenify
lolistat
statusbar download progress
Been a long time Pacrom user and don't wanna give up on this rom as it's always been dependable, feature packed and the best in terms of battery life. Thanks for any help in advance.
EDIT: Also, for further clarification, I do have multirom with CM12 as my secondary rom. The texts are coming in fine there. Hence why I'm convinced it's a problem with the rom and not my carrier or hardware.
Amazon Alexa app crashes in all custom ROMs I have tried. I have tried clearing cache, uninstalling, etc, etc. but the same bad behavior remains. Runs fine if I revert to stock. Anyone else run into this?
Same here. I am on newest lineageOS.
Yep, that is my experience as well.
I use the alexa app on my stock tablet and have removed it from custom roms on my phone.
Haven't found a workaround yes but would appreciate one.
Works fine here on Dirty Unicorns on 3 devices and SAOSP on another.
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
chibichuba said:
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
Click to expand...
Click to collapse
Will try that tonight. Thanks for the idea.
I will post my results.
At least I am not alone in this.
The regular pre conversations app works for me on all devices, however it does not when I add a phone number. Basically I have a problem with the new conversations. It starts to load I get all icons then a faint conversations label and then it crashes. I have tried almost all ROMs available for my moto x pure, no exaggeration. I am using DU at the moment and it does not work. Amazon thought it may be that I did not have an activated SIM card and had no data. So, I purchased and activated SIM card after having phone for almost 2 years and data does not help. Turning data off changes nothing for me as well. My sons phone is a samsung stock and his SIM card has never been activated but it works fine.
I also have been having troubles with TP-Link Kasa the most recent update is causing it to act the similar. It simply ignores my sign in. I have come to conclude their is a security validation check being used by amazon and tplink.
This kind sucks...I don't know why certain apps does this. Android was built on open source however I notice slowly they are closing Windows/doors.
Alexa app crashing solved for me!
Whenever I would hit the listen button the app would crash, if this is one of your symptoms try turning off notifications, it worked for me, found the answer in a post for Miui phones.
Ime using MaxiCM(CyanogenMod-Mod) on 5.1.1 and for me it crashed as soon as i logged in and it got Internet, using the App offline works fine but yea, no use for it.
Hi guys,
My LG V20 is my main, and also my work phone. My goal is to have the lightest ROM available while still having a stable feature set (speaker, bluetooth, wifi, etc all working normally)
After a bit of trouble, I finally got 14.1 Lineage OS loaded up and it's definitely lighter but I've been running into issues. People do not hear me well on speaker, bluetooth music play "skips", and now the bluetooth is no longer connecting to devices I've connected it to before.
I'd love to have something that removes all bloatware, but still has the stability of stock. Any recommendations?
I have a H910 AT&T Variant,
My job requires my phone. I mainly use my phone for Skype, WhatsApp, Email, Google Maps + Navigation, Playing FLAC music using High Impedance headphones and Car 3.5mm input, FM Radio, RockRadio.com app/Galaxie Radio(RadioKing) app and 4G LTE data.
I tried AOKP, RR, LOS, Alpha and Super...both ver. 7(Nougat) and 8(Oreo).
This took me a very long time to decide, I also tried older stuff like WETA, etc...
Alpharom Oreo works best for me, everything I listed works fine.
I use the mk2000 kernel, great battery life, with heavy use you need to fast charge sometime in the day.
The only problem I have, the wifi seems to go off when phone is inactive because whatsapp on pc keep saying not connected until you unlock/wake up phone.
But it is so awesome, I love it...
AOSP based roms have problems with audio and dac, it works but not loud and clean, I tried playing with mixer file but no luck.
They are much faster and LOS15 based roms have the second screen working with custom kernel...
Don't worry, it is work in progress...
This is just my opinion, and it suits my lifestyle, you need to try some different ones and see for yourself.
It's funny you mentioned Alpha being the one you like most. I was going through the roms yesterday, and couldn't install some of the Oreo based roms (I'd get an error that the kernel wasn't the correct one, I guess since I was coming from 14.1)
After looking through some, I ended up installing the alpha omega oreo rom with mk2 kernel and it is working great so far (I just haven't tested bluetooth yet).
I've lost all the sluggishness I saw before, especially when using "Ok, Google" to add calendar appointments, etc.
I have the second screen which is also a nice little bonus. Battery life seems to be as good as it's been, as well.
One question : I tried using Magisik to check all the bloatware I wanna hide, but it doesn't seem to do anything? Is there a way I can remove LG and ATT bloatware completely?
i am still using wetarom with weta kernel... since it was well developed and a stock base rom, i found no problem whatsoever while using it... even tho is outdated, no one has successfully hacked my phone yet lol
The alpha install lets you choose what bloatware you want to remove...
Flash the magisk zip right after before reboot, thats what I do...
You can disable whatever apps remain like uber, etc....
I just keep LG Smartworld for themes, LG Health, FM Radio and LG Music app.
I've been trying to get the LG AirDrive to work, it worked some time with older alpha build but it now keeps crashing.
---------- Post added at 07:42 PM ---------- Previous post was at 07:11 PM ----------
WETA was/is a great rom but something about running the latest android appeals to me. Great performance/battery life and audio stuff.
So far alpha rom has been working well (still trying to find a safe list of bloatware that I can remove via ADB, or some other way.)
Only issue I'm having, which I also had before, is that bluetooth play (especially in the car, but no exclusively), will sometimes stutter like it's a 90's cd player. Not sure if it could be related to the case I have on the phone at all? I'll have to test it both ways and see what happens
Just run BluReset app included with the ROM (I think you have to select it) it helps but need to do it ever so often, I just use Bluetooth for calls in the car and 3.5mm for audio.