yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
Somewhat off-topic while related to adding walleye again to the builds on hudson and this resulting in my curiousity: Is there a way (being no involved developer) to get more info on the - somewhat entertaining but not always all that documentation driven - commit labels? E. g. how to interpret One last revival related to undoing the QPR3 hold? WAAAAAHOOOOOOOOOO was a bit easier to get - especially being a reader of this thread. ;)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
No need to check Gerrit.

I said a week ago what was happening.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
Agree no need specific to walleye - but having learned about hudson a while ago I was simply curious how to read the statements there. It was e. g. quite interesting to see that QPR3 also caused a very short build hold. (Already passed.) So, it was not specific to walleye progress but general learning to connect the dots.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] itsirfandude:
Thank you so much for the build . How frequent will we get the builds from now on
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
Weekly official, monthly unofficial.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] itsirfandude:
Still no official builds at https://download.lineageos.org/devices/walleye/builds
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
Just give it time, like I've said above, build schedule was weird, it'll post soon enough
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] avm_:
Hi,

I just want to inform you that my Pixel 2 is working like a charm with todays official build. Thank you so much for keeping up the great work!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] itsirfandude:
I can see an official build today. How do I switch from unofficial to official build ?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
Excellent news. Thank you for all of your efforts in getting this older device back in the fold
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
you wipe and reinstall
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] |\|3π1:
Great Job. Thank you very much...
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
Hi,

thank you for your hard work.

Unfortunately I have a problem installing the official build. My Pixel runs with the official build from March 15th. Now I downloaded the new build and trued to install it with updater. The installation runs and finally requsets a restart. The Pixel boots the new system and just before it is ready, it restarts again with the old build from March.

Has anybody an idea what I can do? I'm no Android specialist and I don't know where I can find a suitable logfile.

I tried to read the logcat, but it shows only the last reboot.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
did the same and it upgraded to the June build. In my case I downloaded the file, copied it over to the phone and selected "local update" from the options
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
Not sure if anyone has seen an increase in battery usage with the June 28th build? My pixel2 does not have a sim card and is just on wifi. The battery usage has gone from around 0.5% per hour to 8% per hour. It dropped from 100% to 15% (midnight to 9am) when left idle.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
tried locel update, but the same problem. During the first boot I see moving circles, then reboot to old version
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
I followed the same route - update via updater from 240308 or 240315 (can't say for sure whether I had the very last update prior to the break installed) to 240628 on a device without any GApps or other extra packages. No issues here.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
No such issue here - same setup without SIM (flight mode active but WiFi on) but also one with SIM and normal operation.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
thanks. I'll reset the phone and set up from scratch and see how it behaves.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
If you set it up from scratch and use Google apps, please let me know if they fit.

I have a small bit of a suspicion that what's happening is users are updating and the persistence script for Google apps is failing because there's not enough space
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
maybe gapps are the problem with the failing installation on my Pixel. I use gapps. Is there any logfile that reports a failing update?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
I reverted the system to the 20240315 as a first step using the settings -> system -> system updates with the local update option. The battery usage returned to a more normal level. The previously installed GAPPS was "MindTheGapps-14.0.0-arm64-20231025_234300"

Then followed the installation instructions from step.6 (Installing Lineagos from recovery).

Did a factory reset and then sideloaded "lineage-21.0-20240628-nightly-walleye-signed" and "MindTheGapps-14.0.0-arm64-20240612_135921" without any apparent errors apart from the documented 47% message.

Then restarted phone and went through the setup steps but have not installed any apps yet. Now leaving phone off charge to see how the battery drain is, first indications are the it remains high.

Below is the output from the adb commands. I renamed the files prior to install to make the entered commands a bit shorter but the above are the downloaded names.

F:\adb\platform-tools>adb -d sideload LN21_20240628.zip

* daemon not running; starting now at tcp:5037

* daemon started successfully

serving: 'LN21_20240628.zip' (~47%) adb: failed to read command: No error

F:\adb\platform-tools>adb -d sideload GA14.zip

Total xfer: 1.00x

F:\adb\platform-tools>
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
The issue appears to be that before the most recent update the full Google apps package fit, whereas now only the minimum does.

Sadly this means that you're just going to need to reflash Google apps after the update.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ian1182:
The only Googe Apps package in the wiki is 421MB in size, is there an smaller alternate that should be used?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
No no, at runtime on install it decides on full or minimal.

Previously it decided full, but bc of growth, it now decides minimal.

The issue is people who had full before now have their update get bungled ad there isn't enough space to copy them over.

There is no good fix here other than "reflash Google apps after update".
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
how can I reflash the gapps? With adb sideload over the running official version (March 2024)? Or first sideload update from June and then gapps? Or first wipe the phone?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
use updater to get to new build, boot to recovery and reflash gapps
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
:-( doesn't work. Rolls back to March version
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
so, you installed new update, rebooted into it, then rebooted to recovery and flashed google apps?

Try flashing gapps one more time while on the slot corresponding to the one the ROM flashed to
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
I installed the update with the updater app, then booted directly to recovery, not to system, flashed gapps via adb sideload and booted then to system. The circles moved, maybe for 2 or 3 minutes, then it restartet to the March version.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
Ah yeah, you just installed Google apps on the same slot you were on, need to reboot after applying the update and then install
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
now I tried:

adb -d reboot sideload

adb -d sideload lineage-21.0-20240628-nightly-walleye-signed.zip

Reboot to Recovery

Apply Update

Apply from ADB

adb -d sideload MindTheGapps-14.0.0-arm64-20240225_232108.zip

boot to system

..and it worked :)

Important, I had to use the Gapps version I used at the upgrade from lineage 20 to 21. First I used a newer version and the Google Play Store failed.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] itsirfandude:
What's the difference between official and unofficial build? Any notable changes in the official build?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ilpolpi65:
adb sideload last unofficial: all ok

Thank you!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
Not sure what differences you look for exactly but see a. o. OP:

Leading to the assumption that the obvious difference is that official comes without GApps and Pixel goodies. For differences on details, you might have to wait for npjohnson.

From another unofficial build (jfltexx), I am aware that the updater allows there also flashing previous builds if someone wants to rollback. Not sure whether here (walleye) also the case.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Niroman:
Did it change back to pixel launcher or is still Trebuchet? And if it's pixel does the select feature in the recents tabs work?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] frunsel:
The manual update is good. Very big thanks.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
I am having an issue with VPN connections - consistent with two different VPNs:

CalyxVPN - no clue about the underlying protocol

IKEv2/IPSec PSK to an AVM FRITZ!Box 7490 running FRITZ!OS 7.57

Observed problem: Once connected, no connection to internet with no clear error message. Valid in various apps. Also, deactivating Private DNS (no issue without VPN) is not improving the situation.

Things is that I know both can work:

CalyxVPN - was for sure functioning on one of the LOS 21 walleye March builds with activated Private DNS.

IKEv2/IPSec PSK - functions on LOS 21 for hotdogb to same connection point without issues.

Anyone an idea - am I missing something obvious? Will file otherwise an error report in Gitlab.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
And another challenge (therefore in a new post on purpose):

A bit special setup using WhatsApp (via APK available on the official website) but without GApps. Until incl. Android 13 (LOS 20), no issue at all to receive notifications. Since upgrade to Android 14 (since resuming LOS 21 builds in June), I don't get reliably notifications - mostly after not using the device for a while - but see new messages only in the app. So, I guess it is about deep sleep or so.

I tried already the hint related to Android 14 in general about showing standard and silent notifications but no improvement.

Background usage is allowed anyway.

Anyone experiencing the same issue and/or having an idea?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] robi2024:
now I tried to install the build from yesterday with the updater and again the same problem. After the update it restarts and rolls back to the previous verion. What is wrong with my Pixel? Isn't there any logfile where the updae is reported?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] s4tch:
thanks for the little guide, worked for me too
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Cabirto:
Hello,

I did exactly the same as you to update last week. After updating today with the updater, play services (playstore and localisation) don't work anymore. I guess I can adb sideload them again.

And also thank you a lot for the efforts to keep my phone up to date!!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] neimovirne:
Lates build of 07/13 broke Play Store, Chrome and camera...its force closing every second
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
Recent growth in LineageOS pushed it to the point that full MTG doesn't fit. So we hit the grouper (minimal) path, but people who are on old builds with full MTG.... It breaks them. They need to reflash gapps. It sucks but not sure how to handle it.

You need to re-flash google apps via recovery once.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] neimovirne:
so I do not need a factory reset? only reflash gapps?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
correct
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] neimovirne:
it worked

thank you
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] minecraftplayer2937:
My pixel 2 needs a battery repair, but I'll look into this when it's fixed
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Coxswain:
Updated to the 2024-07-20 build and mobile data is no longer working for me on Rogers in Canada. Tested with a factory reset before installing and having the same issue. When I check the APNs it says "Access Point Name settings are not available for this user".

Rolling back to the 2024-07-06 build and mobile data works as normal, and I don't get that message when checking APN settings.

Edit: Upgraded to the 2024-07-13 build that I skipped over and mobile data seems to be working there, it's just the most recent build that seems to be borked for me.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] js-xda:
There are several APN changes mentioned in the change log but nothing that I see related to your provider. Maybe the general order change might have mixed up something. As this is rather a general thing of LOS good to file a bug report there. See OP for link.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Coxswain:
Thanks for the heads up. Once I have some time later I'll do the update one more time to recreate the issue and get everything that's needed for putting up a formal bug report.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Coxswain:
Checked the builds page and the 2024-07-20 build doesn't appear to be there any more. However, I was still able to do the update to the July 20 build through the updater and mobile data seems to be working now with the APN settings page looking normal instead of that permissions denied message.

Not sure if you guys fixed something or if it was something on the provider's end, but it looks good to go for the time being.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] npjohnson:
We fixed it. APN issue.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] itsirfandude:
does it mean that I can move from unofficial to official without wiping now? I am on July 25th unofficial build now
[Google Pixel tablet] npjohnson:
Google Pixel Tablet

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the Google Pixel Tablet.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

tangorpro - Official builds​

tangorpro - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.​

Find any? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​

Kernel Source: https://github.com/LineageOS/android_kernel_google_gs201
[Google Pixel tablet] C.Flat:
Does casting to the tablet while docked work on your unofficial build? I self built and installed Lineage 21 on my tablet and casting doesn't work and I'm wondering if that's expected or not. It's not a big deal I'm just curious
[Google Pixel tablet] npjohnson:
I mean, you'd need gapps, but it should work?
[Google Pixel tablet] C.Flat:
Yes I had gapps built in. I'll test out your unofficial build to see if there's a difference.
[Google Pixel tablet] npjohnson:
Mmm. Interesting.
[Google Pixel tablet] C.Flat:
Hub mode settings are there but there's nothing to cast to when it's docked. I should have your build installed in 30 minutes or so to compare. View attachment 6055566View attachment 6055567
[Google Pixel tablet] npjohnson:
let me know
[Google Pixel tablet] C.Flat:
Same result.
[Google Pixel tablet] Hittsy_TW:
Not to be rude with the potential flood of casting/docked issues, but I updated to LOS 21 (from lineageos.org) added the recommended gapps package during the update, and the device still isn't available to cast to, audio isn't being routed to the dock's speakers, nor does it even seem to recognize that it's docked. (Note the "Dock connected state" in the attached pic, despite the fact that it's charging on the dock.)

View attachment 6069811
[Google Pixel tablet] npjohnson:
That's really weird.

I am actively listening to music on my tablet on the dock on 21

Please file a proper bug report on GitLab for tracking purposes
[Google Pixel tablet] Hittsy_TW:
Turns out I had "Settings > Security & privacy > More security & privacy > Trust > Restrict USB" set to "Deny USB connections". (Also explains why I had difficulty installing LOS21.)

I filed 2 bug reports, one last year for the casting issue, using LOS20:

https://gitlab.com/LineageOS/issues/android/-/issues/6092

And one for the casting + speaker and dock recognition issue, using LOS21:

https://gitlab.com/LineageOS/issues/android/-/issues/6705

Should I close the second? Maybe update it, since dock behavior is unexpected (even if logical, nobody thinks of the dock when configuring access for the USB port). Or close the first, since the issue has persisted on LOS21?
[Google Pixel tablet] npjohnson:
I have no good way to exclude the dock from that check, so if you did update that ticket I would still probably close it sadly.

As for the first one, casting is still an issue that we're working on
[Google Pixel tablet] snickle:
The link the the unofficial versions is down. Is it coming back?
[Google Pixel tablet] npjohnson:
fixed
[Google Pixel tablet] snickle:
Can't find the following files files mentioned in the install step for the unofficial version.

boot.img

dtbo.img

vendor_kernel_boot.img

Find them in the link provided in official build
[Google Pixel tablet] snickle:
Now can't find vendor_boot.img file mentioned as part of flashing recovery.

I tried flashing lineage-21.0-20240211-recovery-tangorpro.img but that would not boot into recovery. SHould I try the link from the official build?

Used the official build files
[Google Pixel tablet] npjohnson:
yeah you can use official stuff to supplement missing files - will fix for next month.
[Google Pixel tablet] snickle:
Everything looks good except for while playing music over the dock, it randomly disconnects from the dock. I have to remove it wait 30 seconds and reattach.

Showed I open a bug on the official support site?
[Google Pixel tablet] npjohnson:
sure, weird, connection is rock solid here.
[Google Pixel tablet] andy356:
@npjohnson Is there a reason touchscreen isn't enabled on the LOS 21 Recovery? I panicked at first and thought something broke before remembering I could still use volume button navigation.
[Google Pixel tablet] npjohnson:
Because in order to enable it on this device would break it on every other pixel that uses the same GS common tree.

We are working in it but it isn't high priority.
[Google Pixel tablet] andy356:
Alright. Just in case it isn't known, the same problem occurs with lynx.
[Google Pixel tablet] npjohnson:
correct, it is know. These two are the oddities.
[Google Pixel tablet] andy356:
@npjohnson Please check your Gitlab notifs. 2 of the 5 bugs I had opened are now resolved in LOS 21. 3 are still existing. I've pinged you on the 3 open ones.
[Google Pixel tablet] hexaheximal:
Yeah, I have this problem too. On LineageOS 20 it worked fine. No idea how it broke the way it did.
[Google Pixel tablet] Mary1989:
HELP!

I can't buy this device in Switzerland

See https://www.toppreise.ch/produktsuche?q=tangorpro&cid=

No match
[Google Pixel tablet] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
Google Pixel 3a

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the Google Pixel 3a .

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

sargo - Official builds​

sargo - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

ESIM enrollment is broken, but if you enroll before upgrade it should work fine.​

Find any? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​

Kernel Sourc.e: https://github.com/LineageOS/android_kernel_google_msm-4.9
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] flyntt:
I'm sorry, but where is the link of lineageOS 21?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
the builds are uploading, it may be ~24 hours for some devices, 40*2GB zip files take a while to upload lol.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] zeartic:
Im going to try this as soon as i can B)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] TatsuMasa:
Upgrade to LineageOS 21 was done successfully. So far so good. Thanks a lot.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] zeartic:
Is there a build without gapps?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
Nope, and there won't be until officials come out in the future.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] saeba01:
Downloaded image and upgraded my 3a. Works great! Thanks so much for continuing to support this phone :-)!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] vuong0888:
Wellcome to 21
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] alex.o:
Works great! Easy update!

I wasn't able to add a card to google wallet for google pay (couldn't on the lineage OS 20 unofficial either).
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] simonirwin:
The author has reported that Google have blocked his patch that allowed Pay to work. I have it working by rooting with Magisk, installing Chiteromans PIF fix, and installing my own "fingerprint" file. Pay then works, but the rooting stops some bank apps. I can still access bank accounts via a web browser.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] skills14:
Updated via adb fine, thanks for this
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] aeldeyr:
Did anyone have an e-SIM before upgrading? Does it work on this build?

Worked flawlessly on the unofficial 20, however, for the version 21 official LOS site tells e-SIM support is a known problem on sargo. Does it mean after an upgrade from 20 to 21 there is a chanse I'll lose the e-SIM support and saved e-SIMs? Would it ever be possible to add new e-SIMs on 21 or starting from 21 e-SIM enrollment is no longer supported?