Merge lp:~phablet-team/network-manager/lp1461593 into lp:~phablet-team/network-manager/vivid-phone-overlay
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Alfonso Sanchez-Beato on 2015-06-10 | ||||
| Approved revision: | 964 | ||||
| Merged at revision: | 963 | ||||
| Proposed branch: | lp:~phablet-team/network-manager/lp1461593 | ||||
| Merge into: | lp:~phablet-team/network-manager/vivid-phone-overlay | ||||
| Diff against target: |
278 lines (+258/-0) 3 files modified
debian/changelog (+9/-0) debian/patches/lp1461593-add-modem-reconnect-delay.patch (+247/-0) debian/patches/series (+2/-0) |
||||
| To merge this branch: | bzr merge lp:~phablet-team/network-manager/lp1461593 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Alfonso Sanchez-Beato | 2015-06-08 | Approve on 2015-06-10 | |
|
Review via email:
|
|||
Commit Message
debian/
a 5s delay to NM_POLICY's activation logic triggered when a
device is disconnected. This allows the modem time to settle
and NM to process the resulting DBus state changes (LP: #1461593).
Description of the Change
This change adds a 5s delay into NM_POLICY's re-connect logic, specifically so that the retry_limit of the associated connection isn't exhausted immediately whenever the connection drops, which then used to result in a 5m timer being set.
There are two changes...
1. The afore-mentioned 5m timer is now reduced to 30s for modem devices. In theory, connections shouldn't be getting disabled anymore due to the above fix, so this is a just-in-case change.
2. The low-level NM_MODEM_OFONO code wasn't setting the modem state to DISCONNECTING when disconnect() was called. This is now done, and in the associated callback ( disconnect_cb ) the new state is now determined by the ofono cached properties ( online && powered && attached ).
I downloaded NM from the phablet PPA (0.9.10.
This happened on krillin, using 2 SIMs. Version is
channel: ubuntu-
last update: 2015-06-09 10:58:15
version version: 28
| Tony Espy (awe) wrote : | # |
Replies to comments added.
Just tested RTM, NM does re-establish the connection when switching the slot with 3G capabilities in that case.
'Powered' does not migrate from one SIM to the other when switching the 3g slot, in vivid and in rtm.
| Tony Espy (awe) wrote : | # |
Thanks Alfonso... that makes sense as the NM/ofono code was forward ported to 0.9.10 for the vivid cycle, so the logic is significantly different.
Silo 31 tested (krillin/vivid ubuntu-
Same results as previously, as expected:
* Switching the preferred technology between 2G and 3G works fine
* Flight mode seems to be ok too.
* NM was not re-establishing the connection when switching the slot with 3G capabilities.
Additionally, I confirmed that switching cellular data between SIM1 and SIM2 does work.
| Tony Espy (awe) wrote : | # |
Silo 31 tested (arale/vivid ubuntu-
Ran the basic test cases from the new network-manager touch-specific test plan:
https:/
Skipped the FlightMode tests due the following bug:
https:/
| Tony Espy (awe) wrote : | # |
Silo 31 tested (mako/vivid ubuntu-
Ran the basic test cases from the network-manager component test plan:
https:/
The only tests not performed were the out-of-range Wi-Fi tests and the force-mobile-


Just some minor comments, besides that it looks great to me.