desktop-packages team mailing list archive

[Lorn Potter <lorn.potter@xxxxxxxxxxxxx>]

@kgunn72 I think we certainly have moved on to a different bug.
Originally, QNAM was not considering mobile data connection at all,
because the QtBearer was only using generic plug (which does not know
the difference between mobile data and other network interfaces and is
not really usable anyway). The NetworkManager backend was also not
working as it should.

@mathieu-tl I just noticed in comment #10, you mention roaming (as does
the bug subject). Roaming in QConfiguration means 'connection migration'
where connections are migrated seamlessly to and from wlan/mobile (kind
of like what mobile does moving from tower to tower), i.e. a streaming
media would continue uninterrupted moving from wlan to mobile data.  I
believe it has been supported only on Symbian which did the connection
migrations at the platform level .

QNAM should now at least switch the configuration it uses when the
default route changes to one that is usable, which is about the closest
we can get to connection 'roaming' at this point. Previously a client
would have to tear down and create a new QNAM. Now, a QNAM get request
should succeed regardless when the QNAM was made.

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

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  In Progress
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “ofono” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions