yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7a] mxz55:
Nice, i see the first official build (20.0-20230625) has arrived :)
[Google Pixel 7a] EthanG01:
Awesome how long will this ROM be supported with security updates roughly? To install security OTA patches is it done from within the settings app like on stock ROM on the Pixel 7a?
[Google Pixel 7a] chrisrg:
At least as long as google supports it which is until May 2028. Most likely longer. At the moment LOS is releasing weekly builds but obviously you can choose to download and update whenever from the system updater(can't remember exactly where it is but it's more straightforward than stock.
[Google Pixel 7a] EthanG01:
That’s perfect, thank you! So with the updates to the phone would they be in the phone settings app after flashing this ROM?
[Google Pixel 7a] chrisrg:
The updater should notify you an update is available for download. If you want to try it out just flash the penultimate build and when you boot up you can have a look. That's if your stock is not latest 5 July I guess. Just noticed July is out
[Google Pixel 7a] [-silver-]:
Hi there.

does the custom os pass the safetynet test? or do you have to work with magisk here?
[Google Pixel 7a] 306bobby:
Magisk Safety net Fix. You can follow my guide here. Very simple
[Google Pixel 7a] Zobat:
ignore
[Google Pixel 7a] wakkaday:
which version of gapps for pixel 7a
[Google Pixel 7a] mxz55:
I've spotted an old repo being actively used again by LineageOS maintainers, it's been used to upload a newer version of GApps than is present in MindTheGApps (e.g AndroidFileHost) mirror linked on LineageOS device wiki's

Here, im talking about: https://github.com/MindTheGapps/13.0.0-arm64/releases/

To be clear, you'll need arm64 for Pixel 7a, so in that link. Even though all other architecture repositories in https://github.com/MindTheGapps were updated equally.
[Google Pixel 7a] Zobat:
Hi all!

You can't change refresh rate on our device in lineage, correct?
[Google Pixel 7a] rogers11:
Thanks for the ROM, it's working really nice.
[Google Pixel 7a] nicknitewolf:
You can only increase it to 90Hz from 60 if thats what you mean.

Yes, MTG works best with Lineage.

Should be fixed in the upcoming build.
[Google Pixel 7a] mxz55:
@nicknitewolf

Thanks for maintaining this device, it works quite well and despite the topic not having much activity, I'm pretty sure there are a lot of 7a owners using it and grabbing the steady & weekly OTA's. Just like the family member for who i've configured it and is my source for the feedback on user experience.

Keep it up, and if you accept donations in crypto shoot me a PM!
[Google Pixel 7a] sumdewd01:
Does anyone know if Symantec VIP Access or Duo Mobile will work on this ROM? I have to use these apps for multi factor authentication at work and this is the only reason I hesitate to install a new ROM.
[Google Pixel 7a] godlich:
I followed this guide:

Install LineageOS on lynx | LineageOS Wiki

wiki.lineageos.org

to install lineageOS, but fail at

Installing a custom recovery using fastboot

at Point 5

I have Android 13, which I verified by:

>adb shell getprop ro.build.version.release
13

I always get:

>fastboot flash vendor_boot vendor_boot.img
target reported max download size of 261095424 bytes
sending 'vendor_boot' (65536 KB)...
OKAY [ 1.487s]
writing 'vendor_boot'...
FAILED (remote: partition (vendor_boot) not found)
finished. total time: 1.558s

I followed all the other steps.

These are the partitions with vendor in its name:

lrwxrwxrwx 1 root root 16 2023-12-04 11:16 vendor_boot_a -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 2023-12-04 11:16 vendor_boot_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 2023-12-04 11:16 vendor_kernel_boot_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2023-12-04 11:16 vendor_kernel_boot_b -> /dev/block/sda23
[Google Pixel 7a] Drizzt321:
So I'm trying to install Magisk on LOS20 on my 7a I just got. Running LOS20 just fine, I follow the instructions from https://topjohnwu.github.io/Magisk/install.html, get the apk installed, get the `boot.img` from https://download.lineageos.org/devices/lynx/builds, use the app to patch it. Reboot to bootloader, flash the magisk patched boot.img to boot, and flash the vbmeta as per directions. I reboot, starts up, Magisk still says it's not installed.

Any tips? I've installed it before on my Pixel 5a before it kicked the bucket, which is why I now have the 7a.
[Google Pixel 7a] 306bobby:
Rename magisk.apk to magisk.apk.zip and sideload it in recovery
[Google Pixel 7a] Drizzt321:
Don't see that in any official directions, and Lineage doesn't have any apparent directions for installing Magisk. Why would this work, and regular APK download/install + patch boot file from the App on the phone won't?
[Google Pixel 7a] 306bobby:
It's not there because those are old instructions/universal, and flashing isn't guaranteed to work.

You can try the solution, or don't ask for help

I've already made a guide for this device

And to answer your question better (which the guide also answers). This device needs init_boot to be patched. Not boot
[Google Pixel 7a] Drizzt321:
Wish the XDA search showed up for non-logged in users, I didn't notice it appearing after I logged in. Ugh. And your thread title doesn't say Magisk, which was the keyword I was looking for.

Thanks, I'll look at the guide in detail.
[Google Pixel 7a] 306bobby:
I'll add the tag for magisk. Apologies for that.

Sorry for any perceived aggression in the last post, xda developers is rapidly dying and trying to port and develop for new devices is hell with nobody who knows anything wanting to help anymore. Whenever easy solutions are asked for and seemingly ignored, it's rage inducing when dev issues I come across with go months without answer lol
[Google Pixel 7a] Drizzt321:
No, I do get it. It's such a PITA with the seeming decline of "I want to own my device" vs big companies "shove whatever we want down your throats and own all your data".

Also, should I re-flash the stock boot.img when I patch & flash the init_boot.img?
[Google Pixel 7a] mxz55:
@Drizzt321 Didn't read everything yet, but if you're still in a pickle, i got you covered, ill write a guide on rooting 7a with custom ROM later this week. But if you're tech savvy, i can boil it down for you in advance: its about extracting init_boot.img from the ROM's main .zip using payload-dumper-go, letting Magisk patch it along with boot.img that's much easier to attain - and flashing them back onto respectively the init_boot and boot partitions

For pixel devices, it tends to be init_boot.img that's most relevant to root, but for example on the LineageOS DL page it's usually not listed for direct & separate download.
[Google Pixel 7a] 306bobby:
There's literally already a guide about all of that lol, just using pixelflasher instead of payload dumper
[Google Pixel 7a] mxz55:
Just so you know, i cannot reproduce; last week by chance i had to do a family member's clean LineageOS install on 7a. First i used factory image to reset device to stock, even the latest Android 14 package so forth firmware, and then following all LineageOS for Pixel 7a installation instructions on the most recent LineageOS build resulted in a perfect, functional installation.

You must have made a wrong turn somewhere.
[Google Pixel 7a] Saswata Chakraborty:
It's been 24 hours I have been on this ROM and everything works flawlessly except Now playing which doesn't show the name of the song on the lockscreen but shows fine on the notification panel. I have disabled and re enabled now playing but it did not solve the issue.
[Google Pixel 7a] ALEX_ANDER:
Hi all!

Does this ROM support signature spoofing for using it with microG?
[Google Pixel 7a] 306bobby:
Should
[Google Pixel 7a] nicknitewolf:
Nope, install Lineage for MicroG instead (I don't support that though).

Use a newer version of fastboot, whatever you installed should be ancient

It could be your lockscreen settings for notifications?
[Google Pixel 7a] TecSnake:
I am on the latest stock update (A14, UQ1A.231205.015). Should I downgrade to install LOS 20 or should I wait for LOS 21?
[Google Pixel 7a] mxz55:
As i've confirmed here, the A14 firmware works just fine so you don't need to downgrade
[Google Pixel 7a] TecSnake:
Great, it is good to know. Thank you for your answer.

I thought that by following the wiki, you had also downgraded as asked in the warning ("Warning: Before following these instructions please ensure that the device is currently using Android 13.0 firmware."). Since you were successful going from stock A14 to LOS 20, I feel safer trying to flash it as is.

Is it safe to assume, when LOS 21 comes around, we will be able to upgrade to it from LOS 20 while keeping our data?
[Google Pixel 7a] mxz55:
There can be a component of luck, as it's just to say A14 firmware hasn't been tested by the LineageOS maintainer yet for LOS 20. But then, i tested it and it turns out nothing user-facing is behaving in unexpected ways for now. However, this means that it's not guaranteed for other versions of the A14 firmware than the latest package at the date of my writing, and that there may be silent failures that don't directly impact the user experience but can still result in lowering security, etc; until it's validated by the actual developer, it can't be truly recommended to use. It's also not my place to alter instructions given by the maintainer.

Personally i wouldn't be worried and just go with it regardless. It works, and on the other hand newer firmwares may have (performance or security) tweaks. Make your own choice while it's still unclear.
[Google Pixel 7a] mxz55:
For 95% of supported devices, LineageOS can be dirty flashed on a major version upgrade (text on the subject should appear on the wiki page for a device when it begins to support more than one major version). Even though one can give reasons a clean flash is better.
[Google Pixel 7a] itarill:
Hey guys, I'm wondering if this is a known issue?

Whenever I take a picture from one of the camera apps everything works as intended.

Whenever I take a picture from within an app that is making use of the stock camera api (e.g. gmail), I can see the picture on the screen, but no checkmark or X button to approve or cancel. This makes it impossible to use the picture taken.

How could I mend this? Lineage 20, clean install

Edit: this is literally my phone screen after I have taken the picture:
[Google Pixel 7a] nicknitewolf:
Updated thread to reflect latest official version. Should be feature parity hence no new thread was created
[Google Pixel 7a] rogers11:
Hello, is it me or is it a bug that Touch does not work anymore in Recovery since LOS 21? On my Pixel 4a it still works.
[Google Pixel 7a] Do Giang:
Does this version have face unlock?
[Google Pixel 7a] nicknitewolf:
Known issue, we are still finding a way to load touch modules in recovery without actually modifying AOSP behaviour.

Nope, face unlock has not been open sourced and exists within Google's custom SystemUIPixel which no one has reversed engineered yet.
[Google Pixel 7a] Do Giang:
Thank bro
[Google Pixel 7a] Shader123:
How can I get a screenshot back by tapping the back cover?
[Google Pixel 7a] Saswata Chakraborty:
I really really love LineageOS and you have done an amazing work here. There is literally no visible bug on LOS 20 and now 21. That's why even small issues look big here lol. Can you please have a look into the Now playing? I have enabled every possible setting but Now playing is still not appearing on lockscreen or always on display. It only shows on the notification area. I faced this on LineageOS 20 as well. I went back and forth and tried many ROMs but did not face this issue on any other ROM.
[Google Pixel 7a] archcry:
I recently went on a little adventure. I was running LineageOS 20 with MindTheGapps and everything was sort of fine. The only issue I had was passing basic and device integrity because Google is constantly banning fingerprints. So what I decided to do was revert back to stock firmware and give that a go. It did not take longer than a day for me to realize stock firmware is a piece of garbage with the pixel launcher and not being able to clean up the google search bar or "at a glance" from the home screen so I quickly decided to unlock the bootloader again and install LineageOS 21.

So far so good, I then had a phone running LineageOS 21 with MindTheGapps which I installed over stock Android 14 (meaning I had the latest google firmware before installing LineageOS). Now my problem is that I experience (in my opinion) excessive battery drain. Where previously I could go all day on a single charge comfortably I now experience my battery drained at 6pm (20% ~ 15%) with the whole night to go still.

I understand that this might be a bit vague so to get to the point of my message.

Is anyone else experiencing excessive battery drain on LineageOS 21 with MindTheGapps on lynx?

Earlier messages in this thread mentioned that previously the wiki mentioned that LineageOS had to be installed over stock android 13 instead of 14, could this be part of my issue?

Are there any tips and tricks to try in order to reduce the battery usage?

Is there anything I can do to help address this issue (if it is not user error).
[Google Pixel 7a] eng.stk:
If you use LOS Gallery app, it will stay forever generating video thumbnails and gridding battery on the foreground and background.

media.extractor then keeps at least 1 BIG core pegged and mediaserver locked, using 10~15% cpu always. Can confirm with top.

Seems like a major bug, happens on my lynx and oriole also,. Killing the gallery app doesn't fix it, you need to check with top if it's that processes eating battery up and kill it.
[Google Pixel 7a] veloz46:
The solution would be to disable the gallery?
[Google Pixel 7a] archcry:
I disabled the LOS gallery app because i'm using Google camera. I tried running top in Termux to see if anything was up but am I correct in assuming I should run top as root? When I run top as normal user I only see two processes.
[Google Pixel 7a] eng.stk:
Yes, that should work also.

But I hope they fix it meanwhile.

Well if you already disabled it, it should not trigger it.

To confirm the runnning processes you need to run as root ofc.
[Google Pixel 7a] archcry:
Looks like something is up with either com.adroid.phone or com.shannon.imsservice since they're hogging the most cpu resources. I investigated a little bit further and threads suggested it could be caused by VOLTE. I disabled that on both sim cards but the resource usage hasn't died down. Any suggestions?

Edit: I got rid of the high CPU usage of the above mentioned two services by disabling one of my two sim cards. I have a Vodafone e-sim and a Youfone fysical SIM. When disabling the fysical Youfone SIM I got rid of the two services hogging the CPU. Leaving the Vodafone e-sim enabled works fine. A short experiment shows that with the fysical SIM disabled battery life returns to normal. Any suggestions on what could resolve these issues?

Could it be faulty configuration for this SIM?

Could it be that there's a bug with the fysical SIM slot?

Could it be that is has to do with the ISP?

Edit 2: I now have the fysical sim card enabled again and found that whenever I set "preferred network" to 3G the two above mentioned services stop hogging CPU. Setting preferred network to either 4G or 5G instantly causes the two services to start hogging again. Kind of makes sense because as I read on the internet IMS features are related to 4G network (and above). If this is a bug in the software, how can I help to further debug this problem? I assume not everyone is facing this issue because it looks like it's only with some providers and/or only with fysical sim slots.

Edit 3: Looks like setting the preferrer network to 3G causes other issues as well. Not having great signal for example. I also notice that the IMS service was fired up upon getting a call as well hogging the CPU. I am kind of at a loss atm considering reverting back to LineageOS 20.
[Google Pixel 7a] archcry:
Might be related to this gitlab issue:

Battery Drain Issue After Upgrading from LineageOS 20 to LineageOS 21 (#6829) · Issues · LineageOS / issues / android · GitLab

Expected Behavior After upgrading from LineageOS 20 to LineageOS 21, the battery should perform optimally, maintaining a reasonable level of power...

gitlab.com
[Google Pixel 7a] mxz55:
If it's related to LOS upgrade, maybe wiping battery stats is worth a try:

adb root
adb shell

Enter to adb shell:
rm -r /data/system/battery-history
rm -r /data/system/battery-usage-stats
rm -f /data/system/batterystats-checkin.bin
rm -f /data/system/batterystats-daily.xml
rm -f /data/system/batterystats.bin
rm -r /data/system/graphicsstats

This procedure was researched by myself (based on modern versions of LineageOS, and at least applicable to it), but if i would post it as a guide for general use, it'll only draw criticism as the popular opinion is "Wiping battery stats is good for nothing". In this case though, maybe some A13 files are lingering in a way A14 can't deal with it, leading to issues?
[Google Pixel 7a] archcry:
For me personally it was on a clean installation. I first installed the latest factory Google Android 14 image using the Android flash tool completely reverting to stock. Then I followed the procedure laid out in the installation instructions to install lineage-21.0-20240301-nightly.
[Google Pixel 7a] luspi:
Just wanted to say Thanks! I switched to the Pixel 7a this week, and everything is working remarkably well and smooth. Also love the changes in Lineage 21 that allow me to run root and at the same time some annoyingly pedantic banking apps ^^
[Google Pixel 7a] appro77:
I have a really weird issue. I've installed LOS 21 on my 7a and it won't recognise the password for either my Google account or my partner's. Just tells me the password is incorrect....which it's not. I've tried several times with both accounts. Anyone have any idea WTF is going on?

I'm pretty sure this happened once when I installed LOS21 on my Pixel 4a5G not long ago but then it ended up accepting the password on the third try.
[Google Pixel 7a] mxz55:
That sounds very odd, the closest thing to rejecting valid passwords/codes in the Android ecosystem would be Keystore / Keystore2 / Keymaster / Keymint failure; a firmware mechanism present in all devices, involved in most cryptographic and authorization processes.

However, afaik that would surface most commonly as lockscreen, pin, failures.. not Google Accounts, as they should be performing a network traffic handshake between your device and Google services. I don't know enough about deep Android architecture to rule out keystore is also involved in the final part of said handshake, in case we're talking about the process of adding a Google Account to the device, through Android settings.

Long story short, that was the background, but practically if it's that, you or the build (or device firmware/build combination) may be suffering from a firmware issue. My concrete advice to you at this point will therefore be to use the Google Pixel stock firmware reset tool, and to make sure you reset it to the latest firmware and do a full factory reset, then install LineageOS.

If to no avail, consult with @nicknitewolf or this ROM (for Pixel 7a)'s other maintainer @mikeioannina so they can check the status regarding firmware support or any potential mismatches at the basis of your issue, or if perhaps a (firmware) bug has sneaked in, if my analysis is right.

If none of my thoughts are right, you should ensure nothing on your network or device is interfering with network traffic so that the Google Account login handshake won't validate. Test using another network. If you are definitely using the right password, I'd be technically baffled if there's not something funky going on, potentially outside of Android.
[Google Pixel 7a] appro77:
Thanks for the comprehensive supply. As you have suggested, it looks like my only option is to install stock, then reinstall LOS and see if that fixes the issue.
[Google Pixel 7a] mxz55:
Yes, while making sure you're fully updated to the latest A14 QPR2 build available, and performing a final factory reset while on that.

LOS for lynx is supposed to package and load the appropriate firmware by itself, but maybe a bug or addition/removal of certain firmwares in newer stock builds, made its way to mess this thing up.

Even though this issue, in all its oddness, screams "firmware issue" to me (trusting you're really not making a password mistake), i could also be completely wrong. This is just a guy, me, trying to explain something that sounds like it shouldn't be something that can manifest at all. Using the closest thing that comes to mind (firmware, through the Android 'key' structures from my last post). Or else network traffic related, something in your environment that can foil the Google Login handshake. Given that your failure isn't during a 2Fa stage but rather during password entry > "Login" button, system time/date also can't play a role in failure, it would need to be valid for 2Fa codes (with the secret key being time-based) only, therefore not applicable in your regular password scenario - so what'll be left besides network traffic if it's not fw? Nothing, probably. Unless of course there's missing information, like you are actually making a login credentials mistake, which again, im assuming not to be the case during these answers. I also gotta assume you're not the victim of unstable Google heuristics to flag & deny what their algorithm considers as suspicious login actions or other requests originating from an Android device. I don't know if such a thing exists and manifests within the Add Google Account prompt from Android Settings, but you never know these days in big tech landscape.
[Google Pixel 7a] appro77:
I got it working. It's even more bizarre than I thought. I reinstalled stock, factory reset, booted stock again, signed in to my Google account, rebooted to fastboot and installed LOS21.

Both my and my partner's accounts still wouldn't accept their respective password. He's the bizarre bit. Both of our passwords include the "-" and "%" characters. On Gboard I always switch to the number keyboard view and type those password characters from there. I was doing the same thing on the keyboard included with LOS and for some reason they weren't being accepted as genuine characters.

The reason I say that is that in desperation I tried using the alternate function of the main keyboard for those characters and the password was accepted....both on my account and my partner's. Unless I'm missing something glaring I have no idea why. I even typed both those character versions side by side, using the number keyboard and the alternate function on the main keyboard and they look identical.

I'm at a complete loss why both of those characters are not accepted in the password if they are typed from the number keyboard. I tried both characters separately from the number keyboard and both of them were causing the problem, not just one of them.

Any ideas?????
[Google Pixel 7a] nicknitewolf:
Which gapps package are you using?

Try using this:

Release MindTheGapps-14.0.0-arm64-20240225_232108 · MindTheGapps/14.0.0-arm64

https://gitlab.com/MindTheGapps/vendor_gapps/-/tree/d5f65a27eaa7f05276200c9b2dd41206097df998

github.com
[Google Pixel 7a] appro77:
That's the one I installed.
[Google Pixel 7a] gnarf49:
Hi Devs,

thanks so much for this ROM! Moved to Pixel7a yesterday after many years of Galaxy S10e (also LineageOS), and everything went perfectly fine. All smooth, no issues at all. Even MicroG "just works" now, thanks for that to the LOS team. :)
[Google Pixel 7a] xinouch:
Hello,

I want to instal LOS on my 7a, but up to now, I always used TWRP recovery. Do you know if this is available for 7a? (can't find it). Should I give up TWRP for the LOS recovery?