Comment 80 for bug 1480877

The generic bearer plugin is brain dead, especially when it comes to knowing when it's actually connected or not.

Although connectivity-api also suffers from blocking dbus calls, I feel the connectivity-api backend is the right way to go for bearer & QNAM right now. In the least, it will lessen the stress on dbus, as ideally, there should be only one Qt entity getting network-manager properties through dbus on a system. At least the blocking calls will be off loaded from everybody and their brother that happens to use QNAM knowingly or blindly.

I am not yet familiar with who originally starts connectivity-api and when things start accessing QNAM at startup, though.