Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
11-10-2009, 12:44 PM #1
GeoHot Offers to Fix iPhone WiFi Problems - For $10,000
GeoHot has declared the blacksn0w/blackra1n WiFi bug "closed," saying that after his investigation he believes it to be a problem with the iPhone firmware itself, rather than his work. On Twitter today, he made a statement suggesting he could fix the bug for $10,000. Most observers, though, are interpreting this as a tongue-in-cheek offer coming as it does in the wake of his smackdown of Jody Sanders' offer of $10,000 for the 3.1.2 baseband unlock.
Several separate Apple support forum threads address a persistent problem users have had with WiFi connectivity since the time of the 3.0 firmware release. The issue has manifested as a complete inability to connect, even from very close to the WiFi access point, to intermittent or permanent disconnects.
I’m using a 3G iPhone, and upgraded to 3.0 yesterday. Since then I’ve been unable to join any wifi network at all.The wifi dropping has been driving me nuts. It’s only started since 3.0. Before, it has always stayed connected, never had conflicts on the network, and was never an issue. But since 3.0, like a lot of others, it can’t hold the connection for more than 20 seconds without releasing.I have exactly the same problem. Wifi drops when the phone sleeps, and needs to be reset by toggling the wifi on-off switch. Scanning for the network is also flaky. It worked perfectly prior to installing the update. We need a fix, Apple!Before updating, Wifi worked flawlessly; at times even better than my macbook’s.
After the updating, my iPhone does not discover my networks anymore. I have made it recognize my home network, however, by getting closer to the router. But since distance has never been a problem, it definitely shouldn’t be now.
Though workarounds from resetting network settings, to enabling/disabling Airplane mode, to putting the iPhone in the freezer for a minute (thus voiding the warranty) have been suggested by the user community, there is as yet no official fix from Apple for this issue... other than returning your phone to an Apple Store for replacement.
The Following User Says Thank You to Paul Daniel Ash For This Useful Post: