yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
This time you did not have any "signature verification" issues like before - good !

For lineage-18.0 on dragon I did fix all build errors first.. and made some changes to hopefully get bluetooth running on Android 11.

I have made 3 test builds but did not install them myself.

As it looks like a few people have tested the builds .. you too.

Does it boot to lineage bootanimation ? .. and reboots to recovery ?

Or just boots to google logo only ?

Does it reboot to recovery or just hangs at google logo for longer time ?

Got different answers.

In future builds TWRP Recovery will not be overwritten anymore ... :)

Linage did merged the related changes for it some days ago.

Will make another test build next days .. to use all the latest lineage changes too !

But I would love to get logcat of boot process from any of the 18.0 builds for dragon .. even you see google logo you might have adb/logcat already running.

This would help a lot to get working/booting builds earlier.

At some point I will need to check myself .. I know.

But I have started 18.0 development on other devices at the same time .. dragon has lost this year .. comes later.

Cheers

EDIT:

Just made a new build for testing .. lineage-18.0-20201117-UNOFFICIAL-dragon.zip
[Pixel C Android Development] Alxoom33:
Good luck! Take it slow and don't improvise. I'm sure you will do fine.

---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------

Correct, with Lineage Recovery I did not have any signature verification issues, which persisted with stock recovery.

For me 18.0 did not boot. It only made it to the Google splash, if I remember correctly as this was in October. I'll try to get a logcat on the next iteration.
[Pixel C Android Development] followmsi:
Pls go ahead .. lineage-18.0-20201117-UNOFFICIAL-dragon.zip

TWRP should be kept now .. you should be able to trigger lineage recovery override in settings .. like in 17.1 too.

Happy for any logs ... :)
[Pixel C Android Development] Alxoom33:
Thanks, will give it a try. Any idea what gapps to use for 11? Or does this include Gapps?

---------- Post added at 10:51 PM ---------- Previous post was at 10:16 PM ----------

I tried Nike Gapps.

System did not boot. Still haven't made it past Google Splash screen.
[Pixel C Android Development] EnginEAR:
:(

"Fresh install" or an update? Curious in case I suddenly feel lucky...
[Pixel C Android Development] Alxoom33:
I would suggest a fresh install. As LOS 18 is Android 11. Good Luck! Perhaps try minimal or no gapps first.

Make sure you save a logcat if it boots.
[Pixel C Android Development] followmsi:
First Opengapps packages are ready to test .. https://sourceforge.net/projects/opengapps/files/arm64/test/

Since a few days I am using version "open_gapps-arm64-11.0-nano-20201107-TEST.zip" without problems so far.

Even you see Google logo only .. the system may have started to boot into Android.

Just plugin usb cable and check if device is connected .. maybe it takes a few seconds before you get adb connection.

To check what is connected .. just type

adb devices

If it works ..

adb logcat > logcat.txt

If you dont get adb conntection to work .. pls reboot directly into recovery and pull console-ramoops from kernel.

Type in TWRP terminal ..

- copy onto sdcard ..

cat /sys/fs/pstore/console-ramoops > /sdcard/ramoops.txt

- in case log file is empty, pls check folder for current/correct name of "console-ramoops*".

ls /sys/fs/pstore/

Thanks for help !
[Pixel C Android Development] EnginEAR:
Can't resist when instruction are so easy to follow

There you go...
[Pixel C Android Development] followmsi:
Thanks a lot for the logs !

You called the file ramoops .. but it was logcat from android system .. the first 400 log entries are missing.

Pls start a bit earlier to pull the logs ..

Nevertheless .. I have seen the issues in logs and have hopefully fixed them ..

lineage-18.0-20201119-UNOFFICIAL-dragon.zip

Pls send logs again when you have time to test this build ... Thx.

Happy testing :p
[Pixel C Android Development] EnginEAR:
Boots. No errors so far. Giving it a first spin :)
[Pixel C Android Development] tabormeister:
Whoooaaa!! Can't wait till it's good enough for plebs like me. Signed, a recovering flashaholic.
[Pixel C Android Development] followmsi:
Sounds good .. indeed :)

Pls test as much as possible .. like wifi, bluetooth and other hardware related stuff.

Pls let us know your results.

Cheers
[Pixel C Android Development] EnginEAR:
The only thing I'm missing so far is "Advanced Reboot" or whatever it's called...

I believe this was in favor of the new "cool" power button options which include home settings.

I use those on my phone and I just set the same controls on the tablet.

I'll live with it.

Other impressions:

Seems buttery smooth. Thanks [MENTION=5480152]followmsi[/MENTION] !!!

No error messages whatsoever.

Installed Magisk 21.1 with no issues as well.

Now, if only we could get WideVine and some control over the notification light bar on the back - this old tablet would be as coveted as it originally was...

Best Android tablet I ever used...
[Pixel C Android Development] tabormeister:
Dammit I'm convinced. What gapps package did you flash?
[Pixel C Android Development] EnginEAR:
No issues with Wi-Fi as of yet.

I use the original Pixel C keyboard (the hard one) and no issues with bluetooth as of yet.

Just for the sake of this response - I connected my bluetooth headphones. No issues as of yet.

Overall - it's super snappy...

I've been attempting to flash since the first test build.

The result of this was I often had to "fresh install" the 17.1 build. Repeatedly :)

Having experienced a "fresh install" as frequently and as recently as I have - I can honestly (and in a somewhat educated manner) say this build doesn't fall short compared with the latest 17.1.

Nothing but appreciation and respect to you for your efforts and time!
[Pixel C Android Development] followmsi:
It's in gestures settings now .. power menu .. here you can enable advanced reboot now.

Does reboot recovery works ? .. aosp has changed some stuff for the reboot process.

Maybe you will need to remove /vendor/lib/liboemcrypto.so to get L3 widevine .. this way you should be able to watch DRM content like Netflix.

Are you able to test upgrade from 17.1 ?

Wipe system only and install ROM, gapps and Magisk in one go .. but keep "dirty" 17.1 /data partition .. reboot and check if system boots up ?

Thx
[Pixel C Android Development] EnginEAR:
https://sourceforge.net/projects/op...ps-arm64-11.0-pico-20201116-TEST.zip/download

---------- Post added at 04:12 PM ---------- Previous post was at 04:05 PM ----------

Thanks again. Found and turned on. Reboot into Recovery works.

I don't use Netflix... I meant something like Chrome playing DRM video on sites...

As for the installation process - I did exactly that!

Wiped system... Then installed ROM, gapps, and Magisk in one swoop. Approved reinstalling of TWRP app as a system app. Voilà!

Still running my childish and unprofessional tests... I'll report anything interesting I find... For better or worse...

---------- Post added at 04:27 PM ---------- Previous post was at 04:12 PM ----------

Probably a stupid question, but is there a way to get battery percentage (actual digits) in the status bar?
[Pixel C Android Development] Alxoom33:
LOS 18 flashed dirty with no issues. Used a Full gapps package and rooted with latest Magisk.zip.

Wow, this Dragon is flying on Android 11, who'd thunk it?

Thanks [MENTION=5480152]followmsi[/MENTION].
[Pixel C Android Development] tabormeister:
Dirty flashed from 17.1, wiped system and installed 18 and gapps, did not wipe data or cache. Logcats attached. Boots enough that I can see the lockscreen, then soft reboots.

Let me know if you want me to try/flash anything, otherwise I'll wipe data and see what happens. (Assuming good boot)
[Pixel C Android Development] Alxoom33:
I had a problem with unlocking the lock screen after flashing, so I used the lock screen pin/pattern remover.zip. It worked! But now I am unable to set pin or pattern. Keeps reverting to swipe. Not a terrible issue to have. But noted [emoji16]

---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------

What Gapps did you use. Nike Gapps works for me.
[Pixel C Android Development] tabormeister:
I'll try those, I used the ones [MENTION=892369]EnginEAR[/MENTION] posted
[Pixel C Android Development] tabormeister:
Still soft rebooting with no final boot, want me to try something else or factory reset?
[Pixel C Android Development] followmsi:
Take TWRP backup of your 17.1 /data partition to test dirty upgrade later on.

If you have pattern/pin on 17.1 remove them before upgrade.

On another device running 18.0 I have also problems to setup pin/pattern .. maybe still some general code is missing.

For now you may have a clean start on 18.0 ..
[Pixel C Android Development] EnginEAR:
I did not have pin/pattern set.

Sorry... I should have mentioned this.

I find the best security in my situation is to leave everything completely open.

My wife is accustomed to iOS... She couldn't find anything incriminating even if she tried using the Pixel C... Not that there is anything to find :)
[Pixel C Android Development] Alxoom33:
That makes sense, because when I dirty flashed 18.0 I could not open home, due to the device not recognizing my pin. When I used the Pin/Passsword reset zip by flashing in TWRP I was able to access the home screen, but I was unable to reset pin. Security just kept reverting to swipe option. Otherwise, running well. Great forr a first itiration.
[Pixel C Android Development] tabormeister:
Same here, can't set pin - I had removed my pin before dirty flashing, but no dice. After factory reset, running like a dream. Bluetooth works, wrote this on the metal Pixel C keyboard. Getting a couple repeated keys here and there but nothing crazy. Camera doesn't work but that's to be expected honestly. Used NikGapps this time.
[Pixel C Android Development] Markeee:
Oh well broke my Pixel C Tablet today changing the battery . I been living with the Pixel C Tab and my Nexus 6 phone running LineageOS for years just looking for some feedback on what might be a fun and logical upgrade that should have good LineageOS Rom support going forward ?
[Pixel C Android Development] Alxoom33:
The logical replacement would be the Google Slate tablet. But it runs Chrome OS and has gotten terrible reviews. I heard good things about the Samsung Tab 5 & 7. Or, if you want to be a turncoat, the iPad Air.
[Pixel C Android Development] frauhottelmann:
The Samsung Tab 5e is nice and supported by Lineage
[Pixel C Android Development] Markeee:
What do u think about the newer Samsung Tab S7 or S7+ ?
[Pixel C Android Development] frauhottelmann:
They are nice, but right now there is no ROM available whatsoever.
[Pixel C Android Development] Markeee:
Yeah seems development is in the works for the S7 and S7+

thinking maybe stay stock for a while living off Samsungs updates then down the road by the time they stop supporting it there should be plenty of third party and LineageOS roms kicking around same as last years 5e

Am I wrong ?
[Pixel C Android Development] followmsi:
Another Android 11 build ..

lineage-18.0-20201121-UNOFFICIAL-dragon.zip

Changes:

- Fixed Widevine (Tested Neflix only)

- Fixed Pin/Pattern/Password (Tested Pattern only)

- Update for WiFi service

- Switched to kernel-based Low Memory Killer.

- Patched framework/base to support microG

Magisk 21.1 sems to require manual reinstall after ROM update .. while opengapps test got automatically reinstalled.

Enjoy :p
[Pixel C Android Development] frauhottelmann:
I just wouldn't count on a ROM. You never know. I did buy a phone in the past with active development, but it never took of.

Personally I won't buy another device without proper support. But Samsung also promises 3 years updates and 5 years security updates so it's probably still an nice device to have.
[Pixel C Android Development] EnginEAR:
Updated previous build to this one with no issues :)
[Pixel C Android Development] Alxoom33:
Updated with no issues. Used Open Gapps Mini package. Lock screen pin works.

View attachment 5139243
[Pixel C Android Development] Markeee:
Yeah after reading around a bit more unfortunately I have to agree with you support doesn't look to good at this point for the S7 S7+ and likely may never martialize sucks it would of been a nicer upgrade but without rom support I can't go there.

On the other hand the Tab S5e has the official LineageOS blessings but I don't think the S5e is actually much of a upgrade over the Pixel c specs are similar power wise am I wrong ?
[Pixel C Android Development] schoerb:
Thanks for the great update to Android 11. It runs very good.

But disabling "Hardware-accelerated video decode" in chrome://flags/ still doesn't help to play videos in Twitter in Chrome.

Kiwi Browser plays these videos without disabling the flag.
[Pixel C Android Development] Alxoom33:
It is an incredible upgrade over a broken Pixel C!
[Pixel C Android Development] Alxoom33:
Is there an "Advanced Restart" toggle or setting in LOS 18.0 Developers Options? Or was that something that was only present in LOS 17.1? There is an Advanced reboot option in the Power button menu in LOS 18, but I didn't see anything in Developers Options. Is that correct?
[Pixel C Android Development] tabormeister:
It's in gesture settings in system
[Pixel C Android Development] Alxoom33:
Thanks, found it![emoji1]

---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------

Are you able to access fastboot? What gapp did you wind up using¿
[Pixel C Android Development] bra1niac:
I'm not entirely sure this is related, but after flashing the 11/21 ver 18 build, using the built in terminal app enabled from developer options, running ssh gives a segfault.

Otherwise its looking good to me. I don't use gapps and just use swipe on the lock screen.
[Pixel C Android Development] Alxoom33:
Lockscreen security works with pin or pattern. Please explain what using the built in terminal app from developer options does?
[Pixel C Android Development] bra1niac:
In developer options, there is an option to enable a terminal emulator app. When you do that, a new app appears called "Terminal" that you can open to get a Unix-like OS where you can run Unix commands.. Its a feature that is available in Lineage.
[Pixel C Android Development] Alxoom33:
OK, found it. Thank you!

But what does this Terminal app do that's different than Terminal Emulator app from Magisk Module or terminal extension in TWRP? Can it be used to execute fastboot commands or fix fastboot? If so, how? Or is it just another terminal emulator app that is built in to LOS 18.
[Pixel C Android Development] bra1niac:
It just a terminal emulator like any other you could install. It's just included in Lineage, so it saves you a step in installing a 3rd party one.
[Pixel C Android Development] Alxoom33:
I saw in previous posts what seems to be a way of using the terminal to sudo fastboot twrp.img and potentially other image files. But I could not get it to work. Did get some unknown options when typing in fwul. I'm not sure what that does.
[Pixel C Android Development] tabormeister:
Used Nik gapps, what do you mean about fastboot?
[Pixel C Android Development] Alxoom33:
I switched to Open Gapps beta Mini. As far as fastboot, I can't access my tablet with fastboot on my computer. Only ADB works. By contrast fastboot and adb works fine for my Pixel 2XL. I have been looking for a way to fastboot boot or flash to my tablet.
[Pixel C Android Development] brackenhill_mob:
At the risk of asking a stupid question, have you thought about returning to stock to fix fastboot and then rolling forward? I haven't followed all of this thread for some time so you might have already tried this... ;)
[Pixel C Android Development] Vartom:
You should also check if the tablet is locked to execute fastboot commands.

fastboot getvar all

Check the status secure parameters.

If you see a line

secure YES

then you need to use the following instruction https://xdaforums.com/showpost.php?p=83489789&postcount=19

fwtool vbnv write dev_boot_fastboot_full_cap 1
[Pixel C Android Development] tabormeister:
This, but also is your problem it doesn't show up and you're having driver problems in windows? If so, use macos or a Linux live boot.
[Pixel C Android Development] Alxoom33:
I tried and failed with stock recovery. Now that I have TWRP, I can try again. But would it be any different to flashing the Dragon Recovery img that was posted by [MENTION=5480152]followmsi[/MENTION]?

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

Thanks, I'll take a look. I don't expect that my unlocked tablet could have been locked when flashing an alpha version of LOS 18. But stranger things have happend, so I'll check.

---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------

Oh, can't execute fastboot commands, as the issue is that fastboot is not working. But the tablet is rooted and the bootloader says unlocked. So I'm pretty confident this tablet has been fully unlocked these 4+ years. Been flashing custom ROMS ever since Google stopped supporting Dragon with updates. So, I'm confident that a locked bootloader is not an issue.
[Pixel C Android Development] Vartom:
In such a case, you can check the value of the variable from the terminal on the system.

Try to run this command Execute from root / su

fwtool vbnv read dev_boot_fastboot_full_cap

If the answer is 0, then run this command

fwtool vbnv write dev_boot_fastboot_full_cap 1

---------- Post added at 08:29 PM ---------- Previous post was at 08:12 PM ----------

Just check this key dev_boot_fastboot_full_cap. It just affects the availability in the fastboot mode. In this case, the bootloader is unlocked. This key sometimes flies to zero or is not installed if the unlocking process was not completed correctly.
[Pixel C Android Development] Alxoom33:
When I entered the commands in TWRP terminal:

# fwtool vbnv write

# dev_boot_fastboot_full_cap/

Got sh: dev_boot_fastboot_full_cap:. not found

Tried same in adb shell from win 10 computer, same message: inaccessible or not found

I'm not sure what else to do. Last option is to delete internal storage and flash stock android in TWRP. Would like to avoid that if possible.
[Pixel C Android Development] Vartom:
This is one whole command, no need to divide it into parts! Write exactly as I have written.

fwtool vbnv write dev_boot_fastboot_full_cap 1
[Pixel C Android Development] TooYellow:
clean install from adb sideload (wiped every partition)

20201121 build

Open GApps 11 beta 20201116 - micro

Magisk 21.0

So far things are running pretty smoothly. Just a couple things to report:

- Lock screen doesn't go portrait, only landscape

- Chrome cannot sign in (also tried beta). I keep getting sent to the "add account screen". It doesn't recognize the google account signed into the device. Other Google apps like gmail, hangouts, keep had to problem logging in.

- I use this device primarily as a news reader. Google News can no longer verify my Washington Post subscription. I keep getting an error saying it can't verify but I'm not taken to a screen to even try to log in to my account. The Wash Po sub works fine on other android devices through Google News. Weirdly, the NY Times sub logged in just fine.

I know these seem like app specific issues but they worked on LOS 17 so I thought I'd mention it.

screenshots attached

Thanks for all the great work!
[Pixel C Android Development] Alxoom33:
I did exactly as you typed. Got same result ...cap = 1 just like in the spoiler.

However, fastboot doesn't detect the tablet.

When trying to fastboot boot recovery Twrp-Dragon.img I get:

< waiting for any device >
[Pixel C Android Development] tabormeister:
Yup most likely your fastboot drivers aren't set up right in Windows. Try Linux live boot or Macos, for some reason I haven't been able to get the pixel c fastboot working under windows 10, only macos/linux
[Pixel C Android Development] Vartom:
In this case, your computer simply does not see the connection to the tablet. This is a different type of error.

Before that, you wrote that fastboot commands cause a response in the form of "FAILED (remote: unsupported command)"
[Pixel C Android Development] Alxoom33:
No, that was regarding adb sideload for LOS 17.1 because I was unable to use fastboot.

2 different issues. I solved the sidload issue and am now using LOS 18.0 and TWRP 3.4.0 recovery. But the fastboot issue persists. Which is what I was talking about with you.

---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------

The thing is, they worked perfectly before I flashed the first alpha 18.0 version. They are very recent, last month, and they work perfectly wit my Pixel 2 XL. Using mac os or Linux may be a solution, but they don't fix the underlying problem.
[Pixel C Android Development] tabormeister:
*shrug* may be a solution here: https://xdaforums.com/pixel-c/help/fastboot-to-t3431999/page2

I haven't gotten fastboot to work under win10 the whole time I've owned the tablet.
[Pixel C Android Development] Alxoom33:
I'll take a look. Thank you my friend!

Nope! Couldn't find Android Bootloader to complete the last step.
[Pixel C Android Development] michie:
You could try Nikgapps untill a stable opengapps package is released. These work well on all my devices running R: https://nikgapps.com/
[Pixel C Android Development] tabormeister:
I'm also running those, no problems so far with em. Even corner swipe assistant works great. Much smoother than Q.
[Pixel C Android Development] Peregr1ne:
Hurray! I have succesfully been able to get 17.1 up and running on the Pixel, and I'm loving it! :)

This indeed was the issue: the somehow not-fully-unlocked-state of the tablet.

I had to take a slightly different approach though (improvise :eek:): in the end I have re-locked and re-un-locked the tablet, both from fastboot (from a Knoppix terminal as fastboot from Win10 is still impossible).

This resulted in a state where the tablet was no longer showing

(bootloader) secure: [B][COLOR="red"]yes[/COLOR][/B]
...
(bootloader) unlocked: [B][COLOR="Red"]yes[/COLOR][/B]

as before but instead,

(bootloader) secure: [B][COLOR="red"]no[/COLOR][/B]
...
(bootloader) unlocked: [B][COLOR="Red"]yes[/COLOR][/B]

which in turn enabled me to actually boot into TWRP from fastboot...

Now that I have 17.1 I can also confirm that the aforementioned "Update recovery" toggle is indeed only present in 17.1 and as such will not help when trying to get from stock android to 17.1.

It is the bottom of the no less than eight toggles in the Memory section whereas in stock android (8.1) developer options only has five...

---------- Post added at 10:22 AM ---------- Previous post was at 10:15 AM ----------

As a more general question to the folks that are frequently flashing a new rom: what is your method of installing all your apps once you have got the new rom running?

I doubt you're going through the Play store hand-picking the apps one by one to install them, are you using Titanium instead?

Are there any things to be weary of when using for instance Titanium to install-all-apps-in-one-go?
[Pixel C Android Development] tabormeister:
Titanium is fine as long as you're not trying to overwrite system apps willy-nilly, but if you're installing Gapps why not use the setup assistant and restore a backup from a previous device? Clean and simple.
[Pixel C Android Development] Peregr1ne:
I've always assumed that will skip any non-playstore-apps, if that is not the case I may be able to save quite a bit of time there possibly...