• [deleted]

  • Post #9

GrapheneOS

Pixel 5 tested on 2024032100 alpha release, no problems encountered. Thank you very much indeed. I didn't know you had problems finding Pixel 5 testers until matchboxbananasynergy posted the request. I hope more here can join in after reading below that I have no problems.

The following all worked fine on Pixel 5:

wifi
vpn = mullvad (in playstore enabled banking profile)

location-GNSS in separate outdoor profile
offline mapping app with GNSS/location fix

garmin connect with bluetooth sync to garmin watch
garmin explore

polar flow app with bluetooth sync to recent polar watch
polar flow app with bluetooth sync to 9 year old polar bicycle computer

fingerprint reader OK for main profile switching and authentication in banking apps

banking apps x3 (and only one requires play services, others fine without)
one further financial app
wise money transfer app

google playstore update of banking apps on dedicated banking profile

opensource voip app = linphone
commercial voip app = localphone

travel / bus / train /ticketing apps x3

fastmail web app
fairemail app (installed from fdroid-basic)

        It's now in the Stable channel for non-extended-support devices but will remain in the Beta channel for the Pixel 4a (5G) and Pixel 5 for a while since it's the first QPR2 release for them due to us needing to port them to it combined with end-of-life devices being a low priority. We'll move it to Stable for the Pixel 4a (5G) and Pixel 5 after we get a lot of feedback.

        [deleted] fingerprint reader OK for main profile switching

        I read few other comments also where people have mentioned that this issue of putting passcode always when switching from profile to another has solved for them, am I the only one who is still being asked for passcode every time I switch profiles? Sometimes, the UI glitches out and screen becomes irresponsive - I have to press power button to turn of the screen and then I am able to enter the passcode (I am using different alphanumeric passwords for each profile).

            • [deleted]

            • Post #12
            • Edited

            dsjvhjdjhgvcjhsdc My intent was to convey that I had tested the fingerprint reader in a few different ways. With regards to your issues with profile switching, I am not a source of expertise. I can only give a few suggestions in reply.

            I'm not sure we should be cluttering up this testing feedback thread but I will reply.

            If your system behaves differently to others', then the cause is most likely to be found in: settings/configuration; a 'buggy' interaction between an app you have installed and GOS/AOSP; hardware; or the 'view' of the fscrypt/filesystem for a particular user-profile 'namespace'. I'm suggesting everything else is a constant we all share. I say this because, for a given release, unlike with most Linux/BSD distributions, my understanding is we all have an identical GOS/AOSP binary distribution sat on the primary partitions.

            • In system > multiple users, there is an 'allow running in background' toggle. If this is off, then you will always need to enter a PIN for that profile after switching profiles.
            • In security > fingerprint there is a toggle 'use for screen unlocking' - I am sure you have been there already but I have to mention for others who read this.
            • Set up a new, blank profile with none of your own apps and see if you have the same profile switching issue there too.
            • Do you have faulty hardware? Can you test the fpr with an app?
            • I do recall sometimes having a slower profile switch. I had assumed a process wasn't quickly getting the priority it required, or something was delaying fscrypt from unlocking the profile's key.

            Hope this helps a bit.

              • [deleted]

              • Post #14

              graph01 Can I simply switch from the beta channel back to the stable channel?

              Sort of, yes ... if you switch system update > Release channel back to Stable , then you will be back on Stable releases when the Beta you have now is promoted to Stable.

              Until the request for Pixel 5 testers came, I had thought there were lots of 'cutting edge' users out there and I had just assumed I was a dinosaur on stable. I think somewhere in https://app.element.io/#/room/#testing:grapheneos.org I read a remark that implied the devs had had to put a lot of effort into porting QPR2 to the low priority Pixel 5. This is because Google have abandoned Pixel 5 in QPR2 and hence GOS has no port to build upon. After all that effort, it was then frustrating that no one was showing any interest in testing (but perhaps just because we didn't know there was an issue). So I think many more of us will need to start using the alpha/beta release channels to make this feel worthwhile for the devs.

                  Version 2024032100 is working fine on the Pixel 4a (5G) (updated via Beta release channel), thanks. No new issues observed so far. That said:

                  A few notes:

                  1. System Settings > About Phone > Android Version > Android Security Update still shows "December 1, 2023". According to the Release Notes, it should show "March 5, 2024" though?
                  2. System Settings > About Phone > Android Version > Kernel Version still shows 2024-02-05 as the build date. Should the build date not be more recent?
                  3. The issue with the low Android system UI framerate when playing back 30 fps videos (AOSP issue #303693361) still exists, even though the issue tracker seems to indicate that it should be fixed with Android 14 QPR2?

                  And a general question:

                  Considering that the Pixel 4a (5G) and Pixel 5 and Pixel 5a use the same SoC and same kernel and considering that the Pixel 5a is not EOL yet (unlike the other two models), would it be possible to install the firmware and drivers from the Pixel 5a on the Pixel 4a (5G) and/or Pixel 5 to get the Pixel 4a (5G) and/or Pixel 5 fully supported again?

                    DeletedUser130 System Settings > About Phone > Android Version > Android Security Update still shows "December 1, 2023". According to the Release Notes, it should show "March 5, 2024" though?

                    No, that wouldn't be accurate. Your device is EOL and can't receive firmware updates past that. The patch level reflects the last time it could get complete patches.

                      Thank you GrapheneOS and all the people behind it! I didn't expect my app compatibility issue is solved so fast! Infact the only reason I bought a Pixel is GrapheneOS. Your work matters and it means a lot to many people.

                      "December 2023" would not be entirely accurate either though? Because:

                      1. The Pixel 4a (5G) stock OS shows "November 2023" (not "December 2023"), does it not? Or is there a December 2023 update available for the Pixel 4a (5G) that is applied to GOS but not to the stock OS?
                      2. The "Android Security Update" date is not necessarily tied to firmware and drivers but to the core OS? Maybe an additional/separate field could be added for the firmware/drivers date?
                      3. Considering that the Pixel 4a (5G) uses the same SoC and kernel as the Pixel 5a (which is not EOL yet), the drivers for the Pixel 4a (5G) should still be up-to-date (the release notes page indicates that both firmware and driver updates would be missing)?
                      4. Could the firmware of the Pixel 5a not perhaps be installed on the Pixel 4a (5G)? If it could, was it just not tried yet due to no Pixel 4a (5G) user be willing to try it yet (due to a potential risk of the device becoming bricked in the process)?

                        • [deleted]

                        • Post #20

                        dsjvhjdjhgvcjhsdc I wish I could delete my previous reply. I found this: https://github.com/GrapheneOS/os-issue-tracker/issues/2847 Prompted for PIN when switching profiles when biometric available which might describe your issue. I don't think I thought through the differences between dedicated fpr and an on screen fpr; and I was probably responding to your remark suggesting only you had an issue. Sorry. All the same, the good news is, it says 'completed 2 weeks ago'.

                            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.