Related
Ok I have never rooted my phone, and never deviated from the stock android ROM. About a week ago my wifi randomly stopped working.
When I go to turn it on it simply says error, and rebooting it does not help.
I tried a factory reset and it did help, temporarily, but after powering the phone off and back on the next day it stopped working again!
This makes me think it is in fact a hardware problem. I also just recently upgraded to 2.3.4, but I'm almost certain this was happening before then. Does anyone have any idea why this is happening?
Anyone know if Verizon will help me if I take it in? I do not have insurance (big mistake!)
Any help is greatly appreciated, I have read TONS of threads and cant find any info on this, besides from people who had modified roms.
Thanks in advanced!
On a vanilla (virgin) dInc, I'd say you are in fact facing a hardware issue. Have you tested with another WIFI connection manager app?
Search for "Wifi Manager" in the market, it's worked well for me in the past.
Awesome! Thanks so much man, Wifi manager did the trick! Very strange that it wouldn't work with the default wifi app, but I'm happy either way.
You made my day!
Looks like I spoke too soon...
It worked for about three minutes then it shut off. This seems so strange!
Any other ideas?
Are you running any sort of power management apps? Many of those will auto shut off your WiFi to save power.
Sent from my ADR6300 using XDA App
No I'm not, but funny you mention that because when I was (before my factory reset) I think thats when these issues first started.
I'm definitely not running any right now though.
Probably just a coincidence, but yea. Any ideas from anyone? I just bought the Seidio 3500mah battery! Would be a shame if the wifi is broken
Try rolling back to 2.2 via htc sync and the 2.2 ruu package. See if you still get the problem on 2.2, if not, stick with 2.2 or invoke the 2.3.4 update again (dialer *#*#checkin#*#*) and test again after the update. This should without further question determine whether there is a hardware problem or not.
Also, although unlikely, maybe your new battery is causing interference.
Try your best to test all of the basic variables before giving up.
Sent from my ADR6300 using XDA App
mindlessacts said:
Looks like I spoke too soon...
It worked for about three minutes then it shut off. This seems so strange!
Any other ideas?
Click to expand...
Click to collapse
Settings>Wireless &Networks> Wifi Settings>Menu>Andvanced>Sleep Policy
What is it set to?
Sent from my CM7 Droid Incredible using XDA Premium App
Unholyfire said:
Try rolling back to 2.2 via htc sync and the 2.2 ruu package.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
You can't downgrade from 2.3.4 to 2.2. If what you say is true, then some rooted users who unrooted for the update with s-on need to know about this.
Not to be off topic, but do you someone who successfully did this?
how long have you had it if it is less than a year then htc will take care of you if it is over a year verizon might be talked into giving you an upgrade early. only way to know for sure is to go into verizon and see...
mindlessacts said:
Looks like I spoke too soon...
It worked for about three minutes then it shut off. This seems so strange!
Any other ideas?
Click to expand...
Click to collapse
Is it showing an error right after you turn it on, or when attempting to connect to a WAP?
Have you tried long pressing to forget the wifi access point then readding/reconnecting it?
SlimSnoopOS said:
Have you tried long pressing to forget the wifi access point then readding/reconnecting it?
Click to expand...
Click to collapse
That's what I was getting at. Trying to tell if it's failing at the connect or at simply turning on the WiFi chip itself.
Sent from my HTC Incredible using XDA App
Thank you very much everyone for your suggestions. I tried everything but downgrading to 2.2 since I didn't know how. However I'm happy to report that my WiFi is now working again and I did nothing.
Well besides buying a new battery! I replaced my oem battery that I bought off amazon with a siedo 3500mah so not only am I getting insane battery life, but it made ky WiFi work!
I should have mentioned that my charge was averaging just three to four hours on my old battery. Maybe it was defective and not powerful enough to run WiFi?
I really don't know, but do hope that if someone is on my same position they find this thread helpful. Thanks again to everyone, these are very kind forums!
Sent from my ADR6300 using XDA App
mindlessacts said:
Thank you very much everyone for your suggestions. I tried everything but downgrading to 2.2 since I didn't know how. However I'm happy to report that my WiFi is now working again and I did nothing.
Well besides buying a new battery! I replaced my oem battery that I bought off amazon with a siedo 3500mah so not only am I getting insane battery life, but it made ky WiFi work!
I should have mentioned that my charge was averaging just three to four hours on my old battery. Maybe it was defective and not powerful enough to run WiFi?
I really don't know, but do hope that if someone is on my same position they find this thread helpful. Thanks again to everyone, these are very kind forums!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Glad you got it worked out!!
Just want to know if there is any news about the latest GSM update because I have not received it and yes I'm on Google build.
With all the reports of signal problems and others have they pulled the update?
Sent from my Galaxy Nexus using xda premium
Nope.
http://code.google.com/android/nexus/images.html
as OTA it seems that yes, it has been pulled
I don't think its being "pushed" per say, but the OTA link usually stays up.
Search around for it.
Sent from my Galaxy Nexus using XDA
spamlucal said:
as OTA it seems that yes, it has been pulled
Click to expand...
Click to collapse
That's just speculation. It's more likely that they are collecting feedback from the first wave of updates as JBQ said. After all, the entire reason for not rolling it out to everyone at the same time is so that they can see that the updated devices come back up and seem to work normally.
Think of it this way. If you push out the update to 100 phones and 70 of them never come back up (ie. they don't login to Google within a certain amount of time), then you have a potential problem with the update.
Maybe not pulled since you can still get the factory image but OTA rollout has been stopped according to a vodafone rep: http://forum.vodafone.co.uk/t5/Google-Nexus/ICS-4-04-Update/m-p/1073311#M13631
There is no OTA 4.0.4 update for more than one week for yakju build devices.
I wouldn't complain if it has. A lot of GSM users complaining of radio troubles during sleep.
Does not affect CDMA users though
Seems like the tables turned on radio issues in 4.0.4. CDMA is better, GSM...not so much.
I don't know if it's been pulled as I've already updated to 4.0.4 but I can say that mine is problem free (thank god).
I find it strange that it doesn't affect everyone.... Anyone have any idea why?
adrynalyne said:
Does not affect CDMA users though
Click to expand...
Click to collapse
That's because most CDMA folks are still on 4.0.2
Sent from my Galaxy Nexus using XDA
ronak47 said:
I don't know if it's been pulled as I've already updated to 4.0.4 but I can say that mine is problem free (thank god).
I find it strange that it doesn't affect everyone.... Anyone have any idea why?
Click to expand...
Click to collapse
There are multitudes of factors to account for when diagnosing or replicating problems across all devices that are not equal per se. I didn't think I had the problem until my text stopped sending after clicking enter. The signal dropped out as well as other radios were gone for a brief moment.
I think it's only a matter of time before it happens to most people.
Sent from my Galaxy Nexus
I can definitely say my cell network data connection has refused to function on multiple occasions on 4.0.4. Possibly the sleep issue. Once restarting the phone fixed it, once not even doing a battery pull could fix it. It started working again at some random time later. I was trying to nail down if walking far enough that being a different tower fixed it or not.
Definitely given the amount of people complaining and the fact I've seen some wonky data connection issues it seems there is a bug.
I bought mine from Negri back in November, it came with yakju. On TMo in NYC.
Sent from my Galaxy Nexus using Tapatalk 2
I'm guessing a rushed 4.0.5 is soon to be released to fix the sleep and signal issues.
ericshmerick said:
I'm guessing a rushed 4.0.5 is soon to be released to fix the sleep and signal issues.
Click to expand...
Click to collapse
When you say rushed, that means at least a month from now, right? It is Google after all.
But I'm not going to complain about 4.0.4; it works fine for me. What I still hate is the poor communication from Google.
rubiconjp said:
That's because most CDMA folks are still on 4.0.2
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
According to AOSP we are on 4.0.4....not everyone is a victim
I haven't been on 4.0.2 since December of last year.
Evangelion01 said:
When you say rushed, that means at least a month from now, right? It is Google after all.
But I'm not going to complain about 4.0.4; it works fine for me. What I still hate is the poor communication from Google.
Click to expand...
Click to collapse
Yeah, I know the .001% of the population on XDA wants weekly massive improvement updates streaming to their Nexi, but it is simply unrealistic. This stuff takes time.
Silence is aggravating, but our phones get updates a LIGHT SPEED vs. any other Android phone. I'll take that any day of the week despite not getting an hourly update from the Android developers working on the inside. They're busy, believe me.
No need to reply to this—just looking for a good poll for 5GHz operation on this phone. If you are using 5GHz successfully or have tried, but are unsuccessful, please vote.
UPDATE:
For what it’s worth, I decided to do some brief experimentation with a business-class stand-alone wireless access point and, while I didn’t spend too much time on this, it appears the Galaxy Nexus’s ability to do Dynamic Frequency Selection (DFS) is broken, non-existent or the device is simply coded (miscoded?) not to connect to UNII-2 5GHz channels (channels 52-140), which require the use of DFS. I was able to connect to this access point’s 5GHz radio using UNII-1, UNII-3 and the 5.8 ISM channels—so, for the most part, this covers channels 36-48 and 149-165. Hope this helps someone.
For more technical information on wireless channels, see http://en.wikipedia.org/wiki/List_of_WLAN_channels...
Cheers.
SECOND UPDATE:
So, while this worked great for months for me, I seem to be having the issue others have reported in that, all of a sudden, 5GHz has stopped working and I have been unable to get it to work again—and, to make matters worse, this issue has persisted even with Jelly Bean/4.1.1.
Shame.
THIRD UPDATE:
Problem still exists with 4.2.2 and I think the most relevant “official” report of the issue is at http://code.google.com/p/android/issues/detail?id=22474.
Works fine here.
Linksys E2500, Channel 48.
Derp, ignore
Sent from my Galaxy Nexus using XDA
Nhialor said:
5ghz OC? Is that not terrible for the phone ?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
It would be extremely terrible, luckily we are talking about WiFi GHz not CPU GHz.
works fine for me
netgear n900
Works for me! Netgear wnd3300.
It used to on 4.0.1. On 4.0.2 the 5ghz channel fades in and out and it will no longer connect to it. When it did work it was much faster and smoother than 2.4
Works perfect for me net gear n600
Sent from my Galaxy Nexus using Tapatalk 2
What is net gear..???
Sent from my Galaxy Nexus using xda premium
Mine doesn't work.
Asus RT-56U
Channel 104
walidhiphop said:
What is net gear..???
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I cant even come up with a smart ass response to that...
Sent from my Galaxy Nexus using Tapatalk
walidhiphop said:
What is net gear..???
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Its this specific gear that people use to make nets see (netgear.com)
Sent from my Galaxy Nexus using xda premium
5GHz working fine on Vzw Nexus, Cisco E3000 running DD-WRT.
Sent from my Galaxy Nexus using xda premium
For a second, and then my phone incinerated.
Sent from my Galaxy Nexus using Tapatalk 2
It use to until I upgraded to 4.04
Sent from my Galaxy Nexus using xda premium
Once upon a time...
... it worked. But now it doesn't. The network shows up in the list but clicking on "Connect" literally does nothing.
However, I updated to 4.0.4 last Sunday, and maybe it works now. Will try it asap.
Same issue, it works at the begging bit not now.. It's shows my 5GHz network but i cannot connect.. I can connect only if i'm over the router just 10-20 cm. Also i've try to connect to other 5GHz network but i have the same issue.. Not depending on channel , I've try every channel 36,38, 40 and etc... I want to know is this hordware or software problem...?
lostindark said:
Same issue, it works at the begging bit not now.. It's shows my 5GHz network but i cannot connect.. I can connect only if i'm over the router just 10-20 cm. Also i've try to connect to other 5GHz network but i have the same issue.. Not depending on channel , I've try every channel 36,38, 40 and etc... I want to know is this hordware or software problem...?
Click to expand...
Click to collapse
Its software. There is a clear pattern here. It used to work but now it doesn't. All of these people didn't suddenly have their hardware crap out.
It worked for less than a week and then suddenly stopped working. Now I can see 5ghz networks but if I click on Connect, nothing happens.
I am using a Netgear WNDR3800. I tried to change channel, bandwidth, remove the password.. nothing.
Here you can see the problem "In action"
http://www.youtube.com/watch?v=V33LAfpgyCM
NCguy said:
Its software. There is a clear pattern here. It used to work but now it doesn't. All of these people didn't suddenly have their hardware crap out.
Click to expand...
Click to collapse
If it works fine for 70% of the people but not for the other 30%, it might be some faulty hardware. Sometimes it happens.. Nikon is currently recalling a bunch of batteries which are defective and Apple did the same with iPod Nano and other products.
It may be a defective batch of GNexus.
I really hope that Samsung is going to address the problem soon.
gardirulez said:
It worked for less than a week and then suddenly stopped working. Now I can see 5ghz networks but if I click on Connect, nothing happens.
I am using a Netgear WNDR3800. I tried to change channel, bandwidth, remove the password.. nothing.
Here you can see the problem "In action"
http://www.youtube.com/watch?v=V33LAfpgyCM
If it works fine for 70% of the people but not for the other 30%, it might be some faulty hardware.
Click to expand...
Click to collapse
Specifically regarding the 5ghz issue working and then not working on the same device, we are talking about 100% of the people that have reported that problem. That was what you replied to, not to people with general wifi problems.
Hey everyone, I have a question about T-Mobile Wifi Calling feature. When it works, it is really great but sometimes when I answer the phone either I can't hear them or the caller can't hear me but I can hear them. My Wifi signal is really good but why does this happen? It seems like a pretty common problem and when I searched for solution, there were many but none that really works 100%.
Is there any remedy for this issue?
Yea I have the same exact problem. It's really annoying.
I'm seeing the same issues myself. Hopefully the update with multi-window will address this. I remember my Wifi calling being much more reliable on my Galaxy S from 2 years ago.
paul2834 said:
I'm seeing the same issues myself. Hopefully the update with multi-window will address this. I remember my Wifi calling being much more reliable on my Galaxy S from 2 years ago.
Click to expand...
Click to collapse
Agreed. and wifi calling on my wife's Sensation works flawlessly all the time. Sad thing is I absolutely need it at home. no cell coverage at all.
my s3 and my n2 used to do that but I have the dual router and when I switched from G to N signal the issue was solved.
elbarto7 said:
my s3 and my n2 used to do that but I have the dual router and when I switched from G to N signal the issue was solved.
Click to expand...
Click to collapse
I've got a Netgear N router that is only a few months old. Still have issues
=( that's pretty disappointing, I guess we all have to wait till T-Mobile fixes it. I was really depending on this feature since I get no service indoor. I can't help but to feel regret switching from ATT...
hd2Raz said:
I've got a Netgear N router that is only a few months old. Still have issues
Click to expand...
Click to collapse
I have Cisco E3000 and I used the 5Ghz band.
Am I suppose to set the router certain way to get this working 100%? I went to T Mobile store today and I only made fool out myself. When it was connected to store Wifi, I just couldn't recreate the issue but as soon as I get home it goes all wrong!
Sent from my SGH-T889 using Tapatalk 2
zen0s said:
Am I suppose to set the router certain way to get this working 100%? I went to T Mobile store today and I only made fool out myself. When it was connected to store Wifi, I just couldn't recreate the issue but as soon as I get home it goes all wrong!
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Have you logged into your tmo account online and set your 911 address? This seems to have made a huge improvement for my wife's phone but also somewhat on mine from the looks of it. Still not 100% but at least it works most of the time.
hd2Raz said:
Have you logged into your tmo account online and set your 911 address? This seems to have made a huge improvement for my wife's phone but also somewhat on mine from the looks of it. Still not 100% but at least it works most of the time.
Click to expand...
Click to collapse
yeah, i had to put my address there first to get the Wifi-Calling feature going. Doesn't seem to be much of different on my part though
So many problems with Wifi-Calling feature...
- One way Audio (either caller can't hear me or I can't hear them)
- Text/MMS not coming in or out
- Phone Calls doesn't go through, phone doesn't even ring... when it does ring and I pick up, phone freezes at the answering screen!
WTF! so unreliable... what a mistake switching to T-Mobile was. AT&T was over charging the heck out of me but at least I had no service problems, I'm not sure if cheaper plan is worth going through this.
zen0s said:
yeah, i had to put my address there first to get the Wifi-Calling feature going. Doesn't seem to be much of different on my part though
So many problems with Wifi-Calling feature...
- One way Audio (either caller can't hear me or I can't hear them)
- Text/MMS not coming in or out
- Phone Calls doesn't go through, phone doesn't even ring... when it does ring and I pick up, phone freezes at the answering screen!
WTF! so unreliable... what a mistake switching to T-Mobile was. AT&T was over charging the heck out of me but at least I had no service problems, I'm not sure if cheaper plan is worth going through this.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1769716
for some reason my wife's s3 has the same IP as my HP wireless printer.
Was having the same problems on my N2. I've since switched to the N band, but I haven't re-enabled WiFi calling as I am a bit gunshy, especially since I am taking a lot of job calls at the moment.
elbarto7 said:
Try this http://forum.xda-developers.com/showthread.php?t=1769716
for some reason my wife's s3 has the same IP as my HP wireless printer.
Click to expand...
Click to collapse
Thanks but after checking, it's definitely not conflicting with any IP. Only thing that's connected to my comcast modem is my pc and my Note 2. =(
I see hundreds of posts and threads regarding to this wifi calling issue on t-mobile support website... I can't believe they haven't fixed it.
Sent from my SGH-T889 using Tapatalk 2
i have the same problem..
WIFI calling is truely a hit or miss... sometimes it works great and other times nobody can call me .. they go right to voicemail.
I really hope they figure this out ... wifi calling is soo important to have.
Only real solution is to turn off the Wi-Fi calling feature for now. It's pretty much a hit or miss if it will work on a daily basis.
Sent from my SGH-T999 using Tapatalk 2
DataDork said:
i have the same problem..
WIFI calling is truely a hit or miss... sometimes it works great and other times nobody can call me .. they go right to voicemail.
I really hope they figure this out ... wifi calling is soo important to have.
Click to expand...
Click to collapse
Yeah, seriously.... The saddest part is every tmobile tech support I get in touch with, they seem to have no clue what so ever with this issue. How do we let tmobile know about this? There are plenty of threads at tmobile support forum but I don't see tmobile doing anything about it! It pisses me off!
Sent from my SGH-T889 using Tapatalk 2
zen0s said:
Yeah, seriously.... The saddest part is every tmobile tech support I get in touch with, they seem to have no clue what so ever with this issue. How do we let tmobile know about this? There are plenty of threads at tmobile support forum but I don't see tmobile doing anything about it! It pisses me off!
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
The problem is that this may be a Samsung phone problem, so nothing a tmobile tech can help you with currently. As others have mentioned, using older phones or other brand of smartphones seems to work with Wi-Fi calling. Most problems were reported from using a Samsung Galaxy s3/Galaxy note 2.
Sent from my SGH-T999 using Tapatalk 2
Im having the sane issue
whatsitsnamenow said:
The problem is that this may be a Samsung phone problem, so nothing a tmobile tech can help you with currently. As others have mentioned, using older phones or other brand of smartphones seems to work with Wi-Fi calling. Most problems were reported from using a Samsung Galaxy s3/Galaxy note 2.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It's a t mobile issue, I've had the same issue using wifi calling with HTC devices.
Sent from my SGH-T889 using xda premium
So I have tested two different Xbox 360 slims. Both do not want to hook up. Old Xbox 360 with wireless g adapter works fine.
Bui... This has not always been the case with Xbox 360 slim. I used to not have problem. I think this may be due to new WiFi drivers.
Thing is... I can't seem to get the old WiFi drivers back on my phone. I used to have option to host WiFi tethering via wep securrty, which I take as an indicator of old wifi.
I have flashed older kernels to no avail. Running latest rasbean. Any suggestions or help?
Try taking off the Wi-Fi security.
Sent from my Galaxy Nexus
Garridon said:
Try taking off the Wi-Fi security.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes. Tried that.
Changing mixed to G or N?
a maguro wrote this.
Now I'm in your boat. Internet's down and I'm trying to tether to my Xbox slim. I googled, found out that this problem only started happening after the 4.2 update.
Sent from my Galaxy Nexus
Garridon said:
Now I'm in your boat. Internet's down and I'm trying to tether to my Xbox slim. I googled, found out that this problem only started happening after the 4.2 update.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I still think its wlan drivers. Gonna try flashing some old ass kernels to test. Maybe today... I recall it working before wlan drivers were messed with.
I decided to USB tether to my laptop and bridge the connection with an Ethernet cable. Works that way.
Sent from my Galaxy Nexus