Qt Bearer Management
summary
Qt Bearer Management exposes concrete APIs to control system connectivity: one-line online check returns carrier-ready state, you can update and list configurations, open/close NetworkSession to bring interfaces up or stop them (requires platform control capability), and handle handover either with force roaming vs application-level roaming where the app can test and accept a proposed config. Backends include ConnMan, NetworkManager, ICD and Native Wi‑Fi; limitation: cannot create and store new access points and some actions need elevated platform permissions. Demo shows online detection and config listing working on N9.
AI-written summary · about
chapters (17)
- 0:00Introduction to Qt Bearer
- 1:11About the speaker
- 2:37Why use Bearer API
- 4:29Main use cases explained
- 6:38Bearer API classes overview
- 8:05Code snippets for use cases
- 10:09Starting and stopping interfaces
- 12:58Managing network sessions
- 14:08Application-level roaming
- 17:25Platform capabilities comparison
- 21:06Bearer API vs Network Access Manager
- 24:45Migration to Qt 5 Bearer API
- 26:13Qt Quick integration
- 29:12Live Q&A session
- 32:24Live demo of Bearer API
- 37:55Real-world usage example
- 38:15Contact and resources
related talks
32mNetwork programmability and telecommunication APIs
33mQtinUse - Networked, GUI-Driven Automation
56mThe Qt Networking Stack
26m Basic Networking with Qt
30mBuild network-aware mobile apps
30mPQC in Mobile Networks: Insights from the GSMA Task Force
24mHow you can develop a new breed of applications
54mExposing device features on 4G & 5G networks