Strange behaviour of QMaemoInternetConnectivity

[Sasler]

I got the following code in my app:

    if (QMaemoInternetConnectivity::isConnected()) {
        getData();
    } else {
        QSystemDeviceInfo* deviceInfo = new QSystemDeviceInfo();
        QSystemDeviceInfo::Profile profile = deviceInfo->currentProfile();
        if (profile == QSystemDeviceInfo::OfflineProfile) {
            QMaemo5InformationBox::information(this, "The device is in Offline mode.", 10000);
        } else {
            QMaemoInternetConnectivity::connectionRequest();
        }
    }

The problem with this is that if I lunch the app in WLAN and then later change it to 3G, it will not see that it's connected and a connection dialogue appears. The same is true visa-versa, that is if it's 3G and I change it to WLAN.

Also, if the device is set to automatically connect to 3G and no connection is present when launching the app, it will connect to WLAN.

Has someone else noticed this strange behaviour with QMaemoInternetConnectivity? Should I do it differently?

Cheers

[divanov]

I think you should be doing something like this

QSystemNetworkInfo* networkInfo = new QSystemNetworkInfo();
if (networkInfo->networkStatus(QSystemNetworkInfo::EthernetMode) != QSystemNetworkInfo::Connected) {
    QMaemoInternetConnectivity::connectionRequest();
}

[Sasler]

I think you should be doing something like this

QSystemNetworkInfo* networkInfo = new QSystemNetworkInfo();
if (networkInfo->networkStatus(QSystemNetworkInfo::EthernetMode) != QSystemNetworkInfo::Connected) {
    QMaemoInternetConnectivity::connectionRequest();
}

Is that QSystemNetworkInfo::EthernetMode active whenever there is internet connection, no matter what connection type is used?

[Sasler]

Is that QSystemNetworkInfo::EthernetMode active whenever there is internet connection, no matter what connection type is used?

I did some testing and it seems that only the WlanMode reoprts the connection status. But if I'm using 3G connection, networkStatus doesn't give me any indications whether is connected or not. All I get is HomeNetwork and that comes even when it's not connected to the internet.

[divanov]

Yes, it looks like if you have mobile data connection it cannot be detected from QSystemNetworkInfo.
It's worth to be reported
http://bugreports.qt.nokia.com/secur...e!default.jspa

BTW, did you check Qt Mobility Bearer Management API?
http://doc.qt.nokia.com/qtmobility-1...ion.html#state

[Sasler]

Yes, it looks like if you have mobile data connection it cannot be detected from QSystemNetworkInfo.
It's worth to be reported
http://bugreports.qt.nokia.com/secur...e!default.jspa

BTW, did you check Qt Mobility Bearer Management API?
http://doc.qt.nokia.com/qtmobility-1...ion.html#state

OK, i made a bug report here.

I tried to use that Qt Mobility Bearer Managemen but was unsuccessful. Is there any simple example code I could see? All I need is to find out whether there is a connection or not.

[divanov]

There is some example in Wiki
http://wiki.forum.nokia.com/index.ph..._Mobility_APIs
http://doc.qt.nokia.com/qtmobility-1....html#isOnline

[Sasler]

But isn't that your goal?

Yes, but I haven't found a reliable way. I made bug report of QMaemoInternetConnectivity too. But I'm starting to wonder if the bug is in Maemo PR1.2 instead of Qt 4.6.2, because I got the same results with this method.

[divanov]

QMaemoInternetConnectivity is obsolete API and should not be used. "This method" is also Qt.
You can see all active interfaces with /sbin/ifconfig utility on Linux.

[Sasler]

QMaemoInternetConnectivity is obsolete API and should not be used. "This method" is also Qt.
You can see all active interfaces with /sbin/ifconfig utility on Linux.

So what should be used to request connection if one is not present?

[divanov]

Qt Mobility Bearer Management.

[Sasler]

Qt Mobility Bearer Management.

Yeah, this seems to work fine:

            QNetworkConfigurationManager mgr;
            QNetworkConfiguration ap = mgr.defaultConfiguration();
            QNetworkSession* session = new QNetworkSession(ap);
            session->open();