yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] baseballfanz:
Yes the WiFi add on work just fine when I was on the latest stable.

I have since moved on to the latest nightly and it's still working fine.
[Nexus One Android Development] NCguy:
Many thanks for that :)
[Nexus One Android Development] blahbl4hblah:
I have about 70mb free from system
[Nexus One Android Development] NCguy:
What all did you eliminate?? I have a standard CM7 ROM and I have 16MB free. It had to be a whole lot more than wallpapers.
[Nexus One Android Development] blahbl4hblah:
I didn't delete anything. Whatever. Cm7 has I will have. And if your wonder which rom this is. It's my own rom that I haven't released yet. I'm deciding on it actually
[Nexus One Android Development] wachalookinat:
+ 1 for releasing your rom :)
[Nexus One Android Development] blahbl4hblah:
Im considering it. But the only thing is internal memory will get high as well. I don't use dts a2sd scripts. And I don't need it.it is a great script but I'd rather not use it
[Nexus One Android Development] i<3myphone:
Wi-fi Error Message

Ok, so I need some help here please. I installed this last night. I thought I did everything right, but apparently not. My phone started acting up the minute I finished the flash. (force closes on most everything.)

So now I did a factory reset, wiped everything and went to a CM Stable Mod.

My wireless connection is non existent. When I click the icon to turn on wireless, it comes back with the words "error" underneath. What happened? What can I do to fix it? And I know many of you are rolling your eyes b/c I have not given enough details??? But honestly, it was late. I was tired. I should not have been messing with the phone.

Can I fix my wifi?? Thanks.
[Nexus One Android Development] blahbl4hblah:
Most likely your issue isn't due to the factory reset. Wifi giving an error is most likely kernel related. Which kernel did you flash btw
[Nexus One Android Development] i<3myphone:
The kernel says:

2.637.6 cyanogenmod-01505-g81b06a8

shade@toxygene #1
[Nexus One Android Development] i<3myphone:
So I just flashed the latest wildmonk kernel. It gave me my wifi back, but now it just keeps searching and searching for my IP address. It just loops. It sees my network, but cannot connect. ???

Thanks so much for your help!
[Nexus One Android Development] baseballfanz:
How's your system storage size?
[Nexus One Android Development] i<3myphone:
System ROM: 152 MB (26.8 MB free)
[Nexus One Android Development] baseballfanz:
The omly time i got wifi searching but never working was when i installed an app call

Phonemypc. After i deleted the app it work fine. Installed anything lately?
[Nexus One Android Development] i<3myphone:
I reflashed the newest CM 7. I am good to go now. Thanks for everyone's help here. I am not sure I will try this wifi calling app again. It messed me up and now I am chicken.
[Nexus One Android Development] baseballfanz:
Nah, don't give up. If anything it show that you can work your way out of the problems.:)
[Nexus One Android Development] i<3myphone:
thanks. i like that way of looking at it.

but.......i went with Groove IP instead. It seemed easier. And it works for me...so. :)-
[Nexus One Android Development] NCguy:
Can anyone tell me, based on other CM7 ROMS, if the t-mobile wifi calling feature gets retained in the CM7 ROM for those phones that also had it in TMO's version of the ROM?

I am seriously considering a sensation, hercules, or possibly the next Nexus (if on TMO). I'm wondering if its in TMO's ROM then if the odds will be that it would also carry over to the CM7 ROM when its available. I know its pure speculation but if someone could tell me whats happened on other TMO phones that had it originally I would appreciate it.:)
[Nexus One Android Development] mayurpatel:
Problems with current nightly

I'm on the latest CM nightly and tried flashing this. It seems to work but kills my data and network connection to T-Mobile... e.g., once I'm out of wifi range, I get nothing.
[Nexus One Android Development] hogg2500:
Yeah I flashed this today too, completely ruined the ROM, CM7 Nightly #177. Had to restore from a backup to see my SIM Card again.
[Nexus One Android Development] baseballfanz:
You guys need to clear up some system space (delete some unuse app from system) and it will work.
[Nexus One Android Development] hogg2500:
I had over 100 MB free Internally. Most of my Apps were Moved to the SD.

When I installed it, 95% of the Apps on my phone were force closing, no SIM Card at all. It was the oddest thing.
[Nexus One Android Development] baseballfanz:
system apps are different from install apps. Since the wifi ad on get flash and install on the system/app section. you need to clear up some space on system/app.

System apps are the one that either come with the ROM or Gapps.
[Nexus One Android Development] hogg2500:
Ah thanks I will try that
[Nexus One Android Development] hogg2500:
I did clear out some system space a on a fresh CM7 Nightly #177 install.

It did the same thing. After I flashed WiFi calling, the phone didn't even acknowledge that their was a SIM Card in it.

Maybe it is my phone that is the issue?
[Nexus One Android Development] baseballfanz:
How much system memory do you have? I'm on nightly 177 and it's fine.

I would have at least 15MB before I flash the WiFi add on.
[Nexus One Android Development] hogg2500:
Finally got it working. Thanks so much :D
[Nexus One Android Development] hogg2500:
Here is something good, when I turn Wifi Calling off, it disables my SIM Card. ANyone had this issue?
[Nexus One Android Development] Bohemus:
Ive been having an issue where wi-fi no longer finds access points after flashing this. It will work right after I flash, but on the first reboot it prevents me from seeing any wireless access points.
[Nexus One Android Development] baseballfanz:
I have not had either one of these problems. This wifi add on is finicky for space.

All I can suggest is clear MORE system space.
[Nexus One Android Development] hogg2500:
I had 26 MB of space free when I installed in and like 15 MB of space after. I wish someone would continue working on this. This is the only thing I miss from my G2.
[Nexus One Android Development] baseballfanz:
I'm sorry but my level of expertise probably a little short and can't really help much.

What about your SIM card, maybe a new one might help?
[Nexus One Android Development] Lost Dog:
Any chance of this working internationally? I'm from the US but in Korea for the week (T-mobile USA sim card). When I turn wifi on I and try to activate the wifi calling I get a error of not being registered on the Tmobile network and "j0012.0 Network Busy Retry".

I then tried using SSHTunnel to funnel all my data connection through my home router (so it would appear my phone is connected to my router in Washington and not international) but still no go.

The odd thing is it worked briefly in the Tokyo / Narita airport but now that I'm in Incheon I get the error.

It would have been great to get this to work so I could tunnel my calls through my router at home but I may be out of luck... Anyone else try anything like this?
[Nexus One Android Development] opus1one1:
It does work internationally, it's supposed to. I always use it oversees. If you're experiencing issues, it's probably due to the wifi infrastructure you're connecting with. It doesn't work as consistently as phones that ship with it.
[Nexus One Android Development] Lost Dog:
Well.... I guess I need to learn more about it! I just threw on the Wifi calling to my CM7 because I was heading overseas but for some reason I thought it was only for US based calling. That is why I was trying to use the SSHTunnel method to make it appear the call was coming from my US based router!

Does TMo charge extra for the calls placed outside the US or is it just normal data usage?

Any other tips for someone traveling out of the states to take advantage of our phone?

Thanks!
[Nexus One Android Development] chichoCRZ:
hogg2500 How did you get it to work?

I have been using this apk for some time now with no issues. I even updated my ROM to CM7.1 stable and no issues as well. But since I broke my touch screen I unrooted back to stock to try and send the phone in for repairs. I never sent it in so I rooted again to CM7.1 stable version but now every time I flash the wifi calling apk it disconnects me form the T-Mobile servers. I noticed it completely deletes my APN setting under: Settings/Wireless & Networks/Mobile Networks/Access Point Names.

Before I flash, the epc.t-mobile.com APN settings are present. After flashing, it wipes it out. I even downgraded to CM7.0.0 stable version as I used it before but same problem.

One other thing i noticed after dropped and cracked the screen is that is intermittently disconnected me from the Google Servers, where the signal bar and data logos did not turn the color green. After searching for an answer I ran into a post where some said to change the APN setting from epc.t-mobile.com to internet2.voicestream.com and now I have a stable connection.

But this is not the case I after I flash the ROM I leave it as the current APN setting of T-Mobile.
[Nexus One Android Development] baseballfanz:
You need to clear out some system space.
[Nexus One Android Development] NCguy:
Galaxy Nexus

I'm betting the tmo galaxy nexus wont have wifi calling and this is going to be a very popular phone. Anyone think that effort will be made to incorporate this into CM's version of android 4?
[Nexus One Android Development] taney:
I was having that issue so I went to t-mobile store and they gave me a new sim. it worked for a day then the issues came back then i called and found out they had accidentally switched me to a windows phone plan.

it's free to get a new sim. do that first and then call and make sure they have you on the right plan and voila!
[Nexus One Android Development] chichoCRZ:
I went as far as reinstalling the ROM (cleared partition, dalvik cache, and factory reset), did not install gapps, just signed in to my Google account and I currently have 175MB of free system space. Looking at my installed apps which were included with the ROM I am not sure there is anything else left to uninstall. I have actually reinstalled a few times and even tried out an older version of ClockworkMod 3.0.0.5, not sure why now the wifi calling apk is giving me trouble.

Thank you taney for passing on your experience. As it turned out, T-Mobile had added me to my wife's old smartphone plan which was not an Android plan for no apparent reason. After they reinstated my old data plan I am now back on the network through the original APN settings.

Before changing my APN settings sometime back I also changed my SIM card and it also worked for only one day. Here I was messing with my phone like a mad man and all along it was T-Mo's mistake.
[Nexus One Android Development] baseballfanz:
That's weird, have about 26mb system space and wifi app work fine
[Nexus One Android Development] taney:
Glad that I was able to help! I feel you on the "mad man" part. It got me so frustrated! I'm so happy that we have a huge N1 community on here. =)
[Nexus One Android Development] rock7632:
Is this working on CM7 nightlies post 7.1? and if so is it the file in the original post that you have to flash?
[Nexus One Android Development] baseballfanz:
It will work on nightly up to 233, starting at 235 and anything after that cause lockscreen reboot.

It does work on a Kang 235 version.:D
[Nexus One Android Development] rock7632:
oh ok, thanks. I have 236 flashed so I guess its a no-go
[Nexus One Android Development] baseballfanz:
How did you get 236?:D
[Nexus One Android Development] baseballfanz:
Regarding the Tmobile wifi ad on causing reboot with CM nightly (Starting at 235)

Looking at the change log, the only thing that changed for the Passion (N1) from 233 to 235 is the VM Heap size

http://review.cyanogenmod.com/#change,9286

changed it back to 32 and wifi ad on flashed without reboot.

Now how would one go about modifying the app to work with the new heap size
[Nexus One Android Development] DaXmax:
Heap size has something to do with this?? Cant be! Btw, this is the only wifi calling app available??
[Nexus One Android Development] baseballfanz:
Looks like it, I have tried flashing this wifi add on since 235 up to 240 and it always reboot at the lockscreen (like a soft reboot but it will keep cycling).

After I changed heap size it boot up after the first try with 240.

Hope someone else try and see what happen.
[Nexus One Android Development] N1_Fan:
Works great. Can even change heap size back to 48 and phone reboots no problem. Thanks.
[Nexus One Android Development] baseballfanz:
Yeah we'll just have to remember to change it to 32 before flashing
[Nexus One Android Development] N1_Fan:
App is not liking #242. After setting heap size to 32 it will flash and boot fine, but the app wont open. Anyone smarter than me have ideas?
[Nexus One Android Development] baseballfanz:
On 242 and it open and working fine. I left my heap size at 32m, no point in changing it to 48 as a bench test show no different. Actually 32m was a bit better.
[Nexus One Android Development] N1_Fan:
I'll try again and make sure I have enough internal memory.

Edit: Working again. Must not have cleared enough space prior to flashing.
[Nexus One Android Development] taney:
yup, it's a system app and CM7 builds are getting bigger. therefore you have to clean out system. i re-partitioned my stock nand with blackrose so i never have that problem.
[Nexus One Android Development] baseballfanz:
I use a file SystemAppRemover.zip

flash CM7 ROM

flash SystemAppRemover.zip (this delete all unwanted apps from system)

flash WiFi add on.
[Nexus One Android Development] taney:
that works too. you just have to have enough free space in /system before you flash the wifi app. you can boot CM7 and remove some system apps manually and then flash the wifi app. it works the same.
[Nexus One Android Development] jimbobalu:
I have 10MB of free system space, is this enough to install wifi calling?

Thanks
[Nexus One Android Development] baseballfanz:
I would say a little more is need but you could always try and if it don't work go back and clear some more space.
[Nexus One Android Development] jimbobalu:
If I don't use any wallpapers is it OK to remove the CM and live wallpapers? This would free almost 10MB giving me almost 20MB free, looks like the app needs 15MB.

I do use the "No Wallpaper" wallpaper.
[Nexus One Android Development] baseballfanz:
That's fine. I have removed cm wallpapers, live wp and a whole bunch of other stuffs I never use
[Nexus One Android Development] ctfrommn:
Themes that you dont use also take up a lot of space.
[Nexus One Android Development] rsdunn:
Does anyone have this working on CM 7.1.0-N1? I tried update3 and my SIM card was throwing invalid error... VM HEAP @ 32MB...
[Nexus One Android Development] baseballfanz:
do you have enouh system memory?
[Nexus One Android Development] rsdunn:
Here's what I have prior..

Total Used Free

/dev/block/mtdblock3 145.0M 133.2M 11.8M 92% /system

/dev/block/mtdblock5 196.3M 114.4M 81.9M 58% /data

Not sure if this is enough to load the update3 or not??
[Nexus One Android Development] avgjoemomma:
I'm having problems with this as well. Running the latest CM nightly (currently 253). I have 26MB free on /system after installing the Wifi Calling zip. When I try to turn on Wifi Calling, the app just stays on Enabling and that's it, the status never changes:(
[Nexus One Android Development] rsdunn:
OK removed both LiveWallPapers and CMWallpapers and the WiFi calling is working well !!

NICE WORK! Thanks a million
[Nexus One Android Development] avgjoemomma:
In the My network section, can someone tell me the values for UNC and SGW Address?
[Nexus One Android Development] baseballfanz:
Yeah me too now. Been running around all day so I never was on WiFi calling.

I went back to an old nightly that I know was working and it's the same. Hopefully

it's maybe a Tmobile server problems or something. I'm in Houston TX and it's been raining storming here.:(

EDIT: Finally got it to work on an older nightly but still not working with nightly 253:(
[Nexus One Android Development] avgjoemomma:
Ah, so maybe hopefully someone will figure out what's wrong and patch us up soon:o
[Nexus One Android Development] unforgiven512:
If you guys are familiar with adb, you can help me out.

Pastebin the output of `adb logcat` and `adb logcat -b radio`

Start the commands while on your home screen. Open the app. Hit enable. Wait one minute. Send me the results.

That'd help me out immensely.

If not, I will try to get to fixing it over the next few days. Thanks!
[Nexus One Android Development] avgjoemomma:
Thanks, just send you some logs :D
[Nexus One Android Development] baseballfanz:
Logcat

http://pastebin.com/kXXrQEBt

Logcat -b radio

http://pastebin.com/6rerR05T

Let me know if you need any more infos, thank you unforgiven512
[Nexus One Android Development] avgjoemomma:
Hoping there's a fix for this, I'm almost out of minutes :eek:
[Nexus One Android Development] baseballfanz:
You could go back to an older build that work till it's sorted out.
[Nexus One Android Development] baseballfanz:
Just flashed a Kang version of cm7 and it's working once again:)
[Nexus One Android Development] avgjoemomma:
Which kang if you don't mind me asking? :p
[Nexus One Android Development] baseballfanz:
I use temasek's

http://www.mediafire.com/temasek#wjy2920vw2wwc

It's P253
[Nexus One Android Development] avgjoemomma:
Awesome, thanks! I'll try it later today. Temasek's kang shouldn't be too whacky :p

---------- Post added at 09:17 PM ---------- Previous post was at 08:32 PM ----------

Installed just fine but Wifi calling still does not work :(

E/KINETO ( 754): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 754): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 754): Connecting... socket = 58, state = 0
D/KIPCapp ( 754): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 754): Connect failed 111
[Nexus One Android Development] baseballfanz:
That's weird, sorry to hear.
[Nexus One Android Development] avgjoemomma:
No problem, it's worth trying hehe. I'm going through this thread right now to see if it might offer anything: http://xdaforums.com/showthread.php?t=1038784

Can you post all the ril entries ( grep ril /system/build.prop ) and mobiledata.interfaces ( grep mobiledata.interfaces /system/build.prop )

I'll compare mine to see if that might be the issue. Thanks :D
[Nexus One Android Development] avgjoemomma:
Fixed it!!!

Just had to make the following changes to my /system/build.prop

Comment out

rild.libpath=/system/lib/libhtc_ril.so

Add

rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2,ppp0,ppp1,ppp2
[Nexus One Android Development] Michael Spencer:
The original patch finally worked for me. I had to free fifteen megabytes from /system and then patch it. That was difficult but totally worth it.
[Nexus One Android Development] pkgingo:
Hey unforgiven!

I've been messing around with WiFi Calling for the HTC HD2 since they both have a QSD8250. I was pleasantly surprised! I am running an old Nightly of Cyanogenmod 7.1 and wanted to see if I could increase the mic gain somehow. I figure, what have I got to loose as long as I back up my old libraries... well.. I replaced my libraries with the ones from here (also require installation of it's app APK, optimizer is the same):

http://xdaforums.com/showthread.php?t=1083729 in the file wifi-calling-htcleo-gb+new+for+miui+1.5.27.zip

It just shaved 10 meg off of the package and it works, and I am told VERY SLIGHTLY louder.

I've been disassembling the libkineto.so and noticed its running opencore-amr so, my next step would be to prod around and try to find out how I can increase the gain as the frame is encoding... this is a messy solution but it's something... perhaps having a pass through library that passes all library calls to the kineto library with the exception of a gain multiplier on the frames?

Have you made any progress on the volume issue at all before I start tearing this apart?
[Nexus One Android Development] avgjoemomma:
Nice job, pkgingo!!! :D I repackaged the files, deleted the old files that were installed and installed the new versions. Works like a charm! Saves about 10MB thanks to the updated libs and the exclusion of the old libcryp98.so. We also get a slightly updated kineto apk :)

If anyone needs a copy, I've attached it. Make sure to add the build.prop entries. If anyone wants to script that, it would be awesome.

/system/build.prop

Comment out

rild.libpath=/system/lib/libhtc_ril.so

Add

rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2,ppp0,ppp1,ppp2
[Nexus One Android Development] avgjoemomma:
OK, so I wanted to figure out why the build.prop wasn't getting patched and got a fully working update.zip built using D4rKn3sSyS's Update Zip Maker

Disclaimer: This works 100% for me with a stock CM 7.x nightly build. Hopefully it works for you and does not mess anything up:o
[Nexus One Android Development] avgjoemomma:
I'm hoping someone that knows this stuff more than I can jump in. I was checking out some newer versions of the kineto apk and library files, example : http://xdaforums.com/showthread.php?t=1216683

It looks like the GAN Optimizer has been replaced with a more robust QoS implementation. This is just speculation based on the new library files that are being loaded. It might be a good idea to see if we can upgrade the lib files then move onto the apks. The updated libs should provide the same needed functionality for the current apk we are using but also provide the networking improvements.
[Nexus One Android Development] pkgingo:
Hmm, I think I disagree, but I could be wrong. I haven't looked at the optimizer yet but if I recall correctly, I remember the optimizer putting out some logcats about adjusting process priorities. I think the optimizer is needed on older devices simply because of their underpowered nature (your conversation will get choppy if your device can't encode the data fast enough or is bogged down by other requests). I don't think this is a problem on celluar calling because this may take place in the modem itself... then again, for me, this is also speculation.

I haven't checked where the settings for the wifi calling comes from but I assume its in the app APK. But if the rogers APK works with T-Mobile, then that would disprove this theory. Similarly, I know it also checks the sim card for some things, perhaps network matching (my old voicestream sim card worked flawlessly).

Regardless, I've been looking to get a Sony Xperia Play (may be possible by cannibalizing the mytouch4g stuff but without one I have no idea and I can't afford to get one on a hunch, but mainly... I WANT that gamepad!!!!) and the biggest hurdle to me in doing so is that it offers no 3G or WiFi calling. If I had WiFi calling, I would happily cancel my data plan and just use it on wifi so, nevertheless, I will be digging deeper and maybe making an open source generic ril switcher if I can figure it out.
[Nexus One Android Development] avgjoemomma:
Hmm, well we'd have to look into what the Optimizer is doing. I just don't think we need to worry about process optimization on our N1's running GB or higher. I'd imagine it would be making some networking tweaks, but who knows :p

I did take a look at the Roger's Kineto.apk but it has the Roger's certs, network IPs, etc hardcoded. If you switch those out with the ones from the T-Mobile one you should be good to go. It might be worth trying to do that as we'd get the newer apk (bugfixes, etc) to go along with the new libs.
[Nexus One Android Development] avgjoemomma:
In case anyone is interested, I put together a new package with a slightly newer WiFi calling apk from T-Mobile and also updated libkineto and libganril. Works perfectly on my Nexus One running CM7.x nightly build 253.

Remove your current WiFi calling app before installing the new one.