[Pixel C Android Development] ipdev:
Hi all. :D

My original Pixel C screen finally died awhile ago..

Recently I took a gamble on a used Pixel C.

Good price. Small scratch on the screen that is only noticeable when the screen is off (and you are looking for the scratch).

I got it the other week, unlocked the bootloader and updated it to the last version.

ryu-opm8.190605.005

Then did a complete clean install of Lineage 18.1.

What I normally do is a little over-kill. You can skip the fastboot erase part. ;)

Boot into bootloader.

fastboot erase boot
fastboot erase recovery
fastboot reboot bootloader
fastboot erase system
fastboot flash recovery /home/ip/ip/twrp/twrp-3.5.0_9-0-dragon.img

Boot into recovery.

TWRP-> Wipe-> Format Data (Type yes) and press enter.

TWRP-> Reboot-> Recovery (Ignore the warning about no system installed).

TWRP-> Wipe-> Advanced Wipe-> (Select all the partitions) and Swipe to Wipe.

TWRP-> Reboot-> Recovery (Ignore the warning about no system installed).

The last reboot to recovery basically just cleans up so you start with a nice clean recovery log.​

All partitions are clean and formatted properly.

Save for boot, there is no option in TWRP to erase the boot partition.

Boot will be replaced when a new rom is flashed so not a big deal.

Install rom. (Using ADB Sideload)

TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.

adb sideload lineage-18.1-20210206-UNOFFICIAL-dragon.zip​

TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.

adb sideload open_gapps-arm64-11.0-stock-20210130-UNOFFICIAL_TEST.zip​

TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.

adb sideload magisk-debug.zip​

Magisk canary 21410. app-debug.apk renamed to magisk-debug.zip​

Reboot to system.

Then updated Magisk.

Update to Magisk 22001

Updated Magisk app.

- Update Magisk -> Direct install method failed.

- Update Magisk -> Patch boot image worked.

Fastboot booted the magisk patched image to test.

It booted and Magisk was 22001. (Temporary)

I was then able to used the Direct install method to install.

Then updated ROM to the 20210304 build.

Boot into recovery.

TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.

adb sideload lineage-18.1-20210304-UNOFFICIAL-dragon.zip​

OpenGApps and Magisk backup scripts ran, no need to manually reflash them.​

Reboot to system.

Clearing the caches before rebooting to system is generally not necessary.

If you have an issue with a cached file then clear the cache(s).

Cache(s) are rebuilt on boot so, it will add a little bit to boot time as the caches are being built.

The Magisk backup script was installed when I originally flashed 21410 in TWRP.

Using the direct install method or using fastboot to flash the patched boot image, will not install the backup script.

The next two Magisk update did not go so well.

Update to Magisk 22003 (and 2204)

Updated the Magisk app.

- Update Magisk -> Direct install method failed.

- Update Magisk -> Patch boot image worked.

Fastboot booted the magisk patched image to test.

It booted and Magisk was current. (Temporary)

- Update Magisk -> Direct install method failed.

- Used fastboot to flash the patched boot image to the device.

---

I have a question about the codecs.

I know there was an issue with Netflix when they were purging old device from the L1 certified list.

What is currently not working using the Nvidia Hardware codec?

This last week I streamed shows and movies with:

Amazon Prime Video

HBO Max

Netflix

I did not have an issue streaming.

I normally used for two to three hours at a time. Even four hours, I still had no issues.

Cheers all. :cowboy:

PS.

I use personal builds of OpenGApps.

[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2021-01-06 xda thread - Post 3,267 - Link

Feel free to use is you want. :)

PPS.

I am currently back on ryu-opm8.190605.005 for testing Magisk patching issue.

There are a bunch of oddities with 2204 and this device.