yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] brackenhill_mob:
Some people can dirty flash this ROM, others can't. The last one I could was the 1st one in December 2020. Every one since I've had to clean flash. But others don't have this issue so I'd try dirty and see what happens as you've nothing to lose (provided you've got a backup :))
[Pixel C Android Development] Alxoom33:
flash upgrade to

It depends which rom you are discussing. The new January version can be flashed dirty, without a wipe. It will even preserve the Gapps, if you want to,

The rom with Gapps included must be clean flashed.
[Pixel C Android Development] tabormeister:
Okay solid this is what I assumed. Trying and will report back!
[Pixel C Android Development] tabormeister:
Dirty flash worked perfectly! Even restored Magisk. I flashed again just to be 100% sure.
[Pixel C Android Development] m+a+r+k:
I'm a bit confused on the description for this ROM specifically "device specific MAC will be ignored."

I need my device MAC Address to set up my fixed wifi IP address. I can't use the randomised MAC nonsense.

Does this mean I can't use this ROM?
[Pixel C Android Development] brackenhill_mob:
There was an issue several months ago for me with the wrong Mac address but I've not had it on this ROM. YMMV ;)
[Pixel C Android Development] m+a+r+k:
Thank you. So if you go into Wifi settings, click on the cog icon for the SSID, under Advanced, you can see your device MAC address f8: etc. and not the randomised one?
[Pixel C Android Development] Thracks:
Not sure what I'm doing wrong, but my Pixel C shuts down when trying to boot this ROM. It gets right to the point where the login screen would appear, then turns off.

1. Latest TWRP 3.5.0.

2. Formatted Cache, Dalvik, Data, and System.

3. Clean flash the latest 18.1 ROM build. Verified MD5.

4. Correct/latest NikGapps for Android 11.

5. Fresh install of Magisk 21.2.

ROM and GAPPS flashes successfully. Reboot the OS, aaaaaalmost finishes loading the OS, then the device powers down.

It was previously running the Pixel Experience ROM just fine. Any ideas, folks?
[Pixel C Android Development] brackenhill_mob:
I see my device mac
[Pixel C Android Development] brackenhill_mob:
I've had this in the past. Flash ROM then reboot then gapps reboot then Magisk reboot
[Pixel C Android Development] m+a+r+k:
Thank you (y)
[Pixel C Android Development] m+a+r+k:
HI

Installed 18.1, NikGApps full and Magisk and all OK.

However Titanium can't reinstall Nexflix app and data (just sits there trying and I have to Force Stop the app) and the Play Store won't show me Netflix at all.

How do I get Netflix back?
[Pixel C Android Development] brackenhill_mob:
TB doesn't play nice with Android 11 in my experience. I've switched to Swift Backup.

There are many sites which have the Netflix APK - your favourite search engine is your friend ;)
[Pixel C Android Development] tabormeister:
FWIW after Magisk Hide and installing the Netflix APK, play store shows netflix again. On the 1/5 build.
[Pixel C Android Development] Chiron1991:
Hi, first of all thank you for all the work on this ROM!

Until earlier this week I was sporting LineageOS 17.1 (Android 10) on my Pixel C, then decided to upgrade to 18.1 since the 17.1 image was discontinued.

However, I have significant issues with video playback in any app (Twitch, YouTube Vanced, Plex). With auto-quality playback I always get 420p-ish resolution although my connection definitely could handle more, and sometimes playback runs on like 10fps.

Is this expected due to the Nvidia codec issue stated in the starting post? Do other Pixel C ROMs face the same issues? Should I just roll back to LineageOS 17.1?
[Pixel C Android Development] francoscala:
@followmsi Very good ROM, thanks for your hard work! I noticed some bugs, I'll explain them:

- long time during chrome opening;

- sometimes every thing in the UI is full of lag (but if I play a video for example on youtube it is smooth);

- the progress indicator (while searching wifi network or bluetooth devices) has a background pink (I think that is a bug).

I noticed that the all the roms (also official from Google) presents some lags, since Android Oreo, someone know the issue?

Thanks

IfI can help in anyway on the development, I can!
[Pixel C Android Development] ax562:
First of all @followmsi thank you so much for all your hard work on this rom and all the other work you have done on the Pixel C! You rock! @francoscalaI can confirm the "long time" for chrome. I have no issues regarding progress indicator. I do notice while charging the touch screen becomes buggy/unstable at times (I'm thinking due to the voltage being upped while charging Edit: Looks like it's a fastcharge issue as I'm not seeing while charging ~=1.5amps). The last majore bug I have come across for sure is google maps force. It loads for a few seconds then force closes every time. Besides that it's silky smooth. As for the laggy UI the @francoscala mentioned, I have seen it at times when I am using a lot of apps/background/processes. I think that is more of a hardware thing, everything smooth when I'm not going loco on a lot of apps. @followmsi let me know if you need any log cats or anything else. Thanks again!

Edit: I forgot to mention, once widgets are placed they are hard to move/remove. All (remove/uninstall) functionality disappears when hold down on widget.
[Pixel C Android Development] revengers:
I noticed lag was present with the native browser. Duplicated the issues with widgets.

Tested lawnchair, made a huge difference,

I believe this is a good workaround; lawnchair stays for now.

Thanks @follomsi
[Pixel C Android Development] followmsi:
LineageOS 18.1

We are still using Google Software decoders/encoders.

Maybe we switch back to Nvida Hardware codecs next month .. not sure yet.

Pls rename/remove the ".bak from "/vendor/lib/libnvomx.so.bak" and reboot to get back Nvidia HW codecs like before.

lineage-18.1-20210206-UNOFFICIAL-dragon.zip

Changes:

- Google Security updates -> February 2021

- Switched back to old HWC composer.

- Some hacks to improve camera/video

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Enjoy :p
[Pixel C Android Development] 82Fgdt:
Just dirty flashed the latest version. Only issue I've had so far is having to reinstall Magisk. Other than that, love the continued work on this ROM @followmsi!
[Pixel C Android Development] muerte33:
Thanks again for all the hard work on this ROM @followmsi !

Greatly appreciated!
[Pixel C Android Development] desireholic:
Hi @followmsi thank you for the great effort.

I've just wanted to share with you this message from the Magisk creator of the risks involved of setting selinux to permissive on Android.

What problems are there currently stopping you from setting it to enforced?

https://twitter.com/i/web/status/1359054106019565571

https://www.reddit.com/r/Android/comments/lfye5r/_/gmoi05a

GitHub - vvb2060/Magica

Contribute to vvb2060/Magica development by creating an account on GitHub.

github.com
[Pixel C Android Development] ax562:
Yooo, just dirty flashed the lates 02 18.1!! AMAZING! TY @followmsi . Definately a smoother experience so far vs the last 18.1.
[Pixel C Android Development] Everio9000:
Sadly I had to come back to Android 7.1 stock in my Pixel C because with newer Android versions it becomes slowly and laggy.

Do you have a smooth and fast experience with LOS? I tried some versions but it always ends up being slowly and laggy. How can I fixed?
[Pixel C Android Development] BeniS98:
Has this ROM the same issue as the Pixel Experience ROM that Google related apps need a long time to open?
[Pixel C Android Development] ax562:
As far as I know, only Chrome is having an issue taking longer to load than usual. I feel it's gotten better with this last version he realease but still an issue. From my understanding, that is more of a google apps issue rather than the LOS rom. Not 100 though at this time.
[Pixel C Android Development] ax562:
dm me bro
[Pixel C Android Development] ax562:
Anyone else having trouble with heavy graphics apps (games)? Kept getting force close on Asphault 8/9. Changed to /vendor/lib/libnvomx.so.bak to libnvomx.so but I actually had more issues. Clearly the display was clearer/looking/better imaging but worse force close. Switching back to .bak and going to test further.

Edit: Yeah, unfortuantely, this release was unstable for me, not only games just overall, freeze, fc, laggy, I'm flashing back to the previous release.

Edit2: Honestly I believe all these problems were related to updating magisk through the apk. On 3/15 build now and flashed latest magisk.zip(renamed from .apk) after I installed LOS and everything cool. Just wanted to share.
[Pixel C Android Development] BeniS98:
But why other ROMs does not have this issue. Does not sound like a Google issue.
[Pixel C Android Development] m+a+r+k:
Why don't we have Ambient Mode in Assistant Settings?
[Pixel C Android Development] m+a+r+k:
My Pixel C is slow and laggy and driving me nuts. So I replaced it.

Tried Lineage and Pixel Experience.

I want to turn my Pixel C into a Home Hub device and I thought it would be easy with Ambient Mode, but it's not there in either ROM.

Any reason why not?
[Pixel C Android Development] b8842dc0:
Thanks @followmsi for keeping our Pixel C devices going strong. This morning, I upgraded mine to the new lineage 18.1. Using the beta version of OpenGapps 11.0 Everything seems to be working great. I disabled the built-in Chrome browser to avoid issues, which wasn't a problem anyway, as I use Firefox all of the time, already. Nice work!
[Pixel C Android Development] poloxo53:
Hi all,

I'm following this tread since a long time now, used to flash my pixel C with Linageos 15, then 17 and just tried to go to 18.1 as 17.1 is discontinued...

I've made a Dalvik/Cache/system swipe before install but after reboot it ask me for a password to uncrypt the device...but I never set up any password or activated any encryption.

Now I'm a little bit stuck because I don't have access to my data (Storage folder) anymore even with TWRP (3.4.0).

Could you help please ? I'm not very used to pass trought my computer with ADB but if that's the only solution I can try with your good advices. :)
[Pixel C Android Development] Alxoom33:
Update your TWRP recovery. Your's is out of date.😄
[Pixel C Android Development] Mother_Teresa:
Try "default_password" also, worked for me sometimes.
[Pixel C Android Development] Alxoom33:
Can also flash password-pin-erase.zip from @follomsi's Google Drive. Download to USB dongle or data file in I eternal memory.
[Pixel C Android Development] poloxo53:
Thank for your advices, I've updated the Recovery but still the same issue yesterday.

Then I tried to flash password-pin-erase.zip but it didn't work on the first reboot just after... but only after 2 or 3 reboot later...

So I managed to get back my data to save it and then to make a factory reset.

Anyway the test with "default_password" as password didn't worked either.

In the meantime I tested Pixel Experience but doesn't managed to get it work as all system applications stop working on first boot, generating a lot of popup and make the tablet impossible to use.

I'll try again to flash Lineage 18.1 from @followmsi with Gapps included at 1st and the nupdate to last version.
[Pixel C Android Development] bra1niac:
Is anyone having trouble updating magisk since the Feb 6th release of 18.1? I get "unable to detect target image" when updating from within the magisk app. I just want to know whether or not its just me before I dig deeper into Magisk.
[Pixel C Android Development] ipdev:
The new version of Magisk has some issues.

There are quite a few "I did not read or search before I posted this." and "Me too." posts.

If you dig though them, you find some devices had issues while others had no issues with the update.

That being said, if you tried the direct install method and received an error. You have now have a broken boot image.

You will need to install an older magisk patched or a stock boot image from the rom you are using.

Then use the Magisk app to patch your boot.img file.

Magisk and Manager were merged, it is now just Magisk.

Then fastboot boot the new patched boot image to make sure it works.

If it works you can then fastboot flash it or install it with TWRP.

The problem seems to be related to MagiskHide.

If you unhide the Magisk app (what was called Manager) and toggle MagiskHide off, you should not have an issue patching a boot.img file of using the direct install method.

You can hide the Magisk app and toggle MagiskHide on after the update.

Cheers. :cowboy:
[Pixel C Android Development] brackenhill_mob:
If you are trying to update to v22 be aware that you cannot do this from within the app. You need to download the APK file and rename it to have a .zip extension then flash this from within twrp.

It's working well on my Pixel :)
[Pixel C Android Development] Alxoom33:
I was skeptical. But it worked for me! Thank you!
[Pixel C Android Development] Sparty73:
Just wanted to say that I love this ROM! Motivated me to actually purchase a used Pixel C (yes, in 2021) off eBay. The keyboard is a killer stand, and, for the most part, just works. Runs really well. Thanks for your efforts!
[Pixel C Android Development] Sparty73:
I did this, but SafetyNet fails. Any tips? Do I need to install MagiskHide?
[Pixel C Android Development] Alxoom33:
You need to go to go to Magisk settings, toggle Magisk Hide and enable remorse hosts. Reshoot🥳
[Pixel C Android Development] Sparty73:
You the man! Worked. Thanks.
[Pixel C Android Development] Alxoom33:
Glad it worked!
[Pixel C Android Development] poloxo53:
After some more attempts I finally managed to get 20201230_lineageos 18.1 more or less working on my PixelC...

I said that because YouTube app is closing as soon as I try to open it for instance.

I tried also to upgrade to 20210206 release from @followmsi but I got a bootloop after flashing. So I came back to 1st release.

Is anybody facing the same issue?
[Pixel C Android Development] Alxoom33:
Did you do a clean wipe/ format of internal storage¿
[Pixel C Android Development] Sparty73:
Anyone having issues connecting to 5ghz networks? Mine doesn't even see them, only my 2.4.

For context, I have a publicly viewable network through Asus AiMesh.

EDIT - Had something to do with the WiFi channels. Sees it on some, but not others.
[Pixel C Android Development] followmsi:
LineageOS 18.1

We have switched back to Nvidia Hardware decoders/encoders.

Pls rename/remove "/vendor/lib/libnvomx.so" and reboot to use Google Software codecs.

Chrome is still opening slowly .. will take longer to solve this one.

lineage-18.1-20210304-UNOFFICIAL-dragon.zip

Changes:

- Google Security updates -> March 2021

- Kernel: Update Wireguard

- Some hacks to improve camera/video

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Enjoy :p
[Pixel C Android Development] Agent.Orange:
@followmsi: I have a problem with the last build. After installing, the bootanimation takes over a minute and then boots back to TWRP. I tried flashing the previous build, but still have this kind of problem. Even if I stick to your instructions, the problem still persists.

1. Boot into TWRP

2. Install ROM.zip

3. Re-Install Magisk 21.x

4. Wipe CACHE and DAVLIK

5. Reboot into system

Did I miss something?
[Pixel C Android Development] drahtwurst:
after 2. wipe cache+dalvik+reboot system? install magisk later, helped me.
[Pixel C Android Development] Agent.Orange:
Yes, still the same problem.
[Pixel C Android Development] Alxoom33:
Thanks@followmsi! New build is running great!

One question. Do you recommend that we stick with the Nvidia drivers, or modify to use the Google drivers?
[Pixel C Android Development] Fly-n-High:
Same issue. Is there something I'm missing?
[Pixel C Android Development] poloxo53:
Hi, I just wipe Dalvik/Cache at the end of rom flashing process...

I usually format everything only for major lineageos updates like 17 to 18.

Let'sctry with last build from @followmsi 😉
[Pixel C Android Development] poloxo53:
Hi, I just wipe Dalvik/Cache at the end of rom flashing process...

I usually format everything only for major lineageos updates like 17 to 18.

Let's try with last build from @followmsi 😉
[Pixel C Android Development] Sparty73:
Google play services is crashing all over the place, even after removing the file. Dirty flashed from prior build, and wiped cache and dalvik.

Suggestions?

EDIT - Reflashing GAPPS seems to have fixed it.
[Pixel C Android Development] tabormeister:
+1 for the bootloop after flashing 3/4, re-flashed Nikgapps and I'm back in. No need to wipe. I am still getting a weird dimming issue if I hit the tablet really hard with tasks where the ui will crash and dim the whole screen and I can't do anything until I reboot, will try to grab a log next time it does it.
[Pixel C Android Development] Alxoom33:
I have been getting dimming and freeze, occasionally, as well.
[Pixel C Android Development] m+a+r+k:
I had this and Chrome taking over a minute to load and e-mail app and other memory intensive stuff being very slow. I put it down to lack of memory and in the end I gave up as it was unusable and I moved on.

Pixel C currently being used as a digital photo frame in living room.

I'd love to turn it into a smart hub but there is no Ambient Mode in this ROM :-(
[Pixel C Android Development] Alxoom33:
I haven't had your chrome issues. Just some slowing down on occasion. Pixel C is still a useful tablet, at least for me.
[Pixel C Android Development] tabormeister:
Honestly I'm blown away at how usable mine still is, especially as like a forum/browsing device
[Pixel C Android Development] Alxoom33:
I agree! Keep thinking it will break or brick soon and I'll have to move on. But its still going strong!
[Pixel C Android Development] Sparty73:
Has anyone else been having location issues with this ROM (not the latest build, but the ROM in general)? I've had multiple apps (Maps, YouTube TV, etc.) tell me they can't locate me. "High accuracy" is on. I know this device doesn't have a GPS, but I also know location's usually found using WiFI and the like in non-GPS devices.
[Pixel C Android Development] thetample:
Just to make sure, if I were to install microG, I can install the Nanodroid zip file directly in TWRP right?
[Pixel C Android Development] markus4000:
Only flashing the ROM itself also gave me a bootloop (or rather boot failure with a boot to recovery after that) but flashing the version with gapps included worked. I had some google app crash messages on first boot though (like "News & Weather", "Calendar", etc) and "Finishing system update..." took forever, but it did finish eventually, followed by a couple of play store updates (including support library). However, even after a device reboot gapps (like youtube and calendar) crash on launch. I will try to flash gapps manually and see if it helps. I also get these "screen dimming" sometimes, indicating some kind of a crash without the proper error dialog.

Thx for all the efforts of keeping this device alive!

*EDIT:*

Uninstalling and reinstalling Youtube/Youtube Music and other apps fixed them. I simply disabled "News & Weather" sync in the "account" settings page and ignored this one.
[Pixel C Android Development] Alxoom33:
Thank you!

If you disable MagiskHide you can update to Magisk 22004 without an issue and without patching. DL the Magisk 22004 apk from github, copy and rename apk to zip. Flash the zip in TWRP. Done!

Then you can enable Magiskhide in Settings and all is well!
[Pixel C Android Development] followmsi:
HW codecs vs. Sofware codecs

It's all about playing videos / movies ..

I did not made a lot of tests .. But the Nvidia HW codecs do have problems playing video content in Chrome browser .. maybe in some other apps too.

This problem exists since Lineage-17.1 .. but in older Chrome versions you could disable "hw acceleration" by chrome flags.

In newer versions of chrome this flag does help partially only .. still a lot of video content does not work/play.

I do use chrome-based KIWI browser and Firefox sometimes .. they do not have this video issues like Chrome browser. Also no need to change config flags.

For this reason I will keep HW codecs per default .. if you are heavy chrome user you may switch to Software codecs.

On 18.1 for dragon the chrome browser has hard delay to start/open up.

Still hope to find root cause for this start delay.

But the delay is not related to the video issue in chrome.

Cheers
[Pixel C Android Development] followmsi:
LineageOS 18.1

Made a quick test build today ..

Backport of Wifi-Display (Miracst) for Android 11.

Tested screen mirroring to Samsung TV only.

And we are testing Android lowmemory killer on 18.1 .. same config like on 17.1 before.

As said above .. Chrome is still opening slowly .. will take longer to solve this one.

lineage-18.1-20210315-UNOFFICIAL-dragon.zip

Changes:

- Backport of Wifi-Display (Miracst) for Android 11.

- Switched from Kernel lowmemory killer to Android LMKD.

- New HWC_composer

- Some hacks to improve camera/video

- Patched frameworks/base to support microG

Enjoy :p
[Pixel C Android Development] Alxoom33:
Thanks for update. Just flashed. Opened pixel launcher seems to be working OK. Nova launcher, my main goto, keeps fc'g. Tried wiping cache in app settings, ng.
[Pixel C Android Development] Alxoom33:
I fix3d by updating Magisk to220005 and wiping all of the Nova app data.

Edit: New build working great for the last 3 days! 😁
[Pixel C Android Development] dsapac:
I just bought the device and I installed this firmware The device is working great I just have delay when I clip an app Netflix for me it's is working I installed module from magisk IPTV from my provider works great. But a lot of apps have delay They are working but ... I stream movies and series and I use MX Player Streams are in 1080p Bluetooth is working with speakers and headphones Mounting external storage with no problem Overall very good firmware Tnx for keeping this device alive with security patches and newer firmware Android 11
[Pixel C Android Development] ax562:
On the 3/15 build all working better than original release (los18.1-010521). I installed los18.1.zip (dirty flash) wiped cache/dalvik installed latest magisk.zip (after I renamed it from .apk) and all gravy!!! Thanks @followmsi ! You ELITE :geek:
[Pixel C Android Development] Sparty73:
I'm going to basically +1 my prior question. Anyone have any clues? It's driving me nuts when trying to watch local networks on YouTube TV.
[Pixel C Android Development] pitchdown:
anybody has an option root 18.1 ?

Didn`t work for me with different magisk files.
[Pixel C Android Development] b8842dc0:
Magisk works fine for me in 18.1.
[Pixel C Android Development] pitchdown:
do you have step by step guide which you did follow?

Which version magisk did you use?

When you use root checker, you see that the device is rooted?

Did you also use magisk manager and/or supersu?

I hope you can help me for a while :)
[Pixel C Android Development] b8842dc0:
1. Download latest Magisk apk (version 22.0) from here:

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

2. Rename file, changing extension from .apk to .zip

2. If you already have Magisk installed, and have enabled Magisk hide, you must unhide it.

3. Reboot into TWRP

4. sideload magisk zip file

5. Reboot.
[Pixel C Android Development] pitchdown:
I did that procedure.

including the installation of 18.1 and gapps.

Magisk flashed after this from TWRP (latest version).