Thank you graphene developers!!!

remove special handling of the resolver activity ("Open with..." dialog) which was added to Android in order to support instant apps as preparation for our in-development App Communication Scopes feature

Does anyone know when the app scopes feature will probably be out?

    "improve isolation of the eSIM activation apps"

    At the convenience of one of the developers, may I ask someone to elaborate on this?

    • [deleted]

    • Post #5

    RRZishe Nobody knows. If i'd had to make a guess, probably about 7-20 releases away

      enable heap memory tagging for vendor processes by default, remove the user-facing toggle in the Settings and restrict toggling the value to debug builds

      I still get mte errors from proton VPN occasionally. I had to manually turn mte off for this app.

      Does this new update mean I will no longer be able to switch mte off?

      Has anyone else experienced these errors with pixel 8 and proton VPN?

        I am on stable and after this update now in the morning I already received two crashes below. The crashes are repeating and was not present prior the update.

        Vanadium

        type: crash
osVersion: google/panther/panther:14/AP1A.240405.002.B1/2024050300:user/release-keys
osVersion: google/panther/panther:13/TQ3A.230901.001/2023100300:user/release-keys
uid: 10092 (u:r:untrusted_app:s0:c92,c256,c512,c768)
cmdline: app.vanadium.browser:privileged_process0
processUptime: 8s

signal: 11 (SIGSEGV), code 1 (SEGV_MAPERR), faultAddr 0
cause: null pointer dereference
threadName: CrGpuMain

backtrace:
    /vendor/lib64/egl/libGLES_mali.so (gles_fb_is_frontbuffer+84, pc 7ad154)
    /vendor/lib64/egl/libGLES_mali.so (gles_fb_flush_if_required+76, pc 7ac81c)
    /vendor/lib64/egl/libGLES_mali.so (gles_fb_flush+28, pc 7a94dc)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 280e3dc)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 52a895c)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5a5bdec)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5a507a0)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 557a9b0)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5b2d2c8)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5b31a98)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5b35c6c)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 1fffe98)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 5580074)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 4595bdc)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 45a9c9c)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 455a644)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 45aa53c)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 457f150)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 6251f30)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 431cfc0)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (pc 431b3c4)
    /data/app/~~MD_akAL5BHqk43zmlbqhQg==/app.vanadium.trichromelibrary_609911532-4JC4EfEw7H1_o8X7qs81IQ==/base.apk!libmonochrome_64.so (Java_J_N_M1Y_1XVCN+136, pc 431bf64)
    /data/app/~~JEiBWEVXT_dxHVte6-PqDQ==/app.vanadium.browser-lpEKLaNyRTcHWI6bPykT3A==/oat/arm64/base.odex (art_jni_trampoline+116, pc 6255a4)
    /data/app/~~JEiBWEVXT_dxHVte6-PqDQ==/app.vanadium.browser-lpEKLaNyRTcHWI6bPykT3A==/oat/arm64/base.odex (Fu.run+3432, pc 5ba7c8)
    /system/framework/arm64/boot.oat (java.lang.Thread.run+80, pc 17ff10)
    /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+556, pc 21096c)
    /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+184, pc 279df8)
    /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithJValues<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, art::ArtMethod*, jvalue const*)+460, pc 621e1c)
    /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+1296, pc 66a6e0)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc c910c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 5c7b0)

        android.hardware.camera.provider@2.7-service-google
        When I started the camera from Telegram to take a photo. Killing apps or rebooting doesn't help. It crashes anyway.

        type: crash
osVersion: google/panther/panther:14/AP1A.240405.002.B1/2024050300:user/release-keys
uid: 1000 (u:r:hal_camera_default:s0)
cmdline: /apex/com.google.pixel.camera.hal/bin/hw/android.hardware.camera.provider@2.7-service-google
processUptime: 0s

abortMessage: Check failed: *physical_mode_info.virtual_output == virtual_mode_info.output (*physical_mode_info.virtual_output={image: {size: {width: 1720, height: 1224}, virtual_channel: 0, data_type: raw_10}, pd: N/A, embedded: N/A}, virtual_mode_info.output={image: {size: {width: 3440, height: 2000}, virtual_channel: 0, data_type: raw_10}, pd: N/A, embedded: N/A}) The virtual output of physical driver mismatches with virtual camera output

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: RunnerN:P-:A:1

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 64e84)
    /system/lib64/liblog.so (__android_log_default_aborter+12, pc 625c)
    /apex/com.android.vndk.v35/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352, pc 18fd0)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 84e7fc)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 52a04c)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 4a0d48)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 675420)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 44e8b8)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 6774e8)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 3e3ba8)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc dde348)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cf93c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc >!66730!<)

          Manky no, you will still be able to turn MTE on/off for 3rd party applications such as ProtonVPN, as normal. The change was regarding vendor/system processes only.

          By the way, regarding ProtonVPN, I found if you change the protocol to OpenVPN UDP, it will work just fine with MTE enabled. There seems to be an issue with their Wiregaurd implementation or something.

              Just updated and everything works fine. Thanks again to the GrapheneOS team!

              For some reason all my brave pwa's were removed from my launcher (lawnchair) after the update. The Firefox ones stayed. Just wanted to report.

              Huge thanks to the amazing graphene team for another great update!

                huberto will be released tomorrow most likely. They are usually released first monday of each month unless that monday is a holiday then it will be released the following day, after the release it will take a few days for GrapheneOS devs to port all the fixes and release a new update so next update will likely have the may patch fixes.

                  huberto It's usually like this. The GrapheneOS team publish a release full of features/patches/fixes very early in each month and then a few days later they publish a release with the monthly security patches. I think it's a clean way to do it, but I don't know the reasoning behind this release-pattern. Maybe the devs can explain a bit more?

                    other8026

                    JayJay
                    Last night while trying to watch a YouTube video in brave the page kept freezing had to keep bringing up the recent app screen to get it to unfreeze every few seconds . don't know if its brave or graphene .