yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
[MENTION=614507]razorloves[/MENTION], I have only noticed one glitch/bug so far and that is with WiFi calling on Verizon. Normally my phone always displays "Verizon Wireless WiFi Calling" or "Verizon WiFi Calling" on the lock screen and when you pull down the tray from the top of the screen, as I have it set to WiFi Preferred as I always have and I am almost always connected to wireless somewhere.. That is my indicator to know that all is working correctly. When I am not connected to any wireless it is always says "Verizon Wireless". Now with yesterdays build, with wireless off it says just "Verizon", and even when I connect to my wireless it just remains at "Verizon", it no longer changes the title to indicate that it is now using WiFi calling. I have checked to make sure that under the call settings it still shows "Wi-Fi Preferred" under the WiFi Calling area. So I don't know now if it is really using WiFi calling anymore, or is it just a visual bug.

Thanks,

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dd805bb:
I am on stock ROM and have the time mobile wifi calling come and go. Whether on wifi preferred or mobile preferred wifi calling. In Dev options it has an option to keep mobile active. Untick that and it will force wifi calling. If not it will stay on mobile until it loses that last cell tower. That I noticed in Jan or December on stock ROM.

---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------

Not "the time". I meant to say that TMobile.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
I appreciate the response :) , but this is definitely something that has changed with the new build. I have been on his builds from the beginning and I am very conscious of how this particular feature works. Razor and I have been working on this very thing (persistent WiFi calling) since the beginning.

Thanks,

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] epapsiou:
Marlin. Dirty flash. TMobile

All good.

And love that battery icon is back

Great stuff razorloves
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] NepoRood:
MOD Edit, Thread Cleaned

Keep it civil guys
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
Thanks! [MENTION=7237874]NepoRood[/MENTION]

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Droid_JD:
I'm seeing the same thing with WiFi calling. I'm on mint mobile and on the notification bar it typically would say, "t mobile WiFi calling". Using the new build, it just says "mint".

Update:

Nevermind.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chapayXDA:
Fingerprint raw data

Hey

Perhaps you can help me.

I want to make a mobile fingerprint reader.

For this, I need to get the raw data from the scanner.

Is it possible?

May be you can give me some advices or helpful links?

Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sh7adeh:
Hope there is more option for ststusbar and clock like make clock with date and option to move network speed .. Im using latest version and the performance impressive
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] some_shyguy:
Is dark mode supposed trigger the dark theme on Pixel Launcher and the Feed? I'm not seeing the way to cause the change otherwise.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DarthDestroyeis:
Aroma gapps still seem to be broke. As soon as it tried to install it crashed and froze on TWRP logo
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wilo108:
Yeah, same here -- I just used the super package with my own custom gapps-config.txt file. Worked great.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EMT803:
Wanted to say thanks to everyone that replied. I downloaded the Viper zip that was attached to this post and transferred it via adb to my device. I just installed the radio update, the February update, ref-flashed Magisk after rebooting to system and then went through the Manager to apply the Magisk update. So far so good. I went to install the Viper module through the manager (I deleted the previous install that didn't work) and it occured to me that I may want to clarify a few things before I go flashing zips haphazardly. So....

1) SInce I just applied updates I am going to take a new Nandroid backup, backing up the partitions that TWRP has checked by default.

2) Rebooting to system

3) When I install the Viper4Android module through the downloads subsection of the manager, is there a conscensus on which one is best for sailfish? (The FX, XHiFi, or FX version v2.3.4.0) If I had to guess, I would install the FX module and then upgrade it to the later version or go strait to the newer one?

4) How should I install the attached zip? Flash it through TWRP?

Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] LeMoise:
3) I honestly wish I knew dude. I've been trying to figure out the difference between FX and XHiFi since I started using V4A and I still don't know. I just install FX.

4) In regards to the ZIP I previously attached, you'll want to unzip it to start. Go into V4A and in the settings it will show you where its storage is located. Somewhere on your phone is a folder called Viper4Android with a sub folder called Profile (for me its in Internal Memory > Viper4Android > Profile) and inside that is where all the different configs/profiles go, put all the profiles in there or overwrite that Profile folder with the one in the ZIP. Once you've done that, when you open Viper you should be able to click Load Profile and have them all appear.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EMT803:
Thank you very much. I transfered the zip to my sdcard via ADB. Can I extract the contents within the phone with the file manager feature in TWRP while it is on the sdcard, or should I move it elsewhere (on the phone or transferred back to my PC) and extract?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] LeMoise:
I am not sure. Usually I set up my phone to allow USB file transfers, unzip it on my PC and move it over manually. I've never unzipped a file with twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EMT803:
Good deal. I will just transfer it back to the PC, unzip, and then transfer them back over via USB. When I transfer them back over I will place them in the V4A profiles folder .

EDIT: SUCCESS!!!!

Thanks to everyone for taking the time to dumb this stuff down for me. Haven't tried using V4A with my headphones yet, but the little bluetooth speaker I use sounds great. So many options. I had to intall Titanium backup and donate for the pro-key (which I have NO problem doing when it's a quality app that noticeably enhances my device), but I am satisfied. Now just have to figure out how to use it. At first glance, TB appears so complicated to me that I have avoided it in the past.. If any one has short answers or links for the following I will be more than happy to start skowering, but:

1) Everytime I install LOS I see the disclaimer warning against using TB to restore/backup apps. Should I not even worry about researching that process? I plan on using LOS indefinetly?

2) What is the advantage of backing apps up individually with TB when we take a Nandroid periodically?

Again, you guys are the best. Thank you!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garaxiel:
Hi all. been reading though this thread a bunch seeing all the issues and problems, trying what some people are saying, and having no such luck, i'm following what the first post says to do, and still no luck, i'm going to outline what im doing step by step because maybe i'm just misinterpreting something in the first post wrong, so please bear with me

First i downloaded everything from the 3 links for Marlin (as im on a pixel XL ) in first post

Downloaded the latest Pixel XL image from google, and using flash-all.bat got back to stock. Loaded it up, skipping everything, got to developer options, turned on USB Debugging, and then adb reload recovery.

From here i follow the instructions and commands to flash the radio and bootloader on the device, both appear to work great

Then i do the fastboot boot twrp.img command and get into TWRP

here i click wipe, then advance, data and system, and hit wipe

go back to main screen and go into advanced - adb sideload and use the adb sideload command to flash on the lineage OS 16 zip

then i hit back, go back into ADB Sideload, and using the command again flash the twrp zip file onto the device

reboot recovery as it says, when it gets back to the twrp menu again go into advanced - adb sideload and flash in the mindthegapps file form the downloads.

At this point i hit reboot, and go directly into a bootloop

Im just not sure what i am missing here. is my phone maybe rebooting into the wrong partition? am i missing a step in getting the files to the pone somewhere that is not explained? am i missing a command for the sideload option?

I have redownloaded and retried this step by step at least 10 times now, every time i fail i reset back to the stock pixel image from google and start from scratch. But im at a loss. Reading this thread people seem to be having issues and i have tried the fixes that look similar to my problem but it keeps doing the same thing.

So any help, thoughts, or ideas, would be appreciated. thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
Thanks

I think after the factory image it's:

- fastboot boot twrp.img

- wipe, advance, data and system, swipe (If updating skip this step)

- flash ROM.zip

- flash twrp.zip

- reboot recovery

- flash gapps

- reboot

Note: I do not see sideload in the instructions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garaxiel:
that's the order i am doing them in, first lineage, then twrp through, both with the sideload command

---------- Post added at 05:44 PM ---------- Previous post was at 05:35 PM ----------

[MENTION=4810220]Homeboy76[/MENTION]

Well then maybe that is where i am having a problem. It's not saying in the instructions to copy the files to the phone, so i assumed since they were not being copied over that you have to use the ADB Sideload command in order to install them, is this maybe where i am wrong? should i use ADB Push to get them on the SDCard first and use the twrp install command to flash them on?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
I think you flash the ROM with twrp.

These files should be on your phone:

- ROM

- twrp.zip

- gapps
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garaxiel:
[MENTION=4810220]Homeboy76[/MENTION]

Just reset phone back to December 2018 stock. Tried whole process again but this time put Lineage, TWRp and GAPPS on phone with adbpush before hand.

followed the whole thing again but used the Install option in TWRP instead of sideload, same problem , the Google G Screen pops up and loops. :/
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
- Backup internal storage and apps

You need the February Factory Image.

- flash-all with the -w

*** Start over ***

- fastboot boot twrp.img

- wipe, advance, data and system, swipe

- flash ROM.zip

- flash twrp.zip

- reboot recovery

- flash gapps

- reboot
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garaxiel:
[MENTION=4810220]Homeboy76[/MENTION]

thanks for the help, sadly it did not work.

However, i went digging in the thread a bit more and stumbled on some people saying that installing the gapps at the initial install was giving them a problem, but installing it after the fact it worked fine, so i figured i would try doing a fresh install without gapps. and lo and behold, lineage booted fine. Got it all setup, used adb to push gapps to the device, rebooted into recovery, installed gapps, rebooted phone again, and i was in business. so not sure why it worked, but it did. So appreciate all the help, and just chalking this up to another weird problem :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Droid_JD:
A similar bootloop happened to me when I rebooted TWRP upon a clean install. It asked me if I wanted to make TWRP a system app (or something along those lines). For whatever reason, whenever I selected "yes", I would get stuck in a boot loop. When I selected "no", the phone finally booted properly. This option/step wasn't included in the instructions, and I don't know if this is what's causing your issue, but I thought I'd throw in my two cents and I hope it helps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] popsulfr:
Thank you so much [MENTION=614507]razorloves[/MENTION] for the work you've put into this.

I was wondering how you set up the build system for it to include the vendor.img in the payload and have it generate the compatibility.zip ?

device/google/marlin/self-extractors_sailfish

has it so it would look for

vendor/google_devices/marlin/proprietary/vendor.img

when the makefiles are correctly linked.

This way it includes the image in the target files zip at

IMAGES/vendor.img

though it still needs a

VENDOR/

in the zip for the final ota payload generation I guess.

Is there more information about this somewhere ? The above was only deduced from reading the source code.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Proprietary vendors can come from here:

https://github.com/TheMuppets/proprietary_vendor_google

This is maintained by razorloves and builds perfectly.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
So the steps to install this ROM on a Pixel XL are:

- fastboot boot twrp.img

- wipe, advance, data and system, swipe

- flash ROM.zip

- flash twrp.zip

- reboot

- boot twrp

- flash gapps

- reboot

Good job :good:

Lesson lerned. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] popsulfr:
Yes, I have had the vendor repo in my local manifest but the vendor.img from the official google ota has much more files and by default lineage does not bake the vendor.img into the final ota.

So after reading through the code I've seen that I could place the extracted vendor.img at the location I've described and link the makefiles so that the image ends up in the out/dist/*-target_files-*.zip under IMAGES/.

But then the ota_from_target_files script expects a VENDOR/ folder in this zip to be able to generate a payload including boot.img, system.img and vendor.img + the compatibility.zip

The script looks for a VENDOR/build.prop, so I tried pushing the files from the vendor.img after mounting it into the zip by hand but the ota_from_target_files errors out on the partition size property.

Is the way to do it more obvious and I'm making life too difficult for myself ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EMT803:
Has anyone figured out how to successfully cast to TV with sailfish. I have searched and found one thread and was able to edit build.prop and add the attached apks, but received a message stating that this ROM was unsupported and to ask the builder to include an "audio_submix" file. This, of course, is a little over my head. I have considered getting a Chromecast and connecting through the Google Home App, but I don't want to go out and buy it if it won't work. Not a deal breaker, just curious if this is a problem that won't have asolution any time soon.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stead2120:
This Rom is legit as f. Battery life is on point and everything! Great work! Im rockin this on Sailfish, just amazing work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
to include a prebuilt vendor img, like the one from the factory image, you just have to tell it where the vendor img is and that it's an a/b partition. like this:

https://github.com/razorloves/andro...mmit/af972d5a3fa5c2965503b9d41a363af5c9605042

to build the vendor image and include it, you have to do like this:

https://github.com/LineageOS/androi...mmit/f06e40fb98c8c485892eb7afb198deab69fb66da

the compatibility.zip is only added when building the vendor img. i just started building the vendor image so that's why it's only in my newest build, and not my older builds in which i only included the prebuilt from factory image.

google yanked out all the miracast support in pie. now you have to have gapps installed and use chromecast.

see my comment here https://review.lineageos.org/224379
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] popsulfr:
Thank you! This is perfect, exactly what I was looking for adds the vendor.img and the compatibility.zip :good:

The whole makefile jungle starts getting clearer now haha

and the WITH_SU environment variable bakes in su :)

EDIT:

I'm not sure but it seems there's still something missing, the installable image only gets 10MB larger with the vendor stuff added but the phone gets stuck on the google screen forever.

If I go back to twrp and flash vendor.img it boots normally.

I merged the patches into device/google/marlin and put the vendor.img at vendor/google/sailfish/proprietary/vendor.img

It doesn't include it properly somehow.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EMT803:
@razorloves

thanks for responding about the Miracast issue. I was afraid of that. I downloaded Google's Home App and did see the cast to Chromecast option. I guess I will have to see if I can find one used for cheap. It bugs me not being able to use every available option, but would much rather have this ROM instead. Thank you for trying. It probably bugs you a little as well. Just to make sure before I buy one, has anyone successfully used the Chromecast method to cast from sailfish?

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

Also, due to the warning about restoring apps using TB, is it a waste of time to use that as a backup avenue for individual apps?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
guys is there a way to keep the stock recovery?

Thing is I'm getting a new Pixel XL due to warranty (from amazon) but don't want to keep TWRP in case I need to wipe and oemlock

any suggestions on how to do it all from fastboot/adb push?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] YTSec:
Just flash the stock factory image from Google?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lukazaz:
yeah I forgot to say last time the unit had a USB-C issue and would only charge :( so I only wiped everything via twrp so it would not boot to LOS, maybe use the reboot to recovery command instead of doing it would work? dunno :( scared to try
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pyrocide:
Been having an issue that pops up intermittently since Jan build. My phone (XL 128) suddenly loses all ability to make or receive calls, send texts, see previous texts either through Hangouts or the SMS app for a random period. Calls made get me set to an automated Sprint Operator message. It'll show this same configuring Sprint network notification and does not go away until it finally does. Problem one is that I am on Project Fi, not Sprint, have been since day one and have never changed/returned/warrantied phones. Reboots don't work, resetting network settings don't work. I finally got fed up with it and wiped everything on phone and reinstalled February build. Includes internal storage, system, data, caches, so on. Blew away my phone to start fresh. So far it hasn't happened again, yet.

Has anyone else experienced this?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jpcdeux:
2.16 still suffer from frequent random reboots?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DarthDestroyeis:
I have not had any issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blu.italia:
Same here! :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Lrs121:
Mine has soft rebooted a couple times but it is far more stable than the January build I was using. I used to get reboots several times a day on the older build. Now its far more infrequent.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] All-In-One:
Yup, suffered a few, and yesterday after rebooting itself the phone got stuck in a black screen even though the status and navigation bars where visible. Tried whiping cache and rebooting the phone again but that didn't work.

Guess I'll stay on the stock ROM until march build comes out.

(I'm on sailfish)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
there's no random reboots with this rom. you guys having that problem must be flashing or installing something to cause them. like a custom kernel, or magisk, or some module or mod.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
I must agree. I have been using every build that has come out (including many builds that have not been released to the masses), and performed clean flashes, dirty flashes, and upgrades multiple times, and I have never experienced any reboot issues to date. It is most likely due to some other factor as Razor stated, it almost always is... I went through this with the early build cycle of LOS15, and almost every set of logs I looked at for people ended up being issues with other things that have been installed, or an issue with the download/install.

Just throwing this out there, maybe provide a list of what you are running, maybe someone might see some similarities with something they are running as well.

Also, I would make a nandroid backup in TWRP, redownload the ROM, and try a clean install without anything else (no custom kernel, or magisk or otherwise), and see how things run for you at that point.

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jpcdeux:
Then why would I have them several times a day? A couple times an hour if using regularly with the 02.07 build even when following directions to the letter with no extra **** installed? Even though I've been flashing/making roms for years, for the first flash I wanted to be as stock rom as I can before I start messing with kernels, modules, etc.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
Please post some logs and I would be more than happy to take a look at them...

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SikYou:
Not once. I've run every build of this ROM and have never had reboot issues. I have had a few minor odd issues on the latest build (Marlin) but no reboots.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xaoup:
Should i still flash the radio.img before flashing?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Stealth111:
If you are going to flash the latest February ROM, then yes.

The radio img in google's feb update is new, so that needs to be flashed. make sure you do '--slot all' fastboot option

Example: fastboot flash --slot all radio radio-sailfish-8996-130181-1811270246.img <---if you are running sailfish

Stealth111
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xaoup:
Just to clarify, the radio.img only and NOT the bootloader.img anymore, correct?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] IISAKNIFE:
I haven't been able to find an answer to this. Do you need to flash to update, or are OTAs available? And if OTAs are available, will it be a seamless transition to official builds, or will I need to flash to go from unofficial to official.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kingbri:
Just run ./flash-base.sh
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] All-In-One:
Yes, you can only update by flashing. Razorloves does not have an OTA server as far as I know.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] razorloves:
that's the wrong way and results in only the current slot being flashed. follow instructions in first post.

That happens when you have the wrong vendor img with different apk signatures. Not sure how you got yourself into that situation. Maybe you flashed the vendor img from the factory image? You can't do that because the apk's on /vendor will end up with insufficient permission and you'll get the embms crash. Now your vendor app data is bad and needs wiped. The easiest way to fix is to just do a clean install. (wipe data)