Currently Being ModeratedSep 29, 2012 6:36 AM (in response to fromsouth)
i'ved used macbook pro running on osx mountain lion and linksys router
Currently Being ModeratedSep 29, 2012 10:49 AM (in response to nujdux)
Thank you! I do not believe there is multiple hardware failure, though usual diagnostic that people use, points that way. That is if restore as new, does not help. So if that is a bug, there should be some kind of system, that I am looking for now.
Currently Being ModeratedSep 29, 2012 11:07 AM (in response to fromsouth)
I don't believe that it's a question of computer and/or router but as a scientist I think it couldn't be wrong to collect any possible data to find a pattern.
iPhone 4s, 64 GB
iMac 27'', 2.93 GHz Inter Core i7, mid 2010, running 10.7.4, latest iTunes 10.7
Airport Extreme, Version 7.6
I didn't check it but I think a read mostly about greyed out wifi problems with an iPhone 4s.
Yesterday I went to my local reseller. The next apple store is about 100 miles away. But as a reseller they are not allowed to sell or replace iPhones. They were sorry to tell me that I either have to hope and wait for an update or send it to apple.
Currently Being ModeratedSep 29, 2012 12:20 PM (in response to Siebbi)
iPhone 4S 32GB
iMac 27" 3.1GHz i5
update via USB
Currently Being ModeratedSep 29, 2012 7:50 PM (in response to Trapdoresoth)
My wifi is also greyed out, which happened right after updating to ios6. I too have tried all the 'fixes' and went to Apple store who told me since my screen is cracked, I could exchange for a new 4s but would have to pay $199. Not sure what a cracked screen (from a 2 foot drop 3 months ago) has to do with a recent IOS upgrade frying my wifi. Frustrating.
Currently Being ModeratedSep 29, 2012 9:19 PM (in response to nujdux)
Hey nudjux, thanks for the reply, I'm not really sure If my phone is still in warranty though. It would suck bigtime if this matter is really because of a hardware issue. Hi Apple, I just updated my phone to the new iOS and it broke my phone, why not shoulder the expenses?
Currently Being ModeratedSep 30, 2012 4:54 AM (in response to Trapdoresoth)
We have 2 iPads, one has Wifi greyed out and we can't activate it, the other iPad is around one year older and works fine at present, also the iPhone 4 still works on wifi.
Tried settings, general, reset, reset network settings and no luck there.
Does anyone have a solution as yet?
Currently Being ModeratedSep 30, 2012 6:32 AM (in response to Swainy1)
For everyone here, if all that small stuff, like turning apps off in multitasking bar and shutting down for five min. does not help, as well as reset network settings. I would try to do full factory restore. And by the looks of those
three responses about hardware configuration, may make sense to try restore on Windows computer. Or at least another, different one from original.
Currently Being ModeratedSep 30, 2012 11:28 PM (in response to fromsouth)
I tried three different machines: iMac (10.8.2), MacBook (10.7.5), & PC notebook (Windows XP). Wifi option still greyed out.
Currently Being ModeratedOct 1, 2012 10:01 AM (in response to Trapdoresoth)
I confirmed that the crazy freezer trick worked... for now!
Initially I put the iPad into a freezer for five minutes and took it out. After switching on, it could then connect to Wifi network. However, it disconnected after about 10 mins of use. Frustrated, I put the iPad in the freezer for ten minutes before trying again. This time, it has connected to the network for more than 8 hours and I hope it will keep working.
Currently Being ModeratedOct 1, 2012 10:30 AM (in response to Joe9019)
I wonder if that confirms some kind of hardware problem. I have seen that on computers, wi fi adapter stops working and then starts after a while.
Currently Being ModeratedOct 1, 2012 12:10 PM (in response to fromsouth)
I reckon that the iPad did not want to be "left out in the cold" ha ha
Currently Being ModeratedOct 1, 2012 12:21 PM (in response to fromsouth)
Now I also tested this freezer trick with my iPhone 4s (10 min at -18°C / 0 F) but as expected it didn't work.
As we now by now the freezer trick seems to work even for a few people. This implies a hardware problem since the software couldn't erperience temperature.
On the other hand some folks say that after they downgraded to 5.1.1 wifi was back again which means that the software causes the trouble.
a) either a frail combination of software and some certain devices or
b) there are two completly different problems with the same symptom that can be solved either with this magic freezer trick or the downgrade
I'm wondering why we are doing apple's work here...
Currently Being ModeratedOct 2, 2012 3:17 PM (in response to Siebbi)
Everyone come to our senses.
The vast majority of us having this issue. It is software problem*.
1- we all have this issue together, all with iOS6. - This points to software.
2- people reportedly fix it definitively with 5.1.1, this is particularly relevant because virtually no post is out there saying
that reverting to 5.1.1 does NOT fix the problem. It just seems like people is not trying to revert to 5.1.1 to fix this, because it's unreasonable hassle, or they do and succeed. This also points to software.
3- ANY statement about it "not being possibly" correlated is just a bit naive. Any developer with some years of xp could confirm that. I'm not going into details but just think: how come the iPhone displays an alert and stops the battery charging when it's too hot to prevent its explosions, if "software couldn't experience temperature".
Simplest thruth is there are things called thermal sensors all over sophisticated chips, and their readings are used by software in calculations and procedures that only depends on the lines of code written by someone, so yes, software does experience temperature pretty much like your brain does. You have sensors and you get readings.
That's pretty much it.
Huge reasons to look at software, no reason to look at hardware.
To be COMPLETELY honest is could be a hardware problem in just one possibility.
That is if iOS was less fault tolerant about some slight hardware or build imperfection. For example some bus reply max latency could have been changed resulting in that.
However that would still mean that a software update could solve the problem.
Currently Being ModeratedOct 2, 2012 3:21 PM (in response to Hidekiyamamoto)
Also one last possibility y for it being hardware : if the software causes it rendering it broken since then.
Also still in this case, the real origin is software.