yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I'd like to thank @fbievan for providing log information for the VVM error.

I'd like to thank @razorloves for working on a fix. Razorloves has already provided the work to the Android project. Let's hope all goes well. All of razorloves' work is greatly appreciated. :)

Razorloves was kind enough to let me try the fix on my phone. Since it's working for me, I asked if I could share it here. I thought others who have stayed on LOS18 might want it.

NOTE: I updated to the Apr 14 2022 build of LOS18.1 before trying the Dialer.apk. This was so we could see VVM work on Mar 10 build, then fail on Apr 14 build, then work after updating Dialer.apk.

I've attached "Dialer.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.

To try this fix....

Enable USB debugging in your phone.

Enable ADB root in your phone.

Use these adb commands....

'adb root'

'adb remount'

'adb shell ls -l product/priv-app/Dialer'

--you should see the Dialer.apk file is from 2008

'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'

'adb shell ls -l product/priv-app/Dialer'

--you should see the Dialer.apk file is now from 2022

reboot your phone.

If you find their work useful, don't forget to support all their work. :)

https://paypal.me/LineageOS

https://patreon.com/LineageOS
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
Anyone planning on building this ROM themselves, now lineageos.org has moved to 19.1? I don't care much for Android 12 myself, I plan on staying on 11 for now. I've build LineageOS in the past for another device, I might give it a go again.

If I build it myself and want to share it, would I post it in this thread or create a new one? It wouldn't be an official build anymore, would it?

Anyone else planning on staying on LineageOS 18.1?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
I think you'll have to create your own thread for that.

If you don't join LOS to become an official maintainer, then no, it won't be an official build anymore.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
The thread title would be in opposition to your build, so you would definitely need to start a new thread. Also, most important details and links to new builds are posted in the OP, which you would not be able to edit unless its your own thread. And its just respectful to the orig dev.

I dont use LOS on this device or plan to. I am tempted to stick with A11. I am still running the stock A11, I too have built multiple ROMs for my previous devices (oreo being the last), but am hesitant at building for this device in case there are any "gotcha's" after spending hours building the env/source etc. I would be interested in following how you go (y) . I havent seen too many details published for building ROMs for this device. Actually, I just realised I have not checked LOS web site, previously they had pretty thorough steps details on building their ROMs for official devices.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Updating to LOS19...Signature verification failed

I tried to update from LOS18 (04-14 build) to LOS19 by following directions here:

I got a long list of errors about reading certain bytes.

Then it said signature verification failed.

I was wondering if anyone could shed some light on the problem. Thanks.

These are the steps I took:

.Downloaded lineage-19.1-20220602-nightly-sunfish-signed.zip &

lineage-19.1-20220602-nightly-sunfish-signed.zip.sha256

from https://download.lineageos.org/sunfish

."sha256sum -c lineage-19.1-20220602-nightly-sunfish-signed.zip.sha256"

--It passed with "OK"

.Plugged phone to PC

.Enabled USB debugging in Settings->System->Developer Options

."adb devices"

* daemon not running; starting now at tcp:5037

* daemon started successfully

List of devices attached

0445199C201DEW unauthorized

--On the phone, clicked on popup to authorize.

."adb devices"

List of devices attached

0445199C201DEW device

."adb reboot sideload"

--My phone rebooted to LOS recovery, ready to sideload.

."adb sideload lineage-19.1-20220602-nightly-sunfish-signed.zip"

--Phone gave many errors and then said

signature verification failed. Install anyway?

I said 'no'
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
Say 'yes'
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Updating to LOS19...Success!

Hmmmm...

I ran through the process again. This time....

."adb sideload lineage-19.1-20220602-nightly-sunfish-signed.zip"

Supported API 3

Finding update package...

Verifying update package...

Update package verification took 50,5 s (result 0)

Installing update...

Step 1/2

Step 2/2

Install from ADB complete (status: 0).

.On phone, I clicked "Reboot system now"

--Phone rebooted in about a minute.

--VVM works on LOS19. (y)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
what did you do differently?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I changed nothing. I took the exact same steps both times. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
I remember reading it in some other thread that this "signature verification failed" can safely be ignored as long as you know what you're doing. ie: you have downloaded the correct ROM for your device, from a trusted site. Since he said that the checksum checked out (pun intended), there isn't any reason to care about the signature verification.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Yeah, I read that also, and I think you even commented once on how I said that I read that exact thing.

However, @mangokm40 actually may of detailed how to correct that in his previous post (y)

https://xdaforums.com/t/rom-official-sunfish-lineageos-18-1.4255751/post-86974617

That is the first time I have seen how to do it (havent tested it yet), and i had searched the internet, and it now seems so damn obvious.:geek:

Connect the phone via USB and click the authorise on the screen. I always use adb over WiFI, which obviously is a different authorisation, and it always came up as unauthorised when I went into recovery, where there is no UI to click on an authorise pop-up.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
June 2 lineage 19.1 update fails, just fyi for the maintainers or anyone else trying it out.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Worked for me
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
Thanks man, I will try it again, I even tried to adb sideload it and it failed, gonna try the updater again, the first time it hung up for 30 min after the download.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
You could check the file-sum of the download (although the updater should do this itself).
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
Yah it succeeded with the check in the official updater. Going on about an hour now updating.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
Ok so it just took a very long time but finally completed, I appreciate the help as I was really looking forward to the removal of the gps icon every few minutes.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
It takes an hour or sometimes two on my devices P3a/P4a
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
In my experience, if you don't click on authorize, you won't be able to execute any adb commands at all.

I always use it wired, so I always check the checkbox that says "remember this computer" when clicking authorize.

I have only experienced this "unable to verify signature" thing once on the 4a, but I'm like 99% sure it's got nothing to do with the adb authorization being allowed or disallowed. Isn't it about the ROM zip being signed correctly?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Thanks to razorloves, I discovered caffeine updates.

This was in LOS18...

I used updater to download update.

I used the QS tile to set caffeine for 30 minutes.

I clicked 'install' in the updater and it took only 10 minutes!

Also, I started this thread:

https://xdaforums.com/t/discussion-of-official-lineageos-19-1.4450095/

I thought it'd be good to keep LOS18 info separate from LOS19.

If it's better to just use this thread for both, let me know. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
So if the screen isn't on, the updater doesn't work in the background?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I can't speak of details. I'm uninformed.

While I was testing the VVM fix, I had to update from LOS18 03-10 to LOS18 0414.

Each monthly update I installed through the updater took about 90 minutes.

It was not an issue for me, because the phone works just fine while it's updating.

User razorloves mentioned that I could use the 'Caffeine' QS tile. He estimated the

update would take about 8 minutes, after I pressed 'install'.

He was right. :)

I shared that info above, in case it's useful to someone.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
But I assume you weren't actively using the phone for 90 minutes?

I guess my question is: if you press update, and use your phone actively for about 8 minutes, does the installation complete in/under that time, or does Caffeine seem to 'magically' speed up the update process?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
Can someone please upload the last build for this(18.1)🙂

I can't find it on the official website
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
LineageOS Downloads

download.lineageos.org
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
These are all 19.x builds though. He was looking for 18.1
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Oops, sorry.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] hammered58:
https://mega.nz/folder/dx8xySZK#a0OIpcpAN3cO4xXSmcc63g
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Is this what you are looking for? I did not test the download.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
Thank You :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mihail1:
VoLTE runs on this rom in unsupported countries?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] wireroot:
You already asked this question 6 months ago, received an answer and nothing has changed since then.

In the official Google support forums you will find many threads dealing with this problem (no solution) like this one.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tokone:
Hello, can someone please upload the last build for this(18.1), last is expired :(
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] hammered58:
File folder on MEGA

mega.nz
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
You pointed me in the right direction, the LineageOS wiki has solid instructions. I've been figuring out how to use a virtual machine in Google Cloud the past few days, as my laptop is not sufficient anymore. It worked out very well, I produced my first build yesterday, on my first try. Now I'm figuring out from the wiki how to sign it with my own keys and after that how to migrate a phone from the last official build to my own build without losing any data. After that I'll figure out how to upload it to Android Filehost or Google Drive and share it on this forum :) If I don't suddenly lose interest this might be pretty soon, if I do lose interest it might be weeks before I come back to this haha 😅 We'll see.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tokone:
Thank You!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I have only built for unofficial/unsupported devices, so signing with a matching key to the official one wasnt ever a question. It does sound like something LOS would not want you do. ie release a kinda official ROM as a random unofficial outsider/builder. It peaked my interest, so I found

Signing Builds | LineageOS Wiki

wiki.lineageos.org

Maybe to keep your interest, when I was building, I would take custom ROMs and do relatively easy things like: debloat, replace standard apps with better FOS alternatives, add CPU Govs and IO Schedulers, add theme colours. I also use to overclock my basic low powered device.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
There's no "signing with a matching key to the official one" since that key is secret. I'm following the instructions on the page you linked to sign my builds with my own private keys and then migrate from the official build to my own build. Since the LineageOS project doesn't provide official 18.1 builds anymore, I'll be releasing them as unofficial builds to help those who, like me, want to stay on 18.1. I don't think that violates any rules.

Ah yes, once you're comfortable compiling a ROM I guess you can then venture into customizing it. My sole intention is to be able to generate LineageOS 18.1 builds with the latest security patches though.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I was pretty sure the LOS key was private, but wasnt 100% sure, so didnt want to stick my neck out, any more than an implication ;).

Regarding signing, from memory, in the "good old days" of flashing TWRP compatible zips, I *think* the check for the correct/same signature was easily editable within a text file (the install script) in the flashing/install zip, and hence could be modified to be ignored on the first switch, and then updated at the end of the first flash to the new key, ready for the next flash with the new signature. I have not investigated if the same trick could be applied to the current non TWRP flashing process.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] maclick245:
Is anyone experiencing bad internet connectivity on this ROM?, I have had same issue on Descendant as well. The only ROM I get stable internet on is SuperiorOS. Any assistance would be appreciated!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
So I was just wondering, is there going to be a support thread for the official LineageOS 19 for sunfish or...?

Not that it's very relevant to me, I'm hoping to create a thread soon for my unofficial 18.1 build with August security updates. I've got hosting figured out and I'm working on implementing OTA updates through the system updater so it's gonna be a real smooth experience once one has switched :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
19.1 official works well, why maintain 18.1?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I created this thread a while back. It's in the discussion section b/c I am not the ROM developer.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
O, the irony of buying a Pixel phone for stock Android and monthly updates, only for Google to go ahead and change the whole UI with Material You just months after I bought it—and I think it's terrible. Of course I could get used to it—we usually resist change before embracing it—but after testing Android 12 a bit and switching back to Android 11 it immediately struck me that it looks só much better. Like a breath of fresh air after Android 12. Usability is so much better.

So that's my reason. My hope is they will bring back brighter colors and more contrast in Android 13 or 14 or something, and maybe shrink the giant headings somewhat, and I'll switch then. We'll see.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I am running Bliss, but have stuck with A11 and not moved to A12. I have a lot of apps which are no longer maintained (and most pulled from the playstore), and barely run on A11. Im not going to switch to A12 anytime soon . AND I haven't been impressed with the general look & feel of A12 in the vid's I have seen. So I can understand why someone would prefer A11.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] old.splatterhand:
A12 is ugly as hell and so i'll stick to A11 as long as needed! Also Bliss 14 in my case.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Oswald Boelcke:
It looks like LOS 18.1 is no longer officially maintained for Sunfish:

Info about sunfish | LineageOS Wiki

wiki.lineageos.org

LineageOS Downloads

download.lineageos.org

If you're not interested in an upgrade to 19.1 but still want to receive updates to 18.1 you might want to have a look into the "unofficial" LOS 18.1 thread by @icantlogin

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] LionDGem:
I wonder too. For me the updater does not work. Hope to find some help there
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] LionDGem:
Now the touchscreen stopped working properly. Hope this is no hardware issue o.O I am on the second to latest update LOS 19 for sunfish.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
As you can see in this thread, I am using the updater on LOS19. I've had no problems.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Just in case nobody has noticed: there is a LOS 20 now for the 4a and it works as expected.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Helvenhel:
Hi! Can I immediately install lineage 18.1 with android 12 or first should I install 11?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] AkumDX:
11 first
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Hello, since this morning (update 20.0-20230824...) I can no longer make or receive calls. Calls are terminated immediately. Callers get the message that I am not available. However, data works.

The whole thing is happening with Vodafone via eSIM.

Am I alone with this sudden problem?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] badtlc:
Is there a trick to get LOS 20 to be a certified device? I can't figure it out.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] artu72:
I am considering to install LineageOS on my Pixel 4a since the official support by Google is now ended (no more updates, in particular security ones).

However, there are some features on stock Android that I am not sure I will find on LineageOS:

1) ASHA support. I have a cochlear implant and I use direct audio streaming to phone. In order to it to work, phone must have ASHA ( Audio Streaming to Hear Aid, https://source.android.com/docs/core/connect/bluetooth/asha?hl=en ). This is present in stock Android, but I am not sure that it will be enabled in LineageOS ROM also.

2) Google Camera. Is it possible to install? On stock Android it is a definitive photo app, and I love much it.

Thank you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I am running A13 crDroid (LOS based), I was shocked that when I installed GCam (is that what you mean?) that the "Magic Eraser" worked. Its all over the ads for the latest Pixel devices, and I presumed they would explicitly of limited/blocked it to only work with the newest devices. Kind of a big advertising/selling point here in AUS, and thereby reason to upgrade; but no.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
@DiamondJohn Magic Eraser was introduced a year or more ago. Pixel 4a has had it for a long time, and I'm not sure it's still limited to just Pixels these days. It's a feature of the Google Photos app, not of Google Camera. The newest Magic Eraser functionality promoted now (moving subjects around) may only be available on supported Pixels though, or can you also do that? Edit: actually, I'm not sure if that's new either, I remember they promoted being able to move a bench or someone on a bench in a picture, but I don't think that feature made it to the 4a.

@artu72 I'd never heard of a cochlear implant before, pretty neat technology! Since I never dealt with it or read about it, I don't know if it will work with LineageOS, but I see no reason why it won't. It might require installing Google services (GApps) and accessibility apps though, which are not included by default.

Google Camera can just be installed on any custom ROM from the Play Store or an otherwise obtained APK. Same applies here: it might require installing Google services. I know it works with but I've never tried without. Also, Google Camera is not Google Photos, they are separate apps, although they integrate well with eachother.

You are posting in the thread of the somewhat abandoned (i.e. no official builds are published anymore) official LineageOS 18.1. There's a discussion thread for official LineageOS 20 here.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
yeah, I noted all that, i was just in total shock when it worked on my phone, while in the TV ads its all attributed to the "special google camera" wuth the implication its only on the latest Pixel devices.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vildevilde:
How to get rid of or uninstall Seedvault? Every day I get on or two notice that Seedvault failed. I don't want any auto backup on my phone.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Clear (Data & cache), Disable & hide. STandard android shell commands.

Its wrapped in my app I distribute here on xda. TeMeFI
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vildevilde:
How do I do that? from where? Hmmm, that will restore my phone completely or?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
you are only doing the action on the single package not the whole device.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vildevilde:
"you are only doing the action on the single package not the whole device."

Thanks, then I believe I have to do it via adb,android shell, but then I need to know the command's and the package name(s). I can't do that without exact commands, I'm not that good at this.

If I'm able to do it, will it come back every update?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
This shouldn't be happening with default settings. Try to disable the Seedvault backup from settings or change the backup provider to Google. On LineageOS 18.1 these settings can be found in Settings > System > Backup I think (you may have to tap Show advanced options first after getting to System). Otherwise, use the search feature in Settings to search for backup or seedvault. Good luck!

If you want to do as DiamondJohn suggests then you need to execute the following command from adb shell:

pm uninstall --user 0 the.package.name

It will not be re-enabled by updates.

You might be able to find the package name with:

pm list packages|grep -i seedvault
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vildevilde:
I have already done that, Seedvault is disabled and Google.... enabled. but I'm not logged in on Google on my phone. Seedvault still is getting me the failed message.

I will try the shell commands....
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] vildevilde:
OK, did it, thanks :)

" root@vilde-master:/home/vilde# adb shell pm uninstall --user 0 com.stevesoltys.seedvault

Success

root@vilde-master:/home/vilde# "

And now there is not any Seedvault as option in backup............
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
And hence the App I linked to providers a GUI and builds & runs the commands for you. But, you have already managed to get what you want, done. When I built the "compound" method, I found that only disabling a package, still somehow left (a small part) it in / consuming memory. It was only when I also Hid the app, it was no longer in memory. Also, not clearing the data & cache beforehand, leaves dead data / wasted space on your device.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] starbright_:
Is esim supported by LOS ?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Yes