yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Homeboy76:
<<Edit>>

:oops: Post #67
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Read the posts above yours.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
The random fingerprint reboots should be solved: https://review.lineageos.org/c/LineageOS/android_kernel_google_marlin/+/367168
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UnOrdinary:
Bug: Is anyone getting issue with google camera and stock camera in official LOS 20?

After a reboot i can capture photos on google camera or stock camera...

But after some time i can't capture photos without reboot on both google camera and stock camera...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wildblade64:
Found two bugs. Nightlight mode acts weirdly. best way to describe it is it activates in the recents menu but deactivates as soon as you switch to an app. Second it is not possible taking picture in this build yet. Strangely video recording is working. That is everything I have found. Despite all that I really enjoyed lineage 20 I hope this keeps getting worked on and will switch to it as soon as its mostly stable. Everyone working on it thank you for the hard work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Which camera app are you using?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wildblade64:
The default camera app that came with the rom. tested fresh install on the unofficial version.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Neuen1:
I'm also getting the camera bug with stock app and with Google camera. Immediately after booting I can take a few pictures but it stops working soon after. Easy way to replicate is holding the shutter button on gcam, you should get a bunch of all green pictures. Sometimes I can take a picture using Google camera but it's just all green. Video works fine, but not 1/8x slowmo video, image gets corrupted and then the app crashes. I tested on fresh install of official ROM
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lmvuong1997:
+1. Looks like the random reboots have been fixed, only camera and night light left to go for a stable rom <3
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Camera issues, slow-mo, and night light issues will be fixed in the next builds!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UnOrdinary:
Bug: Can Anyone check that if you turn on flight mode then turn it off! Is your sim working? Or it's working only after reboot?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Francesco Libera:
Hello guys! Thank you for the official support! Unfortunately, my pc does not recognice the device when it's on lineage recovery. But in bootloader mode and normal usage mode it recognises it. Is there something i can do? I tried a thousand drivers but unfortunately none of them work
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Doesn't recognize at all? Or doesn't see ADB, you need to select ADB side load before it will show
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rauhut:
Can confirm that I also see this on my device. As a workaround it sometimes helps to enable / disable flight mode again and / or to reset the Internet connection in the settings (small button in the upper right, first time I saw this with the current version).

Other things I noticed since updating to clean LOS 20 earlier this week is quite fast battery drain compared to LOS 18 (my battery is old and still the same that came with the phone) but after some reboots / loadings it seems to improve again (will further monitor, might be related to less use after initial setup). Other is some "flickering" when night light is on and you switch apps, turning into a sepia color for part of a second and back to grey / brighter screen again.

Over all I'm quite happy with the new version, thanks for keeping our Pixels alive. 🙂
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
night light and battery issues should be fixed in the next build!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Francesco Libera:
At all. Windows popup windows tells me that the device is not working properly and windows doesn't recognize it. When I try to install proper driver in device manager, it tells me that the best drivers are already installed: unknown USB device (device descriptor request fail).

Tried TWRP (Windows recognizes it). Screwd everything multiple times and reflashed stock. Now even stock OTA doesn't boot up. It shows the Google logo loading screen forever. 😂
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Francesco Libera:
I bypass the problem using TWRP after many non expert try. Maybe it may help someone:

• In Windows PowerShell > flashall.bat in bootloader mode to resuscitate the Pixel XL. (Fortunately no boot loop fore some reason this time);

• activated Debug USB in developer options;

• .\adb reboot bootloader;

• .\fastboot flash boot TWRP.img;

• copied repartition.zip & ROM into device;

• installed repartition.zip;

• rebooted back into TWRP;

• noticed some error of mounting things finishing with "invalid argument" and internal storage (0MB)

• formatting everything > yes;

• noticed that now internal storage says 20136MB;

• formatted system (0MB) using ext2 as I saw in a YouTube video;

• now system has ~3500MB!!! (I sincerely don't remember the precise number);

• copied again and installed UNOFFICIAL ROM with Gapps & Goodies;

• everything went good until the message "No OS Installed" at the reboot. But I rebooted anyway.

•And there we go! It Works! I've never had a ROM this amazing. Lineage OS + Google goodies is the absolute best. Thank you for your work and dedication. Hoping I will not f*ck up the next update 😂
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UnOrdinary:
It's seems like mobile network get disconnected much often ... I just talk with my wife 50 min at that time i saw every 15 min network is gone ... I can't even check balance ... After reboot it's back again and then i called her again same issue after 15 min ... 3 times i rebooted my phone ... Network getting disconnected so often ...

And

New Issue: With camera

If i start record a normal video with google camera or even with LOS Stock camera

First 1 to 3 sec there will be always a glitch (like getting stuck) then play again ... And another thing with LOS Stock Camera and google camera video recording gets lot darker in front camera it's much more darker then back camera ...

Sorry for my Bad English!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lmvuong1997:
I can confirm the airplane mode bug, and yes, resetting internet connection a few times got it back.

About video record, I uninstall los stock cam here but with gcam, sometimes it will say "there was a problem, a part of the video could be not saved" and i have to stop and start new record. And it's the only problem about camera for now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] alex.o:
I'm having trouble using the Updater app. It will fail instantly or at 2%. I'm new to lineageos and am not sure how to resolve this issue. I'm running one of the first official builds and it has been great, just has occasional issues with the camera.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rauhut:
You might want to try clearing cache and/or data of the updater, at least this worked for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] alex.o:
Thank you! I tried, but that didn't work. I'll just flash from ADB.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lentm:
I finally fresh installed the latest LineageOS 20, everything works smoothly except MTP/ADB on my Windows 10. I keep getting USB not recognized error. It worked ok with LOS 18.1 and other phones with LineageOS 20 or stock roms. Re-installed drivers, still the same issue. Any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
which driver did you reinstall?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] lentm:
I tried this: https://developer.android.com/studio/run/win-usb
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
interesting - I'll work on it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UnOrdinary:
@npjohnson bro is there any way to enable Mac Randomization in LineageOS 20.0?

Or is it hardware related feature?

If possible can you add this feature if it's not related hardware! please
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
our firmware isn't compatible. Sorry.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] UnOrdinary:
Bug: is there anyone facing issue like phone turning off when battery 15% to 25% ? In LOS18.1 or stock it never happened! (My phone's battery is old!) Even then on stock or LOS18.1 phone never get shutdown when it's 15% to 25% charge ... If i turn on phone when it shutdown it's shows i still have 25% battery but if i use you wifi or data or camera ... It shutdown again ... Only when i don't use any data or wifi or camera just phone for calling via sim ... It's ok then no more shutdown!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Really just sounds like a dying battery.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] whathaveibecome:
I could use a bit of help.

when I update the partition it says:

(computer, linux)

adb sideload partition.zip

(phone)

Verifying update package...

E: footer is wrong

Update package verification took 0.1s(result 1)

E: signature verification failed

E: error: 21

Installing update.....

And there it hangs, forever. Or at least I let it sit for 15 mins and it hangs at Installing update.

My add kicks in and I press the back button...

Tried all kinds of thingseven tried updating the partition from twrp out of desperation. Nothing works.

Currently running LOS 18.1.xxxx

Update: now I am unable to go back to los 18.1. Great. And I have go to work in 12.5 hours I need this phone working.

Edit #2... After MUCH ****ery I was able to get it installed via this method....

1. download factory images and run flashall.sh

2. fastboot boot twrp-3.7.0_9-0-marlin.img

3. copy partition.zip to downloads directory and use twrp to install it.

4. copy los20.zip to downloads directory, and then use twrp to install it.

FYI LOS recovery flat out refused to install the partition.zip or the actual los20.zip Only twrp worked.

Anyways, I'm good now and can get to sleep. Thought I would share the crap I went through in case any one else had the same issue.

Update2: Phone works as to be expected. Thanks to whomever made this update possible. My only issue is that when talking on the phone, the speaker goes silent as soon as the screen turns off. This happens when using speaker phone or not. So every 30 seconds I have to tap the screen to keep on hearing whomever I am talking to. Kind of annoying.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] somethingsomethingroot:
Finally got around to trying it with a different laptop with a fresh Win 10 install with different cables, enforcement disabled, etc, and I still can't access storage from the PC. My other Pixels worked just fine. Even reverted to stock just to see but the issue was still there., so I'm back on LOS 20.

If the access is lost, I guess it is what it is. "Your warranty is void..." and all that. I just can't figure out why that is, and that's bothering me more than anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Francesco Libera:
Man, let me tell you something. I don't know if it's a new thing and it's just me but updating the unofficial rom (with gapps & pixel goodies) as if it were official through the updater app, it's pretty freaking amazing. No more mess around with TWRP and zip files. Thanks Nolen for your superb work and dedication.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
That's the goal!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Tefzors:
Hey, I just bought a Pixel XL to use as my "unlimited Google Photos" backup and out of curiosity I went to see the ol' trusty XDA forums and I come across this.

I'm impressed. A13 on a 2016 device. That's amazing. Well done and thanks for your work. I'll be definitely tinkering with this later tonight.

EDIT: Successfully managed to install the unofficial LineageOS ROM (and Magisk as well) with no issues thanks to your detailed instructions and can confirm that backing up to Google Photos with unlimited storage is possible. This is great, thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] alex.o:
Are there differences in the Verizon and non-Verizon OG pixels? I have one that is bootloader locked and unfortunately can't run lineage os. The one that can, can't make voice calls. They get different carrier preferences. I made sure the APN settings are the same. I don't know how to get it to make calls. LTE data works, but it says the voice service is disconnected in the dialer menu of *#*#4636#*#*. Does the OS have something to do with that? I need it to have an option of LTE,UTMS,CDMA auto (PRL).

I didn't test this device before lineage OS on verizon though. I wonder if they have different modems or software to connect to verizon. Same Sim card, the bootloader locked verizon phone works no problem, the OG pixel from google won't connect to voice. I'd rather run the one with lineage OS. This is an amazing build!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Try running stock on the one that can run lineage and putting the VZW SIM in and making a call, just to make sure it's a lineage problem and not a phone problem
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] activadroid:
I just DIY replaced batteries in 3 2016 marlins (all orig OEM batts), because they would boot OK then die when loading youtube to play music.

I am hoping this solves the problem.

BTW: Battery replacement is difficult ! I cracked (multiple lines & pieces fell off) the front (touch glass) of the first screen assembly (but amazingly, it still works !). For phone #2, I used single edge razor blade(s) for wider lift, but went TOO FAR IN, under the touch glass & broke the LCD glass only - NOT the touch - but now DEAD. ALSO overheated & 2 spots visible on front. On #3, I used single edge razor again, & removed the whole assembly with no visible damage or screen overheat burns. I ordered 1 replacement screen assembly via ebay for about $30 & it arrived quickly & works great. The batteries were $12 (included tools that mostly did NOT help ! - Torx driver supplied was wrong size !), and about $10 each for #2 & 3. I will probably order another screen assembly, once I confirm that batteries were the only problem.

[NOTE: I also rubbed / rolled up & removed the double sided tape that holds the batteries, just in case the new batteries are bad. the first had mfg date of 2017 ! I rubbed the double sided tape off top & bottom ends of middle frame, so I can remove the $$ glass again easily, if I need to. I plan to use the silicone cases to hold them together for testing. 2 of the 3 phones to be used mostly for audio streaming, in fixed locations, not EDC. 3rd has SIM & will get new double sided tapes after testing].

THANK YOU NPJohnson for keeping these phones alive !
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] justin333:
Thanks for supporting this phone even after these many years...really appreciate this!!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blckbear:
Hi, I've been using your unofficial builds (because I wanted GApps) for a week now and I found some issues that I wanted to report, I'll attach logs on this post.

The first issue was USB tethering not working, the phone just disappears from the PC, tried on a bunch of different PCs and OS and none work. Another user reported the same issue around November I think in the TG chat.

The second issue is that USB 3.0 support is broken, using a USB 2.0 cable works fine, but when using a USB 3.0 cable (which worked fine before on both Stock and crDroid 7, the original A to C cable provided by Google with the device) the PC says that the connected device was unrecognized and when checking the error inside Device Manager (in Windows) it says:

"This device cannot start. (Code 10)

The USB device returned an invalid product description string descriptor."

This was tested on a bunch of different PCs and OS too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
Rootfan tracked down the issues, both of these will be fixed in the next build.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blckbear:
Thanks for the quick reply! That's great to hear, thanks for the great work y'all are doing keeping this phone alive!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rodken:
I've been having the same issue on Windows 11, but not on Windows 10 from the inception of this ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sdmatto:
Is there any way to get Play Integrity passing using this ROM?

I have tried with (i) unrooted LineageOS (your version), and (ii) rooted (Magisk, and Magisk-Delta) LineageOS, with PlayIntegrityFork v.6 and a working custom.pif.json file (I know it is working because it passes Play Integrity on a stock, rooted Moto Z2 Force), and I cannot get the requisite "Device is certified" in Google Play.

Any advice appreciated. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] npjohnson:
likely no, they fixed all the workarounds.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blckbear:
I got it to work using PlayIntegrityFork v7 and a custom.pif.json that uses a fingerprint prior to march 2018 from a Pixel XL. It will most likely be patched anyway in the near future. Send me a DM and I'll share the custom.pif.json file
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HowardZ:
In Magisk settings, I changed from update custom to update stable. Then thought I should not have changed it. But, to set it back to custom, it asks for a URL. I am using lineageOS official, but the version before the current 20.

Sorry if this is the wrong place to ask.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jackeagle:
Moderation Edit

Thread closed per [OP] request.

-jackeagle

Senior Moderator
[Samsung Galaxy S8 Questions and Answers] entitymorton:
few days ago my phone turned off and didn't want to boot for no apparent reason, i tought that maybe flashing another rom could be usefull but no, now the phone can't turn off while not charging but is not a battery problem because sometimes it works, i tried to flash stock rom and kernel but nothings work,

do you have any ideas ?
[Tilt, TyTN II, MDA Vario III Themes and Apps] lljlehr:
I've read a lot about other people's GPS issues but I feel I have something different. With all roms, including stock, I get a "dialed, can't connect" bubble when I try to use the gps. Google maps, Live Search, even when Franson GPSgate starts the gps, the bubble. I've got the L26 kaiser diamond rom with the 1.65.21.18 radio and spl 3.56, unlocked, using media net, HSDPA on, proxy off, running great on a tilt All other data is blazing fast. The gps used to work, with 15 second locks with quickgps. Do I have the same problem as everyone else?

Thanks
[Tilt, TyTN II, MDA Vario III Themes and Apps] lljlehr:
bump it

No one else gets the "dialed" bubble?
[Tilt, TyTN II, MDA Vario III Themes and Apps] kilrah:
Nope.

Are you updating QuickGPS once in a while? It might have outdated data and wanting to try and download the hew info when trying to use the GPS.

You can try to disable AGPS using KaiserTweak too.
[Tilt, TyTN II, MDA Vario III Themes and Apps] khaytsus:
Google Maps and Live Search both have to download data to display maps, so if you're simply seeing them connect to download data that's working as designed.

You might check to see if AGPS is turned on, that downloads data over the cell system for a quicker lock, but generally it just causes more problems than it helps.
[Tilt, TyTN II, MDA Vario III Themes and Apps] lljlehr:
10-4

OK, I'll give the AGPS deactivation a try
[Android Software/Hacking General [Developers Only]] r3pwn:
I've been working on this project for the past couple of weeks, but finally feel like it's in a decent enough state to release to the general public (even if in a beta state). There are some features that may not be 100% functional on all devices. If you encounter one of these areas, please create an issue on GitHub (and provide as much information as possible), and I will get to it as soon as I can.

What is libmjolnir?

Libmjolnir is a frontend JavaScript library designed to simplify the process of flashing firmware to Samsung devices in download mode. It leverages the capabilities of WebUSB to allow you to flash firmware directly from your Desktop's browser (* currently supported in Chromium-based browsers only).

Please note: Use this library at your own risk. I am not liable for any potentially damaged devices as a result of the direct or indirect use of this library.

Current features

- Dump device's PIT

- Parse device's PIT

- Flash file to known partitions

How can I try it out?

I set up an example project using the library, which currently lives at https://r3pwn.github.io/libmjolnir/

If you want to use the library in some site or application of your own, feel free to check out the source code at https://github.com/r3pwn/libmjolnir, and let me know if you have any issues with it!

Note: Please check out the known issues wiki page before reporting any issues, especially for people using Windows desktops and laptops.
[Android Software/Hacking General [Developers Only]] jrkruse:
Didn’t know you were still around man. This looks pretty cool going to try it out in a few days.
[Android Software/Hacking General [Developers Only]] r3pwn:
Yep, still around! Haven't had a ton of time for Android stuff lately, unfortunately, but have been playing around with things where/when I can.

Right now, the demo seems to work well on my SM-T280 and SM-T357, but has some issues on my SM-T290, and I've heard of some issues on the Galaxy Tab S5, as well.

I'm still familiarizing myself with the Odin protocol, and hoping to resolve the bulk of the issues within the next couple of weeks (or sooner, if possible). I'm just excited about the possibilities that this opens up, having a (largely driverless) cross-platform flash tool :)
[Android Software/Hacking General [Developers Only]] jrkruse:
Yes indeed
[Android Software/Hacking General [Developers Only]] r3pwn:
Just pushed a few updates, and created a new release on npm - 0.6.0

- Fixes an issue that was preventing flashing multiple "segments" of a file

- (hopefully) addresses incompatibility with many newer devices

- adds the library version number to the example project

If you are having any trouble using the new version, or if there are any regressions with your particular device, please let me know
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] soryuuha:
Hi guys,

is there any security updates, after A13 update which was on May 2023?

My security patch still stuck at May 2023, while I saw e30u is already at August sec. patch
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] dom88rx7:
After A13 updates, did you get 5G on Malaysia's telco sim card, Unifi Mobile, Umobile & XOX ? Digi & Tunetalk don't have for sure. I am asking this due to Malaysia is very slow & inefficient when it comes to developing the 5G infrastructure & coverage.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] soryuuha:
kinda unrelated, but let me answer. I am currently using Maxis MY 5G on X30 Pro, on A13. I am able to use 5G on Yoodo MY as well, on A13.