yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] frauhottelmann:
No
[Pixel C Android Development] scoliosis:
Good to know. Thanks. This is occurring in Oreo even with a custom kernel. I wonder if I can run a Pie kernel in Oreo... Only 1 way to find out :D

Edit : Still happens with the Pie kernel when running in an Oreo ROM. It at least boots :) All cores enabled, limited to 286MHz tops and 204MHz running. Wifi doesn't work in Oreo when running Pie kernel though. LOL! Going to wipe and run LOS 16 to see if it still happens.
[Pixel C Android Development] xciteful71:
Video of Pie on Pixel

Question: would someone be remotely interested in posting a video of Pie running on their

Pixel C? It would be nice to see how well it runs/works vs the Oreo ROM.
[Pixel C Android Development] Alxoom33:
Pie runs much better than Oreo on the Pixel C. Try it!
[Pixel C Android Development] xciteful71:
I'm tempted, however, I'm loving my setup right now and everything "just works". ;)

Question 2: Are all of these "KNOWNS" current and up to date for the Pie ROM?

Known issues:

- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.

- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.

- Workaround: On fresh boot you will need to wait a bit longer before you enter credentials.

- The waiting time is required on fresh boot only, the following unlocks are working normally.

If I've overlooked something somewhere and that's already listed, obviously disregard my asking.

Thanks.
[Pixel C Android Development] Alxoom33:
Screen unlock working! Encryption no.
[Pixel C Android Development] xciteful71:
Followmsi has done such a great job on rolling up these ROMs and providing fresh kernels with up-to-date security, fixes, etc., that I'm a little reticent to mess with my daily driver running 15.1. If I had another Pixel C for testing, then I'd be more onboard for giving it a shot.

Again, I'd love to see some vids of Pie running if anyone ever gets around to posting (YouTube/Google has nothing).

Thanks again for you guys and your hard work.
[Pixel C Android Development] chrisonline:
If I want to install the 16.0 image I get following error:

E3004: This package is for device: dragon; this device is .

Update process ended with ERROR: 7

--

Problem fixed with latest TWRP install.
[Pixel C Android Development] scoliosis:
Unfortunately once the battery dropped below 67% the issue reoccurs. It's a little better with Pie, where it would sometimes let you go a bit higher and stay there before throttling back down. Screenshot of what it looks like below.
[Pixel C Android Development] frauhottelmann:
That ist very weird. Maybe your battery has a voltage issue. Maybe it drops to far and the processor is automatically down clocking to avoid a halt.
[Pixel C Android Development] scoliosis:
How would I check that? This is a 4 month old tablet that Google sent to me as an RMA replacement when the previous one's screen died.
[Pixel C Android Development] frauhottelmann:
It's just an idea. Try battery bot (pro) (it's free on F-Droid):
[Pixel C Android Development] scoliosis:
Thanks. I just checked with this and Ampere. They both say at 63%, my voltage is at 3.811V. Temperature is around 20C. I have heard of people needing battery replaced to resolve this but these days I can't even find replacement batteries for the device. Parts seems non-existent almost :(
[Pixel C Android Development] locuturus:
I wonder how much of this is normal. Your case seems extreme to me and is a problem for sure but I think the system does this a little bit normally. See my attached screen shots: I have observed CPU freq throttling as the battery level drops but I have never been sure if it is just my hardware or if it is normal. Back in the Marshmallow days I observed the 4rth CPU core wouldn't be used except by the system, even benchmark apps wouldn't use more than 3 cores. That isn't the case today but I mention it to point out that the vendor files and/or kernel have been changing how the CPU works in big ways for literally years now. I suspect the system has become tuned to be very sensitive to the battery and in your case something about the battery is out of spec. I also suspect the throttling isn't very intelligent because in my case I lose several hundred mhz as the battery drops and this does not recover as soon as I connect to a charger -- the battery must also become charged above the threshold for each freq loss.
[Pixel C Android Development] scoliosis:
I understand if they throttle a bit as the battery drops low. But at 30% used and max throttling is to the extreme. I did notice that going back to 7.1 Nougat it scales much better, able to go down to 45% before mild throttling kicks in.
[Pixel C Android Development] xciteful71:
Not sure if this is insightful or not but I'll post a screenshot of some of the CPU stats.
[Pixel C Android Development] iestyn99:
I've had the same. It is a hardware issue and it persists after a hard reset. The battery is not reporting the accurate charge, thus fooling the CPU to throttle. What you need to do is recalibrate the battery by letting is fully discharge and then fully recharge a copule of times. Be sure to let it charge for several hours, even after it claims to be 100%.

(In my case it started to throttle the CPU at higher and higher battery levels until it fell dead at 99% battery. Total reset and reverting to stock ROM did not help, calibrating the battery did.)
[Pixel C Android Development] scoliosis:
I've done that a few times but no difference unfortunately :(
[Pixel C Android Development] keviiinn:
Anyone having adaptive brightness problems? Looks like a recent update messed it up. this happened often on stock, but this is the first time for me on LineageOS. I used to fix it by clearing the cache, but doing that in TWRP doesn't work.
[Pixel C Android Development] Everio9000:
I don't know why Pixel Launcher does not work in LineageOS 16. It's included on the rom, so I figure that it should works.
[Pixel C Android Development] Alxoom33:
I don't think that the Pixel launcher is included with 16.0. I think only Terbochet launcher is included. I personally use Nova Launcher Prime on all my devices.
[Pixel C Android Development] Everio9000:
In LineageOS 16 r21 launchers included are Quickstep and Pixel Launcher. Quickstep (from Nokia Android One devices) works perfectly but Pixel Launcher is into a Forced Close.
[Pixel C Android Development] 12paq:
Yes, but not specifically on Lineage 16. I am on the latest DU v13.0 RC (Pie) 12-23-18 and Adaptive Brightness swings wildly and seems borked. I haven't checked what parts of DU are if any, compiled from Lineage or AOSP that could have similarly introduced the bug, if indeed it is a bug, but Adaptive Brightness is not working on my device. If it's borked on Pie it's very early yet and since there is no and will be no official Pie, bugs are certainly expected now.
[Pixel C Android Development] Alxoom33:
[MENTION=5480152]followmsi[/MENTION], do you think that the LKT Magisk kernel module is compatible/advantageous to use with your p kernel?
[Pixel C Android Development] followmsi:
Just had a quick look ... No tegra support.

https://github.com/Magisk-Modules-Repo/legendary_kernel_tweaks#compatibility
[Pixel C Android Development] Dhalsim43:
The January patch is available
[Pixel C Android Development] Azure2107:
Have we got the Jan vendor? I can't find it in the downloads link.
[Pixel C Android Development] frauhottelmann:
You can extract it from Google image:

https://dl.google.com/dl/android/aosp/ryu-opm8.190105.002-factory-9f1e2867.zip

Or wait until followmsi uploaded it to the usual place.
[Pixel C Android Development] followmsi:
January 2019 - lineage-15.1

The January 2019 changes for dragon device and kernel have been pushed to Lineage github today.

The next official build will require January vendor.img !

Right now it's not clear by when Lineage will merge the general January security updates.

I have just uploaded the January 2019 vendor.img to gdrive folder too. (Oreo only)

Enjoy :p
[Pixel C Android Development] followmsi:
Android Pie - January 2019

lineage-16.0-20190109-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> January 2019

- Google kernel updates -> January 2019

- Latest LineageOS changes for Pie

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

Enjoy ..:p
[Pixel C Android Development] Vartom:
scoliosis@

What is your tablet revision? This information can be viewed in the fastboot menu, in the line where the bootloader version is specified.
[Pixel C Android Development] CharFalco:
Are all of the things in the OP still issues? Encryption, etc?
[Pixel C Android Development] Alxoom33:
No,lol!
[Pixel C Android Development] frauhottelmann:
Is encryption really fixed?
[Pixel C Android Development] Alxoom33:
Yes and no. I don't believe that my tablet is encrypted. However, you can have a pin, password or pattern lock, and TWRP will decrypt your data in recovery upon entering the pin, password or pattern. I did not test if the data can be re-encrypted in Settings/Security. I think that is a question for [MENTION=5480152]followmsi[/MENTION].
[Pixel C Android Development] followmsi:
I am just online.. :)

If you have "proper" encrypted data partition TWRP will be able to decrypt your partition.

There were still some issues sometimes .. for some users.

But TWRP is not really related to the current Android version installed.

It's is own mini Linux running on recovery partition.

The "proper" encryption is done by system .. lineage-15.1 does encrypt properly but lineage-16.0 seems not.

Encryption needs more testing and takes a lot of time.

As well .. I still need to wait on first boot to be able to unlock my device using pattern.

For this reason the known issues are still valid !

Hope to fix them at some point ..

Cheers
[Pixel C Android Development] Verdera11:
*SOLVED* I changed something I shouldn't touch

Hi, just made a fresh install from official Oreo build (the Google one, not lineage).

I unlocked the bootloader, then installed TWRP and finally last lineage 16 with micro gapps

At the beginning the WiFi was working properly and I could restore the backup from Google. However, since this afternoon (less than 24 from the start) I can't use the WiFi. It says that I'm connected but there's no internet connection. I tried with 2 different networks

Any help??
[Pixel C Android Development] Alxoom33:
That's interesting. Thanks for the information.
[Pixel C Android Development] locuturus:
Hi Vartom, I have a similar issue and my hardware revision is 5. I have had my tablet maxing out at 1720 MHz for a while now

I spent several days recalibrating my batter like so:

(1) run the tablet until it dies (oh lordy this takes a while, and it consistently dies at 10%)

(2) reboot and allow it to die again (the first time I did this it ran for almost 5 min so the shutoff warning was too early)

(3) charge it without turning it on

(4) turn it on, still plugged in, and reboot again for luck

(5) check Kernel Adiutor to see if full 1912 MHz is available to the CPU

(6) if not, try it again

This partially worked after 2 cycles but after a short time it 'recovered' it's earlier opinion of the battery or whatever and I'm still maxed out at 1720 MHz. Turning off 2 cores allows 1912 MHz consistently for me today so I spend a lot of time with a dual core machine...
[Pixel C Android Development] Create God:
Can developers port the 415 version of the gpu driver for pixel c?

Nvidia Shield TV uses the same soc

The GPU driver is 415, the pixel c GPU driver is 361, if you can, thank you very much.
[Pixel C Android Development] Vartom:
This is not possible due to strong binding of drivers to the kernel. Porting the kernel is also very difficult (read as not possible).

---------- Post added at 04:12 PM ---------- Previous post was at 03:55 PM ----------

In doubt, I put 2 revision of the tablet. But you have a fifth, in this case, the battery or its controller is in doubt. It is possible to try to build a special version of the kernel with an attempt to solve the problem with the battery. But there is no complete certainty.
[Pixel C Android Development] Vartom:
Can you check what data this command gives in two cases?

1) when the CPU can operate at high frequencies,

2)*when the frequency of the CPU is limited

cat /sys/class/power_supply/bq27742-0/current_max

ps when on my tablet the battery charge approaches 15%, I observe a frequency limit of up to 1530, while the output of this line gives ~5000000.
[Pixel C Android Development] locuturus:
Woke tablet up from sleep in a cold room:

53% current_max = 4046000 & max freq = 1413 MHz (cold battery)

52% current_max = 4378000 & max freq = 1624 MHz

51% current_max = 4565000 & max freq = 1624 MHz

50% current_max = 4953000 & max freq = 1605 MHz

48% current_max = 5015000 & max freq = 1624 MHz

...

After throwing it on the charger for a bit:

68% current_max = 5718000 & max freq = 1720 MHz (this is now my maximum freq with 4 active cores)

69% current_max = 5783000

70% current_max = 5894000

71% current_max = 5916000 & max freq = 1720 MHz

72% current_max = 5963000

...

86% current_max = 6502000 & still max freq = 1720 MHz

etc

I wouldn't mind this throttling so much if it wouldn't do it when on the charger — seems obvious to me that it shouldn't throttle then but no one asked me when they designed the OS
[Pixel C Android Development] Vartom:
Judging by the testimony of your battery, it is in very poor condition. My battery is 100% charged, giving 8561000. Judging by the comments, these data are close to the calculated ones (9000000).

You can give more output to this command

cat /sys/class/power_supply/bq27742-0/uevent

What version of android and kernel are you using now? I have one idea how to fix this, but it needs to be checked.
[Pixel C Android Development] locuturus:
Last night I fully charged my battery and 99% to 100% took almost 40min so I thought that was weird. uevent reported steadily increasing current_max as it continued charging within the reported 99% but I never reached 8,000,000. However I was surprised to discover I could briefly use 1912 MHz. Once the battery reported 100% and the charger dropped off to ~700mA for maintenance the current_max dropped to the low 7,000,000 range and I was kicked back to 1720 MHz.

This morning I ran some benchmarks, did some photo editing, and really warmed the tablet up on battery power and now current_max is still low (7,326,000 @87% battery) but I have access to 1912 MHz. I don't know what to make of it.

sys/class/power_supply/bq27742-0/uevent
POWER_SUPPLY_NAME=bq27742-0
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_VOLTAGE_NOW=4065000
POWER_SUPPLY_CURRENT_MAX=7302000
POWER_SUPPLY_CURRENT_NOW=-655000
POWER_SUPPLY_CAPACITY=87
POWER_SUPPLY_CAPACITY_LEVEL=Normal
POWER_SUPPLY_TEMP=286
POWER_SUPPLY_TIME_TO_EMPTY_NOW=33840
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CHARGE_FULL=7800000
POWER_SUPPLY_CHARGE_NOW=7214000
POWER_SUPPLY_CHARGE_FULL_DESIGN=9010000

Edit:

Latest LineageOS 16 & kernel from this thread.
[Pixel C Android Development] Alxoom33:
Hi, for some reason I am having issues updating to the latest Magisk Manager Canary build. The Magisk Manager app keeps crashing when I try to update. Anyone have the same experience. It's MM version 6.1.0-1d9c4410(175).
[Pixel C Android Development] frauhottelmann:
Get the arm64 version: https://download.lineageos.org/extras

Only install one.
[Pixel C Android Development] followmsi:
New versions ...

lineage-14.1-20170519-UNOFFICIAL-dragon-followmsi.zip

And the LineageOMS version as well ..

lineageOMS-14.1-20170520-UNOFFICIAL-dragon-followmsi.zip

DOWNLOAD:

https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg

Enjoy :)
[Pixel C Android Development] xda_jm:
Thx.

BTW - you have a Github or Changelog for these new images? At least, to know what has changed?

Thx
[Pixel C Android Development] followmsi:
Will add this to the first page as well ..

The used manifest for this ROM ...

https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1

For the OMS version ..

https://github.com/followmsi/manifests/tree/dragon-lineage-oms-cm-14.1

Except for the kernel, vendor files and the dragon device tree we are using 100% lineageos sources.

The general changes are here ..

https://download.lineageos.org

And when LOS will be official we will use the following trees .. ;)

https://github.com/LineageOS/android_device_google_dragon/tree/cm-14.1

https://github.com/LineageOS/android_kernel_google_dragon/tree/cm-14.1

Cheers
[Pixel C Android Development] xda_jm:
Any ETA on when it will become Official ??? :D
[Pixel C Android Development] followmsi:
Short answer : No ;)
[Pixel C Android Development] ToldYouSo:
My Pixel C reboots when I try to disconnect my VPN connection. LineageOMS-14.1-20170520 (versions before that had same problem) :(
[Pixel C Android Development] followmsi:
Sounds interesting ..

I just made a quick test ..

Connect via openvpn .. staying online for a short while and disconnect.

Did this a few times now .. no reboots or problems.

Spontaneous reboot sounds like kernel .. we may make a test kernel for you.

Would be interesting if you use stock kernel.

What VPN client are you using ?

It reboots always if you disconnect .. also on a quick connection for a few seconds/minutes ?

EDIT:

Pls install this kernel tegra-3.18_kernel_dragon_v170522_lineageos-followmsi.zip via TWRP and reboot into system.

Test VPN again .. still reboots ?
[Pixel C Android Development] ToldYouSo:
VyprVPN... It has a L2TP/IPSec psk security...

It connects fine. Also works while browsing. But the second I want to disconnect my device shuts down instantly. Every time I try it. Kernel I tried: tegra-3.18_kernel_dragon_v170512_unicorn-xceed-followmsi.zip

But if it is a kernel problem then shouldn't it also crash when I use VPN with the same kernel on a stock factory image?
[Pixel C Android Development] followmsi:
Yes, if it's a kernel issue, the same kernel should also unexpected reboot on stock image. If it's just a kernel issue.

No VPN reboots on stock image with the same kernel ?

Did you test openvpn or other clients too ?

Reboot too ?

Needs to be clarified if it's a LOS bug .. logs ..etc. ..
[Pixel C Android Development] ToldYouSo:
With the tegra-3.18_kernel_dragon_v170522_lineageos-followmsi.zip it does not crash! :good:

Can not get a log because the crash is so sudden. Everything is fine up until the crash, logs show nothing. Stock LineageOS kernel and tegra-3.18_kernel_dragon_v170512_unicorn-xceed-followmsi.zip are the ones crashing.
[Pixel C Android Development] followmsi:
Good to know .. the lineageos kernel (170522) will be the future stock kernel for LOS on dragon ..

The current "stock" kernel is the same like v170512.

Pls install xceed kernel 9.38 and 9.40 .. same reboot problems with vpn ?

Thx
[Pixel C Android Development] ToldYouSo:
I'd be happy to but I'm not sure where to find those versions?
[Pixel C Android Development] cam30era:
Go here > https://www.androidfilehost.com/?w=files&flid=172973
[Pixel C Android Development] ToldYouSo:
9.38: No VPN crashing, but also no F2FS support? Only boots on EXT4 /data partition.

9.40: Also no VPN crashing, but also no F2FS support?
[Pixel C Android Development] followmsi:
Ok .. the reboot issues seems to be related to the merge of the kernels ..

Will check this ..

Not sure about F2FS support ..
[Pixel C Android Development] followmsi:
[MENTION=4657624]ToldYouSo[/MENTION]

Pls test tegra-3.18_kernel_dragon_v170524_unicorn-xceed-followmsi.zip

Still reboot issue on VPN closing ?
[Pixel C Android Development] followmsi:
Just as an update for you !

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

Still some steps to do ... but we are coming closer. :)
[Pixel C Android Development] ToldYouSo:
Yes it has the same issue :(
[Pixel C Android Development] followmsi:
Pls run in terminal app with root .. using the same kernel from today.

cat /proc/kmsg >> /sdcard/Download/kmsg.log

Start VPN

Stop VPN

System reboots unexpectedly

Afterwards pls send me the kmsg.log file from your Download folder.

Thx

EDIT:

Pls test with the following both kernels .

tegra-3.18_kernel_dragon_v170524_unicorn-xceed-followmsi.zip

tegra-3.18_kernel_dragon_v170524_test.zip

Thanks !
[Pixel C Android Development] keviiinn:
On 16, do we get updates from the OS OTA or from this thread only?
[Pixel C Android Development] Alxoom33:
This thread, only.
[Pixel C Android Development] bbawden:
Hoping someone can help me out here.

I decided to start from fresh, so I installed the latest factory image from Google, flashed that, and it booted up to stock (albeit bootloader still unlocked) with no prob.

I rebooted to bootloader and flashed TWRP.

Booted to recovery fine.

I installed Lineage 16 by copying over the zip and installing via TWRP.

Upon reboot, the Lineage logo shows, but then it reboots to recovery.

Can anyone advise how I fix this? I'd much rather have Lineage than stock.
[Pixel C Android Development] frauhottelmann:
Die you format data?
[Pixel C Android Development] b8842dc0:
I'm not clear on the status of encryption with LOS 16 and the Pixel C. But I wanted to note that my other device is a Nexus 6. The Nexus 6 was also having encryption issues in the LOS maintainer's LOS 16 development builds. But on December 22, he posted:

Then, on December 25th, in reply a question, where somebody asked if he had fixed it just for the Nexus 6, or in general, he replied:

I don't know what he did to fix it on the Nexus 6. But just wanted to reference this, if the problems were/are similar.

Thanks!
[Pixel C Android Development] bbawden:
Yes. I'll give it another go. I'm going to flash stock again, then do the following steps.

Please advise if any are incorrect:

1. Reboot to bootloader

2. Flash TWRP

3. Reboot to recovery

4. Format data and wipe partitions

5. Reboot to recovery again (unnecessary?)

6. Copy over lineage and gapps zip files to device

7. In TWRP use the Install menu to flash lineage and gapps zips

8. Reboot

Does that look OK?

Thanks

---------- Post added at 02:16 PM ---------- Previous post was at 02:09 PM ----------

One thing to note. Sometimes when recovery boots, it asks for an encryption password. But I haven't encrypted it.

---------- Post added at 02:29 PM ---------- Previous post was at 02:16 PM ----------

Working now.

I think I hadn't properly formatted data the first time.

Thanks.

---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------

Maybe I spoke too soon.

It now shows the initial setup screen where you select the language, but as soon as I choose language and tap next, I get the system warning that "Pixel Setup keeps stopping" and I can't continue.

Maybe I'll flash Lineage 15 first.

---------- Post added at 03:06 PM ---------- Previous post was at 02:32 PM ----------

OK, fixed the above. I had installed MindTheGapps instead of OpenGapps.

OpenGapps works.
[Pixel C Android Development] Alxoom33:
Open gapps worse for me. Did you install the correct version?
[Pixel C Android Development] bbawden:
I think I've still got some kind of issue.

The ROM has installed OK and my initial setup is complete, but when I go to settings it still says "Tap here to complete setup" or something similar.

When I do that, it goes to the setup wizard where you tell it whether you want to copy data. No matter which option I select it just closes and I get the error that the app keeps closing.

I think it's a problem with OpenGapps, as it also won't let me use the Google Now launcher.

I selected ARM64 and Android 9. I have tried nano, stock, and full and none of them seem to work.

Can anyone advise what I can do?

Thanks