yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] player911:
I've been using this for a few days now and it is purely awesome!!!

At work I have 0 signal. With this, its awesome because I can connect to the wifi and now able to receive calls, sms, and mms. This would also be great while at home too.

I just wonder which signal uses more battery? WiFi or Cellular?
[Nexus One Android Development] superg81:
im stll stuck on the x screen :(
[Nexus One Android Development] NPS_CA:
Working for me on 5.12.00.08 radio and I also have latest HBOOT.

Those getting boot loops/no boot have you ran adb logcat to see what is going on??
[Nexus One Android Development] pphatmattzl:
I was originally having the forced reboot problem with this app. I was running the 4.06 radio initially with CM7 build 7. I since then flashed 5.08 radio, and then was able to run the program with no problem.

Due to the 5.08 radio, I did not get as good of service in my area (Los Angeles, T-Mobile) so I then updated to the 5.12 radio and have been getting much better service and the app still does perform its function.

Also I always like using the wildmonks kernel with CM7 because I get better battery performance. I can confirm the following for my case:

CM7 Build #7,8

-4.06 radio did not work

-5.08 radio did work

-5.12 radio Does work

-Cyanogen Kernel's used with these and they did work

-Using the .35 HBOOT

Fitsnugly's Nightly Compiles of CM7 Built on 1/20 & 1/21

-5.08 radio did work

-5.12 radio did work

-Cyanogen kernel and wildmonk's [.35.10] CFS SVS (CM7 specific) kernel did work

-Using the .35 HBOOT

Thank you unforgiven512 for the support and for this port, it is now working fantastic and it is a great help!
[Nexus One Android Development] samir5421:
Works great! using custom cm7 build with 5.12 radio.
[Nexus One Android Development] garrisont:
Thank you so much. I've got no reception at work, and since we've been asked to use our personal phones you've quite literally saved me the cost and hassle of a new phone (donation on the way).

I tried this two days ago (unsure of the CM7 build) with the 4.06 radio; the result was endless re-boots.

I've been upgrading CM7 as the builds are released, I believe it's build #10 now, and I upgraded radios as suggested to 5.08. WiFi calling is working great now. I have one question and one suggestion however.

Is there anywhere I can find evaluations of 5.08 vs. 5.12 radios? The threads I've seen seem to have lots of "it seems" statments, not a ton of back to back speed checks. Maybe I just need to do them myself...

I'm no programmer so I'm not sure how practical this would be, but I like to setup a tasker schedule for my wifi policy in order to switch it to "always on" only when I'm in spotty reception areas (I've been using SIP calling at work). Would it be possible to include a time of day schedule on the app or better yet an option that reads cell signal, turns on the app and the cell service off, and then re-checks on some pre-defined schedule?

Hey a guy can dream right? Anyways, thanks again, awesome work!
[Nexus One Android Development] bighead21:
Works great over here... Running Fitsnugly's latest w/ DTA2SD and 5.12 Radio
[Nexus One Android Development] gururise:
Works great on CM Nightly 9. I'm switching to Nightly 10 today, and hopefully with Nightly 11 and the new WiFi update, I'll finally have working MMS.

Thanks!

Now, if we can just do something about the low audio volume...
[Nexus One Android Development] ThunderStick:
Keeps force closing

Using the latest radio update and the latest CM7 Nightly build

Flashed using Clockwork Recovery

With full wipe from the start

ANy help is appreciated.
[Nexus One Android Development] mtw4991:
What is the problem??? We need more information, such as "did a full wipe, then flashed CM7, reboot, etc, etc".

If you are using DT's a2sd; flash rom, flash wifi zip, flash DT a2sd, reboot. Don't reboot until all are flashed. Maybe try reflashing...I had to do it twice to get it working. You also need a good wifi signal or it won't connect.
[Nexus One Android Development] gconcepts:
Anyone knows if this will work on Cyanogenmod 7 hd2? or is it only for Nexus 1?
[Nexus One Android Development] gconcepts:
Just read the PREREQUISITES. I guess NEXUS 1 only.
[Nexus One Android Development] xidominicanoix:
Just flashed over the newest CM7 Nightly (#12 IIRC)

Getting FC when trying to open the WiFi Calling App

Here's the lolcat: http://pastebin.com/CLdqDKFP

Thanks :D
[Nexus One Android Development] pc2828:
+1
[Nexus One Android Development] rjlan82:
I am getting force close as well
[Nexus One Android Development] ThunderStick:
I also get the force close with CM7 Nightly. I used Fitsnugly's release and it works great. No problems at all.

Not sure why, it just does.
[Nexus One Android Development] elililly:
+1 I also get force close in Built#13
[Nexus One Android Development] clashcity:
Build 13>Wildmonks Kernel>Download.zip and a 5.08 radio= Works great. Maybe the stock CM kernel is the problem for you guys?

I saw a commit for the kineto package added to the builds the other day, but it still wasn't playing nicely so I got the latest WM kernel.
[Nexus One Android Development] mikeacela:
Your in the Nexus one forum...

I can confirm this works on fitsnugly's compiled builds and his uses the stock CM kernel. Im using radio 5.08.
[Nexus One Android Development] mikeacela:
Out of curiosity, are you using his theme too? its beast lol
[Nexus One Android Development] gururise:
I also get Force Close on Build #13 of CM Nightly using the updated 1.1 Wifi calling zip. Please Fix!

All nightlies up to #10 worked great with the older 1.0 Wifi Calling zip. Something about the new updated 1.1 Wifi calling is not playing nicely with the newer CM Nightlies!
[Nexus One Android Development] gcng:
Same here
[Nexus One Android Development] tibere86:
Thank you so much! A quick question....does noise cancellation work during wifi calling? I have searched and have not found any answers. Can anyone confirm?
[Nexus One Android Development] unforgiven512:
This is quite odd -- the changes are there, but it seems as if 1.1 isn't working at the moment.

That's rather odd.

Anyhow, in the mean time, you can continue to use 1.0, and it will work fine. I will update the thread when 1.1 is working again. Sorry guys!
[Nexus One Android Development] mikebeatrice:
Can you please update the title of this thread with the version number or at least date of most recent version... I hadn't even realized there was an update...
[Nexus One Android Development] Manacit:
I'm getting force closes with #13, latest wm kernel and no theme. A soon as this is working, I'm switching to 7 for sure.
[Nexus One Android Development] baseballfanz:
Can't seems to get past the X no matter what Recovery I use or what order I flash
[Nexus One Android Development] Optimus1337:
I have been able to consistently get the new one working by flashing the old one then flashing the new one on top of it.
[Nexus One Android Development] mikebeatrice:
Try flashing CM7 first, boot up and make sure everything is good to go. Then go back, do a nandroid so you have a base to go back to and then try flashing wifi calling.

I had trouble the first time, but doing it like this seemed to work.
[Nexus One Android Development] baseballfanz:
Thanks, I'll give that a try. Finally did get past the X but is it normal to loose all your install apps? Cause once I booted up I'm lost all my install apps and trying to reinstall any of them put me in a boot loop:D
[Nexus One Android Development] opus1one1:
I can confirm that this works. Currently using build 13.
[Nexus One Android Development] mikebeatrice:
Sounds like you did a full wipe... that will wipe everything. What rom are you starting with? If already CM7, then just wipe cache and dalvik cache before flashing the next update... don't do a full wipe.
[Nexus One Android Development] baseballfanz:
Not a full wipe. Clear cache, clear dalvik, flash cm7, flash wifi, flash dt a2sd.

Maybe my flash order if wrong?
[Nexus One Android Development] mtw4991:
+2 figured this out the other day. Just flash original then update then reboot, all works fine.
[Nexus One Android Development] Manacit:
Holy crap, I didn't even think of doing this, but it worked like a charm! Thanks so much
[Nexus One Android Development] mikebeatrice:
Shouldn't have removed you apps...

Try doing everything EXCEPT wifi calling. Let it reboot, check to make sure a2sd is running right... move your dalvik back to SD if necessary, etc... then once you're sure everything is working, flash v1.0 of wifi calling and if you want, then v1.1 afterwards.
[Nexus One Android Development] Manacit:
Flashing 1.0 then 1.1 worked on build #14 as well!
[Nexus One Android Development] TechieWannabe:
#14 nightly + 1.0 wifi calling

Fast, stable, phone works, able to send MMS and access T-Mobile My Account app via wifi.
[Nexus One Android Development] salamandar:
How do you properly turn off WiFi calling and get 3g back without airplane mode or reboot. Shouldn't it just switch off and on according to available wifi signal?
[Nexus One Android Development] maximr:
Apologies if this isn't the right forum, but perhaps you could help. I have an HD2 that is running CyanogenMod 7, and would love to be able to use this. It seems that your package is device dependant - but I'm not sure where the actual problem might be. Are modules here kernel or device specific? Or is it radio that needs to be of Nexus One? How could we port this to HD2, which has almost identical hardware, but the implementation of NAND Android is very different because the device was originally designed for Windows Mobile 6.5?

Thanks a lot!
[Nexus One Android Development] AirforcProductions:
To add onto my friends post the CyanogenMod 7 we are currently running are Nexus One based
[Nexus One Android Development] mikebeatrice:
Go into settings... you have 3 choices.

wifi preferred

cell preferred

wifi only

If you pick wifi preferred, it will ALWAYS use wifi unless it's not available

opposite for cell... will always use cell unless it's not available.

If you launch the app you can just hit the little slider at the bottom to turn off wifi calling manually.
[Nexus One Android Development] baseballfanz:
Can't seems to get it working on build #14, actually can't get it working on any build.:D

Flash 1.0 than 1.1 after the phone reboot it hang on the X for a good long time, 15 minutes and phone get real hot.

I was able to install it on Snugfits CM7 but than all installed apps disappeared, LOL. When trying to restore those apps phone bootloop.

You guys that have it working, are you using DT A2SD also?
[Nexus One Android Development] GHOST99K:
not working on #14.Force close and overheating problem.how do i remove it?
[Nexus One Android Development] baseballfanz:
You need to restore back to the previous version if you did a nandroid backup
[Nexus One Android Development] GHOST99K:
NAND back to #10 then reflash #14 again without the add-on.:eek:

EDIT:WAITA MINUTEEEE!!! just flashed the 1/18/2011 which is 1.0 add-on and no FC? 1.1 didnt work on #14(FC).flashed 1.0 on #14, and its working fine(tested).
[Nexus One Android Development] baseballfanz:
Did you flash #14 and wifi 1.0 at the same time or after #14 reboot than wifi 1.0?
[Nexus One Android Development] Manacit:
I've got it working great on #14 - here's what I did.

I flashed 14, gapps, then my wildmonks kernel (you don't need to do that though), then I flashed 1.0, then I flashed 1.1, then I rebooted. Everything works great!
[Nexus One Android Development] GHOST99K:
flashed #14 with the 1.1,didnt work(FC and overheat).went back to recovery and just flashed 1.0(1/18/2011) over the non working 1.1 and rebooted and no FC's at all and also tested it out and works perfectly.try the 1.0 on #14 and see if it works.:D

NOTE:didnt go back to #10,just flashed 1.0 over the 1.1 on the #14.
[Nexus One Android Development] unforgiven512:
I have the issue isolated. Please use version 1.0 for now. I will update the OP shortly to reflect my findings.

The issue is, in 1.1, I've excluded my custom built libmedia.so, because the changes were incorporated in the CM repository, and should've been included in builds 11 and onwards.

However, there is a misconfiguration in the way the buildbots are building the nightlies. Before each build, they are doing $ make installclean, rather than a full $ make clean (or perhaps $ rm -rf out/target/), and this is causing certain parts to not be rebuilt from build to build. I've confirmed this from my own trials/studies on my computer. I will attempt to get in contact with TeamDouche and see if the necessary changes can be made, because I'm sure this is not the only thing that is being affected by this.

NOTE: I will clean this post up when I get on the computer, as well as update the OP. I apologize for the sloppiness.
[Nexus One Android Development] baseballfanz:
Hmmm, I have tried that with both 1.0 and 1.1 separately as well as 1.0 than 1.1 on top, also did 1.1 than 1.0 on top. All these method get me to the X and hang there. All these with build #14

If I use Snug's CM 7 I can get pass the X but all apps is gone and reinstalling them cause bootloop.

I think I will just wipe everything and do a clean install tonight to see what happen.:D
[Nexus One Android Development] blas4me:
I've tried it with nightly's 9-14 and all I get is FC's, I used 1.0 with 6.1 and it worked. Is this latest one compatible with a specific nightly or should it work with the all.
[Nexus One Android Development] baseballfanz:
OK this time I flashed build 14 without DT A2SD and all is good.

I guess this does not go well with DT?
[Nexus One Android Development] Manacit:
Thank you very much for staying up to date, WiFi calling is one of the things that makes Android awesome!
[Nexus One Android Development] mikebeatrice:
Works fine with DT here. Haven't even tried it without DT.

I did have problems the first couple times I tried to flash this. In order to solve it, this is what I did (starting from a CM7 nightly already, going to a new one)

1. nandroid

2. wipe cache/wipe dalvik cache

3. flash CM7

4. flash DT

5. reboot... check that everything is good to go.

usually I have to do a a2sd cachesdreset command at this point because it reverts to internal on my first boot after a fresh flash...

6. let it fully reboot after the dalvik move... check that everything is good.

7. boot back to recovery and flash wifi calling

Then everything was great. And since then all I have to do is do the standard, flash CM, then DT, then wifi calling and it boots up just fine.
[Nexus One Android Development] baseballfanz:
Thanks mike, tried it that way and got stuck at the X.

I'll keep trying different method, thanks for your times and assistance
[Nexus One Android Development] mikebeatrice:
That sucks...

so as soon as you apply either the DT or the wifi patch it hangs on you?

Try starting from a fully wiped start... or have you? You can always get back after the nandroid, but maybe there's something in your configuration that's hosing you up.

Do you have one of the 5.xx radios and the updated hboot?
[Nexus One Android Development] baseballfanz:
Yes I have the updated Hboot and 5.12 radio.

Even with a full wipe I can only get DT or WiFi but not both.:(
[Nexus One Android Development] baseballfanz:
Finally got it working with DT.:D

Steps to get it working for ME

-Flash nightlies

-Flash DTa2sd

-Let reboot, everything OK

-reboot into recovery, clear dalvik

-flash wifi.zip

-reboot

-Open TE and run a2sd cachesd command:D
[Nexus One Android Development] mikebeatrice:
Good deal. I knew you had to be getting close.
[Nexus One Android Development] baseballfanz:
Actually I figured out exactly my reason for being stuck on the X.

Not enough system memory.

I can flash WiFi app on build 17,18,and 19 no problems.

Can't do it with build 21 and remember I couldn't do it with build 16.

Went back an looked, those builds I can flash was much smaller ROM file.

So I moved a few apps from system/app to data/app and boom

now it install no problems.:D

That explained why before I can flashed either DT A2SD or WiFi app but not both.

No room for both.:D
[Nexus One Android Development] unforgiven512:
Warning: Do not flash this on build 21 yet. I am fixing it now.
[Nexus One Android Development] gururise:
I wish I would have read this before flashing.... it seems that flashing the wifi calling app to build #21 causes the DPI to get all screwy, and your icons become way way too small!
[Nexus One Android Development] unforgiven512:
Yeah, it's because of changes to the build.prop file that are causing the patch to be applied incorrectly. I have it fixed on my end, the file is currently uploading to my server.

Anyhow, to put everything straight, you will be able to use 1.2 with build 21 and above. And everything is set up correctly, and you won't have to jump through any hoops like flashing 1.0 then 1.1 or anything like that.

It will just work.

Watch for the update within the next 30 minutes.

So much for that. It appears my webhost is doing planned maintenance. I will update when things are live again.
[Nexus One Android Development] bachviet:
Yeap that's why I moved Gmail, Maps, Voice Search, and YouTube to /data/app and delete the CM wallpapers to free up system memory.
[Nexus One Android Development] Manacit:
I can offer you some free, fast and reliable hosting if you are interested? Its the least I can do after all of your hard work!
[Nexus One Android Development] gururise:
Any updates on the fix for build #21?
[Nexus One Android Development] baseballfanz:
The fix is done, he's waiting on his web server to be back online before he can upload it.
[Nexus One Android Development] Manacit:
It's killing me! I'm still on #20 and #22 just dropped! I'm addicted to these nightly builds! I can't wait for WiFi Calling 1.2 to drop!
[Nexus One Android Development] fitsnugly:
Or just push the files and edit your build.prop yourself...
[Nexus One Android Development] superg81:
care to show me?you know where to find me ;)
[Nexus One Android Development] unforgiven512:
Give me a PM and we'll talk about it. Anyhow, it was planned network maintenance (they were upgrading core software in their Cisco routers due to a security flaw in IOS), but, unfortunately, as that was occuring, there was a hardware failure on my server, and they had to have a tech go down there and pull the drives and drop them into a new system. But, everything is back up and running as it should be, and I am working on getting this live for you guys.

I truly apologize for the delay, and I thank you all for your support. I'm working on bringing it live right now, and provided nothing goes wrong, it should be up within 30 minutes.

EDIT: It's live! Get it here!
[Nexus One Android Development] depraved:
I've been using 1.1 on 17 here in the Philippines for the last couple of days to call the US and it has been absolutely 100% stable and amazingly perfect. Audio is almost perfect. I've spent at least a couple of hours on the phone from Philippines to the US in the last couple of days, not one dropped call, no FC's at all, no issues whatsoever. This thing works awesome.
[Nexus One Android Development] rickh925:
So you are on wifi in the Philippines and able to us wifi calling to make and receive calls using your T-Mobile number? That is awesome. I am going to Italy in a few months and wondered if that would work.
[Nexus One Android Development] gururise:
I was recently in Germany and used the Wifi calling app to make and receive phone calls just fine (on CM6.1). So yeah, should work fine.

One thing to be aware of is, if you decide to use a new SIM card in your phone, it may screw things up. When I was in Germany, I purchased a Tschibo SIM card so I would have local calling when not on wifi. The Wifi Calling App caused problems with the Tschibo SIM card (I would get a cell signal on boot, but after the phone sleeps, the cell signal never came back), EVEN WHEN I TURNED OFF THE WIFI CALLING APP this problem persisted.. I actually had to re-flash just the base CM6.1 w/o the Kineto.zip to be able to use another non T-mobile SIM card. Hopefully, its fixed with this version, but I don't know. Never figured out what the problem was.
[Nexus One Android Development] opus1one1:
I've experienced similar issues. As a general rule, if you're going to be using a non T-Mobile sim make sure you steer clear of Wifi Calling, since its UMA functionality is intrinsically tied to the T-Mobile USA network. In my case, I make sure the app is turned OFF before turning off the phone and swapping sim cards, which seems to prevent any issues.

I travel abroad constantly, and Wifi Calling has enabled me to virtually eliminate having to use other sim cards. There's nothing more convenient than being able to call and text with your own number, and the prevalence of wifi networks makes it hassle free. Wifi calling + Google voice is a deadly combination for international travel.
[Nexus One Android Development] CAL7:
Grandfathered UMA plans !

I just installed this (CM7b22, DTapps2sd 2.7.5.3b3) and it's working great. As expected, the other side of the conversation reports slightly reduced volume, but this is actually less a problem than I expected. There is a little static in my transmissions, but the receiving sound is great.

But the reason for my post is to report that T-Mobile identifies my calls as UMA under my old, but grandfathered and still active, plan with unlimited UMA. I.e, minutes do not come out of my bucket.

With my old blackberry, I was very successful wandering throughout the world and making free calls over UMA. Should be the same with WiFi Calling. As a previous poster said, there would likely be problems with a "local" SIM, since you would no longer be on the WiFi Calling supported T-Mobile network.
[Nexus One Android Development] Manacit:
Just wanted to thank you again for all of your work! Everything is working great with the latest nightly, and I didn't need to flash previous versions! Ill shoot you a pm later about hosting / mirroring. Thank you so much for all of your hard work!
[Nexus One Android Development] unforgiven512:
Wow, I'm glad to hear it's working well for all of you!

It's also good to know that WiFi Calling works world-wide! I plan on making an international trip next winter, so that is good to know.

WiFi Calling will not work with another SIM in the phone, it works, once again, with T-Mobile USA only. The SIM is still required, despite the fact that it is going over WiFi, because it is simply GSM/GPRS tunneled over IP. Everything works exactly the same, except that it's using WiFi and IP instead of the GSM signal radiating from the cell sites. It still authenticates your SIM against the core GSM network to identify you as a valid subscriber, etc.

If you're looking for a solution where you can use a foreign SIM, you may want to look into a SIP account.
[Nexus One Android Development] CAL7:
Bluetooth

The good news keeps on coming...

I don't think I read about bluetooth in this thread, but based on previous experience, I expected my bluetooth headset to not get along with WiFi calling. But, on a couple of test calls, it worked perfectly.
[Nexus One Android Development] alexsql:
Vanilla version

# Removed message
[Nexus One Android Development] Rijal:
Installed Wifi Hack - screen size issue

I installed the wifi calling add in, but now it appears that a setting got changed somewhere relating to the screen size/resoultion. The icons on the home screen are now extremely tiny, and have huge gaps between them (number of columns and rows were not changed). Programs & settings also use these tiny fonts for everything. I tried spare parts, and changing font size to extremely large, this helps get the settings screen almost back to the right size, but everything else is untouched.

Thoughts? I can always re-flash cyanogen's nightly, but wanted to check for ideas here first.

Thanks,

Rick
[Nexus One Android Development] baseballfanz:
Any build higher than 21 you need to to use v1.2

The older version wil cause the smaller icons
[Nexus One Android Development] Rijal:
That did the trick! Thanks!