yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] locuturus:
I have noticed this as well. One avenue to explore might be using Taskbar and enabling its navigation buttons option? I just tried that and it's admittedly not perfect, but Taskbar's overview button works so there may be a different way to manually add the overview button to the navigation bar?

Also if you have it the keyboard alleviates this problem IMAO thanks to the navigation shortcuts.
[Pixel C Android Development] Vartom:
I already wrote a way to fix

https://xdaforums.com/showpost.php?p=78772980&postcount=15
[Pixel C Android Development] followmsi:
How to include into ROM .. overlay ?
[Pixel C Android Development] followmsi:
April 2019 - lineage-15.1

The Google April 2019 changes for dragon device have been pushed to Lineage github today.

There are no kernel updates this month.

Google added new Bluetooth driver.

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

The next official build will require April vendor.img !

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

Enjoy :p
[Pixel C Android Development] Monazite:
About the disappeared recents button...I've noticed Google has fixed it on Android Q. We can waiting for next major update patiently.
[Pixel C Android Development] Vartom:
Tried through the overlay, did not work.
[Pixel C Android Development] followmsi:
Android Pie - April 2019

lineage-16.0-20190404-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> April 2019

- Merged Google device changes for dragon into Pie -> 8.1.0_r63 (new Bluetooth driver)

- No Google kernel updates this month

- Latest LineageOS changes for Pie

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

Enjoy :p
[Pixel C Android Development] Alxoom33:
New 16.0 ROM working great!

Question: is there an easy way of clearing ram when this tablet slows down?

As the Pixel C only has 3 gigs of RAM, slowdowns happen. [emoji1]

Thanks
[Pixel C Android Development] frauhottelmann:
Anyway. Ich was wondering why people were experimenting with ADB commands for the buttons. I have all the buttons since disabling the swipe gesture.

I checked and it doesn't appear with every home button layout! Don't know why though.
[Pixel C Android Development] Vartom:
It is strange that you have all three navigation buttons without additional intervention. How did you install the system?
[Pixel C Android Development] Dhalsim43:
Pixel C has 3 gigs of RAM
[Pixel C Android Development] cartman56:
Any chance that 16.0 going to be official?
[Pixel C Android Development] Alxoom33:
Right you are. The Pixel C has 3 gigs of Ram. But I don't think that makes a difference in my question, since with use the Ram is used up and the tablet slows down. So, as I asked before, is there an easy way of clearing Ram when the tablet slows down?
[Pixel C Android Development] Dhalsim43:
Use recent apps button then clear all
[Pixel C Android Development] cartman56:
Greenify app
[Pixel C Android Development] Alxoom33:
That doesn't do much. Imho.
[Pixel C Android Development] frauhottelmann:
I did a normal installation. Nothing special. But my other Android 9 phone behaves the exact same way...
[Pixel C Android Development] _benedict_:
Hi!

I tried to sideload the last version lineage-16.0-20190404-UNOFFICIAL-dragon.zip and I got an error 7 in TWRP. Does anyone know what I should do?

Thank you for all the great work,

Best,

benedict
[Pixel C Android Development] Alxoom33:
Try flashing it in TWRP.
[Pixel C Android Development] _benedict_:
It worked like a charm, thank you! Out of curiosity, what is the difference between sideloading and flashing?
[Pixel C Android Development] Alxoom33:
Sidloading using ADB functionality, usually of an outside device to install a file in a device. Flashing, by contest, involves installing a zip file using recovery internal to the device. They are different processes that achieve similar results.
[Pixel C Android Development] victorhooi:
I have a Pixel C device currently on stock 8.1.0.

I'm reading through this thread, and excited to try this out. I just wanted to confirm a few things.

So it seems like installing TWRP. is the first step. I can do this from stock, once I unlock the bootloader, correct?

Then I need to boot into TWRP and wipe system, cache, dalvik and data - and wiping data should automatically remove encryption, correct?

(Curious - Is getting encryption to work a possibility, or are there some fundamental limitation here?)

Then I install:

lineage-16.0-20190404-UNOFFICIAL-dragon.zip

OpenGapps (Is ARM64, 9.0, Stock an appropriate configuration?)

Magisk - Does it matter if I install version 18.1 or 19.0?

Are there any other steps I need to do?

And any other caveats or things I should know? How have people found this versus stock Android 8.1?

(I noticed that it says pattern/PIN/Password may not work - does that mean I can't set any kind of protection on the device?

Or is pattern the only safe option, with the caveat of a long wait on first boot? Is long wait here a few seconds, 20 minutes, an hour, or longer?)
[Pixel C Android Development] drewski_1:
I have Magisk 19 without issues.

That Open GApps should be fine; I use Super while trimming a few things with config.

I have PIN. No probs so far . . . knock on wood.

Maybe 10 minutes max for first boot?
[Pixel C Android Development] frauhottelmann:
Yes, first thing is unlocking the bootloader. Then install TWRP. You have to format, not wipe, the data partition. That will wipe your storage as well. You can then either ADB sideload Lineage, GApps and Magisk or copy the zips after formating. If you don't need all Google Apps you can use a smaller package and install the apps you need afterwards. Encryption is not working right now. Pattern unlock is working for me.
[Pixel C Android Development] pierrebe:
Hi. Pixel C with lineageos 15.1. Only Sound with netflix, no pictures. I tried what customer service from netflix recommende to do without success. I tried with the original kernel and with another one (tegra-3.18_kernel_oreo_dragon_v190402_unicorn-xceed-followmsi)

Thanks for any help
[Pixel C Android Development] Karlmay70:
I had the same problem with Netflix. This fixed it for me.

Security - screen lock - off
[Pixel C Android Development] frauhottelmann:
The problem should be live display. Netflix probably thinks that changing the white balance ****s with their DRM.
[Pixel C Android Development] pierrebe:
You're right. I disable live display and now it's ok!

Thanks a lot
[Pixel C Android Development] Boal:
I had that, too. Got annoyed, left the tablet attached to the charger for a few weeks without using it, and then the issue had fixed itself. I'm sure it's something about the battery.
[Pixel C Android Development] killer33:
Pixel c

This was not a user error, this was due to the google lock bug.

Had it even after ik did a full format of all storage parts before the falshing.

It happed due to de lock screen with passwor/pin setup some times and some times it kept saying word code/password even if it was the coorect one because it unlocked 10-15 minutes before with the same code/password.

For the time beeing i have nopin on the pixel c and the stock google rom back on it.

Goolgle also puled the suport plug for the pixel c. witch is to bad.

waiting for samsung to come clean about the wifi designfault in the S5E wifi/lte tabs for europe.

Witch can have an ratter furstrating issue when holding the tablet in landscape mode with the cammera to the left then the wifi conection can be teriminated and only comes back if you place the tablet the otherway arround.
[Pixel C Android Development] followmsi:
May 2019 - Lineage-15.1

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

Google released a new bootloader this month .. bootloader-dragon-google_smaug.7900.139.0.img

The next official build will require May vendor.img !

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

Enjoy :p
[Pixel C Android Development] Rox598:
Was there any major changes made to the bootloader? Not often they do that especially for this device.
[Pixel C Android Development] Vartom:
CVE-2018-6243	A-72315075*	EoP	High	Pixel C TrustZone

https://source.android.com/security/bulletin/2019-05-01#nvidia-components
[Pixel C Android Development] followmsi:
Android Pie - May 2019

lineage-16.0-20190510-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> May 2019

- Google kernel updates for dragon -> android-8.1.0_r0.134

- Re-enabled WifiDisplay (needs testing) -> thanks to [MENTION=4130080]b1ggjoe[/MENTION]

- Latest LineageOS changes for Pie

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

Enjoy :p
[Pixel C Android Development] Alxoom33:
Thanks! For 16.0 do we need to install a new bootloader?

Thanks,
[Pixel C Android Development] followmsi:
Recommended but not required.. still need to update my bootloader. :)

Running latest build with Magisk 19.1 - no (new) issues so far.

For me unlock pattern still needs waiting time on fresh boot.

Enjoy your weekend ..
[Pixel C Android Development] EnginEAR:
Thanks!!!

Thank you very much!!!
[Pixel C Android Development] mightywhites29111971:
Not sure if the issues I am having at the moment are related to this ROM. I am on 15.1 and a couple of days ago installed the latest update. Since the update I have been getting split screen issues. The problem I am having now is that the screen off, and it appears that the tablet is powered down but I am heating noises from the tablet which makes me think it powered on and the screen is not working. The LED's are fully lit at the back and multi-coloured. Does anyone know how I can fix this?
[Pixel C Android Development] m+a+r+k:
It's not likely this is one of those things you are going to fix fiddling around with the limited things you can fiddle with!

The simple answer is to wipe it clean in TWRP and install 16.0 from scratch.

Or put back that nandroid backup you made before you updated it.

You did make a nandroid backup didn't you?
[Pixel C Android Development] mightywhites29111971:
I did make a back up but I cannot get into twrp. The tablet is still on as I can hear email notifications, but the screen is not on.
[Pixel C Android Development] ipdev:
Sorry to say but, sounds like a hardware problem.

Split screen issue. Crappy design and the screen ribbon cable.

No backlight issue. Hardware, Firmware or Software. Not sure if Google ever pined it down or if it was a combination.

Google's solution to both issues was to replace it under warranty. If you were out of warranty, you got a polite fu*k off.

I run into no backlight if I power mine off too long or use a magnetic cover.

For me, a reboot to the boot menu and then system normally works. May have to do it a few times.

It's been awhile since I searched about it. I know there were a few threads here on xda about it.
[Pixel C Android Development] mightywhites29111971:
I've finally got the screen on. Regarding your message will a clean install of 16 make a difference as you make it sound like it's a hardware issue and is not ROM related?
[Pixel C Android Development] ipdev:
I doubt it. If it's working now then your install probably isn't the problem. For me it's the same regardless of what is installed, Stock or Custom.

Thankfully I do not have the split screen issue but, I expect one of these days my backlight will just not work. Hopefully not anytime soon.
[Pixel C Android Development] mightywhites29111971:
OK, thanks. Will contact Google as I think it's still under warranty.
[Pixel C Android Development] ipdev:
Best Wishes and Good Luck. :good:

Keep in mind, it's generally more fun kicking a table leg with your little toe, then dealing with Google. :)
[Pixel C Android Development] mightywhites29111971:
You were right, Spent an hour with them on Google chat going through the same old crap (hard reset, wipe, etc) to be told my tablet was out of warranty (even though I had a letter when my first one was replaced due to another hardware fault a year ago that my warranty would be extended). Basically told me to go fix it myself.
[Pixel C Android Development] Alxoom33:
Hi, is there a way of backing up and restoring the backed-up home page with the Trebochet launcher, like I can do with Nova Prime?
[Pixel C Android Development] drewski_1:
Not sure, but maybe TiBu saving data for it?
[Pixel C Android Development] locuturus:
(Emphasis mine)

I find that connecting to my Samsung 'Smart' TV results in a soft reboot just as the display contents would begin to transfer to the TV. Is this enough to go on or would someone like a logcat?

BTW after a soft reboot my PIN works immediately without having to wait for the library(ies) to do whatever it(they) does(do) to make us wait after a full reboot. Just an aside I thought was interesting. The ROM is stable enough that I haven't had occasion to experience many soft reboots :)
[Pixel C Android Development] followmsi:
Pls post logs.

Not sure if we can improve the situation here.

"Native" ScreenCast/MiraCast support has been dropped in Pie.
[Pixel C Android Development] locuturus:
Here ya go.
[Pixel C Android Development] followmsi:
Thanks for the logs !

As expected..

05-31 12:22:32.789 411 517 D SupplicantP2pIfaceHal: stopFind() completed successfully.
05-31 12:22:32.789 411 517 D SupplicantP2pIfaceHal: leaving stopFind()
05-31 12:22:32.789 411 517 D WifiAsyncChannel.WifiP2pService: replyToMessage replyToMessage recvdMessage=139268 sendingUid=1000 sentMessage=139270
05-31 12:22:32.798 308 352 E MediaPlayerService: listenForRemoteDisplay is no longer supported!
05-31 12:22:32.801 411 434 E RemoteDisplay: Media player service rejected request to listen for remote display '192.168.12.128:7236'.
--------- beginning of crash
05-31 12:22:32.806 411 434 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.display
05-31 12:22:32.806 411 434 E AndroidRuntime: java.lang.IllegalStateException: Could not start listening for remote display connection on "192.168.12.128:7236"
05-31 12:22:32.806 411 434 E AndroidRuntime:	at android.media.RemoteDisplay.startListening(RemoteDisplay.java:121)

05-31 12:22:32.798 308 352 E MediaPlayerService: listenForRemoteDisplay is no longer supported!

For QCOM devices there are some custom solutions available .. not sure about Nvidia.

This will take longer .. if we are able to fix at all.
[Pixel C Android Development] followmsi:
June 2019 - Lineage-15.1

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

The next official build will require June vendor.img !

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

Enjoy :p
[Pixel C Android Development] roblav96:
Enjoying so very much! ?

Much appreciated!
[Pixel C Android Development] followmsi:
Android Pie - June 2019

lineage-16.0-20190604-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> June 2019

- Google kernel updates for dragon -> android-8.1.0_r0.135

- Latest LineageOS changes for Pie

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

Due to holiday season the July builds will be delayed !

Enjoy the summer :p
[Pixel C Android Development] locuturus:
Tethering

This is a feature request I suppose. Would it be possible to enable Android's normal tethering features? The tablet has no cellular radio but there are other reasons to be able to generate a hotspot.

◦ With this feature I could connect to $$$ in-flight WiFi and share the connection to my phone over Bluetooth.

◦ Or I could connect to Ethernet at a hotel and hotspot to the rest of my devices (some hotels have a device limit).

◦ Speaking of hotels I could bring my phone, a Chromecast, and this tablet and use the tablet's hotspot to allow the phone to setup the Chromecast and also screen mirror to the Chromecast (this is still relevant in some situations and serves as a hacky replacement for Miracast)

◦ There are also times when I want to set up a LAN with or without internet access and if the tablet's bigger battery is available that would be my first choice obviously

◦ Finally there are lots of times USB reverse tethering could help me out and this is hard to accomplish even with root but having USB tethering controls enabled helps

Cheers
[Pixel C Android Development] Talonette:
Thank You so much for keeping this ROM updated :)
[Pixel C Android Development] followmsi:
Normally there is no time left for any feature requests .. but it seems I have a good day. :o

Applied the change for all Pie branches now. (AOSP, AICP, RR and PE)

lineage-16.0 branch as example ..

https://github.com/followmsi/androi...mmit/d02f8c7f491450ff9ad91ebdeaaf4cff62e8ee81

As well I was able to trigger a new build ..

lineage-16.0-20190606-UNOFFICIAL-dragon.zip

Changes:

- Added tether config -> Needs testing !!! (maybe we need kernel config change too .. etc.)

No more Lineage updates till end of July .. at least !

Enjoy the summer :p
[Pixel C Android Development] Alxoom33:
[MENTION=5480152]followmsi[/MENTION], I flashed the update, thank you!Two questions:

1. What is the purpose of adding tethering, when the Pixel C has no radio. Can we rebroadcast the home or office wifi internet signal? When I tested the tethering feature, my phone reported it connected, but had no internet signal.

2. Is the P Kernel that you released a few days ago better/more up-to-date than the kernel included in this ROM, or should we stick with the included kernel?

Edit: I flashed the 6/4/19 kernel. Please let me know if I should revert to the included kernel.

Thanks,

Have a great weekend!
[Pixel C Android Development] frauhottelmann:
When you read the post he quoted, you'll understand why the tethering feature was added ?
[Pixel C Android Development] Alxoom33:
Ahhh...I never opened up the spoiler. Good to know. But does it work, as theorized in the feature request?
[Pixel C Android Development] followmsi:
That needs to be tested :)

No kernel changes in last release, just tethering config changes only.

As always - the "standard" google kernel is part of each ROM, if you like you can install "unified" kernel on top.

Cheers
[Pixel C Android Development] locuturus:
Thanks so much! I'll be testing this tonight at my hotel appropriately enough :D

Have fun!
[Pixel C Android Development] Alxoom33:
Updated 16.0 Rom and the unified [MENTION=5480152]followmsi[/MENTION] Pie kernel running very smoothly. Thank you!
[Pixel C Android Development] locuturus:
Tablet is able to generate a 2.4 GHz hotspot. 5 GHz fails to start. However it can only operate in offline LAN mode so forwarding an Ethernet connection to the hotspot does not work but the local LAN does. Bluetooth tethering results in loss of pair whether offline or not so that isn't working at all. USB I haven't had occasion to try. So certain sync apps and Chromecast can work with the LAN and that's a good start :)
[Pixel C Android Development] JohnnyChim:
Just moved from 15.1 to 16.0 for a few hours.

It is laggy comparing to 15.1. Hope there will be improvement in the future.
[Pixel C Android Development] followmsi:
Thanks for testing.

Not sure if "bridging" ethernet will work .. most probably you will need app or use some terminal commands to make it work, if at all.

Google has disabled bluetooth NAP service some time ago - no idea if this is related to the Bluetooth tethering problem.

https://github.com/followmsi/androi...74c119b#diff-9abfc3fa0a586782b875ee02ad45dcd8

We can re-enable for testing .. maybe more changes are required.

I have no time for testing right now .. maybe next month.

Cheers
[Pixel C Android Development] locuturus:
Did something change in Android generally or is this yet another 'Dragon' thing? This used to be normal Android behavior — a phone connected to Ethernet via USB OTG cable used to have no trouble sharing it over a WiFi hotspot.

Cool beans. Enjoy the summer :)
[Pixel C Android Development] 4oo4:
Anyone know if encryption is working on the 9.0 builds? Really excited to try it but was waiting on that.

[MENTION=5480152]followmsi[/MENTION] Thanks for everything and enjoy the break
[Pixel C Android Development] barbara-luise:
[MENTION=5480152]followmsi[/MENTION]: thanks for the great work that keeps our pixel c alive! Will there be an official lineageos 16 in the future? If so, when can we expect it?
[Pixel C Android Development] followmsi:
Aa said .. not sure - hope we get Android "standard" working on dragon too.

Made one more change today ... we will see the result next build - End of July.

https://github.com/followmsi/androi...mmit/99e008766df64e963ea34687c771e2e3603717cc

Thanks .. Enjoy the summer as well :)
[Pixel C Android Development] followmsi:
No device changes in terms of encryption .. still no progress here.

As it looks like it will take longer .. just no time left to look into this (complex) stuff.

No .. main reason is encryption and some other minor stuff - same problem - no more time left for Android.

Not sure if and when the dragon device will switch officially to lineage-16.0 branch.

Maybe someone else is joining the team who has more time left to work on the open issues.

Sorry.. no better news on this topic.

Enjoy the summer :p
[Pixel C Android Development] reject519:
Is anyone else having issues with Netflix? I have audio, I can see the Netflix logo / show name, but there's no video from the show itself. I didn't have any problems until about a month ago.
[Pixel C Android Development] frauhottelmann:
Turn live display off ?
[Pixel C Android Development] Alxoom33:
Looks like Google is no longer supporting the Pixel C. No security update for July.

https://www.androidpolice.com/2019/...tablet-may-not-get-any-more-security-updates/
[Pixel C Android Development] b8842dc0:
Three Cheers for Lineage!
[Pixel C Android Development] m+a+r+k:
If Google don't provide security updates, they can't be incorporated in Lineage.
[Pixel C Android Development] b8842dc0:
Can you explain further? I'm still using a Nexus 6 with Lineage 15.1. It currently has the June 5, 2019 Google security patches.
[Pixel C Android Development] frauhottelmann:
OS will be patched with the usual AOSP patches. Only vendor stays at a certain patch level.
[Pixel C Android Development] victorhooi:
I have a Pixel C running the LineageOS 16 (4 April 2019) builds.

When I go into Settings, and the LineageOS Updates - it shows no new updates found. Is that to be expected?

What is the best way of updating to the latest July builds?
[Pixel C Android Development] frauhottelmann:
Yes. This is not an official build, that you can get from the Lineage servers. If you want updates, you'll have to get them here.
[Pixel C Android Development] drewski_1:
download and flash in TWRP. dirty should be OK. update GApps, while you're in there?
[Pixel C Android Development] Alxoom33:
[MENTION=5480152]followmsi[/MENTION], now that google no longer providing security updates. Will you/ Lineage continue to update the Pixel C with kernels and Lineage 16.0?
[Pixel C Android Development] followmsi:
Like mentioned before .. Google vendor updates have been stopped in June 2019.

For this reason all the new ROM stay at vendor security patch level of June 2019.

The base AOSP part will be updated to latest month, like for all other devices too.

Kernel.org seems to have stopped working on 3.18.x kernel.

As well Google stopped Dragon kernel updates in June 2019.

No more kernel updates for the next time.
[Pixel C Android Development] followmsi:
Lineage-15.1

Google has stopped the support for Dragon device in June 2019.

For this reason the June 2019 vendor.img will be used for all upcoming lineage-15.1 builds in the future !

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

lineage-16.0-20190721-UNOFFICIAL-dragon.zip

Changes:

- Google base AOSP security updates -> July 2019

- Google vendor security updates for dragon device -> June 2019 (based on final vendor.img)

- Latest LineageOS changes for Pie

- Some more "tethering" config

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

Enjoy :p
[Pixel C Android Development] narse:
Just dirty flashed over the previous version and all working well so far.

Thanks for the update.
[Pixel C Android Development] Markeee:
Did a clean install from stock nice job running good thanks for the update :)