* open system settings->update
* when there is a larger update available, start the download.
* turn off wifi or walk from wifi zone
Known issues:
1. Euronews, Engadget and Today scope to not ever see network
2. Occasionally update check will hang when changing network device(wifi -> 3g)
3. Occasionally update download will not resume properly when network change.
I am fairly certain that #1 can only be fixed by moving QtBearer plugin to connectivity-api, although I do not see any apparmor denials in the log, with this change it makes QNetworkRequest require a QNetworkSession, which in turn I believe fails as the known and unfixable QtNetwork network-manager backend issues with apparmor. I am assuming that scopes run in contained space, because other commandline based tests with QtNetworking access work, but Click apps that use QtNetworking fail similarly.
#2 and #3 most likely will continue to occur as I believe they are timing issues with the actual network process and the linux networking subsystem does not migrate the actual data/sockets and behave like the Symbian networking backend (which this feature was originally written for) to have seamless network transitions/migration.
The test app I wrote that downloads big file: /code.launchpad .net/~lorn- potter/ +git/test- servicenetwork
https:/
Of course, this runs from commandline so is uncontained.
Steps to reproduce: /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ landing- 060
Landing for testing:
https:/
* open system settings->update
* when there is a larger update available, start the download.
* turn off wifi or walk from wifi zone
Known issues:
1. Euronews, Engadget and Today scope to not ever see network
2. Occasionally update check will hang when changing network device(wifi -> 3g)
3. Occasionally update download will not resume properly when network change.
I am fairly certain that #1 can only be fixed by moving QtBearer plugin to connectivity-api, although I do not see any apparmor denials in the log, with this change it makes QNetworkRequest require a QNetworkSession, which in turn I believe fails as the known and unfixable QtNetwork network-manager backend issues with apparmor. I am assuming that scopes run in contained space, because other commandline based tests with QtNetworking access work, but Click apps that use QtNetworking fail similarly.
#2 and #3 most likely will continue to occur as I believe they are timing issues with the actual network process and the linux networking subsystem does not migrate the actual data/sockets and behave like the Symbian networking backend (which this feature was originally written for) to have seamless network transitions/ migration.