@Michi I guess I look at this from NetworkManager's point of view. Your either "connected" or you're not... The network indicator reflects this, it shows the mobile data technology if connected to the mobile operator. If WiFi is enabled, it works like the desktop. You can easily see the state of both WiFi and the mobile data connection by running the command 'nmcli d'.
Yea, the QNetworkAccessManager documentation isn't super clear. It also looks like there's a lot of control provided over network configuration, which may not actually work correctly on our platform. With that said, it looks to me like "unknown" is the default accessible state, until the first request is created. From the thread you posted on qtcentre.org in comment #7, it appears that the accessible state can be primed: "QNetworkAccessManager::networkAccessible is not explicitly set when the QNetworkAccessManager is created. It is only set after the network session is initialized. The session is initialized automatically when you make a network request or you can initialize it before hand with QNetworkAccessManager::setConfiguration() or the QNetworkConfigurationManager::NetworkSessionRequired flag is set." It also includes sample code to do this: QNetworkAccessManager* mNetworkAccessManager = new QNetworkAccessManager(); QNetworkConfigurationManager manager; mNetworkAccessManager->setConfiguration(manager.defaultConfiguration()); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1502282 Title: "unknown" connectivity status problematic Status in The Savilerow project: New Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: metadata provides a scope a network connectivity status enum with three possible states: * connected * disconnected * unknown Sometimes unknown is the current state. This is quite problematic because in general a scopes that queries the network (that is, most scopes) need to know whether there is network or is not network and depending on this either make the network queries or display an error message. A status of unknown connectivity leaves the scope with no valid option: * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily * the scope could assume the network is up, but this is dangerous if it is not up To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp