yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] dublus:
Tytung - I finally got wifi calling to work perfectly. Thank you for your hard work.

The last piece of the puzzle for me was to uninstall Volume+. For some reason it makes the phone freeze when either wifi signal drops or wifi app is disabled after it has been enabled. This was so hard to figure out so I wanted to make sure anyone who is using Volume+ knows they will never get wifi calling to work without occasionally freezing their phone unless they remove Volume+. I am going to let the Volume+ dev know. Maybe he can figure out why it does it. Tytung, you might want to put a warning on the first page.

*Edit - I have also discovered the wifi app is very sensitive to low clock speeds and the level at which different phones freeze is different from one phone to the next. Very similar to how phones have different thresholds for the Sleep of Death (SOD) with respect to lowered clock frequencies. This became obvious as I started installing and enabling wifi calling on all of the 5 HD2's in our family. The first one went without any problems and continues to perform flawlessly (once I removed Volume+) but the next one would freeze up. Once I raised the minimum clock frequency the freezes were completely eliminated. Now I will find the minimum clocks for each phone and re-install volume+ to see if it was merely a contributor and not a cause.
[HD2 Android NAND Development] tyrone1:
Any chance to get this working on clk???

Works perfectly fine on mag typhoon.
[HD2 Android NAND Development] trex3300:
Since both clk and wificalling need ppp to connect, you will have wificalling but loose data once you get out of your wifi range. It works perfectly on MAGLDR because MAGLDR uses RMNET by default. Until someone is able to get RMNET to work on clk, wificalling on clk will not be perfect.
[HD2 Android NAND Development] gudmundsonsc:
First, thanks to all who have helped make wifi calling a possibility with SD haret booted android on the HD2. The 23 August instructions are the first time this has ever worked for me. I did have to go get a new SIM card before it worked.

I still have one windows mobile app for which I have not found a suitable replacement on android: GPSTuner 5.6. Once I find a replacement for it then I will move to NAND instead of SD. Also having a working swype in android is a high priority for me.

Now, this wifi calling solution introduces a new problem for me: no mobile data. Only wifi works. I know the post says PPP will not work. I assume there is a way for me to get RMNET to work? What should I try. Other threads talk about scripts to run using gscript to swtich between RMNET and PPP, but seem to be outdated instructions. Some threads talk about settings a parameter in the startup.txt, which didn't work. Not sure whether it matters, but I do have android data service on my account. And I have used my 3G mobile data on android before adding the wifi calling patch files.

Any advice on how to get RMNET working while having wifi calling working will be greatly appreciated.
[HD2 Android NAND Development] tytung:
WiFi Calling works well on cLK.

The side effect is that you will lose PPP data connection feature.
[HD2 Android NAND Development] trex3300:
Hey tytung,

I currently have cwm_recovery with 135MB partition, if I flash a cwm_recovery with 145MB partition to make room for wificalling app, will my backed up rom work with the new partition or do I have to do a clean install?

Thanks
[HD2 Android NAND Development] tytung:
You can restore your backup from CWM.

System partition size won't cause any problem as long as new size is bigger than your system.img made by CWM.

Since you enlarge your system partition, you won't get any trouble.

However, you can use another solution:

Convert Google Maps from system app to user app (i.e. move to data partition) by using Titanium Backup to increase the remaining space of the system partition.
[HD2 Android NAND Development] gudmundsonsc:
Since PPP does not work with wifi calling, how does one enable RMNET in its place?
[HD2 Android NAND Development] dublus:
I have edited my post up above to reflect the following:

If your phone sometimes freezes up go into settings/CyanogenMod settings/Performance/CPU settings/Min CPU frequency and set the frequency equal to the Max CPU frequency.

See if that fixes your phone freezing issue. It fixed mine, then I lowered the setting until I found the level at which the phone started freezing again then bumped it back up a bit. Funny thing is, it didn't make a difference in the current consumption while sleeping. Either way I always get 3 mA. We have 5 HD2's in our family and this was the last fix that got all of them running perfectly with wifi calling on t-mo.

THANK YOU TYTUNG!!!!
[HD2 Android NAND Development] trex3300:
Wificalling uses PPP. If you are using MAGLDR, then you have nothing to worry about. However, for those with cLK, your wificalling will still work but you will loose data connection once you are out of your wifi range.
[HD2 Android NAND Development] trex3300:
Good job, keep us posted. By the way, do you get a warm handover once you are out of your wifi range?
[HD2 Android NAND Development] dublus:
Sadly, there is no warm handover with the Kineto app like there is with the original HotSpot calling phones. I've owned just about all of them, the last one being a Blackberry Bold 9700. From what I've read, the app simply wasn't designed to do it and once you move out of range of the wifi signal the call just drops. For me, the benefits of android far outweigh the lack of a warm handover.
[HD2 Android NAND Development] trex3300:
I agree with you, Android is the king. Also, I too can live with no warm handover. All thanks to tytung for his work on this wificalling app.
[HD2 Android NAND Development] tytung:
WOW! Five HD2's. :eek:

Thanks for sharing your finding.
[HD2 Android NAND Development] dublus:
You are the one that deserves the thanks my friend. It's fantastic that we can use wifi calling again. There are actually 7 of us, the other two have rooted iPhones - yuk.

We have the original unlimited t-mo wifi calling and between that and the 5 faves and the Google Voice callback app we never get above 400 minutes in a month and we all talk as much as we want. Last month, without wifi calling, we came within 5 minutes of our limit (only 700).

Also, I forgot to mention, with the most stubborn phone and the freeze-ups (mine, of course) I had to change the governor to conservative or it would freeze up if the wifi signal dropped and the phone was sleeping. If it was awake, no problem, only when it was sleeping. I don't know if any other governor works but I know smartass and interactive didn't.
[HD2 Android NAND Development] Slavid:
I must have one of the stubborn HD2's. I have never been able to get this to work. I got the new sim card and can complete 1 call before phone freezes. I'm using Nexus 2.9 nand and I don't have Volume + installed. Since it's not a CM7 Rom I don't have the the Cyanogen Mod settings to change the CPU frequency. I downloaded Set CPU from the forum and set the scaling to Conservative, I think this corresponds with governor on CM7, and I raised the min frequency substantially and I still can't seem to get it to stop freezing. One other interesting thing is that once I complete the first call, if I try to adjust the ringer volume with the rocker switch, the screen says "In Call Volume" and not "Ringer Volume" even though the call has ended. Any advice is greatly appreciated.
[HD2 Android NAND Development] dublus:
I would suggest doing what I did.

If you have a spare phone it makes it much easier because you can quickly discover a setup that, in principle, should work even if it requires further fine tuning on a different phone, which is exactly what happened to me. I had a spare so it was easy to find a "base" setup that would work. The two I tried were the TyphooN and Dorimanx ROMs in their most basic forms and they both worked. Once I tried it on my daily use phone I got different results so I assumed it was something I had added. I started to systematically remove everything I had added or changed over the months until it seemed to work. I could make calls, turn off and on the app and wifi without freezeups. That's when I started to notice the Sleep of Death (SOD) issue occurring that I wrote about above. It was happening all along but now it was the only problem left so I could concentrate on it.

Good luck!
[HD2 Android NAND Development] trex3300:
I gave the wificalling app another shot yesterday. I used the August 23 universal Nand update with tytung's v3.0. No matter what I do, the app will crash after 3-4 calls. I did not mess with clock or governor settings, I believe changing v3.0 scalling to anything other than interractive will mess up the bluetooth functionality. By the way, I have new SIM card and I don't use volume+. Hope someone else could figure out what need to be tweaked to get tytung's rom to work with the wificalling without crashing after few calls.

If only we could bring tytung to the United States for few days, all these wificalling issues will disappear. ;)
[HD2 Android NAND Development] dublus:
So, I was just about to walk out the door this morning and my daughter calls to tell me someone just rear-ended her. She tells me where she is between here and the high school and I start driving over. About a block from our house I pick up my phone to call her back and it's... FROZEN! Noooooooooooooooooooo!

Apparently, all my work has been able to do is make the freeze-ups "less likely".

Now I'm pretty frustrated but not ready to admit defeat. I'm thinking to myself, what could cause freeze-ups to be more likely to happen when resources are low and clock is slow but still possible to happen even after a fresh boot (it's freezing on me right now, even after a fresh boot)? It almost seems like from one boot to next, things get setup in a different priority and that there are also some Gingerbread memory management issues that can cause bad things to happen. Then I remembered reading about the "V6 SuperCharger" something-or-other that somehow prioritizes things so the phone runs more efficiently. Back when I was reading about it, the only reason I didn't try it out was it says you should have Busybox 1.18.2 or earlier and mine was later so I didn't feel like messing with it.

Anyway, I found the thread here and started reading again. So, guess what? After running the script I am back to no more freeze-ups. Coincidence? Maybe so. That's why I'm posting here. Can some people that have had freeze-up problems go to the thread and get the script (V6_SuperCharger_for_Android-update9beta1.sh.txt) and run it to see if it helps?

Follow the basic instructions here.

The version shown in the screenshots of the tutorial are a little different because it's an earlier version but the basic steps are the same. I choose option 6, "Balanced 3 settings".

Just follow the instructions and report back if it helps. Thanks.

*Edit - no freezes until I stressed the phone by loading up several memory-hog type apps then left home (thus dropping wifi). Phone froze. Back to the drawing board.

It still seems like the wifi app is having a hard time cleaning up after itself when it is disabled and if I could assign all of the associated services a high enough priority the freezing might go away. Maybe some supporting service is even getting whacked?

I think what bothers me the most is my wife's phone has never frozen once. Why?
[HD2 Android NAND Development] Slavid:
I switched ROMs from Tytung's Nexus Rom to Typhoon's CM7 and it started working better. I've had it running all evening. I did however have to adjust the minimum cpu frequency to 691mhzand change the governor to conservative in the CM7 performance settings. I started out with the minimum pretty high and slowly started working it down and when I tried 652 it froze up. Thanks everyone for working on this. The signal in my house is terrible. I have to stand in a certain spot in my kitchet or it cuts out. Wifi calling would be a great help.

Thanks
[HD2 Android NAND Development] dublus:
Does anyone, Tytung maybe, know how to find out all dependencies for a particular app or process?

I want to set higher priority (renice) to anything related to the Kineto app so they all stay in RAM to see what happens.
[HD2 Android NAND Development] zdentist:
I keep on getting wifi force close any help is appreciated
[HD2 Android NAND Development] tytung:
I don't know what apps or commands can check dependencies on Android.
[HD2 Android NAND Development] tytung:
You need to provide more info.

For example:

Did you update to a new SIM card?

Did you install Volume+ app?

Did you change CPU governor?
[HD2 Android NAND Development] AEBobby912:
Wifi calling works flawlessly for meeee. I have Volume + installed as well and everything is great!:D
[HD2 Android NAND Development] dublus:
Is there a way to wipe a phone that is a "deeper" wipe than a task 29 ? Is it possible for the radio to be buggy but still work?

We have 5 HD2's. Of the five, two of them seem to be much more stable, in general, than the other. Two of the less stable phones seem incapable of running the wifi calling app without occasional freeze-ups - even with the exact ROM, settings, etc. as one of the more stable phones that never freeze. Sometimes they work well for a while and they trick me into thinking they are working right. Then they freeze again. I know that some of the things I've tried have made them freeze less often but they never completely stop freezing.

The last thing I tried was to take one of them and do a task 29 and only put the minimum things required for wifi calling to work. With even this minimized setup the phone still freezes after a while. This has to mean that either the phone just simply is different (hardware) or something running on the phone is having a problem that it doesn't have on the other phone.

So, that's why I ask, is there a more complete wipe than task 29 or could the radio be buggy or something else ?
[HD2 Android NAND Development] trex3300:
One more thing to consider, as soon as I install the wificalling app, I always test it by making and receiving many calls, and by the time I get to call number 4 or 5, the wificalling app will freeze my phone. The calls are usually short and few seconds or minutes apart, now is there something in the wificaliing app that is not shutting down and call up again properly anytime you make many calls in quick succession, like few minutes aparts?

By the way, I have not tested the above theory by doing something like making one call per hour.
[HD2 Android NAND Development] dublus:
So I admitted defeat and traded phones with one of my daughters that doesn't need wifi calling. Strange how out of 5 phones that are configured identically, 2 of them have problems running the wifi calling app while the other 3 run it without skipping a beat. The this kind of thing makes me crazy.
[HD2 Android NAND Development] MarkAtHome:
I am not sure if this is exactly what you are looking for, but check out Autorun Manager at the market.
[HD2 Android NAND Development] dublus:
Here's an update in my quest for getting all 5 of our rooted HD2's working with t-mo wifi calling.

Two posts above I mentioned I was switching phones with my daughter because hers worked with wifi calling and mine had the freeze problem and she doesn't really need wifi calling anyway.

Once I switched I had absolutely perfect wifi calling. Not a single problem. Along with that, something else happened - my daughter also still has flawless wifi calling using the phone that often froze on me. So, I put my sim card in her (my old) phone and, sure enough, the phone freezes like it did before. Just to be complete about it, I totally restored the phone to be mine again with all my apps and settings and got the same result - her sim = phone perfect, my sim = phone freezes.

The only conclusion I can draw from this is that even if you've got the newest sim card you may still have problems with wifi calling. Luckily for me, I've got 5 different phones to play with.

Today, I'm going to drop by the t-mobile store to see if I can get a new sim card. They were happy to replace the older style ones we had but I don't know what they will say when I tell them my new one doesn't work like it should and I want another new one.
[HD2 Android NAND Development] tytung:
R12 beta 3 kernel

R12 beta 3 kernel with an updated kineto_gan.ko kernel module. (Added HTC Official kineto_gan.c for WiFi Calling)

Please try r12 beta 3 kernel (removed, please use r12 final) with WiFi-Calling-htcleo-GB_for_NAND_v2.zip to see if they solve the phone freeze issue. Thanks.
[HD2 Android NAND Development] dublus:
Tytung, thank you so much for your efforts in getting wifi calling to work, even though you aren't even a t-mobile customer. People like you are what make this community so valuable.

I won't be able to test the new kineto to see if it fixes my freezing because yesterday I traded my sim card (already the new type) for another new one and all my freezing issues are completely gone. It appears as though all of the new sim cards are not created equally. I will also swap out the one in my son-in-law's phone to see if it has the same effect. I have a feeling it will.

For anyone that's getting any type of freezing, even if you already got a new sim like I did, I encourage you to get another one.

The way I did it was going on the online chat, tell the csr your phone freezes with your sim card in it but not when a different one is in it (that's what made me realize it had to be the sim) and have the csr note the account to give a free sim. Without the note on my account, the guy at the store would never have given me one. He was very insistent that it couldn't possibly be the sim and carefully checked my account to make sure it was noted about the free sim. Even after that, he wanted to argue about it with me.

Perhaps someone else with wifi calling problems can try the new kernel and report back the result.

On a side note, I have been using wifi calling, even with the freeze-ups for the current billing period which ends Sunday. Between the 5 faves, t-mo to t-mo, google voice, and wifi calling I have used a total of 6 "anytime" minutes. The vast majority of the minutes that would have been "anytime" minutes changed to free minutes because of the wifi calling at home and at work.

Again, thank you, Tytung!
[HD2 Android NAND Development] tytung:
I'm glad to know that new SIM card works for you.

If you (or anyone) have time, could you please still test the new beta kernel?

Because I cannot ensure if using new kineto_gan.ko kernel module has any side effect or not. (i.e. break WiFi Calling or make it unstable compared to the previous one)

If the new beta kernel doesn't have any side effect, I will keep the new source code in the next kernel release, r12 final. Otherwise, I will remove this source code change.
[HD2 Android NAND Development] TheSkilled1:
I tried both v2 and the r12 and it seems okay so far. I was having freezing problems before even with new install and new sim card. I havent made many calls yet but i'll update this post when i do

edit: wifi calling seems to work fine now with no freezes but i don't have any signal when not using wifi calling. When i'm outside i have no signal at all.

edit2: It seems as if its on and off. sometimes Wifi calling would work but i would have no signal and sometime it says i'm not registered and w005.4 i'm going to call tmobile and see if they would enable wifi calling on my line anyway.
[HD2 Android NAND Development] trex3300:
I flashed the r12 beta 3 kernel and wificalling-NAND_v2.zip, unfortunately, my phone froze after about 3 calls, I reboot and it froze again after the second call. I have a new SIM card however, I will try to get the SIM card replaced again and give it another shot.

Thank you tytung, you are the best.
[HD2 Android NAND Development] tytung:
Thanks for testing.

Since WiFi Calling still works, I will keep new source code kineto_gan.c in r12 kernel.

I will release it soon.
[HD2 Android NAND Development] tytung:
Removed r12 beta 3 kernel and added r12 final kernel.

Sep. 12: tytung_r12 (For new/desire camera libs and HTC extended battery.)

Added proc file interface /proc/mic_level to fix low speakerphone mic gain (Credits to mdebeljuh and jdivic)

Included /system/etc/init.d/10mic_level (Set to '0 400' for Handset and '1 600' for Speaker)

Removed support for specific htcleo.acdb file to improve the booting speed when htcleo.acdb is not present.

Loaded the real MAC address from SPL if running SD build on WinMo 6.5. (Not for MAGLDR and cLK bootloaders) (Credits: savan and tytung)

Added HTC official kineto_gan.ko kernel module for T-Mobile Wi-Fi Calling.

Downloads:

kernel_tytung_r12_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included stock default.acdb and Gpc's libaudio.so.)
[HD2 Android NAND Development] dublus:
Sorry, but is the "update" the same as "final" or do we need to flash the update over the beta?
[HD2 Android NAND Development] trex3300:
kernel_tytung_r12_update = kernel_tytung_r12_final = kernel_tytung_r12

Yes, just flash the update/final over the beta or over whatever older version you have. Just remember to follow tytung flashing instruction from here.
[HD2 Android NAND Development] dmunseyautotech:
Wifi Calling

I can call out fine...no freezing, but phone will not wakeup to recieve call. If I wake it up manually call will come thru. Changed wifi settings to never disable when screen off. Any ideas,
[HD2 Android NAND Development] tytung:
Sep. 13 update:

Included the latest lib and updated settings of default.prop from HTC Glacier ROM which supports T-Mobile WiFi Calling.

WiFi-Calling-htcleo-GB_for_NAND_v2.zip (for MAGLDR) after flashing any Gingerbread NAND ROMs.

WiFi-Calling-htcleo-GB_for_SD_v2.zip (for WM6.5) when running any Gingerbread SD builds.

You can use r12 final kernel with WiFi-Calling-htcleo-GB_for_XX_v2 update files because r12 includes the latest HTC official WiFi Calling kernel module (kineto_gan.ko) from HTC Glacier.

I'm not a T-Mobile customer, so I cannot test them.

Remember to backup your ROM before testing.
[HD2 Android NAND Development] tyrone1:
So how can I use this on clk? I remember you said it can be done but data will be messed up or something like that.

I tried installing the zip from clk but when try to run app force closes.
[HD2 Android NAND Development] Slavid:
I tried the kernel and then installed the Sept 13th update. It froze the first time I went out of Wifi range and it's been fine since. Until now, this hasn't worked well at all. It kept freezing after the first couple calls. It seems like this fixed it for me.

Thanks

I installed the Sept 13 update and have been running it for a couple hours now. I've come and gone in and out of wifi coverage and the phone did not freeze. I also updated my second HD2 and it hasn't had a problem either. This may be finished. Congrats and Thanks!!!
[HD2 Android NAND Development] kbsc:
after getting a new sim card everything is working perfect...thank you for ur hard work and time...it is greatly appreciated...
[HD2 Android NAND Development] Slavid:
Well, the phone still freezes from time to time. Usually when it's plugged in charging with the screen off or when going in and out of wifi range. The building I work in is particularly challenging. While the entire building has wifi, there are places where the signal is low or there is no coverage. Place like stairwells and office on the outer edges of the building have low or no singal. The phone tends to freeze when moving about. If I leave it at my desk it stays connected to wifi and all is well. Any ideas anyone. I've replaced the sim card some time ago, I'm using Typhoon CM7 with r12 final kernel.

Thanks