← Back to team overview

desktop-packages team mailing list archive

[Bug 1426122] [NEW] Problems switching between WiFi and Mobile Data on MTK-based phones

 

Public bug reported:

On recent vivid  images running on phones with MTK modems ( arale,
krillin ) switching between WiFi and mobile-data and back leads to
broken networking where neither device ( WiFi or WWAN ) will establish a
network connection.

It appears that the new version of network-manager in vivid (
0.9.10-4ubuntu6 ) is incorrectly attempting to manage the devices
created by rild when mobile-data connections are established.

For instance, on krillin running RTM, 'nmcli -d' reports the following
networking devices:

% nmcli d
wlan0          wifi        disconnected
ril_0             gsm        connected
ril_1             gsm        disconnected

On the same device running vivid, an extra device which should be
unmanaged is listed:

% nmcli d
ril_0        gsm       connected     /310410786147829/context2
ccmni0   wifi       connected     ccmni0                    
wlan0     wifi       disconnected  --                        
ril_1        gsm       unavailable   --
ccmni1  wifi        unmanaged

Note that ccmni0 is listed as a wifi device, with a status of connected
whereas ccmni1 is listed as unmanaged.

If you look at syslog, you'll see a two log messages output after ril_0
is activated which show network-manager detecting a change in ccmni0 and
deciding it should become managed:

This bug was discovered on ubuntu-touch/vivid-proposed #122.


Feb 25 21:17:08 ubuntu-phablet NetworkManager[1163]: <info> (ccmni0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20\
 41]
Feb 25 21:17:08 ubuntu-phablet NetworkManager[1163]: <info> (ccmni0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20\
 30 41]

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1426122

Title:
  Problems switching between WiFi and Mobile Data on MTK-based phones

Status in network-manager package in Ubuntu:
  New

Bug description:
  On recent vivid  images running on phones with MTK modems ( arale,
  krillin ) switching between WiFi and mobile-data and back leads to
  broken networking where neither device ( WiFi or WWAN ) will establish
  a network connection.

  It appears that the new version of network-manager in vivid (
  0.9.10-4ubuntu6 ) is incorrectly attempting to manage the devices
  created by rild when mobile-data connections are established.

  For instance, on krillin running RTM, 'nmcli -d' reports the following
  networking devices:

  % nmcli d
  wlan0          wifi        disconnected
  ril_0             gsm        connected
  ril_1             gsm        disconnected

  On the same device running vivid, an extra device which should be
  unmanaged is listed:

  % nmcli d
  ril_0        gsm       connected     /310410786147829/context2
  ccmni0   wifi       connected     ccmni0                    
  wlan0     wifi       disconnected  --                        
  ril_1        gsm       unavailable   --
  ccmni1  wifi        unmanaged

  Note that ccmni0 is listed as a wifi device, with a status of
  connected whereas ccmni1 is listed as unmanaged.

  If you look at syslog, you'll see a two log messages output after
  ril_0 is activated which show network-manager detecting a change in
  ccmni0 and deciding it should become managed:

  This bug was discovered on ubuntu-touch/vivid-proposed #122.

  
  Feb 25 21:17:08 ubuntu-phablet NetworkManager[1163]: <info> (ccmni0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20\
   41]
  Feb 25 21:17:08 ubuntu-phablet NetworkManager[1163]: <info> (ccmni0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20\
   30 41]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1426122/+subscriptions


Follow ups

References