yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sherdog16:
For some reason my computer isn't recognizing my phone via ADB. I only have the Lineage recovery. Am I screwed?

When I get home I'll grab another cord and try tomorrow but I think I just learned a hard lesson about using the updater

---------- Post added at 09:15 PM ---------- Previous post was at 08:52 PM ----------

I think I'm really screwed. I did the factory reset when it prompted after it tried to boot and now ADB says "unauthorized". Is this the kill shot? Perfect "oh crap" storm?

Any insight would be appreciated

---------- Post added at 09:49 PM ---------- Previous post was at 09:15 PM ----------

Follow-up for those who may have issues like mine:

Booted to bootloader (hold volume down and power)

Fastboot booted a TWRP image "fastboot boot [filename].img" (images available on the website)

Switched slot

Rebooted

Really wished i didn't factory reset
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
to switch to the other slot you can do the following.

boot into bootloader mode and give the following command: fastboot set_active other

or

boot into twrp and tap 'reboot' then tap the slot you want
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kkjb:
Looking forward to "let there be light" to dev team members....thank you
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] magsu:
im still having this issue, on 7-26-19, JUST upgraded from unofficial

---------- Post added at 06:23 AM ---------- Previous post was at 05:45 AM ----------

so as of this moment, is there no fix to this other than reverting back to the may version?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sindalf:
rasor please, can we have Android q gestures on los 16 ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] B2Pi:
I find that, when I enable the hotspot, I can get a connection, but it doesn't appear to relay packets. I've already tried my old standby trick of setting tether_dun_required to 0, but still no joy. Has anyone experienced and/or solved this problem? I presume that there are others hotspotting successfully.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] skatastic:
No problems here. I use hotspot everyday with my android head unit in my car.

---------- Post added at 04:22 AM ---------- Previous post was at 04:19 AM ----------

Is VoLTE with Verizon supported on LOS 16 on pixel xl? I've read it works on some phones but not others but I can't find which are supported?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] zultron:
Do not install twrp app

It's important to note, DO NOT install TWRP app.

Installing it causes boot to stay on the LOS startup screen for a long time and then reboot back into recovery, with no obvious way to fix the problem other than reinstalling.

THANK YOU for this guide. Without it, setting up my new Marlin would have taken much longer than the two days I needed (I'm dumb: one day to find this thread, the other to follow the instructions as written).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Crumplet:
Gapps not working on this rom that is posted in the OP...Also no other outsourced Gapps working aswell.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bigmike35:
Was able to get Open Gapps to work but it was finicky. For me to get it to work, I could not log into Wi-Fi else it would hang on "Updating." I believe I skipped and went through the rest of the setup then once through the screens, came back and signed into wifi/google account(s). Remember to Flash Rom -> Flash TWRP -> Reboot Recovery -> Flash Gapps -> Reboot System
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shinoks:
What's the right way to install permanently TWRP 3.3.1? i guess i don't need "installer version zip" anymore?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] alifmohammadmagdy:
Can't boot after flashing gapps

How do I fix this?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
August security patches have been merged.

The	'lineage-16.0-20190811-nightly' build or newer will have it.

https://review.lineageos.org/q/topic:P_asb_2019-08

https://review.lineageos.org/c/LineageOS/android_device_google_marlin/+/253485

https://review.lineageos.org/c/LineageOS/android_device_google_marlin/+/253486

https://github.com/TheMuppets/propr...mmit/578f1f89aaae011b09251d26a13781f4dc96ca3a
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
I don't think you can.

---------- Post added at 09:43 PM ---------- Previous post was at 09:42 PM ----------

Clean install?

Very carefully follow the instructions. Starting with stock.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drmarble:
I am unable to get my self built lineageos rom to boot. I use TheMuppets for vendor. Everything else is straight linage 16.0 except for adb enabled by default and I hate safety net. I ran flash-all.sh from the Aug update (leaving in the -w erase flag). I then flashed the latest nightly (aug 11) to both slots. I boot twrp (3.3.1-0 or 3.2.3-1) and advanced wipe both system and data. I then flash the rom either from sdcard or sideload. It boots up with the boot animation and hangs with the following logcat messages:

08-13 17:27:48.204 620 1031 W ServiceManagement: Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default. Waiting another...
08-13 17:27:48.576 1444 1444 E android.hardware.contexthub@1.0-service: Could not get passthrough implementation for android.hardware.contexthub@1.0::IContexthub/default.
08-13 17:27:48.579 1445 1445 D vndksupport: Loading /vendor/lib64/hw/android.hardware.sensors@1.0-impl.so from current namespace instead of sphal namespace.
08-13 17:27:48.584 1445 1445 E /vendor/bin/hw/android.hardware.sensors@1.0-service: Couldn't load sensors module (Unknown error -2147483648)
08-13 17:27:48.584 1445 1445 E android.hardware.sensors@1.0-service: Could not get passthrough implementation for android.hardware.sensors@1.0::ISensors/default.

The ServiceManagement error occurs most often. More than once per second.

I have no idea what causes this. Dr. Google told me to delete /data/adb from a magisk install. That is long gone. I have even tried formatting data (typed yes). Same error. Something doesn't match up. I have flashed my rom to both slots or just one. I have been at this for several weeks and no luck. Luckily, this isn't being used as a primary phone since the microphone died. I may just give up and install the Q beta and play with that.

Any advice would be appreciated. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SalsifiPourri:
Will you keep maintening lineage os when lineage 17 will come ? It would be si cool, you've been doing great things since toi maintain lineage os :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bsd1101:
Just found these issues on my sailfish

under about phone/android version: lineageos/build date version still says 16.0-20190731 on version 20190812 and 20190815. security patch level says july 5, 2019.

on 2019082015 Style Accent colors are broken. It's locked into blueberry, and cannot be changed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
probably

none of those issues here. you installed something to cause that. guessing magisk or some magisk module or a theme.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bsd1101:
So apparently I was/started doing something wrong with the boot slot. From what I recall I would always flash the rom, then reboot back into the recovery and install gapps/magisk. Whenever I did this slot A was always selected. The one time I tried starting the phone in slot B it didn't work; this was when I first received the device. Now after flashing lineage it would always leave slot B selected; which I don't remember ever happening. I had to flash gapps/magisk on that slot, then booted into B. The version and build number are now correct, and themes are working. Has something changed? Am I doing something wrong?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aL_09:
What did I do wrong? Please tell me!

1. Wipe data and system

2. Flash ROM and TWRP

3. Tap reboot and then recovery

4. Flash Gapps and su-addon

5. Reboot system

Now my phone reboot to twrp instead of rebooting to system. Whyy??!!

*Edit: By not flashing the twrp zip file, my phone reboot normally but how do I flash gapps and su-addon?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] :
Did you swipe to install the twrp app before rebooting? ? Make sure you don't do that
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aL_09:
Thx for helping!! I did swipe I'm gonna retry rn!

Edit: It works :)) Thx very much!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drmarble:
I figured out my problem: PEBKAC.

I studied logcats and dmesgs and decided that contexthub wasn't starting. I finally noticed that I had a remove-project line in my roomservice.xml for google/device/contexthub. I removed it when I had a much smaller ssd and saw it was only used for a couple of google devices. I removed that line, synced, saw the contexthub directory. Build, flashed and it is running. I feel rather stupid now. Thanks for your help, razorloves.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aL_09:
Edit: Fixed
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] moonlightdrive:
Is somebody facing issues using auto updater? I cant pass 20% on finalizing update..., Tried via recovery (los and twrp) and google services get lots of fcs when system boots, basically i can not update conserving my data.

Thanks!

Mods: only magisk

Device: pixel sailfish

EDIT: SOLVED by activating ' Prioritise update process ' into embedded los updater.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sindalf:
Hello folks, Can we flash this rom over an android 10 beta 6 ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
I wouldn't.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
Hi Friends, I'm new to pixel and want to change to LOS. Do I have a similar camera quality if using (patched) gcam or Footej pro?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NepoRood:
You don't have to use a patched anything, Google Camera works just like on stock :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ESmazter:
Same problem here. What a bad process. I tried to use TWRP as well, which is a common process and they same with the FC happens. Now no chosen update boots at all.

Sunday midnight. nice.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aL_09:
I change my animation boot, now I have to reboot twice to reboot to rc bc the first one reboot the system...Why?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayloofah:
Anyone have word of LineageOS 17?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] All-In-One:
Android 10 has barely been out for 2 days, so I think we won't be getting any word about LOS 17 in a while.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
I am no expert, but I kept notes, and this is what I did:

--------------------------

General rules I have read:

FOR TWRP, you will need BOTH its img file and its zip file.

Always install ROM's zip file when TWRP shows it is in SLOT-A

TWRP zip file can be installed in either SLOT-A or SLOT-B

Always install everything else's zip files when TWRP shows it is in SLOT-B

Changing TWRP's SLOT doesn't take effect until you reboot TWRP

--------------------------

--------------------------

Sources:

1. For factory image: https://developers.google.com/android/images

2. For TWRP IMG and ZIP files: https://eu.dl.twrp.me/marlin/

3. For LineageOS: https://download.lineageos.org/marlin

4. For SU (ARM64): https://download.lineageos.org/extras

5. For gapps: https://opengapps.org/

--------------------------

1. restore factory image, ALLOW IT TO BOOT, don't bother to set it up, power off.

2. boot to bootloader (Power + volume Down)

3. flashboot flash boot twrp-recovery.img

4. flashboot boot twrp-recovery.img

5. Should be in SLOT-A (TWRP SLOT change is in TWRP Reboot menu), if not, switch to SLOT-A, reboot to bootloader, flashboot boot twrp-recovery.img

6. Advanced, Sideload: adb sideload twrp-installer.zip

7. Advanced, Sideload: adb sideload lineage.zip (darn lineage changes to its Recovery)

8. Advanced, Sideload: adb sideload twrp-installer.zip

9. Boot into SYSTEM, ALLOW IT TO BOOT, don't bother to set it up, power off.

10. boot to bootloader, select RECOVERY, boot into TWRP

11. Should be in SLOT-B, if not, set to SLOT-B, reboot to bootloader, select RECOVERY, boot into TWRP

12. Advanced, Sideload: adb sideload addsu.zip

13. Advanced, Sideload: adb sideload gapps.zip

14. For now on, always use SLOT-B for all TWRP uses (except use SLOT-A for flashing ROMs).

--------------------------

--------------------------

How to update LineageOS without going through all this?

I don't know!

LineageOS's update hangs.

Doing the update manually royally messed things up - had to go back to factory image and do it all over again.

LineageOS's update appears to be BROKEN.

TWRP SLOT-B backup seems to work.

I am only backing up Boot, System, and Data.

TWRP recovery????

I don't know, as I have not tried doing a recovery.

Previous phone was Samsung S4 MDK. No slots to worry about. Did have to worry about LOKI and ODIN.

So far, I don't like the Pixel XL

1. All the SLOT business is very complicated

2. LineageOS updater doesn't work

3. When I connect booted phone to PC, I can not use Windows Explorer to look at the phone's SDcard files.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reverse-anastomosis:
Read the lineage wiki! You only boot twrp to flash lineage the first time. Then you use lineage recovery which is included in the lineage zip. Stop trying to flash TWRP. This whole slot business is the reason why lineage recovery exists, so use it.

Edit [MENTION=614507]razorloves[/MENTION] could you add something to the op about this. People are banging their heads against a brick wall for no reason. Everything works fine if people would follow the lineage wiki, and understand TWRP is not a permanent option with Marlin/sailfish. Or at least if you want to update easily.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Duane500:
Hmm... ROM is working great, however I'm having a problem receiving texts when the screen goes off. As soon as I pick it up and it lights up, my texts come in. Any suggestions?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
When lineage's recovery can do backup and restore - then it will be worthy of using.

Currently, it is rather useless.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
I suspect it is battery optimization.

There is a way to turn off battery optimization on a per-app basis.

So, try turning off battery optimization for any apps that handle text messages.

However, LineageOS 16 makes it super difficult to find battery optimization app list in the settings.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reverse-anastomosis:
I agree that its not great, however if you want updates...then use it. Otherwise stop complaining. Its what we have for now, and it works. You have 1 rolling backup with the previous slot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Duane500:
Thanks! I will look into it again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
I screwed up the system again - by trying to install the update manually with TWRP.

I must have tried at least 5 times to get LineageOS 16.0 with su and gapps installed WITHOUT flashing TWRP - and I couldn't.

The way I see it is:

There is no way for a newbie to install LineageOS, su, and gapps using the Wiki nor the other instructions on lineage download page. The reason is - probably nobody has done it in a long time.

The developer and friends never test it - doing a factory image install and then lineageos,su,gapps - because the Lineage OS recovery can't do backups and restores - and nobody wants to spend hours setting everything up after a "fresh install test".

So, I flashed TWRP, as it's the only way to get su and gapps installed.

Without flashing TWRP, TWRP just can't install su and gapps regardless of Slot used.

It will take hours to get everything setup the way I like it - again.

I will never be able to do a Lineage update.

Unless maybe you have the Lineage OS recovery in a zip file that I can install over TWRP?

Howard
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
a/b devices, like pixels, install updates while booted into android. no recovery is used.

so if you're updating, then you just use the lineage updater in settings. there's no recovery used in that process. and it doesn't matter which recovery is currently installed.

but if you want to manually update using a recovery (old school), then you just fastboot boot twrp and follow steps in first post.

don't even bother with lineage recovery if you don't want to. there's no reason you have to use it. twrp works fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
Are GApps and root preserved using the built-in updater?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
Yep
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
That sounds great. I will keep TWRP as my recovery so I can do backups of Boot, System, and DATA.

The updater says I have Sep 2 2019 version installed (the file was Sep 3rd). I am updating to Sep 7th file. It is taking a long time - the notification says it is always at 7%.

How long does an update take?

I also noticed that when I downloaded from https://eu.dl.twrp.me/marlin/ the latest TWRP ZIP and IMG files, that they are slightly different versions. The latest ZIP file is older than the latest IMG file. twrp-3.3.1-0-marlin.img and twrp-pixel-installer-marlin-3.3.0-0.zip files. So it is possible that the latest TWRP IMG file has a problem installing the SU and GAPPS.

The updater says it is Updating Final Installation, and progress bar does not move.

It has been 20 minutes and the notification still shows 7%.

How long is the lineage 16.0 updater supposed to take?

Howard
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
As the latest zip flashable installer of TWRP (3.2.3) is not able to decrypt data, you should use the 3.3.1 img file for this. Booting directly with fastboot seems to be the most useful solution. So the LOS recovery can remain as it's not needed.

Regarding the update process, I remember there ware the hint with process priority or similar some postings above...maybe it's related.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reverse-anastomosis:
I have installed lineage on 2 brand new devices in the last few months. Except for the newest TWRP not working the wiki 100% correct and works perfectly. I personally have not tried using TWRP as a permanent recovery, as it isn't documented anywhere, and it seems that people have a lot of problems using TWRP. This device has been very stable and headache free for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
OK,

Update finished after 1 1/2 hours.

Then I rebooted.

I just did not expect it to take so long, but it is OK.

I have noticed that for other nexus devices, LineageOS download page has a download for the ROM and another download for the Recovery. But not for the Pixel XL. Not a big deal, as I like TWRP's backup/recovery functions.

Howard
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
AFAIK the Pixel is the first (Google) device using the AvB technique. The nexus devices seems to be straight forward.

I had a pixel some days (was defect) and the update in background of the Stock firmware also takes quite long...

To use backup/recovery you can still use twrp by booting the img file using fastboot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
https://xdaforums.com/showpost.php?p=79116759&postcount=930

https://source.android.com/devices/...e-while-the-system-is-running,-isnt-that-slow
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
If you noticed in the changelog there are a couple new marlin/sailfish specific changes. I've added a usb security feature.

It blocks new usb gadgets when the device is locked.

If you like, you can enable it in settings->security->trust.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
Is there an option to prevent a LineageOS Update from installing the useless worthless recovery?

It can't do backup or restore.

It can't even let me install zip files.

All it seems capable of doing is a factory reset.

Why is LineageOS forcing their recovery upon us after every update?

I seem to remember from years ago in the CyanogenMod days on an older device that there was a Developer option to prevent updates from touching the Recovery, but I can not find such an option.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
As the A/B devices like Pixel don't have a separate recovery partition, TWRP must be installed by patching both boot slots after each update in case you want to have it permanently installed. If you need to do nandroid backups or installing other zips you can boot the TWRP temporary by using fastboot boot twrp.img and after this doing all you want. The updater cannot exclude recovery for this reason.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] B2Pi:
Am I wrong in thinking that TWRP is still unable to decode the encrypted data partitions, also?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] adm1jtg:
If you use it through fastboot it's fine..... I only have those issues if I try and install it permanently
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
Using the 3.3.1 temporary with fastboot it can decrypt.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
Hi,

I came across a writeup regarding dm_verify, and the fastboot commands:

fastboot oem disable_dm_verity

fastboot oem enable_dm_verity

Is this something we should or should not do, with LineageOS ?

Regards,

Howard
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ESmazter:
Hello,

I have updated to the latest nightly using the updater. Now, whenever I call someone they hear a loud beep every 15 seconds but I do not hear it. This is a really strange problem and I tried a full factory reset already.

Does anyone else have this issue?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
I don't have a SIM card and service yet for this new-used Pixel XL, so I can't make phone calls to see if I get the beep you describe.

The following is not likely your problem, but perhaps it is...

https://www.youtube.com/watch?v=nTRlhElkcPs

Notification sounds caused by a nearby NFC capable credit card.

Anyway, in general I am pleased with TWRP and LineageOS 16.0

It is inconvenient to need to reflash TWRP after updates.

And, I can't figure out why my Windows 8.1 PC can't see the phone's internal storage.

But, it general it is nice.

I am slowly reading through the 281 pages of the TWRP thread - maybe by the end I will better understand the slot system. Then I plan to read this long LineageOS thread.

I plan to get service in a month or two. I hope I don't get the beep every 15 seconds that you described.

Edited for a few other thoughts:

Maybe you have phone call recording software, and it beeps to let the other party know it is being recorded?

The 15 second beep for phone recording is described here:

https://www.phone.com/phone-support/call-recording-beep/
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aL_09:
Is this how to update system?

1. Backup data in twrp

2. Wipe data and system

3. Redid the installation guide

4. Restore the backup
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] supachris:
Why not use the built-in updater?