Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
clcrawl said:
Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
Click to expand...
Click to collapse
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Thank you very much, I am going to give this a try shortly.
scarroll825 said:
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Click to expand...
Click to collapse
The 8/26 nightly fixes this issue and was just posted to get.cm.
Related
I scoured the forums for a couple hours trying to see if there's anything like this out there, I couldn't find anything.
I flashed the 8/29 Cyanogenmod 10, properly cleared caches and stuff, and it's been great... except for when someone calls me, I answer and neither of us can hear anything. When I call back everything works perfectly.
I tried switched to speaker, muting and unmuting, resetting, nothing helps... the really odd thing is that if I press a key in the dialer while on the call, the person on the other end can hear the key tone. That goes both ways.
I thought maybe since a lot of people were having audio issues that were fixed by the 7/27 kernel that it might help, so I flashed that and it didn't make a difference.
Does anyone have any ideas as to what I can do? I'm stumped here. If the outgoing calls work like normal, it shouldn't be an issue with hardware.
edit: I flashed the first OTA modem as well, didn't affect anything
EDIT - flashed to the Aug 30 experimental call build, it's working fine now. Hooray! Sorry for posting like a noob -.-
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Whisk_33 said:
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Click to expand...
Click to collapse
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
amber12129 said:
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
Click to expand...
Click to collapse
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
mtemlm satisfy
Whisk_33 said:
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
Click to expand...
Click to collapse
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
amber12129 said:
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
Click to expand...
Click to collapse
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Whisk_33 said:
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Click to expand...
Click to collapse
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
amber12129 said:
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
Click to expand...
Click to collapse
So, I have the option to force stop it. (no change in results).
I've even downloaded the "Google Voice" app, which added the "Voice+" app, opened it, confirmed that it was on disable and still no change.
I have no idea why this problem started this morning since I don't believe I am any changes to my phone the past couple days... I really don't know what information I can provide to help troubleshoot it...
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
thezam said:
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
Click to expand...
Click to collapse
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Whisk_33 said:
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Click to expand...
Click to collapse
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
thezam said:
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
Click to expand...
Click to collapse
A bunch of us on S4s seem to be having the same problem! The timing of this issue all happening at once is weird... http://forum.xda-developers.com/showthread.php?p=50552025
OK this really does seem to work for me as a temp workaround...it sticks through reboots and all. Go to the dialer and enter the trusty old *#*#4636#*#* then go to phone settings and change preferred network type to CDMA only then back out and reboot.
It kinda sucks cause it's slow on the go, but at least I can send texts reliably. I have WiFi most places I am anyway.
If anyone figures out a real long term fix please post!!!
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
gagnier27 said:
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
Click to expand...
Click to collapse
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
amber12129 said:
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
Click to expand...
Click to collapse
Some people don't have voice+ and the solution you used isn't an option for them.
For those of us less fortunate than you, It seems you can fix the problem by loading a TW ROM and flashing the MB1 firmware. Then you can return to CM
I had XVoice+ for Exposed on my SGS4, it stopped me from sending texts. It was ok when i uninstalled it. I hope that might help.
I applied the update and I lost sound on calls both incoming and outgoing. A reboot seemed to fix it for now, but I'm concerned it will crop up again.
Anyone else experience this or have an answer?
It happened to me this morning. Had to reboot to get it working again.
greystealth said:
It happened to me this morning. Had to reboot to get it working again.
Click to expand...
Click to collapse
Was that right after the update too, or did it happen more than once?
Also happend to me now, fortunately reboot helped.
Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
I am having the same issue with SMS. I am running the 20150225 nightly.
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
solution?
NikoStone said:
Hey guys,
So I'm experiencing issues receiving calls and SMS on my OPO ever since I flashed a CM12 nightly in early February. I don't know for sure that CM12 is the issue because I can't find anyone that has a similar problem, but since the problem didn't start until after the initial clean install of CM12, I'd say this is a good place to start.
I'm currently running CM 12-20150223-NIGHTLY-bacon and have not changed anything else (kernal, xposed, etc...). I use AT&T and am located in the US.
SMS Problem: First off, I use Hangouts as my SMS application. Sometimes I will go hours without receiving any text messages, only to have a dozen of them all come flooding in at once. Usually this is prompted by me sending myself an SMS. I also occasionally have trouble downloading group MMS.
Call Problem: About 80% of the time, calls do not come through to me. My wife tells me the phone rings twice and then goes to voicemail. I do not receive any notifications of missed calls but if the caller leaves a voice mail, then I do get notified of that most of the time.
Does anyone know if this is strictly a CM12 nightly issue, or is something else going on? If the answer is just a full wipe and clean install of another ROM I'm ok with that, just wanted to get opinions from the community before I proceed.
Thanks in advance!
Click to expand...
Click to collapse
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
cyruskane said:
I am having the same issue with SMS. I am running the 20150225 nightly.
Click to expand...
Click to collapse
NikoStone said:
Bump.
Still having this problem. Is the only way to fix it to go back to KitKat?
Click to expand...
Click to collapse
Zurtri said:
You have described my exact problem to a T. Any updates on this issue? I am thinking about going back to CM11. Every nightly I update in hopes that it resolves this issue but it hasn't yet.
Click to expand...
Click to collapse
NikoStone said:
No fix that I've found yet. Here is another thread on the issue that has seen more interaction than mine. http://forum.xda-developers.com/oneplus-one/help/cm12-delayed-messages-missed-calls-t3049583
Have you come across any fix yet?
Click to expand...
Click to collapse
nadeem.patel said:
Yesterday there were several updates related to mms..if you still use cm12...then install cynadelta app select last bacon zip. Then click on refresh, it will check the latest bacon file and update only incremental data..means you dont have to download entire rom. Saves your time and data package.
Once you see all the components are working.. Take backup using twrp and keep it in USB.. Incase you need to restore.
Click like if its helpful:thumbup:
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
lillsmartdude said:
Hi! I har the same problem after updating to cm12. I solved it by go to settings/ mobile network/ preffered network and chose 3g. That worked for me. Much longer batterylife too.
Click to expand...
Click to collapse
SweStag said:
Setting connection to 3g is not a solution, but a workaround. For those of use who actually use LTE/4G, that's not really an option.
I have this same issue, but I'm using Carbon ROM. So it would appear it is a CM-based issue that has carried over.
Edit: I was just in contact with my carrier Tele2, and this is a known issue with 4G/LTE systems. If you have this issue, contact your carrier, and they can likely help you sort it out.
Click to expand...
Click to collapse
Anyone that is still experiencing the issue please follow this link and vote this subject up.
https://jira.cyanogenmod.org/browse/BACON-3371
This is the bug log for Cyanogen and they just escalated the issue to critical.
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here