I have enabled simultaneous connections for Voice & Data in my ROM by editing the 'ContextNumber' values in the registry.
Code:
[HKEY_LOCAL_MACHINE\Software\OEM\\RIL\OperatorContexts\23415] ;Vodafone UK
"GPRSContextNumber"=dword:3
"UMTSContextNumber"=dword:3
This seems to work, to a degree but I am not sure about some of the behaviour. I have my data connection set to permanent as I use Exchange ActiveSync for work as well as MS Office Communicator Mobile 2007 R2. I have a 2nd data connection for MMS but this is hardly ever used and only for MMS anyway.
If I am on a call and an email arrives I hear a notification and if I quickly look I can see an email has been received whilst the call is still in place. If the call is short then everything seems fine, however if the call is for a few minutes or more then typically my OCS presence status gets messed up and the connection to the OCS server gets broken. The data connection is still in place but there seems to be some breakdown of sending/receiving data whilst the voice call is connected for more than a few minutes.
I am struggling to troubleshoot this and was wondering if anyone else has issues with simultaneous voice & data calls?
Andy
generally it's not a phone thing class A gsm phones all support it
but if your phone operator don't have full support in their end
there is not much you can do
read about it here
http://en.wikipedia.org/wiki/General_Packet_Radio_Service#Hardware
every htc phone I had supported it fine without any reg changes
Rudegar said:
generally it's not a phone thing class A gsm phones all support it
but if your phone operator don't have full support in their end
there is not much you can do
read about it here
http://en.wikipedia.org/wiki/General_Packet_Radio_Service#Hardware
every htc phone I had supported it fine without any reg changes
Click to expand...
Click to collapse
No, that's the thing it does work and I can receive emails via the data connection when I am on a voice call. It just seems after the voice call is active for more than a few minutes then there is some communication breakdown, however the data call remains active.
Andy
Updated! Now works on 4.2! Updated!
Hi All-- I really miss Tmobile wifi calling, and I have finally put together a system which works for me...so I thought I would share it if anyone is interested.
It works about as well as Wifi Calling did on my Tmobile Gs2.
I have found this to have two main benefits over the Groove IP method put together by codesplice here: (note: all credit goes to codesplice--he did the heavy lifting on this..I just modified his approach)
1) the call quality is a LOT better. a LOT LOT LOT better. Groove IP sucks.
2) with this method, calls will still ring through to your gmail (assuming you have it set up that way in google voice)
Download these apps to your phone:
CSIPSimple
Google Voice
Google Voice Callback (donate) (you can get it from the amazon appstore...not on the play store anymore for some reason)
Tasker (you need the newest beta, available here http://tasker.dinglisch.net/beta.html )
Secure settings
Download this file, unzip it, and put the files on your phone's SD card (tasker profiles):
https://docs.google.com/file/d/0B4nxPgKYHIDjbVN1b3IzNC0wd1E/edit?usp=sharing
Instructions:
1) Go to Callcentric.com and sign up for a free account. Write down your SIP number that it gives you (it will start with 1777)
2) also in callcentric, sign up for a free phone number. If you say that you live in the us, you have to pay for 911 access....
3) Open CSIPSimple on your phone. It will pop up with some questions about when you want it to work. I have mine set to ONLY be in use when I am connected to a wifi network. Then add an account. It will have an option for callcentric. Do that and sign in with your callcentric account (username is the 1777 number again).
4) Go to voice.google.com on your computer, go to the settings page, and add the new phone number that you got from callcentric (the phone number, not the 1777 number). It will call you to confirm the number...it should ring through to your phone! (note: under your regular cell number, choose 'edit>advanced>make sure that "Ring my other phones before going to voicemail " is checked)
--You have now set it up for incoming calls. If that's all you care about, you are done! Any call made to your google voice number will ring through to your phone via wifi calling.--
Now we're going to set it up to make outgoing calls
5) Open Google Voice Callback. Sign in with your account. In the settings, choose your new callcentric phone number as the callback number. That's it! you're set! now when you initiate an outgoing call, it will ring back to you, and you are good to go for free wifi calling!
--If you don't care about automating it, you can stop now.--
We're now going to set it up so that it works like WIFI calling, meaning that it a) turns on when connected to a good wifi network, b) turns off your cell radio when connected so you're not wasting battery, and c) it turns off automatically when you are not connected to wifi. We will do this with the miracle of tasker.
6) Make SURE you are on the latest beta of tasker. It is required for this to work!
You can find the newest beta here: http://tasker.dinglisch.net/beta.html
DL this zip file that I put together with my tasker profiles, unzip the files and put them on your SD card. Open up tasker and long-press on the 'profiles' tab. Choose import, and then import them.
Ze hu! You're done! Please let me know if it works--and I'm happy to try to help if it doesn't.
If it works for you, please click 'thanks'!
----
Note--the tasker profiles were put together originally by codesplice, and all credit for them goes to him, not me. You can find his thread here: http://forum.xda-developers.com/showthread.php?t=1646755
----
The advantage of CSIPSimple over the native SIP client in JB is that CSIPSimple can be set to only operate when connected to wifi.
I hope this is useful for everyone--works great for me!
Sent from my Nexus 4 using Tapatalk 2
Just to clarify your method works only if someone dials the google voice number?
I mean that's fine, but I think a majority of folks are looking for T-mobile Wifi calling that ties in with their regular phone number and plan feature.
Re: [Guide] Wi-Fi Calling!
Your thread title is very misleading. Change it.
Sent from my Nexus 4 using xda premium
edit.. nevermind
I agree, the title should be called Voice Over IP. T-Mobile WiFi Calling is actually their product name.
But the guide is great! I use Google Voice too, but for my Sprint number because it is free full integration. But that's not really possible with T-Mobile, and its not free either. I just need a fix for my T-Mobile Nexus 4 so I can get service everywhere lol.
Re: [Guide] Wi-Fi Calling!
Op,
Welcome to n4 world. I saw your same post in nexus7 forum.
Your method may work well for n7 but not for n4 because of battery drain issue. Using this method over 3g, n4 will not last 12 hours. Its because callcentric doesn't support TCP.
IMO, this is only good for WiFi as the title suggests. But I agree that the title is misleading. When i first saw it, i thought you cracked tmo WiFi calling. OTOH, there are tons of threads on free WiFi calls.
There is another side effect for your outgoing calls. The callback method is equivalent to initiating a call from gv web app. Gv calls both parties. I have found that this adds close to .4 sec lag one way. Do an echo test at 909-390-0003. You will hear your voice after 1 second.
Sent from my Nexus 7 using Tapatalk 2
Issue with WiFi Calling Method
Please correct me if I'm wrong, but the major issue I see with this method is that it requires an active cellular connection for an outgoing call. For me (and I'm sure may others) the need is to be able to send and receive calls with no cellular coverage. Personally, with a lab/office in the basement of a building, having any coverage is not feasible, regardless of carrier.
Is there any workaround/alternate plan that would solve this issue?
Edit: At first, it was saying I needed to disable airplane mode, but once I reconfigured the CSIP and the callback app, it worked even on airplane mode. I guess the GV Callback (now called Voice+ in the Play Store) intercepts the call and initiates the callback via WiFi.
Thanks for the guide. This will work as a workaround until TMO Wifi Calling gets ported to the N4.
I use talkatone, really good sound quality
Sent from my Nexus 10 using XDA Premium HD app
I use Skype, $3 per month for unlimited US and Canada calls. For outbound calls and text you can use your own phone number. For inbound you can not, but you can probably set up some kind of redirection. I never gave it a thought, because I never needed it
So no one has an alternative to WIFI calling?
By this I mean, being able to recieve calls from anyone with my phone number just like TMo Wifi calling when I don't have any mobile signals?
edo101 said:
So no one has an alternative to WIFI calling?
By this I mean, being able to recieve calls from anyone with my phone number just like TMo Wifi calling when I don't have any mobile signals?
Click to expand...
Click to collapse
I setup call forwarding when not reachable (**62*PhoneNumber#) to my google voice/hangouts number. I don't have too many opportunities to test this, but it seems to work.
voland66 said:
I setup call forwarding when not reachable (**62*PhoneNumber#) to my google voice/hangouts number. I don't have too many opportunities to test this, but it seems to work.
Click to expand...
Click to collapse
So how does that work? It calls your phone number and when it seems you have no signla and therefore cannot be reached, it dials your google voice number when then dials your phone? Have you checked to see if it works when you have no tmobile signal?
I tested this in a couple of ways. First, I switched to airplane mode and turned wifi back on. I had someone make a phone call to my t-mobile number. It came through on hangouts, the quality was great etc. I think the calling party did not see a delay in the call being answered. Of course, I knew that the call was coming so I answered quickly; but I think t-mobile system saw that the phone is not registed with any tower and forwarded the call to google voice right away. I repeated this test at least a couple of times.
The second test was a "real" one, in a building which does not have t-mobile signal. This test was only a partial one because I was in a meeting, so I could not answer. But the phone rang (vibrated actually) and the calling party got a google voice answering machine.
I also had a couple more accidental, partial tests. There is a stretch of the road near my house where the phone switches between two towers, neither tower has a good signal and calls are dropped when I drive/walk through there. So I recently received two calls in that area. The calls came on hangouts; there was no sound when I answered but at least I got the call and caller's name. I think the following happened: when the initial call came the phone was in the dead zone and the call was forwarded to google voice. By the time it came through on hangouts, the connection was restored but was not fast enough for voip call. Now that I think about it, I got another accidental test at home -- while I have a good signal at home, on some rare occasions my phone does not ring; so recently a call came through hangouts while I was at home and everything worked fine.
I should mention that when I started doing this, I was under impression that the forwarding setting occasionally resets to default (no-forwarding) on its own. But now it looks like the setting stuck permanently and I don't need to check/reset it anymore.
Yes, use Google voice/google hangouts dialer.
Make and receive calls from google hangouts.
You can setup a google voice number for free as well. you can use it to receive calla directly and/or to call from.
https://support.google.com/hangouts/answer/6079055?hl=en
Sent from my Nexus 4 using XDA Free mobile app
Hi.
I've recently started having lots of difficulty when moving out of range of my home's wireless signal in the phone picking up and connecting to the Mobile Data network.
Specifically:
1) Run phone for ages at home using wireless
2) Walk out of house, out of range. Wireless connection goes unconneced
3) Wait for Mobile Network to connect, have at least 3 bars of signal - fails, no E/G/H Sign, Network indicator stays white ( So far waited up to 3 hours)
4) Reboot Phone, instant Mobile Network Connection @ H
Things I have tried:
1) Turning Wireless off before leaving range of wi-fi, sometimes this works ( circa 1 in 20)
2) Turning Phone to Airplane Mode & Back - sometimes this works ( circa 1 in 15 ).
Turning Airplane mode on can take about 4 minutes, as though something is waiting for a closure timeout. Normally, this takes about 5 seconds.
3) Phone calls are intermittant during this time - sometimes I can make them, sometimes i can't.
4) While in range, turn phone off/on again so a "clean" boot, then walk out of range. No affect on ability to reconnect.
Check Phone Status under About Phone, the Mobile Network States reports "Not Connected"
It's really annoying, as I want to use the phone to during breakfast to check the latest traffic information and map updates from Google Maps before I leave home, then get in the car and go, not reboot the phone.
Has anyone else suffered a similar problem?
Phone Specifics:
Motorola Razr I XT890
Android 4.1.2 Stock
T-Mobile
Is there some investigative
Thanks!
I've had exactly the same issue on/off for weeks.
Not found a reason/fix for it yet, although I've been loath to do a full wipe with how busy I am atm.
6630 4682333
harryjan said:
I've had exactly the same issue on/off for weeks.
Not found a reason/fix for it yet, although I've been loath to do a full wipe with how busy I am atm.
Click to expand...
Click to collapse
Hmm.
At least we know we are not in the same boat, and a recent forum query on Engagdet highlighted others.
I've tried to capture a bug report to give me some logs to look at, but that's not working at the moment either !
Thinking it might be an "Always On" app related problem such as sykpe or amazon mp3 :S
I am on my second T-Mo LG G4. Both have exhibited a strange behavior that is rather annoying. I've disabled all automatic sync features and the like - in the same manner as I've done successfully with both a Nexus 5 and a LS990 G3.
So here's the issue(s):
1) Whenever I boot the phone - it automatically turns mobile on. e.g. as indicated by "Data Enabled" quick toggle or the Android Setup slider control.
2) Most times when I enable WiFi, the phone (or whatever) systematically turns on mobile data again - and it's damn repeatable e.g. at ~ 15 seconds after I tap the WiFi quick toggle.
3) Most times when I am running off of WiFi, the mobile data will randomly come on by itself even after I hammered it off that first time in response to manually turning on WiFi.
Zero technical assistance from the obvious sources. LG points the finger at T-Mo. T-Mo points the finger at LG.
I'm starting to think this is related to the Lollipop API change crammed down everyone's throat by Google.
I'm on metered service and have grown accustomed to living off of WiFi. With prior phones I was in full control of what I've been charged. With the G4, it's nearly impossible to manage ...
Any thoughts, shared experiences or recommendations ?
Hmm, there is a setting that can automagically use LTE if the Wifi is detected not to have internet access. I can't think of what it's called at the moment but it's in setting somewhere - possibly WIFI settings.
I would also be sure to disable T-Mobile's "diagnostics" setting in the T-Mobile app and attempt to turn off any other monitoring settings contained within. I think there is a setting that monitors the LTE signal strength and that could be making it pop on.
Other than that, it does seem rather annoying for you! You are on T-Mobile though, didn't you get the 10GB data pass and have the unused data rollover? Another note, why not setup the data limiter in Data Usage to automagically turn off the data after X GB usage. I know it isn't a direct solution but if data usage is a concern, it could work as a workaround!
Hey, thanks for the response and suggestions.
To be clear, I'm on Ting's GSM network - which is serviced by T-Mo.
I'm well versed with Android and prior to this phone I was on a Nexus 5 with 5 .1 .1 and it didn't behave like this.
I've tried all the buried settings to get in front of "enabled" data on two different G4's but nothing is panning out.
And yes, I did think of that T-Mo diagnostics app and it's not enabled - at least not on the surface.
And one more thing, my WiFi is solidly connected when data goes rogue robot.
Hadn't considered the data cap setting. Seems clunky but might help until a custom ROM is available.
rockerrock said:
Hmm, there is a setting that can automagically use LTE if the Wifi is detected not to have internet access. I can't think of what it's called at the moment but it's in setting somewhere - possibly WIFI settings.
I would also be sure to disable T-Mobile's "diagnostics" setting in the T-Mobile app and attempt to turn off any other monitoring settings contained within. I think there is a setting that monitors the LTE signal strength and that could be making it pop on.
Other than that, it does seem rather annoying for you! You are on T-Mobile though, didn't you get the 10GB data pass and have the unused data rollover? Another note, why not setup the data limiter in Data Usage to automagically turn off the data after X GB usage. I know it isn't a direct solution but if data usage is a concern, it could work as a workaround!
Click to expand...
Click to collapse
I am having issues with receiving notifications on time over Wi-Fi after screen was turned off for 10+ minutes. Usual delay is about 5 - 10 minutes. I don't have any problems with same applications and scenarios over mobile connection. These apps are chat and video call apps: WhatsApp, Viber, Duo, Slack. This is especially annoying for calls, because I just get missed call notification (after 5 or so minutes or if I manually launch the app), instead of a call ring. I ticked all of them off in "Optimise battery usage" section. Same behavior on Oreo and now on Pie version. Same behavior on my home network, my parents' house network and at my work place. Browsing, streaming and all other things over internet work, no issues with it, so the connections were good. I have SMN960F model, if that matters.
At first, I thought this issues are caused by Doze when the phone is in "Connected to Wi-Fi" state. I don't even know if Doze could distinguish those two states (Connected to Wi-Fi or Connected to Mobile). But since everything works just fine over mobile, I doubt it is Doze. Now I think it is something related to my Wi-Fi settings, but I can't figure it out.
@Japro
Did you ever figure this out?