yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] michie:
I used this as a dirty workaround in the nvpowerhal. Not sure if it's still relevant for 4.9 though.

Dragon: Fix lightbar behaviour · ThaMichie/android_device_google_dragon@3363f85

Contribute to ThaMichie/android_device_google_dragon development by creating an account on GitHub.

github.com
[Pixel C Original Android Development] npjohnson:
I'll look - thx.
[Pixel C Original Android Development] 306bobby:
Any reason to actually using the 4.9 kernel?
[Pixel C Original Android Development] npjohnson:
Because we can't progress past Android R on 3.18. BPF is a hard blocker, and to boot you need to remove all net restrictions features.

4.9 is the path forward.
[Pixel C Original Android Development] 306bobby:
Gotcha, just curious!
[Pixel C Original Android Development] muerte33:
In the initial post on the thread it says:

"My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default"

In the installation guide it says that if you want to add google apps, you must add before the initial reboot.

Is the google playstore installed by default with this ROM ?

Also, is the install of the Sphynx recovery required or can we use TWRP?

Thanks so very much!
[Pixel C Original Android Development] npjohnson:
where does it say that? I can remove it.

And yes it's all included - and yes you need to use Lineage Recovery for sphinx to flash.
[Pixel C Original Android Development] muerte33:
Thanks very, this is great! I may have to give it a shot this weekend!
[Pixel C Original Android Development] _benedict_:
Looks interesting! I might give it a try soon and try to help beta test.
[Pixel C Original Android Development] Thor316c:
Awesome stuff, just got this installed on my 4 year old's pixel C...what a perfect way to test right?

Couple things I noticed right away, apologies in advance if these are expected.

System Error Pop up Message on boot up into Android:

Android System - There's an internal Problem with your device. Contact your manufacturer for details.

Notifications:

Serial console enabled - Performance is impacted. To disable, check bootloader.

Charging this device via USB (I have nothing plugged into the charging port).

Not Responding Messages:

When I hit the "Square nav button" clear out any apps, then click the circle button I get: Trebuchet isn't responding.

When navigating in settings, randomly I'll get: System UI isn't responding.

Random bug observations:

Auto Rotate not working, will be orientated based on what it was booted up with, for example if the tablet is in landscape orientation when i boot up, it stays that way even when i try to flip it to portrait. Vice versa if I boot up in portrait mode.

Besides those, everything that my 4 year old cares about(aka all the video apps/games etc) are all working, really awesome way to breathe more life into this tablet.

Thank you again for your awesome work, looking forward to continue testing!
[Pixel C Original Android Development] npjohnson:
Talking about these individually The notifications are expected, the serial notification is really just debugging stuff, the pop-up is actually an issue with all Nvidia devices right now, we're working on it. It doesn't impact functionality, Android just doesn't like the kernel version that we're on, it's subversion is a bit too old for the build systems liking.

Charging this device, that's weird, I don't have that.

Sensors aren't expected to work yet, if I didn't already put those in the OP I should go do that.

The trebuchet crash should be fixed? Not sure why it would be crashing but if you get me a log I will look into it.
[Pixel C Original Android Development] Thor316c:
Thank you for the quick reply, is there a guide on how to pull a log to send to you?
[Pixel C Original Android Development] npjohnson:
There is a guide on wiki.lineageos.org as to how to pull logs

But instead of uploading them to a GitLab ticket just share them here
[Pixel C Original Android Development] Thor316c:
Awesome thank you, found the guide and here are the logs! Again happy to test any new builds, provide logs etc!
[Pixel C Original Android Development] muerte33:
I finally got around to trying to update my Pixel "C" to this new ROM.

I have TWRP 3.4.0.0 on this machine running the last Lineage OS20 ROM from April 2023

This Pixel "C" already has an unlocked bootloader so I just went to this step:

Install LineageOS on sphynx | Odd Solutions Wiki

wiki.oddsolutions.us

I knew I had to get the Lineageos recovery on there, so I started with the "fastboot flash recovery.img"

When I tried to perform that command I got:

Unknown Partition recovery.img

Fastboot error: cannot determine image filename for recovery.img.

Do I have to put the Stock Google Pixel "C" image back on before I go to Sphynx?

Thanks very much!
[Pixel C Original Android Development] npjohnson:
you aren't reading close enough.

fastboot flash recovery recovery.img
[Pixel C Original Android Development] muerte33:
Sorry about that, my bad!

I put in the correct syntax this time:

fastboot flash recovery recovery.img

and got:

Sending 'recovery' (21748kb) OK[0.766S]

Writing 'recovery' Failed (remote: 'Unsupported Command')

Fastboot: Error: Command Failed

On the Pixel "C" screen:

Waiting for Fastboot command
[Pixel C Original Android Development] npjohnson:
no clue man, check your drivers. that works here and for others.
[Pixel C Original Android Development] muerte33:
I assume all that I need to flash is the recovery.img (I saw the boot.img and vendor.img out there)?

I am running Android SDK Platform Tools 35.0.0.

Thanks!
[Pixel C Original Android Development] npjohnson:
yes, wiki details it.

Other images are for debugging.
[Pixel C Original Android Development] muerte33:
I tried updating the Pixel "C" from a Windows 11 machine instead of the Windows 10 one. It gave the same messages. I tried two different USB cables, updated the Android SDK Platform tools to 35.0.1 (March 2024) from 35.0.0 (Feb 2024).

I think it might be failing because of TWRP being there or maybe some messed up partitioning over the years that was necessary to get LineageOS20 to work. I am stilll working fine on LineageOS20. Thanks so very much for your help! I may work on it some more next month when I have more time.
[Pixel C Original Android Development] A$h!$h:
'Fastboot flash recovery' then drag recovery file to command or simply rename recovery file (example - lineageRecovery.img)

Final command like--- fastboot flash recovery lineage recovery.img and press enter
[Pixel C Original Android Development] muerte33:
I tried with the IMG file renamed under Windows 11, and it failed too, I got the same error message.

Under LineageOS20, I did see another developer option called:

Rooted Debugging

Allow running Android debugging as root

I turned that one on too, and attempted the fastboot again, and got the same error message:

Sending 'recovery' (21748kb) OKAY [ 0.653s]

Writing 'recovery' FAILED (remote: 'unsupported command')

fastboot: error: Command failed

I can then boot back into LineageOS20 after holding the power button down for about 30 seconds or by issuing a "fastboot reboot" command.

Thanks very much!
[Pixel C Original Android Development] npjohnson:
is your bootloader locked?
[Pixel C Original Android Development] muerte33:
No the bootloader is unlocked, that 30 second delay hits me every time with this message:

"Bootloader is unlocked and OS verification is OFF"

I think it may be related to this problem:

Modified Dragon MTP driver for Windows

While testing some MTP stuff for TWRP I have realized that you always have to disable USB debugging to make MTP working. The same problem like on other devices too. But it´s just a Windows driver issue only .. and pi*** me off :) I was...

xdaforums.com

I cannot update the driver on Windows 11 because it is not signed (W11 blocks it hard).

I am just using the ADB one that came with Windows 11, which kind of works, but obviously not good enough!

I will go back to the older Windows 10 machine next week and see if I can force this driver that FollowMSI adapted in the thread above for Windows 7, and try that one.

I also tried to force update TWRP from the 3.4.0-0 (6/22/2020) that is on the Pixel "C" to the current version of 3.7.0_9-1 (3/25/2023),

but got the same error message as the lineage recovery.img, so it has to be a bad USB driver, or I just need to boot a Linux machine and be done with it. It is not the USB cable.

Thanks again, I am sorry about these Windows issues, what a pain.
[Pixel C Original Android Development] A$h!$h:
Try another recovery
[Pixel C Original Android Development] npjohnson:
No, don't do that, as I said in the OP, because this uses 4.9, it's very specific about what works and what doesn't
[Pixel C Original Android Development] A$h!$h:
Sir is there any telegram group for this tablet.. I didn't find any group.. even Google pixel tab don't have Android 14 rom
[Pixel C Original Android Development] npjohnson:
Nope.

I don't do telegram groups, I have a build server, a wiki for installation, and this thread for feedback and bugs
[Pixel C Original Android Development] iraklilion:
I have an issue. After installing the rom everything worked for me and did oem lock.

Now I ran fastboot oem unlock and factory reset does not work after oem unlock. It shows error and my device is stuck in semi unlocked state where fastboot is saying device is already unlocked, but it is not factory reset…

The recovery I used in your instructions is broken and does not do factory reset correctly.

What can I do to oem unlock the device again?

Thank you.
[Pixel C Original Android Development] npjohnson:
I have no clue why, on a ROM with broken features intended for developers, you would relock your bootloader - I am honestly surprised you didn't brick.

The recovery factory resets correctly, but doesn't handle FRP/force reset because 3.18 and 4.9 handle very differently.

You can try fastboot -w.

If that doesn't work I don't know, you can try to boot the recovery again and wipe, but not sure.
[Pixel C Original Android Development] iraklilion:
Yeah, I know... I was installing stock rom and was having weird errors. Thought it was caused by the oem unlock state. Now that I think about it I feel stupid that I locked the bootloader. I guess I'm forever stuck with lineage 21 haha lol

Is there any other backdoor way to go back to stock rom and lock?
[Pixel C Original Android Development] Thor316c:
Just loaded up the March 27th build, right away trebuchet issue is fixed and everything seems to be running well! @npjohnson ! Thank you again!

Perfect timing too as I have a trip coming up this week...time for my son to stress test this build 😂
[Pixel C Original Android Development] A$h!$h:
Thanks for this rom. Hope will u make more fully functional
[Pixel C Original Android Development] npjohnson:
there's literally a wiki, with explicit instructions and all the links you need linked in the OP.

Not sure what you expected out of this post.
[Pixel C Original Android Development] l3iggs:
Hey thanks very much for this. I would really love some life to be breathed into my tablet here. Should I expect any WiFi issues? I can't connect to my WPA2 network.
[Pixel C Original Android Development] npjohnson:
weird, got logs?

Wifi works fine here.
[Pixel C Original Android Development] A$h!$h:
After installing recovery file by fastboot... Rom zip file should I flash but what about boot.img file?

Plz send proper procedure
[Pixel C Original Android Development] npjohnson:
Read the wiki.

It literally lays it all out. If there isn't a step that needs it you don't need it.
[Pixel C Original Android Development] l3iggs:
I'll work on fetching some now. Relatedly, the (adb) USB ID is pretty unexpected:

$ lsusb | grep 'Bus 003 Device 029'
Bus 003 Device 029: ID 057e:7104 Nintendo Co., Ltd Pixel

I think we should expect 18d1:5208
[Pixel C Original Android Development] npjohnson:
yeahhhh "whoops" that's on me lol - will fix (I also maintain the Nintendo Switch android port)
[Pixel C Original Android Development] l3iggs:
android_kernel_google_msm-4.9/include/linux/ieee80211.h at a64c90281b01d8c38b5586981c07452a7a4ee463 · LineageOS/android_kernel_google_msm-4.9

Contribute to LineageOS/android_kernel_google_msm-4.9 development by creating an account on GitHub.

github.com

WLAN_STATUS_REQUEST_DECLINED?
[Pixel C Original Android Development] pranks1989:
Thanks for the ROM! I just flashed it, and it is working great except for the known issues. Is it possible to remove/uninstall gapps?
[Pixel C Original Android Development] npjohnson:
If you want to ADB root and remount I don't see why not.
[Pixel C Original Android Development] pranks1989:
Could you guide me to a list of the apps related to gapps in the system drive that I should remove? Sorry I have not been in this space for a while.
[Pixel C Original Android Development] npjohnson:
Nope. I don't support it.

You can try whatever you want though.
[Pixel C Original Android Development] pranks1989:
Then is there a way to support a build without gapps? Or does LineageOS have native gapps support nowadays?
[Pixel C Original Android Development] npjohnson:
This is unofficial. My builds, not LineageOS's official ones.

Official builds have no google apps. Mine do.

Anyone can sync the source I work on and build sans gapps, I just won't be doing it.
[Pixel C Original Android Development] pranks1989:
Then calling it LineageOS is misleading. I am confused why gapps would be included in any LineageOS build - official or unofficial

I can see the source - how do I exclude gapps?
[Pixel C Original Android Development] npjohnson:
It is not misleading at all. It's literally LineageOS with Google Apps. I even say it in the OP.

I include them because I use them, and many people enjoy the more stock like experience while maintaining LineageOS features. Plus, I use these builds to verify VTS/CTS/GTS on LineageOS, which explicitly requires full GMS.

If you don't like it, frankly, don't use the builds. Build your own.

You can literally sync a fresh lineageos tree per the wiki, then just add the following to your .repo/local_manifests/sphynx.xml:

```

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="TheMuppets/proprietary_vendor_google_sphynx" path="vendor/google/sphynx" remote="github" revision="lineage-21"/>

<project name="TheMuppets/proprietary_vendor_nvidia_foster" path="vendor/nvidia/foster" remote="github" revision="lineage-21"/>

<project name="TheMuppets/proprietary_vendor_nvidia_common" path="vendor/nvidia/common" remote="github" revision="lineage-21"/>

<project name="TheMuppets/proprietary_vendor_nvidia_t210" path="vendor/nvidia/t210" remote="github" revision="lineage-21"/>

</manifest>

```

Then it's as simple as `build/envsetup.sh && brunch sphynx`, a LineageOS zip will spit out the other end.

Again though, the ODS wiki covers all this.
[Pixel C Original Android Development] pranks1989:
Perfect. tysm! Appreciate the super quick response.
[Pixel C Original Android Development] A$h!$h:
Download option showing - This device does not exist
[Pixel C Original Android Development] npjohnson:
April builds are building and uploading.
[Pixel C Original Android Development] KaedeNashi:
Could this ROM can read the 8GB RAM?I changed the Pixel C from 3GB RAM to 8GB，The others ROM can reboot the system,but it can't read the 8GB RAM,It also display to 3GB
[Pixel C Original Android Development] npjohnson:
What exactly isn't seeing all 8?
[Pixel C Original Android Development] A$h!$h:
New build I saw in download section 12-4-24 but still you not posted
[Pixel C Original Android Development] npjohnson:
Huh?
[Pixel C Original Android Development] KaedeNashi:
I changed the Hardware from 3GB DRAM to 8GB,​

I changed the Hardware from 3GB DRAM to 8GB,​

but the other ROMs only read and display 3GB on system，​

For example：​

remixOS,LineageOS 19，LineageOS 20,MOKEE 11，crDroid 12，crDroid13.​

Could this ROM can read and display the 8GB DRAM?​
[Pixel C Original Android Development] npjohnson:
I don't know how you missed what I said, I'm aware of what you said, I asked you where exactly it wasn't detecting all 8 gigs? In settings? From command line?
[Pixel C Original Android Development] KaedeNashi:
In setting
[Pixel C Original Android Development] npjohnson:
That's harmless, as long as the CLI shows the full amount, it's just a visual
[Pixel C Original Android Development] npjohnson:
no clue man. You'll have to figure out why it doesn't detect more memory.
[Pixel C Original Android Development] muerte33:
I never could flash the new Lineage recovery to the Pixel "C" using the

fastboot flash recovery recovery.img

I could NOT upgrade TWRP to version 3.7.0.9-1 either using fastboot flash recovery (from TWRP 3.4.0-0).

I used an "adb push" command to get the final version of TWRP to \sdcard\Download , then was able to update TWRP to 3.7.0.9-1 from TWRP 3.4.0-0.

My question is, can I load the LineageOS recovery.img the same way (from the TWRP menu).

Thanks again for all the hard work!
[Pixel C Original Android Development] npjohnson:
probably, but idk why you can't flash it:

```

nolenjohnson@ODS-PROD:~$ fastboot flash recovery ~/website/lineage/sphynx/20240412/recovery.img

< waiting for any device >

Sending 'recovery' (21752 KB) OKAY [ 0.660s]

Writing 'recovery' (bootloader) writing flash

OKAY [ 0.568s]

Finished. Total time: 1.280s```
[Pixel C Original Android Development] BreakfastBerry:
Thanks for the great work! It is great to see our old tablet getting a breeze of new life :)

The issue I encountered is that whenever I tries to flash Magisk through adb sideload (`adb -d sideload Magisk 27.0.zip`), the system bootloops and refused to boot up. Is that expected due to the age of our hardware? Are there any ways to try and fix it?
[Pixel C Original Android Development] KaedeNashi:
Maby we must to Recompilation the coreboot?

Pixel C uses coreboot。

Its hardware parameters may be written inside coreboot？
[Pixel C Original Android Development] npjohnson:
You can't just do that - it's signed.

You said the 8gb works somewhere else on some other ROM?
[Pixel C Original Android Development] KaedeNashi:
No,other ROMs also only works 3GB RAM 🥲
[Pixel C Original Android Development] npjohnson:
yeah then I have no idea my guy
[Pixel C Original Android Development] KaedeNashi:
All right，I will try to found other method，Thank you!
[Pixel C Original Android Development] michie:
Nice work, apart from LP0, led and the jank it's kind of in the same state as LOS20 on 3.18.

Maybe some kind of touch boost mechanism to boost the gpu frequency could help reduce the jank. That made animations smooth on 3.18.

What do you think of the LP0 issue. Could it be bootloader related?
[Pixel C Original Android Development] npjohnson:
bootloader? Why would it be bootloader related?

The issue is that Nvidia products on 4.9 don't even properly have LP0, as they're set top boxes. NV never fixed LP0 because it was un-needed, those devices have screensavers and such.

We need to fix LP0 in the NV kernel.
[Pixel C Original Android Development] michie:
Well, I figured that if Icosa got LP0 working on the same kernel then it could only have something to do with the way they load their custom bootloader. Anyway, I don't know much about that, just trying to help. :)
[Pixel C Original Android Development] pranks1989:
I am getting the following error during the build:

FAILED: ninja: 'vendor/nvidia/common/rel-shield-r/nvcpl/app/NvCPLSvc/NvCPLSvc.apk', needed by 'out/target/product/sphynx/obj/APPS/NvCPLSvc_intermediates/package.apk', missing an no known rule to make it

This is a relevant error I saw with your reply when I searched in Google, but nothing else, so thought would check with you if you have any suggestions.

I did run ./extract_files.sh
[Pixel C Original Android Development] npjohnson:
I didn't tell you to run extract-files :)

I gave you the local manifest to use to fetch the files the build server uses.

Do that.
[Pixel C Original Android Development] pranks1989:
I did use the local manifest you provided:

I only ran extract-files later when the build initially failed thinking that might help. roomservice.xml was likely auto created at some point. I deleted that, reran breakfast and am still getting the same error
[Pixel C Original Android Development] npjohnson:
run repo status from the root of the lineage tree and give me the output
[Pixel C Original Android Development] npjohnson:
huh something went wrong.

Try a full repo sync, if they're still empty cd to each repo effected and git reset --hard.
[Pixel C Original Android Development] pranks1989:
I did a

repo forall -c "git reset --hard && git clean -fd"
repo sync --force-sync

and now I can see all the files. It is currently building. Thanks again for all the help!

Do you have any guides to enable continuous automated builds, or should I simply set up something using cron?
[Pixel C Original Android Development] npjohnson:
I wouldn't automate it. Just repo sync --force-sync & build monthly after the ASB is merged I guess.

I say that as often repo will require some intervention.
[Pixel C Original Android Development] pranks1989:
The build completed but there is a boot loop - it does not go past the Google logo. Recovery does not load either. So I tried to adb sideload using your recovery, and that did not work either.

My builds are 820MB vs your build of 1.6 GB which is likely because your builds have gapps integrated.

Not sure if you have any suggestions, but I understand if you are not able to support
[Pixel C Original Android Development] npjohnson:
did you make any changes other than syncing the sources?

try repo status again.

Also, yeah the size diff is gapps.

Not sure, you can build -eng to get adb on boot for logs
[Pixel C Original Android Development] pranks1989:
Repo status looks good

repo status
nothing to commit (working directory clean)

My recovery.img is 12kb smaller than yours.

I didn't make any changes. Will try the eng build and debugging.

Currently I am doing a full fresh repo sync - wondering if running extract_files.sh was the issue
[Pixel C Original Android Development] npjohnson:
extract-files should make a 1:1 copy of vendor, you can use repos status to see changes.

A confused why it doesn't boot for you.
[Pixel C Original Android Development] pranks1989:
I agree. repo status looks good, and ideally that should be the definitive signal that the baseline is correct for the build.

A fresh repo sync after deleting everything, and a quick build (1.5hours with 10 cores of 10900k) later, it is the same result and strangely the recovery.img continues to be ~12kb smaller than your build.

To weed out all unknowns and variables, I nuked the entire build server VM, and now doing a fresh install of Ubuntu 20.04. I do not expect any new results, but does not hurt to try before going crazy on other methods of debugging.
[Pixel C Original Android Development] npjohnson:
yeah, let me build a test build and see how it goes for you. Will link you via DM.
[Pixel C Original Android Development] npjohnson:
Please grab this in the next 8 hours: https://download.ods.ninja/Android/purgatory/
[Pixel C Original Android Development] pranks1989:
Sorry I missed the 8 hours deadline! The fresh build in the new build server also results in the same bootloop even with recovery.img

Attaching it here in case someone wanted to check it out.
[Pixel C Original Android Development] npjohnson:
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja
[Pixel C Original Android Development] pranks1989:
Thanks. Just tested the recovery.img and it worked. Did not test the .zip, but I think that will work as well since for my builds, even recovery.img did not work.

I attached the recovery.img from my build in a previous post in case someone had the tools/knowhow to compare/check what's wrong
[Pixel C Original Android Development] npjohnson:
I can compare.

But what I gave you was just a no modifications build.
[Pixel C Original Android Development] pranks1989:
Your build worked too - just flashed and booted. Attaching my builds.