[Interest] Android crashes on high-end devices (Pixel, S25)

Nuno Santos nuno.santos at imaginando.pt
Wed Mar 25 16:38:52 CET 2026 

Hi Ekke,

Thanks for your reply.

I was using Qt 6.10.2 but yesterday I’ve updated to Qt 6.11 to see if it would solve the problems I was having, but no.

These are my settings:

QT_ANDROID_MIN_SDK_VERSION 28
QT_ANDROID_TARGET_SDK_VERSION 36

None of the 5 devices I have crash. This only happens on users devices:

Happens mostly on Samsung S24/S25, and Android 16 but it also happens on other devices and Android versions.

I’m clueless and very frustrated. This is with DRC synthesizer:

https://play.google.com/store/apps/details?id=com.imaginando.drc

The stack trace is always this vague.

          Crashed: Thread: SIGABRT  0x0000000000000000
#00 pc 0x72fbc libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#01 pc 0x72f94 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#02 pc 0x5d6d8 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#03 pc 0x5e39c libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#04 pc 0x5e30c libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#05 pc 0x5e514 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#06 pc 0x5ff68 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#07 pc 0x42f54 boot-core-libart.oat (BuildId: afe0b8b9e6a8be64b5142541958971d77a196989)
#08 pc 0x2eb9d0 boot.oat (BuildId: 79e668f1b05f7c3627c7fe666bfd37c24afbc248)
#09 pc 0x13a4c8 boot.oat (BuildId: 79e668f1b05f7c3627c7fe666bfd37c24afbc248)
#10 pc 0x28474 boot-core-libart.oat (BuildId: afe0b8b9e6a8be64b5142541958971d77a196989)
#11 pc 0xc12ffc libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#12 pc 0xc14404 libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#13 pc 0x264cc boot-core-libart.oat (BuildId: afe0b8b9e6a8be64b5142541958971d77a196989)
#14 pc 0xc12ffc libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#15 pc 0xbf4d8 boot.oat (BuildId: 79e668f1b05f7c3627c7fe666bfd37c24afbc248)
#16 pc 0x361d94 libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#17 pc 0x28d808 libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#18 pc 0x48bb34 libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
#19 pc 0xcc0f8 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#20 pc 0x8428c libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#21 pc 0x113ffc libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#22 pc 0x767b0 libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#23 pc 0x8419c libc.so (BuildId: abcf83f14ae2c45a6d60fe61e32454a8)
#24 pc 0x1b5094 ld-android.so (BuildId: e02a4273a87802d1642be7f2538baee1)
#25 pc 0x1b5394 ld-android.so (BuildId: e02a4273a87802d1642be7f2538baee1)
#26 pc 0x48b5dc libart.so (BuildId: 31bc808ce39ae9de9b1ea203eb380b2f)
       
Best,

Nuno 

> On 24 Mar 2026, at 20:07, ekke <ekke at ekkes-corner.org> wrote:
> 
> Hi Nuno,
> my customers are using Pixel and S25 without problems at startup.
> What is your Qt version, Target API, and NDK version?
> 
> BTW: I noticed a Nullpointer at quitting some of my customer apps - but harmless—users don't notice anything. (Qt 6.10.2, Target API 36, NDK 27)
> Unfortunately not found a way to make it reproducable yet, but working on this. (Just transitioning all my apps to 6.10 and SafeArea-refactorings)
> ciao
> ekke
> W/default : java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.content.Context.getSystemService(java.lang.String)' on a null object reference
> W/default :     at org.qtproject.qt.android.networkinformation.QtAndroidNetworkInformation.getConnectivityManager(QtAndroidNetworkInformation.java:158)
> W/default :     at org.qtproject.qt.android.networkinformation.QtAndroidNetworkInformation.unregisterReceiver(QtAndroidNetworkInformation.java:151)
> W/default :     at org.qtproject.qt.android.QtNative.startQtApplication(Native Method)
> W/default :     at org.qtproject.qt.android.QtNative$$ExternalSyntheticLambda5.run(D8$$SyntheticClass:0)
> W/default :     at org.qtproject.qt.android.QtThread$1.run(QtThread.java:25)
> W/default :     at java.lang.Thread.run(Thread.java:1563)
> 
> Am 24.03.26 um 20:07 schrieb Nuno Santos via Interest:
>> Hi,
>> 
>> I'm in the middle of a crash-elimination effort across my Android apps and I've hit a wall with a specific class of crashes I can't seem to own. They happen at app startup, before my code is reached, and show up most on high-end devices like Pixel and Samsung S25.
>> 
>> Stacktraces are always very similar (example below). My gut says it's something at the native/loader level but I'm not sure where to dig.
>> 
>> Anyone dealt with something like this? How did you track it down?
>> 
>> Thanks,
>> 
>> Nuno
>> 
>> 
>>           Crashed: Thread: SIGABRT  0x0000000000000000
>> #00 pc 0x7137c libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #01 pc 0x71354 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #02 pc 0x5d26c libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #03 pc 0x5dcbc libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #04 pc 0x5dc30 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #05 pc 0x5de18 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #06 pc 0x5f7d0 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #07 pc 0x119170 libandroid_runtime.so (BuildId: ce43a883b125c777ef749883d69eb39e)
>> #08 pc 0x72ab35d4
>> #09 pc 0x2ab6d4 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #10 pc 0x7286d480
>> #11 pc 0x7286d79c
>> #12 pc 0x72685d58
>> #13 pc 0x7286d924
>> #14 pc 0x7286cf90
>> #15 pc 0xc0f07c libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #16 pc 0x726215f0
>> #17 pc 0xc0dffc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #18 pc 0x2aaf94 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #19 pc 0x2708ec libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #20 pc 0xc0d3bc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #21 pc 0x4bdfe0 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #22 pc 0xc0dffc libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #23 pc 0x4bdb30 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>> #24 pc 0x10bffc libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #25 pc 0x82740 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #26 pc 0x74b98 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #27 pc 0x82684 libc.so (BuildId: 61a049a7ad18156ebc52d8d483539df9)
>> #28 pc 0x18d094 ld-android.so (BuildId: 44249f662570b6c2670db1a98725cc14)
>> #29 pc 0x18d394 ld-android.so (BuildId: 44249f662570b6c2670db1a98725cc14)
>> #30 pc 0x4bdb24 libart.so (BuildId: a1fcb66a9fb3fa9071e8a42dcf9cd5ea)
>>         
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org <mailto:Interest at qt-project.org>
>> https://lists.qt-project.org/listinfo/interest
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20260325/993880c7/attachment.htm>

More information about the Interest mailing list