So confirmed that adding a case for
NM_DEVICE_STATE_REASON_MODEM_NO_CARRIER in device_state_changed ( nm-
device-modem.c ), causes the connection to be blocked from auto-
connecting.
I still see the initial retries decrement log message in
device_state_changed ( nm-policy.c ), I mentioned this is
** Tags added: lt-category-visible
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1418077
Title:
After radio technology is changed, mobile-data takes ~5m to re-connect
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: canonical-devices-system-image
Status: Confirmed = Won't Fix
** Changed in: canonical-devices-system-image
Status: Won't Fix = In Progress
** Changed in: canonical-devices-system-image
Milestone: ww09-2015 = ww13-2015
--
You received this bug notification
So what seems to be happening, is that the radio technology switch
causes the modem to unregister from the current carrier, and attempt to
re-register using the new tech preference ( eg. umts, lte, gsm, ... ).
This will cause the ofono ConnectionManager 'Attached' property to
return FALSE until
** Summary changed:
- NM fails to create a cellular data connection for a unacceptably long time
+ After radio technology is changed, mobile-data takes ~5m to re-connect
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
6 matches
Mail list logo
