yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] hay112:
I'm using tonight's cm7 build 1-19...flashed rom first then wifi calling...enabled wifi, then enabled wifi calling...instant restart...and will keep restarting

I just waited until it booted back up and instantly disabled wifi calling as fast as I could
[Nexus One Android Development] nwskier:
restarts

yeah same experience here. Using Cm7 nightly build 7 and been having instant reboots since install. I can't even disable and now am going to have to restore my backup. Pretty disappointing but that's what we get for mixing two betas lol
[Nexus One Android Development] unforgiven512:
Hmm, I just flashed build 7 on my Nexus One, and gave it a shot. I can not reproduce this issue. I tried rebuilding my libmedia.so from the latest source, and the md5's are identical, so nothing was changed. I have no idea what is causing this issue, however, if you can pull me a logcat or something, that would be wonderful. Also, if you would like, we could meet up in #cyanogenmod or something, and we can work this out.

I don't like bugs :(
[Nexus One Android Development] mikebeatrice:
That's amazing! Will give it a try later.

Can we also magically receive calls over wifi too?
[Nexus One Android Development] clashcity:
Yep. Just tried it out this morning. Now I won't have to worry about missed texts in my fortress of solitude as well!
[Nexus One Android Development] tuan209:
how is call volume and does it work with bluetooth?
[Nexus One Android Development] mtw4991:
dang, was on CM7 nightly build with DT a2sd and flashed the file with Amon_Ra then rebooted...no joy! Got stuck at the X and wouldn't load the OS, plus I didn't have a nandroid (stupid, lol) handy at home....dl'ing it now at work:p. Anyone else have issues installing the zip file with Amon_Ra recovery?
[Nexus One Android Development] pphatmattzl:
Having the same problem of the forced restart, pulled a logcat for you, sorry about the extra garble in there, i am not super familiar with how to filter out stuff you don't want in a logcat. I can reproduce it again and if you need I can start the logcat at boot to give you the most info.

(ironic that my 1st post is a logcat?)

Running CM7 build #7

CM Kernel

Sorry can't post a link yet, but here is the URL h**p://dl.dropbox.com/u/248961/logcat.rtf

EDIT: ClockworkMod Recovery
[Nexus One Android Development] lessthanjoey:
I used Amon_Ra and had no problem
[Nexus One Android Development] superg81:
Stuck at the x for me
[Nexus One Android Development] mtw4991:
redownloading and gonna try with CWM now....stay tuned, lol;) Nandroided 1st this time!

Edit: yay! got past the X and booting...fingers crossed for no bootlooping!

Edit2: booted up this time, idk why it worked this time?
[Nexus One Android Development] mikebeatrice:
Will this screw up MMS permanently, or only while wifi calling is enabled?
[Nexus One Android Development] jdubso:
It didn't mess up mms enabled or not for me.
[Nexus One Android Development] CiDhed:
Works great. Had to change the script to make it work as my build.prop file has the default density of 200. Thanks!
[Nexus One Android Development] chadtn:
1.3 stopped working for me around easter. I've really missed it.

Chad
[Nexus One Android Development] dubt17:
I don't know what it is, but every time I flash 1.3, it says my sim cards invalid, and no amount of wipes can fix it :/

Any help? I've had to get 2 new sim cards so far, and going to need a third...
[Nexus One Android Development] N1_Fan:
I get that same error if I do not flash wifi calling right after rom. Then I can flash dt and kernel after wifi calling and sim error goes away.
[Nexus One Android Development] CAL7:
My order is:

Wipe Cache, Dalvik Cache

ROM

Kernel

DTA2SD

WiFi Calling

No problems.
[Nexus One Android Development] salamandar:
I have had good success with s2e I flash and load in this order:

Wipe all

latest Fits release

GApps

Wifi Calling

Reboot

Skip sign in then enable WiFi

Launch Market (which prompts Google Acct Log In)

choose cancel when prompted to install google apps (and keep canceling, it will come back no worries)

Install s2e and Titanium Backup from market

launch s2e, enable advanced mode, move everything to SD ext partition (requires reboot from app menu, thats why I don't allow apps to install or any other accounts to sync, less chance of failed/hung reboot or data loss).

Restore apps via Titanium (which will now show the ext partition and how much space used).

I also use Titanium to remove Car Dock, wallpapers, etc., to free up 11 to 14mb in the system partition (seems to allow Wifi calling to work smoothly and allows my G3 signal to come back automatically after I switch off Wifi Calling, no more airplane mode flop needed).
[Nexus One Android Development] superg81:
still not working here,tried everything recommended and then a few things ive thought up :( no update from OP?
[Nexus One Android Development] akirajds:
try this,

1. wipe cache and dalvik

2. flash rom

3. flash gapps (if needed)

4. flash kernel (if needed)

5. boot up rom and let everything come up

6. reboot into recovery

7. flash wifi calling

that combo seems to work for me
[Nexus One Android Development] superg81:
tried this several times but thanks for the input.ive even reformatted card,super wipe 3 times,regular wipe 3 times and went thru install process to no avail.redownloaded addon didnt help either.always sim error
[Nexus One Android Development] akirajds:
what are you trying to flash?
[Nexus One Android Development] superg81:
cm7 nightly and wifi calling addon.sometimes it works,sometimes it doesnt.im in the "it doesnt" stage.i know it works for some on here that are running the same setup i am.for others it is not working.no rhyme or reason that i can see
[Nexus One Android Development] dnsmo:
I do rom, kernel then wifi calling v 1.3
[Nexus One Android Development] superg81:
ive done it that way also :(
[Nexus One Android Development] iheartn1:
installed this and now my phone does not work anymore. invalid sim card error and now i cannot make regular calls or anything. running cm7 nightly 83
[Nexus One Android Development] superg81:
wipe cache and dalvik cache and reflash rom without addon.you will be back to normal.you "might" have to reflash gapps
[Nexus One Android Development] kitsunisan:
Just confirming that I'm also getting the invalid sim error. Flashed CM7's latest nightly(87 I think), Google apps, IR's latest GB kernel then the Wifi add-on, no good. I tried it without the new kernel just in case that was the issue, still the same result. Have the .08 radio, full wipe of everything each time. Don't know why this is hit-or-miss for some people.
[Nexus One Android Development] fkananeh:
I used to receive the invalid SIM error when I first tried the Wifi calling app. I thought it was a problem with my rom or phone, but in reality it's an issue with the SIM.

T-Mobile updated their customers' SIMs recently (March '10) to allow the use of new features for HSPA+ and Wifi Calling. My SIM was so old, it had different colors! So I took it to the nearest T-Mobile store and picked up a new one for free. once I inserted the new SIM in the phone and turned on Wifi calling, BAM, No more invalid SIM error and I could use my phone on Wifi with no issues
[Nexus One Android Development] kitsunisan:
Might be a possibility, I'm still using the same sim I got with my replacement G1 back in December '09. I'll hit T-Mo tonight and get a new one.
[Nexus One Android Development] superg81:
i will drop by Tmobile also tonight
[Nexus One Android Development] galaxys:
Going to get my Sim replaced also, since it's older than the hills :eek:
[Nexus One Android Development] mooselander:
I picked up a new sim today and still haven't been able to get this working.

For those that have wifi calling working, can you post your setups?

I've tried nightly #87 and fitsnuggly's latest with a combo of various kernels and DT-A2SD. So far no luck, the wifi calling app never loads and my phone won't connect to T-Mobile's voice or data network (bars are greyed out).

Thanks!
[Nexus One Android Development] dnsmo:
I am using fit's rom and redstar kernel then wifi calling been working for me for a long time
[Nexus One Android Development] gururise:
No, its not a problem with T-Mobile's SIM card. I got a brand new SIM card from t-mobile and I'm still experiencing the problem.

The problem stems from the fact that changes were made to the ril library in the newer CM nightlies. Unforgiven has already updated to the gingerbread ril_library, we just need to be patient and wait for him to upload it. A few weeks back, it looked like he was going to upload a new release of the wifi calling app in a few days, but I suppose he got busy with something else.
[Nexus One Android Development] gururise:
If you want wifi calling working, you will need to:

1. wait for Unforgiven to update to 1.4

-or-

2. Use a CM nightly older than #47 (or there about)
[Nexus One Android Development] denverpedro:
No APN?

I read through the whole thread (at least a ways back to the end of January) and I don't see any mention of this problem. Maybe someone has seen it and can help.

Whenever I flash 1.3 over CM7.0.3 (stable release) the APNs disappear. I've also tried with the latest nightly (#87) with the same result.

If I try the 1.2 build I get a funky screen resolution and invalid SIM error.

Any help would be appreciated. I'm heading to Zurich this weekend and would love to have WiFi calling enabled. I'm willing to completely wipe my phone to get this working I just need a combination of ROM/Kernel/Wifi/Radio that is known to work.

Any suggestions?

Thanks
[Nexus One Android Development] denverpedro:
Also, I am unable to add an APN. I enter all the appropriate information then save it from the menu but when I go back to the APN list it's still not showing any APN. Is there a process I need to follow to update the APN list (turning off mobile service while I'm doing it maybe? I'm going to give that a shot.)
[Nexus One Android Development] denverpedro:
OK, not sure what happened... but I (again) did a full wipe (data, cache, dalvik-cache), installed CM7 nightly #87, 0507Gapps and booted into the OS. Then back to recovery and installed the 1.3 version of the WiFi add-on and rebooted.

I'm back up and everything is working. That is of course after spending some time restoring everything via Titanium, etc.
[Nexus One Android Development] superg81:
if you got it working,dont touch it.i dont think it has anything to do with nightly number.i have it working on one nexus here with a nightly from a week ago and another i cant get it working on.its really hit and miss.glad you got it to work ;) wish i could :mad:
[Nexus One Android Development] th3pr1nc30f3gypt:
what are DT and IR kernels?
[Nexus One Android Development] baseballfanz:
DT = dark tremor a2sd

IR = intersectravin
[Nexus One Android Development] dnsmo:
I am having the sim card error problem with fits 0603 build looks like we need another update soon
[Nexus One Android Development] akirajds:
are there any other options for wifi calling? (not counting SIP)

are there any other devs tinkering with it?

wifi calling works great for me considering i get almost no signal inside my work

but lately its been less that reliable
[Nexus One Android Development] dnsmo:
Check your system space. Clean up some space should work at least that was what I did
[Nexus One Android Development] chadtn:
How much free space does it need? I've got around 80-100 megs free right now and haven't had any luck.

Chad
[Nexus One Android Development] N1_Fan:
That 100mb is internal memory. You need to look at system ROM memory when you are having flashing issues. I generally try to stay above 10mb.
[Nexus One Android Development] chadtn:
Says I have 228 megs of memory free and 95 megs of internal storage available.

Chad
[Nexus One Android Development] Babydollll:
That's not the kind of memory He is talking about. The 228 megs is your RAM. HE IS TALKING ABOUT SYSTEM ROM MEMORY. You can find this info if you look at TITANIUM BACKUP, on the bottom, one of the numbers will be system ROM (as in the partition used for the ROM). The N1 doesn't have much system memory. It can cause issues if you have less than ten mb.

Edit: there are other ways (probably more accurate) to find this info also but, titanium backup is the easiest.

Sent from my NS running NSCollab 1.0.32 cuz I. STILL can't find my tin cans and string ....
[Nexus One Android Development] superg81:
i used root explorer,went in and deleted a bunch of **** i dont use in system/app and i be damned if it didnt work. thanks heaps dude :D
[Nexus One Android Development] chadtn:
I had always considered the internal memory to be the "rom". After downloading Titanium Backup it showed that the system rom was down to only 8 megs. I deleted a couple of things and reflashed wifi calling. It went from 15 free to 13.1 after the flash and wifi calling is working again.

Thanks!!

Chad
[Nexus One Android Development] baseballfanz:
Thanks man, working again. Now to call tmo and get free wifi calling:D
[Nexus One Android Development] ronn888:
now that OP has moved on from the Nexus One, is there any hope that this will be updated to be usable for newer CM7 nightly?
[Nexus One Android Development] superg81:
It works on latest nightlies. Read above posts again:)
[Nexus One Android Development] denverpedro:
OK, so I have this working on nightly #87 but anything after that it fails for me using the same install methods. If I read this last post correctly I'm guessing my solution is to clean up some system space and then it will start working?

If so how are you doing this? Is it simply a matter of moving apps to SD? Or will removing unused components work as well (or a combination)?

Any advice would be greatly appreciated. I love this add-on but I've been back on #87 for a long time just to keep it working.
[Nexus One Android Development] chadtn:
I downloaded the free version of titanium backup. It will tell you in the overview how much of the system rom is free. The backup tab will list the stuff installed to the rom in red. I noticed CM has five megs of wallpapers that I don't use. That's probably a good place to start. You can click, backup just in case, and then uninstall.

I followed the advice in this thread until I had about 10 megs free and flashed wifi calling again. Worked perfectly!

Chad
[Nexus One Android Development] denverpedro:
Yep, just tried it. Installed #103 (latest nightly I can find) and rebooted. Removed a bunch of stuff (live wallpapers which I don't use, CM wallpapers which I also don't use and a few other things). I then rebooted and applied the WiFi calling zip (1.3).

The first time through it didn't work.. (I had free'd up 11.6MB of ROM space). I removed a few more items and it worked the second time.

Thanks for the help, this is fantastic!
[Nexus One Android Development] mooselander:
"System ROM" free space does indeed seems to be the key with this application. I had T-Mobile add the "free wifi calling" service and have been pretty happy so far.

I just wanted point out though... I recently found Groove IP in the market and I think I may actually prefer it to clearing free space used on an ever expanding "system rom" partition.

Groove uses Google Voice and Google Talk to route free calls to and from my N1. For me, the incoming quality is better than any SIP client or this T-Mobile app (haven't tested call quality at the other end yet).

I'm digging that it's not a "callback" application for Google Voice too, it places calls directly so it's as transparent as the T-Mobile wifi app but there are less hoops to jump through.

Anyway, there are some good options out there for free wifi calling if this app ever stops working or becomes unsupported.
[Nexus One Android Development] trevmar:
I installed Groove IP and it did work well. But it clobbered all the sockets which CSIPSimple had created, so I am assuming it is only SIP and not Jabber. I uninstalled it immediately after I noted that it sent back my unique IMEI number, and other data, to "flurry.com"

It didn't warn me about this, and there is no way to shut it off, so I uninstalled Groove IP and wrote off the $3.99 this experience had cost me :mad:
[Nexus One Android Development] CMUKyle:
Is there any chance of this ever being developed to a point where it can be used with any ROM, like the old WiFi calling on Froyo? I would love to be able to migrate from CM.
[Nexus One Android Development] CAL7:
One more vote for cleaning up /system. I was at Build 86 and was not able to flash a new ROM without losing the SIM. I checked /system and found I had 152KB available. Following the advice here, I deleted everything I could to get to 12MB and reflashed per the following.

Clear cache and Dalvik cache (don't know if its necessary, but it has worked for me since I started flashing, so I do it)

Flash #105

Flash my choice of kernel (Redstar 2.6.38.7 OC1152)

Flash DTapps2SD 2.7.5.2

Boot

Re-delete the junk that CM #105 just added

Boot and flash WiFi 1.3

All Good!
[Nexus One Android Development] SiliconBug:
V1.3 works great with nightly #107, no extra kernel updates needed. :D

I also remove CM wallpapers and live wallpapers to get more system space before flashing v1.3.
[Nexus One Android Development] Jnn1:
If you have google voice and use it as your number, using GrooVe for wifi calling at home is a good option. It can both take and make calls with your google voice number and doesn't use up your minutes when your connecting via wifi. It's on sale at amazon app store.
[Nexus One Android Development] Jnn1:
Comment above was meant as a reply to this (not jacking the thread)
[Nexus One Android Development] SiliconBug:
WiFi calling doesn't work on my N1 with CM RC1 now, and keeps saying W006.15 error. :(

G2x works fine with the same SIM card and same WiFi, so I think the problem should be on N1 itself.
[Nexus One Android Development] Manacit:
I'm getting the same issue, I can offer some debug help if it will move things along?
[Nexus One Android Development] baseballfanz:
Try and clear up some system space. Its working for me on cm7.1rc
[Nexus One Android Development] SiliconBug:
After flashing v1.3, I have about 11MB free, but still can't get it work.

I also remove live wallpaper, so there's no extra room I can clean.
[Nexus One Android Development] teh_lorax:
Its automatically shutoff now. Check the Whats New tab.

https://market.android.com/details?id=com.gvoip
[Nexus One Android Development] SiliconBug:
I wipe my N1 and have a fresh installation of RC1, but still get the same error. Looks like that I miss something...
[Nexus One Android Development] trevmar:
Thanks teh_lorax. I have updated, and Flurry is indeed gone. But GrooveIP still uses 80Kbps of bandwidth in each direction, just like SIP does. Is it really using Jabber, or is it just calling a SIP gateway?

OK - Found an answer in the grooveIP FAQ:

"For registration and call signaling, GrooVe IP communicates with talk.google.com over TCP port 5222. For voice traffic, local UDP ports 19003 and 19004 are used"

http://snrblabs.com/groove_ip/faq

I guess that means it uses XMPP and Jabber in the phone. But surely this would have been a simple question for snrb to answer? This is important info for a traveler who has to operate behind the Great Firewall of China
[Nexus One Android Development] SiliconBug:
Under [Wi-Fi Calling Settings] => [Advanced settings] =>[My network], both UNC address and SGW Address are empty, and I guess that's why the registration is always failed.

Is there anyway I can modify it?
[Nexus One Android Development] SiliconBug:
I finally fix my problem.

My AP/router is Linksys WRT54GS with Tomato. With QoS enabled, nexus one keeps saying W006.15 error.

I add a rule to make all traffics on nexus one get "HIGH" priority, same error. Then I change it to "HIGHEST" priority, it works!

It also works if I create a rule to give port 500 and 4500 the "HIGHEST" priority.

However, I still don't understand why my G2x (same SIM, same AP, no special rules in QoS settings) works without any problem.
[Nexus One Android Development] Bling_Diggity:
Wow...so apparently this thing won't work with CM 7.1. Just found that out the hard way. SD-ext not mounting, radio is f#@ked, and the Wi-Fi calling app itself won't even work. Something about an invalid sim...which makes zero sense whatsoever.

Wish I had done a Nandroid before I flashed this thing...oh well, live and learn.
[Nexus One Android Development] SiliconBug:
No, it works great with 7.1. The only thing I need to change is QoS.
[Nexus One Android Development] N1_Fan:
Works just fine here as well. Been using it for all the nightlies and no issue.
[Nexus One Android Development] Bling_Diggity:
Odd. Wonder why it completely f'd mine all up? Maybe has something to do with my app2ext scripts I have installed? But that doesn't make sense because I had the same scripts installed on 7.0.0.

Or maybe it won't work with Busybox 1.19? I just installed that...had 1.16 installed on CM 7.0.0.

I'm kinda grasping at straws here. I know it installed on 7.0.0 without a glitch on the first try...and worked perfect. But every time I try flashing it on 7.1 the whole damn phone just goes haywire.
[Nexus One Android Development] denverpedro:
Check the available System ROM memory (look in Titanium Backup). I had all sorts of issues and the problem was not enough free System ROM memory. Go back a few pages in this thread there was a whole discussion on it. I used Titanium Backup to remove a bunch of useless stuff from the system partition (things like live wallpapers, Books, CarHome which I don't use, CyanogenMod wallpapers, Home Screen Tips, etc.). Doing that freed up about 12MB more System ROM space (from 8 to 20MB free) then the install works for me.

Good luck.
[Nexus One Android Development] denverpedro:
FYI, I saw 12MB quoted as the free space required for this to work but mine failed with 12MB available so I normally shoot for as close to 20 as possible before attempting the install.
[Nexus One Android Development] Bling_Diggity:
Thanks for the input. Checking out my system rom memory right now I only have about 13mb free. So that may very well be the root cause of all my issues after flashing the wi-fi. Will try and clear some space then flash again. This time AFTER making a Nandroid backup, which I neglected to do the first time. :eek:

Edit: After uninstalling some system apps with Titanium, I now have 19.1mb free on system memory. Going to re-flash now. Wish me luck!
[Nexus One Android Development] baseballfanz:
^^^ Good luck, I had the same problems till I clear some system space.
[Nexus One Android Development] Bling_Diggity:
SUCCESS!

Turns out not having enough system memory was indeed the problem. Thanks again for your help denver!
[Nexus One Android Development] CAL7:
Seems to be the universal solution.

Has anyone tried TB's option to move system apps to user? Seems like a good way to get more system space.
[Nexus One Android Development] mtw4991:
umm, most system apps need to stay on system/app to function properly. Better way is to just delete the ones you don't need.

Temasek made a flashable zip for me that deletes Androidian, Cyanbread, Live Wallpaper, Android Term, ProTips and Magic Smoke Wallpapers. Leaves me with about 20mb free. Flash right after Rom/nightly. You can edit with notepad also.

Here is the zip, all credit to Temasek for his help!
[Nexus One Android Development] CAL7:
Big help! I used it to flash 129 and everything fits.
[Nexus One Android Development] chadtn:
Any news on that update? It sounds interesting.

Chad
[Nexus One Android Development] NCguy:
Do you think this will work after the latest stable? Is timing important or just sequence? Does it have to be immediately following the stable flash or can some time pass after installing the flash?
[Nexus One Android Development] baseballfanz:
You can flash it anytime but the purpose of it is to delete system app before reboot.

Flash your ROM, flash the SystemAppRemover than anything else like DT or Wifi than reboot
[Nexus One Android Development] NCguy:
I take it that you feel its probably compatible with the latest stable?