yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Iggy82:
I must stress to others that you could encounter issues as these new 10.0 builds are effectively BETA. I have faced numerous issues personally, but I see others aren't having the same issues, so I'm not sure what is causing the problems. In all cases, I have followed all the guides for flash, i.e.:

1. TWRP build 3.3.1-1

2. Format Data

3. Wipe system, data, cache, dalvik, etc (i.e. everything!)

4. Flash the latest 10.0 zip

5. Unmount, remount system

6. Flash gapps (Pico variant, 20191006)

7. Unmount, remount system

8. Flash Magisk v20.0

9. Reboot

These are the problems I've had:

1. System wont boot up at, shows Lineage OS boot logo then reboots to TWRP, tried multiple times but fails.

2. With latest November build. System does boot up, but freezes on Welcome screen. Reboot didn't fix this either. Shows the initial blue 'Hello' screen on boot but not responding to touch and no changes on screen if I plug in charger, it appears to be frozen.

3. System does boot up, but Launcher constantly crashing and restarting (You can watch notification/status bar & buttons dissappear and reappear constantly.

4. When full stock gapps were used, Chrome wouldn't open. Chrome beta worked OK. Followmsi recommended I enable permissions for chrome but I didn't have a chance to try as I already started from scratch with Pico variant of Gapps and the problem was gone.

5. Random reboots, seems to happen the first few boots and then fixes itself.

6. 'Dirty Flash' didn't work for upgrade from October to latest November build (i.e. wipe dalvik cache, install latest zip, reboot). It just rebooted back to TWRP no matter how many reboots I tried after install.

Maybe I'm doing something wrong!? I haven't a clue

Update - Successful flash of 20191107 build

This is exactly what I did to get it to boot up successfully, hopefully it helps others. This time I used 20191105 pico version of Gapps beta instead of 20191006 on the last install. I'll update this post if I encounter any issues.

1. Mount all partitions in ‘Mount’ menu

2. Format Data

3. Reboot Recovery

4. Mount all partitions in ‘Mount’ menu

5. Wipe all parititons (cache, system, data, dalvik, etc)

6. Reboot Recovery (as couldn’t mount USB OTG storage)

7. Unplug, replug USB OTG storage

8. Mount all partitions, select USB OTG Storage

9. Install Lineage OS 17.0-20191107 zip (Zip signature verification ON)

10. Unmount, remount System

11. Install OpenGapps pico 10.0 beta (20191105) (Zip signature verification OFF)

12. Unmount, remount System

13. Install Magisk v20.0 (Zip signature verification OFF)

14. Wipe Cache/Dalvik

15. Reboot (Uncheck Install TWRP app options)
[Pixel C Android Development] Guancho:
I think, this is the important part. With just (dirty) flashing the image, my pixel wouldn't boot.

When un/remounting system and installing gapps after flashing the image, it worked.
[Pixel C Android Development] frauhottelmann:
su is hidden with the new kernel! Nice! (I am using the LOS su-addon)

Safety net doesn't pass,but I don't really care for now (hopefully Netflix doesn't become stricter).

On a side note: is it just me or is twrp veeery slow? The animations take forever and so does typing or using the "yes-slider". I am on your latest build. It was slow right from the beginning when I first installed twrp...
[Pixel C Android Development] followmsi:
Thanks for the feedback.

https://github.com/omnirom/android_bootable_recovery/commit/fbb4353a247157d32208f8f133cd1ee42f4fbc49

TWRP is using DRM graphics .. which is still an issue.

Not much devices using it at all.

The TWRP team (Dees-troy) is aware of the problem.

Not sure when this will be fixed.

The functionality is given .. the speed may improve later on.
[Pixel C Android Development] frauhottelmann:
Ah OK. Thanks for the info. Yeah, functionality was never a problem. I was just wondering. Linux DRM graphics is an always popular topic ?
[Pixel C Android Development] ToldYouSo:
The 24 test version has the crashing VPN issue.

Finally have correct recovery.log files
[Pixel C Android Development] followmsi:
Thanks for testing !

MTP is crashing ..

Are you using mtp connection ?

Pls disable mtp before starting the installation.

Still hanging ?

Not sure why it's crashing .. you have cut the logs a bit too early.

detected filesystem ext4 for /dev/block/platform/700b0600.sdhci/by-name/APP

about to run program [/tmp/install/bin/backuptool.sh] with 2 args

/tmp/install/bin/backuptool.sh: cd: line 113: can't cd to /tmp/addon.d/

md5sum: can't open '*sh': No such file or directory

E:[MTP] request read returned -1, errno: 5, exiting MtpServer::run loop

I:[MTP] MtpServer::run fd: 14

Pls send full log of hanging installation ..
[Pixel C Android Development] ToldYouSo:
That was the last line in the log

It happens with or without an MTP connection active.
[Pixel C Android Development] followmsi:
The backupscript restore does not end successfully.

At least it's missing in the logs.

script succeeded: result was [1.000000]I:Updater process ended with RC=0

I:Legacy property environment disabled.

I:Install took 24 second(s).

Did you wipe system before both installation ?

Or just before the hanging one ?

I see you have made a install-queue .. always the same install order ?

Please use the TWRP version from the download share and do the LOS installation again .. (TWRP_dragon_3.1.1-0.img)

Pls send full log ..
[Pixel C Android Development] ToldYouSo:
I don't know what to tell you. Seeing that the installation of LOS 'freezes' all of a sudden should the log also freeze and end abruptly?

This is from the log file with the LOS install that did work. And yes I am very aware that the other log file is missing those lines.

Yes did it before both. But by now I know that wiping or not does not matter. The error occurs both ways

Does not matter if I que ZIPs, install as a single ZIP, same problem occurs. The successful log file was coincidentally a cue that worked, but could just have been as a single ZIP install. (I cut it where it begins to install the next ZIP) And the log file of the one that failed was as a single ZIP and ends abruptly. But again, could have been vice versa, doesn't really matter.

Thats the same recovery I am using I have tried reflashing that also.

I would like to point out the fact that this problem only started to occur in the most recent (24th) LOS. Never had the problem before that... Installing in cue's or as a single zip, wiping or not wiping, install from OTG, or first copy to /sdcard. Copy it from OTG or through MTP. I have tried everything but this problem seems to be as random as ****.

I have NEVER had this problem before. Only in the latest LOS release. And since it is so frequent I don't think it because of some kind of wrong input on my end. Since that input has always worked on older LOS releases. Which I have flashed also with TWRP_dragon_3.1.1-0.img recovery.

Maybe I'm missing something here and it doesn't sound logical (at least to me there is very little logic). But I am not the only one with the problem.

Sorry if I sound a little annoyed. It has been a long day....
[Pixel C Android Development] cam30era:
[MENTION=4657624]ToldYouSo[/MENTION],

That's the risk we take, when we unlock bootloader, install custom recovery, root, and install custom kernels and ROMs. You should look at it as a learning experience.
[Pixel C Android Development] ToldYouSo:
I am very aware of that. And I am all up for learning new stuff. But the Pixel C just has been a pain in the butt for a lot of the time for me and is THE worst Pixel/Nexus device to do custom anything on. The 30 second delay at every friggin boot alone is really getting old when rebooting dozens times a day.
[Pixel C Android Development] followmsi:
You should always use "official" TWRP version !

https://dl.twrp.me/dragon/

The version inside download folder is build for testing ..

I want to understand problems with TWRP as I need to forward them to TWRP team for fixing, if applicable.

For me your problem sounds randomly too .. even worse to find the root cause.

As explained before .. since last version the normal unchanged LOS installer is used.

Different (newer) scripts are used in official version..

Could be related to BusyBox .. still needs to be verified - using official version only !
[Pixel C Android Development] ToldYouSo:
Ok maybe it's not so random as I said. I found patience within myself to go through all the steps again. It is confirmed that it is the official TWRP recovery used.

It seems to happen after I wipe the system partition. I said before it did not matter but I must have confused it with wiping other partitions.

Also, wiping system, and then rebooting recovery produces the same error. Basically when I wipe the system I just have to go through the process of the first install failing, reboot recovery and then install again. When not accidentally wiping system again it always seems to work that second time.
[Pixel C Android Development] jeffyca:
I can confirm that I am having the same issue as above. Using the newest official TWRP and when flashing 0524 build, installation hangs upon flashing when wiping everything. Once I reboot TWRP and flash 0524 again without wiping, it installs fine.
[Pixel C Android Development] followmsi:
Thanks again for testing and reporting .. I have to confirm the issue !

Did have time to test myself today.

Wiped system and made a fresh installation ..

For me its hanging at the same position ..

detected filesystem ext4 for /dev/block/platform/700b0600.sdhci/by-name/APP
detected filesystem ext4 for /dev/block/platform/700b0600.sdhci/by-name/APP
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
/tmp/install/bin/backuptool.sh: cd: line 113: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory

Tested official TWRP 3.1.0, 3.1.1 and owncompiled 3.1.1 version too - same result.

This is an issue !

Especially if the "official" LOS version will come hopefully soon .. with the same installer problem !

The "workaround" you have found is working fine.

( To reboot into TWRP and start installation again - without system wipe. )

But it's not an acceptaple solution either !

Made a quick check ..

https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/prebuilt/common/bin/backuptool.sh

restore)
if check_prereq; then
if check_whitelist tmp; then
exit 127
fi
fi
check_blacklist tmp

Compared "my" backuptool.sh script and this part is missing .. the reason why it was working before - also with system wipe.

The system has been installed succesfully, but the "backuptool.sh restore" part is hanging at the whitelist/blacklist checks.

This problem needs to be analysed more deeply ... I will need to get in contact with TWRP team first .. and maybe LOS team too.

For me it's looking like a TWRP issue right now - as the same code is used for all other LOS devices too - the script is part of "android_vendor_cm" - used by all LOS ROMs the same way !

The TWRP shell is busybox .. maybe some different compilation flags are required.

Sorry, for the "double" installation in the next time .. for the next release you will not need to wipe system again.

This is my mistake - as I should have used the regular installer scripts earlier - to find problems like this earlier too :)

Right now I have no idea how long it will take until the problem will be solved !

Cheers
[Pixel C Android Development] followmsi:
Just a short update ..

As it looks like the installer script is hanging because of this line ..

grep -q $s /system/addon.d/blacklist && rm -f $f

https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/prebuilt/common/bin/backuptool.sh#L50

The grep command seems to hang.

Made a new version yesterday .. changed this line to make it working also on wiped system !

If you want to play with latest version .. until this problem is solved.

lineage-14.1-20170601-UNOFFICIAL-dragon.zip

Cheers

EDIT:

After several chats with TWRP and LineageOS team we have agreed on a general solution for all LineageOS devices.

To be changed in LineageOS sources. (android_vendor_cm)

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

Once the change is fully approved and merged the LineageOS installer will not hang in TWRP anymore.
[Pixel C Android Development] sxg75:
Great work followmsi ... few days left on our way to be LOS official

:good:
[Pixel C Android Development] J_M_H:
Thanks followmsi for your hard work. With Google support for this device ending this year, I was getting worried about the Pixel C future.
[Pixel C Android Development] followmsi:
Thanks for the feedback .. actually I am still fighting.

The first build should have been ready already last week .. failed.

https://jenkins.lineageos.org/job/android/3339/

The build today .. just a few hours ago. - failed.

https://jenkins.lineageos.org/job/android/3507/

The problem is related to the official signing process of the ROM.

https://wiki.lineageos.org/signing_builds.html

Maybe this is related to "... its strange partition system and other issues. " .. like in the article you mentioned. :)

I did all the steps locally without problems .. but the signing process in production is a bit different.

All this takes a lot of time .. not sure when the first official build will be available for download.

Just to give you some more information for better understanding ...

Cheers
[Pixel C Android Development] apascual89:
Having the same issue trying to add official support for the pixel devices on AOKP. Just like you mentioned local builds are fine, but fail when signing with official keys. I'll update you if there's any progress.
[Pixel C Android Development] ToldYouSo:
thnx for the update and hard work man...

something for the future though..... the ''do not disturb'' function really annoys me when I just want my device to be silent (but keep receiving messages and stuff). Wasn't there a setting in stock where you could choose to not engage the DND function with the volume buttons? Or like a little extra step between ''low volume'' and ''Do not Disturb''? I keep fiddling with it now to mute it but instead it is on the lowest volume possible (but still making sound) without going to the DND function....
[Pixel C Android Development] MrTim68:
This is exactly what I found.
[Pixel C Android Development] Alxoom33:
I tried to clean flash, used Open Gapps 11/7 beta gapps for Andriod 10. Had issues as the playstore app did not work, tried both full and stock versions. I used the 11/4/19 Open Gapps that I had on my USB drive and the playstore app worked! Was able to recover my data and apps and set up my device.

So, watch out for the 11/7 gapps. Use the 11/4 versions or look for a more updated version.
[Pixel C Android Development] followmsi:
I did not search .. but for now I get all Opengapps BETA versions from here ..

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

And some special versions from [MENTION=7280276]ipdev[/MENTION] :)

It seems your are using different builds ..

Pls post download link of your gapps versions ..

Thx.
[Pixel C Android Development] Alxoom33:
I was using the 11/5 beta builds from Source Forge link. They are the one's that I got a bad Google Play from, with both the full and the stock versions. I used the previous versions, 10/6 full and stock that I had saved on my usb drive, and they were able to access Google Play and download my backups successfully.

Sorry I got the dates of the Gapps wrong, but please watch out for the 11/5 gapps, especially if you are clean flashing!
[Pixel C Android Development] Matt Carter:
No OS installed and Gapps error

After installing the latest version of the ROM 11/7/19, if I try to reboot it, a waring of no Os installed apears. Also if I try to install Gapps, it says the current version is android 9 not 10.
[Pixel C Android Development] Alxoom33:
Sounds like you got a bad download. Try a fresh download. What Gapps package were you using?
[Pixel C Android Development] Matt Carter:
I've tried:

- open_gapps-arm64-10.0-mini-20190928-BETA

- open_gapps-arm64-10.0-mini-20191006-BETA
[Pixel C Android Development] Alxoom33:
Those should both work. Try a fresh download of the Rom. Mount System and vendor and flash the Rom and gapps seperately.
[Pixel C Android Development] flyinggeek112:
Got a somewhat probably obvious question: how do I update after installing LineageOS 17 as described here? E.g. how do I get security updates when they get released. Will the LineageOS downloader from the Android store work?

Thanks for a quick pointer here...
[Pixel C Android Development] Alxoom33:
You will need to wait for LOS 17 updates from [MENTION=5480152]followmsi[/MENTION].
[Pixel C Android Development] kurze12:
Lineage 17 is fine, thank you! :good::good::good:

Everything was very easy with the tool "Nexus Root Toolkit" : https://www.wugfresh.com/nrt/
[Pixel C Android Development] synchrolees:
Great thanks to your hard work on Pixel C!

The 1107zip Flashed successfully, it's stuck in the second screen while rebooting then reboot to rec. I had to wipe the system partition and flash gapps &magisk again so that I got my Pixel C boot successfully. This situation had appeared several times in previous updates of Q. Could you tell me the reason?
[Pixel C Android Development] followmsi:
pls read first page first !!!

system-as-root (SAR)

For gapps installation issues and more information ..

Fresh Installation / Upgrade from any other ROM:

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

Upgrade from previous lineage-17.0 builds:

1. Boot into TWRP

2. Wipe SYSTEM only !

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
[Pixel C Android Development] szescxz:
I know Oreo development is pretty much being ignored nowadays, but - can anyone check out the official LineageOS 15.1 builds after Nov 15? There seems to be some weird crashes starting from that build, e.g. on my device Chrome always crashes after completed downloading a file.
[Pixel C Android Development] Elektron60:
My Chrome crashes also at the end of download. Im waiting........
[Pixel C Android Development] Elektron60:
And Chrome craches......

---------- Post added at 09:22 AM ---------- Previous post was at 09:17 AM ----------

Firefox works......
[Pixel C Android Development] followmsi:
Yes .. no dragon device/kernel/vendor changes for long time.

Quickly checked general lineage sources for Oreo .. not much activity except for monthly security patches.

November security patches got merged on Nov. 13 .. the date fits to your problems.

Did you removed chrome completely from system .. uninstall updates .. etc. .. same problem ?

Did you install chrome beta for testing ? .. same problem ?

Did you made full clean install for testing ? .. problem still persist on clean install ?

If you go back to build before Nov 13 ..all is working again ?

Do you use gapps package to install chrome as system app .. or install it just from Playstore ?

Of course, we will need logs .. full logcat.

We need more information to understand the root cause of the problem.
[Pixel C Android Development] szescxz:
Yes, but with data restored from Google Drive.

Yes.

Both - I installed OpenGApps STOCK, and then update it via Play Store.

I may try to grab a logcat next time, but I'd like to add that my device has issues other than Chrome as well (Play Store crash at startup, SafetyNet check fails (the error is failed to connect to Play Services, IIRC), Google Play Games does not work in supported games, etc). I think they are all Play Service related, as clearing Play Services' data can solve the issue temporarily.
[Pixel C Android Development] followmsi:
As said above .. we will need logs of the problem(s).

Full clean install (without) data restore should be tested as well.

Pls use same gapps package for all your testing.

Thanks
[Pixel C Android Development] Ookamix:
Hey, how long would it take approximately until the camera is fixed?
[Pixel C Android Development] pierrebe:
A certain time :D
[Pixel C Android Development] Iggy82:
Disable Location permission in app settings for Chrome to fix this. (Settings > Apps & Notifications > Chrome > Permissions > Uncheck 'Location')
[Pixel C Android Development] jailbird2:
Has anybody else had any weird BT issues with 11/07?

Using the “official” (old) releases months ago everything was fine, so I’m assuming it’s something new.

Since the Pixel C doesn’t have its own GPS/GNSS receiver, I use a Dual brand BT GPS receiver with my Pixel C. Lately once I pair the devices, everything is gray until I deep sleep or reboot (so basically break the connection somehow). Once that happens, it’ll never reconnect unless I have the Pixel C forget the Dual and then repair with it. It’s almost like the pairing information is getting lost somehow.

On a side note, thank you followmsi for getting this device going as well as you do. It’s sad that after all of these years that it’s still basically the best Android tablet around. Do you accept donations for your hard work?
[Pixel C Android Development] LSS4181:
Is there any room for improving power efficiency?

Tried the 20191107 build and I'm finding the tablet is performing rather inefficient.

The UI is not smooth, and after playing games for a while the tablet starts feeling very very hot and slows down due to overheat. This was not the case with Android 9 based ROMs.

Also, does anyone know how to disable captive portal detection on Lineage 17? Tried the good old ways (that I've been using) to change captive portal URL to my own server but no avail, the device still says no internet access, and would not auto connect to the home router because of this.
[Pixel C Android Development] drewski_1:
i was having issues with Google Apps crashing so i did a full wipe of the device and now it won't boot!

during the boot animation it reboots to recovery!! :crying:

restored my Pie backup. tried again and same result . . .
[Pixel C Android Development] followmsi:
You jumped from lineage-15.1 to lineage-17.1 ?

Did you DUAL receiver still work in lineage-16.0 ?

Did you try "unified" kernel for testing too ?

Some time ago I tested BT pairing with my BT audio speakers .. worked ok.

We will need logs to check your problem.

No donations pls.
[Pixel C Android Development] followmsi:
https://review.lineageos.org/c/LineageOS/android_packages_providers_DownloadProvider/+/264274/

This change is still missing .. not sure why it has not been merged - like in 14.1 and 16.0.

Have asked for clarification .. we will need to wait.

If you have time you can make test build to prove missing patch is related to "your" problem.
[Pixel C Android Development] followmsi:
There is always room for improvement. :)

Not sure if I will be able to replicate and troubleshoot your "heating" issue ..

As I will not play games to reproduce .. maybe some other stress test will work too.
[Pixel C Android Development] followmsi:
You try to install 17.0 or 16.0 ?

Actually clean install should work on both lineage versions.

Dirty upgrade from 16.0 to 17.0 is not working smoothly .. I do recommend clean install.
[Pixel C Android Development] followmsi:
Quick update !

Lineage team has merged the 4 "missing" changes for November security update a few hours ago !

https://review.lineageos.org/q/topic:"O_asb_2019-11"+(status:open OR status:merged)

They should be part of next build .. https://www.lineageoslog.com/15.1/dragon

New build is triggered .. https://buildkite.com/lineageos/android/builds?state=scheduled

Pls test on new build .. and pls report if all is good again !

Thanks
[Pixel C Android Development] Alxoom33:
Any changes or updates to November 17.0?
[Pixel C Android Development] followmsi:
No .. just Oreo was affected.
[Pixel C Android Development] drewski_1:
Sorry, I wasn't clear on the details¡

I tried 17.0 and am back to 16.0 for the time being