In article <00893d89$0$24358$c3e8da3@news.astraweb.com>, John Doe <jdoe@usenetlove.invalid> wrote: > > IIRC, 2.0 software was pretty buggy and Apple rectified most if > > not of it with 2.1. With reports like these, I might wait for 3.1 > > before I upgrade my wife's 2G phone... > > As you probably already read... There is no software fix if the problem > occurs on her iPhone. Unless she can live without Wi-Fi and Bluetooth, > you definitely should wait. not everyone has wifi and bluetooth problems. 3.0 is working fine here. however, connecting to wifi sites that have a login page is a little different and the wifi icon doesn't always show up when you think it should even though it's connected. > I am technically inclined, with time to research the issue. At the > moment, I am trying to revert back to 2.2.1 but getting errors. how did you upgrade to 3.0? downgrading will require removing all traces of itunes and installing an older version so that you can load 221. it's a pain. archived from misc.phone.mobile.iphone

0

In article <hO81m.26$Vr2.18@newsfe21.iad>, Todd Allcock <elecconnec@AnoOspamL.com> wrote: > > 2.0 was a buggy mess. 3.0 is fairly stable, however, one issue to be > > aware of is push won't work on phones that aren't officially activated > > with at&t, at least until the dev team fixes the problem. > > Hmm... is that because only "official" carriers support the new notification > framework? For my wife's needs, she can live without push, but frankly, I'm > not sure anything in 3.0 is worth an upgrade headache. While I might do it > just for cut and paste, she doesn't care, and the other "revolutions" of > 3.0, like MMS don't work on her 2G, and for tethering we can just use my > phone. from what i understand, the push server looks for a valid account to push the alert and if it doesn't find a valid account, there's no reason to push anything. it makes sense from their point of view but it clearly sucks for users. i don't know how it will work on non-iphone carriers such as t-mobile usa, but their staff seems to welcome iphone users so who knows. there is also a hack for jailbreak apps that fakes the push but that's just for jailbroken apps. > I suspect I'll have to upgrade it to 3.x eventually for the same reason I > upgraded from a perfectly good 2.1 to 2.2- a few apps refused to work under > the "older" OSes. yep, that's what will drive it. already there are a few apps that require 3.0 and that will increase dramatically over the next month or two. i delayed 2.2 for a while but it got to the point where it was no longer an option. archived from misc.phone.mobile.iphone

0

In article <00264c77$0$9982$c3e8da3@news.astraweb.com>, John Doe <jdoe@usenetlove.invalid> wrote: > What version of iTunes should I use? Or can you link me to a page of > instructions? something before 8.2 final, which changes things for 3.0. google for downgrading, there's a lot of pages on how, with various techniques. here's one <http://www.hackint0sh.org/forum/f201/75172.htm> archived from misc.phone.mobile.iphone

0

In article <kQ81m.27$Vr2.1@newsfe21.iad>, Todd Allcock <elecconnec@AnoOspamL.com> wrote: > Do you have a recommendation for predicting exactly which phones will have > their WiFi and Bluetooth rendered inoperable prior to upgrading them? ;) > If not, John Doe's suggestion is probably prudent! nope, but if i had to guess, ones that were jailbroken and had non-standard software installed such as themes, 5 icon dock, categories, etc. would be most likely and the ones that are on official accounts the least likely. most people don't have any problems but that doesn't help a whole lot if you happen to be one of the unlucky ones. if you don't need to run something that requires 3.0 then you might as well wait. archived from misc.phone.mobile.iphone

0

John Doe <jdoe@usenetlove.invalid> wrote in news:008ba75a$0$29062$c3e8da3@news.astraweb.com: > http://discussions.apple.com/thread... > t=0 > > There is a very long thread about the same issue. > > Apparently the 3.0 update plagues some iPhone 3G with both of the > following conditions. > > No Wi-Fi > Bluetooth Unavailable > > I suspect it has something to do with my battery drain problem, at > least one poster in that thread at that web site mentioned the same. > > Not to be confused with poor/slow Wi-Fi connection speed, > it is totally unavailable. > "Daddy" decided you didn't need it? Trying to get more people to buy data service from ATTWS? No Bluetooth at all? -- ----- Larry If a man goes way out into the woods all alone and says something, is it still wrong, even though no woman hears him? archived from misc.phone.mobile.iphone

0

In article <007d6c56$0$5709$c3e8da3@news.astraweb.com>, John Doe <jdoe@usenetlove.invalid> wrote: > > would be most likely and the ones that are on official accounts > > the least likely. > > My account is pristine (and about two weeks old). have you tried deleting all network data? settings->general->reset->reset network settings > > most people don't have any problems > > Yes, especially those who have not made the upgrade. I wonder what > percentage of iPhone users have upgraded to 3.0. according to admob, 44% by june 20th, just three days after its release, and no doubt much higher now. <http://images.macrumors.com/article/2009/06/25/124210-iphone-os-june-22. jpg> archived from misc.phone.mobile.iphone

0

"John Doe" <jdoe@usenetlove.invalid> wrote in message news:007d92cc$0$5711$c3e8da3@news.astraweb.com... >>> I think it is a hardware problem. Maybe has something to do with >>> heat destroying a chip. The occurrence might effect certain >>> batches of iPhones and coincide with the update perhaps because >>> it produces more heat in a certain area of the iPhone (like the >>> WiFi chip or whatever). >> >> i doubt it's a hardware problem, > > The reason it is likely a hardware problem is because users do > something that fixes the problem, but shortly afterwards the problem > comes back again. Many people report that the problem magically > appears for no reason. That is highly suggestive of an intermittent > hardware failure, maybe caused by heat. > >> but it is definitely something that is affecting some users. >> >>> Who knows, maybe it has to do with charging and updating at the >>> same time. >> >> highly unlikely. > > Says who? Based on what? > > A total reset of the iPhone does not solve the problem. Technicians > at the Apple store cannot fix it either. > > All that stuff strongly indicates that it is a hardware problem. I'm inclined to believe the theory in the thread that there's corruption in the baseband NVRAM due to a partially failed update. Most people with the problem see no intermittent WiFi- it's dead and stays dead, while others see it come and go. Perhaps only less-critical portions of the code are corrupt for those folks, and it wigs out the hardware for a while until the wireless hardware resets itself, or until the next phone reset. Sort of like a bad sector on an old floppy disk- if the boot sector is bad, the computer can't read the disk at all, but if a random sector somewhere else is bad, the software on it runs just fine until it tries to access data from that bad sector and blam! Something unexpected happens, but you can reboot and run the same software again. If the WiFi/BT hardware's initialization code is mucked up, the hardware won't "boot", but if random code is corrupt it can initialize and just run flakey. Just my theory based on a _very_ limited understanding, but it fits the "clues." That would have to be a bizzare hardware defect for it to have been undiscovered, in some cases for up to two years, until this particular firmware, or just the "stress" of upgrading hit the device. (Not impossible, perhaps, but probably unlikely.) In either case, hardware or software, I'm certainly not updating my wife's 2G until a final determination is made by Apple as to cause, and a fix or workaround in place. Thank you for bringing it to my attention here, anyway, else I'd have probably been upgrading her phone this weekend! archived from misc.phone.mobile.iphone

0

In article <00896cf6$0$2718$c3e8da3@news.astraweb.com>, John Doe <jdoe@usenetlove.invalid> wrote: > I think it is a hardware problem. Maybe has something to do with heat > destroying a chip. The occurrence might effect certain batches of > iPhones and coincide with the update perhaps because it produces more > heat in a certain area of the iPhone (like the WiFi chip or whatever). i doubt it's a hardware problem, but it is definitely something that is affecting some users. > Who knows, maybe it has to do with charging and updating at the same > time. highly unlikely. > The same problem has occurred before with other updates, including the > battery drain problem. Mine will be taken to the local Apple store on > Monday for them to mess with, and then hopefully they will replace it > with new. If 3.0 is not preinstalled, I will wait until the next minor > version before updating. if it's under warranty, by all means bring it in. they'll make it right. archived from misc.phone.mobile.iphone

0

"Todd Allcock" <elecconnec@AnoOspamL.com> wrote: > IIRC, 2.0 software was pretty buggy and Apple rectified most if > not of it with 2.1. With reports like these, I might wait for 3.1 > before I upgrade my wife's 2G phone... As you probably already read... There is no software fix if the problem occurs on her iPhone. Unless she can live without Wi-Fi and Bluetooth, you definitely should wait. I am technically inclined, with time to research the issue. At the moment, I am trying to revert back to 2.2.1 but getting errors. -- Google has destroyed access to the USENET archive... down with Google archived from misc.phone.mobile.iphone

0

nospam <nospam@nospam.invalid> wrote: > In article <00893d89$0$24358$c3e8da3@news.astraweb.com>, John Doe > <jdoe@usenetlove.invalid> wrote: > >> > IIRC, 2.0 software was pretty buggy and Apple rectified most if >> > not of it with 2.1. With reports like these, I might wait for >> > 3.1 before I upgrade my wife's 2G phone... >> >> As you probably already read... There is no software fix if the >> problem occurs on her iPhone. Unless she can live without Wi-Fi >> and Bluetooth, you definitely should wait. > > not everyone has wifi and bluetooth problems. 3.0 is working fine > here. however, connecting to wifi sites that have a login page is > a little different and the wifi icon doesn't always show up when > you think it should even though it's connected. > >> I am technically inclined, with time to research the issue. At >> the moment, I am trying to revert back to 2.2.1 but getting >> errors. > > how did you upgrade to 3.0? downgrading will require removing all > traces of itunes and installing an older version so that you can > load 221. it's a pain. So far, I have what looks like the 2.2.1 software. iPhone1,2_2.2.1_5H11_Restore.ipsw What version of iTunes should I use? Or can you link me to a page of instructions? Thanks. FWIW. I keep known good incremental copies of the operating system partition. I also know where all important data files are, and regularly copy them to safe places. Doing what you describe is no problem here. archived from misc.phone.mobile.iphone

0

In article <007d92cc$0$5711$c3e8da3@news.astraweb.com>, John Doe <jdoe@usenetlove.invalid> wrote: > >> I think it is a hardware problem. Maybe has something to do with > >> heat destroying a chip. The occurrence might effect certain > >> batches of iPhones and coincide with the update perhaps because > >> it produces more heat in a certain area of the iPhone (like the > >> WiFi chip or whatever). > > > > i doubt it's a hardware problem, > > The reason it is likely a hardware problem is because users do > something that fixes the problem, but shortly afterwards the problem > comes back again. Many people report that the problem magically > appears for no reason. That is highly suggestive of an intermittent > hardware failure, maybe caused by heat. it also could be buggy software. > >> Who knows, maybe it has to do with charging and updating at the > >> same time. > > > > highly unlikely. > > Says who? Based on what? because in order to do a firmware update, you have to plug in the cable which charges the device. in other words *every* iphone and ipod touch charges when an update is done. > A total reset of the iPhone does not solve the problem. Technicians > at the Apple store cannot fix it either. i thought you said you will be going in on monday. if they can't fix it, they'll replace it. > All that stuff strongly indicates that it is a hardware problem. could be, but if it was working before, i'd be surprised that updating caused it to fail. archived from misc.phone.mobile.iphone

0

nospam <nospam nospam.invalid> wrote: > In article <kQ81m.27$Vr2.1 newsfe21.iad>, Todd Allcock <elecconnec > AnoOspamL.com> wrote: > >> Do you have a recommendation for predicting exactly which phones >> will have their WiFi and Bluetooth rendered inoperable prior to >> upgrading them? ;) If not, John Doe's suggestion is probably >> prudent! > > nope, but if i had to guess, ones that were jailbroken Nope. > and had non-standard software installed such as themes, Nope. > 5 icon dock, Nope. > categories, Nope. > etc. Nope. > would be most likely and the ones that are on official accounts > the least likely. My account is pristine (and about two weeks old). > most people don't have any problems Yes, especially those who have not made the upgrade. I wonder what percentage of iPhone users have upgraded to 3.0. > but > that doesn't help a whole lot if you happen to be one of the unlucky > ones. if you don't need to run something that requires 3.0 then you > might as well wait. > > > Path: news.astraweb.com!border2.newsrouter.astraweb.com!news-out.octanews.net!indigo.octanews.net!news.glorb.com!feeder.erje.net!newsfeed.straub-nv.de!feeder.motzarella.org!news.motzarella.org!motzarella.org!news.motzarella.org!not-for-mail > From: nospam <nospam nospam.invalid> > Newsgroups: misc.phone.mobile.iphone > Subject: Re: Why is setting "Wi-Fi" grayed out now? > Date: Fri, 26 Jun 2009 15:06:31 -0400 > Organization: A noiseless patient Spider > Lines: 14 > Message-ID: <260620091506319101%nospam nospam.invalid> > References: <0025b1b4$0$9990$c3e8da3 news.astraweb.com> <008ba75a$0$29062$c3e8da3 news.astraweb.com> <Xns9C367A99159D6noonehomecom 74.209.131.13> <iz71m.3$ox3.2 newsfe17.iad> <00893d89$0$24358$c3e8da3 news.astraweb.com> <260620091352436673%nospam nospam.invalid> <kQ81m.27$Vr2.1 newsfe21.iad> > Mime-Version: 1.0 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 8bit > X-Trace: news.eternal-september.org U2FsdGVkX1/E4a7hlVgcdNyNL8vsrfUZBJBXQJBXcBHQ0Zc5vjqN3OQfTUVT/ldYBQ2l5tW34/aSCOVbmPJAPGIKD/yPd1/hIXBulN8k/Pkf3/OrVeClzi9ej6DrKvWQl0GZpmYht4U= > X-Complaints-To: abuse motzarella.org > NNTP-Posting-Date: Fri, 26 Jun 2009 19:06:32 +0000 (UTC) > X-Auth-Sender: U2FsdGVkX1+vC5Dw29m5fkwtQtZW7sISnMe/ePeEncE= > Cancel-Lock: sha1:Z12Wt23CyxpRQ3L/U8wk6Z+opBQ= > User-Agent: Thoth/1.8.3 (Carbon/OS X) > archived from misc.phone.mobile.iphone

0

On 26 Jun 2009 07:05:30 GMT, John Doe <jdoe@usenetlove.invalid> wrote: >Without changing anything to do with my wireless router, after >upgrading to OS 3.0 (coincidental or not), now the settings for Wi-Fi >are grayed out. Anyone know why? Before, I was being asked for a >password apparently to my 2-Wire wireless router. > >Thanks. Just got my WIFI to connect after I turned on and off the VPN settings 3 or 4 times in a role, I didn't set anything up I just turned it on then clicked cancel 3 or 4 times in a role and now my WIFI worked where as before I couldn't get it to connect after 3.0 update but mine was not grayed out like some is but maybe it will work for you archived from misc.phone.mobile.iphone

0

nospam <nospam@nospam.invalid> wrote: > In article <00264c77$0$9982$c3e8da3@news.astraweb.com>, John Doe > <jdoe@usenetlove.invalid> wrote: > >> What version of iTunes should I use? Or can you link me to a page of >> instructions? > > something before 8.2 final, which changes things for 3.0. google for > downgrading, there's a lot of pages on how, with various techniques. > here's one > > <http://www.hackint0sh.org/forum/f201/75172.htm> http://discussions.apple.com/thread... "Before I made the upgrade to FW 3.0 my iphone was working just fine with the FW 2.2.1 (Wi-Fi and Bluetooth working). Now that I made the upgrade to the FW 3.0...my phone grayed out the Wi-Fi and made my bluetooth unavailable. So I downgrade my phone to the 2.2.1 to see if the problem could be solve...but guess what No Wi-Fi and No Bluetooth!!!" archived from misc.phone.mobile.iphone

0

Mike <mikeloveschampagneandrugby@googlemail.com> wrote: > Todd Allcock wrote: >> >> "nospam" <nospam@nospam.invalid> wrote in message >> news:260620091352436673%nospam@nospam.invalid... >>> In article <00893d89$0$24358$c3e8da3@news.astraweb.com>, John >>> Doe <jdoe@usenetlove.invalid> wrote: >>>> >>>> As you probably already read... There is no software fix if the >>>> problem occurs on her iPhone. Unless she can live without Wi-Fi >>>> and Bluetooth, you definitely should wait. >>> >>> not everyone has wifi and bluetooth problems. 3.0 is working >>> fine here. however, connecting to wifi sites that have a login >>> page is a little different and the wifi icon doesn't always show >>> up when you think it should even though it's connected. >> >> Do you have a recommendation for predicting exactly which phones >> will have their WiFi and Bluetooth rendered inoperable prior to >> upgrading them? ;) If not, John Doe's suggestion is probably >> prudent! > > A big Upgrade always carries risks, even with apple. I tend to be > cautious and wait o see if the upgrade is successful with others > however I dove in head first at 6:15 pm BST and thankfully had no > problems beyond apple's then O2 servers being very busy delaying > and the reg and MMS. > > I personally know six iphone users all upgraded without problem in > the first week and sat next to a couple of very attractive young > ladies on the train who had no problems either. I think it is a hardware problem. Maybe has something to do with heat destroying a chip. The occurrence might effect certain batches of iPhones and coincide with the update perhaps because it produces more heat in a certain area of the iPhone (like the WiFi chip or whatever). Who knows, maybe it has to do with charging and updating at the same time. The same problem has occurred before with other updates, including the battery drain problem. Mine will be taken to the local Apple store on Monday for them to mess with, and then hopefully they will replace it with new. If 3.0 is not preinstalled, I will wait until the next minor version before updating. archived from misc.phone.mobile.iphone

0

Todd Allcock wrote: > > "nospam" <nospam@nospam.invalid> wrote in message > news:260620091352436673%nospam@nospam.invalid... >> In article <00893d89$0$24358$c3e8da3@news.astraweb.com>, John Doe >> <jdoe@usenetlove.invalid> wrote: >>> >>> As you probably already read... There is no software fix if the problem >>> occurs on her iPhone. Unless she can live without Wi-Fi and Bluetooth, >>> you definitely should wait. >> >> not everyone has wifi and bluetooth problems. 3.0 is working fine >> here. however, connecting to wifi sites that have a login page is a >> little different and the wifi icon doesn't always show up when you >> think it should even though it's connected. > > Do you have a recommendation for predicting exactly which phones will > have their WiFi and Bluetooth rendered inoperable prior to upgrading > them? ;) If not, John Doe's suggestion is probably prudent! A big Upgrade always carries risks, even with apple. I tend to be cautious and wait o see if the upgrade is successful with others however I dove in head first at 6:15 pm BST and thankfully had no problems beyond apple's then O2 servers being very busy delaying and the reg and MMS. I personally know six iphone users all upgraded without problem in the first week and sat next to a couple of very attractive young ladies on the train who had no problems either. The only problem I have had is a few safari crashes, particularly if trying to exit/change pages whilst one is downloading. Mike archived from misc.phone.mobile.iphone

0

nospam wrote: > In article <iz71m.3$ox3.2@newsfe17.iad>, Todd Allcock > <elecconnec@AnoOspamL.com> wrote: > >> IIRC, 2.0 software was pretty buggy and Apple rectified most if not of it >> with 2.1. With reports like these, I might wait for 3.1 before I upgrade my >> wife's 2G phone... > > 2.0 was a buggy mess. 3.0 is fairly stable, however, one issue to be > aware of is push won't work on phones that aren't officially activated > with at&t, at least until the dev team fixes the problem. Works fine with O2! Mike archived from misc.phone.mobile.iphone

0

nospam <nospam@nospam.invalid> wrote: > In article <00896cf6$0$2718$c3e8da3@news.astraweb.com>, John Doe > <jdoe@usenetlove.invalid> wrote: > >> I think it is a hardware problem. Maybe has something to do with >> heat destroying a chip. The occurrence might effect certain >> batches of iPhones and coincide with the update perhaps because >> it produces more heat in a certain area of the iPhone (like the >> WiFi chip or whatever). > > i doubt it's a hardware problem, The reason it is likely a hardware problem is because users do something that fixes the problem, but shortly afterwards the problem comes back again. Many people report that the problem magically appears for no reason. That is highly suggestive of an intermittent hardware failure, maybe caused by heat. > but it is definitely something that is affecting some users. > >> Who knows, maybe it has to do with charging and updating at the >> same time. > > highly unlikely. Says who? Based on what? A total reset of the iPhone does not solve the problem. Technicians at the Apple store cannot fix it either. All that stuff strongly indicates that it is a hardware problem. > >> The same problem has occurred before with other updates, >> including the battery drain problem. Mine will be taken to the >> local Apple store on Monday for them to mess with, and then >> hopefully they will replace it with new. If 3.0 is not >> preinstalled, I will wait until the next minor version before >> updating. > > if it's under warranty, by all means bring it in. they'll make it > right. archived from misc.phone.mobile.iphone

0

FWIW: I posted the question to (sci.electronics.design), in case anyone else is interested in reading technical discussion about the subject (assuming replies). -- thanks to the replies archived from misc.phone.mobile.iphone

0

* John Doe (2009-06-26): > nospam <nospam@nospam.invalid> wrote: > > In article <00264c77$0$9982$c3e8da3@news.astraweb.com>, John Doe > > <jdoe@usenetlove.invalid> wrote: [...] > "Before I made the upgrade to FW 3.0 my iphone was working just fine > with the FW 2.2.1 (Wi-Fi and Bluetooth working). Now that I made the > upgrade to the FW 3.0...my phone grayed out the Wi-Fi and made my > bluetooth unavailable. So I downgrade my phone to the 2.2.1 to see > if the problem could be solve...but guess what No Wi-Fi and No > Bluetooth!!!" Restore the phone in DFU mode, do _not_ use your backed up settings but set up a new device next. This fixed BT on my 2G, didn't have any WiFi problems before or after (WPA2-PSK). -André -- May as well be hung for a sheep as a lamb! Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns.org> iPhone <http://hvkls.dyndns.org/downloads/documentation/README-iphone.html> archived from misc.phone.mobile.iphone

0

André Berger <andre.berger@web.de> wrote: > * John Doe (2009-06-26): http://discussions.apple.com/thread... >> "Before I made the upgrade to FW 3.0 my iphone was working just >> fine with the FW 2.2.1 (Wi-Fi and Bluetooth working). Now that I >> made the upgrade to the FW 3.0...my phone grayed out the Wi-Fi >> and made my bluetooth unavailable. So I downgrade my phone to the >> 2.2.1 to see if the problem could be solve...but guess what No >> Wi-Fi and No Bluetooth!!!" > > Restore the phone in DFU mode, do _not_ use your backed up > settings but set up a new device next. This fixed BT on my 2G, > didn't have any WiFi problems before or after (WPA2-PSK). > > -André ? You did not even have the same problem, dude. > Path: news.astraweb.com!border1.newsrouter.astraweb.com!feed.news.qwest.net!mpls-nntp-07.inet.qwest.net!195.208.113.67.MISMATCH!goblin1!goblin.stu.neva.ru!news.albasani.net!fuchs.local!not-for-mail > From: Andr‚ Berger <andre.berger@web.de> > Newsgroups: misc.phone.mobile.iphone > Subject: Re: Why is setting "Wi-Fi" grayed out now? > Date: Sat, 27 Jun 2009 11:49:35 +0200 > Organization: albasani.net > Lines: 22 > Message-ID: <20090627094935.GA14365@fuchs> > References: <0025b1b4$0$9990$c3e8da3@news.astraweb.com> <008ba75a$0$29062$c3e8da3@news.astraweb.com> <Xns9C367A99159D6noonehomecom@74.209.131.13> <iz71m.3$ox3.2@newsfe17.iad> <00893d89$0$24358$c3e8da3@news.astraweb.com> <260620091352436673%nospam@nospam.invalid> <00264c77$0$9982$c3e8da3@news.astraweb.com> <260620091502214089%nospam@nospam.invalid> <00266d36$0$9982$c3e8da3@news.astraweb.com> > Mime-Version: 1.0 > Content-Type: text/plain; charset=iso-8859-1 > Content-Transfer-Encoding: 8bit > X-Trace: news.albasani.net q+yF8Hy+Z1vVXnFmNTMu01v40eVFTYF2tmlNXcfQt5QC3nMTEChbg/Amwp4h4regNBLxWd4k220Xl03IQR7gyszyjpWyHfvGhtsRea2D1+L8vpXe2HzbFm+1FQ71YH1M > X-Complaints-To: abuse@albasani.net > NNTP-Posting-Date: Sat, 27 Jun 2009 09:50:09 +0000 (UTC) > X-User-ID: Bg3cTapAzsUBkOXqtPVEZ+v5q5h/WGeCQmMxCoGxPXk= > In-Reply-To: <00266d36$0$9982$c3e8da3@news.astraweb.com> > Content-Disposition: inline > X-GPG-Key: 0x7FB4C1A3 : "http://www.keyserver.net" > X-GPG-Fingerprint: 6991 DFD7 5BED A877 779F F7DE 9A56 EBBE 7FB4 C1A3 > Cancel-Lock: sha1:4EaKzHj+ROpB9pQPnKExh073c/0= > User-Agent: Mutt/1.5.19 (2009-01-05) > X-NNTP-Posting-Host: obGkfIplAjWBfku+abXns5OvYrZegFe7gGnL8+w2YP0= > X-Web-Site: <http://hvkls.dyndns.org/> > Mail-Copies-To: nobody archived from misc.phone.mobile.iphone

0

Here is an interesting possibility for trying to get the WiFi back. Also taken from the Apple forum. http://discussions.apple.com/thread... > I am one of the victim losing WiFi and Bluetooth (grey out) after > OS 3.0 upgrade. I spent hours searching internet and finally > recover my WiFi only (but not yet bluetooth). Would like to share > if this helps other victims of OS3.0 upgrade. > > 1. Download iRecovery for Windows 1.3 > > http://www.zaksenterprises.com/inde... > 2. Install both libusb and iRecovery > 3. Turn your iphone 3G to Recovery mode > http://www.zaksenterprises.com/inde... > 4. Goto c:\iRecovery\iRecovery_SVN > 5. run iRecovery -s > 6. printenv wifiaddr to confirm still "00:00:00:00:00:00" > 7. setenv wifiaddr "xx:xx:xx:xx:xx:xx" - new wifiaddress > 8. saveenv > 9. fsboot > > Now you have your WiFi back to normal. archived from misc.phone.mobile.iphone

0

John Doe wrote: > Without changing anything to do with my wireless router, after > upgrading to OS 3.0 (coincidental or not), now the settings for Wi-Fi > are grayed out. Anyone know why? Before, I was being asked for a > password apparently to my 2-Wire wireless router. > > Thanks. I had to reset WiFi to get it to work at all but it now refuses to connect to 2Wire router, invalid password although it isn't. Works OK on WiFi hotspots and our other router. Chris archived from misc.phone.mobile.iphone

0