I installed CM6 onto my sister's Hero as well as my mom's Hero. My Mom's Hero works fine but my sister's will not connect to the 3g network! I have gone through and turned on/off all of the network settings and can't get it to re-enable the data services. Wifi works, calls/text work, just not the internet connection over the mobile network. I tried flashing Fresh to see if that would work and I get "Data Call Failure - Error Code 67 .Registration failure. Your PCS Vision username and/or password may be incorrect. Please try again." repeatedly. The 'Mobile Network' in the settings menu in Fresh stays stuck on "Turning on...". I don't get that error in CM6, however. I've tried reflashing/wiping as well with no luck. Is the 3g radio separate from the radio that does calls/texts? Is there a way to check it? I don't want to tell her that I broke her internet connection :/
What radio are u using on that phone? And what all have u wiped?
Root-Hack-Mod-Always™
I was using the most recent radio I believe, 2.42.01.04.27, and I tried wiped everything in recovery. I continued searching for an answer and was able to find a thread that solved my problem! http://androidforums.com/sprint-her.../13197-data-call-failure-error-code-67-a.html
I just had to go into system updates in about phone and perform a 'profile update'
When I first setup her phone she couldn't remember her gmail password so we reset it and she was able to log in. I completely forgot but her 3g worked for that day! the NEXT day we noticed it wasn't working and it stayed like that for a few days until I was able to fix it now. She set up her gmail account at the sprint store when she first got her phone, could her gmail password somehow be related to her PCS username/password so that changing it screwed up her ability to login into the sprint PCS service? I'm still confused as to why this happened on her's but not on my Mom's phone, and never on my phone!
I had this happen saturday night,, running dd 2.8.. data would not start for nothing.. I nandroided back.. and all is good!!
I run CM7 nightlies on my Tmobile N1. Recently I killed my cable Internet/TV connection at home and have been using the built in WiFi tether for my home devices.
While it typically works great (for free), the data on my N1 will lock up. I have full 3G/HSDPA at my house. Using #*#*4636*#*# it states I am connected but fails to ping or load up any data on the phone or through its shared connection.
The only way to fix the problem is to toggle airplane mode and re-enable the WiFi Tether or sometimes a reset is required.
I've changed to several Gingerbread roms, flashed various radios, and even exchanged SIM cards.
Is this behavior normal or not? For regular web surfing I can live with it, but the main problem is that I cannot download anything without it getting interrupted (like updated nightlies or 50mb+ files).
Bumpity
No one has any problems with their WiFi sharing?
i used my phones internet as my regular home internet for a month. i used up about 25 gigs. i streamed videos, downloaded videos and podcasts with no interruptions. don't know what your problem could be. i was using cyan 6.1.1
I occasionally have experienced that issue, but it seems as if you have it much more frequently than I ever did. I would mainly get it when I tethered from areas with bad reception.
You state that you have full 3G/HSPA at your house. I am wondering how many bars of reception you happen to have. Also, try setting your phone to WCDMA Only in that 4636 menu. That seemed to decrease the frequency at which it happened for me.
I also found that once in a while, I could get tethered data working again by simply using the phone's native web browser to access any data. Good luck with the issue.
player911 said:
While it typically works great (for free), the data on my N1 will lock up. I have full 3G/HSDPA at my house. Using #*#*4636*#*# it states I am connected but fails to ping or load up any data on the phone or through its shared connection.
The only way to fix the problem is to toggle airplane mode and re-enable the WiFi Tether or sometimes a reset is required.
Click to expand...
Click to collapse
I typically have full bars of signal usually reading around -100dbm. When the internet drops, it drops completely; maps, browser, apps, etc all fail and I can't "jump start" it other then toggling airplane mode or resetting the phone. Typically a reset is best.
Perhaps I'll flash back to CM 6.1 and test it over the weekend. I'll do a backup of my current setup if things aren't fixed.
The purpose of this thread was simply to see if others have experienced the same issues and if it was worth "trying" to fix.
It might be a case of overheating device - it'll be good to test different ROMs and kernels.
I don't think the device is over heating at all rather then just a carrier issue. I flashed to CM 6.1.1 over the weekend and immediately found I was still having data issues (where it would work for like 5 minutes then drop out).
I did find that EDGE was a solid connection and stayed connected while I downloaded CM7 and GAPPS. I put a call into Tmobile and yacked at them for several hours. They escalated it up several times in their engineering department and so we'll see. I spoke to HTC a few times in there and they didn't think it was a handset problem either.
I guess we can close this thread as it doesn't seem to be a wide spread problem. I am running a stable version of CM7 now and we'll see.
@above: I have tested different radios, roms, and kernels. This thread started out as a issue with WiFi Tethering but ended up being the phone simply dropping its data connection. I originally was curious if this wifi sharing behavior was normal or not.
player911 said:
I put a call into Tmobile and yacked at them for several hours. They escalated it up several times in their engineering department and so we'll see.
Click to expand...
Click to collapse
+1 for this part..
Sent from my Nexus One
Hey folks. I fixed my phone last night, and know how to get through the scary stuff. Now I'm having a small issue with my wireless data connection.
I'm able to use voice and messaging, and my wifi allows me to use the web. Unfortunately, I can't do anything web-based on the Rogers network.
I'm hoping there's a way to sort this out in the settings, but if not, I'm reflashing soon anyhow. Thanks for any help.
find out what your APN should be for rogers.
After switching to Firefly 3 everything kicked in perfectly. Thanks.
Used Odin to update to gingerbread from froyo on my i9000m the other day. Theres no service here at home unless I put the phone on the bathroom windowsill, so I didn't notice until today when I went to work that I wasn't getting any data network connection. Could make and receive calls fine, wifi works, but no data, so no browsing or facebook or any apps that require it. I called bell and they came to the conclusion that I have to send the phone in for repairs. Thats a absolute last resort, so I tried another factory reset, this time from the recovery menu. The first time, during set up I enabled wifi, this time on a hunch I did not, and it worked. Also note that the first time, the network connected for a split second before disconnecting again. Anyways, I was getting 3g fine, then I tried wifi, and it disconnected again. Turn off wifi, data comes back. Whats up with this?
Did you set your APN? Go
Settings > Wireless and Network > Mobile Network > APN Names
Then hit menu and add a new APN if none are there. If one is there, it's named something like 'browser' (at least that's what mine is called on my Bell i9000m) and I'm wrong. But I had this problem, and this is how I solved it. You can find the APN settings for your network by google-ing "[Provider] APN Settings]", and if you're on bell you can find them here:
http://support.bell.ca/en-on/Mobili..._Nexus_One_for_the_Bell_Mobility_HSPA_network
It says Nexus One but it works for all phones on bell.
settings are exactly as depicted on the bell site, except the apn was called browser instead of bell. changed that, same thing. other suggestions?
Can you tell me the version of gingerbread you're on, where you got the files, any mods to the firmware like pre rooting?
Sent from my GT-I9000M using XDA App
2.3.3, downloaded from here, no mods.
Alright, so totally stock. What's the version code? It should be UGKG3. Have you tried forcing a kies update with a registry hack? Was it one PDA when you flashed it or 3 files?
Sent from my GT-I9000M using XDA App
Yes, its UGKG3. I flashed with the PDA, PHONE and CSC files. I dont really know what you are talking about with regards to forcing a kies update, if you could explain I'd try it out
This has always happened to me, on Eclair, on Froyo, and now on Gingerbread. Whenever my Wifi is active *and* connected to a network, the Data through HSPA is automatically disconnected.
I always thought it was a battery saving feature - if you have Wifi access, and presumably internet access, then you don't need internet through the cell network, right?
So if you're not getting internet access when your wifi is active and connected, then perhaps it's a problem with your wifi router not passing external internet to your phone?
The thing is nothing changed besides the firmware. wifi worked fine here in the house before and no problems connecting to the data network on the go with wifi enabled. I'm really running out of ideas here.
I guess I misunderstood you before. Are you saying you have no data access at all when wifi is enabled, whether or not you are connected to a wifi network? If that is true, something is definitely wrong. That doesn't happen to me with KG3 - just checked.
Have you tried reflashing the modem file? Maybe it got messed up in your flash before?
Sent from my GT-I9000M using XDA App
yes, no data regardless of wifi connected or not, as long as its enabled.
which is the modem file?
just an update, this seems to have mysteriously fixed itself.
This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?
Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.
I also flashed a fresh image of the latest software and could not get it to work. This was at my home network. My wife's WiFi calling works perfect on her S6 so I know its not my router.
Even if WiFi is set preferred, mine seems to only switch if it drops off of LTE or the LTE signal is weak. At home, 70% of the time I've been on WiFi calling, with the rest of the time on good ol' cellular.
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
edit: the above sentence is incorrect. I don't know why it didn't work for me at first, but it's working now. Calls can be placed on WiFi solely.
Same here with this build.... I'm where I would prefer having it.
ignitionnight said:
This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?
Click to expand...
Click to collapse
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
TheAmazingDave said:
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
Click to expand...
Click to collapse
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I have encryption enabled and having the same issue.
andy o said:
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
Click to expand...
Click to collapse
Sir, you are correct. I based that statement on my experience of not being able to place a call on WiFi alone originally after the update. I just tried it again though, and it worked. Strange it didn't work before, but no matter. I'll append my post above.
Do any of you have a prepaid plan? I got the 5GB 100 minute $30 plan, maybe that's it?
Edit: although wifi calling with prepaid plans works fine on other phones.
esjames said:
Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.
Click to expand...
Click to collapse
Yup home wifi.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.
ignitionnight said:
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.
Click to expand...
Click to collapse
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.
andy o said:
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.
Click to expand...
Click to collapse
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing
ignitionnight said:
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing
Click to expand...
Click to collapse
The kernel and the ramdisk are in the boot.img. Wifi calling ability is in all likelihood in the kernel. According to the file name it's the correct build version though, but the sizes vary significantly at 8,338KB for the modified img and 7,442 for the original boot.img, but this could be because of repacking. Someone who knows better might chime in. I followed this to check the version, and it matches (Linux version 3.10.40-g8887dbc). It's weird that they would disable wifi calling for unencrypted devices though.
I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?
bob110011 said:
I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?
Click to expand...
Click to collapse
Rooted, but otherwise stock. Mine shows WiFi Calling on the lockscreen next to T-Mobile, in the quick settings shade as you've mentioned, and on the dialer when in a call.
Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.
bob110011 said:
Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.
Click to expand...
Click to collapse
Yes, and also during the call there's an indicator on the screen. Where did you get your boot.img?
I noticed that when I'm on stock kernel (or boot.img maybe) WiFi calling works but on a custom kernel even those made for 5.1.1 it never switches to WiFi mode.
@ignitionnight I installed the no encrypt boot.img here http://forum.xda-developers.com/nex...ed-encryption-gain-root-t2946715/post61015828 and wifi calling is working. You'll also notice the size is very close to the original. I think something was wrong with the NRT file. FWIW, I tried the NRT yesterday and it detected the wrong TWRP and wanted to install its own boot.img when I already had those two installed.
Hey guys, so I might have a solution to the issue with WiFi calling not showing in the notification bar or during a phone call. I recently side loaded the new update and then rooted. After rooting I tried out WiFi calling and it worked flawlessly, notifications and all. Immediately after I modified the build.prop file to allow a miracast connection to my Xbox One. After realizing my WiFi calling wasn't showing up anymore I thought the miracast line may have messed with WiFi calling, so I deleted it from my prop file. I rebooted and you guessed it!! WiFi calling shows up in the pull down menu and during a phone call. So give it a shot and see if it works like it did for me. Best of luck
Mike