One day we might solve this problem, if we're ever able to pressure phone companies into reinvesting into their infrastructure instead of their investors.
[1]: http://speedify.com/mobile-vpn
[2]: https://play.google.com/store/apps/details?id=it.opbyte.supe...
[3]: http://forums.androidcentral.com/samsung-galaxy-s5/402722-ho...
Short of hammering the AP with test transmissions (oh no, battery life) when the connection starts to get below a certain level, not sure how it could solve this before the user attempts to do something.
Or how about if some x% of packets were lost/failed checksum you revert to cellular?
Both of these would likely require changes to the wireless drivers but they don't seem too unachievable.
I'm making a bit of an assumption here, but I think if Apple or Google could detect spotty wifi quickly enough to boot up the cellular antenna, they would be. I think the issue is more that by the time the phone can tell there is a problem there isn't enough time to bring up the cellular antenna and connect before service is interrupted.
I can't say I know much about cellular networks either, but in my opinion having the cellular antenna connected to the network at all times would greatly simplify the handoff when wifi gets spotty. The ability to use both to download/upload is just icing on the proverbial cake.
Great prices also. Since I'm almost always using WiFi, the $20 a month for global unlimited text and phone calls with a $10/gig data rate means I only spend about $25 a month for my smartphone service. You can only use a subset of Google phones, but I find my Nexus 5x fits my needs. I also always get Android updates right away, if I want to install them.
My phone lasts nearly 24 hours on a charge, I wouldn't mind it last considerably less (18 hours for example) if I used both antennas though.
They're $10/gb flat with refunds for unused GB. At what usage levels do you think they're 'some of the highest rates in the industry?'
I use <3 gb/MO, mainly because the mobile <-> WiFi switching is so seamless, and I've never paid more than $50/mo off contract. The UX is also top tier, which i couldn't say about Straight Talk (my last provider).
I'll buy that they're not the cheapest, but which plan offers substantially cheaper?
https://play.google.com/store/apps/details?id=com.cheekydevs...
Network switch comes with non-zero cost that all connections must be treated reset and have to be reestablished, so even if the platform monitors quality of all uplinks, we still need some uplink stickiness to avoid constant switching between uplinks in places with spotty coverage or flaky uplinks. I'm not saying current status quo is the best, but currently we cannot have it work perfectly.
There are other possible failure modes, of course, but fixing the common case has value.
I would also add that specifically for things like Uber it'd be good to set very low network timeouts for Wifi and allow certain apps to suggest to the device they'd like to switch.
The problem is that Apple botched the roll out and everybody freaked out and complained about their iPhone eating their data plan and driving their phone bill to $2000.
Also helps me avoid worrying about spying... work has a right to monitor (blue coat) all comms so better to keep work and home stuff separate.
Having wifi on is pretty bad for my battery life in general, because I'm moving around a dense city and my phone constantly is trying to connect to open wifi hotspots that are going in and out of range. Keeping it on only extends battery life if my phone is staying in one place with good wifi.
Airplane mode, Wifi only, Mobile data (LTE) only, Wifi + Mobile data (LTE). This listing is in order of battery consumption AFAIK.
The user I responded to uses only Mobile data (LTE). His Wifi is never on, but his Mobile data always is. I suggested that since he uses mobile data instead of wifi, he would be using more battery.
Settings > Wi-Fi > Ask to Join Networks (at the bottom of that screen)
On Android, if you unlock the hidden Developer Options, there is a toggle for "Aggressive WiFi to mobile handover".
But I wonder why the setting is hidden and not a default.
I've no signal at home. Can't receive SMS or calls. So I need to leave my phone next to the window to get the SMS. And then, generally, wait, since verification SMSs take from minutes to hours to reach.
I wish companies abroad would stop taking instant SMS for granted. It's also the stupidest second-factor you can ask me for: if I ever lose my phone, then I lost my number too.
I get get Wi-Fi from home up to about half a block down my road. Then there's the cafes and stuff, and of course, 4G.
This is a known probem, and most good 2FA services have solutions. For example, Google offers a small number of "recovery codes" you can store for times when your 2FA device isn't available. https://support.google.com/accounts/answer/1187538?hl=en
The assumption is that your phone is PIN-protected, and you can contact your phone operator to get the old SIM blocked and a new SIM issued. This breaks down when it comes to prepaid though.
I know this works for some companies in some countries, and this brings me back the same thing I keep seeing all over: stop assuming the entire world works exactly like your city/provider/contract.
Of course there was a massive online campaign when it was released last year to turn it off, because Apple was costing you money because the phone might use more 3G data! People... [in AU at least you pay by the GB for data]
You can tap on About Phone a few times to enable Developer mode.
I've gotten to the point where I'll manually turn off WiFi as soon as I set foot outside my front door. It should be automatic.
My intuition for whether a request that's not done yet is ever going to complete seems to be much better than what's written into most apps. It's really annoying when I have to entirely kill and reopen the app, rather than just have that one operation retried.
The main culprit here is of course TCP's session based view of the world which was invented for a completely different era. An era when "cable got cut" was a catastrophic event that was almost never going to happen. It's a pity that the native app world is still mostly stuck with TCP/HTTP based networking stack where a UDP/mobile-specific-protocol is what's needed.
https://www.howtogeek.com/129728/how-to-access-the-developer...
you then have the option to enable "Aggressive Wi-Fi to Cellular handover"
> It just artificially reduces the WiFi RSSI (received signal strength indication) to encourage the WiFi state machine to decide to switch the connection from WiFi to cellular network.
https://android.stackexchange.com/questions/90250/what-does-...
Anecdotally, I have had fewer headaches with the phone holding on to poor wifi-signals since I enabled this. Ideally the phone would handle this in a smarter way, e.g., by monitoring the strength of both the wifi and data signals and switching to whichever is likely to have the least packet loss.
The tradeoff here of course is battery life. The phone OS doesn't want to switch on a second radio until absolutely necessary for obvious reasons.
My naive intuition would just say that if the wifi connection suddenly degrades, the networking stack should just automatically switch over and try cellular -- are there complications?
That wait time, unfortunately, is long on human timescales. Also, there's the chance your ping was lost, so your phone tries at least a few times before giving up.
This Quora thread is a good example of the typical non-answers provided to this question.
https://www.quora.com/Why-does-it-take-so-long-to-establish-...
Add more antennas, and you can say more things on more channels at once. "Enterprise-grade" multi-antenna routers (e.g. routers in conference halls) negotiate new connections much more quickly.
Cell towers are essentially a whole bunch of antennas (or a few antennae in highly-MIMO setups, so effectively the same thing) so there's comparatively next to no latency for sending "unexpected" packets to the tower.
(Establishing connectivity with a new cell is still hard, though, since it takes a moment for a handset to get the tower's attention when the handset doesn't yet know where precisely the tower is for MIMO-beamforming to kick in. This is ameliorated by many cellular ISPs mirroring connection state between neighbouring cells, so that when you move from one cell to another, the new tower is already "expecting" you.)
Since connectivity takes (far) less than 10s on enterprise-grade multi-antenna routers, all that time is being spent in some component that's different between the two classes of hardware. So looking at the difference in BOM between average products of the two classes might be helpful in figuring things out.
Otherwise, I hope things have been going well, btw =).
(I agree you make it seem pretty clear though, either it is silly or there are more details to be learned...)