App does not open

App version: v3.1.2 from F-droid

Android version: Android 14. CalyxOS v5.0.3

Device model: Pixel 6 Pro

Expected behaviour: Tapping the app icon opens the app.

Current behaviour: Tapping tbe app icon opens the app briefly (a fraction of a second) then minimizes and is unable to stay open.

First occurred: This morning, 11/8/23

Steps to reproduce:

  1. Tap icon on screen of phone
  2. Then the app looks like it’s opening on full-screen
  3. Then app minimizes immediately

Environment: Auto download certain subscriptions. Auto update from F-droid.


[if available]

We need some logs, otherwise we can’t find out what causes this. Given that you are running a custom rom, I guess you know adb logcat?

Ok, I will upload today when I can. Thank you!

I am a bit of a noob…I’ve never shared code before. Do I just copy and paste the text code right here in the text box?

The logs could contain sensitive information (especially if it’s the logs from the entire phone). I suggest to only send the few new lines that appear when AntennaPod crashes on your device. However, if you want, you can also send them to me via email if you don’t want to post them publicly (info@<my username>.com)

I looked at your logs, the following is the interesting part for AntennaPod:

Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 29225 (noeh.antennapod), pid 29225 (noeh.antennapod)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
CalyxOS version: '5.0.3'
Build incremental version: '23500030'
Build fingerprint: 'google/raven/raven:14/UP1A.231005.007/10754064:user/release-keys'
Revision: 'MP1.0'
ABI: 'arm64'
Timestamp: 2023-11-08 10:22:40.598741990-0700
Process uptime: 1s
Cmdline: de.danoeh.antennapod
pid: 29225, tid: 29225, name: noeh.antennapod  >>> de.danoeh.antennapod <<<
uid: 10172
tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'JNI FatalError called: RegisterNatives failed for 'org/conscrypt/NativeCrypto'; aborting...'
    x0  0000000000000000  x1  0000000000007229  x2  0000000000000006  x3  0000007fd1076320
    x4  0000000000005005  x5  0000000000005005  x6  0000000000005005  x7  7f7f7f7f7f7f7f7f
    x8  00000000000000f0  x9  000000767fab7050  x10 0000000000000001  x11 000000767fb00b60
    x12 00000000000016dc  x13 0000000000000001  x14 0000000000003003  x15 00000054dbf518f0
    x16 000000767fb6ccf8  x17 000000767fb49470  x18 00000076a2058000  x19 0000000000007229
    x20 0000000000007229  x21 00000000ffffffff  x22 00000076a1946000  x23 00000073e5c16000
    x24 00000076a1946000  x25 00000073668b3a5c  x26 b400007438afa230  x27 b4000075a8ae9130
    x28 b4000075a8ae9130  x29 0000007fd10763a0
    lr  000000767faf1178  sp  0000007fd1076300  pc  000000767faf11a4  pst 0000000000001000
46 total frames
      #00 pc 000000000005c1a4  /apex/ (abort+164) (BuildId: 4039ab9698000909cdb5ea7ba1fcc536)
      #01 pc 000000000064ac20  /apex/ (art::Runtime::Abort(char const*)+1456) (BuildId: 54e38742aaf726fac6ccf8c960f0860e)
      #02 pc 0000000000038730  /apex/ (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: 9f4a6d4a184c4c3ea2cb9cb643ad81c0)
      #03 pc 0000000000037c30  /apex/ (android::base::LogMessage::~LogMessage()+352) (BuildId: 9f4a6d4a184c4c3ea2cb9cb643ad81c0)
      #04 pc 0000000000472a54  /apex/ (art::JNI<false>::FatalError(_JNIEnv*, char const*)+196) (BuildId: 54e38742aaf726fac6ccf8c960f0860e)
      #05 pc 000000000006a748  /data/app/~~j1wWgjTUgbm5n6c62ErwSA==/de.danoeh.antennapod-00eCPVxtbi3VMioUnFTAkA==/lib/arm64/ (BuildId: 352afc779189eb554333530d462aaa54aaafe1ec)
      #06 pc 0000000000069ad4  /data/app/~~j1wWgjTUgbm5n6c62ErwSA==/de.danoeh.antennapod-00eCPVxtbi3VMioUnFTAkA==/lib/arm64/ (JNI_OnLoad+120) (BuildId: 352afc779189eb554333530d462aaa54aaafe1ec)
      #07 pc 0000000000463a00  /apex/ (art::JavaVMExt::LoadNativeLibrary(_JNIEnv*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, _jobject*, _jclass*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*)+3264) (BuildId: 54e38742aaf726fac6ccf8c960f0860e)
      #08 pc 000000000000535c  /apex/ (JVM_NativeLoad+412) (BuildId: 8f90f96c2ba1b44cb48acfb731dc01ff)
      #09 pc 000000000009b93c  /system/framework/arm64/boot.oat (art_jni_trampoline+156) (BuildId: 62fc68c27e58cc4127778fe0fd1815427d050b5a)
      #10 pc 00000000000ab648  /system/framework/arm64/boot.oat (java.lang.Runtime.loadLibrary0+328) (BuildId: 62fc68c27e58cc4127778fe0fd1815427d050b5a)
      #11 pc 00000000000ac840  /system/framework/arm64/boot.oat (java.lang.Runtime.loadLibrary0+368) (BuildId: 62fc68c27e58cc4127778fe0fd1815427d050b5a)
      #12 pc 00000000004a1138  /data/app/~~j1wWgjTUgbm5n6c62ErwSA==/de.danoeh.antennapod-00eCPVxtbi3VMioUnFTAkA==/oat/arm64/base.odex (org.conscrypt.NativeCryptoJni.init+632)
      #13 pc 0000000000209418  /apex/ (nterp_helper+152) (BuildId: 54e38742aaf726fac6ccf8c960f0860e)
      #14 pc 000000000073ee4a  /data/app/~~j1wWgjTUgbm5n6c62ErwSA==/de.danoeh.antennapod-00eCPVxtbi3VMioUnFTAkA==/oat/arm64/base.vdex (org.conscrypt.NativeCrypto.<clinit>+0)

This seems to crash in a system component outside of AntennaPod. Did you recently download an update of your custom ROM?

I see. Yes, there was a recent update to CalyxOS (maybe I should contact them?). Here is their most recent changelog:

CalyxOS 5.0.3

  • Android 14
  • Chromium 119.0.6045.66 (latest stable)


  • Work profiles are now actually “turned off” instead of being “paused”. Restores Android 13 behavior
  • Custom status bar icons are back
  • Custom font selection is back
  • Single-touch wakeup on rear & front fingerprint scanner.
  • Bluetooth airplane mode crash has been fixed.

Known issues

  • F-Droid will ask for unknown sources to install/update certain apps. Fixed with F-Droid 1.18.0, kindly update.

It works again. Not sure what happened or why it kept crashing right after opening it. But it seems like it’s back to normal now. I didn’t do anything, just used my phone as normal, I charged my phone, but I didn’t even reboot it. Weird. Well, thank you.


This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.