yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] AustrianBagpiper:
I have the weirdest problem with my hardware keyboard... Googled, tried all keyboard settings (really all of them) in Android to no avail. Maybe someone here can help?

I use a German Keyboard worked fine now since I installed the rom 2 weeks ago. Suddenly while most Umlauts öäß still work the ü doesnt and only results in an ´. And the "alt gr" of the thre middle right keys ceised working as well... That makes no sense to me.

I remember that with another bluetooth keyboard that I had that I used for Android first and a PC later, I had to use some key combination to switch between Andorid, IOs and PC mode, there I had similar problems. Any ideas? Thanks!!!
[Pixel C Android Development] Draco32:
Pretty impressive works great for such an old device loving it!
[Pixel C Android Development] HooloovooUK:
Installed this on my Pixel C over the weekend - everything I need working great so far, and much better Bluetooth stability than the old Android 8 it's been stuck on for a few years.

This is probably a very stupid question, but since this is an "unofficial" version of LineageOS does that mean that it wont get any updated directly from LineageOS? Is this just a one-shot install, or will it still get updates now it's running?

Also, is there any way to get it "certified" in the Play Store? So far the stumbling block seems to be that it has to run SELinux in permissive mode. If it's possible, could someone direct me to instructions on how to do it? I've played with various Magisk modules following random advice via a web search and so far not had any success. If someone could confirm that it's not possible, that would allow me to stop trying to get it working ...

Thanks! I'm somewhat new to custom ROMs these days, have not had anything to do with the scene for several years now.
[Pixel C Android Development] Blackmoth311:
Have a magnetic keyboard too. works no issues
[Pixel C Android Development] HooloovooUK:
Answering my own question, because figuring it out is usually how it works as soon as you ask a technical question on the internet ...

The issue was that I couldn't get Zygisk to activate. I upgraded from the latest Magisk release to Canary (23307) and now it works, and the USNF is active. Basic integrity and CTS profile tests pass. The last bit of the puzzle was to clear storage/cache from the Play Store to get it to run the check again. The device now appears certified and all apps are available.

I'm amazed by this. Absolutely everything is working (and better than it was before!), except the known issue with the cameras which I don't care about at all. Thanks so much to everyone that makes stuff like this possible!
[Pixel C Android Development] matt.weatherford:
Thank you for offering your experience / datapoint @Blackmoth311 - appreciate that.

Based on that, I assumed I had some baggage left over from a "dirty flash update" :)

Sp heres what I did:

- backed up my lineageOS PixelC to google.

- I did *not* re-flash (on April 22 update and pico gapps 12L)

- wiped to factory defaults

- set up again and restored apps/data

Bluetooth and keyboard work perfectly now
[Pixel C Android Development] myarsenal:
firstly,thanks for your awesome work @followmsi

i have two pixel c and i got the 19.1 update and pico gapps yesterday,but i have met one question that the usb doesn't work any more and i can transfer any files by usb.
[Pixel C Android Development] BartKey:
Flashed los 19.1 and pico Gapps yesterday using Bugjaeger app from playstore on my OnePlus Nord 2. Works well. No need of pc to unlock bootloader and flash TWRP and rom and Gapps. Used this because my old PC didn't recognize pixel c in bootloader modus. Made connection between OnePlus and pixel c through USB c to c cable.

One question. All works well, except the camera as mentioned by OP. Google chrome keeps crashing and resulted in reboot. Which browser do you guys use? For the moment I use Via browser, works well. Any better alternative?
[Pixel C Android Development] Rampage:
Hey guys,

i haven't been in the xda game for a while and dusted off my Pixel C yesterday.

It's running LOS17.1 right now and i was wondering if is possible to upgrade to 18 or 19 without wiping everything.

😊
[Pixel C Android Development] muerte33:
I use Firefox with Ublock Origin as the only Add-on.
[Pixel C Android Development] followmsi:
lineage-19.1

Lineage Team added new setting to enable/disable the 12L taskbar ..

lineage-19.1-20220507-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> May 2022

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

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

Pls check latest gapps builds here ..

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

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 24.1.

Enjoy Android 12L (y)
[Pixel C Android Development] Markeee:
Dirt Flashed -20220507 from previous build all good no issues
[Pixel C Android Development] jadewong:
New Works like a charm!

Anyone have mic issues? I'm not getting much volume from my Pixel C.
[Pixel C Android Development] Markeee:
Where is the new setting to enable/disable the 12L taskbar ?
[Pixel C Android Development] Agent.Orange:
Settings > System > Buttons > Enable taskbar
[Pixel C Android Development] Markeee:
I don't know what going on but It's absolutely not available for me there is no Enable taskbar option that I can find ?
[Pixel C Android Development] locuturus:
Pixel Experience user here and I have the same problem. Very low gain here on the mic, I guess it's common to both ROMs somehow.
[Pixel C Android Development] locuturus:
Pixel Experience user but I think this advice works here too: use Firefox. Beta or Nightly if you like about:config or extra addons. Chromium browsers really suffer for some reason but Firefox flies. Too bad it has a garbage tablet layout, barebones mouse + keyboard support, and no multi-window.
[Pixel C Android Development] mrbubba999:
Any mirrors for the download, as Google drive days too many people have downloaded it
[Pixel C Android Development] muerte33:
Yes, the gain must be set very low, I don't know how to adjust it up. I have to put my EKG device right up to the mic or it will not work, on the Android 11 ROM it worked almost a foot away.
[Pixel C Android Development] Everio9000:
New build and new Gapps working flawless and perfectly. I can't see when to replace this Pixel C almost 7 years after...
[Pixel C Android Development] straumli:
I am stuck in a reboot loop, any advise anyone? I followed the steps in the start post.

edit: formatted everything and installed via adb sideload, now everything is fine
[Pixel C Android Development] ProjectPatatoe:
Went from GSI LOS 17.1 to this `lineage-19.1-20220507-UNOFFICIAL-dragon` + `MindTheGapps-12.1.0-arm64-20220416_174313`. Very nice had some hiccups during flashing but otherwise went ok. (factory reset after flashing fixed everything)

It seems like there is some power management issue as the top left gets very hot and the battery drains extremely quickly even while the screen is off.

If I turn the screen brightness down too far, it starts to flicker and may cause it to reboot (happened once). Keeping it above 25% seems to cause no issue.

What can I do to get what you need for logs/testing/etc ?
[Pixel C Android Development] _benedict_:
Great work on 12! Is there hope for the camera to work in the future?
[Pixel C Android Development] mrbubba999:
Issue now fixed, doesn't like booting up before Gapps installed, so had to wipe and start again
[Pixel C Android Development] mrbubba999:
Can you expand on how you did this? I've updated Magisk to canary and the Zygisk option still says noedit - got Zygisk working and Playstore doesn't say it's not certified, but not all apps are in the store still (Netflix for example)
[Pixel C Android Development] HooloovooUK:
I downloaded the Canary release from the GitHub repo. It was build 24307 at the time, although that may have changed.

Perhaps you've installed the APK but not actually installed the new version of Magisk? On the Magisk home screen, there's two entries - "Magisk" and "App". The installed version of Magisk should match the version of the app you have installed. If not, you need to click "Install" next to Magisk to get the app to install the newer version.

My installation now says "Installed cc79a96f (24307)" next to both entries.

After rebooting I had "Zygisk yes" and then it was just a matter of installing the USNF module, rebooting, and clearing the Play Store cache.
[Pixel C Android Development] mrbubba999:
I've got zygisk now and play store seems to be verified, but still can't get Netflix to work (the app installs from a website download) but the Netflix site itself won't play any content at all, gives me an error message about protected media (DRM stuff)

I've been trying all day to get this to work and failed so far
[Pixel C Android Development] QuantumSingularity:
Installed the latest version.

Very smooth.

Just one (big for me) problem I found:

DFS channels (WiFi 5GHz) do not work.

I've tried changing WiFi-Country etc a few times (and rebooted), but no success.

I'm in NL, Europe.

@followmsi Is there a workaround for this?
[Pixel C Android Development] samoht76:
My PixelC is still on LO16 from 2019, also TWRP. I would like to flash LO19, my question: should I first update TWRP?
[Pixel C Android Development] brackenhill_mob:
I would if it was me.
[Pixel C Android Development] jadewong:
You should always have TWRP up-to-date
[Pixel C Android Development] Alxoom33:
My Dragon is retired. Doesn't hold much of a charge and isn't recognized by adb/fastboot. Has been a nice run for, what 6 years?? Thank you@followmsi and many others for making is fun!
[Pixel C Android Development] tabormeister:
Cheers to a good run.
[Pixel C Android Development] Alxoom33:
Thank you my friend! It has been a great run! 🍻

Now, pretty much using an Asus Chromebook instead. Let's see what Google has in store for us with their next tablet.
[Pixel C Android Development] jadewong:
I recently just acquired another unit with the keyboard. With the development here, this device is like a dream machine. So portable, hardy and good battery life. The development here just keeps good hardware alive and well! From android 8 till now, the pixel C just gets better and better! Keep it up!
[Pixel C Android Development] followmsi:
Did you test PE 12.1 ROM .. same problem ?

Still need to test latest power changes from michi.

Looks not promissing on 19.1 .. if you need Camera go for last lineage-18.1 ROM instead.

Did DFS channels work on 18.1 ? .. or on earlier 19.1 builds ?

We may have to adjust wifi overlays for android 12 ..

Sorry .. not much time left for Android.

Right now I just make monthly builds based on same device/kernel sources .. hope this will change at some point.

And we still use the old prebuilts from last stock ROM (Oreo).

You can't just take sources from Nvidia shield and they magically work on dragon .. if it's possible to use some sources it takes quite a while to adapt for dragon .. and for some problems we may never find a solution .. at least not me.

Cheers
[Pixel C Android Development] QuantumSingularity:
Yes. They worked on 18.1. Never on 19.1.

My other PixelC is still on 18.1-20220216-UNOFFICIAL-dragon and DFS works well.

Settings is: 'System/Advanced/Wi-Fi Country Code' and is set to 'Europe'

I installed 19.1 clean (formated/wiped system, cache, data) en installed the 12.1l gapps (arm64_12L-pico-220507....MOD). No root or something.
[Pixel C Android Development] followmsi:
Pls install Magisk 24.1 and test to set wifi-country code again.

Magisk is using "resetprop" to overwrite country code.

While regular "setprop" may has some read-only prop issues.

Needs to be checked ..
[Pixel C Android Development] QuantumSingularity:
Unfortunely it doesn't work.

Only channels 16, 34-60 I see.

I installed Magisk 24.1 apk (from github) in TWRP.

Wiped cache.

Booted.

Changed WiFi-country to Germany.

Rebooted.

Changed WiFi-country to Europe.

Rebooted.

Still no DFS-Channels.

On my other PixelC I see channels 36-64, 100-112 (there are more channels, but WiFi Analyzer only shows occupied channels).

I have 3 Unifi WiFi5 AP's, 5GHz 40MHz.

One on channel 38, one on 102 and one on 110.
[Pixel C Android Development] followmsi:
Pls check ro.boot.wificountrycode on your both Pixel C devices ..

getprop ro.boot.wificountrycode

Same countrycode on both devices ?

If yes, we need to check related changes on 19.1 .. as wifi kernel drivers remain unchanged in 18.1 and 19.1.
[Pixel C Android Development] QuantumSingularity:
I've checked both devices.

Stange thing is: Display in the settings says `Europe` and getprop says `GB` on both devices.

bem@BasPC:~$ adb devices
List of devices attached
6121000728 device

bem@BasPC:~$ adb shell
dragon:/ $ getprop ro.boot.wificountrycode
GB
dragon:/ $ exit
bem@BasPC:~$
bem@BasPC:~$ adb devices
List of devices attached
6130000716 device

bem@BasPC:~$ adb shell
dragon:/ # getprop ro.boot.wificountrycode
GB
dragon:/ #
bem@BasPC:~$
[Pixel C Android Development] Thug Life of the France:
Hey there, it's been a while for me on these forums !

Mainly because as it's difficult as hell to get any replacement screens for the Pixel C, I just bought another one that wasn't too far from me... (a 64GB btw, so quite cool to see that, along with a proper magnetic keyboard that is a pleasure to type on, and quite sturdy, not really mushy)

Someone here sent me a link to get screens and such, but it's really difficult to even understand how to place an order.

----

So now that I'm back with using a C, I can say that it's not aging well, last time I used one was on the Android 10 days and it was really smooth...

I think that instead of bumping Android versions and following ROM development, we should focus more on bugfixes and optimizations...

That tablet has potential SoC wise, and the 3GB of RAM should only be an issue for demanding stuff...

That ROM should include zRAM or something, and a bit more aggressive LMK to help smoothen everything out.

Too bad the NAND flash is quite slow otherwise it would have helped using it I think honestly.

Android 12(L) may be the last proper version we'll get because of the really ancient kernel we're using.

3.18 isn't of good use, and NVIDIA being who they are won't help us... unless that opensourcing of drivers also extends to embedded devices like everything in the Tegra family and such...
[Pixel C Android Development] mrbubba999:
Are there any further updates planned for this?

I'm not sure what tablet I could replace this with
[Pixel C Android Development] alterjsive:
The LineageOS 19.1 2022-05-07 is a great rom, thanks so much! Any idea why the battery usage is so high?
[Pixel C Android Development] henrywhtin:
Could you please elaborate more on how to use magisk to set wifi-country code?

As I am new to this and I think I have the same problem.

Thanks!
[Pixel C Android Development] ipdev:
Hi. 🙂

Can be a bit complicated.

Magisk - [github.io] - resetprop

Magisk - [github.io] - Resetprop

You can change the prop values while booted.

Spoiler content hidden.

That would only be temporary since the default value will be restored on (re)boot.

Might work for testing, not sure if it needs to be set earlier (during boot) to make a difference.

You will need to use a boot script to adjust the prop value on boot.

Magisk - [github.io] - Shell scripts

Magisk - [github.io] - Boot Scripts

You can use the MagiskHide Props Config module to change the prop instead. 🙃

Quick search, I did not find an official list of country codes.

This is one of the better lists I found.

AppTweak - [apptweak.io] - Country and language codes

Cheers. :cowboy:
[Pixel C Android Development] _benedict_:
Hi!

Do some of you have the same problem? The audio stutters a lot via BT.
[Pixel C Android Development] jadewong:
Help! Flashing custom rom and then it crashed midway. Lost TWRP and when I tried to use adb fastboot, adb unable to recognize device. Unable to find Pixel C adb driver and using other drivers doesn't seem to work. Any ideas?
[Pixel C Android Development] BartKey:
I flashed los 19.1 and pico Gapps using Bugjaeger app from playstore on my OnePlus Nord 2. Works well. No need of pc to unlock bootloader and flash TWRP and rom and Gapps. Used this because my old PC didn't recognize pixel c in bootloader modus. Made connection between OnePlus and pixel c through USB c to c cable.
[Pixel C Android Development] jadewong:
Never mind! I managed to solve this. My pixel C has come back to life stronger than ever!
[Pixel C Android Development] Jeantree:
Hi All, can anyone connect the physical keyboard? My pixel c can't find the keyboard in this rom. Not sure if it's my own issue only.

Thanks.
[Pixel C Android Development] EnginEAR:
Yes.
[Pixel C Android Development] EnginEAR:
Just upgraded to Magisk v25.0.

Everything seems to be fine.

Question - is there a way to completely disable the 12L dock thingy? I find it useless for my purposes... And somewhat ugly :-)
[Pixel C Android Development] followmsi:
Need to check the country code script on 12 .. maybe the process of applying the country code has been changed.
[Pixel C Android Development] followmsi:
Every kind of help/input is welcome. (y)

Michi has started to use some Nvidia/Tegra components .. maybe you can adjust the dragon sources to be able switch to Nvidia sources.

Pls push your changes to Github.

I don't have the time anymore to work on Android like I did in the previous years.
[Pixel C Android Development] followmsi:
Yes .. Magisk 25.0 works well .. and Zygisk works on "older" kernels now.

You can disable "Taskbar" in lineage settings to get rid of the 12L taskbar .. no idea if Lineage is planning more changes related to the "12L style" on tablets.
[Pixel C Android Development] followmsi:
lineage-19.1 - June 2022

Due to the upcoming holiday season the July build will be delayed or skipped ..

lineage-19.1-20220615-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> June 2022

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

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes

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

Pls check latest gapps builds here ..

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

Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.0 !

Enjoy Android 12L (y)
[Pixel C Android Development] EnginEAR:
Buttery smooth! Thanks for the "taskbar" tip. Happy camper right here :-)
[Pixel C Android Development] mrbubba999:
How do I get rid of the grey bar with the list of apps at the bottom of the screen? It used to swipe away, now it's there permanently
[Pixel C Android Development] EnginEAR:
Settings -> System -> Buttons -> Enable taskbar -> switch off!
[Pixel C Android Development] matt.weatherford:
I had this issue with my pixel C and had to backup to google account, wipe, and reinstall rom and GAPPS.... then my magnetic cover bluetooth keyboard started working again
[Pixel C Android Development] Jeantree:
Before reflashing the rom, you can't pair the keyboard or it's just not listed in the Bluetooth devices list?

Thank you.
[Pixel C Android Development] jamesthedisciple:
Hoping someone can help:

Installed latest twrp and LOS 19.1 all went well, cool and smooth.

Closed cover. opened cover and blank screen.

Will (adb) reboot to OS, to recovery and to fastboot but no screen, no logo, no usual "warning". I've backed up. wiped and flashed (sideloaded) LOS 18.1, boots but still no screen.

Update: the screen works but no light! (I can see a shadow of the lineago startup screen

Are there ways to check/adjust screen brightness from adb?

Any ideas to get screen light working? or is it stuffed
[Pixel C Android Development] tabormeister:
Mine just did this, scroll up a bit :/ I ended up buying another. I feel like it's a hall sensor that's stuck or something, every once in a while with the right reboot combo it would come back to life but got steadily worse
[Pixel C Android Development] jamesthedisciple:
Thanks. Most annoying. A trick I've just discovered (whether it will contine to work is another thing!) is that if I put the screen cover behind the unit, the screen light comes on. Almost as if the hall-effect switch is switched on when the magnet is reversed?
[Pixel C Android Development] tabormeister:
WHOA I'll try this!! Which cover, folio or aluminum kb? What orientation?
[Pixel C Android Development] jamesthedisciple:
Folio, like this one: https://www.amazon.com/Google-Table...?keywords=Pixel+C+Cover&qid=1656040114&sr=8-3
[Pixel C Android Development] tabormeister:
Huh. I have both first party accessories but not this one. Might be worth trying just to see if it revives the old one I have haha. Is that the exact one you have?
[Pixel C Android Development] jamesthedisciple:
I believe it is, I bought mine many years ago. I also did a clean install of 18.1 boot, followed "start up" connected to wifi, then dirty flash of 19.1. Boot, flipped cover to behind and viola. It might work by placing a magnet on the back of the unit just to see if it is the hall effect switch?

Update: Started having the light not work again. A "fix" was to close the cover, press power button once and open, light on. Had to do it a couple of times to make sure. That seems to be the work around.

Have fun :)
[Pixel C Android Development] Blackmoth311:
Awesome.

Can anyone confirm if network data monitoring is working now?
[Pixel C Android Development] CyberSpuds:
Thanks for your efforts on this! Dumb noob question: after the install, do I just live with the message at bootup: "Bootloader Unlocked / OS Verification Off / Device will continue booting in 30 seconds" or is there a way to bypass that message or relock the bootloader? I did some searches on XDA and found a few custom mods to lock the bootloader (on different devices) but it looks pretty complicated. Just want to make sure I'm not missing some obvious thing, like "fastboot oem lock"! ;)

Thanks again!
[Pixel C Android Development] EnginEAR:
Yes :-( I've been just living with it for a while and wasn't able to find a way not to (without dying, of course) :-)
[Pixel C Android Development] CyberSpuds:
Thanks for confirming that. Appreciate your work!
[Pixel C Android Development] julz24:
Thank you for this ROM. Nice to enjoy 12 on our now old devices. Followed the procedure to flash, all went well.

After a few weeks of use, my device becomes unresponsive when it wakes from sleep.it takes a good 5 to 10 minutes t become usable. Anybody else has this issue? or maybe my device has some hardware issues?

Thanks again for this ROM.

Thank you for this ROM. Nice to enjoy 12 on our now old devices. Followed the procedure to flash, all went well.

After a few weeks of use, my device becomes unresponsive when it wakes from sleep.it takes a good 5 to 10 minutes t become usable. Anybody else has this issue? or maybe my device has some hardware issues?

Thanks again for this ROM.
[Pixel C Android Development] Blackmoth311:
i have the same issue.
[Pixel C Android Development] lx1905:
I flashed the latest 19.1 system, connected to the computer after booting it up, and there was no response when I selected file transfer, so I couldn't connect to the computer. What happened? This is the case after re-flashing the system several times. How to solve it, I have to flash back to the official system. Have the same problem?
[Pixel C Android Development] heyChristo:
I had similar issue after flashing an older version and was never ever to get it recognized. Was not eve able to flash magisk so i'm stuck on stock LOS. One day when I have the time, my hope is to upgrade it and get it communicating with the PC again.
[Pixel C Android Development] tabormeister:
Update: Didn't fix my original issue, but I like the case! Keeping it for simplicity.