yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] ipdev:
If I am reading your posts correctly.

You are having issues with MTP (Media Transfer Protocol) when booted into system?

- What OS (Windows, MacOS, Linux)?

If you are referring to adb/fastboot, what release of platform-tools are you using?

- The newer versions seem to have some issues with (the chromeOS parts of) dragon.

Note:

Platform-Tools r27.0.1 (December 2017) seemed to be the safest to use at the moment.

You can download an older release of platform-tools by adjusting the official download link to the release you want.

Spoiler content hidden.

Cheers. :cowboy:
[Pixel C Android Development] EnginEAR:
Just installed the 20220815 build on Google Drive. Still smooth as butter :).
[Pixel C Android Development] followmsi:
lineage-19.1 - August 2022

lineage-19.1-20220815-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> August 2022

- Patched system/netd to bring back Network traffic monitoring on older kernels.

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here ..

https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy Android 12L (y)
[Pixel C Android Development] StefanoGY:
Hi, thank you for your work. Is there any way to fix the L1 DRM? Thank you
[Pixel C Android Development] Everio9000:
I don't know why but with the last update my Pixel C run smoother and faster than ever. Thank you.
[Pixel C Android Development] followmsi:
L1 has been revoked by google. pls contact them,
[Pixel C Android Development] followmsi:
lineage-19.1 - August 2022 - Part 2

One more build this month .. to test all the nice changes from @michie !

lineage-19.1-20220819-UNOFFICIAL-dragon.zip

Changes:

- Various device, kernel and vendor changes -> Big thanks to @michie !

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here ..

https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy Android 12L (y)
[Pixel C Android Development] mrbubba999:
This will need a full wipe then?
[Pixel C Android Development] ivanperezcaro:
It is not necessary.
[Pixel C Android Development] Everio9000:
@followmsi I tested the last update and it's amazing. I'd like to give you my humble opinion and I think it'd be better if the user experience was smoother and slower and not too faster like now. It's just an opinion. : ) Thank you for your incredible work !!!
[Pixel C Android Development] tabormeister:
You should be able to increase the animation timers in developer options if you wish
[Pixel C Android Development] lx1905:
我刷了最新版的八月rom还是这样，电脑是win10系统，电脑连接pixelc才能充电。电脑与平板电脑连接后，选择文件传输无反应，无法将文件从电脑复制到平板电脑。使用 Platform-Tools 工具仍然不起作用。不知道是什么原因？你的pixelc可以连接电脑复制文件吗？

Mod translation via GT: I flashed the latest version of the August rom and it is still the same, the computer is win10 system, the computer can be charged only when it is connected to pixelc. After the computer is connected to the tablet, selecting File Transfer does not respond and cannot copy files from the computer to the tablet. Using the Platform-Tools tool still doesn't work. Do not you know why? Can your pixelc be connected to a computer to copy files?
[Pixel C Android Development] QuantumSingularity:
DFS channels still don't work. 😞

I've changed the region in system - advanced to US rebooted, checked, changed back to EU, rebooted.

But that's the only bad bug/feature.

The rom is fast and smooth.

Thank you for your time and effort.
[Pixel C Android Development] ttrueten:
Hi there

thanks again for your Work. Except for Chrome (hangs after a few web pages) and the camera, everything runs as desired.

T.
[Pixel C Android Development] Papaw01:
Thanks for a great rom! It turned an inexpensive Pixel C into a great, modern, tablet
[Pixel C Android Development] lx1905:
May I ask the system 19.1 that I flashed from the official 8.1, the rom, gapps, magisk installed in order, do I need to replace the kernel?
[Pixel C Android Development] Papaw01:
I followed the instructions in the OP, I did not replace the kernel. YMMV
[Pixel C Android Development] Papaw01:
re: Pixel Keyboard

I had trouble getting the keyboard to pair. I wiped and reflashed, still nothing. I let it sit for awhile, reattached it and , bam, there it was. I probably didnt let it charge enough before trying it, and probably didnt need to wipe everything. :(
[Pixel C Android Development] followmsi:
lineage-19.1 - September 2022

lineage-19.1-20220926-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> September 2022

- Increased ZRAM size and swappiness

- Patched system/netd to bring back Network traffic monitoring on older kernels.

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here ..

https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy Android 12L (y)
[Pixel C Android Development] Papaw01:
I am having an odd problem... I am on the previous build and everything is running great, except when I try to restore a saved backup. Doesnt matter what ROM the backup is , it gets to "Restoring System.. " and it crashes, and boots into Fastboot mode. I can reflash everything and its fine.. I just cant restore anything. Thoughts?

thanks!
[Pixel C Android Development] QuantumSingularity:
Super smooth.

Only minor is no-dfs 5GHz WiFi.
[Pixel C Android Development] 101010101001:
The lastest update seems to have am issue playing 60fps content. Basically the same issues listed in your crdroid forum. When interacting with the tablet via volume controls or something in the app playing content, the fps is normal. Otherwise it stutters
[Pixel C Android Development] cognitivedesires:
Is the camera working on Pixel C
[Pixel C Android Development] BartKey:
Camera doesn't work on Android 12 custom roms for pixel c
[Pixel C Android Development] cognitivedesires:
Should I wait for Android 13 ROM then?
[Pixel C Android Development] BartKey:
Don't know, I'm only end user, no developer. Let's hope the developer can fix the camera.
[Pixel C Android Development] tabormeister:
Problem is proprietary Nvidia blobs. Basically needs redone from scratch .... @michie has been doing some magic porting things from Shield TV though, so you never know.
[Pixel C Android Development] ndrs81:
Hello fellow Pixel C fans,

I've installed the Rom on my trusty Pixel C and noticed the physical keyboard is not mapped correctly. I had the same probem running PixelExperience btw. I'm using the german keyboard layout and ö, ä and ü files are not mapped right. ü = ´, shift + ü = ` and alt gr + ü does nothing but should be +. Ö and Ä do work but their alt gr functions are missing (should be ' for ö and # for ä). Any chance this can be fixed somehow?

Thanks for keeping the Pixel C alive!

Regards

Andy
[Pixel C Android Development] followmsi:
Did this problem start with September build ?

Both August builds did not have this "60fps" problem ?
[Pixel C Android Development] followmsi:
lineage-19.1 - October 2022

There is still some strange "60fps" stuttering .. The last device and kernel changes were made in August .. to test the changes from michie.

Maybe some lineage patches are related .. need to check and find the root cause.

lineage-19.1-20221010-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> October 2022

- Patched system/netd to bring back Network traffic monitoring on older kernels.

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here ..

https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy Android 12L (y)
[Pixel C Android Development] followmsi:
lineage-19.1 - October 2022 - Part 2

This build should fix the "60fps" issue ..

lineage-19.1-20221019-UNOFFICIAL-dragon.zip

Tested with Magisk 25.2 !

Enjoy Android 12L (y)
[Pixel C Android Development] Papaw01:
Since the recent builds need a new gapps, can we still dirty flash?

thanks for you hard work!
[Pixel C Android Development] _benedict_:
For those of you who made the jump to Android 12/12L, how good is it? Have some spare time in the weekend and planning to upgrade 🤩
[Pixel C Android Development] followmsi:
All 12L builds will need 12L gapps !

Otherwise go for it .. dirty upgrade from previous build should work without problems .. I did the same.
[Pixel C Android Development] EnginEAR:
I've been on the latest build since it was out.

Smooth and no complaints.
[Pixel C Android Development] _benedict_:
I updated and am now enjoying a very smooth experience with Android 12. Thank you @followmsi !
[Pixel C Android Development] _benji:
Hi,

I also see the same issue on my Pixel C with the german Pixel C Keyboard. Looks like its missing the correct keyboard layout. https://github.com/followmsi/android_device_google_dragon already contains an App called DragonKeyboard, and this does contain the correct .kcm keyboard layout file for the Pixel C Keyboard (res/raw/keyboard_layout_german.kcm) but this seems to get overriden by the version provided by InputDevices.apk, which contains a different mapping not suitable for the PixelC keyboard.

As a workaround I used https://exkeymo.herokuapp.com/ to provide an additional layout containing the correct mapping (copied from here: https://github.com/followmsi/androi...ard/res/raw/keyboard_layout_dragon_german.kcm), but of course it would be nice to have this active by default.
[Pixel C Android Development] _benedict_:
Hi,

LineageOS 19 has also installed Lineage Recovery, while I am pretty sure I did not approve to.

Did I miss something in the installation process?
[Pixel C Android Development] ndrs81:
Thanks, that looks promising!

I'll give that a try when I get home.
[Pixel C Android Development] jwhan:
Hi, I want to ask a dumb question. Please forgive my ignorance. How to change the command kernel command line parameter. BTW I am work on lineage-17.1 branch of your kernel repo.

I want to add the console=tty0 to kernel command line parameter. Till now, I've tried three way but none of them worked.

1. Modify the device/google/dragon/BoardConfig.mk.

BOARD_KERNEL_CMDLINE += console=tty0

2. Insert these line to kernel/google/tegra/arch/arm64/configs/lineageos_dragon_defconfig

CONFIG_CMDLINE="console=tty0"

CONFIG_CMDLINE_EXTEND=y

3. Modify the kernel/google/tegra/arch/arm64/boot/dts/tegra/tegra210-smaug.dtsi

chosen {
#ifdef CONFIG_KASAN
bootargs = "cros_legacy console=ttyS0,115200n8 init=/init rw kgdboc=ttyS0 earlycon=uart8250,mmio32,0x70006000 ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend";
#else
bootargs = "cros_legacy console= init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend androidboot.selinux=permissive androidboot.hardware=dragon";
#endif
};

to

chosen {
#ifdef CONFIG_KASAN
bootargs = "cros_legacy console=ttyS0,115200n8 init=/init rw kgdboc=ttyS0 earlycon=uart8250,mmio32,0x70006000 ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend";
#else
bootargs = "cros_legacy console=tty0 init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend androidboot.selinux=permissive androidboot.hardware=dragon";
#endif
};

But all I get is just this

[ 0.000000] Kernel command line: cros_secure vpr=0x08000000@0xf6800000 cros_legacy console= init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=bc81152b-b527-4ab1-9cf1-c39104dffc12 no_console_suspend androidboot.selinux=permissive

As we can see, there is no value on console key. Am I do something wrong?
[Pixel C Android Development] _benedict_:
Hi!

USB file transfer doesn't seem to work for me. Tried different ports or different cables. Has anyone tested it?
[Pixel C Android Development] heyChristo:
Mine hasn't worked for years now. I gave up and have to download everything to the tablet.
[Pixel C Android Development] Mother_Teresa:
EDIT: it works

-------------------

Thanks, will report if it worked soon.

Obviously I am not current affairs. Is this an oreo/twrp issue or did I manage to mess it up myself :)
[Pixel C Android Development] followmsi:
Actually it's an Oreo/TWRP problem .. hopefully fixed in the next official version and in v2.
[Pixel C Android Development] Mother_Teresa:
EDIT: I used EF file explorer to browse root and copied the file to /system.

In recovery I mounted system and that allowed flashing the .img.

As I type it is backing the **** out of it so it worked ;)

--------------

Excuse if this is noobquestion etc; I do not have a usb cable at hand atm, so how to flash the v2recovery.img as the download folder is gone in recovery.

I tried flashfire in hope it managed somehow, using ' flash firmware package'.

It reboots, loads, reboots. OS loads.

Loading recovery next it seemed the same and backup failed and with the same cant mount data stuff.

How to check if the flashfire method I used indeed failed (as I did not see any V2 reference)?.

If I must use pc to flash the v2 recovery I can only try later (no cable).

Thanks for the feedback.
[Pixel C Android Development] ketos90:
Hi,

i was on unoffical oreo build, flashed the magisk 14 update and encountered Boot loops. I decided to go back to official los 14.1. I wiped everything flashed the correct vendor.IMG and los Rom with open gapps. Now in Boot Android ask me for the encryption password, but i habe never set one. The strange thing is that formatting data did not solve the Problem.

Has anyone a hint for me?
[Pixel C Android Development] Mother_Teresa:
I read this somewhere:

" It uses "default_password" as the default password"
[Pixel C Android Development] followmsi:
Tested all unofficial lineage-15.0 versions .. no bootloops at all.

Since magisk 13.6 beta or 14.0 final.

The official LineageOS version has forced encryption !

Like requested from LineageOS team.

Only the unofficial version is not forced encrypted !

If you want to bypass encryption you need to install magisk, supersu or other tools to prevent forced encryption - before you boot the first time into system.

Hope this helps..
[Pixel C Android Development] followmsi:
Do not you copy into system .. will make more problems !

Flash as recovery partition with flash fire.

Or use cable and fastboot.

Sorry .. no V2 reference.
[Pixel C Android Development] ketos90:
Thank you the password is correct, but the system says my data is corrupt. Factory-Reset doesn't solve the corrupt data. I wiped several times now, used different los 14.1 builds and installed magisk before booting first time, but no change. I think I have some serious problems with my device.

My data-partition is on ext4 and repairing with e2fsck results in error 8 "operational error".
[Pixel C Android Development] followmsi:
Go into TWRP and "format" data partition .. and start from scratch. ;)
[Pixel C Android Development] ketos90:
I did, 5 times ...
[Pixel C Android Development] Mother_Teresa:
I tried flashfire, but at the time the issue was the data folder not showing in recovery. It seemed flashfire couldn't either.

To fix that I had to flash the V2 recovery.

The way I managed is by copying the .img to the system folder (by now I managed to flash linegage os) and after booting to recovery I mounted the system folder so I could have a file to flash, with succes.

Having flashed the V2 allowed me to acces the data folder and/or backup where before I couldn't due to mounting failure as mentioned earlier.
[Pixel C Android Development] followmsi:
Sounds not good ..

You may try ..

- to install latest stock image via fastboot.

- relock/unlock bootloader..

.. etc..

Before you start the RMA process and send it back to google ..

Good luck !
[Pixel C Android Development] Mother_Teresa:
Did you actually format or only wipe?
[Pixel C Android Development] ketos90:
Well, .... no ....

I formated now and it works again. Thank you and followmsi for your help. Have a nice weekend :)
[Pixel C Android Development] AmazingToast:
I just installed the latest 14.1 nightly from yesterday and I didn't find any new 7.1.2 vendor's in the folder so I just flashed it and now in my secruity patch says September. Was I supposed to flash a new vendor and is this text an error?
[Pixel C Android Development] followmsi:
Actually no .. no text error ;)

lineage is actively maintaining the "old" Nougat sources.

They did merge 7.1.1 September security changes into 7.1.2 branches .. etc.

It's September release level now.

At some point there are coming some kernel patches too.

Also .. at some point the dragon device will get lineage-15.0 ROMs only.

Depends on the kernel (security) and on the other points.

But the vendor.img for Nougat will not change anymore .. you always keep August 2017 vendor.img for Nougat.
[Pixel C Android Development] JLowe:
I am using LOS 14.1 and want to setup a direct LAN connection (USB-LAN connector) from the Pixel to another Linux device (without going through a Router) and don't know how to configure a static IP. Anybody a clue how I can solve this? Adb?
[Pixel C Android Development] customrus:
This is an amazing ROM, thank you. Sorry for asking but is development dead? If so which ROM would you recommend?
[Pixel C Android Development] followmsi:
Still weekly releases for Nougat .. https://download.lineageos.org/dragon

Once Oreo is ready there will be Oreo weeklies. ;)

Hope this helps ...
[Pixel C Android Development] customrus:
Thanks for the information. I'll stick with this build until official then.
[Pixel C Android Development] _benedict_:
But for me it was working well in previous versions.
[Pixel C Android Development] heyChristo:
From arrowOs thread:
[Pixel C Android Development] ipdev:
Are you referring to adb command(s) like adb push or connecting using a file manager (MTP connection) to copy files between the device and computer?

MTP is currently broken in TWRP for dragon..

Are you using Linux, MacOS or Windows to connect?

MacOS needs a third-party app to connect via MTP.

- Unless they updated something recently, I haven't booted up MacOS in about two years.

Cheers. :cowboy:
[Pixel C Android Development] heyChristo:
I have windows 11 and adb commands work when I get the tablet recognized, just no file transfer either when the tablet is plugged in or when I am in TWRP and its plugged in. It just errors out the device driver every time. Fastboot it recognizes if I go manually select the driver after plugging it in.
[Pixel C Android Development] _benedict_:
Thanks @ipdev ! Yes I was referring to an MTP connection. I am using Linux.
[Pixel C Android Development] ragwo:
First, thanks a lot for bringing new life into this old tablet!

When using the physical keyboard with Norwegian layout I'm missing the letter Å. The rest of the special Norwegian characters are present, but the \ is where the letter Å should be. Using enhanced ASCII code doesn't work either. Does anybody know of a fix or work around? I could have the software keyboard on the screen while typing, but it takes up a lot of screen space. Any suggestions are highly appreciated!

Edit: I'm on the latest LineageOS build downloaded from the first post in this thread. The letter Å is supposed to be where the + and = is located.

Edit 2:

Seems like the Swedish and Danish keyboard setup has the same bug.
[Pixel C Android Development] zvondroid:
I'm a software developer who is new to Android OS development. In my career I learned you should have two important things, a great machine and teacher. I got both

MSI Creator 17 laptop and followmsi !
[Pixel C Android Development] ragwo:
Quoting myself as I found a sokution to the problem.

I had to find the specific key layout file for the Pixel C keyboard, as editing the Generic.kl file in /system/usr/keylayout/ did not work. The Pixel C keyboard file is named Vendor_18d1_Product_5018.kl. I changed th EQUALS key to Å and chose Norwegian as keyboard language. The only thing missing now is the apostrophe key, still trying to figure that out.
[Pixel C Android Development] tabormeister:
Nicely done!
[Pixel C Android Development] Papaw01:
I wonder if Lineage 20 and their new camera would solve our camera issues...
[Pixel C Android Development] michie:
I made a Lineage 20 test build for for anyone who would like to try. It's based on my A13 device tree with all optimizations included.

Clean flash is advised. Give the system some time to settle and do it's background tasks during setup. Do a reboot after everything is set up and enjoy a smooth Android 13.

I noticed that the boot animation seems frozen when system is loaded but give it some time, its just loading the UI.
[Pixel C Android Development] EnginEAR:
Seems pretty smooth so far.

Will take me time to bring it back to a state where I can share more though...

I wiped the device since I was on your build of ArrowOS before.

One thing which I noticed almost immediately is that although the cameras still don't work - the camera app doesn't crash :)
[Pixel C Android Development] michie:
Reworking the device tree was priority. Camera's are connected to the system again and are detected. Need some frameworks hacks.
[Pixel C Android Development] followmsi:
lineage-19.1 - January 2023 - final 19.1 build

This is my last dragon build .. @michie will continue to build and publish monthly lineage-20.0 builds for dragon.

lineage-19.1-20230111-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> January 2023

- Patched system/netd to bring back Network traffic monitoring on older kernels.

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here ..

https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy (y)
[Pixel C Android Development] tabormeister:
So long, and thanks for all the fish! You made the Dragon worth using again, and I'm so stoked Michie is carrying it on.
[Pixel C Android Development] muerte33:
I also appreciate all the hard work over the years keeping this device going!

Thanks so very much for all your efforts!
[Pixel C Android Development] muerte33:
Which Gapps should you use with the new Lineage 20 ROM?
[Pixel C Android Development] michie:
All info is in the new thread 🙂
[Pixel C Android Development] muerte33:
Sorry, I did not know a new thread had been started! Many thanks for taking over the Pixel "C" LineageOS project!
[Pixel C Android Development] followmsi:
LineageOS for Oreo is still under construction.

The security level is kept unchanged since first release .. they replacing repo by repo .. step by step.

For this reason I want to wait for more stability .. maybe we can make another beta before first official release.

But right now it's not the time for a new beta.

Hope you have a better understanding now ..
[Pixel C Android Development] JLowe:
Tested also latest lineage-14.1-20171023-nightly-dragon-signed.zip and wondering what is the reason, that native 24bit audio playback doesn't work.

Never tested this before with the Pixel C and LOS14.1. Is there a library or anything else missing?
[Pixel C Android Development] followmsi:
I take care for the dragon blobs and the dragon device tree (only).

Not sure if something related has changed in the base lineage sources.

If it's indeed a missing blob/lib .. we may can fix it.

On which version does it work on Pixel C ?

Stock N and O ?

AOSP tested too ?

Cheers