asked 2014-03-25 17:52:06 +0200
mobile data should only be disabled when wifi is actually working completely, i often see that mobile data is disabled even when it's trying to connect or not getting dhcp or whatnot...
this means that network is interrupted while moving in/out of range.
not sure if this is connman or not. but this seems like a feature not yet present (probably in connman)
answered 2014-03-26 22:14:35 +0200
Since we do not have support for seamless wifi <=> 2/3/4g connection migration, there will always be network interruption when switching technologies. Is this what you mean?
well, it's not really about seamless, (though that would be nice), but more when you have a wifi connected, that does not give DHCP, you can see that when a open or remembered wifi is available, mobile data is disconnected immediately... before a valid DHCP address is set.
thing is, if you would not disconnect mobile data, what would happen is that you get a wifi ip and default route, which (if metric is used) would have priority over mobile data, at that point, all existing routes would still use mobile data, and the new ones would use the wifi. what i would like is that ip route flush cache is called and mobile data disconnected afterwards.
i suspect this is connman functionality, but i'm not sure, it would be nice to get confirmation; because, afaict it should be perfectly possible (and desirable (even if not, it can still be an option)), and if so, community could help make this possible
AL13N ( 2014-03-26 23:05:19 +0200 )editanswered 2014-03-27 02:11:28 +0200
That would be very, very bad for those of us trying to keep mobile-data-tranfers under control, which, to us, costs money!
What we want is that whenever a Wifi is available, no mobile-data is spent. If/when wifi connection is deemed impossible, and only then, mobile-data should be enabled!
Altough I would not oppose to a settings option to reverse this behaviour for the ones spoiled for bandwidth!
I think the OP's goal is to minimize network downtime and keep the mobile network running until the WLAN connection has actually been established, rather than take down mobile communications first, then begin to attempt and possibly fail at connecting to WLAN, leaving the user without any network at all during the interim. So, basically s/he wants the same as you request, i.e. mobile data as long as WLAN communications are impossible.
00prometheus ( 2014-03-27 05:42:38 +0200 )edit@dsilveira@00prometheus that's right, and if you paid attention, i'm not adverse to having this as a setting being non-default...
some people prioritize mobile data bandwidth costs, other people prioritize having connectivity.
that being said, even if connectivity is prioritized, i'm just saying that if wifi doesn't work, to keep having mobile data for a few seconds... it's not gonna make that much of a difference...
AL13N ( 2014-03-27 08:57:22 +0200 )editAsked: 2014-03-25 17:52:06 +0200
Seen: 336 times
Last updated: Mar 27 '14
This sounds like the same thing I reported here: https://together.jolla.com/question/35651/bug-losing-mobile-data-connection-when-known-wifi-available-but-no-signal/ duplicate?
matrixx ( 2014-03-27 16:15:38 +0200 )edit@matrixx not sure if it's 100% the same issue (afaict, internally, it tries to connect (doesnt show it) and has signal, but just doesn't get DHCP or has some other kind of error), and mine is a feature-request, not a bug, and i want clarification regarding if or if not this is connman, and so i could fix it myself in mer upstream. i did look for similar issues, but didn't find anything...
AL13N ( 2014-03-27 16:58:39 +0200 )edit@AL13N I agree. Now when I compare them a bit more, they are different issues. My case happens in a "spot" in the edge of wifi where it can't make a decision to use working mobile data over non-working wifi, cause it's still in the range and prefers the wifi.
matrixx ( 2014-03-28 23:23:22 +0200 )edit