Development [ROM][12.1][ENCRYPTION] Official LineageOS 19.1 for A52 4G and A72

Search This thread

ralanar

Member
Apr 30, 2022
10
6
This is intended to make sure the correct sim card is being picked for audio output. Can't do it any better at the moment.
I also noticed the delay. Since I have and use dual-sim capability, I really appreciate that it works at all.

I did notice, however, that if the phone is hooked to my vehicle through Android Auto, the calls go through almost immediately, with no noticeable delay at all compared to making a call with just the phone itself. I haven't tested with just a bluetooth hook-up.
 
  • Like
Reactions: Simon1511

kingozilla

Senior Member
Sep 12, 2020
70
17
Saudi Arabia
I don't understand who criticize the encryption, ROMs with no encryption doesn't have a real usage in a daily life. Anytime your phone get stolen, your data just are completely open for the theft, or you make your phone around your friend he just can plug your phone in computer and copy some files.
 
So I've jumped from Pixel Experience to LineageOS. I'm finding it more stable for me personally.

However, I've noticed the FOD on AOD is a bit buggy. It sometimes doesn't turn on.

I didn't experience this issue in the final July update of Pixel experience. So maybe they already have this patched.

Thank you for the ROM :)
 

Ryzen5950XT

Senior Member
Mar 16, 2022
221
187
Samsung Galaxy A52 4G
So I've jumped from Pixel Experience to LineageOS. I'm finding it more stable for me personally.

However, I've noticed the FOD on AOD is a bit buggy. It sometimes doesn't turn on.

I didn't experience this issue in the final July update of Pixel experience. So maybe they already have this patched.

Thank you for the ROM :)
Could you explain what you mean by more stable?
 
Could you explain what you mean by more stable?
PE:
1. Auto brightness was too aggressive. It would quickly brighten up in a completely dark room due to sensing it's own brightness (sort of recursive, increases brightness, senses more light, increases brightness more). This became a problem using the phone at night.
2. Lock screen brightness (not a problem as it's being looked at)
3. Battery life was lower than LOS/RayOS. AOD brightness bug might've made it worse.

What I loved about PE:
1. Google stuff (dialer, recorder, pixel goodies)
2. Patching smaller things quickly from upstream (e.g. alignment of text under FOD)

Guess it's just the brightness bug that made me not properly enjoy the pixel experience. Other than that it seemed to work fine.

I have my eye on both ROMs. I really enjoy the pixel experience ROMs (have used it before on lavender).

I really want to try and learn a bit about building and working on these ROMs so I can better contribute through code rather than posting bugs. It's just that I haven't worked on low-level kernel stuff (or android in general) before. Will probably need a mentor that is willing to teach me :D

These are just my personal nitpicks. I really appreciate all of you devs for spending your time making these ROMs for us :)
 
  • Like
Reactions: Simon1511

kingozilla

Senior Member
Sep 12, 2020
70
17
Saudi Arabia
One of the annoying things in pixel rom is when you use battery saving mode, dark mode just get turned on automatically. Google mayn't know that I use battery saver as a default, dark mode is very annoying in day time. I have to ask here, does battery mode in LOS behave the same of pixel rom?
In real what Ryzen did in pixel ROM is a great work, any minor edit he will do (like what I criticize) will just ruin the pure pixel experience.
 
One of the annoying things in pixel rom is when you use battery saving mode, dark mode just get turned on automatically. Google mayn't know that I use battery saver as a default, dark mode is very annoying in day time. I have to ask here, does battery mode in LOS behave the same of pixel rom?
In real what Ryzen did in pixel ROM is a great work, any minor edit he will do (like what I criticize) will just ruin the pure pixel experience.
Yes, dark mode gets enabled automatically when you enable battery saver on LOS too.

I believe this flow is baked into AOSP, so it's present in both PE and LOS.
 
  • Like
Reactions: Simon1511

Ryzen5950XT

Senior Member
Mar 16, 2022
221
187
Samsung Galaxy A52 4G
PE:
1. Auto brightness was too aggressive. It would quickly brighten up in a completely dark room due to sensing it's own brightness (sort of recursive, increases brightness, senses more light, increases brightness more). This became a problem using the phone at night.
2. Lock screen brightness (not a problem as it's being looked at)
3. Battery life was lower than LOS/RayOS. AOD brightness bug might've made it worse.

What I loved about PE:
1. Google stuff (dialer, recorder, pixel goodies)
2. Patching smaller things quickly from upstream (e.g. alignment of text under FOD)

Guess it's just the brightness bug that made me not properly enjoy the pixel experience. Other than that it seemed to work fine.

I have my eye on both ROMs. I really enjoy the pixel experience ROMs (have used it before on lavender).

I really want to try and learn a bit about building and working on these ROMs so I can better contribute through code rather than posting bugs. It's just that I haven't worked on low-level kernel stuff (or android in general) before. Will probably need a mentor that is willing to teach me :D

These are just my personal nitpicks. I really appreciate all of you devs for spending your time making these ROMs for us :)
Hmm thanks for letting me know, Ill work on the brightness curve.
 
  • Like
Reactions: thatdevsherry
Aug 6, 2016
21
6
with dolby integration, can i use another equalizer like viper4android?
Yes you can!
Read my Post (#10) i wrote in this forum. That's the only way i have made viper4android to work with this phone.


@Simon1511
Since the last update (06.08.) i notice some bugs.
- AOD brightness is to low
- no connetion to mobile data after staying a long time in WiFi or coming back from airplane mode (overnight). I have to restart the phone to get mobil data back
- during a call (the phone is at the ear and the display is off) the display 'flickers' sometimes (white and black)
- the minimum brightness during direct sunlight ist still present, no so often as in the July build

The AOD doens't move his location. What about inburn protection?

As always, THANK'S for your work

WBR
Danny
 
A few issues I've encountered. Has anyone else faced these?

- Hotspot. The page informs that hotspot is working, but it doesn't work in my case. I moved my sim to another phone and the hotspot from that phone worked, but when using this ROM, other devices trying to connect get stuck on "Obtaining IP address".

- Handling audio between SIM and whatsapp (WA) call. When I'm on a WA call with BT earbuds. If I get a SIM call in the middle, after declining (or ending the SIM call after accepting), the WA audio does not come back to BT earbuds. I encountered it twice but wasn't able to figure it out properly.

I believe the sound was coming from the phone speakers, but it certainly isn't the same as before the SIM call. Note that the volume slider still shows the BT icon after I switch back to the WA call.

- Quickly pressing the FOD on lockscreen makes the brightness go 100%. Opening the phone and changing brightness doesn't work. I turn the display off into AOD and the brightness goes down.

I've also mentioned a similar behaviour in PE thread. It's just that in PE, the brightness increase happened on AOD, here it happens only on lockscreen.

- Low AOD brightness, already mentioned by @Peter_Petersen
 
  • Like
Reactions: Simon1511
Announcement!
A52 4G and A72 are now officially supported by LineageOS!

From now on new builds will be released weekly on LineageOS' website. That means every week there will be new official builds for both devices.
New builds for A52 4G will currently release on every Friday and for A72 on every Saturday.

What are the differences between the unofficial and the official versions?
  • The official versions will be updated frequently (every week) with the latest changes from LineageOS.
  • They have OTA-Update support built-in, which means you will be able to easily update to newer versions using the Updater found in Settings->System->Updater.
  • Also, as mentioned by @thatdevsherry and a few other people, hotspot accidentally went broken in the last unofficial build. This has been fixed on the official ones.
  • Macro (A52 and A72) and Tele (A72 only) cameras are now accessible by Gcam, which wasn't working before.
How do I update to the official version?
You should be able to just dirty flash the official build over the unofficial ones.

Apart from that, all device trees and the kernel can be found on github.com/LineageOS and review.lineageos.org. Feel free to contribute!

Downloads
A52 4G: download.lineageos.org | wiki.lineageos.org
A72 4G: download.lineageos.org | wiki.lineageos.org
 
This is awesome, congratulations!

I'll be doing a clean install. The lineageos wiki mentions installing the latest stock update (maybe to be at the latest bootloader version etc).

Is it really necessary to install the latest stock image? My device was already running Android 12 (maybe June patch).
 
This is awesome, congratulations!

I'll be doing a clean install. The lineageos wiki mentions installing the latest stock update (maybe to be at the latest bootloader version etc).

Is it really necessary to install the latest stock image? My device was already running Android 12 (maybe June patch).
No, you don't necessarily need the latest stock firmware. It's enough as long as it's Android 12.
 
  • Like
Reactions: thatdevsherry

itsesa

New member
Aug 25, 2022
4
1
Hey Guys!
is there any hope for A52 5G? 🥲
I Really want to try out Lineage OS / Pixel XP on my device as well...
 

itsesa

New member
Aug 25, 2022
4
1
but what's the difference between the 5G & 4G model?
sorry lol I don't really have a lot of information about custom rom buildings 😅
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi Simon 1511,
    I just went through all steps and smoothly installed everything. As your brief points were not detailed enough and I had to search a lot around and I made myself some notes. Here are the notes:

    Secondhand Samsung A52 (SM-A525F/DS)
    Android 12 (One UI v4.1)
    Baseband version A525FXXU4BVG2
    Android security patch level October 1, 2022

    = Backup Samsung stock ROM =​

    == Backup using fastboot (spoiler: does not work)​

    • Power off by pressing vol_down + side_key
    • when screen goes off keep holding vol_up + side_key
    • release all buttons when Samsung logo appears
    • select Reboot to bootloader
    • on PC run: fastboot reboot twrp-3.7.0_12-0-a52q.img
    • ends with error: fastboot FAILED (remote: 'unknown command')
    • this method cannot be used with Samsung devices as Samsung does not support fastboot

    == Backup using flash TWRP (spoiler: does not work)​

    • Factory reset your phone, boot and skip what is possible (mainly any security patterns, fingerprints etc.). Just connect to Internet.
    • Open Development Options (7 taps on Build number)
    • OEM Unlocking (Allow the bootloader to be unlocked) ON (if you don't see the item in menu, connect to internet via WiFi and restart phone)
    • Switch off the phone (side_key + vol_down)
    • With disconnected PC cable hold vol_up and vol_down (download mode) and connect PC cable
    • Unlock bootloader (long vol_up and vol_up on the next screen)
    • Wait for deleting all data and reboot to stock ROM.
    • Skip through first run wizard again (just connect to Internet) and check that OEM Unlocking is ON and grayed out. (Necessary step!)
    • Reboot to Unlock bootloader screen again, but this time press vol_up shortly to continue to download screen. By the way, if you select Lock Bootloader, you still can get original phone with warranty.
    • Now, if you use vbmeta_disabler.tar in the next step you will break stock rom. But without using it you cannot boot into TWRP recovery. From this fact I conclude, that it is not possible to backup stock ROM.
    • Start Odin and put vbmeta_dislabed.tar in AP field. Disable Auto reboot options and flash by pressing Start. Without this step you will get "Invalid verifying vbmeta image." in the next step.
    • Put twrp-3.7.0_12-0-a52q.img.tar in AP field. Disable Auto reboot options and flash by pressing Start.
    • Reboot (Down+side) and immediately after display gets black boot to recovery (Up+side)
    • In TWRP Backup all excluding Data (it is erased anyway) and in options enable compression. Backup.
    • Unfortunatelly, as the vbmeta_disabled.tar modified stock rom and Samsung firmware immediately finds this out the backup is probably useless.
    • Fortunatelly, I was able to download the stock rom at sammobile.com .

    = Installing Lineage with Google Apps and Magisk root (optional) (spoiler: works like a charm) =​

    • Go through previous chapter "Backup using flash TWRP" up to the point where you boot into TWRP recovery (just before making backup)
    • Click Mount and uncheck all partitions leaving just Micro SD card
    • on PC: go to https://topjohnwu.github.io/Magisk/install.html
    • download last version of Magisk app and rename .apk extension to .zip.
    • Upload lineage, GApps and Magisk to the phone SD card using adb and USB cable:
    Code:
    adb push Magisk-v25.2.apk /external_sd
    adb push lineage-19.1-20221125-nightly-a52q-signed.zip /external_sd
    adb push MindTheGapps-12.1.0-arm64-20220605_112439.zip /external_sd
    • in TWRP Install lineage, return home
    • in TWRP Install MindTheGapps, return home
    • in TWRP Install Magisk, return home
    • Wipe->Format Data->yes
    • Wipe->Advance Wipe->Select Cache and Metadata->Wipe, reboot system

    • Boot in Lineage and go properly through welcome wizard.
    • Go to files, navigate to SD card, rename Magisk .zip file to .apk file and install it
    • Start Magisk and let it reboot your phone and finish the installation.

    And now many days of restoring all custom settings of my UI.
    1
    Since a week or two, updater doesn't work. Manual downloads of new builds work
    Just did the update this morning and it worked perfectly.

    I'm on A52 with TWRP.
    1
    Solved my updater problem, somehow the permission to use wifi data was removed. Allowed wifi connections again, et voila it works
  • 23
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device.
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Supported devices
    All variations of A52 4G and A72 (A525F, A525F/DS, A525M, A525M/DS, A725F, A725F/DS, A725M and A725F/DS) are supported, but only A525F (6/128 variant) is well tested as I have this device.

    Working
    • Audio
    • Wifi
    • Hotspot
    • Calls
    • WifiDisplay
    • Bluetooth
    • OMX
    • Camera
    • NFC
    • Fingerprint
    • Screen-Off-FOD
    • Mobile data
    • GPS
    • DT2W
    • ...

    Bugs
    • VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)
    • Audio output in VoIP calls is swapped (WhatsApp, Discord, etc)

    Installation instructions

    • Make sure your device's bootloader is unlocked.
    • If not done before, flash disabled VBMeta with Odin in AP slot (originally posted here).
    • After that, follow the guides on the lineage website: A52 | A72

    • Make sure your device's bootloader is unlocked.
    • If not done before, flash disabled VBMeta with Odin in AP slot (originally posted here).
    • Make sure to have the latest available version of TWRP installed.
    • If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
    • Download the lineage build for your device from the link below and optionally download your preferred Gapps package too.
    • Flash the LineageOS zip using the "Install" button.
    • Optionally, flash Gapps right after.
    • Optionally, also flash Magisk v24 or newer right after
    • Format data in TWRP as the very last thing, otherwise you may end up in a bootloop if using encryption or coming from stock ROM.
    • Wipe metadata and cache partitions.
    • Reboot

    Downloads
    A52 4G: download.lineageos.org | wiki.lineageos.org
    A72 4G: download.lineageos.org | wiki.lineageos.org

    Gapps (choose arm64 and 12.1/12L): MindTheGapps | OpenGapps canary | FlameGapps Canary | NikGapps Canary

    Old builds:
    MEGA (18.1 and 19.1)

    Support
    Donations
    They aren't necessary, but if you like my work feel free to send me or LineageOS a donation.

    Credits
    To...
    • Me, for spending my time on this project
    • Whoever made the VBMeta disabler
    • @Grarak for his fingerprint fix for A70 and DT2W fix
    • @TheLeo2307 for testing on his A72
    • @miamighost for testing on his A52
    • Maybe more, feel free to tell me if I forgot someone

    Source Code: https://github.com/LineageOS/android_kernel_samsung_sm7125
    16
    Announcement!
    A52 4G and A72 are now officially supported by LineageOS!

    From now on new builds will be released weekly on LineageOS' website. That means every week there will be new official builds for both devices.
    New builds for A52 4G will currently release on every Friday and for A72 on every Saturday.

    What are the differences between the unofficial and the official versions?
    • The official versions will be updated frequently (every week) with the latest changes from LineageOS.
    • They have OTA-Update support built-in, which means you will be able to easily update to newer versions using the Updater found in Settings->System->Updater.
    • Also, as mentioned by @thatdevsherry and a few other people, hotspot accidentally went broken in the last unofficial build. This has been fixed on the official ones.
    • Macro (A52 and A72) and Tele (A72 only) cameras are now accessible by Gcam, which wasn't working before.
    How do I update to the official version?
    You should be able to just dirty flash the official build over the unofficial ones.

    Apart from that, all device trees and the kernel can be found on github.com/LineageOS and review.lineageos.org. Feel free to contribute!

    Downloads
    A52 4G: download.lineageos.org | wiki.lineageos.org
    A72 4G: download.lineageos.org | wiki.lineageos.org
    8
    Hey people, again thanks for waiting patiently and reporting bugs. Lineage 19.1 is now available with some more bugfixes and improvements!

    Apart from that, SeLinux is now enforcing!

    Also, this build has encryption enabled by default. That means that your data will be encrypted right on boot. If you don't want encryption to be enabled flash something like services disabler before first boot.
    If your phone keeps rebooting after flashing lineageOS 19.1 with encryption enabled make sure to format data in recovery instead of only wiping it.

    Downloads: A52 | A72

    Changelog:
    Code:
    -Updated to Lineage 19.1
    -May security patch
    -Enabled freeform windows
    -Build SamsungDAP for dolby audio
    -Fixed color calibration in livedisplay settings (Please note that not all display modes support color calibration)
    -Show download mode instead of bootloader in advanced restart menu
    -Re-enabled FM-Radio
    -Enabled night display/bluelight filter
    -Fixed audio with USB headphones/speakers/etc
    -Correctly detect phone variant and set props accordingly
    -Enabled encryption (FBE)
    -Removed unused partitions from fstab
    -Fixed USB mode not being select-able
    -Enabled MAC randomization for WiFi
    -SeLinux enforcing
    -Use correct default network mode (4G)
    -Enabled adoptable storage to work with FBE
    -Set props from stock ROM to make Netflix select DRM L1
    -Fixed proximity sensor not working at all
    -Updated kernel to A525FXXS4BVA2
    -Enabled burn-in protection
    8
    Hey people, thanks for waiting patiently and reporting bugs. Lineage 19 is now available with a long list of bugfixes and improvements!

    Before installing, make sure to be on OneUI 4 firmware and have OrangeFox or TWRP 3.6 or newer installed, otherwise you will end up in a bootloop.

    Also, this build contains an unofficial implementation of monet. Feel free to give me feedback on this.

    In addition the device trees are now available on my Github!

    Downloads: A52 | A72

    Changelog:
    Code:
    -Updated to Lineage 19.0
    -February security patch
    -Updated all blobs and configs to A525FXXS4BVA2 (Android 12)
    -Updated kernel to A525FXXU4BUL8 (Android 12)
    -Unified more blobs
    -Fixed screen rotation on A72
    -Switched to AOSP WifiDisplay implementation
    -Corrected status bar padding
    -Built more blobs from source
    -Switched to Clang r383902
    -Disabled APEX compression
    -Switched to UDFPS
    -Fixed FOD on AOD
    -Make FOD stay always on for working FOD on AOD
    -Increased the amount of time the screen lights up when touching the fingerprint sensor
    -Switched to stock health blobs
    -Overall cleanup
    -Enabled F2FS support for system partition
    -Switched to newer AIDL libperfmgr power HAL
    -Updated vibrator to AIDL to switch to manifest level 5 and match stock
    -Fixed audio in bluetooth phone calls on A52 (for somehow still broken on A72)
    -Imported APTX BT encoder from Pixel 5
    -Enabled unofficial monet implementation
    8
    Update

    13-01-2022: A52 (MEGA) | A72 (MEGA)

    Lineage recovery: A52 (MEGA) | A72 (MEGA)

    Changelog
    Code:
    -Latest lineage sources with december security patch (january one wasn't released yet)
    -Updated blobs to A525FXXU4AUJ2
    -Added initial A72 support -- see more information below
    -Switched to OSS fingerprint HAL by @Grarak
    -Cleaned up unused config files
    -Built lineage recovery for both devices
    -Added missing overlay for the system to know that we have a notch
    -Built more blobs from source
    -Fixed A2DP offload and switched to AOSP bluetooth audio implementation
    -Correctly boost brightness when the fingerprint sensor is touched
    -Fixed fingerprint sensor not working when screen brightness is low
    -Corrected size and position of the fingerprint sensor (And yes, the sensor is REALLY that big)
    -Disabled screen off FOD for now since it doesn't work anyway
    -Limit fingerprints to max 4 per user
    -Temporary disabled FMRadio since it somehow broke with latest sources
    -Built QCOM audio effects from source

    Some notes regarding A72 support
    Since I don't have an A72 here it was kinda hard to blindly support it. But first I wanna thank @madseason.live and Leo on Telegram for testing my builds on their A72's. Even though both of them did good testing, we didn't succeed in getting the fingerprint sensor to work. A72 uses a different sensor and driver than A52 does and without having the device here by myself it's hard to fix that without knowing what the actual issue is. It only works for setting up a fingerprint, but actually unlocking the phone with it doesn't work. Additionally, for somehow screen rotation is flipped by 90° which makes no sense at all since A52 and A72 use the same sensors except for fingerprint and camera. If someone has an idea or wants to contribute, feel free to contact me.