• General
  • Thread for discussing 3rd party app compatibility.

Hey ! Do you plan adding support for Digital Wellbeing app ? That would be really cool ^^

    Hey all,

    Love GrapheneOS, and haven't had a single issue or bug, until I tried to play a game I love, Mahjong Soul, on a separate profile (doesn't work in the mail profile either).

    The app installs fine, I've done uninstalls and reinstalls, and granted it all the permissions I could, but every time I load it, the app crashes in seconds.

    Full crash log below, any ideas on if I can fix it? Or should I submit an issue on GitHub?

    type: crash
    osVersion: google/raven/raven:12/SQ3A.220705.004/2022080900:user/release-keys
    package: com.YoStarEN.MahjongSoul:114
    process: com.YoStarEN.MahjongSoul
    
    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version     : 2020.3.13f1
    Device model      : Google Pixel 6 Pro
    Device fingerprint: google/raven/raven:12/SQ3A.220705.004/2022080900:user/release-keys
    Build Type        : Release
    Scripting Backend : IL2CPP
    ABI               : arm64-v8a
    Strip Engine Code : true
    
    Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2020.3.13f1 (71691879b7f5)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
    Build fingerprint: 'google/raven/raven:12/SQ3A.220705.004/2022080900:user/release-keys'
    Revision: 'MP1.0'
    ABI: 'arm64'
    Timestamp: 2022-08-15 16:39:45-0700
    pid: 7683, tid: 7735, name: UnityMain  >>> com.YoStarEN.MahjongSoul <<<
    uid: 10170
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    Cause: null pointer dereference
        x0  0000000000000000  x1  0000000000001000  x2  0000000000000001  x3  0000000000000004
        x4  0000000000000255  x5  000000009fac4a5c  x6  000000006b206574  x7  0000000042a70797
        x8  0000ce1df00a9000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000001
        x12 0000000000000020  x13 0000000000020657  x14 0000000000022202  x15 0000000000020200
        x16 0000ce50d8f5d078  x17 0000ce50d8f50284  x18 0000000000000001  x19 0000ce1df00a86b8
        x20 0000000000000000  x21 0000ce1df00a87b8  x22 0000000000001000  x23 0000000000000eb5
        x24 0000000000012a98  x25 0000ce50d8f60440  x26 0000000000000c71  x27 0000ce1deea5324c
        x28 0000ce50d8f60000  x29 0000ce1df38fe780
        sp  0000ce1df38fe700  lr  0000ce1def0b09bc  pc  0000ce1def0b09bc
    
    backtrace:
          #00 pc 00000000007b69bc  /data/app/~~8bU0QOydSO2U_eZ70ellBQ==/com.YoStarEN.MahjongSoul-3bQZDp7pao6pgTR698R5ig==/lib/arm64/libunity.so (BuildId: 34a2cbe2f3e9764f23cc9718e78528f3886a8ae8)
          #01 pc 0000000000159268  /data/app/~~8bU0QOydSO2U_eZ70ellBQ==/com.YoStarEN.MahjongSoul-3bQZDp7pao6pgTR698R5ig==/lib/arm64/libunity.so (BuildId: 34a2cbe2f3e9764f23cc9718e78528f3886a8ae8)
          #02 pc 00000000000b15e8  /apex/com.android.runtime/lib64/bionic/libc.so (__cxa_finalize+288) (BuildId: 761d634420410980165d18a838ce8c70)
          #03 pc 00000000000a2e90  /apex/com.android.runtime/lib64/bionic/libc.so (exit+24) (BuildId: 761d634420410980165d18a838ce8c70)
          #04 pc 0000000000030b84  /data/app/~~8bU0QOydSO2U_eZ70ellBQ==/com.YoStarEN.MahjongSoul-3bQZDp7pao6pgTR698R5ig==/lib/arm64/libtolua.so (BuildId: ab8f2cce87ece7d68f4f7ffb621a06afc3491627)
    
    	at libunity.0x7b69bc(Native Method)
    	at libunity.0x159268(Native Method)
    	at libc.__cxa_finalize(__cxa_finalize:288)
    	at libc.exit(exit:24)
    	at libtolua.0x30b84(Native Method)

    Thank you!

    [deleted] What about the other Duo, Google's video call app (that's getting merged with Meet). Does that work on GrapheneOS?

      Has anyone been able to use Airlock 2FA (banking authentication app) on GrapheneOS?
      The app said it needed Google Play Services.
      I enabled that (also had to install & open the Play Store app) which made the error go away.

      But enrollment still isn't working.
      The QR code from my e-banking website is simply ignored / not recognized by the app.
      No error messages, it just acts as though the QR code is not on the screen.

      The GrapheneOS QR code scanner scans the QR code just fine.
      Enrollment on Android works fine.

      Any other Graphene-specific suggestions?
      Any special permissions, etc I should be aware of?

      Links:

      Thanks!

      sapphicvixie can you do something for me?

      Have you got Lastpass running alongside sandboxed Play Services in your owner profile?

      If so go to SETTINGS>SECURITY>Enable secure app spawning and toggle it OFF.
      Reboot
      Try to open and login to Lastpass again and let me know if it crashes again.

      Hi @Tilde, I have a similar issue with Imou life APP. How I can get the log? Do you have solved it?

      Thanks!

        Pixel 6 - Pixel Recorder app

        Transcription works on Android 13, but only with English. All the other language options are gone, and when I first launch the app, it asks me to enable an app, but tapping on the settings option in the popup dialogue leads me nowhere (launches the settings app then closes it immediately). Anybody know what I'm missing? This is still an improvement over 12, where transcription didn't work, period.

          omori This worked. Thanks! For some reason languages other than English aren't showing up for me atm.

          Edit: They loaded after a while.

          Edit 2: Now transcription isn't working at all again :(
          I'll probably have to leave it as it was originally.

          Tilde Thanks for the update!

          I will keep an eye on that thread.

          Thanks!

          sifuhall Same here, I've been using the web portal, but I hate that the only 2FA option they offer is SMS/Voice call, unless you have the app. Really wish they would offer TOTP. Hopefully we can get a fix for this from one side or the other

          Has anyone been able to activate/login to Viber on Graphene OS (Android 13)? It worked fine on Graphene OS Android 12, but I keep getting "Activation Failure" message. Viber staff says they aren't receiving any activation request for my account.

          With the new update, 2022083000, I was able to get BimmerApp working by disabling hardened Molloc in the settings.

          It now downloads the data properly instead of simply failing. I tried toggling to compare and this is the only setting making a difference.

          Will test more later.

            Gira that is the setting that will affect it as the hardening and improved security of GOS has demonstrated BimmerApp to have a latent memory corruption bug that the developer hasn't resolved, the only way to get these apps working that need this function is to disable the hardening.

            The project added the feature to ensure that people could have the option to remain no compromise and find alternate apps or for those that don't wish to or can't for whatever reason they can make the informed decision to disable it.

            GrapheneOS is for everyone™ after all ;)

            I have an issue on GOS with a few battery alert apps that tell me if I'm over a certain % of charge. I use this so that my battery stays in better health for longer.

            I have found that regardless of the app I use (BatteryBot, Battery Alarm) they refuse to start up automatically when the phone boots up. I need to manually open them before they start to alert me.

            This did not happen on stock, and understandably, on GOS (even the stable branch) I need to often reboot my phone.

            Would love to hear any workarounds to get this working as intended after a reboot. I did not find enabling more permissions helped, but maybe I missed something.

            Thank you!

              thrik that really isn't necessary: Battery Management Advice

              Official Advice: https://support.google.com/pixelphone/answer/6090612

              Realistically using the standard charger to ensure correct voltage delivery at appropriate percentage and keeping the phone away from heat sources means you don't need to worry about the 80% mark and it isn't relevant to modern devices with onboard controllers with charge bypass.

              If you wish to discard the advice then you need to ensure the apps you mentioned support direct boot:
              https://developer.android.com/training/articles/direct-boot