Development [ROM][13.0][ENCRYPTION] Official LineageOS 20 for A52 4G and A72

[SuperUser008]

Since upgrade to LOS 20 the phone screen quite often remains active during phone calls, resulting in unwanted touches of buttons with the cheek.

Everything else seems to work good so far.

Are there chances that it will be fixed? The macrodroid workaround does not seem to work, at least on my phone...

 

[Ryzen5950XT]

Are there chances that it will be fixed? The macrodroid workaround does not seem to work, at least on my phone...

Touch the top of the phone to your ear and you wont face any issues.

 

[Rampler]

Touch the top of the phone to your ear and you wont face any issues.

Sarcasm on
.. or stop calling ..
Sarcasm off

 

[MarioRS]

Im really not sure if i'll ever figure it out or not.

Dear Simon,

do you maybe have any news regarding the problem with the BT connection?

Best regards, Mario

 

[Simon1511]

Dear Simon,

do you maybe have any news regarding the problem with the BT connection?

Best regards, Mario

Im working on it.

 

[MarioRS]

Im working on it.

Many Thanx!

 

[MarioRS]

Many Thanx!

Let me know, if I can be of any help with testing e.g.

All the best, Mario

 

[mariusmauxy]

Is there any performance , or any difference between this rom and pixel experience?
I've noticed You both cooperate (the 2 Devs ryzen and Simon), and i can't decide wich one to use.
I am currently using Lineage 20.0, and the only thing i have noticed in both Roms is that annoying back button laggy animation.
And somehow lineage seems less laggier, however the autobrightness is to high and in some apps flickers

 

[Rampler]

Is there any performance , or any difference between this rom and pixel experience?

My 5 cents: I use LOS20 and most annoying bug's are:
- Bluetooth doesn't work with my headset (known bug)
- During a phone call, the display does not switch off, which is why I regularly get muted, or hang up etc. (known bug)
- The hands-free button on Whatsapp, Signal etc are inverted. Hands-free calling during native calls (SIM) works (known bug)
- The call setup takes an extremely long time (known bug)
There are only four bugs, but still annoying.

The developers may still find solutions, until then I have chosen the Samsung as my backup cell phone and bought a Motorola (without LOS)
Hopefully I'll be happy with the Motorola.

best regards Klaus

 

[Ryzen5950XT]

My 5 cents: I use LOS20 and most annoying bug's are:
- Bluetooth doesn't work with my headset (known bug)
- During a phone call, the display does not switch off, which is why I regularly get muted, or hang up etc. (known bug)
- The hands-free button on Whatsapp, Signal etc are inverted. Hands-free calling during native calls (SIM) works (known bug)
- The call setup takes an extremely long time (known bug)
There are only four bugs, but still annoying.

The developers may still find solutions, until then I have chosen the Samsung as my backup cell phone and bought a Motorola (without LOS)
Hopefully I'll be happy with the Motorola.

best regards Klaus

We have found a fix for bluetooth calling and also inverted audio output/inputs on voip calls, it just needs to be properly implemented now, which is turning out to be quite tricky and will likely take us some more time.

As for the display not turning off during calls, samsung just gave us a crappy sensor, so you need to touch the portion of the screen near the camera punch hole to your ear for it to work, or just click the power button after picking up the call.

 

[mariusmauxy]

My 5 cents: I use LOS20 and most annoying bug's are:
- Bluetooth doesn't work with my headset (known bug)
- During a phone call, the display does not switch off, which is why I regularly get muted, or hang up etc. (known bug)
- The hands-free button on Whatsapp, Signal etc are inverted. Hands-free calling during native calls (SIM) works (known bug)
- The call setup takes an extremely long time (known bug)
There are only four bugs, but still annoying.

The developers may still find solutions, until then I have chosen the Samsung as my backup cell phone and bought a Motorola (without LOS)
Hopefully I'll be happy with the Motorola.

best regards Klaus

I use the google dialler app for calling, and yes i cant confirm the other bugs, and for the laggy UI and back button animation, i am using Rootless Laucher, that seems to solve the probleme atm.

 

[Flyos]

I just noticed something. Typical image size of photos taken while on the stock ROM is roughly 4-6MB, while photos taken by either Aperture or OpenCamera on LineageOS is much higher (roughly 70-90MB). I have found nothing immediate that could explain this (quite large) discrepancy in file size (neither resolution, nor apparent JPEG compression quality, they seem to be the same by default).

Anyone with an explanation as to what is going on here? And maybe a way to go back to some more reasonable file size per picture?

 

[SchwarzerAfri90]

I cant install the rom somehow. I can install TWRP, but either with flashed multidisabler nor without it i can install the rom.

Im getting an Error wile Patching the vendor image.
E2001: Failed to update the vendor image. Updater Process ended with error: 1

Tried to install coming from the newest stock Firmware (but phone wants KME Enrollment After Reboot)

What am i doing wrong ?Its a while ago since i flashed devices, but i could manage to flash Lineage 18.1 on an old Tab, managed to install TWRP here...

Also, whats weird for me, is that TWRP doesnt keeps its Language Settings, its english after every restart.

Can somebody please help ? i just want to get rid of this knox enrollment bull****, cause i cannot unenroll it anymore cause of lost credentials / beef with the guy that has acces to the Enrollment Terminal...

 

[Simon1511]

I cant install the rom somehow. I can install TWRP, but either with flashed multidisabler nor without it i can install the rom.

Im getting an Error wile Patching the vendor image.
E2001: Failed to update the vendor image. Updater Process ended with error: 1

Tried to install coming from the newest stock Firmware (but phone wants KME Enrollment After Reboot)

What am i doing wrong ?Its a while ago since i flashed devices, but i could manage to flash Lineage 18.1 on an old Tab, managed to install TWRP here...

Also, whats weird for me, is that TWRP doesnt keeps its Language Settings, its english after every restart.

Can somebody please help ? i just want to get rid of this knox enrollment bull****, cause i cannot unenroll it anymore cause of lost credentials / beef with the guy that has acces to the Enrollment Terminal...

Please follow the instructions on wiki.lineageos.org.

 

[SchwarzerAfri90]

Please follow the instructions on wiki.lineageos.org.

Thats what i did, except that i used TWRP instead of the Lineage Recovery.

I reverted back to the stock rom via Odin , device turns on, but now the Efuse is at 0x1 and when the device tries to setup a work profile , it just aborts the process with the usual knox error and starts setup over again.

Before, i could use alliance shield qr code to setup own work profile and enable oem unlock. But now this is blocked by the e fuse.

I can enter the settings menu / browser / install a launcher and run it , but developer options is locked now, and the usual process via FRPTool to disable Knox (and make dev options show again) doesnt work too.

Standings right now:

Stock Android 13 / Latest Sec Patch / sticking in MDM/workprofile setup loop.
Oem Lock : On(U1)
KG State: Prenormal

What can i do now ? Is there any way to unlock the bootloader again without accessing the dev options ? Chances to use a custom recovery ?

Sorry for the huge input, but i wasnt on the flashing topic for like 6 years now

 

[rien333]

I think flashing Magisk with Lineage recovery should work if you put the zip onto an SD card.

Otherwise yes, you can just download the latest TWRP .tar for A52 from the TWRP website and flash that with Odin.

Indeed, this first option was a super easy way of acquiring root! And thanks for all your work

To reiterate:

1. Download the newest magisk release, and change the apk extension to '.zip' if necessary.
2. Put that file on your sd card.
3. Then, during the add "add ons" step of the official installation guide, install it just like you would flash the LineageOS rom, but instead of sideloading it by means of adb, choose "select from android".

 

[rien333]

Just updated to the march 10 release! Still, I have a minor issue.

Bluetooth works great with my bluetooth speaker, but I can't get the bluetooth icon to show in the statusbar when bluetooth is on but unconnected. IIRC, this used to work on my last phone (not a samsung, but running lineage OS 18). The bluetooth icon is displayed the moment when I connect to a device.

I'm using a galaxy a52. I could be mistaken ofc, in the sense that this was never a feature. But otherwise, it seems like a bug. Of course, I do have System > Status bar > System icons > Bluetooth set to enabled.

 

[ethical_haquer]

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.

/*
* 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)
• On some bluetooth Watches/Earphones In-Call sound is played from the phone's speaker/earpiece

Installation instructions

Make sure you are on OneUI 5 firmware before flashing this ROM, otherwise the installation will fail!

Recommended
Follow the guide on the LineageOS website: A52 4G | A72

Alternative way (TWRP/OrangeFox)

1. Make sure your device's bootloader is unlocked.
2. If not done before, flash blank VBMeta with Odin in AP slot.
3. Make sure to have the latest available version of TWRP/OrangeFox installed.
4. If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
5. Download the lineage build for your device from the link below and optionally download your preferred GApps package too.
6. Flash the LineageOS zip using the "Install" button.
7. Optionally, flash Gapps right after.
8. Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
9. Wipe metadata and cache partitions. This only has to be done once when you install LineageOS.
10. Reboot

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

Gapps (choose arm64 and 13.0):
FlameGapps Canary | NikGapps Canary | MindTheGapps

Old builds:
LineageOS 20

Support

• Telegram

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

Bugs

• VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)

So I guess AT&T will not work then? Are there not any workarounds?

 

[Simon1511]

So I guess AT&T will not work then? Are there not any workarounds?

It won't work unless they still have 2G and/or 3G running. Sadly there are no workarounds for that.

 

[rien333]

Quick tip:

I don't have Google play services installed, and couldn't get Google maps or other maps applications to work, at least not properly. After messing around with UnifiedNLP for a bit, I discovered that the simplest workaround is just to install an older Google maps apk. You can easily find these online, I used the newest one from 2021.