Amazing work guys. Thrilled that updates comes to us P5 users still. Makes me endorse the fantastic work you guys do, even more.

Hello and thank you very much for your efforts.
I've connected my watch a few days ago the first time, and BT sync is working.
Today, after installing the latest system update, I got the following exception when sync started.
It doesn't say much, don't know if it helps. Closing and restarting the app made sync working again, no exception anymore.

`type: crash
osVersion: google/husky/husky:14/AP1A.240305.019.A1/2024032100:user/release-keys
package: com.garmin.android.apps.connectmobile:8462
process: com.garmin.android.apps.connectmobile
processUptime: 11716 + 249 ms
installer: com.aurora.store

java.lang.NullPointerException: Attempt to invoke interface method 'java.util.List u80.d.w()' on a null object reference
at com.garmin.android.apps.connectmobile.settings.devices.common.c.onPostExecute(SourceFile:228)
at android.os.AsyncTask.finish(AsyncTask.java:771)
at android.os.AsyncTask.-$$Nest$mfinish(Unknown Source:0)
at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:788)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loopOnce(Looper.java:232)
at android.os.Looper.loop(Looper.java:317)
at android.app.ActivityThread.main(ActivityThread.java:8532)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ExecInit.main(ExecInit.java:49)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)`

DeletedUser130 Pixel 4a (5G) and Pixel 5 have the 2023-11-05 patch level officially and were able to obtain the 2023-12-01 patch level via our extended support but not 2023-12-05 or beyond it. The YYYY-MM-01 and YYYY-MM-05 patch levels are split so that if you have the previous month's full patch level you can provide the YYYY-MM-01 patch level with only AOSP patches as long as nothing needing an AOSP patch is built into parts of the code you can't update such as a fix changing the API defined in C/C++ headers including changing inline functions/methods or templates which would require rebuilding code using that functionality in the header. We checked the 2023-12-01 patches and confirmed we had provided all of them.

They stopped getting firmware and MOST driver updates after their end-of-life. They still get partial driver updates via the Pixel 5a being supported. Pixel 5a has nearly the same hardware and it's very unfortunate the Pixel 4a (5G) and Pixel 5 didn't get their support extended until Pixel 5a end-of-life, but that's not within our control. It would have been possible to provide support for them for a bit longer. It might cost more money to license it from Qualcomm and it might have had to be paid for earlier. Regardless, they didn't get it so they shouldn't be used anymore.

Could the firmware of the Pixel 5a not perhaps be installed on the Pixel 4a (5G)

The firmware is different between each of the devices. There are minor hardware differences between them and since the Pixel 5a shipped later it's a later revision of the hardware with some improvements that were in progress for future devices.

    They can't reach 2024-01-01 since that requires 2023-12-05 which cannot be provided. This is often misunderstood. The 01 patch level still includes the previous 05 patch levels. It's not a separate path but rather simply split into 2 parts per month, sometimes a 3rd part if urgent patches were added too late to be officially part of it but early enough to include in a special YYYY-MM-06 patch level.

    First of all... I use GOS without Google Services / Play Services. I checked the following with beta build 2024032100:

    1. After installation and the first restart, the Signal app crashed. There was an error message that the app tried to start several times and crashed. After a restart, I was able to start the app normally. However, Signal prompted me to send diagnostic information.

    2. Existing Bluetooth connections work without any problems. New devices are connected without any problems.

    3. GPS connection works - also in conjunction with navigation app

    4. Existing WLAN connections are recognised. New ones can be added without any problems.

    5. Hotspot works

    6. Fingerprint works when unlocking the device and all apps without any problems

    7. Overall battery consumption is normal. Except for Signal. However, this is a known problem when the app is operated without Play Services.

    8. Various banking apps work

    9. Email, SMS and Threema work.

    10. MTP works between mobile phone and Linux notebook

    11. The OS is very stable and runs smoothly.

    If there are any special functions that need to be tested, please send me a message. If I notice anything else in the coming days, I will let you know.

      For what it's worth, this QPR2 build is noticeably more responsive on Pixel 4a 5G than the older QPR1 builds were. For instance, the delay on tap for notifications I had since Android 14 day-1 is gone. So, thumbs up.

      [deleted] After your reply, I actually went and created 2 new separate profiles and setup the system settings to my preference for both of them (to check if it is an app which is messing up something). And after that, I noticed that I was never asked for pin and FPR always worked when switched in between these new profiles, but when switched from either of these new profile to one of my older profiles (created and setup last year), I had to enter pin to unlock.

      Today, I formatted my spare device (P7a with GOS) and set it up with only 2 profiles with my system settings of choice on both 'owner' and 'New Profile'. I thought it should not ask me for pin and FPR should work every time I switch in-between these 2, but it is not the case. I am having similar exp as of my main device (P8 with GOS) - I had to turn of the screen after each profile switch and then have to enter the pin to unlock it. Later on the same device, I created a 3rd profile and set it up. Now, when I switch from 'New Profile 1' to 'New Profile 2', FPR always works. It is just the case that whenever I try to switch to/from 'owner' profile, it fails.

          dsjvhjdjhgvcjhsdc

          I tried to recreate this, but my phone kept closing down the new profiles for some reason (maybe limit on how many profiles I can have going simultaneously?) lol
          But yeah, having issues with the fingerprint reader when switching profiles, which is not fun since I do it so often.

            [deleted]

            Why was it closed? It has not been resolved at all and is still reproduceable every time.

              @GrapheneOS

              graph01 @GrapheneOS The Signal System log contained the following error codes several times at the time of the crash:

              -------- switch to system
              10000 1645 2025 W BatteryExternalStatsWorker: error reading Bluetooth stats: 9

              Maybe this is interesting for you? So far, the app is running normally and has not crashed again.

                  graph01 from what you posted here, I am not sure there is enough information to determine that the crash was caused by this error or anything related to it.

                    Pixel 4a (5g) bug after this update.
                    Steps to reproduce:

                    1. Use non-default launcher (e.g. Niagara Launcher)
                    2. Disable animations, either from Accessiblity > Color and motion > Remove animations or set Developer options > Animator duration scale to off
                    3. Be on the home screen

                    The bug:

                    • Pressing the recents button does not open the recent menu, it quickly flashes the recents screen(or last opened app preview) and goes back to the home screen
                    • This happens on both owner and secondary profiles
                    • Quickly tapping the recents button a few times does open the recents screen, but that is not the fix

                    Note:
                    The recents button already has another bug that it does not work at all with non-default launchers on secondary profiles, my workaround for that is to force stop and clear data for the Launcher3 (default launcher) app on the required profile, then the recents button starts working, but only for that profile, so doing this on a secondary profile would make recents button on owner and all other secondary profiles buggy, but make it unbuggy for the current profile. and I tested the animation bug after applying this 'fix' on the relevant profile. i.e. this is a new bug.

                      gra123d Maybe not related, but I have experienced a similar issue with Nova when trying to use it at main and at an addicional profiles. No issues at main profile but recents refusses to show at additional profile. Issue at additional profile dissapearead when installing default launcher at main profile. Seems to me isn't possible use at custom launcher at main and at an additional profile. No issues using a custom launcher at 2 additional profiles due to additional profiles aren't running at the same time.