Develop Bugs

[Q] Wifi Calling

Please don't spam me if I say something stupid, Im just a noob here. Also don't spam me if I post in the wrong thread. (only in the epic forum will I ever have to leave something like that before a normal quesiton/post)
Okay, so I saw this on the xda news thingy. http://forum.xda-developers.com/showthread.php?t=1142448 . Someone on the vibrant forums was able to get wifi calling working. Could this be ported to or work on our epics?

Looks promising, but I see some users are getting charged for land line minute usage and others not. Also see some grandfathered plans are being changed upon usage of Wifi Calling. This goes for T-mobile customers of course.
I currently make my Wifi calls with gv + sipdroid without have to deal with any of these hassles.
BTW - Running 2.2 Froyo, have not played to much with ginderbread integrated VOIP features yet.

I feel like ive heard of tmobile being one of the only carriers with wifi calling... But im not sure, maybe we cant do it and they can but it was disabled... Just my 2¢
Sent from my SPH-D700 using XDA App

T-Mobile WIFI Calling

Anybody think it's possible to get T-Mobiles Wifi Calling working on an imported Galaxy Nexus? I want to import it but I rely on Wifi Calling at home.
Is it as simple as pulling the APK from a phone that has it or is there more to it?

I'm no Dev, but I've flashed enough roms on my tmous sensation to know that its more than just that .apk.

joeyklatzko said:
Anybody think it's possible to get T-Mobiles Wifi Calling working on an imported Galaxy Nexus? I want to import it but I rely on Wifi Calling at home.
Is it as simple as pulling the APK from a phone that has it or is there more to it?
Click to expand...
Click to collapse
No, there's a lot more to it.
The #1 thing that's going to be required is a radio interface layer that supports the necessary authentication calls to switch to GAN. This is assuming that the Kineto app and libraries work on ICS.
The thing that killed progress on the Nexus S was that we were never able to get a RIL that supported the necessary auth calls - and as a result it would never switch over to GAN, set up the tunnel, etc.
Kineto responded and blamed Google for "not requesting" support from the vendor for this feature. It's yet to be seen if it will work with the Galaxy Nexus. It's possible but I wouldn't count on it. Seeing as how the RIL is distributed as a closed source blob if it doesn't support it there aren't a lot of options.
At a minimum you need:
- A kernel with kineto_gan or gan-eth build in
- A vendor RIL that supports all of the auth calls to set up gan
- libganril, librilswitch and your vendor ril - librilswitch loads on boot and manages the handoff from the vendor ril (normal calling) to libganril (gan/wifi calling)
- Kineto app, libcryp98, modified libkineto that uses the local libcryp98 for ssl and tunneling.
- libaudio(I think) that has been modified to support the constructor called by kineto - it changed in Gingerbread and had to be modified to support the old call
- build.prop modified to use librilswitch, define the vendor and gan ril
It's been a while since I gave up on the port (After months of getting nowhere with Samsung or Kineto on a RIL and no RIL from other devices working on the Nexus S) so that list may be partially incomplete but it should at least give you a good starting point.

SO badly wish we could get it to work! It's the ONLY thing stopping me from purchasing and importing as I 100% rely on wifi calling at home.

lp1527 said:
SO badly wish we could get it to work! It's the ONLY thing stopping me from purchasing and importing as I 100% rely on wifi calling at home.
Click to expand...
Click to collapse
If you can't get service at home, is it possible for you to get a [email protected] that would allow you to use wifi calling transparently? I imagine T-Mobile would be willing to accommodate if you're a contract customer.

I work for T-Mobile and know for a fact that they now offer in home boosters, for people with low reception issues. You should try stopping by your local T-Mo store, or call Customer Care to inquire about it, because there are some restrictions, in regards to qualifying for it. Hope this helps!
Sent from my Galaxy Nexus

CM7 has this built in. Maybe CM9 will also.
I work in a dungeon and we have a cellular repeater in the hallway. It works well with Verizon and AT&T bands, but not so well with Tmobile. So I rely heavily on WiFi Calling while at work.
But since I'm upgrading my Verizon business blackberry to a Galaxy Nexus, I won't have to fool with it anymore.

player911 said:
CM7 has this built in. Maybe CM9 will also.
I work in a dungeon and we have a cellular repeater in the hallway. It works well with Verizon and AT&T bands, but not so well with Tmobile. So I rely heavily on WiFi Calling while at work.
But since I'm upgrading my Verizon business blackberry to a Galaxy Nexus, I won't have to fool with it anymore.
Click to expand...
Click to collapse
It does not have the GAN/UMA wifi calling they are referring to built in. CM7 has the built in Gingerbread SIP functionality.

krohnjw said:
It does not have the GAN/UMA wifi calling they are referring to built in. CM7 has the built in Gingerbread SIP functionality.
Click to expand...
Click to collapse
Exactly. CM7 built it in their roms, so hopefully CM9 will have it as well.
Probably won't happen until we start to see some Tmobile ICS phones with it included out of the box. The App is picky.
However I have heard that they are doing away with WiFi Calling (newer phones don't include it). I think they are moving to a new SIP platform and requires a new unreleased app.

player911 said:
Exactly. CM7 built it in their roms, so hopefully CM9 will have it as well.
Probably won't happen until we start to see some Tmobile ICS phones with it included out of the box. The App is picky.
However I have heard that they are doing away with WiFi Calling (newer phones don't include it). I think they are moving to a new SIP platform and requires a new unreleased app.
Click to expand...
Click to collapse
This only happens on some device specific configurations like the glacier. It's a moot point entirely if the RIL does not support the calls used by kineto like the Nexus S RIL.
Sent from my Nexus S using xda premium

Does anyone know how I can get T-Mobile "My Account" app to actually pull up my info?

Are there any updates to this request? Haven't seen it lately and wondering if anyone has new information. Wi-fi calling for Tmobile.

Not sure if its possible, but I would like this too. Would be a huge plus.
Sent from my Galaxy Nexus using xda premium

New2Houston said:
Does anyone know how I can get T-Mobile "My Account" app to actually pull up my info?
Click to expand...
Click to collapse
The app does not work on ICS. T-Mobile has said so.
Sent from Galaxy Nexus (GSM)

nxt said:
The app does not work on ICS. T-Mobile has said so.
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
I thought it works now.
At least it shows my data usage and minutes.

rome425 said:
I thought it works now.
At least it shows my data usage and minutes.
Click to expand...
Click to collapse
Oh I guess so, was updated March 25 and said now supports Android 4.0 ICS.
Didn't realize that. Good to know, thanks.
Just installed. Yep, fully supported, getting all the usage information.

krohnjw said:
No, there's a lot more to it.
The #1 thing that's going to be required is a radio interface layer that supports the necessary authentication calls to switch to GAN. This is assuming that the Kineto app and libraries work on ICS.
The thing that killed progress on the Nexus S was that we were never able to get a RIL that supported the necessary auth calls - and as a result it would never switch over to GAN, set up the tunnel, etc.
Kineto responded and blamed Google for "not requesting" support from the vendor for this feature. It's yet to be seen if it will work with the Galaxy Nexus. It's possible but I wouldn't count on it. Seeing as how the RIL is distributed as a closed source blob if it doesn't support it there aren't a lot of options.
At a minimum you need:
- A kernel with kineto_gan or gan-eth build in
- A vendor RIL that supports all of the auth calls to set up gan
- libganril, librilswitch and your vendor ril - librilswitch loads on boot and manages the handoff from the vendor ril (normal calling) to libganril (gan/wifi calling)
- Kineto app, libcryp98, modified libkineto that uses the local libcryp98 for ssl and tunneling.
- libaudio(I think) that has been modified to support the constructor called by kineto - it changed in Gingerbread and had to be modified to support the old call
- build.prop modified to use librilswitch, define the vendor and gan ril
It's been a while since I gave up on the port (After months of getting nowhere with Samsung or Kineto on a RIL and no RIL from other devices working on the Nexus S) so that list may be partially incomplete but it should at least give you a good starting point.
Click to expand...
Click to collapse
Spoke to 3 different TMO support (to make sure) . They all said the GNEX does support the new WIFI calling, however its all depend on google or samsung to incorporate it. They gave me a number to call Samsung (I dont have it with me right now) to request WIFI calling for GNEX

hoodred said:
Spoke to 3 different TMO support (to make sure) . They all said the GNEX does support the new WIFI calling, however its all depend on google or samsung to incorporate it. They gave me a number to call Samsung (I dont have it with me right now) to request WIFI calling for GNEX
Click to expand...
Click to collapse
I would love to hear some follow-up on this please

I know it's not a perfect solution but have you tried Bobsled calling app?
Sent from my Galaxy Nexus using Tapatalk 2

Another "not perfect" solution, But if you send your # to Google Voice, then there are a bunch of app's that can do Wifi calling very well. I use it while traveling overseas for work.

AOSP tether patch.

Has there been anything developed that can be applied to the stock ROM (rooted) to enable the AOSP tether, overriding Verizon's tether?
If not, why?
Is it a kernel issue? Can it be done on a stock ROM at all? Etc...
If you believe it to be possible, can you guide me toward information so that I can dive into this rabbit hole? I have background in development, though I've never touched Android, the OS, or the kernel, so I'm looking for a good place to get started.
I understand that I can just install a custom ROM, but that is not the answer to the puzzle I'm trying to solve.
Sent from my Galaxy Nexus using XDA App

http://www.droidforums.net/forum/galaxy-nexus-development/188611-official-wifi-tether.html

This is not AOSP tether. I have considered poking around in its source though.
As I remember it, my OG Droid needed a kernel modification to run android-wifi-tether where the Nexus doesn't. Figure it might be tapping into something existing.
As I said before, never played around with any of the dev stuff on Android, so feel free to correct my way out left speculation with fact.
Sent from my Galaxy Nexus using XDA App

hgray said:
This is not AOSP tether. I have considered poking around in its source though.
As I remember it, my OG Droid needed a kernel modification to run android-wifi-tether where the Nexus doesn't. Figure it might be tapping into something existing.
As I said before, never played around with any of the dev stuff on Android, so feel free to correct my way out left speculation with fact.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Confused - if it works, why does that matter? Just curious.

I see that devs have it worked out in their ROMS, so I wondered if it was available as a patch in the same way that battery percentage patches have been in the past.
The Android-Wifi-Tether is a good piece of software, but I figure that whatever is built into the OS is probably WAY more stable. I've always had problems with the software for one reason or another and I'm currently having stability issues on the Nexus.
I'm also interested to be able to learn more about how tethering operates on the backend because I'm currently having issues with my tethering speed.
http://forum.xda-developers.com/showthread.php?t=1436598
I could possibly avoid the speed issue by installing another ROM or trying to wipe and see if that fixes it, but that would not actually SOLVE the problem. I want to know why.
Note, should my speed issue go away I would still be interested in getting AOSP tether running.
TLDR; I'm curious too.

you should try this: https://market.android.com/details?id=com.koushikdutta.tether
it can't be blocked by verizon, and it's made by the creator of clockwork mod.

I did try Tether in an attempt to determine if android-wifi-tether was the culprit of my speed problems and I had the same slow results. Aside from that, my interest is in getting the AOSP tether into a patch. I'm setting up to poke around inside the source code now.
Wish me luck!
http://source.android.com/source/initializing.html

The only difference between carrier tether and aosp tether in ICS is provisioning.

http://www.galaxynexusforum.com/for...e-wifi-hotspot-using-unrooted-phone-free.html

Just add a tether widget using Switch Pro Widget and it overrides the check. Easy, free tethering.

adrynalyne said:
The only difference between carrier tether and aosp tether in ICS is provisioning.
Click to expand...
Click to collapse
I tried the tether widget you shared. I'm getting 4G speeds with it, but still not with any other tether program...
Can you point me to some more info about the above quote? I'm not being a smart-butt. Just genuinely curious as to the deeper answer of why. It seems as though the other tether apps are pulling from the 3G radio.
I just thought of a way to test it... Make a phone call while tethering and see if it dies. Not sure if the Nexus has SVDO, but I'll turn off LTE to ensure that it's riding on 3G and make a second test to confirm.
I can't make a call right now, so I'll try later and post results.
I'm still interested in how this is circumvented by the widget and why the 3G is being used be the other tether programs, if this is actually what is happening.

Hmm...
Funny business going on. I just tried android-wifi-tether once more for kicks and now it's running on 4G speeds.
Rebooted the phone to make sure that it stuck and it did.
Not sure why, but still interested to know.
Out in left field (but still reasonable) speculation is welcome.
Sad that I will not get to try and test my 3G theory. I do have my clockworkMod backup and might try it all tomorrow and see what results I get.

hgray said:
I tried the tether widget you shared. I'm getting 4G speeds with it, but still not with any other tether program...
Can you point me to some more info about the above quote? I'm not being a smart-butt. Just genuinely curious as to the deeper answer of why. It seems as though the other tether apps are pulling from the 3G radio.
I just thought of a way to test it... Make a phone call while tethering and see if it dies. Not sure if the Nexus has SVDO, but I'll turn off LTE to ensure that it's riding on 3G and make a second test to confirm.
I can't make a call right now, so I'll try later and post results.
I'm still interested in how this is circumvented by the widget and why the 3G is being used be the other tether programs, if this is actually what is happening.
Click to expand...
Click to collapse
I can confirm also that using a WiFi hotspot toggle will override the Verizon hotspot check. I saw this on another forum and tried it out. It works flawlessly. Apparently this worked on Thunderbolts on VZW but not on other devices. If I had to guess, they implemented the check in a very rudimentary way that is bypassed by using a toggle. The toggle likely just executes a command to enable the hotspot whereas the toggle in the settings has a check in place first and then the command is executed. Either way, it works and I don't have any issues at all.

A more apt title for this thread would be "Verizon tether patch", seeing as AOSP has tethering and doesn't need any patching to enable it, like you do on American carrier-phones.

After digging around in some source code and stumbling upon some relevant topics both here and other forums, I see that this is something that happens before compile. I suppose it would be possible to replace recompiled versions of these files, but I don't know enough about what I'm doing here to make that happen at this point.
A few other people have been down this road of inquisition for ROM development. The answers were out there, I just didn't have the right keywords until I started poking in the ICS source code.

Desire Z on WIND Mobile (which radio version)

Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA

skewty said:
Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
You could try to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Sent from my HTC Vision using xda premium

evilcuber said:
You need to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Click to expand...
Click to collapse
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?

skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
As someone who has friends on Wind... I'm thinking it may be your network. Also, you're not supposed to match the rils unless you're using sense. Which ROM are you running?
Sent from my Transformer TF101 using xda premium

skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
Use latest Radio from T-Mobile 26.13.04.19_M, I'm on it, have never lost 3.5 G data connection

I am currently running ILWT but experienced the same running CM 7, ICS Audacity and ICS Quattro.
I have flashed the newest TMobile ROM a few times.. It must be the WIND network here.
Sent from my HTC Vision using XDA

Update
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.

skewty said:
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.
Click to expand...
Click to collapse
The issue isn't ICS. The issue is the vendors haven't released proper drivers for ICS. What we're dealing with is code we've hacked up to make things work. If the vendors released ICS source code for our devices things would be much more stable.
We're always working within our means. It's not Android/Google's fault and it's not an ICS issue, it's just circumstance.

Thanks
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).

skewty said:
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).
Click to expand...
Click to collapse
Drop by #g2ics on freenode if you're interested

I have the same issues, G2 on Wind as well. I've had some ROMs where it never occured, but then they had some kind of bug that left me unhappy. I'm currently on CM 7.2 RC1, and I keep a "data" toggle in my notification bar. When it drops I toggle it off and on and it connects again pretty quickly. Until about twelve months ago, MMS was unreliable, but I don't seem to have problems with that anymore.
In general I'm not happy with Android, but as the alternatives are all utterly closed systems I guess I'm stuck with it. It would be unbearable if it weren't for the hard work of all the developers around this forum. Thanks, developers

Agreed. Google has been a huge let down for me as well. Updates are slow or non existent in Canada (even on Nexus devices). Look at the percentage of devices that run ICS. JB is what ICS was supposed to be. I may get an iPhone for work. I am excited to compare it to my Samsung S3 on CM10.
Sent from my SGH-T999 using xda app-developers app

[Q] Flash Int Roms with Wifi Calling

I was wondering if there is any way to flash a international rom and implement the Wifi Calling back in the settings. Want to run wanamlite with Wifi Calling? Is this possible? Perhaps an apk for Wifi Calling. It is a T-Mobile device

Zackg111 said:
I was wondering if there is any way to flash a international rom and implement the Wifi Calling back in the settings. Want to run wanamlite with Wifi Calling? Is this possible? Perhaps an apk for Wifi Calling. It is a T-Mobile device
Click to expand...
Click to collapse
Not yet. Its more than just an apk, which can be easily extracted and installed on any device. It needs a lot of libs to go with it, and those are pretty closed sourced and hard to figure out.
There is a team trying to reverse engineer it to get it working on non stock ROMs. They are doing it for another device but once its done it should in theory work for any device. Last I heard there was a sizable bounty of promised donations if they could get it working, so I'm sure they are motivated.
Many people will tell you this is and will always be impossible. But the WiFi calling app was hacked and made installable for ICS AOSP ROMs. So its been done before. They JB version is apparently tougher, but the software that couldn't be hack has yet to be developed yet as far as I am aware. Its jus a matter of if XDA's devas are smarter than T Mobile's devs
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Not yet. Its more than just an apk, which can be easily extracted and installed on any device. It needs a lot of libs to go with it, and those are pretty closed sourced and hard to figure out.
There is a team trying to reverse engineer it to get it working on non stock ROMs. They are doing it for another device but once its done it should in theory work for any device. Last I heard there was a sizable bounty of promised donations if they could get it working, so I'm sure they are motivated.
Many people will tell you this is and will always be impossible. But the WiFi calling app was hacked and made installable for ICS AOSP ROMs. So its been done before. They JB version is apparently tougher, but the software that couldn't be hack has yet to be developed yet as far as I am aware. Its jus a matter of if XDA's devas are smarter than T Mobile's devs
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Thank you for the evaluated answer. I thought it was more along the lines of possibly working because of it originally having Wifi Calling. Its not like making it work on att or verizon. I thought it would be more of a verification issues with other carriers.

Zackg111 said:
Thank you for the evaluated answer. I thought it was more along the lines of possibly working because of it originally having Wifi Calling. Its not like making it work on att or verizon. I thought it would be more of a verification issues with other carriers.
Click to expand...
Click to collapse
I'm 100% positive it will never work on other carriers (unless they introduce their own wifi calling app that woks on their networks)
The app itself checks your SD card and makes sure that you have a T Mobile account before authenticating you on T Mobile's server. So if you're on an AT&T SIM card it won't matter how well you get the app working, the app won't let you use AT&T accounts on the T Mobile wifi calling server.

Skipjacks said:
I'm 100% positive it will never work on other carriers (unless they introduce their own wifi calling app that woks on their networks)
The app itself checks your SD card and makes sure that you have a T Mobile account before authenticating you on T Mobile's server. So if you're on an AT&T SIM card it won't matter how well you get the app working, the app won't let you use AT&T accounts on the T Mobile wifi calling server.
Click to expand...
Click to collapse
Ok I am on T-Mobile anyways. I figured that would never work especially with your normal number.

Keep an eye on this Dev, fingers crossed here!
Zackg111 said:
I was wondering if there is any way to flash a international rom and implement the Wifi Calling back in the settings. Want to run wanamlite with Wifi Calling? Is this possible? Perhaps an apk for Wifi Calling. It is a T-Mobile device
Click to expand...
Click to collapse
Skipjacks said:
Not yet. Its more than just an apk, which can be easily extracted and installed on any device. It needs a lot of libs to go with it, and those are pretty closed sourced and hard to figure out.
There is a team trying to reverse engineer it to get it working on non stock ROMs. They are doing it for another device but once its done it should in theory work for any device. Last I heard there was a sizable bounty of promised donations if they could get it working, so I'm sure they are motivated.
Many people will tell you this is and will always be impossible. But the WiFi calling app was hacked and made installable for ICS AOSP ROMs. So its been done before. They JB version is apparently tougher, but the software that couldn't be hack has yet to be developed yet as far as I am aware. Its jus a matter of if XDA's devas are smarter than T Mobile's devs
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2302313

I'm hoping that when the Google Edition of the S4 comes out that T-Mobile picks it up and they have to disclose stuff for WiFi calling to be enabled properly in AOSP.

cosine83 said:
I'm hoping that when the Google Edition of the S4 comes out that T-Mobile picks it up and they have to disclose stuff for WiFi calling to be enabled properly in AOSP.
Click to expand...
Click to collapse
I hope that Keidi Klum will show up at my door to deliver a briefcase full of money.
If you and I get together maybe we can start a support group for people who's hopes don't come true.
Fact is that the WiFi calling app is closed source proprietary stuff. It will get hacked by XDA, but T Mobile is never going to willingly release it. They have a vested interest in getting you to buy the phone from T Mobile. Why would they take away something that encouraged you to do that?
Sent from your phone. You should be careful where you leave that thing.