Thank you for providing once again a fantastic update.

  • provide standard haptic feedback for fingerprint authentication success when 2nd factor PIN is enabled

Although I understand the reasoning for keeping everything close the standard I actually liked the haptic-less fingerprint authentication. Is this a setting which the user can personalize?

    • fid02

      • Post #4

      I disabled vibration and haptics as a whole when I discovered I could do it from Settings > Accessibility > Vibration and haptics. I actually prefer it this way!

        fid02 I prefer the haptic vibrations but thanks for sharing the method for disabling it, I'd never tested it before.

          Thx again for the fast update! :)
          (Will make an Donation, for all the good and hard work...)

          I was surprised that there was no app optimization after the update and the first unlock. New?

            Everything is working well on my Pixel 8, including WiFi, Bluetooth audio, hotspot, private space, multiple users, etc.

            Thanks for the super quick updates!

            Contacts: improve dark theme contrast for empty contacts list background

            Thank you for that. I've been unable to see those empty fields forever.

            The update hasn't arrived yet on my Pixel 8a. How long does it take usually? (This is my first update experience – using GOS for two weeks now)

              inoigjig That's because releases go through alpha to beta to stable, it has reached beta already so you'll get it soon!

                Beerman I was surprised that there was no app optimization after the update and the first unlock. New?

                Yes, that was already new in the 20241230 release. It happens in the background while the boot animation is running.

                    DeletedUser87

                    But that "only" concerned the first optimization round, before unlocking.
                    Then there was the second round, after unlocking, which was still there after the 20241230 update. But this did not happen after today's update.

                      Awesome! I can confirm that my Pixel 6a, Pixel 7 and Pixel Tablet are working fine under 2025010700.

                      I'm very pleased that when first rebooting into the new update, apps don't need to optimize in the background while the device is already in use.
                      In the last update 20241230 the apps had to be restarted after the optimization process, which led to multiple apps not properly restarting their background process and thus e.g. not receiving notifications since the background push service was not running. But that's fixed in this new update since apps don't need to be optimized and restarted after the boot already finished. Thanks!

                      It is strange that apps do not compile anymore, compilation is part of the security process right ?
                      For me the part of the update where apps are being compiled was expected and now for me it is perceived like an anomaly

                        • Rryrona

                          • Post #17
                          • Edited

                          NetRunner88 It is strange that apps do not compile anymore, compilation is part of the security process right ?
                          For me the part of the update where apps are being compiled was expected and now for me it is perceived like an anomaly

                          Many including me noticed the absence of app optimization after reboot yesterday, and brought it up in the alpha/beta channel. Apparently the optimization is automatically skipped whenever possible, when there are no relevant changes to the system that would require a recompile. This release didn't need any recompile. This is what the official GrapheneOS account wrote:

                          <grapheneos:discord> it's quite possible this update just didn't need recompilation
                          <grapheneos:discord> the packages show as speed compiled in dumpsys package

                          ...

                          <grapheneos:discord> this appears to be why (re @grapheneos: it's quite possible this update just didn't need recompilation)
                          <grapheneos:discord> this update simply had very few changes to Java libraries

                          ...

                          <grapheneos:discord> it's confirmed that there were no changes to boot class paths in the update so no need to recompile apps

                              • Dde0u

                                • Post #18

                                ryrona Apparently the optimization is automatically skipped whenever possible, when there are no relevant changes to the system that would require a recompile. This release didn't need any recompile.

                                Thanks for bringing that information here!

                                  augmented @inoigjig
                                  12 hours between each channel I think it was

                                  Its not 12 hours. Length of time depends on an assessment of likely possibility of problematic bugs, depending on whats changes are included. Alpha channel can often be a couple of hours. Beta is more likely to be something like the 12 hours you suggest. But there can be wide variations.

                                    Once again, thanks for fixing the visibility of empty Contacts fields in Dark Mode. I just went to add another contact and I can actually SEE things. Thank-you.