Related
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Anyone else have any wificalling issues?
My issue is more on loosing connection to the server while the phone is in asleep. the wifi connection is not lost just the connection to the server is lost and then my battery gets lost on locating connection.any ideas on that ?
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
word for word same issues im having, also 2 different routers.:crying:
Although I am not certain if this problem exited before rooting and flashing my phone, my WiFi Calling has not been working. I can place the call, but I cannot hear it ring or hear anything when calling. I can receive calls, but once I answer, I cannot hear anything. I am able to receive text messages normally.
I have resorted to switching to the cellular preferred only option. I hope there will be a remedy for this issue.
I'm on the FreeGS3 R3 rom with stock kernal.
d0gan said:
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
justice26 said:
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
I am running Whitehawks STOCK TVALUEM999 ROM with none of these issues. I am only on wifi as thats all I have available and I do not have an issues. It's possible that the removal of all the T-Mobile Bloatware, or some Mods done could be causing this. I have great battery life on that ROM and everything works fine. I am excited about this ROM, but am waiting to see another release come out and see how that works. ALSO, get ROM Manager, update to the newest CWM and try a data/dalvick cache, factory reset and install from zip from internal SD. Let me know how that works out
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
rowan fire said:
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
Click to expand...
Click to collapse
I am not sure if what to tell you, but I am in Afghanistan with the Samsung GS3 rooted, and I do not have a single issue with call quality with some of the crapiest internet connections you can ask for.. No echo, no dropped calls. Your internet connection quality can make a difference, when you make phone calls, any downloads going on can hinder the quality, also the type of router u have makes a difference. A wireless N router with 300MBS per second would be ideal...
It doesnt matter if your are using Touchwiz, the rom you are using matters, no other threads are stating this issue. I suggest you try another rom like redruM cause he just released a new update today, or Whitehaws STOCK. It performs great and has CIQ removed, zipalign on boot, some T-Mobile bloat removed, no force closes on any apps and good battery.. It doesn't have the crazy scripts and 4 in 1 reboot, however, if u dont care about that and you want stable and root, its a good option
According to T-Mobile technical support, they have escalated the issue of wifi-calling and wifi connectivity issues to Samsung and supposedly there is a team working on this. Supposedly they will be doing an over the air update.
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
No wi-fi calling
MMakoto said:
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
Click to expand...
Click to collapse
TMo - GS3
My phone is and has not ever been Rooted. I'm having the same issue that when wi-fi calling is active, if I receive a call, the caller cannot hear me, and then the app. hangs for a minute when I hit end or the caller hangs up. I tried it on a couple networks. I thought I was able to make wi-fi calls, but that seems to not work all the time, either.
I believe this is the first TMo ICS phone, right? I had a 4.0.3 custom (Passion) ROM on my Vibrant (GS1), but since there wasn't ICS TMo phone, there was no wi-fi calling app. on it.
I called T-Mo support and told them I found this thread with other users with the same problem, but they didn't say anything was in the works. Samsung support gave me their usual answer, of doing a factory reset, reinstalling and reconfiguring everything (yeah right).
I get the hang sometimes and I also get the problem of people not being able to hear me when I pick up. Annoying. I got rid of my amaze after the ICS update because it screwed up wifi calling(delay in voice 5-10sec). Piss poor. Wish it worked better because I don't get a cell signal in my house.
To get rid of the voice echo - disable the noise cancelation during a phone call in the in call menu. The noise cancelation uses two mics but unfortunately picks up the noise of the speaker as well, causing the echo effect.
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
jknakes said:
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
Click to expand...
Click to collapse
You have to have them add the free WiFi calling feature to your plan and then they don't count. Just tell them you want your minutes on wifi to be free. There is no extra charge after they add that code.
Sent from my SGH-T999 using xda app-developers app
I'm having the same issue, wifi calling does not work. No one on the other end when I answer incoming calls. Can't connect out.
For me it works sometimes and sometimes it doesn't I just turn it off, I use 200 minutes so far this month and today is the last day so I'm good with 500 minutes plan
Sent from my SGH-T999 using Tapatalk 2
Did any of you with the wifi calling problem install Skype? My first phone had the problem of no one hearing me and freezing when hanging up. I ended up returning it to Tmobile for another phone.
Right before I returned the old phone I did some testing. I flashed it back to stock and it didn't fix the problem, but when I wiped the data and cache in download mode, it seemed to help with the wifi calling, not sure how consistent it worked, but at least for the first call I can hear them and vice versa.
So I'm thinking something I installed may have played a factor, and right now my suspicion is that it's skype. I haven't installed it on my new phone since I don't want to screw the wifi calling on there.
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
And now it has happened 3 days in a row but at different times of day. This is a huge problem for me as I use my phone a lot. Any help would be appreciated
You still have your IMEI number via settings -> about phone -> status?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ARPLEMODE
TRy making sure yiur not in airplane mode. i was stuck in airplane for a week ._____________.:cyclops:
That's weird. Re-seat your SIM card, if that doesn't do anything then take a trip to your nearest AT&T store/dealer and have them swap out your SIM card and see if it still occurs after that.
I had a similar problem a while back and it happened to be a network problem with my carrier. Gave them a call and all is fine now.
Sent from my SGH-I747 using xda app-developers app
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
It happend to me too. I went to att store and get new sim. No problem for last 15-20 days. Looks like i got stronger signal too.
Just to give anyone interested in this an update:
I went to the AT&T store today and told them my issue so they told me to go to the nearest AT&T device support center (which was really far away). People over there told me they heard about this issue many times over the past couple of months. The guy working there had a S3 and said he has the same problem. They received an email from the higher-ups this morning specifically talking about this random outage thing I have and that they are currently working on it. They were told to not exchange phones or sim cards because of this since it wont help. The issue involves a combination of Network and Jelly Bean software problems and happens on all new LTE devices that have Jelly Bean from AT&T. They told me to check periodically if there is a solution.
I guess I just gotta wait. Unless someone recommends a ROM that is not based on the latest AT&T jelly bean?
Bumping it up, both me and my wife have had this happen. From what im read its a pretty widespread deal.
Anyone know of a work around at least until they fix it?
Keep us updated
Same problem here - switched from Verizon to AT&T last month and started noticing this problem a few weeks ago. Back then a Google search didn't find much on it, but this thread looks promising.
Just to add my two cents: I'm on a rooted S3 with task650's AOKP (4.2.1) build 12.23.2012 (link). Made sure to flash the modem for my phone (I747UCLI5 from here). Problem: phone randomly won't receive calls or texts. Sometimes calling someone will fix it.
I read somewhere that on AT&T, calls and texts are received over 3G and sometimes phones have difficulty switching from 4G. Anyone know if this is true?
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
I had this same problem except it would only happen on WiFi.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
thatsupnow said:
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
Click to expand...
Click to collapse
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
mrmooney said:
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
Click to expand...
Click to collapse
Care to share what you did that fixed it?
fafik90 said:
Care to share what you did that fixed it?
Click to expand...
Click to collapse
Yeah more info here.
http://forums.att.com/t5/Android-Di...ing-Calls-Phone-issue-or-Android/m-p/3404809#
Seems to still be working fine.
I started a thread on this also and just yesterday received some info from AT&T tech.
http://forum.xda-developers.com/showthread.php?t=2123974
guys,
it is an ATT issue,
here is a temp solution for a fix:
1) With phone on, take off back cover and press your SIM card so it releases from the spring. It won't come all the way out as it's blocked by the battery. This seems fine - I didn't bother trying to force it out as I didn't want to break anything...
2) Once you see the message that the SIM card is removed, go to the dialer and dial *#2263#
3) You should see a menu with band selections. The current setting is "Automatic". If you switch to "GSM All", you will be EDGE (2G). If you switch to "WCDMA All", you will be on HSPA+ (3G, though AT&T and others call it 4G).
4) Press the SIM card back into place until it clicks. For whatever reason the phone will not recognize it until you reboot. Upon reboot you should see your new setting in effect
please see, post, comment here:
http://forums.att.com/t5/Android-Di...ls-Phone-issue-or-Android/td-p/3270741/page/3
Myself and three others are experiencing the same issues with our GS3's and was wondering if anyone else has had these issues.
1. When trying to place a call most times it tries to dial then hangs up and goes to the lock screen.
2. When #1 does not happen it take 3-4 times of retying the number before actually ringing. Tried from different towers same thing
3. The keyboard does not keep up with the typing it often takes a while for it to work
4. When tethering with paid subscription and I try to place a call the data stops working.
Anyone else have these issues?
94loranger said:
Myself and three others are experiencing the same issues with our GS3's and was wondering if anyone else has had these issues.
1. When trying to place a call most times it tries to dial then hangs up and goes to the lock screen.
2. When #1 does not happen it take 3-4 times of retying the number before actually ringing. Tried from different towers same thing
3. The keyboard does not keep up with the typing it often takes a while for it to work
4. When tethering with paid subscription and I try to place a call the data stops working.
Anyone else have these issues?
Click to expand...
Click to collapse
Very interesting that you bring this up. I recently have been suffering from the following:
1.) When trying to place a call it tries to dial and hangs up. I usually have to try 3 times before I can get the call to go through or have to soft reset
2.) A LOT of my friends have told me that when they try and call me it will only go through about half of the time. Sometimes the get "The ATT customer is unavailable", other times it will just beep at them, and finally it will go through but not ring on my phone.
3.) Same keyboard issue. I found that if I turned off all the auto correct and predictive text that it helped, but I will still get a lag issue once in a while.
Comments- I thought it was just my original GS3 that was starting to crap out so I did a warranty exchange, and the same symptoms keep happening. I also got a new SIM card, but that has not helped out either. One AT&T Tech rep told me there were major tower issues in my area, but then another I spoke to said there were none.
Now I dont know if I should ask for a new GS3, go to a different phone or what.
Yup. My keyboard freezes up once in a while, also I get " unfortunately music player has stopped" while connected through bluetooth. I usually just re open music player and it works fine.
Sent from my SGH-I747M using xda app-developers app
Yeah, we all have the same issue when people try to call us and they get "The ATT customer is unavailable". Also one more thing I forgot to mention is that I sometimes try to call a number and get a pop up that says Emergency Calls only.
Not sure what to do at this point but getting very frustrating.
I've definitely had the keyboard lag pop up. Only solution I've found is to turn off the phone and back on. It seems to do OK for a few days then at least.
just got back from an ATT store. A girl there confirmed that its related to the JB update for the GS3 and for the Note 2. She has the Note 2 and said its much better than the issues with the GS3 but it still has inbound and outbound calling issues. It has to do with how the phone (maybe modem related) switches from LTE to 4g.
Customer service offered to send me a Note 2 for $100 and let me keep my GS3. I might do that and sell which ever I dont like better.
Yeah I went to the ATT store as well and was told that this is a known issue and that Samsung is working on a fix but there is no ETA. Wish they offered me a Note 2 for $100.
94loranger said:
Yeah I went to the ATT store as well and was told that this is a known issue and that Samsung is working on a fix but there is no ETA. Wish they offered me a Note 2 for $100.
Click to expand...
Click to collapse
doesnt help much since the note 2 has the same issue.
iceman4357 said:
just got back from an ATT store. A girl there confirmed that its related to the JB update for the GS3 and for the Note 2. She has the Note 2 and said its much better than the issues with the GS3 but it still has inbound and outbound calling issues. It has to do with how the phone (maybe modem related) switches from LTE to 4g.
Click to expand...
Click to collapse
It seems that the switching between LTE and 4G due to a call is causing multiple issues. From what I have seen issues extend not just to these problems but also random battery plummets for some. The "switch" somehow does not work correctly hardware wise for some phones. Under JB it seems to break at times for receiving and making phone calls. I hope they find a way to make LTE work as a voice line as well and update accordingly so the switch does not have to occur.
I have searched for over 2 weeks now online for a fix, I am on phone number 3 and sim card number 3. My phone, at least once a day, send all phone calls to straight to voicemail (showing no missed calls), texts do not come in etc. When this is happening, I show full bars and 4G. My wife is using my old Galaxy S and her works fine (not the network being down). If I restart my phone, I will get my missed texts and voicemails and I will receive calls as normal for a little time.
I have factory reset several times, as above, I am on my 3rd phone (2nd refurb that was probably sent back for this issue), 3rd sim card, I make sure I'm not in airplane mode, auto block calls are off, call forwarding is off, not connected to WiFi calling.
I am at my whits end, I'm about to send this great Galaxy S3 back and switch to maybe a Nexus 4 (granted I've seen all JB phones with this same issue) to see if I can just get a phone that works...like a phone.
Has anyone figured out yet why this occurs? Alot of people said it started with the upgrade to JB. Has anyone found a fix for this thing?
Also, would rooting and tossing on a custom rom fix this?
Please help, thanks in advance!
Geisty said:
I have searched for over 2 weeks now online for a fix, I am on phone number 3 and sim card number 3. My phone, at least once a day, send all phone calls to straight to voicemail (showing no missed calls), texts do not come in etc. When this is happening, I show full bars and 4G. My wife is using my old Galaxy S and her works fine (not the network being down). If I restart my phone, I will get my missed texts and voicemails and I will receive calls as normal for a little time.
I have factory reset several times, as above, I am on my 3rd phone (2nd refurb that was probably sent back for this issue), 3rd sim card, I make sure I'm not in airplane mode, auto block calls are off, call forwarding is off, not connected to WiFi calling.
I am at my whits end, I'm about to send this great Galaxy S3 back and switch to maybe a Nexus 4 (granted I've seen all JB phones with this same issue) to see if I can just get a phone that works...like a phone.
Has anyone figured out yet why this occurs? Alot of people said it started with the upgrade to JB. Has anyone found a fix for this thing?
Also, would rooting and tossing on a custom rom fix this?
Please help, thanks in advance!
Click to expand...
Click to collapse
I would trying odin with the latest stock ICS image. See if that helps first! Its UVALJ4....heres the link
http://forum.xda-developers.com/showthread.php?t=1949687
mattedwards2686 said:
I would trying odin with the latest stock ICS image. See if that helps first! Its UVALJ4....heres the link
http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse
I could give that a try, but I really don't want to go back in versions, I love JB and don't see the point in wasting money on a new phone when I could have gotten one for free or cheaper that uses ICS.
Thanks
I was having the same issue. However, mine was just blocking one person. I check under the persons contact info, you can hit menu and select reject calls. I then checked under Call Settings (press menu while on the dialer), first option is Call rejection. You can turn this option on or off and add or remove numbers here. Hope this helps someone.
Occasionally, my Verizon Galaxy Nexus won't ring. It'll receive one phone call just fine, and then later, calls will go straight to voicemail. I've tried a factory reset, modem firmware update, and re-activating with *228, but the problem still exists. I'm on Page Plus. Any ideas?
Edit: I realize this is the wrong category...if a mod could move this to the Q&A section that would be great.
I thought *228 didn't work on LTE phones, but I might be wrong on that.
In any case, are you somewhere with marginal reception? Do you live in an old house made out of some strange material that might be blocking the radio? If you have access to another, more reliable phone, can you try calling your phone when it's in different states (awake, asleep after idle timeout, asleep after forcing sleep, etc) to see if one of those is causing it to shut off?
tumadre0 said:
Occasionally, my Verizon Galaxy Nexus won't ring. It'll receive one phone call just fine, and then later, calls will go straight to voicemail. I've tried a factory reset, modem firmware update, and re-activating with *228, but the problem still exists. I'm on Page Plus. Any ideas?
Edit: I realize this is the wrong category...if a mod could move this to the Q&A section that would be great.
Click to expand...
Click to collapse
rearden888 said:
I thought *228 didn't work on LTE phones, but I might be wrong on that.
In any case, are you somewhere with marginal reception? Do you live in an old house made out of some strange material that might be blocking the radio? If you have access to another, more reliable phone, can you try calling your phone when it's in different states (awake, asleep after idle timeout, asleep after forcing sleep, etc) to see if one of those is causing it to shut off?
Click to expand...
Click to collapse
It does if you dial *228# Nope, I have another phone also on Page Plus that rings just fine. I also have full bars on my Galaxy Nexus and have no problem receiving texts.
Same problem here. I learned to accept it'
Fixed it! Turns out this was a phone programming issue. To get it working,
I flashed the "toroplus_for_toro_full_radios-FC12.zip" zip found on the "CDMA Gnex Flashing thread". This wiped out all the CDMA settings on the phone for me.
Next I flashed "vzw_jdq39_radios" to get the LTE radio back to VZW, and then flashed "toroplus_for_toro_cdma_radio-FC12.zip".
The Sprint ROM I'm running then stopped saying "No SIM Card", as expected, and was ready for programming. I dialed *22890# - note the hash at the end - to get the phone to OTA program. After programming completed, the phone received calls just fine! I just had to get data set up at this point, so I connected the phone to ETS, set the active profile to 1 (no 3g, only 1x speeds) and entered "vzw" as the HA and AAA passwords. Voila! 1x, text, and talk works great now!
Hopes this helps someone stuck in the same boat as me.
TL;DR: speaker button in phone app.
I had a similar problem with a simpler solution.
I have a Nexus 1 with largely factory software. The notification sounds, music playing, and phone ringer recently just stopped working. None of the system settings fixed it. Rebooting the phone did not fix it.
After a while poking around I discovered that I had left speaker button on in the telephone app. Apparently it's persistent. I turned off the speaker button there, and everything started working again. So try that first.