There is a Bug filed called "Can't debug Android App": https://bugreports.qt.io/browse/QTCREATORBUG-20379 In one of the comments someone mentions that you'll need to manually update the AndroidManifest.xml file to add the attribute android:debuggable="true" To the Application tag. This gets the Application deployed and starts it up. But looks like the debugger still can't attach. And it also looks like the Manifest gets autogenerated and needs to be updated each time you try to debug. Hopefully there is something one can set to adjust the automatic generation so you don't have to edit that manifest each time you need to deploy.

Found it: https://github.com/qt/qtbase/blob/5.12/src/corelib/global/qlogging.cpp Specifically, I needed to set application name in QCoreApplication.

Hi and welcome to devnet, Did you try with QCamera and it's friendly classes ?

@p3c0 Yes, thanks. I found this example. And he is works. http://doc.qt.io/qt-5/qtwebview-minibrowser-example.html And I found - Webengine is not supported on android and not with MinGW either.

@mcosta W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_client_method W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_server_method W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_server_method W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve SSL_select_next_proto W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb W/libPmps.so(10267): (null):0 ((null)): qt.network.ssl: QSslSocket: cannot resolve SSL_get0_next_proto_negotiated

yes the input isn't blocked , it not validated!

If you are building Qt for Windows, it won't link to the Android runtime