An: Fabrice Mousset | GEOCEPT GmbH
> Cc: Qt Interest
> Betreff: Re: [Interest] Trouble with Android JNI and QEventLoop
>
> The JniHandler::stateChanged is called from Android/Java (or Kotlin) I
> guess?
> Can you try to emit a signal in JniHandler::stateChanged and call the
Van Daele
Gesendet: Montag, 13. Juli 2020 16:45
An: Fabrice Mousset | GEOCEPT GmbH
Cc: Qt Interest
Betreff: Re: [Interest] Trouble with Android JNI and QEventLoop
The JniHandler::stateChanged is called from Android/Java (or Kotlin) I guess?
Can you try to emit a signal in JniHandler::stateChan
NonRecursive", it will
> dead lock!
>
> Regards
>
> Fabrice
>
> Von: Marc Van Daele
> Gesendet: Montag, 13. Juli 2020 11:36
> An: Fabrice Mousset | GEOCEPT GmbH
> Cc: Qt Interest
> Betreff: Re: [Interest] Trouble with Android JNI and QEventLoop
>
>
will dead lock!
Regards
Fabrice
Von: Marc Van Daele
Gesendet: Montag, 13. Juli 2020 11:36
An: Fabrice Mousset | GEOCEPT GmbH
Cc: Qt Interest
Betreff: Re: [Interest] Trouble with Android JNI and QEventLoop
Can you also print the thread-pointer/id next to the name?
Maybe (just gue
Can you also print the thread-pointer/id next to the name?
Maybe (just guessing) one QtMainLoopThread is from the main app and the
other one is from the service?
You could add a QMutexLocker (https://doc.qt.io/qt-5/qmutexlocker.html) to
ensure that the calls are executed sequentially.
Kind Regards
Hi all,
First, I tried to send this mail to Android mailing list, but got an error
message as reply, so I try here. Sorry if I am wrong
I have a random issue with one of my Android service I've build with Qt 5.12.9.
I have centralized JNI interface in one C++ class, which is a singleton.
My serv
