The logs you sent may point to a ForegroundService issue which has a new behaviour requirement in Android 15, but could also just be info, and not causing the actual segfault.
https://developer.android.com/about/versions/15/behavior-changes-15
Send the debug logs for a fresh app with just a button, would be interesting to see, ensure no permissions are set on the new app too, see if the segfault occurs with no permissions set and just a basic component.
FYI : I have created a new Application an empty form with just a button on it and I have the same Behavior on android 15 (instant crash on launch) --> on Android 14 everything works fine.
The Apllication Name is : applamwproject2 (new application with just a button )
The chipset is set to: AARCH64
the App is running fine on Android 14
I attach the
logcat on file messages.txt.zip
however the source of problem is the same.
Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007692482ff8 in tid 24959 (applamwproject2), pid 24959 (applamwproject2)and it happens when libcontrols.so is attempt to be loaded.
10-13 03:27:42.553 24986 24986 F DEBUG : backtrace:
10-13 03:27:42.553 24986 24986 F DEBUG : #00 pc 0000000000046074 /data/app/~~t6uZCHCqPgY4p5aAnb2sOA==/org.lamw.applamwproject2-WoN_zDsgG-BcA_4ySNLQeg==/lib/arm64/libcontrols.so (BuildId: d18c6778ab2cf0befb00244a902b053646432242) FYI: A "Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)" error is a segmentation fault that means a program is trying to access a memory location it doesn't have permission to access. This often happens due to a bug in the code, such as trying to access an invalid memory address, a corrupted pointer, or a data type issue, but it can also be related to hardware memory problems or specific system configurations.
If I use a non NDK app from Android Studio it runs fine on Android 15, for this reason I suspect the NDK and possibly the Gradle version of LAMW.