AlmostTI crashing when loading ROM after March 2026 Android update

[Zan Hecht]

I have a Google Pixel 8 running the March 5, 2026 update to Android 16. After the most recent update, AlmostTI instantly crashes to the launcher when loading a ROM. If I clear cache and data or uninstall and reinstall from the Google Play Store it will work once, but when I stop the app and restart it, the crashes resume. I am using the same TI-84+SE ROM that I have been using successfully for years.

The crash trace from dumpsys dropbox is included below:

========================================
2026-03-11 00:33:19 data_app_crash (text, 2574 bytes)
SystemUptimeMs: 306058940
Process: com.fms.ati
PID: 21933
UID: 10721
Frozen: false
Flags: 0x2889be44
Package: com.fms.ati v3109 (3.1.9)
Foreground: Yes
Process-Runtime: 2257
Timestamp: 2026-03-11 00:33:19.758-0400
Build: google/shiba/shiba:16/CP1A.260305.018/14887507:user/release-keys
DefaultScreen-State: ON
Keyguard-Locked: false
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 6

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fms.ati/com.fms.emulib.ATIMainActivity}
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4519)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4723)
        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:224)
        at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:133)
        at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:103)
        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2987)
        at android.os.Handler.dispatchMessageImpl(Handler.java:142)
        at android.os.Handler.dispatchMessage(Handler.java:125)
        at android.os.Looper.loopOnce(Looper.java:269)
        at android.os.Looper.loop(Looper.java:367)
        at android.app.ActivityThread.main(ActivityThread.java:9333)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
Caused by: java.lang.RuntimeException: error:1e000042:Cipher functions:OPENSSL_internal:function should not have been called
        at com.android.org.conscrypt.NativeCrypto.EVP_CipherUpdate(Native Method)
        at com.android.org.conscrypt.OpenSSLEvpCipher.updateInternal(OpenSSLEvpCipher.java:129)
        at com.android.org.conscrypt.OpenSSLEvpCipher.engineDoFinal(OpenSSLEvpCipher.java:182)
        at javax.crypto.Cipher.doFinal(Cipher.java:2074)
        at j2.a.a(SourceFile:15)
        at j2.g.b(SourceFile:12)
        at j2.i.<init>(SourceFile:46)
        at com.fms.emulib.MainActivity.onCreate(SourceFile:237)
        at com.fms.emulib.ATIMainActivity.onCreate(SourceFile:1)
        at android.app.Activity.performCreate(Activity.java:9290)
        at android.app.Activity.performCreate(Activity.java:9268)
        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1543)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4503)
        ... 14 more  

[fms]

Aware of this. Working on a fix.

[Zach Whaley]

Having a similar issue with vgbanext. I was playing a rom last night and now when I go to open any rom app crashes immediately. Ive deleted and installed app a couple of times. I have a Samsung s22 on android 16. Game crashes even if I select start without using any file. Not sure if its related or not but since previous comment mentioned a known issue didnt want to spam threads. 

[fms]

To reiterate, this is an issue with Google breaking their own licensing check with Android 16 update. I am working on a fix.

[fms]

Please, update to version 3.1.11, released today. It should fix your problem.

On Wednesday, March 11, 2026 at 2:27:21 AM UTC-4 zhe...@gmail.com wrote:

[fms]

Please, update to version 3.1.11, released today. It should fix your problem.

On Wednesday, March 11, 2026 at 8:45:43 PM UTC-4 azwha...@gmail.com wrote: