yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zman519:
It really sucks that we don't have a fully working TRWP No VVM is a good reason to restore a backup if we could even make one:(
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Similarly...I couldn't figure out what happened to visual voice mail.

I tried to boot from the other slot, which I figured would get me back to

02-17. Obviously, I don't know what I'm doing. :) I also wound up with the LOS boot animation 4ever. I restarted the phone and it booted back to

my 03-17 slot.

That's why I'm asking if a clean-install of 03-10 (or other version) will be a problem.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Yes. With other phones, I never did the OTA update.

I booted to TWRP. Did a full backup. Then, flashed the new zip file.

I only used that backup a couple of times. But, it was great when I needed it. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Ryan Diesel:
Guys, there's a service called "Connectivity Health Services" that runs all the time on my stock ROM. Is this service necessary? Do you guys have it in your customs ROMs? If you guys don't have it in your custom roms then I am looking forward to disabling it. So please check and help me out.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Chaplan:
Flashed the first official build with open gapps Micro, had to install google's web view because some apps derp with the included one.

Besides that when opening HBO Portugal APP either to stream or playback downloaded content the app errors out stating the content can't be played.

Attaching an SS of the log error that comes up when I hit the play button.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] claviger-pc:
i used stock package. One trick I remembered was to boot lineage first without gapps or root. Then reboot and flash gapps. This was something that often had to be done on certain devices. I have it all set up and seems to be working just fine. Also, make sure that you have Android 11 flashed on both slots (fastboot set_active a (or b)).
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Edmontonchef:
Flash the ROM, reboot recovery then sideload mindthegapps.

Works great here

MindTheGapps-11.0.0-arm64-20210328_143848.zip | by Alessandro Astone for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] roxy1712:
When I flashed and booted without MindTheGapps, then sideloaded after, it worked great.

Unfortunately now dealing with a nasty bootloop after I try to flash the Magisk patch... it'll load everything but screen will become unresponsive and inevitably reboot.

Fixed by doing the direct install from Magisk instead of sideloading the patch... works great now!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Do I have to flash the microg version for spoofing? Doesn't seem to work with the official 4/1/2021 build. Or did I not flash it correctly?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
The sole reason why my unofficial builds are still up is due to microG support.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sinkoo1979:
ok

thanks

I will flash the microg version
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
System Updater should work.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] dlbarron:
I'm currently running stock ROM on my sunfish, but I always ran Lineage on my old Nexus so I'd like to switch. Unfortunately, I have several two-factor authentication apps that I cannot do without and getting them setup is a pain. I have to ask for permission and be "allowed" to re-enroll.

So, my question is. How much do I lose if I install Lineage?

One of the steps in the install is to "Format data" and that worries me.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] PeterCxy:
You basically need to wipe all data when switching ROMs. It's impossible to switch ROMs without losing all data.

For 2FA, I personally use KeePass to store the keys so that I don't lose them every time I wipe / change my phone, because I am a custom ROM developer and I wipe my phones very often.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] miko12312:
1. Enter fastboot ,fastboot flash boot boot.img

2.restart into recover

3. Wipe data

4.reboot into recovery

5. Sideload rom.zip

5.download https://androidfilehost.com/?w=files&flid=322935 these gapps

6.do not flash after sideloading rom , after sideloading rom reboot into recovery and sideload gapps, it will say failed signature verification, just finish installing reboot into phone

7. Install magisk canary v21 only one all modules like viper4android works with pixel 4a just update magisk patch boot and flash v21 mod in magisk to downgrade,use safteynet fix mod, magisk hide prop mod , use pixel 4a 5g, pass , also use fkm to flash different kernel Blu spark best and fsocitey best options

Sorry I can't provide full info on sfatynet pass fix on here
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] droncheg:
Just flashed new 080421 build via OTA - stuck on boot animation. Forced reboot via power+volume up, booted back to 010421 and tried again - same result with 15 mins of waiting at boot animation. Booted again to 010421 and rebooted to recovery, flashed 080421 via adb, rebooted to recovery again, flashed magisk 22 and mindcoregapps and it's works!

Seems OTA flashing not ready for use? Or it's because of magisk and gapps?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eng.stk:
Worked fine for me. Maybe it's mindthegapps derping, happened to me exactly the same while flashing unofficials builds.

lineage-18.1-20210408-nightly OTA flashed fine with open_gapps-arm64-11.0-pico-20210130-TEST.zip and Magisk v22.0, keeping all nicely updated after reboot.

Just flashed blu_spark kernel after and I'm at home :)

No April ASB merged in it seems @PeterCxy?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] droncheg:
Test clean install of 010421 with opengapps and magisk, ota upgrade to 080421. Yep, this works fine. Damn mindgapps =)

Offtop (if its possible) - can anyone tested Viper4android on this rom? How to make it work? Added via Magisk modules, rebooted, disabled AudioFX, entered in V4A, rebooted again, switched on some settings, but still not working (even in compat or old mode). Tested on Youtube Vanced.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] eng.stk:
@PeterCxy There's a toggle in battery section for battery percentage, doesn't do anything.

Probably something left behind from vendor overlays?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] miko12312:
Need magisk v21 and a certain v4a to make it work and switch to legacy mode also audio mod for magisk only way I have tested to work there is not any other way that has worked
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] miko12312:
You need to install magisk canary let it update , install audio modification library magisk mod ,viper4android 2.7.2.1,and in the module page of magisk go-to install from storage and install magisk v21.zip and reboot ,allow proper privileges and install drivers for v4a and choose legacy mode in settings check driver status for yes and enable master limiter option , also convolver and ddc can be modified and added only while plugged into PC and added to android data folder viper4android
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sk8223:
Sorry, I posted in the wrong thread. :confused:

But I started using this ROM, and it seems pretty stable. Thank you OP! No major crashes other than setup--some weird msg about the SIM crashing but it hasn't come up again.

1 thing I miss from stock is the Pixel Camera, the Google Camera app from the Play Store produces some really grainy photos with this ROM. I'm not surprised since the stock ROM would contain a lot of tweaks and processing to make the camera hardware work well. I'll flash a Gcam port at some point but we'll never get stock ROM-level photo image quality unfortunately. Not a big deal for me because I don't intend to make this 4a my daily driver.

I flashed Nikgapps' basic package (Canary), it contains some carrier bloat I don't care for. I don't recommend this package unless you use Google Fi as it forces the Fi app to stay enabled. Go with the core package instead.

After that, I flashed Magisk 22, Universal SafetyNet Fix, EdXposed and a couple of other Magisk Modules. Everything is looking good so far. @eng.stk's kernel is working well here too, but I understand that no support will be given for custom ROMs. Still worth using, thank you!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sk8223:
Accidental double post. I am so not used to XDA's new layout.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] miko12312:
What version of edxposed and riru ,riru edxposed did you use and can you confirm it works , as of right now latest riru and edxposed not working or are not detected
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I don't have it. I also don't have GApps installed, if that matters.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] amphi66:
This is not an app on my Stock A12 ROM (Mint Mobile). Something from your carrier?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Ryan Diesel:
Ok then I will test it out by disabling it.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] wireroot:
I don't have GApps but I installed the Gcam Services Provider which possibly mocks some functionality.

When looking at the output of adb shell pm list packages you will find a long list of apps.

Some "obvious" examples (as they have descriptive names) are the following (some are disabled):

Adaptive Connectivity Services
com.google.android.apps.scone

Google Assistant
com.android.hotwordenrollment.okgoogle
com.android.hotwordenrollment.xgoogle

Google Connectivity Services
com.google.android.apps.gcs

My Verizon Services (Verizon does not operate in my country)
com.verizon.mips.services
com.verizon.llkagent

If you execute the above mentioned ADB command, does any of the package IDs appear in your list?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I ran the adb command, as you asked.

All 6 of those packages appeared.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Ryan Diesel:
I didn't notice any difference after disabling it. So I turned it back on.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] icantlogin:
I noticed your post just now while searching for something else. I only recently started using LineageOS on my Pixel 4a and experience the same issue with long pressing the shutter to take a video. Motion photos I don't know, I hardly take any photos and have never seen a motion photo when I was using the stock ROM either--although the setting to take motion photos has always been on auto. Since using LineageOS though, I have experienced taking a photo and it not actually being saved, so I guess I'm going to turn off motion photos now to prevent that from happening, thanks!

Edit: some extra info that might be relevant -- I'm using Nikgapps Core.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
What steps did you take when you tried your downgrade?

Did you start by loading the 02-05 factory firmware?

Did you try loading the older LOS ROM from LOS recovery? If so, did you wipe data first?

Thanks.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] d33dvb:
Anyone mind hopping over to the twrp thread and helping get us a working twrp for our device? I think the community would broaden if we had twrp.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Visual Voicemail Issue. I'm back to 03-10 build.

As I mentioned previously, with the 03-17 build, I lost visual voicemail.

According to this merged update, it's an AOSP issue:

https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/325978/

Notice they mention "This will break functionality for calling voicemail in a multi-sim

device."

I opened this issue:

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

My attempts to go back to 02-17 failed. I downloaded the 03-10 build files.

I'm not sure if these instructions (push_update script) can be used

to go back to older versions:

https://wiki.lineageos.org/devices/sunfish/update

Thinking that LOS19 might show up in the next couple of months, I waited.

If a clean-install of LOS19 would happen soon, why clean-install 03-10?

This GrapheneOS issue opened a couple of weeks ago:

https://github.com/GrapheneOS/os-issue-tracker/issues/1108

Apparently, Android 12 (LOS19) also brings the problem with visual voicemail.

Thus, I clean-installed 03-10 build of LOS 18.1.

I am now back to February 5, 2022 security update.

But, visual voicemail is working. :)

BTW, I noticed this yesterday...

Our device got an experimental build:

https://buildkite.com/lineageos/android/builds/43232

That's good news, I hope. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Hello, the official instructions say that the Pixel 3a needs to be updated to the newest firmware (from Android 11 to 12) before updating LOS to 19.0.

There is no such instruction for updating the Pixel 4a. Is this really not necessary?

Thanks in advance.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] binary**#:
The official installation instructions have been updated to state that you need to be on Android 12, but since the latest build for this device is yet to go live, the instructions here are still for installing LieageOS 18, which is based on Android 11.

UPDATE: Android 12 first nightly build is now live and yes, you need to be on the latest Android 12 firmware
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Ok, thanks for your answer. How do I update the firmware of my 4a with LOS 18.1 to Android 12 without losing all data? Just by installing the factory image with -w and immediately LOS 19.0 and GApps?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] binary**#:
Yes, you will first have to install Android 12 firmware, either by flashing the factory image via Fastboot or Flash Tool. But both these methods use the fastboot -w command which will wipe off all the data from your device. And you cannot skip this command because you are going from custom rom to stock, so a reset is a must. In short, you wouldn't be able to escape a data wipe.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Thanks a lot, in this case the "upgrade instructions" for e.g. Pixel 3a do not make much sence. The firmware upgrade from 11 to 12 is mentioned there for the upgrade, but an upgrade would not include a wipe usually AFAIK.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] binary**#:
Glad to help. Just remember that whenever you are upgrading a ROM to a newer OS build, clean flash is always the way to go. Dirty flash is only advised when you are installing nightly builds and/or monthly updates.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
1. I always follow the above advice and "Dirty flash ... only ... when ... installing ... monthly updates.

2. I'm not updating to 19, yet. I want to see if the visual voicemail issue gets fixed in AOSP.

3. However....

When going to the LOS download page, I clicked on "Device Info".

There, I found a link to "Upgrade to a higher version of LineageOS (eg: LOS18.1->LOS19.1)".

That page says nothing about 'latest firmware'. Furthermore, the latest blog entry says

"Please note that if you’re currently on an official build, you DO NOT need to wipe your device,

unless your device’s wiki page specifically dictates otherwise, as is needed for some devices with

massive changes, such as a repartition."

As I stated in #1, I would not go from 18 to 19 without data wipe/format & first loading the new firmware.

However, if this is necessary, I can see a way that someone might think it is not.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] archy112:
I dirty flashed LOS 19.1 over offical LOS 18.1. I followed the guide provided by the wiki https://wiki.lineageos.org/devices/sunfish/upgrade

After flashing the the update package, i rebooted to recovery and also flashed the Mindthegapps package. I already used the latest firmware because i tried the stock android 12 a few weeks ago and the returned to LOS 18.1.

So far everything works fine. First boot with LOS 19.1 took a little bit longer but everything works. ;)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
I've also dirty-flashed my 3a and 4a today with GApps and M****k and both are working well.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Joojoo1993:
Have you been on stock Android 12 already before or Android 11 was the only stock ROM installed before?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Both devices have never seen stock Android 12 before.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] The Transporter:
I just flashed Lineage 19.1, so far so good.

However, I'm trying to reinstall Magisk but I'm unable to find the boot.img. Do you know how to find one?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Since I use LOS recovery, I used that (64MB) image.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
You would have to extract it from payload.bin (there are tools avilable to do this). Much easier is renaming it (Magisk.apk) to *.zip and flash it via "adb sideload /path/to/zip". This will also install a script to keep Magisk while updating.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] wireroot:
Since I no longer have a bulletproof backup & restore solution (compared to TWRP on my previous phone) I became very cautious/reluctant regarding OS updates on my Pixel 4a.

I don't mind/care about visual voicemail, since I did not even know about that feature - I simply don't want my OS to crash or my screen turn off unexpectedly while using my phone (like what @k4tfish experienced) ...

Which LineageOS 18.1 version can you recommend after reading about your reported problems regarding the 2022-03-17 update?

Is 2022-03-10 a good choice or should I pick a different/later version?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
As I posted earlier, I'm on a clean-install of 0310. This brought me back to Feb security update.

However, visual voicemail is working.

I didn't have any problem with screen on/off, so I can't comment on that.

I would have loved to try LOS19, but I'm pretty sure the voicemail issue is there, too.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I'm not having the problem now (on 0310 build).

Wouldn't I need to extract the dialer apk from the 0317 (or later) build?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I found "Dialer.apk" under "/system/product/priv-app/Dialer"

Is that what you need?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
This is the file found in "/system/product/priv-app/Dialer".

My phone is currently running 03102022 build of LOS18

EDIT: I had attached the 'Dialer.apk' file. Maybe it's too big (14MB).

I've attached a zip file containing the 'Dialer.apk' file.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
Using your binary pulled from lineages it works
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Could you provide some details.

Are you running 18.1? A build after 0310?

Did you install the 'Dialer.apk'? How?

Thanks for your time.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
By basically uninstalling original dialer, then using "package manager" from f-droid repo and using installer from there because I don't really care how to do it manually rn, and I was also in a rush.

Sooo. Basically uninstalling orginal dial, then installing provided dialer as system app from package manager

Also I'm on lineageos 19.1
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
I'll provide (hopefully) better instructions once I get to a computer
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Thanks for this.

If I understand correctly...

You installed LOS19 and had trouble with voicemail.

You're rooted (Magisk) and were able to use 'Package Manager' to uninstall the system app "Phone".

Then, you were able to install a new system app "Phone" with the "Dialer.apk" file from LOS18

0310 build.

You no longer had voicemail issues.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Flash magisk zip through recovery
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
Essentially but I also did try some extra stuff but those steps should work. It all could be done manually. Yes that is exactly seems the problem is with the app 'Dialer' itself.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
I think its one of these, this is the log that standard out most to me when ever I was debugging the oob app.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] fbievan:
Stil

Still not sure how but
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
Wait, is there no need to patch the stock boot.img with Magisk if we're going to sideload Magisk in recovery anyway?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I hope it's ok to ask here...

I'm planning to upgrade to LOS19. I was going to try the instructions here:

https://wiki.lineageos.org/devices/sunfish/upgrade

Has anyone done this?

I have a question about this:

"Run adb sideload /path/to/zip (inserting the path to your LineageOS package)."

If I run that command, will it also update my recovery?

When I've done a "clean install", I flashed the recovery img file to boot partition first.

Will the recovery be updated when I run the "adb sideload LOS19.zip" command?

Thanks for your time.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Installing Magisk.zip via adb will do it for you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
Sh*t. What's the point of patching the boot image then? Is that only necessary for the first time you install a custom ROM?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rogers11:
Just sideload via adb and look at the messages. It will patch the img.

And you have to do it just once. When getting an OTA it will reinstall Magisk for you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
I'm not 100% sure on this, but I think boot.img contains the recovery as well?

I think you can also just reboot to bootloader, use "fastboot flash --slot all boot boot.img", then reboot to recovery, go to Apply update -> Apply via adb, then use the adb sideload command.

(Keep in mind though that I've never installed LOS on my 4a, but the above mentioned install path has worked for me on several custom ROMs)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Thanks for this.

Since someone always does, I will remind us that this method is no longer supported.

You can see the install instructions here.

Of course, when I've needed Magisk, I've done it as you describe. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
Since I use custom ROMs, I'll have to patch the boot.img of whatever ROM I'm planning on flashing, and then if the ROM has an updater, the patched boot image will save me the hassle of having to manually sideload Magisk?