- Apr 5, 2013
Btw does the screen have a green tint at brightness lower than 15% with 90 Hz on?
Literally started this test last night, doing another controlled battery test to see how it does. Can't share the results even when the phones die; as it's now under embargo lol.
I didn't notice anything like this, no.
Yes, but I wrote Pixel 3 (regular size), which has a good stereo balance. The Pixel 5 has not.
Yes, but the other embargos are still active. Supersaf told his unboxing that he us not allowed to upload a photo comparison.
the second video of op about the 5 actually has a decent amount of camera / video footage. There was another pretty high quality video and image showcase on youtube but the person did delete and reupload the video without the camera footage, certainly because of the current embargo.
Hate to necro this thread...but we need some insight on AVB on the Pixel 5.
As most of us know, root has been blessedly simple on the Pixel series up through Android 11.
However, Android 12 brought about some new challenges.
With the 12 Beta, users on the 4a5g, 5, and 5a discovered that to be able to boot a patched boot image from /boot, vbmeta must be reflashed with --disable-verity and --disable-verification. That seemed to be the only additional requirement. Otherwise, a patched image loading from /boot would result in the bootloader error "failed to load/verify boot images".
But, with the 12 stable release, we discovered that reflashing /vbmeta with the disable flags will cause the device to bootloop into recovery with an error message: "Can't load Android system. Your data may be corrupt". At this point the user has a choice:
* Wipe /data, but be able to successfully run permanent root
* Reflash /vbmeta and /boot back to stock, and either run unrooted or live boot a patched image from fastboot for temporary root
Again, this has been specific to Android 12 on the Pixel 4a5g, 5, and 5a, as well as the 6 series. Maybe it has something to do with Boot Header v4 introduced with Android 12?
So what about subsequent updates? If reflashing vbmeta was required when updating from beta to stable, I would assume that it would also be required for the monthly updates - and therefore a data wipe. Dm-verity and verification do not stay disabled if you reflash vbmeta without the flags. I wiped when I installed 12 beta 5, and I was unable to retain data when upgrading to stable. It's really going to suck if we have to wipe /data every time we update vbmeta.