v1.4.3

Finding out why the app cannot connect

On some custom kernels and firmware the app cannot connect at all, and until now nothing said why. Tick Verbose helper log before connecting, and the helper now scans the whole QRTR bus and prints what it finds under "Helper output":

• one line per processor on the bus, listing the services it offers — the familiar ones by name (2 DMS, 14 RMTFS, 4097 DIAG…), the rest as numbers;
• a verdict at the end: the modem publishes DIAG and the helper has something to talk to; only this CPU publishes it; nobody does; or the bus is empty.

If the verdict says there is no DIAG, the helper simply has nothing to connect to on that firmware — it is not a bug in the app. That output is also the useful thing to paste into a bug report.

A clearer error on kernels without QRTR

A kernel built without QRTR used to fail with a bare socket(AF_QIPCRTR) failed: Address family not supported by protocol. It now says plainly that the kernel has no QRTR support, so there is no bus to reach the modem through. This one shows even without the verbose log.

Nothing changes for devices that already connect: without the verbose tick the helper behaves exactly as before.

The bundled helper is 1.4.3, matching the app.