Because, unless you only use your phone in Cupertino, WiFi sucks A LOT. Particularly on public networks (usually automatically).
-
Show this thread
-
I assumed that when the phone appeared to be using WiFi, but packet rate sucked, it’d quietly switch to cellular. Beautiful.
4 replies 0 retweets 9 likesShow this thread -
Instead Apple did the opposite. When your phone appeared to be on LTE but (marginal) WiFi was available, it’d SWITCH TO THE BAD WIFI.
9 replies 0 retweets 18 likesShow this thread -
So I’m constantly wondering why my AT&T service sucks, and no — my phone’s just connecting to WiFi. And failing. With no indication.
4 replies 1 retweet 13 likesShow this thread -
Literally the only thing that makes the phone operational in range of marginal WiFi is to turn off WiFi. And now Apple’s made that harder.
11 replies 2 retweets 28 likesShow this thread -
Dear Apple: if TCP connections are failing and ACKs aren’t coming back, stop trying to use that network and switch to another. Why so hard?
12 replies 7 retweets 68 likesShow this thread -
Replying to @matthew_d_green
In the age of unlimited 4G/LTE, the built-in preference for WiFi is odd. Android has this too; Samsungs do system updates only over WiFi.
3 replies 0 retweets 5 likes -
Replying to @mjos_crypto @matthew_d_green
So I had to flip that 4G sim to an another phone, set it up as a mobile hotspot, and THEN my primary phone downloaded the 1GB system update.
1 reply 0 retweets 1 like -
Replying to @mjos_crypto @matthew_d_green
Hypothesis: phones would be a lot better with a "case" like the ext batt ones but containing 4G modem & wifi ap, no sim in phone.
2 replies 0 retweets 1 like -
Thereby no baseband vulns/backdoors.
2 replies 0 retweets 0 likes
Plus you could buy a $200 iPod touch instead of a $1000 iPhone.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.