yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Alxoom33:
The update is running great! Flashed with no issues.

One question, should we keep the dragon stock kernel or use the June [MENTION=5480152]followmsi[/MENTION] dragon kernel. I don't know if there is a difference at this point. Adviice?
[Pixel C Android Development] followmsi:
The lineage-16.0 ROM contains "stock" Google kernel.

The separate "unified" kernel does include more patches, uses slightly different config and has "features" like wireguard (VPN) support.

I personally will still use June "unified" kernel for the next time.

Cheers
[Pixel C Android Development] Alxoom33:
Thank you! I followed your advice and flashed the unified June Kernel
[Pixel C Android Development] kurze12:
Problem: My Picel C crashes constantly, the open apps closes after about 15 seconds by itself, Wifi loses the connection, it comes the message: Tablet is restarted. But it does not restart, then everything is normal for 15 seconds, until it starts again. I deleted the tablet and reinstalled, now it works again.
[Pixel C Android Development] Alxoom33:
Can't help you, u less we know what you are running on your tablet and what you flashed to get this issue.
[Pixel C Android Development] kurze12:
The problem occurred two days after flashing the latest ROM. I've completely redesigned Pixel C now, everything is now running smoothly.
[Pixel C Android Development] studio37:
Hi, impossible to send e-mail with Gmail (smtp) ? Any idea ?
[Pixel C Android Development] Thug Life of the France:
Custom recovery

Hey,

Anyone knowing another recovery than TeamWin for the Pixel C as it's broken in it's current release please ?
[Pixel C Android Development] Alxoom33:
Twrp 3.3.1 working great for me. Which version are you using?
[Pixel C Android Development] locuturus:
5ghz wifi hotspot turns on successfully now as well as the 2.4ghz which had already been working. Thanks for your continued efforts there :)
[Pixel C Android Development] Thug Life of the France:
Using 3.31 as well, and it doesn't fully work. I'm barely able to do sideload with ADB and get MTP working.

Standard zip flashing doesn't work

Plus there's still encryption even though I'm on a custom ROM, custom recovery, and unlocked bootloader.

Now it's bootlooping, and I can't even get it to recovery or adb with the usual key combinations
[Pixel C Android Development] Alxoom33:
Are you sure you flashed the img file for 3.3.1.0 for dragon?
[Pixel C Android Development] followmsi:
Get rid of /data partitions encryption and start from scratch. (format data in twrp, just wiping is not enough)

If you boot just once into stock ROM/Lineage-15.1 you will need to format data again. ( forced encryption in stock rom and official lineage-15.1)

Cheers
[Pixel C Android Development] followmsi:
Android Pie - August 2019

lineage-16.0-20190806-UNOFFICIAL-dragon.zip

Changes:

- Google (base/general) AOSP security updates -> August 2019

- Switch back fingerprint to pass SafetyNet

- Latest LineageOS changes for Pie

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] EnginEAR:
Thanks!!!

Thank you!!!
[Pixel C Android Development] Alxoom33:
Flashed, all's good!

Thank you!
[Pixel C Android Development] Markeee:
Dirt Flashed over last months build

All good Thanks
[Pixel C Android Development] studio37:
Cameras crash After a few seconds
[Pixel C Android Development] cmit37:
Swipe up no longer brings up recent apps. Any way to restore that?
[Pixel C Android Development] studio37:
I return stock rom, imap ans camera now working.
[Pixel C Android Development] henrywhtin:
hi, does this rom work will pixel c keyboard flawlessly like the stock rom?

Thanks!!
[Pixel C Android Development] frauhottelmann:
It works very well, but when the keyboard disconnects after a while and you happen to be watching a video, it might pause your video, which can get annoying. Same thing happens when it connects while you're watching a video, because you happen to be hitting a key by accident. But that is the only bug.
[Pixel C Android Development] followmsi:
One last version here ..

lineage-14.1-20170524-UNOFFICIAL-dragon.zip

lineage-14.1-20170524-UNOFFICIAL-dragon.zip.md5sum

This version above is using the normal LOS installer this time .. your gapps will be kept as well.

The kernel and the device tree are based on LOS sources too.

All the changes have been approved now.

Starting next Monday the first weekly build will be produced on LineageOS server.

Google Pixel C has become an official LineageOS device now !

https://wiki.lineageos.org/devices/dragon/

Mission accomplished :)
[Pixel C Android Development] Eschatologius:
Congratulations and thank you for all your efforts!!!
[Pixel C Android Development] dafresh:
Awesome work!

Nice to hear it`s official now.

Got me device these days and had some issues and problems i noticed:

1. Flashing never finished

Flashing lineage-14.1-20170524-UNOFFICIAL-dragon.zip freezed TWRP.

TRWP commandline showed something like

detected filesystem ext4 for /dev/block/......
Patching system image unconditionally
detected filesystem ext4 for /dev/block/......

at the second "detected filesystem ext4 for /dev/block" it stayed for more than 10 Minutes so i shuted the device down.

Tried Version 20170519 which is working for me.

2. Play Store don`t show Safety Net apps protected apps

Tried the Installation routine writen on page 1 with magisk as following

Installation:

1. Boot into TWRP

2. Wipe system, cache, dalvik and data.

3. Install lineage

4. Install current stock vendor.img

5. install opengapps (arm64)

6. install Magisk.

7. Reboot into system

8. Set "hide magsik" in magisk manager

9. Reboot

Magisk passed safety net but protected apps like netflix or super mario run did not appear in the app store.

Seems like app store was already flaged as bad (but showing certified device under settings).

I cleared the app store cash but still no luck.

Got it working by:

1. Boot into TWRP

2. Wipe system, cache, dalvik and data.

3. Install lineage

4. Install current stock vendor.img

5. install Magisk

6. Reboot into system

7. Set "hide magsik" in magisk manager

8. Reboot

9. install opengapps (arm64) with twrp

10. profit!

Any suggestions?

3. "no command" issues

With the problems from point 2 i tried uninstalling magisk (with official uninstaller.zip via twrp)

hopeing the play store will show the apps again.

But the device did not boot into lineageos...just saying "no command" (line in https://xdaforums.com/pixel-c/help/pixel-c-booting-comman-error-t3269918 ).

I flashing vendor.img but didn't helped.

Got the device alive again with flashing whole factory image package.

Maybe i had to flash only original boot.img from factory image or boot.img from lineageos zip?

Got the same "no command" problem by this:

Unlocked the bootloader (android stock) an just booted in twrp via "fastboot boot twrp...".

TWRP said crypted data found. I skipped the screen and went straight to reboot menu and selected reboot system.

I changed nothing...no flashing...nothing => bam "no command".
[Pixel C Android Development] followmsi:
1)

I do have installed this version (20170524) without any issues.

Which TWRP version are you using ?

Did you compare md5 hash of the zip file ?

20170519 and earlier versions were still using "my" slightly modifed installer.

Since version 20170524 we use the "unchanged" LOS installer.

You should try again .. it's the normal LOS installer version and works the same way. (keep your gapps)

Only for the OMS version I will keep "my" installer .. no big changes anyway.

2)

The "helping" reboot in between is maybe related to setupwizard issues with opengapps.

Pls check magisk XDA forum for more details.

Pls try with BeansGapps again.

3)

Yes, you need to install the boot.img from the lineageos zip file.

Extract the zip file and use the boot.img to flash either via TWRP or via fastboot.

Pls send recovery.log to be able to replicate your issue.
[Pixel C Android Development] dafresh:
Thanks for reply. I will get an OTG cable next week for easier handling the flash files. I will report back
[Pixel C Android Development] frauhottelmann:
Does kernel su-hide work already?

https://www.lineageos.org/Changelog-9/
[Pixel C Android Development] followmsi:
Have seen this one a few days ago .. not sure about the "full" impact.

Made a test version now .. based on "official" cm-14.1 branch.

Pls have try ...

tegra-3.18_kernel_dragon_v170526_lineageos-followmsi.zip

The related commits ..

https://github.com/followmsi/android_kernel_tegra/commit/2ed1adb2e045abe621251c2be72d0c96ec4bb826

https://github.com/followmsi/android_kernel_tegra/commit/fd8b4402e0c39e7c51b28c2305e55c6c3648be0a

The 2 commits are not yet on LOS github.

If the kernel still works fine .. I will push them.

SuperSU and/or Magisk are still working fine ?

Pls test and report !

Thanks

EDIT:

Made some quick tests with Magisk v12 only - looks good.

Will approve and submit the change soon.

Pls let me know if there are any issues.
[Pixel C Android Development] ToldYouSo:
Ok.... Have been busy for some time so no time experimenting for me.

I also seem to suffer from often freezing installs of the latest LineageOS (would say about 1 out of 2 times) it freezes at:

Patching system image unconditionally

detected filesystem ext4 for /dev/block/.......

I have to reboot and try again. It will install eventually. (Tried installing LineageOS from OTG or internal /sdcard folder but does not seem to make a difference)

All the kernels released since the 22nd seem to be incompatible with my TWRP 3.1.1-0 created F2FS partitions. It won't boot with a F2FS /data partition.

Concerning the VPN problem I have captured (some) log files of working and crashing kernels.... So tried the latest 2 released kernels 170526 works fine but the just released 170527 has the VPN problem. I captured 1 other log file with a crashing kernel, don't know if it is of any use.... Can get you some more log files of the 2 kernels you released on the 24th if it is of any use?

Also one thing that has been bothering me since the day I got this tablet.... Is that friggin' 30 second delay at boot.... especially when flashing a lot it is such a bummer to say the least. In your opinion, with your experience, is this ever going to be avoidable??
[Pixel C Android Development] followmsi:
Quick answer .. thanks for the logs.

Yes, pls make logs from the 24th kernels too.

Thanks.

F2FS has been removed from fstab in latest release.

The kernel supports it but as it looks like you still need to change fstab accordingly.

LOS has not approved the modified fstab, especially for data partition.

The OMS version will remain working like before.

As a comment, I had to enable forceencrypted as well!

There are some changes between unofficial and upcoming official version.

The last unofficial is as close as possible.

Cant replicate the TWRP issues .. pls send log as well.

Most probably not ;) just get used to the 30seconds waiting time.

Cheers
[Pixel C Android Development] ToldYouSo:
see att.

ah yes I've heard of the fstab story...

see att. recovery.log? it still saves screenshots when it freezes :P

It didn't happen after more than 1 year so I don't think I'll ever will... Very tempted to sell this Pixel C when the Pixel 7 comes out. :D I had the Nexus 7 2013. before my current tab and I miss the handy smaller screen... This one is so heavy and 1" too big for me... Too bad there is no Pixel 9 yet because 7" is 1" too tiny.... anyways.... :P
[Pixel C Android Development] followmsi:
Cant find any LOS installation in recovery.log ..

Pls send a new one.

Freezing is different .. as it still can write your screenshot.

How long did you wait at this screen ?

Did you try with decrypted data partition too ?
[Pixel C Android Development] ToldYouSo:
several times over an half hour. one hour at least 1 time. also the USB LED stops flashing completely when installing from OTG.

This log file should contain one failed and one successful LOS install.

Also have a log of older crashing kernel. Again all of these kernels work fine when disconnecting the VPN when on a rooted android factory image
[Pixel C Android Development] followmsi:
All of these kernels ?

All kernel including from today are working fine on stock Android image ?

Just on LOS do you have this VPN problems ? And only with certain kernels ?

Pls confirm.
[Pixel C Android Development] ToldYouSo:
Well up until v170512_unicorn I have been using this kernel for ages on a stock encrypted image without any VPN crashes. It's only happens on LOS. Have not tried any newer ones on a stock image.
[Pixel C Android Development] followmsi:
No installation in logs again .. do you reboot after failed installation ?

You need to take the log via adb, but no reboot.

Get rid of encryption and test installation process again ..

As well copy the file to internal storage first.
[Pixel C Android Development] ToldYouSo:
I used adb pull /tmp/recovery.log

where is it now? :P
[Pixel C Android Development] ToldYouSo:
and how do I get rid of encryption again? and which kernel would u like me to try it with? :P Don't have a lot of time left so...

btw I think I posted a wrong log earlier for v170522_lineageos

So far it seems the VPN works on LOS kernels only with LOS installed (and the xceed kernel 9.38 and 9.40 also did not have the VPN crash. I noticed then those kernels had encryption disabled by default)
[Pixel C Android Development] ToldYouSo:
and how do I enable F2FS? :P
[Pixel C Android Development] followmsi:
The 24 test version in the download share ..

Just test if it works on LOS for you .. no need for logs.

The recovery.log is still the same place.
[Pixel C Android Development] followmsi:
I just installed the boot.img of latest LOS and installed magisk afterwards... Copied the log to data and here it is ..

As an example what we need ..

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'install'

I:Set page: 'install'

I:Set page: 'flashimage_confirm'

I:Set page: 'action_page'

I:operation_start: 'Flash Image'

[IMAGE FLASH STARTED]

Image to flash: '/sdcard/Download/boot.img'

Calculating restore details...

I:Image filename is: boot.img

I:Reading '/sdcard/Download/boot.img', writing '/dev/block/mmcblk0p1'

[IMAGE FLASH COMPLETED]

I:Set page: 'action_complete'

I:operation_end - status=0

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'install'

I:Set page: 'flash_confirm'

I:Set page: 'flash_zip'

I:operation_start: 'Flashing'

Installing zip file '/sdcard/Download/Magisk-v12.0.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Update binary zip

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

Archive: /sdcard/Download/Magisk-v12.0.zip

inflating: META-INF/MANIFEST.MF

inflating: META-INF/CERT.SF

inflating: META-INF/CERT.RSA

inflating: META-INF/com/google/android/update-binary

inflating: META-INF/com/google/android/updater-script

inflating: arm/busybox

inflating: arm/magiskboot

inflating: arm/magiskhide

inflating: arm/magiskpolicy

inflating: arm/resetprop

inflating: arm/su

Stopped it here ...

Pls check your logs before sending .. will not be able to help you without logs.

If you format data you will remove encryption .. but you may keep it a bit for testing. ;)

F2FS will be more complicated now .. you need to change the fstab inside ramdisk.

Cheers
[Pixel C Android Development] followmsi:
August 2019 - Lineage-15.1

Google made another stock factory image for dragon device - still based on June 2019 security updates.

No device and kernel changes .. just a new vendor.img !

Either you pull it from latest stock ROM .. https://dl.google.com/dl/android/aosp/ryu-opm8.190605.005-factory-25b457f3.zip

Or from gdrive folder ..vendor_OPM8.190605.005_Aug-2019.img

The next official build will require the new vendor.img !

https://github.com/LineageOS/androi...mmit/ad0267e01beabb9fd6d5e45704801631e3f2acae

Enjoy :p
[Pixel C Android Development] Markeee:
Do we need to update this now or will next months build just include this new vendor.img ?

If we flash this latest vendor will it wipe the system requiring a fresh install or can you just like dirt flash it and your good to go ?
[Pixel C Android Development] frauhottelmann:
When you flash the next 15.1 build you also have to flash the new vendor. No need to wipe anything.
[Pixel C Android Development] Alxoom33:
Hi [MENTION=5480152]followmsi[/MENTION], I just saw this article

https://9to5google.com/2019/08/09/google-pixel-c-update/

Is there anything in the update that we should be using on 16.0, such as the bootloader, which appears to have been updated? Or has everything been incorporated in the latest Lineage updates?

Just curious.

Thanks,
[Pixel C Android Development] drewski_1:
His prior post says it's a new vendor.img which will be in future LOS update
[Pixel C Android Development] Alxoom33:
What about the new bootloader.
[Pixel C Android Development] followmsi:
The same changes for 16.0 .. will be part of next month build.

https://github.com/followmsi/android_vendor/commit/fb1156ec2e753fc7197a8a5dbd417c1aecaa08c1

Same bootloader .. no changes here.

Just unzip the stock factory image ..you can check the version number yourself.
[Pixel C Android Development] Vartom:
Anyone interested in getting started on Pixel C Android 9 on the Nvidia kernel 4.9 and drivers?

In the kernel, need to add support for sound, cameras and sensors (accelerometer, gyroscope, ...).

I do not have enough time for this.
[Pixel C Android Development] john-soda:
Screen brightness so low that the screen turns black.

Thank your very much for your excellent work!!!

I'm enjoying this rom very much!

But maybe for next months build you can set the lower limit of the screen brightness a bit higher?

The brightness of the screen can be reduced so much, that the screen turns black and I can no longer see how I can make the screen brighter again.

I really enjoy, that I can reduce brightness much more than on stock rom (stock rom was always too bright at night.), but if I'm not careful with the brightness slider, I have a real problem.

Thanks for your great work, and I would be happy to see this improvement in the next build.

john-soda
[Pixel C Android Development] ahoneybun:
Works as great as the last build, only thing that doesn't work so far is the Pixel Launcher but thank you for the awesome work at keeping this device up to date!
[Pixel C Android Development] followmsi:
We had similar discussion last lear .. to make it even darker :)

https://github.com/followmsi/androi...fa71aa2#diff-b41e17a6a8a471d4818c58faa070ace2

Tested value "0" in settings too .. still fine to see and adjust brightness again.

Sorry, no changes in this area for the next time.

Cheers
[Pixel C Android Development] john-soda:
when I adjust the brightness to minimum or almost minimum my screen turns completely black! I can't see anything because the screen is off. I attached a picture which shows tha last value before my screen turns black. Slide <1 millimeter to the left -> completely black.
[Pixel C Android Development] Thug Life of the France:
I have the exact same issue.

Though it might be easy enough to fix, wouldn't it ?

Like I messed up with these kinds of config files in the Android 2.3.x days, and it was quite easy.

Maybe now it's more difficult.

If it was an OLED panel, these settings would've been fine, but now they aren't tbh
[Pixel C Android Development] followmsi:
Pls go to .. settings - display - brightness level

Change down to minimum level here - and see the difference to quick settings brightness level.

Not sure why it behaves differently, maybe just a lineage bug.

Not sure if and by when this can be fixed.

Cheers
[Pixel C Android Development] john-soda:
You were right. If I go to -> settings -> display -> brigtness my display doesn't turn black. But I noticed a strange behavior of the slider. Before the slider is completely on the left side, it already has the value zero (see attached pics). The brightness value drops directly from 11% to 0%.
[Pixel C Android Development] followmsi:
Android Pie - September 2019

lineage-16.0-20190906-UNOFFICIAL-dragon.zip

Changes:

- Google (base/general) AOSP security updates -> September 2019

- Latest LineageOS changes for Pie

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] Markeee:
Will there be an auto update available or will we need to manually update ?
[Pixel C Android Development] frauhottelmann:
Lineage 16 is always manual since it's not an official build.
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_ALPHA1

There is no need for a new thread .. and I will not start to continue building AOSP ROM.

But I want to test fresh AOSP 10 sources .. lineage-17.0 will come later this year.

The ROM is fully untested !

It's the first build .. and it's not sure if it will work at all !

As I will have no more time left for Android and testing in the next days/weeks I have uploaded the ROM ..

AOSP_10.0.0_r2_ALPHA1_dragon-ota-eng.followmsi.zip

Changes:

- First build of AOSP 10 sources for dragon device !

- Not tested yet !

The ROM does contain it's own vendor.img !

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy :p
[Pixel C Android Development] ipdev:
Had to try. :D

No go.

Get the Google splash screen and then Waiting for fastboot command....

Clean flash of course.

- flash-all minus system.

- Formate and wipes in TWRP.

First attempt was ROM only.

Second attempt was ROM and Magisk (Canary-Debug).

Magisk detected device as system as root. :confused:

Will try again when I have some time and grab logs.

Installed Lineage 16 (0906) for now.

Lineage is running fine. ;)

Cheers all. :cowboy:
[Pixel C Android Development] Alxoom33:
I take it we need 10.0 gapps?

I'll give it a try when I have a chance [emoji4]
[Pixel C Android Development] followmsi:
Big thanks for testing and your feedback !

I still have not tested myself.

But I checked boot.img quickly .. and it's "system-as-root" partition layout now !

Actually boot.img has a "mini" ramdisk which just contains the init binary.

Before Android 10 the full ramdisk was in boot.img (dragon device) .. now it's part of the system.img.

Seems to be mandatory for all devices running Android 10 ..

https://source.android.com/devices/bootloader/system-as-root

The meaning of a system-as-root configuration differs between Android 9 and Android 10. In an Android 9 system-as-root configuration, BOARD_BUILD_SYSTEM_ROOT_IMAGE is set to true, which forces the build to merge the root file system into system.img then mount system.img as the root file system (rootfs). This configuration is mandatory for devices launching with Android 9 but is optional for devices upgrading to Android 9 and for devices running lower versions of Android. In an Android 10 system-as-root configuration, the build always merges $TARGET_SYSTEM_OUT and $TARGET_ROOT_OUT into system.img; this config is the default behavior for all devices running Android 10.

For "system-as-root" config we need to mount system.img not as "/system" anymore but as root "/" now.

Next step is to change "fstab.dragon" (in system.img now) and set the mount point for system.img from "/system" to "/".

Not sure if missing/disabled DM-verity will still break the boot process.

As you can see .. still a lot to do !

Cheers
[Pixel C Android Development] xda_jm:
Do we know if Lineage 15.1 had a regression somewhere? Seems like the HW acceleration is disabled.

Suddenly I can't play War Robots anymore on my Pixel C.

Using latest Lineage 15.1, latest kernel from followmsi.

Anything I can do to troubleshoot that better except getting logs and sending in a bug report to the Lineage OS guys?
[Pixel C Android Development] 4oo4:
Just read about this NVIDIA Tegra vulnerability in BootRom, I suppose we're out of luck with a patch for that since Google's done with releasing vendor updates? Really wish I knew what the details of it are.

http://cve.circl.lu/cve/CVE-2018-6240