• mrxx0

    • Post #2
    • Edited

    Some things to test for users in alpha channel since kernel has MTE enabled (from GrapheneOS account in Alpha/Beta testing channel on Matrix) :

    • Bluetooth
    • NFC
    • DisplayPort alternate mode,
    • Wi-Fi Direct
    • any other niche hardware functionality
    • BLE Audio
    • USB peripherals (USB-C audio, mouse, keyboard, joystick)
    • Controller like xbox controller etc
    • Drives with exFAT and Fat32
    • Stress test on GPU, disk etc
    • Weird games, emulators

    Edit : If you're on 8th or 9th gen Pixels and testing this release, please enable system crash notifications in Settings > Security & privacy > More security & privacy > Notify about system process crashes so you get kernel crash notifications after a kernel panic reboot in case hardware memory tagging finds any kernel bugs.

    • KK8y

      • Post #3
      • Edited

      Thank you. Do we need to restart our phones while connected to the internet for this to update automatically or need to click on a certain link?

        K8y
        Unless you have elected to receive Alpha channel releases then there isn't anything yo receive yet.

        Alpha: announced on the forums, released only to those who elect to receive it.
        Beta: usually released 12 to 24 hours after Alpha to those who elect to receive it assuming no detected issues with the Alpha release.
        Stable: Pushed to everyone with GOS after the developers are convinced that no issues with the release are found, usually 12 to 24 house after Beta

            two questions:

            1. what does the above "MTE" stands for ?

            as I'm relative new with GOS:
            I see on an google 8 (Install.: I followed the readme here, and esp. the last step too) that Google complains something "another OS is booting or something like that. It boots though.

            1. is that usually ?
            • yore replied to this.

              • yore

                • Post #9
                • Edited

                JoeAverage64 what does the above "MTE" stands for ?

                Memory Tagging Extension

                See:
                https://source.android.com/docs/security/test/memory-safety/arm-mte
                https://community.arm.com/arm-community-blogs/b/architectures-and-processors-blog/posts/enhancing-memory-safety

                JoeAverage64 Google complains something "another OS is booting or something like that. It boots though.

                A yellow boot warning is normal when using any operating system other than the stock Pixel OS. This is expected behaviour.

                See: https://source.android.com/docs/security/features/verifiedboot/boot-flow

                    JollyRancher Beta: usually released 12 to 24 hours after Alpha

                    Alpha tends to be less time than betta can be just a couple of hours. But time in alpha and beta can have wide variation. Much depends on what has been changed and the perceived possibility of serious issues.

                      Tbh, I thought hardware KASAN was already enabled... 🤔

                        Just to report

                        Device: Pixel 8
                        All my USB-C peripherals work including USB-C headphones, Ex FAT flash drive and Ethernet adapter.
                        I'm unable to make seedvault backups to my flash drive, no crash notification, it says "attempted to access a cursor after it has been closed", AFAIK it may just be a seedvault thing. Will try with another flash drive tomorrow.

                          • VAULT

                            • Post #15
                            • Edited

                            DESKTOP BOOKMARKS LOST -
                            I can confirm for the first time, imeadiately on restart after this stable update, all my Desktop Bookmarks from Vanadium were wiped from their folders. Only using primary user.
                            VAULT - P9P XL

                              Since this, update, fingerprints have been broken for me whenever I switch users on my Pixel 8a. Previously, going to another user and then returning to the main user would require me to use the pin code once to unlock fingerprint unlock on later attempts.

                              Now fingerprint unlock is completely broken upon switching users. If I switch out of the main user and switch back, the fingerprint unlock stops working entirely. In order to enable fingerprint unlock again, I have to go to the lock scren settings and toggle the option to use fingerprint for screen unlock off and on again.

                              5 days later

                              Since the last update, I've been unable to configure the eSIM, which is in "emergency call only" mode, so I can't make or receive calls, and the same goes for SMS, even if I delete and reconfigure the APN.
                              I installed the same eSIM on my wife's iPhone to test it out and it works perfectly well for calls and texts.

                                UWB still broken on Pixel 9Pro XL.

                                VAULT It's a known upstream bug in Android causing shortcuts to be lost in certain edge cases. We fixed a similar upstream issue for widgets recently but not shortcuts yet.

                                  ScarletKing07 carlnickel We know Seedvault doesn't work well. It's not GrapheneOS-specific, it doesn't work well anywhere and keeps having major regressions. It's clear that it's never going to be a good app and needs to be replaced.

                                      GrapheneOS So where is the problem coming from? I've reset the mobile network settings and even done a factory reset and the problem persists.

                                      What can/should I do?