yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] shadow_empire1:
This was finally working for me now:

1. Boot into TWRP

2. Wipe SYSTEM and DATA

3. Install ROM: lineage-17.1-20200113-UNOFFICIAL-dragon.zip

5. install gapps (arm64): open_gapps-arm64-10.0-pico-20200116-BETA.zip

6. install Magisk: Magisk-v20.3(20300).zip

7. Wipe CACHE and DAVLIK

8. Reboot into system -> "without flashing twrp"!!!
[Pixel C Android Development] shepliu:
It works well, but no netflix, after magisk hide, netflix is back, thank you!

Solution for lineage boot logo is looping, don't wipe system partition!
[Pixel C Android Development] followmsi:
It's hardcoded in kernel .. we change to enforcing once sepolicies are in place .. this will take longer.

If you switch now to enforcing you may get strange issues.
[Pixel C Android Development] rauhut:
Smooth installation

Hi followmsi & all!

Updated successfully to *0113 as a dirty flash over last version, this time without any manual installation of OpenGapps, Magisk, unmount/remount actions. No issues so far, many thanks. :good:
[Pixel C Android Development] QuantumSingularity:
Opengapps for Android 10 is now official (non beta)...

https://opengapps.org/
[Pixel C Android Development] Alxoom33:
Thanks for the heads-up. Noticed only Nano and Pico versions available. Downloaded both and flashed the larger, Nano gapps. Seems to be working well so far.

Thank you, again!
[Pixel C Android Development] followmsi:
Made a test build .. https://crdroid.net/

Still need to check myself.

Maybe "you" want to test as well ..

crDroidAndroid-10.0-20200128-dragon-v6.2.zip

Pls install Gapps and Magsik.

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

Enjoy :p
[Pixel C Android Development] braunie:
WLAN disabled after time

I yesterday installed the latest build (20200113). It's very good and smooth - I like it!

But after a few hours WLAN is disabled by it self and I have to enable it manually. Bug or feature?

Thank you for our work :)
[Pixel C Android Development] zonlicht:
Following the steps below seem to flash my device into a boot animation, then shut down sequence. Also tried with just wipe + ROM flash without gapps or magisk. Any thoughts on my situation?

1. Boot into TWRP

2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)

3. Install ROM.zip

4. WORKAROUND for Android 10 system-as-root: unmount / remount SYSTEM in TWRP mount menu

5. install gapps (arm64)

6. install Magisk.zip (20.0+)

7. Wipe CACHE and DAVLIK

8. Reboot into system

edit: it seems to be a bad gapps. Also did a mount/remount between each step sine I was getting system mount errors
[Pixel C Android Development] 12paq:
I clean flashed crDroid and it's running fine so far. Google set up was glitchy, but no big deal.

One thing to report, in <settings>crDroid Settings> fails to launch and crashes. So the ROMs specific features are not accessible.

Always fun to try new ROMS, so thank you!

Edit: Workaround - you can find many but not all of the missing settings by using the settings search bar.
[Pixel C Android Development] followmsi:
Thanks for testing .. still have to test myself.

Pls make logs of the settings crash .. we may can fix it quickly.

Google setup glitchy .. I am still not confident with opengapps status. :)

Which gapps version did you use ? Pico only ?

Cheers
[Pixel C Android Development] 12paq:
Thanks,

I used these <open_gapps-arm64-10.0-nano-20200124.zip> Google setup was buggy but worked. All good after setup.

And a log of the crDroid settings error is here: https://del.dog/wexulegudo
[Pixel C Android Development] followmsi:
I still recommend Pico version .. anyway.

Quickly checked your few log lines .. quite generic failure message. Not much logs either :)

No time to check myself now .. same crdroid settings crash on Nexus 7 (flo) .. seems to be general crdroid problem.

As I have not much time left for Android in the moment I prefer to wait for crdroid fixing this problem .. and make new "fixed" dragon build a few weeks later :)

Cheers
[Pixel C Android Development] braunie:
Also for me the "Expanded desktop" feature is not working. If I touch it it goes back to root settings.
[Pixel C Android Development] 12paq:
I understand completely.

Thank you for all your time and efforts!

?
[Pixel C Android Development] Thug Life of the France:
Hey there, could I know how to root please ?
[Pixel C Android Development] redukt:
Install Magisk 20.3 after rom / gapps...
[Pixel C Android Development] braunie:
The WLAN was stable the last few days. But could you please fix the "Expanded desktop" feature? That would be nice :)

Thank you for this awesome rom.
[Pixel C Android Development] followmsi:
https://review.lineageos.org/q/expanded+desktop

Lineage is working on this .. they may drop this feature in 17.1.

This stuff is not device related .. all 17.1 devices waiting for this "feature"

Cheers
[Pixel C Android Development] braunie:
Thank you for that information :)
[Pixel C Android Development] xda_jm:
Hia followmsi,

works really nice. Only since 17.x (I think my device is just getting old), the HW Accell stops at 85% battery. 2 months ago it was at 75%, and 6 months ago at 50% ...

Anyone knows what's going on?

This is the main device I use to play War Robots ... and I can barely play 20Minutes now :(
[Pixel C Android Development] Thug Life of the France:
Just to confirm, I have the exact same problem.

The UI becomes slow af when the battery drops to 85.

After 85%, it starts to become more responsive.
[Pixel C Android Development] followmsi:
Have a look here ..

https://xdaforums.com/showpost.php?p=78567865&postcount=951

Pls read the posts before as well ..

Cheers
[Pixel C Android Development] Thug Life of the France:
Yeah, I did it a week ago, charging it to 100% then discharging to 7% five Times ( when the tablet actually shuts down is 7% for me)

Quite interesting to see someone having the exact same issue with your ROM, your kernel, your recouvery (even if it has nothing to do)

I also got the throttling only at 50% 6 months ago

By the way, I asked a while ago for the boring 30 seconds of delay when starting the unit up

I remember that we were talking about switches inside but since there isn't any switches inside, I'd like to know if it progressed.

Cheers, Lothaire
[Pixel C Android Development] followmsi:
Just test your "throttling" issue on last Oreo Google stock ROM .. same problems ?

As discussed last year .. seems to be hardware/battery issue.

No updates on the 30 seconds delay .. and no time to look at this stuff.
[Pixel C Android Development] followmsi:
Android 10 - February 2020

New build has been uploaded ..

Opengapps for Android 10 is "stable" now .. for the moment pico and nano packages only.

This month I have patched framework/base to support microG.

lineage-17.1-20200209-UNOFFICIAL-dragon.zip

Changes:

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

- 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] ger_kar:
Tested reinstallation and dirty installation, no problems.

---------- Post added at 07:34 PM ---------- Previous post was at 07:07 PM ----------

Tested reinstallation and dirty installation, no problems.
[Pixel C Android Development] xda_jm:
Installed over old version. No problems so far :)

Thx a bunch!
[Pixel C Android Development] schmitty782:
I did a clean install. Lineage works well. But when I install GApps Nano (version 10.02.2020) the system no longer boot and I always end up in recovery mode. Which GApps do you use?

greeting

Christian
[Pixel C Android Development] frauhottelmann:
Pico and nano should work. Did you install the arm64 version? I've installed them both at the same time ??
[Pixel C Android Development] 2ig2ag:
Screen timeout does not work after dirty flash lineage-17.1-20200209-UNOFFICIAL-dragon.zip

Edit: never mind. It works again after resetting option
[Pixel C Android Development] Alxoom33:
Nano gapps work fine. Make sure you had a clean download by checking md5. Also make sure you downloaded the arm 64 nano gapps for Android 10. Not some other version or earlier operating system, i.e. Android 9.
[Pixel C Android Development] followmsi:
I was able to trigger a new build today .. and still not tested myself.

Most probably the crdroid settings will still crash.

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

Like mentioned before the crash seems to happen on "wifi only" devices .. crdroid does not have much "wifi only" devices running Android TEN.

Your logs are pointing to Statusbar.java .. and some telephony settings code .. maybe the reason for the crash on "non-phone" devices.

Would be still very nice to get a "fully working" crdroid ROM for dragon. :)

[MENTION=2850740]12paq[/MENTION] pls contact crdroid team directly.

Pls let them know about this issue and send them your logs.

Thanks a lot for your help !

Cheers
[Pixel C Android Development] 12paq:
I'm on it!

Thanks for you time and the new build.

Fyi, I am still using the 1rst CRDroid build as my DD. Even with the CRdroid settings bugs it's a good build and a good ROM.

---------- Post added at 07:54 PM ---------- Previous post was at 06:54 PM ----------

I'm on it!

Thanks for you time and the new build.

Fyi, I am still using the 1rst CRDroid build as my DD. Even with the CRdroid settings bugs it's a good build and a good ROM.

Thx!
[Pixel C Android Development] followmsi:
Pls let me know when you have updates on this issue.

Will make new build once we have patch for it.

Thanks !
[Pixel C Android Development] splinterededge:
wifi-only dragon

I have installed crDroidAndroid-10.0-20200213-dragon-v6.3.zip on my wifi-only dragon and found that crDroid settings was indeed crashing when attempting to launch. I am not am much help around here, but if I will see if I can find the time to submit something to crDroid. Thanks everyone, this is really good work.
[Pixel C Android Development] Alxoom33:
How does crDROID compare with LOS 17.1 in terms of custimizations and stability.

I tried new DU RC build, very nice customizations, but it froze and crashed while using photos, setting up widgets and using the browser. So I'm back on LOS 17.1. :)
[Pixel C Android Development] ipdev:
Hi all. :)

It's been about a month since I was able to use my Pixel C.

Backlight issue and took some time to get it to turn on again.

Long story. ;)

OpenGapps is currently in a state of flux.

I haven't had issues with some builds while others have. (Including same devices.)

Builds have been pulled a few times recently due to apk versions or new permissions.

Pico seems to be the safest but Nano seems to be the most stable.

If that makes sense to someone, maybe they can explain it to me.. ;)

They are setting up a testing group and I'm sure some will start complaining when the stable builds become weeklies.

I'm not a big fan of Nightly/Daly builds in general. Most of the time there is no change and just a waste to build/flash. This is OT here but, a little insight into what is going on in the world of OpenGapps.

crDroid is based on lineage and has similar/more customization. If available for the device, it is one of the roms I recommend trying when some one asks "What is the best rom for NameOfDevice ?"

If you like DU you will probably like crDroid. ;)

As others noted, (WiFi Version) crDroid Setting does not work.

Most customization is under crDroid setting. (Gestures for example, you are stuck with the default 3-Button nav bar.)

If you have a WiFi device, you will probably want to wait to try crDroid until settings is fixed.

Note:

There is no best rom. Just the one you like the most and fits your needs, may be different from device to device. Currently I'm using; abc, aex, Candy, crDroid, GroundZero, Lineage and Validus. (Most devices are Android 10, some still on 9)

Note 2:

I uploaded my Dragon (WiFi) crDroid logs GoogleDrive - Link

- ROM only, No Gapps or Magisk.

- Running insecure to grab logs at initial boot. (Sometimes it make a difference.)

- Haven't looked through them completely. (Just skimmed them quickly.)

- Feel free to look or pass this link on to others who might be able to help.

Cheers all. :cowboy:
[Pixel C Android Development] Thug Life of the France:
By the way any news for the kernel ? Will you continue updating it, or will it ever get a branch upgrade ? Let's say 4.4 or 4.9 ?
[Pixel C Android Development] followmsi:
One new version for the waiting time :)

lineage-14.1-20170606-UNOFFICIAL-dragon.zip

lineage-14.1-20170606-UNOFFICIAL-dragon.zip.md5sum

The change for the installer issue has been already merged and is part of this release.

Pls test fresh install - wiping system partition - the installation should work without issues now.

This time we use "official" LineageOS kernel too.

The June updates are also included.

Pls use vendor.img from June now !

Enjoy ...
[Pixel C Android Development] Reuben_skelz92:
Is there going to be a OMS version
[Pixel C Android Development] followmsi:
Yes .. here you are :)

lineageOMS-14.1-20170606-UNOFFICIAL-dragon.zip

lineageOMS-14.1-20170606-UNOFFICIAL-dragon.zip.md5sum

- June updated included

- tegra-3.18_kernel_dragon_v170606_unicorn-xceed-followmsi

Enjoy !
[Pixel C Android Development] Reuben_skelz92:
Awesome thanks. Can't live without my pixel theme haha
[Pixel C Android Development] Reuben_skelz92:
Dunno if it's something you look into but I've noticed substratum never changes the nav bar. I could imagine it's a lineage problem
[Pixel C Android Development] ToldYouSo:
Tested and still crashes when disconnecting VPN everything else works normally.
[Pixel C Android Development] followmsi:
Thanks again for the logs and your testing ... a short summary of the issue.

- On Xceed kernel no VPN crash

- On LineageOS kernel no VPN crash (close to google stock kernel)

- Test 24 kernel was a merge of stock and DU kernel only - VPN crash

- On unified kernel - VPN crash

- You say the VPN crash happens only on LineageOS

- You say the unified kernel does not crash VPN on stock ROM

As it looks right now the problem seems to be related to DU kernel patches .. but only crashing on LineageOS.

We are talking about 600 DU changes over a long time of period.

This will take time to find the root cause !

And maybe the merge of all 3 kernel sources is the reason for the crash and not only the DU part.

The logs are not really helpful either .. when I have some more time I will try to replicate the issue on my device.

Quick tests using OpenVPN client I am not able to reproduce a crash at all.

If you use the "normal" LOS version you are already using the lineageos kernel where VPN is not crashing.

If you want to use the "OMS" version you need to install the lineageos kernel I have made for you.

Maybe next OMS release will also use lineageos kernel.

As said above .. to find a proper solution for this problem will take longer !

Hope you have a better understanding now ...
[Pixel C Android Development] followmsi:
Our problem is related to the chromeos signing part ... vboot_signer.sh, futility and devkeys .. etc.

They are missing in otatools.zip today.

Now we have 2 new changes (android_build) which are fixing this issue and including them into otatools.zip.

But the PATH is not correct - the "sign_target_files_apks" script is still failing.

if we move the required folders into the "correct" location, after otatools.zip extraction, all is working fine.

The "best" solution has not yet been defined :)

Pls let me know your results ..
[Pixel C Android Development] apascual89:
I'll let you know. Someone with far more knowledge than me is trying to figure it out.... I'll keep you informed.
[Pixel C Android Development] Alessandro999:
Whats different between Smaug and dragon
[Pixel C Android Development] followmsi:
There is no difference .. Pixel C, ryu, dragon and smaug - all names are the same device.

For example the chromeos kernel team seems to prefer the name "smaug" ;)
[Pixel C Android Development] followmsi:
Both changes are merged now .. :)

https://review.lineageos.org/#/c/176470/

https://review.lineageos.org/#/c/176468/

Now the otatools.zip contains all the required tools for proper chromeos signing while release signing.

The first official signed dragon release is coming closer.

Yes, pls keep me informed ..

Cheers
[Pixel C Android Development] NYCHitman1:
It's a theme issue. Google separated the nav bar assets in 7.1.2, which requires themers to theme the sw900dp drawables as well. Unfortunately, none (that I am aware of) have.
[Pixel C Android Development] apascual89:
Will do, quick question, is ambient display working for you?
[Pixel C Android Development] Reuben_skelz92:
Ah ok. Thanks:) I've found 1 paid theme that worked
[Pixel C Android Development] followmsi:
Yes, works for me .. but as I did test the feature not all messages/notifications were triggering the feature.

Not all messages/notifications are triggering the wake-up and showing up shortly on dark background.

Maybe settings related .. made no further tests here.

Still use my case for dragon .. don't see them anyway ;)

EDIT:

The gestures / moves will not work due to kernel limitations and disabled proximity sensor.
[Pixel C Android Development] apascual89:
Got it. I'm late to the dragon game, but finally got mine. Since you're doing RR builds as well I'll probably be putting out AOKP builds soon..... Will look at Ambient display as well. Great work on the LOS trees!
[Pixel C Android Development] followmsi:
Please do so .. publish some AOKP builds.

As more ROMs we have as it's better for the dragon device !

Do you want to take over RR for dragon ? ;)

Now as all the relevant stuff is inside the LineageOS sources you will have good chance to make it official quickly.

You will take over the thread, the builds and the "making official" ?

Pls let me know .. I would appreciate it.
[Pixel C Android Development] apascual89:
LOL ok, if you want me to I'll take over RR, I can also probably put out AOKP, but I don't really have the time to actively do both :crying:
[Pixel C Android Development] followmsi:
Sounds like a plan ;)

Did you already made a RR build for dragon ?

Maybe the following link will help you .. especially the device tree.

https://github.com/followmsi/manifests/tree/dragon-resurrection-cm-14.1

Pls let me know when your first build is ready.

If you have questions, don't hesitate to get in contact with me.

Just sent the me a private message on XDA.

Is this Ok for you ? .. is this OK for the new RR maintainer of the dragon device ? [emoji106]
[Pixel C Android Development] UberPrutser:
i finally decided to install LineageOS on my Pixel C since there are no updates any more since June last year and I want to have a dark theme.

Now I tried to install 15.1, following both the instructions on XDA AND the ones on LineageOS their website but everything goes well, except I don't see any Gapps installed (while I sideloaded them).

I have tried multiple versions of 15.1 and multiple Gapps packages but for some reason I can't see the Gapps installed.

Now I installed 17.1 with the pico Gapps package for 10 and this works fine but... I really want to have full encryption as I travel and work on my device.

Anything that might point that the instructions are outdated on both LineageOS and XDA?
[Pixel C Android Development] Dhalsim43:
Are you sure that you have downloaded the good gapps version : arm64 8.1 ?
[Pixel C Android Development] UberPrutser:
Sir, yes Sir.

I also tried multiple versions (as in nano, pico, even full), and also to install the arm one.

Of course the arm one gave an error that the LineageOS forces arm64 so it cannot be installed.

I flashed many devices in the past and also contributed to CyanogenMod way back (2012 - 2014) so I was just unsure if I am lacking skills now. :)

I also tried to flash the vendor.img first and then the Gapps .zip but same results, as mentioned in the OP.

And erasing the partitions in fastboot also didn't do anything.

The combination I used without succes:

lineage-15.1-20200214-nightly-dragon-signed.zip + open_gapps-arm64-8.1-nano-20200215.zip, open_gapps-arm64-8.1-pico-20200215.zip, open_gapps-arm64-8.1-full-20200215.zip

lineage-15.1-20200123-nightly-dragon-signed.zip + open_gapps-arm64-8.1-pico-20200215.zip

And also restoring the devices completely with the original Ryu June 2019 firmware between extra try, including the oem lock / oem unlock to ensure everything is as it was out of the box.
[Pixel C Android Development] Alxoom33:
Did you do a fastboot format data before flashing back to 15.1?
[Pixel C Android Development] Matt Carter:
Version not matching

I'm trying to update from lineage 16 to 17.1 with your files but when trying to install GApps, it stops saying the versions don't match, that my ROM is android 9.0.
[Pixel C Android Development] followmsi:
Pls test older gapps version before Mid January !

Like this here ..

https://sourceforge.net/projects/opengapps/files/arm64/20200111/

Big mess since they merged android 10 stuff into master branch.

Cheers
[Pixel C Android Development] followmsi:
For dirty upgrade wipe system only .. install new ROM and gapps pico for TEN .. maybe magisk afterwards.

Wipe cache and dalvik only .. reboot into system.
[Pixel C Android Development] followmsi:
Another wifi only device ..

https://github.com/crdroidandroid/android_packages_apps_crDroidSettings/issues/525

Have added a quick comment too :)

Cheers
[Pixel C Android Development] followmsi:
Like mentioned in kernel thread .. only unregular updates for 3.18 !

No for 4.x branches .. takes too much time.

vartom was working on 4.x .. no idea about android intergration.

If you use linux on dragon device you may can use 4.x kernel already today.

Cheers
[Pixel C Android Development] NYCHitman1:
FWIW, I upstreamed the kernel a ton which is on our GitHub. However, I've officially dropped support for the device altogether as I'm moving to a newer device -- so I will no longer be providing updates for Dragon.
[Pixel C Android Development] Alxoom33:
Sorry to hear that. I thought it was only for the DU rom. Take care and thank you for all the work that you have done!

---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------

Fyi, I am currently using LOS 17.1 with the 2/15/20 open Gapps Nano package without any problems whatsoever. Been using them for a few days.
[Pixel C Android Development] UberPrutser:
I feel stupid now, only changed the type of Gapps, not the build... :silly:

In other words, it works now! Many thanks!
[Pixel C Android Development] Vartom:
Android launch has not yet tried on the 4.9 kernel. Launched Linux for Tegra and twrp recovery.
[Pixel C Android Development] SnapCount:
Is image tearing/flashing normal for this build guys?
[Pixel C Android Development] 12paq:
Thanks for all of your work.

Just out of curiosity, which newer device?
[Pixel C Android Development] NYCHitman1:
Haven't decided between Galaxy Tab S6 or an iPad Pro. Currently weighing pros and cons of each.
[Pixel C Android Development] tschmid:
Do have a tip what youve done about backlight issues? Ive a black screen after a drop, no visual display defect. Maybee a cable problem

Gesendet von meinem Pixel 2 XL mit Tapatalk