yashsingh1/xdaforums huggingface dataset:
[Moto E4 Plus Themes, Apps, and Mods] Uttiya:
Okay, I'm kinda weirded out and very happy at the same time.

Just when I thought this Moto E4 Plus is a good for nothing phone with old security patches and maximum OS upto 7.1.2, I see some magic happening.

Dark mode rolls out, officially by Google on many apps, which according to the news is meant for Android 10 but I'm getting it as well?

For starters I have a dark Play Store (version 17.0.12), which according the news is rolling out for a few phones with Android 10. I have a dark Instagram (version 116.0.0.8.121) which is also meant for iOS 13 and Android 10 phones. Other dark mode stuff includes a dark Chrome enabled using the chrome://flags trick (which when I did it to other higher end phones didn't work) and other dark Google apps like keep, calendar etc.

The even more surprising part is that this is my ONLY phone which isn't rooted and is completely official and stock.

My friends with stock Android 9 are killing me why they are not receiving dark mode especially on Instagram and I have gotten beaten up for it a lot :D. Because the Instagram dark mode can't be toggled in the app and requires a system wide settings variable to control it. Well my entire **** is white af except Instagram lol but of course I'm a beta tester for the app but who isn't? I have no idea at this point what is happening and so I'm asking you all here for an explanation. Save me from further bullying xD.
[Samsung Galaxy S10 Questions & Answers] cggamer1:
Please excuse any mistakes I make as this was my first time flashing firmware. So anyway, I have a Verizon S10. I got tired of Verizon’s bloat and all the missing stock features so I flashed the Unlocked Firmware from Sammobile. As I had no prior experience, I did research and came to download the latest U1 firmware with the XAA CSC. I know there’s a U1 version with the Verizon CSC, but I decided to use the XAA version because I knew it was universal. Now I could be totally wrong on this, but isn’t at least one of the three CSCs supposed to be XAA? All mine are still VZW, just like it was on the original carrier fw. I even tried taking the Sim out and reflashing, but no luck. The phone is still locked to Verizon, could that be why? The problem is, can I still get OTA updates? How can I stay on unlocked firmware and get them? Did I mess up and should’ve flashed the VZW U1 fw? Is this fw all vzw cscs too and I just messed up somewhere else? I have the pda of the xaa version with the csc of the vzw version. I don’t know what to do. I would’ve loved to install the one ui beta now that I’m in unlocked fw, but I can’t because my active csc is version, who blocked it
[Samsung Galaxy S10 Questions & Answers] StoneyJSG:
Some answers to your questions:

1. I don't know, it should flash a data partition that's for the unlocked firmware. I remember reading that somewhere here in the forums.

2. I think Verizon phones are more locked than the others, but I could be wrong.

3. You can get the OTA updates on the unlocked firmware, you just have to have a SIM inserted.

4. You may have, do a factory reset in recovery and try flashing this with that special version of ODIN:

https://www.androidfilehost.com/?fid=1899786940962609128

5. U and U1 firmware are different, sort of. U is carrier and U1 is unlocked.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
​

LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the changelog for a full list of changes & features.

What's working

RIL (Calls, SMS, Data)

Bluetooth

Wi-Fi

Camera

Video Recording

Video Playback

Audio ( Record and Playback )

Sensors

Flash

Led

What's not working

Active Edge (support will not be added. Explanation here)

Feel free to report any other issues you may encounter with relevant logs

Installation

Download the latest supported Lineage OS build, TWRP image and optionally gapps and the TWRP installer zip.

Reboot to bootloader

Wipe userdata (fastboot format userdata)

Fastboot into TWRP recovery (fastboot boot twrp.img)

Flash the latest build of Lineage OS

Reboot to bootloader and fastboot TWRP again

(Optional) Flash gapps of choice (OpenGapps micro or smaller are recommended)

Reboot to system and don't install the TWRP app

(Optional) Flash custom kernel / TWRP / Magisk

A more detailed installation guide can be found here.

Updates

Simply update from the Lineage Updater in Settings and reboot or repeat steps 4 - 10. You shouldn't need to flash factory images as all partitions (firmware, vendor etc.) are updated with the lineage zip. Gapps MUST be reflashed if taking an update via Lineage recovery or TWRP. Lineage updater will automatically restore gapps up to nano in size.

Downloads

Latest Lineage OS 17.1 (taimen)

Latest Lineage OS 17.1 (walleye)

OpenGapps (Micro or smaller is required)

Unofficial OpenGapps (old but confirmed working package)

Google Fi Gapps

TWRP (taimen) / (walleye)

Magisk

Credits

razorloves

javelinanddart

RaymanFX

Sultanxda

LineageOS Team

Source

android_device_google_wahoo

android_device_google_taimen

android_device_google_muskie

android_kernel_google_wahoo

proprietary_vendor_google

Feel free to join my Pixel 2 telegram group here.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MrBrady:
Thanks for keeping our Pixel 2 XLs alive!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ismael47:
Thank you for keeping our pixel alive when the next update to fix all these errors greeting I would like to make a donation for this project.

---------- Post added at 07:09 PM ---------- Previous post was at 06:55 PM ----------

Thank you for keeping our pixel alive when the next update to fix all these errors greeting I would like to make a donation for this project.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] zook:
I'll definitely be watching this project. While I wont install it for now due to the few bugs it does have, I'm sure all of you have done a great job so far.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TechNash:
Thank you for all the ports you make!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] almahix:
Can't wait to try 17! Thank you very much for supporting our phones.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shaunnicho:
Will be watching development keenly and will jump in once it's more stable. Cheers for doing this bud. ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bailx:
i tried the permissive version, couldn't ever get it to boot up.... wonder if it's the version of TWRP i was using (3.3.0.0) i might have to try an older version... i did see some permission errors during the install... (should have taken a picture) i'm prob. headed back to your lineage 16 build for now... thanks for this though... really looking forward to it. thanks

just a side note about TWRP - really wish they would disable the screen timeout option by default.....

i'm flashing lineage 16.... screen goes black.... can't get it back on at all.... had to force reboot and start over....

that's happened on a LOT of other phones too (i've been using cyanogenmod a LONG time).... aggrivating default feature (just a suggestion to maybe put in any future instructions to go into TWRP settings and disable that crap) / rant over lol sorry
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
That and the TWRP app installer. That'll mess things up in a hurry if you swipe it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bverns88:
This Rom is legit.

Running wahoo kernel

Magisk mod FDE.AI

Thank you devs.

Can't wait for update.

[emoji846]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
Small question regarding the GPS, on LOS 16.0 i have to set enforcing to off to get continual tracking to work, will this be addressed in this ROM?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bailx:
goddammit twrp and the friggin screen timeout.... you have to start all over .... dumbest ****in option ever.... please start adding a reminder in your guides to DISABLE SCREEN TIMEOUT - because it destroys lives.... uuuuughhh
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
I've done that a number of times, and I never seem to learn...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Triscuit:
Lol same here, it's a pain in the butt, but I don't seem to learn from my mistakes lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] primed1:
Can you post builds without GApps please? Literally the only reason I use Lineage OS is because I can choose to have a Google-free experience, and your ROM doesn't give me that option. Kinda goes against Lineage's philosophy, no? People can flash GApps packages if they like, but it's impossible to remove GApps from a package. Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] crixley:
Have you ever tried flashing gapps on an a/b partition phone?

I think having both posted would make more sense, though that's a lot of work for maybe one or two outliers.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] primed1:
Have you ever tried to remove GApps from a ROM that contains them?

I disagree with you on the front that having a separate build without GApps is more work because when Lineage is built from source, it's built without GApps. Technically, adding GApps to the finished ROM manually is more work; not to mention that adding GApps to the ROM makes updates much larger to download and install.

I get that including Google apps makes it one step easier for a lot of users, but it also takes away choice for a lot of security-centric users, and those that may not want all of the Google apps pre-installed on this ROM.

And isn't the whole point of Android and LineageOS choice?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] crixley:
So build your own without? Again you're a drop in a bucket of water.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] primed1:
Apologies if I came off as combative, I was just making a suggestion to the developer of this ROM that I think more than a "drop in a bucket of water" of people would also appreciate. Thank you for your suggestions though, and have a nice day! :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am still on this ROM, this is the ONLY 10 ROM for my pixel 2 XL, that doesnt suck battery life. In fact, the battery life is pretty decent for this ROM and 10! LOS (this ROM) is pretty decent, I am using it for my DD the past 3 days and so far, not a single issue! AWESOME work Eamo5 and thank you!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Yes. It's the best stock alternative with bare bones. Minus the Active Edge and AOD.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
What issues are you facing with AOD? Behaviour is pretty much identical to stock AFAIK
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
AOD works here, there's no issues on my side, whats the issue you face? And I agree, it's a nice plain OS, I have always preferred LOS/CyanogenMod over Google OS even though they're derived from the same open source code. LOS just seems to do it better in my opinion! I'm glad there's no active edge, I hate that stupid feature and disable it when available (different ROM). It's like the stupid notch on my Pixel 3XL, what a waste of space (I have both 2XL and 3XL). The 3XL doesn't get used because it's Verizon junk so just waiting to be sold.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tippete_3:
Thanks for the great work, I plan on switching to this custom ROM once the official support ends

Just want to ask, why the active edges support won't be added? Dirty unicorns managed to have it working, sadly I can't link because I'm a new user but it's on their github
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Because it uses proprietary code that is not open source from Google which leads to several licensing issues. We'd rather avoid legal action towards the Lineage team from pissing off Google again. For this reason, support for active edge will never make it into Lineage OS unless its open sourced by Google.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
NIce info there. So someone is surely having unofficial persona builds with active edge on lineage :D .

And yes AOD works fine. I had it confused with some other ROM, sorry for that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
--deleted--

I don't know why the Quick Reply in XDA posts double in browser (Edge chromium)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I for 1, am glad, I hate that stupid edge and disable it across the board. And I'm happy to say that I'm on LOS (this rom) for over a week now and used as my daily driver and it's awesome! No major bugs, nothing but pure Android, and I am loving it! This is the ONLY 10 rom I run on my pixel 2XL, otherwise it's pie but I do plan to stay with 10 and LOS. Thanks again EAMO5!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (05/05/20)

May ASB

Switched to source generated dtbo

Various bug fixes
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Dirty flashed from "lineage-17.1-20200427" (found under older builds / taimen folder in AHF) to the latest build, no issues, smooth sailing and running great! Thanks for the updates and LOS!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
And there was no need to flash the vendor separately of Google right? Since Eamon's builds are the only ones where he has his own custom built vendor. My wordings might be slightly misplaced related to teh "vendor" but you get teh picture what am looking to confirm from you. I tried Bliss - while its blissful but its overloaded for me and phone is running alwys warm which i never had in my Lineage or ABC. So thinking to fall back here and continue this as daily driver. Just getting tired of flashing the vendors and roms over n over again.

I need a work profile for company in my phone and that works good here, others its not that stable.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Update from today is working fine for me! Appreciate the attention to our old phones.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Emilius:
Is it possible to add signature spoofing?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Yes, use smali patcher. It's linked in the changelog in the second post
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Emilius:
Oh wow, creating your own Magisk module for that... Nice, it worked perfectly.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Not that I am aware, but I also have never flashed a single vendor image in my life, instead, I use the old Google firmware and open the ROM zip, lineage-17.1-20200505-OFFICIAL-taimen.zip\META-INF\com\android\metadate and open it in notepad or whatever you use to read TXTs. In there, find this line: post-build=google/taimen/taimen:10/

QQ2A.200501.001.B3

/6396602:user/release-keys. That is the required firmware, vendor, ETC., I always copy the entire contens of my internal SD (after backing up my TXT/MMS to XML so its also copied) to my PC, use the Google firmware with the -w so its wiped, and my partitions are restored to what Android needs them to be, then I follow the dev steps and install. This means, I never have any type of mismatch nor ever have to flash anything outside of the initial firmware, then ROM. After I setup my device, I simply copy the contents back to my internal SD, overwriting the destination, then restore my messages (from XML) to Android and go on about my day. I know its a longer process than most are willing to use, but I never have any type of issues, bugs, nada, my device is always freshly cleaned, installed, and configured without losing a single byte of data or TXT/MMS!

This is my process across the board.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Might get torched for this.

I know it's not recommended but this time instead of updating with the May factory images I flashed May LOS instead. I think they bundled radio and vendor in the ROM. Is this correct?

Everything seems good, even flashed another May ROM with success
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
There were no firmware differences from April to May ASB. Yes, I do bundle all firmware with this ROM so flashing factory images is unnecessary. This should prevent there ever being a firmware mismatch on any of my Lineage OS builds. If you switch from Lineage to a ROM without a custom built vendor, I'd advise you flash the stock vendor first.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tcables:
We can dirty flash this latest build correct? Just download the zip to storage and flash via twrp immediately?

Or is encryption a problem still? (I didn't enable it purposely, is it also on or off by default?)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Every build I release should be fine to dirty flash unless I explicitly state otherwise. I would recommend adb sideloading the zip instead of downloading the zip as userdata can't be decrypted in TWRP or Lineage recovery yet. Encryption is enabled by default as per the Lineage OS charter.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] a_khusairi:
I backup Lineage OS's default kernel for Taimen, using the Ex kernel manager, in img. Can I return to stock kernel by flashing this backup on twrp with flash boot.img?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am loving this ROM! This is so smooth and stable, I have ZERO issues, nor bugs!

Just a head's up, I dirty and clean flash in TWRP without an issue (but I dont bother to install TWRP, I ADB TWRP when its needed), nor do I sideload any updates. Encrypted /data does not interfere with the update or flashing from my experience. I have no issues updating or installing clean using TWRP ADB mounted.

The other piece I love about your builds, is its USERDEBUG, because of this, it allows me to remount /system in read/write, USER cannot (which is most Android 10 ROMs) and most users are not aware of the differences between USERDEBUG/USER, but for me, its a huge PLUS! I will stay on this LOS for probably the rest of my device's use. I will test other ROMs, but this is my DD for the battery life, stability, and USERDEBUG. I need direct access to the build.prop, the magisk modules "MagiskHide Props Config" do not do what I need. I need direct access to /system in read/write (which this ROM offers)! I LOVE LOS!

Anyone curious what I mean, read here:

https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md

https://source.android.com/setup/develop/new-device#build-variants

https://source.android.com/setup/build/building#choose-a-target

Buildtype	Use

user	Limited access; suited for production

userdebug	Like user but with root access and debug capability; preferred for debugging

eng	Development configuration with additional debugging tools
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
The reason you can mount /system as rw is actually due to this commit. In theory, I think you should be able to do the same on my AOSiP builds despite the fact we ship user builds there. I'm very glad to hear you've been having a positive experience. Me and a few other Lineage team members are working hard on getting the ROM to official status which hopefully isn't very far away :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I thought (but I could be wrong) it was due to the way USER build system images are formatted as EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS for de-duplication of the blocks (not a flag as in the github link). I thought because it is a USERDEBUG build, it was formatted differently and not de-duped (allowing the partition to be remounted as write)? That was my understanding because the USERDEBUG is more for development use, it was formatted to allow mounting RW of the /system? Whatever the reason is, IDC, as it works flawlessly for me, and allows me to mount all partitions, so I am happy as can be with this build! I tell EVERYONE to use your LOS, anyone who asks about a 10 AOSP ROM, I point to your LOS version!

Your post takes me to where I originally found the issue/bug:

https://twitter.com/topjohnwu/status/1170404631865778177

https://github.com/Eamo5/android_de...mmit/2a60f2f5b9cfd846d30e108af34114006c3a01e3
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] afn78:
thank you so much for your time and effort, can't thank you enough. I'm a Pixel 2 user (walleye) and you're the only one providing this OS, you're our only hope ;_;

BTW google drive link isn't working for sometime now, can't download the latest build and telling me: "Sorry, you can't view or download this file at this time." :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Jere1000:
Dumb Question, sorry

Hi, just want to know because you didn't mention it.

Should I unlock the bootloader first?

First time and I feel little worry to brick it #noob

Thx!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Hi, that's unusual. Try navigating to the older builds link where it will take you to the google drive folder where builds are hosted. Hopefully this will resolve your issue. The direct link seems to work fine for me. Also you might need to sign into a google account as I've seen that cause issues before for some inexplicable reason.

Yes, your bootloader needs to be unlocked to install any custom binaries.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (11/05/20)

Google splash screen is now always black, irrespective of light or dark theme

Various bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
The Google link fails from a mobile browser other than chrome but works fine from PC using any browser. Try it from PC not phone, that error is a known Google issue and not just for this rom. It happens to me on any drive link from mobile browser (jot Chrome). I hate chrome these days so I dont use it so I see this all the time. I just opened it in PC, and NP:

View attachment 5016315
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] afn78:
I was on PC but I don't use google so I wasn't logged in, tried to use different VPN servers with different browsers didn't work, when I logged in with a gmail account it let me download. thank you.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
That's what i meant by non chrome browser, it's trying to log you in but can't. It happens across the board with non chrome browsers. This is to let everyone know when you see that error, it's related to browser. I have never gotten it with PC so I'm surprised you did but I also do not know your PC or browser type are, whatever the combo, Google didn't like it and error'd. All I'm saying is that error is not related to any single ROM or upload, but failing to login to Google and happens all the time.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] user602:
Thank you for keeping Walleye development alive. I have been running your builds since March with no problems. :good:

I have found only one minor issue: When creating or editing a Style In Settings > Display > Styles & Wallpapers, the option, "Choose primary color" is empty (no color choices appear) unless the device is set to dark theme (it took me a while to figure that out). Perhaps the option could be renamed, "Primary Color for Dark Theme" so it'll be less confusing. :D