GrapheneOS No, that didn't work either. It's really weird. I have sideloaded the system update twice, nothing changed(integrity IDs too). what can I try, factory reset? Thanks for your help!

  • de0u replied to this.

      lumzl Does the sideload succeed, or does it return an error?

          lumzl Ok, I just compared the picture to the web site and I think the signature hash in the picture is the correct hash for the 7a according to the web site. Can you say what you mean by "the integrity IDs are different"?

              Dear team and users,
              for me the haptics on this version are really f'd up. Pixel 8 has one of the best vibration motor I ever used, and the haptics were perfect. Now, agree this update, I would describe them very "springy", with reverb, and unpleasant. Have you made some modifications or is it something that Google screwed?

              Thank you.

              Edit: I searched the forum, and it may be Google's fault: https://arstechnica.com/google/2025/03/bad-vibes-google-may-have-screwed-up-haptics-in-the-new-pixel-drop-update/

                de0u You're absolutely right. I stupidly thought that these two lines should be the same, even though there is only one, lol.
                This is probably a hardware issue, and it has nothing to do with GrapheneOS. My device just died for no reason. I'll try flashing factory image anyway. Thanks for the help!
                Here it is: https://imgur.com/a/eSq4GvM

                  ToffoliGate I agree with you.
                  The haptics feel very strange. I am using 3-buttons-navigation and since the update the buttons don't work like before. I often have to tap a seconds time. I have the feeling that you now have to press the buttons more centrally.

                    SCRCPY not working after this release. Any help please

                    lumzl Ok, as a result, there was a problem with the software. flashing the factory image fixed all the problems. That's really weird.

                      Pixel 9 Pro running 2025030800

                      The Messaging App isn't working in secondary profiles. It sends & receives in Owner but does neither in a secondary profile.

                      Other messaging apps (QUIK and Fossify) work as normal.

                      The issue didn't exist before the 2025030800 update.

                        I'm using the charging limitation since the feature was introduced. I have to admit that I never recognized the occasionally full charging. Charging was always capped at 80% as expected.

                        Since this release, and also with the 20250309, it's not limited anymore. Was there any change in this regards? Or might the "occasionally full charge" just happened now few times in a row by chance?

                        Everything else works fine as before the updates. Thanks a lot for your great efforts!

                        Pixel 7

                          Google seriously fucked up the haptics man. I hate typing with my P8P now. Wtf. I hope this gets reverted soon. oh boi

                            I think I'm having a problem with the latest operating system version. The Pixel 8 Pro only charges at 1.8 watts. The operating system says that there are 10 minutes left, but the charge doesn't increase; it only stays at about 65% and 10 minutes left.
                            When I restart it, the charge speed is normal, but after a few minutes it goes back to 1.8W. This wasn't a problem a few days ago.
                            It has 50 full cycles of wear and 100% health according to AccuBattery.