Here is an example... when using Google Maps Navigation on my EVO I will get a call, and I will answer it either via Speakerphone or Bluetooth.
My navigation will then give me an updating screen like it is trying to find the directions... at first I thought this was a NAV issue but then I noticed my mobile data icon dissapears and I noticed that my mobile data does NOT work AT ALL when I am on a call.
Is that normal behavior, or is it a problem? I thought it might be the ROM but I have tried this on both a stock based rom (Baked Snack and FRESH) and on CyanogenMOD...
I am trying to figure out if this is a HARDWARE ISSUE or if this is just normal par for the course and I never noticed it before...
Has anyone else experienced this?
Thanks,
Tim
that is normal with Sprint. You can only call and use data while on wifi.
Man... that sucks! It makes it hard to rely on the phone for nav as I have been doing when I need to get on a conference call or something during the drive... damn! So other carriers don't have this limitation? Like if I used Verizon or AT&T with an Android device this would work? (Just curious)
Thanks for the quick response!
Simple fact: CDMA (which Sprint, Verizon, etc. use) can only handle data or voice at once. There is a version which can do both, and Verizon is supposedly looking into rolling it out, but it would require tower, infrastructure, and phone upgrades, much like rolling out the LTE/WiMax networks.
Easiest solution to bypass this:
1) Make calls as VoIP. Will cut on your web browsing/navigation bandwidth, but at least makes it possible.
2) Be connected to WiFi. Voice will go over your cell radio, data will go over the WiFi network.
3) Be connected to WiMax. Same as WiFi.
You can only use wifi or wimax when on a call.
OK so this gives me a really good reason to flash over to something that I can use Wimax with... I will flash over to Fresh or something and try navigating with 4G on and make phone calls. Thanks for all the great info!! I love this forum
I don't know if it is normal but I don't think it is. I know you can't use voice and data at the same time on a CDMA network but today is the 1st time I've ever had nav shut down when on a call. I thought the nav program downloaded the route and then would reconnect if alternate directions were needed if you missed a turn or something. I've used nav and voice almost every day since I got the phone months ago and this problem has never happened before today.
motenak said:
I don't know if it is normal but I don't think it is. I know you can't use voice and data at the same time on a CDMA network but today is the 1st time I've ever had nav shut down when on a call. I thought the nav program downloaded the route and then would reconnect if alternate directions were needed if you missed a turn or something. I've used nav and voice almost every day since I got the phone months ago and this problem has never happened before today.
Click to expand...
Click to collapse
It has to pull the map pictures as you drive. Unfortunately, Google didn't allow for a large cache to be created on your phone.
Use the locations app in an hd port and download maps for your area. That way here is no need to use the internet for maps to have gps at all.
Sent from my PC36100 using XDA App
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 upgraded to the Galaxy S III from the Vibrant. I had no problems with my Vibrant making or receiving WiFi calls on the secured WiFi networks at home and at the office. However, I am having serious problems with WiFi calling on the S III.
I can make calls (most of the time) and can send and receive texts in WiFi but I cannot answer a call. The phone either does not ring and the call goes straight to voicemail or I hear the phone ring, answer the call and can hear the other party, but they cannot hear me.
I called tech support who had me do a factory reset. That worked briefly, but within 24 hours, I was back where I started. My 911 location situation is sorted, so that is not the problem. I am also close enough to the routers that I do not believe that is the problem either.
My first suspicion was a bad sim card but another co-worker of mine who also has an S III cannot answer WiFi calls in the office either. Now, I suspect some network security issue is causing the problem on both networks I regularly use, but do not understand why considering my Vibrant had no problems at all.
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
tiisai44 said:
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
Click to expand...
Click to collapse
The other thing that happens when people call me is that the phone will ring once and then go to a busy signal.
I went to a T Mobile store and replaced the sim card. They also made some test calls to my phone without success. I also upgraded the firmware on my home wireless router. In the end, nothing worked and Tech Support is sending me a replacement phone.
My replacement phone arrived and it initially did not work either. After several hours of experimenting and getting results that weren't always easy to duplicate I have reached the following conclusions:
1. There was indeed something wrong with the original phone.
2. Both phones could answer WiFi calls straight out of the box, but as soon as I altered the Setup or downloaded apps, they wouldn't.
3. I strongly suspect that either the power saving settings or the voice cmd for apps settings are incompatible with receiving WiFi calls. I could not determine that any individual app caused a conflict. When I ran into troubles with the replacement phone, I could restart it and get it to work after altering the phone's settings. I never could get the original phone to do so, however.
4. WiFi calling is still wonkier than it should be compared to my Vibrant. I am still getting calls that go straight into voice mail without the phone ringing, or the caller will hear my phone ring once or twice before it goes to a fast busy signal. I at least feel comfortable that if I hear the phone ring I can answer it, where I couldn't do so before.
Whenever I'm using any Wifi to make a phone call, my voice is not projected. I can hear the other person completely fine and otherwise, my phone is completely functional. Once I make a video call, my voice is projected fine and the other person is able to hear me.
I've tested this with multiple apps such as Skype, Vonage, and Kakao Talk. The only other app where I've used "phone call" and have had my voice heard was Tango.
I'm unsure of why this is which is why I'm asking here in the Q&A.
Could it be that there's something wrong with my phone from the get-go and I should just convert back to stock and talk to AT&T about this? Or is this a problem that other SG3 users have seen with their phone, or with the AOKP JB Build, although I don't think it's the build since other users haven't reported this issue.
Specs of my phone:
SG3 AT&T- Refurbed
AOKP JB Build 10.28.2012
Suggestions or ideas?
dragonxero13 said:
Whenever I'm using any Wifi to make a phone call, my voice is not projected. I can hear the other person completely fine and otherwise, my phone is completely functional. Once I make a video call, my voice is projected fine and the other person is able to hear me.
I've tested this with multiple apps such as Skype, Vonage, and Kakao Talk. The only other app where I've used "phone call" and have had my voice heard was Tango.
I'm unsure of why this is which is why I'm asking here in the Q&A.
Could it be that there's something wrong with my phone from the get-go and I should just convert back to stock and talk to AT&T about this? Or is this a problem that other SG3 users have seen with their phone, or with the AOKP JB Build, although I don't think it's the build since other users haven't reported this issue.
Specs of my phone:
SG3 AT&T- Refurbed
AOKP JB Build 10.28.2012
Click to expand...
Click to collapse
dragonxero13 said:
Suggestions or ideas?
Click to expand...
Click to collapse
I've never tried any app for WiFi calling besides Talkatone, but it works fine over 3g and WiFi for me using my Gvoice number. Could be that those apps are not fully functional on JB yet. It hasn't been out long and you know how app devs are with Android. If not, they usually help us after iPhone, but before WM.
Edit: My suggestion: Try Talkatone.
Hello. Maybe someone seen something similar and has a solution.
My Note 3 immediately drops all signal to almost nothing the moment WiFi connects. Where I am, I have 4 bars with LTE on. Once I enable WiFi and connect to AP, signal goes to zero bars.
Initially I thought it's cosmetic. But after some testing, I realized that it is not. About 40% of all calls go to voicemail. When I do get a call that comes through, if it's HD voice, I sound to them like latest T-Pain's album, like I am being auto-tuned. When it's not HD voice, it's simply breaking up.
WiFi calling does not kick in.
And weirdly enough, it's happening to my girlfriend's Nexus 5, also on T-Mobile.
Stock rooted.
Baseband N900TUVUBMI7
Kernel 3.4.0-1670611
SIM and region unlocked with Chainfire's utility.
Any help would be greatly appreciated.
There was a thread in here about that, from what I read when you turn on wifi the data pretty much shuts off as far as 4g/lte. This is how it comes out of the box, a least for 4.3 I'm sure is the same on 4.4. Will look later on tapatalk and searching sucks.
Sent from my SM-N900T using Tapatalk
voice sounds bad as well, other person kept saying they could barely hear me
I figured the mobile data will be pretty much disabled. But that does not explain why voice problems would pop up.
Meanee said:
I figured the mobile data will be pretty much disabled. But that does not explain why voice problems would pop up.
Click to expand...
Click to collapse
See my post at the end of this thread (http://forum.xda-developers.com/showthread.php?p=50514889#post50514889). It should solve the problem.
rahulisola said:
See my post at the end of this thread (http://forum.xda-developers.com/showthread.php?p=50514889#post50514889). It should solve the problem.
Click to expand...
Click to collapse
Awesome, that worked right away. No more robotic sounding, breaking up calls.
Now I need to find out why it's happening on my gf's Nexus 5, which does not have WiFi calling.