yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
@andrepd So I understand there are various options for enabling signature spoofing on any ROM. There's NanoDroid patcher, there's an option with Xposed or whatever its current reincarnation is, and there are the Needle/Tingle/Haystack scripts. Five years ago I ran microG and used Tingle to patch my ROM, which worked fine for me. Can you explain to me the advantage of having signature spoofing pre-enabled in the ROM?

@BWRainbow I have no experience with custom kernels. I've looked at some custom kernel threads in the past but it has always remained vague to me what the advantage of them would be. I would be interested in reducing power usage during standby, is that something a custom kernel could do? My current battery life is 2-3 days on average, with most of the time spent in standby.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] BWRainbow:
@icantlogin I was asking for that same reason: I have no idea of what are the real advantages of a custom kernel :D. Let see if somebody else can help us.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
This month's build includes a patch for a vulnerability where anyone with physical access to your phone can bypass the lock screen within 1 minute by plugging in a SIM-card, entering the wrong PIN for that SIM three times and then entering the PUK-code for that SIM and setting a new PIN. Try it before updating if you like...

Yesterday I happened to stumble upon this article by one of the people who reported this bug to Google earlier this year. Seeing him easily bypass the lock screen in the included video was kind of terrifying. It really drove home to me why we update. Imagine how long this has been possible... at least since Android 10 (older versions aren't supported by Google), which also received the patch.

Makes you wonder what kind of vendor patches we are missing out on by not upgrading to Android 12/13 and now being more than a year behind 😭
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] BWRainbow:
I was going to talk about that vulnerability some days ago but didn't want to pressure you (as, in my case also, it's very hard for that to happen to me).
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
Thanks for making this! I'm trying to follow this step:

However, when I try to do this from the Apply from ADB menu, or alternatively flashing in fastboot, I get failures. For the ADB approach, it seems to start, but ends up at E:Error in /sideload package.zip (status 255). For the fastboot approach,

unknown partition '.\open_gapps-arm64-11.0-aroma-20220215.zip'

fastboot: error: cannot determine image filename for '.\open_gapps-arm64-11.0-aroma-20220215.zip'

Is there some other way I can flash GAPPS?

Thanks again.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
Seems like it's the same issue as this: https://gitlab.com/LineageOS/issues/android/-/issues/2074

I choose "yes" when the verification fails, and then I get the (status 255) error
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
Update: Aroma gave me those errors, Stock gave me space errors, but Pico worked fine. Seems like a LineageOS recovery issue (TWRP has always worked fine before with the others, albeit on my old XZ1 Compact).
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
Alternatively you could try a different Gapps, i.e. not OpenGapps. I myself am using NikGApps. There's others as well.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
I have a new issue where I can't sign into any Samsung apps. My other Pixel 4a running Stock 13 has no issue. 3 apps display the issue differently: Galaxy Wearable goes to a white screen, Samsung Health gets a permanent spinning wheel, and Smartthings freezes. I am able to sign in via browsers, and Samsung Internet comes with Android Account integration, and that works. The other 3 have to go via a browser, but the apps fail to redirect. I have tried with Chrome, Samsung Internet, and Lynket.

I'm assuming something is trying to connect to Samsung and can't and so it doesn't proceed. I tried uninstalling Adaway and that didn't help. I also hid the Magisk app and that changed nothing.

Is there a log I can access somewhere to see what might be hanging/blocking?

My XZ1 Compact had the same set up (18.1, Magisk, etc) and I could sign in.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
You can run logcat in an adb shell to see informational, warning and error messages i.e. see what's going on behind the scenes. There are arguments you can use to filter the output.

Are you using a VPN provider by any chance? If so, have you tried turning it off before signing in?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
OK, so I was able to sign into Samsung Health! Here's what I changed, based on those logs:

I uninstalled Lynket. I don't think this mattered, but it was easy to do. I'll try installing it again and see if that changes anything.

I stopped the service for an app called Advanced Charging Controller App (AccA), which is not an app that existed on my old phone. The clue for this was all the random calls to battery in the logs, which made me think maybe it was interrupting Samsung.

I think it's the 2nd one, though the first is browser-related and given Samsung's hardcoded method for whitelisting only certain browsers (Lynket should work because it's just Chrome via Chrome Custom Tabs, but Samsung blocks it), it might just be Lynket.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
Can confirm that Smartthings and Galaxy Wearable are both working, too. I haven't tested which app is the issue (I'm afraid to irreparably break it again) but will follow up here if it reoccurs. It's definitely one or the other!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
Maybe Lynket was still set as the default WebView implementation in Developer Options before you uninstalled it. Next time try changing that option to Chrome or Android System WebView. Anyway, glad you solved it. And that you learned to use logcat; it's really useful to get a clue in these kinds of situations!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ToddBonzalez:
Interesting. I didn't realize you could change that. I did check just now and only Android System WebView is an option, but maybe Lynket was there before I uninstalled and reinstalled it?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
I recently ran into an artificial limitation built into AOSP. The default maximum lockscreen password length is set to 16 characters, which is ‘kind of arbitrary’, as the accompanying comment in the source code says:

/**
* Maximum supported password length. Kind-of arbitrary.
* @hide
*/
public static final int MAX_PASSWORD_LENGTH = 16;

From what I understand, this value is simply checked when setting a lock screen password, and if the new password is longer it is rejected. Organizations can set a different value for their managed devices through Android Device Policy, but regular users are stuck with it.

From now on, I will change this to 64 in my builds, which should accomodate any sane password or passphrase length, and about covers the maximum static password length supported by hardware tokens like the YubiKey and OnlyKey. GrapheneOS does this too by the way.

It's probably not a concern of many and I'm adding this tweak for my personal benefit, but if you ever wanted to secure your phone with a decent passphrase or long random string of characters stored on a hardware token, now you can.

Happy New Year everyone!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] betacrypt:
Just d/led the Jan build, runs great. Thanks for continuing to work on this into the new year.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
Loving the rom👍

Thanks for keeping it updated 🙂 @icantlogin
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
How's the battery life for you guys back on A11? I'm on stock A13 and since a few months battery life has got veeery bad. I'm thinking of factory resetting or going back to A11 which was heaven in comparison to 13. Does Gcam work fine here?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
@icantlogin Thanks for the February update 🙂👍
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xneuromancer:
I did a wipe and clean install last Friday, battery life has been perfect on my 2+ year old 4a battery. I'm coming from A12, now back to this build of A11.

The only thing that is not working is finger print gestures. However, this is some sort of issue or limitation with all ASOP roms, not this ROM version specifically.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
If you're talking about Settings > System > Gestures > Swipe fingerprint for notifications, it works just fine for me when turned on... are you sure it doesn't work for you (it might be turned off by default), and it does work on your phone with the stock ROM?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Thank you! I've updated to latest monthly A13 stock rom, after factory resetting, with no luck. Battery life is still so poor, so I think I'm switching to LOS.

@icantlogin Just a curiosity, are you planning to release every monthly update? Not to bother you, since you're already doing a great job, but I'm just trying to decide whether to downgrade to stock A11 first and test it for some days or go straight to your LOS release... :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xneuromancer:
Just go to this version.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xneuromancer:
I use Digilux to control backlight brightness. However it doesn't work in AOSP. I googled around and I found a few answers saying fingerprint gestures don't work on AOSP.

thanks for reminding me of this setting though. This is working at least :-⁠)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
Ah, I didn't know there were apps that let you customize fingerprint gestures, that's pretty cool! Shame it doesn't work on AOSP then.

I use Edge Gestures by the way, you can set it up so you can adjust brightness by sliding in from a screen edge and then pulling up or down - I use it all the time! I also use it to open quick settings by swiping down on an edge, which I find more comfortable than using the fingerprint scanner on the back.

@ZioRò I've been publishing monthly updates since August, usually within one day of LineageOS integrating the montly security patches. They've started working on this month's patches last Wednesday, so a March release is in the pipeline...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Thank you! In the end I decided to go straight to your LOS release and so far so good.

Are you guys using any custom kernel?

Only thing I'm missing from stock Android 13 is the one handed mode, is there any way to implement it?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
Even better than Android 13's one handed mode (in my opinion): Quick Cursor. Makes the whole screen reachable by giving you a sort of mouse under your thumb that operates a cursor in the upper half of your screen. When you bump it into the upper edge it will pull down quick settings for you, and you can configure it with 'zones', e.g. left half of the upper edge opens notifications, right half opens quick settings, that kind of thing.

Edit: operating a "mouse" on your smartphone maybe doesn't sound like fun, but once you try it... well, read the Play Store reviews! It's the best thing ever, couldn't live without this app (or one like it).
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Thanks for the hint, I'm going to test it out!

By the way, after 1 ½ days into LOS everything is fine. Battery life seems better than stock (quite better than A13 for sure), but I need to test it for a few more days. One thing I noticed is that LOS seems to have fixed the issue of my iPad not able to connect to my Pixel's hotspot, regardless of the WiFi band I used. Very odd it was...

Edit: One more question, is there any way to get back Google phone call filter? I'm using Google telephone app, but it seems vanished :(
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Do you guys know what's that process keeping phone constantly active? That's such a long wakelock time and it drained quite a lot of battery... I didn't make any backup and I couldn't think of anything doing it in the background for so long 🤔
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
Got about an hour extra screen on time with March update 🤩 also scrolling seems much smoother than February update

Thanks @icantlogin 👍
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Thanks for the latest update, working fine so far!

By the way, I managed to re-enable Google Phone's call filter, I just needed to systemize the com.google.android.dialer as priv-app and reboot. Very useful feature for spam and robocalls.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
Edit: Double post by mistake.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] VV6666:
With LOS20, there's a tactile bug: multitouch management (pinch to zoom, pinch to rotate, etc.) no longer works.

Any problems with your LOS18-based version?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] VV6666:
I'm answering myself because I've just tested it. I installed your version over rom stock android 10 directly. Because the bug appears when switching from A10 to A11 (https://xdaforums.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/).

I lost the use of multitouch ....

Does it work for you?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
I never had any issues with that. I regularly use it to zoom in on maps and photos, that's what you mean right?

It could be a firmware issue. If you flash the latest official Android 11 ROM from Google (as linked in my first post) and then this ROM, fully wiping the device, no Gapps and addons, do you still have this issue?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] VV6666:
Yes, that's exactly it. I can't zoom in, for example. On this forum, there are a few users who have encountered this problem.

I tested it with the factory rom you suggest. It doesn't work any better.

I'll try to get the warranty to work.

Thank you for your reply.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tM&M:
Thank you for this ROM. Builtin updater is also a blessing!

Works faster than A13 and looks much better too. Top quality port, even Widevine L1 works!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
when you say "over rom stock android 10 directly", did you dirty flash?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] VV6666:
What I mean is that I didn't upgrade to Android 11 before installing LineageOS.

But then, I also tested over the A11-based rom proposed at the beginning of this topic, to get the same result: no correct screen support.

In any case, I sent the phone back to the after-sales service. They'll send me a new one. I hope I won't run into this bug again.

On another topic on XDA, I understood that the problem came from Google's setting of the touch screen and that it only affected a few phones. A production run probably, so a few thousand.

Thanks for your answers.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheNathan:
Hi, great firmware, but the only reason I can’t use it is that I can’t use the NFC, I can’t add a card because it’s a modified software.

Will this be fixed in the next update?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ZioRò:
You need to flash magisk, then activate zygisk and put Google Wallet in zygisk list, then reboot. If needed clear Google play services and Google Wallet data.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheNathan:
yes, I know, but on other current A13 firmware, the wallet works without such additional actions, I want it to be the same for this.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
I don't think so. LineageOS are not actively working on the 18.1 branch anymore, just implementing the monthly security patches.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
How's everyone doing on Android 11? Seems like an ancient version to me now, since I made the switch to Android 13 two months ago! I have to say I had no adverse reaction to Material You this time and surprisingly I've even grown quite fond of it. The extra whitespace, the big headings, the pastel colors... not an issue anymore. It even seems calming in some kind of way. And some things I really like about Android 13 over 11:

Gesture navigation FINALLY works fluid with 3rd party launchers

No more tapping ‘Advanced’ in every Android settings screen, all settings are visible by default again, hallelujah! (This "feature" annoyed the sh*t out of me, if you can't tell.)

You can choose to only share your approximate location with an app if it doesn't need your precise location

You can set language per-app

13 also seems to be a huge improvement over 12, from what I have read. One thing I remember from testing out Android 12 was that the battery usage graph had been even further simplified, providing almost no utility anymore. In Android 13 they've actually made it more feature rich than in Android 11, it's now akin to how iOS does it. (Not that it's good enough to stop me from using GSam Battery Monitor and Simple Battery Graph...)

They may also have added some saner color schemes in 13. I can just have black text on a grey background in Settings now. I seem to remember it was all pastel colors with low contrast on 12.

Anyway, for you Android 11 dwellers the August update is being compiled right now and will be available in a few hours. Hope you enjoy it!

p.s. Do you plan to upgrade to the latest Android version sometime or will you stick with 11 for the rest of the time you use the Pixel 4a? What would be your reason for upgrading or sticking?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tM&M:
Hi!

Thanks for the hard work, been really happy with this ROM. It has been top 3 I've used, can't seem to find bugs, battery doesn't drain, performance is quite good, etc.

If 13 is better, I still plan to use this for a while, at least until bugs get sorted out. I have never had a good experience with versions that are less than 1 year old, be it stock or Lineage OS.

That said, I will eventually switch when 11 loses security patches (not sure if Sept or later).

My experience with 12 is that it is much slower than this, which is one of the reasons I wanted to try a previous version, as I was quite happy with how Lineage 18.1 had turned out on my older phone. As like you, I was also very turned off by the cumbersome user interface changes.

Since Google is also going to remove support soon, trying this ROM a couple months ago was all benefits as far as I was concerned. It turned out much better than I expected!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] old.splatterhand:
I have a second Pixel 4A where i have Android 13 on it.

I still think that Material You is ugly as hell (especially the quicksettings), but with crDroid 9.x i can adjust the most parts of it in a way that i can live with it.

That's why i plan to migrate to it in the next few weeks.

All in all crDroid seems to me the most customizable Android 13 rom for my needs.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
O wow, crDroid looks really good! All the tweaks LineageOS offers and more! I was just thinking to myself this week: ’I wish I could disable the exclamation mark on the signal strength when mobile data is disabled.’

crDroid: You can. 😃

Looking at the screenshots also makes me realize I miss media cover art on the lock screen, as I'm currently on the stock ROM. Which will probably only receive one last security update in the next 6 months, so I'll definitely switch to a custom ROM again at some point. I see @DiamondJohn is doing the Lord's work making crDroid available for the Pixel 4a 🙏🏻 Guess I'll try his/her/their build in te future.

Regarding Material You, Quick Settings and customization, there are ROM-independent options, some of which require root or Shizuku:

Better Internet Tiles Separate wifi & data tiles.

Fabricate Overlay Customize QS panel (and any part of the interface really, if you can find the right settings, but it's really cumbersome to use; tutorial here).

Project Themer (Play Store only, €) Customize QS panel with much better interface, also customize Material You colors; haven't tried it myself.

Dark Mode Live Wallpaper Also lets you customize Material You colors.

Repainter (Play Store only) Customize Material You colors.

Just using crDroid definitely seems the easier route though! Will check it out.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
To be clear, my crDroid build is the latest Android 13, not A11

Also, since you are building LOS, you may wish to also build your own crDroid. I have my changes to enable it and the local_,manifest all in the thread, so it shouldn't be any issue for you.

https://xdaforums.com/t/rom-unoffic...crdroid-v9-7-with-gapps.4593649/post-88763057

https://xdaforums.com/t/rom-unoffic...crdroid-v9-7-with-gapps.4593649/post-88816773

https://xdaforums.com/t/rom-unoffic...crdroid-v9-7-with-gapps.4593649/post-88822105

You may get some kudos, as many people hound me for a non GApps version. I also do some minor tweaks that move away from a stock crDroid.

Another build that may interest you is the RisingOS build. I dont use or test the builds, and only perform builds as a favour to users who prefer it over crDroid (I built & released it before crDroid, so didnt want to leave people in the cold). However, I think it gets more than twice as many downloads as crDroid! I have listed my reasons for preferring crDroid in the thread.

https://xdaforums.com/t/rom-unoffic...w-very-customisable-rom.4592521/post-88763499
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] old.splatterhand:
After one week with Android 13 i'm back on Android 11 again.

There are several reasons, which are in detail:

- I use pattern as screen lock and while on 11 almost every attempt works, i get constantly wrong patterns on Android 13 (the line is some kind of thicker as on 11). This gets pretty annoying after a while.

- I hate the notification dot in statusbar, which is disabled on the 11 build i use. But on 13 it isn't and i haven't found a way to remove it. As i use my clock, wifi, battery, network traffic on the right side, like in old times, the dot does always come and go, but i want to decide myself if i see all those stuff or not!

But the most problematic things are my smartwatches:

- I don't get my Huawei watch connected at all! It shows "Connected" on the watch and on the phone but i can't synchronize my daily steps or fitness data, or watch my workouts in Huawei Health.

And while the watch was disconnected to my 11 phone, i was able to connect it again in a few steps.

- My WearOS watch i was able to connect to the 13 phone, but after a few days it said on the watch i should do a reset and reconnect to the phone. And in the WearOS app on the phone it was like there was never a watch connected... I could solve that with my PC but what can i do if this happens again, away from PC?

This are things i'm not willing to waste my time right now, because all those problems do not exist on my phone with 11.

Maybe i try it again, when i had to do a reset on the watch, but right now, i'm done with Android 13...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xneuromancer:
Staying with this build since the battery life is great (and I don't have time to re-do rom installs).

Hope you keep publishing updates.