I just wanted to mention an issue that my S8 started having after i upgraded to Oreo. I was unable to make or receive any calls. As soon as i tried to make a call, it immediately ended the call and any incoming call would go straight to voicemail. After playing around with settings, i disabled the Enhanced LTE option and i was able to start making calls again. This setting is only for HD Voice so its not a huge loss. I'm not sure if anyone else has run into this issue but I wanted to mention it to the community. I had tried to reset Network settings and cleared cache to not avail.
I should note, i have not tried to do a factory reset because i was hoping that would be a last resort so its possible that would fix the problem all together but I talked to the tech at the AT&T store and he said he wasn't aware of this issue. If anyone else runs into this issue, feel free to comment.
Matt
lewbrah said:
I just wanted to mention an issue that my S8 started having after i upgraded to Oreo. I was unable to make or receive any calls. As soon as i tried to make a call, it immediately ended the call and any incoming call would go straight to voicemail. After playing around with settings, i disabled the Enhanced LTE option and i was able to start making calls again. This setting is only for HD Voice so its not a huge loss. I'm not sure if anyone else has run into this issue but I wanted to mention it to the community. I had tried to reset Network settings and cleared cache to not avail.
I should note, i have not tried to do a factory reset because i was hoping that would be a last resort so its possible that would fix the problem all together but I talked to the tech at the AT&T store and he said he wasn't aware of this issue. If anyone else runs into this issue, feel free to comment.
Matt
Click to expand...
Click to collapse
I'm in the same boat. Any chance you figured it out? I completed a reset and still have the issue.
Thanks, James
Related
My calls are not saving to history. It will save calls to history, then if I soft reset it seems to not be able to save calls again until I clear the history. This is very annoying. I have an idea what may be causing it (maybe the file isnt closing correctly and its unable to access it on restart?), but im not sure. In either case it sucks to get 3 missed calls and not have any idea who called you. Not good for business. Any solutions folks?
I am running the latest HTC Cingular Update on a CID cracked h2o mini s. I had phone dashboard installed, but removed it, did not solve problem.
Thanks,
Josh
OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
First try a data factory reset, if that doesn`t help refash the stock rom with odin 3.09 and after that factory reset/wipe cache in recovery.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
Im having the same issue, i cleared the cache, did a factory reset and made sure s voice was turned off, it cleared the issue up for about a month. Recently i have been having this issue happen more and more. Im starting to think it may have something to do with the Bluetooth or the visual Voice mail / voice mail. Anyone else have any ideas on what else to try or do ? The only problem is recreating the environment to cause it to happen. Right now its completely random.
Ok ive been pulling my hair out for a while with this problem so im really hoping you guys can give me some answers or suggestions to help me fix it My Girlfriend has the Galaxy S5 SM-G900V. Baseband version G900VVRU2BOG5 So rooting or custom ROMS is out of the question so that leaves me with trying to diagnose and eliminate this problem without a easy way out.
Ok the problem is once she updated the phone to lollipop she had all the common problems that come with it over time i have slowly eliminated them with factory resets and cache cleaning and such although i have one problem that not even verizon can figure out. The phone itself with occassionally and randomly just refuse to make or receive calls its a very odd problem because the phone will send and receive sms and mms just fine when this happens but when we try to dial out it just sits at dialing and never connects, when calls are dialed into the phone it will ring 5 times or so then go to voice mail or just go straight to voicemail altogether without ever ringing the s5 shows no sign of anyone ever trying to call at all no ringing no records nothing. Once in a blue moon it will ring 4 times on the dial in and then the s5 will start ringing around the 5th ring which is extremely long time IMO. This happens very randomly and in all different locations i have disabled call blocking and auto reject i have tried safe mode to only experience the same problems, i have factory reset several times. Verizon opened a ticket with there tier 2 techs and network development team to check out the issue they tell us everything is completely fine and theres nothing they can see wrong. But they do not deny the problem is there they just cant explain it. Now get this, This is the second phone that has done this to her Ther first one had the same problem and was warranty claimed this is the second phone and same exact issues. Im not sure what else i can do i am a very tech savy person and this one has got me stumped the only thing i can see thats odd for me is the phone has 3 Phone services running in the background But I believe this may have something to do with the Touchwiz Easy Or Regular Home UI althought im not sure why it would use seperate apps. Anyway any input would be helpful Thanks
Hi, I made some calls yesterday, woke up this morning and am unable to make or receive calls.
I've cleared the cache on the stock dialer app, installed another dialer, reset the network, but nothing so far has worked.
MMS and Data works fine, I also had my provider check the sim and it was fine on their end, I just cannot make phone calls. Has anyone come across this and can chime in?
X-Nemesis said:
Hi, I made some calls yesterday, woke up this morning and am unable to make or receive calls.
I've cleared the cache on the stock dialer app, installed another dialer, reset the network, but nothing so far has worked.
MMS and Data works fine, I also had my provider check the sim and it was fine on their end, I just cannot make phone calls. Has anyone come across this and can chime in?
Click to expand...
Click to collapse
Hi, this may or may not have anything to do w/ it but I have experienced this. What happened was I'm a little nervous about the 3g getting shut down & since no volte button like the v30 I was trying different things and to see if my phone would work I flipped the setting to turn off 2g, everything seemed fine or so I thought because I mostly text on this phone, don't care who calls & I don't call out often. When I realized I couldn't make or receive calls I switched the 2g back on & it worked immediately. I know that I as well as others I'm sure end up realizing random things in their settings are all screwed up, 1,2 or more & never changed that particular setting etc so just in case it's something to check out & see. It's under mobile network & the only toggle right there. Just in case u might still need help.