yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] seam0nster:
Thanks Simon, installed 20 successfully on A52 4G today, works great.

Dumb question for anyone, I'd prefer to ask for clarification than risk bricking my phone. I want to root with Magisk but see some conflicting information online with which method to use, is it the patched boot.img or sideloading the zip or is it fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img or something else entirely?

If there's a guide for the specific process, I can follow guides like a boss. Thanks!
[Samsung Galaxy A52 4G] Simon1511:
Usually it's enough to download the Magisk.apk from github.com/topjohnwu/Magisk/releases and flash it in recovery (depending on recovery you will have to rename it to Magisk.zip).
[Samsung Galaxy A52 4G] seam0nster:
I followed the lineageos.org guide to the letter and installed Lineage Recovery but it's my first time using it and it seems lacking compared to TWRP, so I don't think I can flash the zip via recovery (unless I sideload?). I would be happy to install TWRP if it's just as simple as replacing it with Odin, then I guess I could flash Magisk via TWRP.
[Samsung Galaxy A52 4G] Simon1511:
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.
[Samsung Galaxy A52 4G] seam0nster:
I think I'll go with that option, carefully following the instructions On the TWRP website. Thanks again for everything, not only fantastic maintainer, also incredibly helpful!
[Samsung Galaxy A52 4G] faceghost1996:
I want to report a bug, when playing music the FX equalizer stops and I have to open it again to activate the equalization again, do you think it can be solved?
[Samsung Galaxy A52 4G] bluKae:
Hi Simon1511,

thank you for this amazing ROM. I've been using your LOS 19.1 builds on my a52q and recently updated to the latest unofficial LOS 20 build. I didn't know about your A52 firmware GitHub repo though, so I flashed the latest official Samsung Android 13 firmware, causing most of the sensors (especially the gyro) to not work with both LOS 19.1/20 anymore. Furthermore, the fingerprint enrollment always fails on LOS 19.1 (only). As the sensors don't work with your first official build as well and nobody mentioned this issue, I guess that flashing the whole Samsung Android 13 was a mistake. So now my question: Is it a general issue with the new firmware or is the cause of the sensor problem the wrong UneUI 5 firmware? If the latter one is true, could installing your firmware solve the issue? If not, I'll just flash the old Samsung Android 12 again.

Thank you for your help and lots of fun developing this ROM!
[Samsung Galaxy A52 4G] Simon1511:
Using OneUI 5 firmware on 19.1 and early 20 builds can/will lead to those issues since at the time those builds were made official OneUI 5 wasn't released yet, which means the firmware on your phone (OneUI 5 firmware) is too new for those old(er) LineageOS builds. This has been fixed on the newer unofficial and official 20 builds though.

So in conclusion:

LineageOS 19.1: OneUI 4 firmware

Early unofficial LineageOS 20 builds: OneUI 4 firmware

Newer unofficial (from December and newer) and official LineageOS 20 builds: OneUI 5 firmware
[Samsung Galaxy A52 4G] bluKae:
This makes sense, thank you.

Does this mean, the gyro is supposed to work on your first official LOS 20 build? If yes, I guess using the firmware of original Samsung Android 13 is unsupported, so I'll need to install the OneUI 5 firmware of your repo.
[Samsung Galaxy A52 4G] Simon1511:
Yes, gyro should work just fine on official 20. It doesnt matter if you install official OneUI 5 firmware or the one from my repo, they're 100% the same, the one from my repo just doesn't require you to factory reset your phone.
[Samsung Galaxy A52 4G] bluKae:
That's weird... I'm running the latest official LOS 20 release and phyphox reports missing accelerometer, gyroscope, light sensor and magnetometer (and more, but those would neither work with Samsung Android 13) and Auto-rotate doesn't wanna work.

So I guess it's a bug.

Edit: It's not a bug, I could fix it by reflashing the persistent partition. (Tanks to Simon1511!)
[Samsung Galaxy A52 4G] Simon1511:
Do they not show up in AIDA64 either? If not, that sounds like a broken persist partition. Just download stock ROM, extract persist.img from it and flash that either with Odin or TWRP, after that your sensors should start working again.
[Samsung Galaxy A52 4G] Flyos:
Does anyone has a workaround when you're hit by the bug of sound coming out of phone instead of bluetooth headset? I tried other apps, just in case, but no luck.
[Samsung Galaxy A52 4G] ceoofacerbutnot:
Does this ROM run smoother than stock? I really don't want to trip Knox so tryna decide whether installing this ROM is worth it or not.
[Samsung Galaxy A52 4G] Simon1511:
Sorry, currently there is no workaround for that.

Yes, it runs smoother than stock ROM.
[Samsung Galaxy A52 4G] Rampler:
Today i have made a update via settings/system/updater. The LOS recovery still says version 19.1, although update recovery is set to on in settings..
[Samsung Galaxy A52 4G] Rampler:
From time to time i use my mobile for phone calls ;)

Everytime i choose a phone number from any contact, i have to wait few seconds until the dialing dialog appears. Does anybody have the the same experience?

I use only one sim card, second slot is for sd card..
[Samsung Galaxy A52 4G] Simon1511:
That's my "fault" since I implemented a check for dual sim to work with phone calls. Previously there was just no sound in calls with second SIM, so that fix is kinda neccessary.
[Samsung Galaxy A52 4G] Rampler:
After installing recovery manually (via odin), the version will be shown correct.
[Samsung Galaxy A52 4G] Rampler:
Is it possible to make it customiseable ? I think, most user's use SD card instead of a second SIM card.

The delay is very annoying.
[Samsung Galaxy A52 4G] Simon1511:
No, currently that's not possible.
[Samsung Galaxy A52 4G] MarioRS:
Hi Simon,

I appreciate the great job you have done to get this build running and your clear communication in this small bug.

As I'm travelling often by car, Bluetooth is important for me. Do you expect a solution soon or should I look for another phone?

Best regards, Mario
[Samsung Galaxy A52 4G] Flyos:
I used another phone call app, it solves the issue. There's one on F-Droid, "Simple phone" I guess it's called, worked very smoothly. Google Phone works well also.
[Samsung Galaxy A52 4G] Simon1511:
Im really not sure if i'll ever figure it out or not.
[Samsung Galaxy A52 4G] la3ev:
Probably a dumb question, but in the guide it states phone needs to be downgraded to android 12 before installing lineage 20, why is that ?
[Samsung Galaxy A52 4G] seam0nster:
I noticed there's a new update, is there a change log available anywhere?
[Samsung Galaxy A52 4G] Zedonite:
LineageOS Downloads

download.lineageos.org
[Samsung Galaxy A52 4G] MarioRS:
Thanx for the straight answer! Can I be of any help with e.g. testing?
[Samsung Galaxy A52 4G] Simon1511:
Thanks for noticing, I have fixed that now. Android 13 is required for LineageOS 20.
[Samsung Galaxy A52 4G] ethical_haquer:
Thanks for developing this ROM, Simon! I have been using it for a little while now and it works well. There is only one problem: the camera app doesn't appear to know the size of certain photos it takes. For example, every photo taken with the 64 MP main camera is supposedly exactly 73.22 MB large. All of the following info is from my A52 4G running your first official build of Lineage OS 20. When I copy the photos to my Linux computer I get the same results. Notice how the italicized cameras create photos that are both ginormous and the same exact size. As far as I know, each photo should be slightly different (as the 12MP and 5MP photos, and all videos demonstrate). Anyone else noticing this?

Camera App (Aperature) Settings: Ratio 4:3, Capture Mode - Minimize Latency, Enable OIS

All images are JPGs

12MP Ultra Wide:

Photo1:

Width 4000

Height 3000

File Size: 3.63 MB

Photo2:

Width 4000

Height 3000

File Size: 3.71 MB

64MP Main(Shown as 12.2MP):

Photo1:

Width 4032

Height 3024

File Size: 73.22 MB

Photo2:

Width: 4032

Height: 3024

File Size: 73.22 MB

Video1(5 Seconds):

Width: 1920

Height: 1080

File Size: 12.41 MB

Video2(5 Seconds):

Width: 1920

Height: 1080

File Size: 12.10 MB

5MP Macro:

Photo1:

Width: 2675

Height: 1932

File Size: 1.20 MB

Photo2:

Width: 2576

Height: 1932

File Size: 1.12 MB

32MP Back(Shown as 8.0MP):

Photo1:

Width: 3264

Height: 2448

File Size: 47.94 MB

Photo2:

Width: 3264

Height: 2448

File Size: 47.94 MB

Video1(5 Seconds):

Width: 1920

Height: 1080

File Size: 12.30 MB

Video2(5 Seconds):

Width: 1920

Height: 1080

File Size: 12.55 MB

UPDATE:

I just installed the "Open Camera" app on F-Droid, to see what the filesize was of photos taken from a different app, and...they are even bigger! Every photo I take with the Open Camera app is 96.22 MB large. Interesting how they also end in ".22".
[Samsung Galaxy A52 4G] Rampler:
Which steps i have to do for installing again original samsung stockrom (coming from LOS 20.0) ?

Is it enough to install the complete firmware from sammobile via ODIN ?

(A525FXXU4CWA2_A525FOXM4CVL4_EUX.zip)
[Samsung Galaxy A52 4G] ethical_haquer:
Just ran into another problem. A few days ago I updated to the latest official build (1-27-23). I used some apps after I updated it, and put it away. Then, a day later, my phone is temporarily bricked! The problem is when I press the power button, the phone display turns on, but I can only see the top bar; the rest of the display is black with a little white digital clock and time displayed. When I drag down from the top I can see the info expanding, but everything seems to be blocked by the black area. I thought I could reboot to fix the problem, but the power button isn't even fully working. I can press it to turn the screen on and off, but when I press and hold it the phone vibrates, the top bar dims, and the display turns off, not the phone. Apparently I'm not the only one that's had this happen, a quick search brings up this and this. Anyone have any ideas, only thing I can think of is let the phone die and reboot...

UPDATE (2-25-23):

It just happened again! This time I was granting Easer permissions, turned the phone off, go to use it a few minutes later and...the screen had the same issue as before! Look below at the second screenshot; you can tell it is different because the wallpaper and time/date are different. Thanks to @Ryzen5950XT I knew how to reboot it by holding voldown+power.
[Samsung Galaxy A52 4G] RisenID:
force a reboot by holding power and volume down
[Samsung Galaxy A52 4G] ethical_haquer:
Thanks so much, I just did and it worked, unlike holding the power button.
[Samsung Galaxy A52 4G] ethical_haquer:
@Simon1511 When I originally went to follow your instructions here, I was pretty surprised to see them say "Note: The following instructions require a machine running Windows 10 build 17063 or newer." I don't have a device running Windows, so I started searching for a workaround. I tried all kinds of things, including heimdall, JOdin3CASUAL, and WINE, but eventually found a solution here. I saw you were looking at this post, and I just recently posted this thread on using Odin on Linux, so I thought I would share it with you and anyone else here who doesn't have a Windows machine and needs to use Odin.
[Samsung Galaxy A52 4G] atahanacar:
I used Heimdall to get the pit file, and JOdin3 to flash. No need to use virtual machines and such. Just use their git versions, as older versions may not support "newer" phones.
[Samsung Galaxy A52 4G] ethical_haquer:
Tried using JOdin3CASUAL, but got errors about exceptions in threads, tried to fix it, but couldn't.
[Samsung Galaxy A52 4G] 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.
[Samsung Galaxy A52 4G] seam0nster:
I know it's not the ideal solution but you could fix this with macrodroid until it's fixed in the rom.
[Samsung Galaxy A52 4G] fartyfart:
Important notice:

in order to have data roaming, it absolutely has to be enabled in the stock OS before switching to LineageOS.

Yes, the instructions say

but it doesn't mention data roaming specifically.
[Samsung Galaxy A52 4G] JohnnyZin72:
pls help, i have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: "CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta", but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?
[Samsung Galaxy A52 4G] RisenID:
You are talking about a completely different phone from the one that this rom is for. The solution to your probolem however is to flash a patched vbmeta image.
[Samsung Galaxy A52 4G] Simon1511:
The first post in this thread says:

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.

Please consider reading before trying stuff meant for other devices on your phone.
[Samsung Galaxy A52 4G] SuperUser008:
Are there chances that it will be fixed? The macrodroid workaround does not seem to work, at least on my phone...
[Samsung Galaxy A52 4G] RisenID:
Touch the top of the phone to your ear and you wont face any issues.
[Samsung Galaxy A52 4G] Rampler:
Sarcasm on

.. or stop calling ..

Sarcasm off
[Samsung Galaxy A52 4G] MarioRS:
Dear Simon,

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

Best regards, Mario
[Samsung Galaxy A52 4G] Simon1511:
Im working on it.
[Samsung Galaxy A52 4G] MarioRS:
Many Thanx!
[Samsung Galaxy A52 4G] MarioRS:
Let me know, if I can be of any help with testing e.g.

All the best, Mario
[Samsung Galaxy A52 4G] 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
[Samsung Galaxy A52 4G] Rampler:
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
[Samsung Galaxy A52 4G] RisenID:
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.
[Samsung Galaxy A52 4G] mariusmauxy:
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.
[Samsung Galaxy A52 4G] 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?
[Samsung Galaxy A52 4G] 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...
[Samsung Galaxy A52 4G] Simon1511:
Please follow the instructions on wiki.lineageos.org.
[Samsung Galaxy A52 4G] SchwarzerAfri90:
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 😅
[Samsung Galaxy A52 4G] rien333:
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".
[Samsung Galaxy A52 4G] 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.
[Samsung Galaxy A52 4G] ethical_haquer:
So I guess AT&T will not work then? Are there not any workarounds?
[Samsung Galaxy A52 4G] Simon1511:
It won't work unless they still have 2G and/or 3G running. Sadly there are no workarounds for that.
[Samsung Galaxy A52 4G] 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.
[Samsung Galaxy A52 4G] ethical_haquer:
Okay, thanks for replying. So I see people on here that are talking about calls, so are there any carriers in the United States that don't require voLTE? If not, I guess I'll have to go back to stock :(. I finally reached the limits of using an open-source, De-googled Android phone. After flashing your build of Lineage OS on my phone (Thanks for building it), rooting it with Magisk, and installing only open-source apps on my phone, it was Samsung's proprietary implementation of voLTE that stopped me in my tracks. Messaging works, but not calling (the "Phone" app, and a different open-source phone app, crash after trying to make a call), when using an AT&T SIM card. Perhaps eventually there will be a solution to using voLTE on a custom ROM for Samsung devices, but until then, I will try my hand at De-googling and rooting the stock ROM.

Best regards,

@ethical_haquer
[Samsung Galaxy A52 4G] ethical_haquer:
Take a look at my post on this thread:

So far, you are the only other person I know who is having this issue. I even posted a thread on this problem, but know one replied. It's like, yeah, it's a nice camera app, but it's not even usable because of the size of the files. Right now I'm stuck using Open Camera because it has a better settings. I hope some Dev can fix this...
[Samsung Galaxy A52 4G] Flyos:
Thanks for sharing this (and sorry I missed your post). What I don't get is that Samsung's stock photo app is taking seemingly the same resolution/JPEG quality for the files and ends up with files roughly a hundred times smaller than both Aperture/Open Camera. I mean, I expect some level of hardware/software optimisation being lost with LineageOS, but this is... huge.

Anyhow, what is your config for Open Camera? Did you find a way to end with files of reasonable size?
[Samsung Galaxy A52 4G] ethical_haquer:
I know, it's crazy, are we really the only ones having this issue? Anyway, using Open Camera I can get ~5 MB photos by going to Open Camera, clicking on the "⚙️", then "Photo settings...", and then "Camera resolution". I have mine on "1280 x 720 (16:9, 0.92MP)", and get photos that are ~5 MB. I'm pretty sure, however, that this size photo is still huge in relation to how many megapixels (0.92) big it is. The only way I can get normal (i think) sized photos is to change, in the "Photo settings...", the "Image format" to PNG. Surprisingly, this creates an image that is ~19 MB large...at 16.04 MP (the largest photo size possible with a custom ROM on this phone). Compare this to 96.22 MB with a JPEG that has the same amount of MPs. WEBPs are similiar to PNGs in size, and both create files that vary slightly in size, unlike JPEG ones on this phone, which are always 96.22 MB (I say "on this phone" b/c this is not normally the case with JPEGs). I hope this info helps, and thanks for sharing your problem!
[Samsung Galaxy A52 4G] Simon1511:
Honestly from what I know VoLTE on Samsung devices running AOSP has been an issue for a loooong time (>6 years), and nothing has changed in that time. So the chances for VoLTE being supported in the future are.. low.

I honestly totally forgot about this.. Will check soon.
[Samsung Galaxy A52 4G] ethical_haquer:
Thanks for being honest. I will try to reflash the stock ROM, and then come back to this one after I get a different phone for phone calls. Also, do you know where to get the firmware for this thing? I looked online and found many websites that host them, including this one, but they only have ROMs with csc codes from other countries. My A52 is unlocked, and I'm in the U.S., so what one should I download?
[Samsung Galaxy A52 4G] Flyos:
Thanks. I played a bit with it. I discovered something very troubling. At the resolution I was at that time, Open Camera produced JPEG of 72MB, but then I asked Open Camera to save the RAW (DNG) file only: it was only 32MB! This is getting super weird. What could cause this?
[Samsung Galaxy A52 4G] ethical_haquer:
32 MB at how many MPs?