yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
A new build to fix Bluetooth ...

Gallery app is still missing.

Lineage activated the Trebuchet launcher for Pie now ..

lineage-16.0-20181117-UNOFFICIAL-dragon.zip

Changes:

- Fix for Bluetooth

- Latest LineageOS changes

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

Enjoy ..:p
[Pixel C Android Development] brackenhill_mob:
[MENTION=5480152]followmsi[/MENTION] what the heck have you done to my dragon? I was about to buy a Chromebook as the October update was truly awful but this November update makes my dragon really fly! Many thanks for all that you do for us.
[Pixel C Android Development] aiglesh:
Just want to report that extended desktop function doesn't work. If you choose it, settings app crashes and setting is never applied.
[Pixel C Android Development] followmsi:
Like many other things .. Under development

https://review.lineageos.org/#/q/topic:pie-expanded-desktop
[Pixel C Android Development] Rox598:
[MENTION=5480152]followmsi[/MENTION]

A little OT but since you're the main developer breathing new life into our forgotten tablet what do you reckon the chance of the pixel slate OS being able to be installed on the pixel C is?

Be nice to get the OS that was meant to be on it.
[Pixel C Android Development] NYCHitman1:
0%
[Pixel C Android Development] JohnnyChim:
I moved from stock android to Lineage os 15.1. Everything is great, extremely smooth.

But it seems that the battery drain much faster than the stock android.

Anyone facing the same problem?
[Pixel C Android Development] Rox598:
I figured that would be the case :(
[Pixel C Android Development] Alxoom33:
That would be awesome!
[Pixel C Android Development] NYCHitman1:
If you want to use ChromeOS -- buy a Pixel Slate or experiment with Chromefy at your own risk.
[Pixel C Android Development] Alxoom33:
Thank you! This is great!

Just set up my tablet. It's running faster and smoooter than it ever has.[emoji16]

Thank you both for your terrific work in getting 9.0 on our Pixel C's. It's like I just bought a new tablet![emoji7]

---------- Post added at 10:03 AM ---------- Previous post was at 09:45 AM ----------

Just an FYI, although BT appears to be working, I am uable to detect or pair the Google magnetic BT keyboard with the tablet.

Also, while my Motorola Buds but headphones are detected, they are unable to pair.

Any suggestions?
[Pixel C Android Development] Rox598:
Working now, weird.
[Pixel C Android Development] Ditzer:
I also seem to have the Netflix issue. The app loads and seems to work until you try and play something. Then it's just a black screen.

Clean install from yesterday.
[Pixel C Android Development] Rox598:
Turn off the night light/Live display from the quick toggles it's what causes it and can hard lock the tablet (in my case)
[Pixel C Android Development] Ditzer:
Wow. That was it. Thanks for the help!
[Pixel C Android Development] Rox598:
Tbh I was actually going too until I saw the price of the base model came with a Celeron...no chance.

I only asked cause the tablet was supposed to come with ChromeOS so wondered if it was possible.
[Pixel C Android Development] Gadzks:
remote couldn't create file: Permission denied

Need some help, please.

After unlocking BL, flashing TWRP 3.2.3, played with stock, got bored and flashed current LineageOS 16.0. Very happy! Decided to try kernel this morning, and when I pushed it, ADB gave me "remote couldn't create file: Permission denied". Currently the ROM, Magisk and stock Gapps are still in /data.

Suggestions? TIA!
[Pixel C Android Development] followmsi:
Which kernel .. unified kernel ? .. pls install zip via TWRP too.

Either download from system and reboot into TWRP or make ADB connection inside recovery.

Good luck !
[Pixel C Android Development] followmsi:
Tested new pairing with Sony 1000xm2 .. no issues.

If first time fails, try a second time.

Cheers
[Pixel C Android Development] Alxoom33:
Tried many times, with reboots. The bt Pixel C keyboard that magnetically couples to and is inductively charged by the Device is not even detcted. The Motorola Buds are detected but when pairing I get the message that the device is unable to communicate with the Motorola Buds.

Perhaps the new Sony headphones have a newer bt protocol that can pair. It would be nice if the keyboard purchased with the Pixel C can be used as it had on Stock 8.1.

Thanks
[Pixel C Android Development] followmsi:
Bluetooth protocol is backwards compatible ..

Tested another pairing..got communication error once, tried again and it worked.

Will have a look in the next time .. maybe we need to test prebuilt Oreo libs for Bluetooth.

If you check the thread above .. some users report working keyboard and some not.

I do not own the Pixel C keyboard and for this reason I can't test it.

All the "small" reasons why official lineage-16.0 for all devices and especially for dragon device is still far away.

Cheers
[Pixel C Android Development] frauhottelmann:
Keyboard works for me. But I paired it a few builds ago ?
[Pixel C Android Development] followmsi:
Just have a try and pair it again .. :)

Last device related change for Bluetooth was in August 2018 .. used for Oreo and used for Pie too.

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

If you see the description .. it should actually fix pairing.

Cheers
[Pixel C Android Development] Monazite:
The official keyboard on lineage OS and AOSP can't connect automatically, but I found a workaround on XDA. Hold left SHIFT + P + A + I + R and a dialog will pop up to show correct PIN.

I don't know the internal reason, but I think it doesn't related to bt driver. Official Lineage OS 15.1 couldn't connect keyboard directly as well.
[Pixel C Android Development] Alxoom33:
Thank you both. I'll give it add'l tries and see if I can get the keyboard and headphones to pair.

---------- Post added at 12:03 PM ---------- Previous post was at 11:54 AM ----------

Thank you! That worked!!! Awsome, I typed on my Pixel C keyboard. :)
[Pixel C Android Development] Alxoom33:
After getting my keyboard to pair, I was able to pair my headphones, as you had suggested. Thank you! Happy Thanksgiving to you and your family!
[Pixel C Android Development] NYCHitman1:
Moral of the story is that open gapps are terrible lol
[Pixel C Android Development] Everio9000:
Because Google will not support anymore the Pixel C tablet, yesterday I installed LineageOS 15.1 and very happy with it. I will keep LineageOS 15.1 until 16.0 be more stable or official nightly versions be released. Thank you !!! :) :)
[Pixel C Android Development] Alxoom33:
I'm using 16.0 now, it's pretty stable and fully functional. [MENTION=8444383]Folllowmsi[/MENTION] and [MENTION=2489052]NYCHitman1[/MENTION] did a tremendous job!
[Pixel C Android Development] Everio9000:
Yes, they are amazing, great developers.

I read in the 16.0 list issues that screen set pattern and password security still doesn't work. This is very important for me.
[Pixel C Android Development] Alxoom33:
That appears to have been solved, I tried and used both the pin and the pattern. I like the pin for the tab.
[Pixel C Android Development] Alxoom33:
Correction: I tried both the pattern and pin screen unlock methods. Both worked for me without an issue. I personally, prefer using the pin.
[Pixel C Android Development] Everio9000:
So do you see any issue at this time using 16.0? Which rom did you installed? LineageOS or AOSP?

Thanks :)
[Pixel C Android Development] Everio9000:
Finally installed LineageOS 16. It works fine, not like smooth and stable 15.1, but it's fine. I don't know which Launcher use on it because I cannot find the way to show "Recents Apps" working on background.
[Pixel C Android Development] Alxoom33:
I installed Lineage OS. No issues right now.

---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------

I use Nova launcher. Working great![emoji16]

Actually, it's amazing how well this rom is running on ye olde Pixel C!
[Pixel C Android Development] 夜霜行:
Good job ! Think you:svetius:

---------- Post added at 04:06 PM ---------- Previous post was at 03:59 PM ----------

Good job ! Thank you:svetius:
[Pixel C Android Development] UlyssesAm:
Anyone have screenshots of this running on their device? I'm very curious as to how this works
[Pixel C Android Development] Everio9000:
LineageOS 15.1 20181128 nightly update erased Google Play Services of my Pixel C. I cannot use a lot of Google apps and Google Play disappeared.

I don't understand why. :) :)
[Pixel C Android Development] Alxoom33:
I thought you installed v.16.0?
[Pixel C Android Development] Everio9000:
I installed 15.1 again days ago :)
[Pixel C Android Development] Alxoom33:
Well, that's your punishment, Lol!
[Pixel C Android Development] Alxoom33:
I have very much been enjoying Lineage OS 16.0. It's been smooth and have been enjoying using it as my daily driver. Thanks to you and [MENTION=2489052]NYCHitman1[/MENTION]

So, will you be the official Lineage OS 16.0 maintainer for Dragon? What is the plan, if any, going forward if you don't mind me asking?

BTW, been using my trusty Nova Pro launcher, it has been working well with this OS.
[Pixel C Android Development] followmsi:
Normally there is a maintainer for a certain device, but not for each Android version.

Two years ago I have started with official cm-14.1 and moved to lineage-15.1.

And if the device "code" should be ready at some point we can move on to lineage-16.0.

No idea when lineage-16.0 will start officially .. dragon device may take even longer.

There are still encryption issues .. and maybe some more problems.

For dragon we had to change drm_composer sources .. this repo needs to be tracked by lineage now.

Not sure if our change will break other devices using the same sources.

Maybe we use prebuilt libs inside vendor to bypass this kind of problems.

All takes time .. and there is not much time left in the moment.

Cheers
[Pixel C Android Development] 夜霜行:
When I follow the steps to install, restart the system after success, but keep restarting on the boot page, what is the reason? anyone help ，is the recovery or rom problem ?:crying:
[Pixel C Android Development] Alxoom33:
You need to describe the exact steps you followed in your installation. If you want someone to help you
[Pixel C Android Development] 夜霜行:
I instant the room success, and reboot into system,but it boot into recovery again .
[Pixel C Android Development] 夜霜行:
I installed los16 directly from pixel c Android 8.1 and then can not reboot into system ,instead of recovery (3.2.2). what can I do ?:crying:
[Pixel C Android Development] Monazite:
This thread is not for noobs. You should learn how to flash ROM before.
[Pixel C Android Development] 夜霜行:
now I success, but pixel launcher can't work in Los 16…:angel:
[Pixel C Android Development] Alxoom33:
Congratulations!

I like to use Nova launcher Pro. It's been working great for me on this Lineage OS.
[Pixel C Android Development] 夜霜行:
Thank you:good:
[Pixel C Android Development] Dhalsim43:
Google has just released December patch for the Pixel C...
[Pixel C Android Development] Everio9000:
Could it be the last one?
[Pixel C Android Development] Alxoom33:
Right, but it really doesn't matter what Google does for dragon 8.1, we are on to 9.0.
[Pixel C Android Development] followmsi:
December 2018 - lineage-15.1

The December 2018 changes for dragon device and kernel have been pushed to Lineage github today.

The next official build will require December vendor.img !

Lineage plans to merge the general security updates on 2018-12-07.

https://review.lineageos.org/c/LineageOS/android_build/+/235696

Enjoy [emoji14]
[Pixel C Android Development] 夜霜行:
looking forward the new build :silly:
[Pixel C Android Development] WangAaron:
Would you please upload a December vendor.img?
[Pixel C Android Development] Agent.Orange:
He already did: https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
[Pixel C Android Development] followmsi:
Like mentioned above .. already uploaded at December 4th.

If you don't "see" new files pls use chrome browser in desktop mode.

Google drive app does have strange delays sometimes.
[Pixel C Android Development] followmsi:
Android Pie - December 2018

The Gallery app is back.

Let's check what else has been changed ..

lineage-16.0-20181208-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> December 2018

- Google kernel updates -> December 2018

- Notification Bar -> back to "standard" size

- Latest LineageOS changes for Pie

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

Enjoy ..:p
[Pixel C Android Development] Alxoom33:
Thanks, downloaded and flashed without a hitch. Running well, althogh I got a few camera fc's.

I take it we don't have to reflah gapps.

In System/About tablet it indicates that the Vendor security update is November 5, 2018. Does that make sense?

Should I install the December 5th Vendor image that I downloaded from your Drive?

Thank you again for all of your hard work and friendly advice.
[Pixel C Android Development] followmsi:
I have started to set vendor security level last month for the first time.

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

Once the last vendor.img from google will come we set vendor security level accordingly.

Actually it's cosmetic change anyway.

Do not install Oreo vendor.img on Pie !

You will get much more problems - if system will boot at all.

Cheers
[Pixel C Android Development] Alxoom33:
Thanks, I didn't realize it was an Oreo Vendor image in your folder, Dah! No wonder it didn't boot. :)

I was just curious, since settings/about tablet/ indicated it included the December patch, but a November Vendor security level.
[Pixel C Android Development] Dark_Eyes:
Which vendor should i install?

Отправлено с моего ONEPLUS A5010 через Tapatalk
[Pixel C Android Development] frauhottelmann:
You need to install the December Vendor for the latest Lineage 15.1 version. You don't need a vendor for 16 as it is included.
[Pixel C Android Development] AlfreGarcia98:
Installed latest 9.0 version. Working perfectly except for the inicial setup. What do you think is better, aosp or lineage 16? Thanks for the rom and all the time
[Pixel C Android Development] gettinwicked:
Is there an updated GAPPS somewhere? I have 9.0 stock 20180912 that I downloaded in September, but I never did get around to flashing this ROM. I am a go now, so, I want to make sure I have everything I need. Thanks!
[Pixel C Android Development] Alxoom33:
Just download from opengapps
[Pixel C Android Development] gettinwicked:
Okay, sooo, I'm having some issues here. I unlocked my bootloader, booted into the OS and did as little setup as possible, then flashed TWRP, no problems yet. After booting into TWRP, I wiped data, dalvik, cache, and system, I flashed Lineage 16, opengapps, then magisk 17.3. When I rebooted to system, I get to the Google screen, then it bootloops. Does this every time. So, I flashed the factory image, did initial setup, flashed twrp again, booted into twrp, flashed magisk 17.1, booted fine. So, went back into twrp, followed the directions to the T once again, same thing, bootloops at the Google screen... Any thoughts as to what may be going on? Have I missed something? So far I've tried two versions of Magisk. Did everything twice. I'm not sure what the deal is. Right now I'm rooted on 8.1 zero issues. Halp! I would love to try this version of P!

Please and thanks!
[Pixel C Android Development] Dhalsim43:
Might need to format also user data in order to decrypt the device
[Pixel C Android Development] locuturus:
My device has a very unhappy camera. Stock won't launch at all, Open Camera does work, and Duo works for a moment before the camera crashes. Checking dmesg just now I see a lot of binder transaction failed errors after running Duo. Is this something you could troubleshoot with more information?

Otherwise it just does the normal weird stuff for this LOS16 build.
[Pixel C Android Development] followmsi:
Camera has been tested a few times now .. should work fine.

Did you install stock opengapps ?

Replacing stock camera with latest google camera ?

Pls post logcat and dmesg.
[Pixel C Android Development] gettinwicked:
Ah, okay. That's the format button in wipe, right? Would I do that before or after wiping the other stuff?
[Pixel C Android Development] Dhalsim43:
Yes. Be aware that it will erase all your data so think of backup
[Pixel C Android Development] gettinwicked:
Got it. So, before or after wiping the other stuff? Or does it matter?
[Pixel C Android Development] Dhalsim43:
It doesn't matter
[Pixel C Android Development] gettinwicked:
So, I formatted user data, wiped system, data, cache, dalvik. The downloads folder disappeared from sdcard. No biggie, pushed everything to sdcard. Flashed Lineage, gapps, magisk 17.1, bootloop... I give up. Flashing back to 8.1 with root...

---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------

Wait! It bootlooped a couple times, now it's doing something different. Crossing fingers it worked!
[Pixel C Android Development] Alxoom33:
That will wipe EVERYTHING! Back-up any data, apps and media you want to save on a USB drive or on your computer. Then wipe.
[Pixel C Android Development] Alxoom33:
[MENTION=1038414]follo[/MENTION]msi I thought I needed to delete a Magisk module in order to allow my tablet to boot. Turned out to be a false alarm. However, I was not able to locate the Magisk Manager in my SD card.

Just for my own edification, where is it located? Thanks,
[Pixel C Android Development] locuturus:
I installed Nano (3 or 4 builds ago) to avoid replacing any AOSP apps. Stock (AOSP) camera worked for me in the Nov build and the build before that once I copied some files into the vendor partition. I am willing to try a larger Open Apps if you think it'll help.

dmesg isn't very helpful at the moment, even with the - variable it won't post anything since Sunday. I may reboot tonight and check it again.

logcat has a lot more activity. I opened the AOSP camera, and wouldn't you know it the darn thing worked so then I opened Duo and that worked briefly before locking up the camera system resulting in AOSP camera, Duo, and Open Camera failing to work. So I'll amend my complaint to say Duo appears to upset the camera system.
[Pixel C Android Development] mediawiz:
The latest version of this ROM (20181208) seems to drain the battery much faster than the previous version.

Also, in the last few versions, watching high resolution video in full screen for any period of time will crash my tablet. (ie: YouTube HD or 4K in full screen for 10-15 minutes causes my tablet to freeze or reboot. )
[Pixel C Android Development] locuturus:
Is 1080P enough to crash it for you? My tablet won't offer 4k via the YouTube app. Something something DRM maybe. How are you watching 4k YouTube?
[Pixel C Android Development] mediawiz:
Yes. I was using YouTube to watch HD or 4K movie trailers and setting the video resolution to 1080p.

Sometimes it will freeze/crash/reboot my tablet, but sometimes it doesn't.
[Pixel C Android Development] followmsi:
Thanks for the summary .. have to check logs.

The logs include crash of duo app too ?

Are you able to adjust video settings for Duo app only ?

Lineage is still using AOSP camera .. switching to "Snap" camera soon.

Not sure when time is left for Android troubleshooting in the next days/weeks ..
[Pixel C Android Development] followmsi:
Need to check YouTube app .. but Netflix 1080p works fine for hours.

Any example videos to replicate your problem quicker ?
[Pixel C Android Development] Alxoom33:
Is it possible to switch to the Pixel 2/3 camera?
[Pixel C Android Development] locuturus:
Duo never crashed per-say. The camera became very laggy after a few seconds, around 1 fps, and soon after that the camera became inoperable system-wide. Duo to its credit never crashed despite losing access to the camera. The logs should cover these events. I can run more at another time if you want to see something in particular. I also figured out today that after using the camera that day and capturing that log the camera has been consuming 70% of battery in ~12 hours and restricting its background use and force closing it haven't prevented that. I just rebooted and I expect that will have fixed the battery drain for me. So long as I don't open it again I suppose.

I don't think Duo has camera settings. It is a pretty bare bones and 'just works' app.

Cool.

What, is it a holiday time of year or something? (Sorry, I kid)
[Pixel C Android Development] killer33:
Cant get the rom to work normaly, it boots but when it goes to sleep the screen wont turn back on.

Cant flash the ota or factory image on it trough twrp it wont even boot that. even with the flash all they provide it wont even flash it.

I had the worng pin bug issue they still did not fix.
[Pixel C Android Development] Alxoom33:
Did you format your memory before flashing the rom?
[Pixel C Android Development] killer33:
Shure did

trough the wipe option --> advanced wipe selected dalvik/cache,systen,data,internal storage and cache .

then the install option and went ahead with the linage zip.
[Pixel C Android Development] Alxoom33:
That's probably your problem. You were supposed to format your internal memory. Not advanced wipe. Redo and use the "Format Memory" option in TWRP and profit.
[Pixel C Android Development] ipdev:
When you boot into the rom, does everything seem to work fine?

Only have a problem after the screen is off for awhile?

The full factory image needs to be flashed using fastboot(fastboot mode) not recovery(TWRP).

Factory image Link

Flashing instructions Link

Ignore the parts about re-locking the bootloader.

Note:

Yet another place Google erased Pixel C "Ryu" Link

Booting into fastboot mode

Fastboot is a bootloader mode in which you can flash a device. During a cold boot of a device, use the following key combinations to boot into fastboot mode:

Press and hold Volume Up, then press and hold Power.

Volume Down and Power will boot into the Bootloader Menu
[Pixel C Android Development] killer33:
Hi, i have more isues

1 is a bit gettinge annoied

After some time the pixel looks like it unlocks but imediatly goed back to the lock screen. I am getting a bit angry with this bad tablet and bad support from google at the brink of just buuing an ipad or meizu tab.
[Pixel C Android Development] Alxoom33:
On the rare occasion when that happens to me, I just reboot the device and it unlocks wiithout a problem. As I said before, you needed to do a full Format of the tablet's internal memory before flashing the Rom and gapps. Which is likely the source of your problems. Don't blame the tablet or google for user error!

Read the OP and follow it to the letter and you will have much more sucess. This tablet has been great for most of us for a very long time.
[Pixel C Android Development] dijia1124:
Works fine with my replaced pixel c (the last one which has battery issue was sent back and the seller sent me this one )
[Pixel C Android Development] nobse:
Spontaneous reboots

My Pixel C reboots spontaneous. It happened with Stock Android and LineageOS (currently running the build from two days ago), so it got replaced by Google three times in the meantime, because it seemed to be a hardware problem. The spontaneous reboots happen on different places (at home and in my office), but this morning I realized that it happens way more often when the tablet is in the office. Also the battery seems to drain a lot faster in the office.

Wild guess: Something with the Wi-Fi in the office leads to more often reboots. Anyone has heared about something before?
[Pixel C Android Development] ToldYouSo:
Have the same issue. But every app using the cam eventually leads to the inoperable camera. Wether I'm scanning QR s or need to upload a passport picture in-app. Not just DUO causes it so to speak. It seems to happen at around 30secs of keeping the camera open. Maybe even sooner than 30secs. A reboot fixes the problem, only until the camera is on too long again.
[Pixel C Android Development] scoliosis:
Those running Lineage 16, does the Pie kernel limit your CPU to 204 Mhz when battery is less than a certain amount (mine is 67% on Oreo)?