yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] ipdev:
If I remember correctly, there is only one connection for the screen. These devices are glued together so, opening them up to check a connection is a little tricky.

Use a heat gun very carefully around the edge of the screen to heat up the glue. Cracks/breaks can happen if the glass is heated too fast or hot.

Outside of that, the screen cable is glued into the screen assembly and there are a few pinch points that can/may/will eventually break the wire. This normally results in a split-screen showing static on the right(?) side if I remember correctly.

It's been awhile since I looked this all up. (2ish years ago?) Google Support kicked me between software and hardware then politely told me to fu*k off since I was out of warranty. ;)

If it is just the backlight, you might be able to get it to turn back on by a dumb reboot sequence. This will require a flashlight to illuminate the screen. (Angle and brightness will make a difference. A dimmer flashlight actually works better.)

Boot into system (rom)

Power button-> Restart

When it powers down for the reboot (Before it actually restarts)

- Press Power and Vol Down to reboot into the boot menu.

- Then choose Reboot to Recovery

- In recovery Reboot System

The backlight will turn on during the reboot system step from recovery. If not, you may have to repeat the steps.

Save for a few weeks ago, it was 4/5 months ago that I had to reset mine to get the backlight working again.

The notes I made (added) and what worked for me this last time also.

- Flash factory image.

- Skip through Setup and reboot.

(Pwr Vol-)

- Boot menu -> Reboot into Android Recovery

(Stock recovery. Press Power and then toggle volume down and up to show the options.)

- Run graphics test

- Reboot system

For me, normally, powering off the device too long or using a magnetic cover/case will cause the backlight to not turn on. So I just turn off the screen and let it go into deep sleep mode.

(Not sure what caused my problem last month.)

Hope it helps a little bit.

Cheers. :cowboy:
[Pixel C Android Development] m+a+r+k:
Does this ROM have the selection to use "Device MAC Address" rather than the default "Randomised MAC Address" under wifi settings?

Looks like Pixel Experience doesn't and I need this option.

Thanks you.
[Pixel C Android Development] tschmid:
Afaik same kernel so i would say no

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] m+a+r+k:
Thanks, :(
[Pixel C Android Development] Thug Life of the France:
Sad to see that the Pixel C is starting to show it's age regarding available RAM.

Could you check how to improve performance with, for example compiling the kernel with zram, optimized I/O settings ?

On my own, with "No launcher", "Minimal keyboard", nano Gapps, most **** uninstalled...

It's better, but not snappy as it was when I bought the tablet.

This is my second Pixel C, as the first one I got back in january 2016 got screen issues in summer 2018, but since stock 7.1, it strted feeling quite slow imo

When you have time, if you could make more optimized ROMs, and if all the other Pixel C savy people around there know how to unlock dat ****, just tell us ;)
[Pixel C Android Development] locuturus:
I have a Galaxy Tab S6 and I like it. Samsung adds some great bells and some terrible whistles but on balance, it's a good upgrade. The OEM keyboard layout is worse than Pixel C's and I really like the Pixel C folio design compared to a loose floppy keyboard hinge but that's a personal preference thing.

---------- Post added at 08:03 PM ---------- Previous post was at 07:48 PM ----------

I personally run the optional kernel by [MENTION=5480152]followmsi[/MENTION] which allows me to change IO to fiops. Placebo is hard to account for but I have had great success with fiops. I also currently run a pretty large zram (1024), with swappines 100, dirty ratio 50, dirty background ratio 1. Does this help? Who knows! But I was inspired by this article: https://haydenjames.io/linux-performance-almost-always-add-swap-part2-zram/

I do this even though zram consumes extra CPU because I use tablets like small computers and run multiple resizable windows all the time. So I probably need RAM more than I need an extra 5 or 10% of CPU performance.
[Pixel C Android Development] Thug Life of the France:
Honestly someone should do an article regarding how to get the most out of the Pixel C.

A lot of people would like it
[Pixel C Android Development] 122877087:
It fixes the open gesture, and the navigation bar is abnormally high
[Pixel C Android Development] xda_jm:
For those have the 3d Accel being disabled after a short while (Battery at 75% or higher), [MENTION=5480152]followmsi[/MENTION] sent me an article (link - sorry, I lost it) where it is mentioned that the system needs to "identify the max and min loads of the battery" first to be able to function correctly.

So - it does work. However, I had to completely discharge my battery and let the device shutdown by itself. Having low battery only and plugging in the charger at 20% didn't work for me.

Just started War-Robots, and went on the main screen and let it drain the battery for 10hours made the trick.

After that, on charger - and the next time I played, I could even have 3D accel at 15% battery :}
[Pixel C Android Development] 122877087:
The abnormality of the gesture navigation bar should be caused by a dpi below 320, and the dpi adjusted to above 320 is normal
[Pixel C Android Development] NYCHitman1:
I picked one up last week and I'm very much enjoying it. Love the power and performance this thing delivers. I do not use or own the hardware keyboard, so that's not an issue for me.
[Pixel C Android Development] xda_jm:
How about installing Lineage on these devices? Or alternative ROM's?
[Pixel C Android Development] NYCHitman1:
There's no custom ROM scene on the device, if that's what you're asking. However, I'm OK with that.
[Pixel C Android Development] xda_jm:
Too bad. Hate it when I don't have control over my device. Well, still have to use that one, and will have to seek for a device I can put on a ROM years after its release and the Manufacturer OES/EOL'd it
[Pixel C Android Development] locuturus:
I am an unusual customer in the grand scheme of the cheap media-consumption Android tablet space because I use mine as if they are small laptops. In other words I am exactly who Samsung should be courting. But there are 2 different Samsung teams and they are not talking to each other. I'll call them Samsung_Phone and Samsung_DeX.

Samsung_DeX understands big screens, mice, keyboards, and trackpads. Lovely, just what I want. Their product, DeX, has a long way to go but it's already nice and on a good trajectory.

Samsung_Phone understands touchscreens; big friendly UX elements; in-house input devices (S-Pen); and "gimmicky" branding features like redundant apps, improved split-screen/windowing, dual-audio, renamed features like Miracast -> Smart View, etc. They do not understand generic input devices, they do not understand large screens, and they do not respect AOSP advancements over time.

Because Samsung_DeX builds on top of what Samsung_Phone gives them, we end up with weirdness:

<> Like a full-size 16:9 widescreen tablet set up at both a hardware & firmware level as portrait by default (check out the camera placement, volume button operation, light meter location (my thumb is always covering it & dimming the screen), occasional apps wanting rotate to the default, niche input devices like Wacom tablets relying on default orientation, etc).

<> Or how the Samsung_DeX team understands a mouse has multiple buttons which can do useful things like open context menus, but if you exit DeX mode those middle and right mouse buttons change to legacy, API 9 ish, Android behavior of HOME and BACK respectively. Apparently, because Samsung_Phone hasn't bothered to check in with AOSP's changes to mousing in the last 300 years*. So not only does right-click stop working outside of DeX it now results in the BACK command. This context shifting is bad, full stop. It also is unecessary if Samsung_Phone would just get with the program and use AOSP correctly.

I should call it short though, and /end-rant early. There is so much to love about it as well, I just really get bothered by the split personality of the design.

*some artistic license might be at play here
[Pixel C Android Development] followmsi:
One more build .. and finally tested myself.

I like it .. nice bootanimation :)

crDroidAndroid-10.0-20200227-dragon-v6.3.zip

FraEgg made a "workaround" patch for crashing crDroid settings on non-telephony devices.

Seems to work well - Thanks to FraEgg !

As well I have added kernel hack from Team Mokee for Wifi/Bluetooth MAC addresses.

Disabled DM-verity in kernel too, cleaned init.rc script and removed some encryption related blobs.

Same changes will be part of next lineage build too.

I will run/test crDroid for the next time .. still not sure about regular/monthly builds for dragon.

Cheers
[Pixel C Android Development] 12paq:
Thanks for the fixes!

Been running this as a dd since the first test build. A really nice rom for dragon.
[Pixel C Android Development] Thug Life of the France:
Hope it'll happen before march, because February's build wasn't all that innovative

These changes are bringing quite a lot to the table, very nice !

Hoping you'll be able to fix the 3D acceleration being quite hit or miss...

Looks like the more and more I use the tablet, the more and more it lags.

I'm also a tablet user that actually thinks it's a netbook, so I do a lot of things on it, such as 1080 60 video editing, zipping files, creating bootable pendrives, and so on

Gaming is way better on stock if I recall correctly, very weird because everything 2D feels snappy as hell...

Newer tablets aren't honestly worth the upgrade as of right now...

The Pixel C is the last Android tablet that's good for price to performance goodness these days.

The Tab S6 is lacking the GPU performance, however it destroys the Pixel C in the CPU department
[Pixel C Android Development] Alxoom33:
Nice boot animation, UI and customizations. Gesture nav did not work. Slow, freezups navigating through screens. Slow andreezups during browsing. Reeboots. After freezups. Poor bt. Eg didn't pair with keyboard.

Sorry, ok for an alpha build. But [MENTION=5480152]followmsi[/MENTION] you have us spoiled with LOS17.1. No comparison. Thanks.
[Pixel C Android Development] tapol93808:
Hi, I've successfully installed Lineage 17.1 in my google pixel C, unfortunately the tablet isn't recognized anymore by my computer, should I download other drivers because I changed the OS ?
[Pixel C Android Development] zmw:
Man is anyone able to help me get 17 on my pixel C - I've posted about this before, I ran lineage 14 and 15 for years on this damn thing, and as soon as I tried to go to 16, I've never been successful, now with a more official unofficial build I thought I'd try again. Have followed the directions to a T, and I just get caught in a boot loop. What's happening is it boots, shows the lineage logo and annimation, and ends up rebooting back to TWRP. I am able to install the factory image and TWRP/ROOT that - but man it sucks to be that far behind.

Yes I am formatting data, yes I am installing proper gapps as SAR... it sucks that this device is getting so long in the tooth.

---------- Post added at 07:50 PM ---------- Previous post was at 07:30 PM ----------

Well I spent 5 minutes on the lineage KIWI channel, and turns out the TWRP app is the culprit - disabling it and it rebooted instantly...
[Pixel C Android Development] hydromanbj:
wifi problem

I installed this new rom on my pixel C. Everything works fine except the wifi.

Two problems:

1. I cannot see 5G hotspot on my router. I can only see and connect to 2.4G.

2. Even on 2.4G connection, it gets dropped after 5 minutes. I need to manually reconnect to the hotspot.

Any ideas?
[Pixel C Android Development] Thug Life of the France:
TWRP is ****, and will always be ****, we obviously need to bring back what worked before it. For example, CWM, Philz worked great back in the day. Doing a fancy interface is killing functionnality.
[Pixel C Android Development] tapol93808:
Alright, managed to make it work again, downloaded drivers from here : allusbdriverscom/google-pixel-c-usb-driver (ALL new users prevented from posting outside links in their messages. so add the dot)

on the devmgmt panel, right click on the yellow triangle, updated drivers as android abd interface version 2.0.3.0 (Google Inc, oc)

and abd is alright !

Have a nice day folks
[Pixel C Android Development] Thug Life of the France:
Great to see that it works correctly !
[Pixel C Android Development] followmsi:
RIP Oreo

https://review.lineageos.org/c/LineageOS/hudson/+/269773

https://buildkite.com/lineageos/android

The last builds of Lineage-15.1 have been made .. they are still available on the website for downloading.

Within the next time lineage-17.1 will go official and all lineage-15.1 devices will be removed from download website.

For this reason I have uploaded the last build to androidfilehost.com too ..

lineage-15.1-20200221-nightly-dragon-signed.zip

As mentioned before .. I will not continue to be Lineage maintainer for Pixel C .. just the unofficial builds here in this thread.

Of course, it would be nice if somebody else will find the time to continue working on "official" Lineage builds for dragon.

Cheers
[Pixel C Android Development] followmsi:
Android 10 - March 2020 - Part 1

New build has been uploaded ..

Thanks to updateing from Team Mokee !

I have used the DragonParts app to set Country Wifi country code on dragon .. needs testing on lineage.

To change Wifi country code: Settings -> System -> Advanced -> Extra

As well I have used the MAC address Kernel Hack for Wifi/Bluetooth.

This one is still temporary .. it requires trigger from init.dragon.rc to work.

In certain cases system hangs at google logo, second reboot is required to pass google logo and boot normally.

We still use patched framework/base to support microG.

lineage-17.1-20200302-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> Still February 2020 (android-10.0.0_r27)

- Patched framework/base to support microG

- Added DragonParts to change Wifi country code

- Added Kernel HACK for Wifi/Bluetooth

- Minor cleanup for init.dragon.rc

- Disabled DM-verity in kernel config

- Removed some encryption related blobs.

- Latest LineageOS changes for Android 10

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

The "March 2020 Part 2" build will come a bit later this month .. once fresh security patches have been implemented .. etc.

Enjoy :p
[Pixel C Android Development] Alxoom33:
So far flashed and booted up without incident. Using most recent Open Gapps Nano 2020.02.29 version.
[Pixel C Android Development] 12paq:
How odd. I am experiencing none of these problems after a clean flash. Gesture nav works great, no freezes etc. In fact CRdroid runs much better than LOS ever did on my tablet. Not sure why. Thinking out loud: Possibly our different setups? And maybe different launchers with navigation?

I am just glad we have a couple of good choices for roms here! Thanks to MSI ?
[Pixel C Android Development] 2ig2ag:
Feedback about build 20200302:

After reboot, Wifi country code is reset to default value.

---------- Post added at 02:08 PM ---------- Previous post was at 01:59 PM ----------

Screen timeout issue for build 20200209 and 20200302 (earlier builds do not have the issue):

If Security - Screen Lock is set to 'None', Screen Timeout does not work properly. It turn back on a few seconds after timeout, which ends in infinite loop of screen off by timeout and turning back on.

Setting Screen Lock to 'Swipe' or turning screen off by pressing power button does not have the issue.
[Pixel C Android Development] Alxoom33:
Thank you for your response. I clean flashed, as well, used Open gapps Pico. Nano bootlooped, probably there was insufficient space in System partition.

I used the stock launcher as the primary and Nova Prime Launcher as an optional launcher. I also tried to use gesture navigation, which did not work for me.

Navigation was choppy and had big slowdowns and freezups in Firefox beta and chrome browsers.

Also my bt keyboard didn't connect, and was not seen by the tablet.

All of above works perfectly for me with LOS 17.1 including Nano gapps and gesture navigation.

What is your setup?

Thanks,
[Pixel C Android Development] xda_jm:
So - went through this.

If I drain my battery until the device shuts down. It works for the next 2 times. Then, it re-adapts pretty fast to a higher value (I tend to charge when I reach a level below 40% in the evening).

And it is definitely Software driven somehow. Any chance one can add a flag to disable this feature? it really is crap and only serves Google/Apple to sell their devices and keep the battery life high (in time).

But if you want to play games on that tablet, this is a real game killer :(

The battery calibration seems to be reset. Should be possible to influence this IMHO.
[Pixel C Android Development] 12paq:
That is strange. My setup's close to yours.

I know you've been around a while and you know your stuff ? so this is curious.

I used both open GAPPs Pico from 1-16-20 and Nano, both boot fine. Sticking with earlier versions from January has been recommended so I just use those GAPPs.. I did format system with a full wipe coming from LOS.

I use Nova launcher, full gestures. Also use MSI's kernel, i/o fiops, and zram at 1024mb.

My use is mostly research, web browsing, email, marketing my photography biz via social media. YouTube. No gaming.

I use Bromite webview module. Chrome dev for basic web browsing, which works fine for everything except video in browser. If I'm only doing video in browser I switch to Opera.

Looking back on what I just wrote, I guess I do quite a bit of things to make this old tablet run okay for me as a DD.
[Pixel C Android Development] Alxoom33:
Only difference is I did a Factory wipe, did not wipe internal storage. Also I used the January 29 Gapps not the January 16 version. Either one could have caused my problems.

Hopefully it's the latest Gapps.

Can you do me a favor and try to flash the later Nano and Pico Gapps package from January 29 and see if you are having issues? As I am back on LOS, it would be difficult for me to test.

Thanks
[Pixel C Android Development] ivanperezcaro:
I am using the latest version of Lineage 17.1, 0302. In my workplace only devices with the registered MAC can access Wi-Fi. My Pixel C is no longer connected, although before it could with the official version of Lineage 15.1. In all other cases the Wi-Fi connection works perfectly. Does anyone else have a similar problem with MAC filtering?
[Pixel C Android Development] followmsi:
Yep .. missed 2 changes for country code .. pls check next build again. - Thanks

Did switch from "swipe" to "none" and let go device into sleep .. a few times.

I can not replicate this issue .. no difference in all ways (none, swipe, pattern) - dozing works fine for me.

Cheers
[Pixel C Android Development] followmsi:
Pls test this kernel ..

https://xdaforums.com/pixel-c/development/test-kernel-fix-cpu-frequency-limitation-t4055619
[Pixel C Android Development] followmsi:
As written above .. we have used kernel hack in this build .. your MAC has been changed now.

Check "new" MAC address and correct your access list on router - all should work like before.

Pls read here ..

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

The "hack" is a bit dirty, as it requires trigger from init.rc, but most probably I will keep it for next releases anyway ..

Cheers
[Pixel C Android Development] Thug Life of the France:
I'm using the 3C CPU manager as a workaround now for the ****ty performance, so 51 MHz when screen off or charging, and 1.9GHz when using all the time.

And two days later it's working way better imo

The ROM appears to work fine. No real problems here
[Pixel C Android Development] Vartom:
The worst solution to the problem.
[Pixel C Android Development] schmitty782:
Hi there.

Is it necessary to always reinstall the gApps or does this happen automatically via the Playstore?
[Pixel C Android Development] ivanperezcaro:
Well, I can't get it to work. The administrator has registered my "new" MAC but the tablet does not connect. Otherwise, everything works correctly.

EDIT:

I have restored my backup of LOS 15.1 and I have verified that I have exactly the same MAC as in 17.1. But the tablet does not connect with LOS 17.1!
[Pixel C Android Development] followmsi:
No idea whats going wrong for you .. just test unified kernel which has no MAC changes - yet.

https://xdaforums.com/showpost.php?p=81614985&postcount=841
[Pixel C Android Development] followmsi:
Android 10 - March 2020 - Part 2

And the second and last build for this month ..

lineage-17.1-20200305-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> March 2020 (android-10.0.0_r31)

- Some more changes to fix Wifi country code

- Added parameters for Hotspot 2.0

- Kernel HACK for Wifi/Bluetooth MAC Address

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

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

Enjoy :p
[Pixel C Android Development] hydromanbj:
Downloaded and flashed, my pixel c runs like breeze!

Many many thanks!
[Pixel C Android Development] xda_jm:
Hi followmsi,

have to confirm, this kernel works. It is a breeze. At last, the UI remains fluid even when the battery goes down to 25% etc. and I can even make a War Robots game when at 20% or so. Excellent! :)

I never understood why Google/Apple force their devices to become slower and hiding it from their user base. They should give us (the users) the possibility to select battery life or performance if we want, and not take over the entire battery management.

This attitude of theirs is a way to incapacitate us to take our own decisions!

Thx a bunch for that one!
[Pixel C Android Development] followmsi:
In this case .. Thanks to [MENTION=6556709]Vartom[/MENTION]

The "fix cpu frequency limitation" patch is part of latest unified kernel too ..

https://xdaforums.com/showpost.php?p=81938531&postcount=842

Cheers
[Pixel C Android Development] Alxoom33:
Thank you both. Los 17.1 is running great!
[Pixel C Android Development] rauhut:
Android 10 - March 2020 - Part 2

Dirty flashed the update over the February version (bypassing March Part 1):

Upon initial successful install the device did not boot but only showed boot animation with automatically returning to TWRP.

Installed update a second time but now together with opengapps (version 7 March 2020): device booted but several apps (for example Syncthing) lost access and required re-granting access then it worked again.

Gmail app continuously crashed (so far the only app noticed), manually re-assignment of access, deleting cache and data did not help: to get it working again full removal & re-install of app was needed.

Magisk got lost and required new install via TWRP.

Besides this I do not see anything negative so far and Wifi link seems to be more stable (not sure if related to ROM or Repeater that also got an update this week) but I'm wondering what changed towards the hassle-free update of last release that kept opengapps & Magisk in the installation process? :confused:
[Pixel C Android Development] zmw:
should I have been able to just install the latest image dirty over the old one? I had to reinstall gapps and magisk, I didn't think that was necessary on a dirty flash?
[Pixel C Android Development] JoylessHat:
Thanks very much [MENTION=5480152]followmsi[/MENTION] and [MENTION=6556709]Vartom[/MENTION]!

My Pixel C had almost become useless with the stupid CPU throttling and now, it's not only usable but quite a pleasure with Lineage/ Android 10. Would like to send a beer towards both of you, it's not much but just an appreciation from my side. Let me know the best way. ;)
[Pixel C Android Development] _benedict_:
Downloaded and flashed, it works flawlessly, I love it!

Please let us know if there is a way to support you.

Any chance this might become official?