yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] krohnjw:
An update: no significant progress at this point. Kineto needs a verify specific RIL to function.

For HTC phones they must use a very specific version of libhtc-ril.so. The Nexus One can utilise this without issue. This obviously will not work with the Nexus S.

I had hoped that the version of libsec-ril on the Galaxy S would work with the Nexus S (taken from the Vibrant update the included Wifi Calling), but this does not appear to be the case. The library itself is significantly smaller from the Vibrant and results in no service when used on the Nexus S.

So, for now we're stuck. I spoke with Zinx regarding this and he confirmed that Koush had tried as well with the modified libraries and ran into problems. Unless someone wants to dig through the binaries themselves and find out what's needed to get the libsec-ril working with Kineto (both the kineto binary and the RIL) we are likely at an impasse.
[Nexus S Android Development] b84cops:
well dayum..... completely bummed.
[Nexus S Android Development] brian6685:
Yeah that sucks :( oh well. Thanks for trying though
[Nexus S Android Development] superhtchd2:
this would def be nice to have on the nexus s..!
[Nexus S Android Development] kenvan19:
Its too bad the devs decided it was not possible
[Nexus S Android Development] MacGuy2006:
I sure hope the decision is not final and where there is a will, there is a way. :)
[Nexus S Android Development] krohnjw:
It's certainly not a final thing. If we can get a working RIL then there's hope that the Kineto binary from the Vibrant could use it. Those are currently 2 big IF's though unfortunately.
[Nexus S Android Development] b84cops:
stupid questions here, but i thought i'd ask anyway.

can the nexus s run on version 2.2?

if so, would the the wifi calling app work?

i'm desperately needing to be able to use this app at home since i have no cell coverage.
[Nexus S Android Development] kenvan19:
There are no builds of Froyo for the Nexus S and from what I understand you cannot simply use a ROM from another SGS phone. Sounds to me like you might just be SOL or you could try the almost free way of doing wifi calls thats in General of the Nexus S forums.
[Nexus S Android Development] tekkitan:
Read the thread in a bit more depth and you will have your answer. It has nothing to do with Froyo.
[Nexus S Android Development] b84cops:
Does this article help the cause at all?

http://www.androidcentral.com/wifi-calling-nexus-one-cyanogenmod-7#comment-108781
[Nexus S Android Development] krohnjw:
Nope, we need a RIL that works with kineto and the nexus s....a combo that does not exist currently. The libsec-ril from the galaxy s does not work with the nexus s and the libsec-ril from the nexus s does not work with kineto currently.
[Nexus S Android Development] kenvan19:
The real question I have is once there is a SGS with a gingerbread build, do you think the right drivers will be available?
[Nexus S Android Development] krohnjw:
Unknown. The current ril for the galaxy that works with kineto won't work with the nexus s at all. That's not a froyo issue really.

The ril for the nexus s is substantially larger (30 % or so), so I am guessing that even though they have similar hardware there are substantial differences between the two that will continue to prevent the ril from being interchanged like the htc ril can be with several htc phones. Hopefully I am wrong, but I am not optimistic.
[Nexus S Android Development] Anderdroid:
T-Mobile should just release the app on Market jeez. In the T-Mobile tab.
[Nexus S Android Development] kenvan19:
Agreed.

Sent from my SubCyan CM7 Google Nexus S!
[Nexus S Android Development] MacGuy2006:
Even if they ever do, the Nexus S will be running OS 3.5 by that time.... :)

Does T-Mobile have WiFi Calling for anything other than the Vibrant?
[Nexus S Android Development] kenvan19:
Isn't it on the MT4G?
[Nexus S Android Development] Anderdroid:
MT4g and G2. And Galaxy S 4g
[Nexus S Android Development] ogdobber:
defy +10char
[Nexus S Android Development] bogdi1988:
maybe the Samsung Galaxy S 4G would help us get a working RIL?
[Nexus S Android Development] sheek360:
Im willing to donate to see this through
[Nexus S Android Development] brian6685:
Me too, but I think a lot of people are and its not easy to do.

Nexus S
[Nexus S Android Development] krohnjw:
It's being worked on, hopefully I'll have some good news in the next few day.

It's not a question of motivation, just gathering the proper resources currently.

If you want to donate I'll make sure proper credit it's attributed to those helping with this and you guys can send some donations their way if you want.
[Nexus S Android Development] Jayrod1980:
Sounds like great news!
[Nexus S Android Development] Bry5on:
I'll kick in a few bucks to get this moving! There are probably quite a few lurkers watching this progress
[Nexus S Android Development] b84cops:
I will absolutely chip in as well!
[Nexus S Android Development] rome425:
I am pledging $20 or so, as soon as I can get it working :)
[Nexus S Android Development] dudeimgeorge:
I whole heartedly pledge as well

I am in this as will $20 to a solid working dev team. And i can easily scrap a few friends on this as well!
[Nexus S Android Development] MacGuy2006:
I'd be happy to chip in as well :)
[Nexus S Android Development] Lootes:
So here is something interesting I read today. Looks like T-Mo is really touting their Wi-Fi Calling for Android app. Let's hope this means they plan to take it a little more mainstream which could help us. Market app perhaps?

http://www.tmonews.com/2011/02/t-mobile-says-5-million-customers-use-wi-fi-calling-service/
[Nexus S Android Development] blktalon:
I'm in for 75 dollars. I'm in Vermont on the weekends and need this....or tmo can put up a nice tower on my land. :)
[Nexus S Android Development] dro3432:
Im willing to chip in too. Prefer some dev here does it over tmo just releasing it to the market. I already give them enough of my money.
[Nexus S Android Development] brian6685:
This is very good news :)

Nexus S - cm7
[Nexus S Android Development] slowz3r:
The N1 boys got it working, does that give us a lil edge now?
[Nexus S Android Development] krohnjw:
Got the necessary log file - a quick scan doesn't look good for the RIL cooperating. I'll look more in depth later.
[Nexus S Android Development] brian6685:
Ugh, anything I can do to help?

Nexus S - cm7
[Nexus S Android Development] j0hnZ:
I have a Vibrant sitting next to me right now. I've never run a logcat so give me instructions and you'll have it with the quickness. I have pretty much everything I can think of working adb, fastboot whatever.
[Nexus S Android Development] krohnjw:
I did end up getting the necessary log file. Ill let you know if I need anything else. I am hoping to take a look tonight.
[Nexus S Android Development] anotherbrick:
Please excuse my ignorance, but what does RIL stand for, what type of component is it?
[Nexus S Android Development] kenvan19:
krohnjw I just wanted to say thank you for working so hard on this. I know that my wife and I would very much appreciate it if you get this working but I understand if you can't. I'm just happy to see someone working on it. I'm not very good at coding but I'm a great guinea pig if you need one :)
[Nexus S Android Development] Lootes:
+1, thanks for your work and happy to test.

Sent from my Nexus S
[Nexus S Android Development] Bry5on:
Count me in as a willing guinea pig as well, thanks!!
[Nexus S Android Development] krohnjw:
Radio Interface Layer - it's acts as the go between from the software (Android processes) and the hardware radio / modem. This is not open source - so we can't get the code and make changes.

So far no more good news. After the auth fails the request to hand off to GAN is never made. Unless the RIL for the Nexus S can be made to succesfully support the call to requestOemAuth I don't see much progress being made.

Testing on CM7 with the new radio shortly.

Edit:

Same on new baseband:

E/RIL ( 129): requestOemAuth: sub_id 0x01 len 16
E/RIL ( 129): requestOemAuth: Unknown Auth OEM sub_func_id 0x01

Things are not looking great.

I decompiled libsec-ril.so from the Vibrant hoping it was a defined function (present in the vendor RIL for the Vibrant but not the Nexus S) and not the radio code, but it's not defined in the vendor RIL at all. If this is part of the radio code we are pretty SOL.

I do wish I could post *good* news as an update, but I am not encouraged :(
[Nexus S Android Development] Br1cK'd:
I was checking up on ya seeing if that logcat helped at all. Would the lib files from the Vibrant help you out maybe? I can post them if you need them. Let me know what else you need from this side, I'll do what I can for ya.

Sent from my Loki powered Vibrant via the XDA App
[Nexus S Android Development] illmaticone:
Can't wait for this. Keep up the work guys!

Sent from my Nexus S
[Nexus S Android Development] krohnjw:
It did help, although it helped more to demonstrate that the errors I'm seeing are indeed showstoppers and not something passable. At this point it looks like the RIL for the Nexus S doesn't support the necessary AUTH request being made. This request is necessary to hand off to GAN and then make the subsequent connection.

I tried the RIL from the vibrant a while back but it didn't work with the Nexus S - resulted in no service (the Vibrant RIL was ~370k while the Nexus S RIL was ~480k). So I am not sure the 2 are interchangeable, (if the missing functionality is in the vendor RIL lib and not in the radio code.

If you want to upload a copy of libsec-ril.so from your working Vibrant it's easy to give it a shot and see how it goes.
[Nexus S Android Development] heinrich:
Removed UMA service from my plan

Well guys after about 2 years of never using UMA because I had an iPhone and lately a nexus s with no actual way to do uma, I gave up and pulled my unlimited wifi calling service. I figure I can use the 10 bux a month better than a service I cannot use anymore. Oh well ... Seems sip calling works well, I will use that when traveling from now on.

In my opinion T-Mo have shown no interest in UMA.
[Nexus S Android Development] Br1cK'd:
Ill post it for you when I get home this evening.

Sent from my Loki powered Vibrant via the XDA App

Here's the file, godspeed!

This is from our KB1 Build/Modem, the same version I was using when I captured the logcat. HAd to zip it as well, xda doens't allow .so attachments.
[Nexus S Android Development] krohnjw:
Thanks,

I decompiled libsec-ril from the NS as well as the SGS, and both have requestAuthOEM defined in the RIL. However, interestingly, they are different. So, at least it's defined in our RIL and not something radio specific. I'll pop this on tonight and give it a shot and see if I can step through this assembly and find out what's going on (fun times!).

Edit: Still no service using the SGS RIL. The SGS RIL is missing over 130 function definitions present in the Nexus S :( It doesn't look good for the two being interchangeable in the near future.
[Nexus S Android Development] j0hnZ:
I heard the samsung vibrant 4g came with a different wifi calling app, might be worth looking into. I know there is a i9000 port to the vibrant, but I haven't looked to see if anyone has gotten wifi calling working on it. It's pretty beta atm.
[Nexus S Android Development] Br1cK'd:
There is no wifi calling in the i9000 Vibrant port. I tried to push the files in my latest build while I was cooking that firmware, but no dice.

Sent from my Loki powered Vibrant via the XDA App
[Nexus S Android Development] j0hnZ:
I wouldn't expect it to have TMobile WiFi Calling on an international version of the phone BUT someone might be working on it in that dev community.
[Nexus S Android Development] Br1cK'd:
No ones mentioned it publically but youre absolutley right somebody might be. If we come up with anything, I'll be sure to let you guys know about it.

Sent from my Loki powered Vibrant via the XDA App
[Nexus S Android Development] ronn888:
Might be old news, but they got it working on the nexus one:

http://www.xda-developers.com/android/make-calls-via-t-mobile-wifi-on-your-nexus-one-with-cm7/
[Nexus S Android Development] tekkitan:
You should really read this whole thread before posting this :P
[Nexus S Android Development] dsellers2:
I don't believe he should have to read the whole thread to share relevant information even of its known. It doesn't make sense, on the other hand if he wants information he should read the whole thread to obtain said information.

People share information all the time and may not care one bit about the subject at hand.
[Nexus S Android Development] jkusmc:
A friend of mine got the Galaxy S 4g at work today. If you guys need anything off of it, let me know.
[Nexus S Android Development] jonjon68:
Condolences to him.
[Nexus S Android Development] jkusmc:
Haha, that bad?
[Nexus S Android Development] krohnjw:
If he can pull the RIL I'm willing to test it (libsec-ril.so).
[Nexus S Android Development] tekkitan:
Considering what he linked was already talked about earlier in the thread, yes, he should have read the whole thread.
[Nexus S Android Development] k4str0:
Hoping that the attempts to get this working aren't abandoned. Looks like there was quite a bit of progress.
[Nexus S Android Development] MacGuy2006:
Just keeping hope alive.... :)
[Nexus S Android Development] chrlswltrs:
I'm really looking forward to this also!
[Nexus S Android Development] krohnjw:
Not to be a buzzkill, but until we get a RIL that works with the nexus s AND supports the necessary auth calls to enable GAN we are dead in the water. I'll continue to test updated RILs as they emerge in new devices and in updates to the nexus s. But until we get that we are at a standstill.
[Nexus S Android Development] rome425:
I am checking this thread every day... still no progress?
[Nexus S Android Development] MacGuy2006:
I am hoping that the release of the Galaxy S Gingerbread code will help this a bit.

Or do we have to wait for the Vibrant to get Gingerbread?
[Nexus S Android Development] krohnjw:
I don't think it will help. So far the RIL from other Samsung devices (which support the auth calls for GAN) don't function with the Nexus S. They are missing quite a few functions defined in the Nexus S RIL (around 110 if i recall correctly). I don't expect that the RILs for these other devices will be updated to have the necessary Doe for the Nexus S as there appear to be some significant differences in the RILs.
[Nexus S Android Development] cybereclipse:
:( so were dead on the water for now then huh?
[Nexus S Android Development] denis_y_s:
The T-Mobile G2 Gingerbread upgrade is leaked, there should be a WiFi calling in it. So can it help with development for the Nexus S WiFi calling adoption?

http://www.androidcentral.com/htc-doubleshot-and-flyer-roms-leak-so-does-gingerbread-t-mobile-g2
[Nexus S Android Development] krohnjw:
Not really - the problem is not the Kineto (Wifi Calling) App. It's the Radio Interface Layer. It does not support the auth calls to initialize the switch to GAN. It's unknown if it supports the rest of the necessary calls after the switch as well. If one is missing though I'd venture a guess that it's not the only one.

Unfortunately the G2 is made by HTC, so the RIL from the G2 will not function with our Samsung device. The RIL from the Galaxy series (which does support wifi calling) does not work with the Nexus S.

As the RIL is distributed as a closed source binary only we have no real way to make modifications to it. Hopefully the RIL will be updated with a future update or the RIL from an upcoming device (perhaps from the Galaxy S II with NFC) will work on our device. Until then there's not a lot that can be done.
[Nexus S Android Development] krohnjw:
libsec-ril.so was updated with 2.3.4.

Unfortunately requestAuthRequest and requestOemAuth appear to have undergone no changes in the patch itself (compared decompiled assembly from the old and new libraries). As a result I am not as optimistic as I was before looking at the file itself.

However, once CM7 updates to 2.3.4 I'll flash a nightly CM build and give it another shot.
[Nexus S Android Development] rome425:
Resurrecting
[Nexus S Android Development] brian6685:
Man I wish we could get wifi calling to work on here. I don't know why T-Mobile won't do it I guess because it's not branded a T-Mobile phone. Ugh

G2X & Nexus S
[Nexus S Android Development] denis_y_s:
T-Mobile just announced unlimited WiFi calling -

http://www.tmonews.com/2011/05/t-mobile-bring-unlimited-wifi-calling-back/

I really hope WiFi calling will work on NS..
[Nexus S Android Development] dany>boricua:
Anyone tried WiFi calling with 2.3.4?
[Nexus S Android Development] swa2k4:
lets try itt

anyone on any 2.3.4 based roms getting this working? like SupeAOSP or anything? I am going to be going on a flight where Ill have wifi and like to use this..
[Nexus S Android Development] unforgiven512:
I've been tinkering it with it, guys.

No luck :(

Trust me, it kills me. I get no signal in my house. I have to go outside to make calls. =/
[Nexus S Android Development] j0hnZ:
Me too, so much fAIL.
[Nexus S Android Development] cybereclipse:
uggh I'm already looking to get rid of my Nexus S becuase it doesn't have wifi calling....If only If only.... :(
[Nexus S Android Development] unforgiven512:
It's not that big of a dealbreaker for me -- I already have 3000 min/unlimited SMS/unlimited (5GB 3G) data, 2 lines, $149.99/mo so I'm not too worried about the free minutes.

But, the lack of signal is frustrating. I'm trying to get in contact with some people, and continue to tinker. Only time will tell, guys.

BTW -- Don't return the phone! You'll regret it. You can't beat the sexiness of the S-AMOLED screen.
[Nexus S Android Development] hyperfire21:
Do you think we need to wait for a galaxy 2 type phone on Tmobile to get this working on nexus s?
[Nexus S Android Development] krohnjw:
Unless we can come up with a working RIL or another solution. So far attempts to contact Samsung and Kineto have gone unanswered.
[Nexus S Android Development] hyperfire21:
Yea maybe we should wait till the Hercules leak to see if it helps.

Also its not just about the free minutes anymore. Apparently if we travel to any country Wifi calling doesnt charge any roaming fees! Hopefully someone gets it to work before my trip in July :P

Keep up the good work guys
[Nexus S Android Development] brian6685:
Yeah I REALLY wish we could get wifi calling working on this phone. It would make my life so much easier as I barely get service in my house. :(
[Nexus S Android Development] dany>boricua:
I feel ya, I stay in an apartment in the mountains close to collage and I have no service either. Sadly I use to have all the time when I had my Vibrant with WiFi calling, now I'm stuck with a better phone but no signal.
[Nexus S Android Development] rfgamaral:
Hey ele, quick question... I always do a few tweaks to each ROM update before flashing and I've noticed that the following has been removed from build.prop a couple of versions back:

#wifi network etc..
ro.ril.def.agps.feature=1

# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000

# To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=1000

#sound
ro.config.notification_sound=Teleport.mp3
ro.config.alarm_alert=Light.mp3
ro.config.ringtone=Old_Phone.mp3

#windows management
qemu.sf.lcd_density=160

# default value of brightness
settings.display.brightness=143

# The OpenGL ES API level that is natively supported by this device.
debug.sf.hw=1

If you could be a little more specific on each one of them individually I would really appreciate it. I just want to understand if I should add them back to my custom ROM or not.

By the way, do you know about any property (like the ones above) to make sure that the mobile data connection starts disabled on a first boot?
[Nexus S Android Development] hyperfire21:
Hey guys the Galaxy 4g Gingerbread rom leaked. Any use of it?

http://xdaforums.com/showthread.php?t=1125747
[Nexus S Android Development] craftyguy:
I would be very pissed off if i had to sit next to someone on a plane who was chattering away on a phone. It's worse than a screaming baby; at least the baby doesn't know any better
[Nexus S Android Development] BrokenWall:
I called T-Mobile and they said they were working on releasing an APP in the market to install as a service that would allow calls to be redirected, but then they didn't release it.

Sucky part is that I have to leave my apartment and move out due to work, and I am going back to my mother's house, thing about my mother's house is all cell phone signals go there to die. My wife is fine with her Stock MyTouch4G though.

Does anyone know if T-Mobile has a small Micro-cell like AT&T
[Nexus S Android Development] Nospin:
Bought a nexus s for a family member stupidly thinking it could use t-mobile's wifi calling app. Wishing you guys a lot of luck with this, or this thing is probably going back in 28 days.

Sent from my T-mobile G2
[Nexus S Android Development] BrokenWall:
I am moving to a new location where cell signal is complete crap, this is only temporary but im talking so bad that I have to walk outside about 100 feet to even get a good enough signal to talk without cutting in and out.

So I am switching phones, even know I don't want to, I have to get a phone with Wi-Fi calling as there is nothing else T-Mobile can do, they even sent out engineers to the new place to double check.

So my choices are either the Sensation 4G or the G2X

I did try installing the Wi-Fi calling app from the G2 and it installed but crashes when you try to open it.
[Nexus S Android Development] rome425:
Bump

Thank you.
[Nexus S Android Development] Babydollll:
@brokenwall I have a Sensation also and Wifi Calling works well...

Sent using two tin cans and some string.....
[Nexus S Android Development] mprziv:
I would definitely donate/pay for a working wifi calling app on my NS.
[Nexus S Android Development] faceoff007:
Bump.

Thanks.
[Nexus S Android Development] IamObie:
I would also easily donate/pay to see this completed.
[Nexus S Android Development] LowQue27:
I too would luv to see this happen.
[Nexus S Android Development] krohnjw:
Please send all donations to Samsung and ask them to provide a radio interface layer blob that supports all of the auth calls needed :)

We're still stuck with a RIL that will not allow the switch to GAN (necessary for wifi calling) due to it's lack of support for the authorization calls. Until we get that it's dead in the water.

Essentially it works as follows:

the base RIL (libsec-ril) is replaced with libswitch-ril.

libswitch-ril hands off functionality to libsec-ril for basic phone operation.

When you want to initiate wifi calling some authorization is done to verify you are a t-mobile customer (sim) and can use wifi calling.

Once this completes the RIL functions (or a subset of functions) get handed off to libgan-ril

As libsec-ril does not support all of the authorization requests it will never hand off to libgan-ril to begin the process of instantiating the connection, creating a tunnel, etc.

We've tried all of the new RIL's from the current gen of Samsung devices and none of them function on the Nexus S. So we are waiting for the blob to be updated via an OTA or another RIL to surface that will work on the Nexus S and supports wifi calling.

Kineto blames Google for not requesting these features from the manufacturer (oddly though the RIL on the Nexus One supports it just fine, so this appears isolated to Samsung).

So, to make a long story short, don't hold out hope. If an updated RIL comes out it will be tested, until they we are at a stand still.
[Nexus S Android Development] faceoff007:
May be the RIL from Hercules will help. Keeping my fingers crossed !!