Googling that error gives various possibilities: from running out of heap space due to large assets, to de-referencing a null pointer, to calling methods on the same object from different threads.
My gut feeling is that this has to do with multiple threads, i.e., in which thread is your Bluetooth code called, and is that thread the same as the UI thread?
I think more information is needed than a seg fault message, to localize the problem. Contextualizing the error could be very useful for readers who are smarter than I am. What do you mean by application output? Do you mean in a log file? Are you are logging problems comprehensively? The reliance on Q_ASSERT_X, which of course doesn't even apply in release mode, suggests you are not.The error that is given by the application output
By the way, on what devices and versions of Android has this been observed?
Bookmarks