yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] xinouch:
@Simon1511 Thanks a lot for your work! This is a life saver for me (Samsung stock is awefully full of bloatware). Bye bye Bixby!

Everything works very smooth for me on my A525f, I only noticed minor bugs that I'll list below but nothing critical 🙂

If you can make encryption work, it will be perfect!

Minor bugs:

- Agenda stock app not working (I replaced it with the Etar app)

- Over reboot, the screen brightness setting seems to be forgotten (I like low brightness and I have to reset it after each reboot. The Adaptive Screen Brightness setting is correctly kept though)

- Over reboot, the icon shape settings is forgottent and reset to default (I prefer the Squircle option)

It seems to be more stable without Magisk (I had a few app crash with Magisk)

Generic questions:

- What camera app are you using? The default one doesn't work, the Google one is buged (off-centered). I installed OpenCamera and it works great but is a bit over complex
[Samsung Galaxy A52 4G] Simon1511:
The minor bugs you listed are probably related to lineage itself. It was still in an early state when I released this, so they have most likely already been fixed there.

What exactly do you mean with that? So far I've been using BSG and LMC for GCam.
[Samsung Galaxy A52 4G] xinouch:
Well I may not doing things the right way... I installed the GoogleCamera app from the PlayStore and here is what I get:
[Samsung Galaxy A52 4G] Simon1511:
Yeah thats not the proper way. There are various guides and configs to get GCam to work in the A52 Telegram GCam channel.
[Samsung Galaxy A52 4G] xinouch:
Thanks! I'll have look :)
[Samsung Galaxy A52 4G] ralanar:
Correct. The phone is an "SM-A525M/DS", and the Settings->About Phone screen shows that with a stock samsung rom. With your LineageOS build, Settings->About Phone displays "SM-A525F" instead.

I'll happily test anything. What is "pe" in this context?
[Samsung Galaxy A52 4G] RisenID:
My Pixel Experience build linked here

https://xdaforums.com/t/unofficial-rom-12-0-pixel-experience-plus-for-a52-and-a72.4434401/
[Samsung Galaxy A52 4G] ralanar:
@Ryzen5950XT Yes, your PE build also mis-identifies the phone as an SM-A525F.
[Samsung Galaxy A52 4G] RisenID:
Ahhh i see.. Thanks for testing!
[Samsung Galaxy A52 4G] ofeking06:
the proximity sensor fix now on lineage 19.1 on a52/a72 ?
[Samsung Galaxy A52 4G] RisenID:
Not yet, but it works on my pixel experience rom. Simon will update soon tho.
[Samsung Galaxy A52 4G] ofeking06:
yea i have pixel rom its working there
[Samsung Galaxy A52 4G] xinouch:
Cool, I just have to wait for the update from @Simon1511 then :)
[Samsung Galaxy A52 4G] Simon1511:
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:

-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
[Samsung Galaxy A52 4G] ralanar:
Can confirm model detection is much improved, my test phone is now showing "SM-A525M" under Settings->About Phone->Model. No-audio-with-second-sim bug is still present. Possibly related: Samsung's firmware showed model "SM-A525M/DS" rather than "SM-A525M", denoting the dual-sim capability.

Everything else has worked flawlessly so far, including the encryption. Thanks for the release! It's very nice.
[Samsung Galaxy A52 4G] xinouch:
Wow! Thanks a lot @Simon1511 !!! I'll test that in the weekend :)

The proximity sensor will be a life saver, especially during calls.

I have a dumb questions: as the device will be encrypted at first boot, do you recommend to do a fresh install, or is it safe enough to do a standard update? I don't mind doing the guinea pig here ^^
[Samsung Galaxy A52 4G] maxvav9813:
Hello, will the problem of screen blinking when using the push fingerprint scanner ever be fixed, especially noticeable in applications that use it for authorization?
[Samsung Galaxy A52 4G] Simon1511:
Yes, a fresh install (formatting data before first boot) is mandatory if you want to use encryption.

Likely not, as Samsung's FOD HBM implementation doesn't work on AOSP.
[Samsung Galaxy A52 4G] xinouch:
Just an input about the fingerprint sensor (but once again, I know nothing about it so it is pure speculations): I have the feeling that the samsung ROM increases the luminosity of the screen but only on the sensor part, in order to read the fingerprint.

I saw this solution in SO (which is a bit hacky as you increase the full screen luminosity but add a gray layer to hide it): https://stackoverflow.com/questions...ghtness-level-to-each-part-of-screen-activity

BTW, since you have all important features working now, are you still interested in making this build an official Lineage OS one, and if so how much trouble is it?
[Samsung Galaxy A52 4G] Simon1511:
Yes, official is still the goal. The only thing keeping me from official though is broken audio in calls with second SIM.

Also yes, on stock ROM Samsung light's up only the area around the fingerprint sensor, but I didn't get it to work on lineage (yet?).
[Samsung Galaxy A52 4G] ruslan_3_:
Hello

Simon1511​

Please help. Build Lineage, error "error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "android.hardware.power@1.3-service.samsung-libperfmgr" depends on undefined module "vendor.lineage.power@1.0""
[Samsung Galaxy A52 4G] RisenID:
Did u add device trees and device specific code to local_manifests
[Samsung Galaxy A52 4G] xinouch:
Hey! It seems latest NickGapps Canary are not working: it is messing with system_root so the device won't turn on after installation, and TWRP won't allow to do any further installation as it tries to backup some stuff before and fails with system_root...

Any idea how to easily get rid of this? I have formatted data and reinstalled TWRP with Odin but the issue is still here... Somehow the system_root folder and Gapps mess won't disappear.

Reflashing Stock ROM with Odin works but it takes ages...
[Samsung Galaxy A52 4G] xinouch:
So, I must do something wrong because it is impossible for me to boot in the new 19.1 version.

I did a full reinstallation, starting from freshly reinstalled Samsung Stock image. My steps:

- flash VBMeta + reboot to download

- flash TWRP + reboot to recovery

- format data + reboot to recovery

- wipe data + dalvik + cache

- install 19.1 + wipe dalvik

Here, the phone tries to start to system but fails for some reasons so it reboots to recovery. I haven't been able to make it work....

I have succesfully reinstalled last version with the same steps though, so I'm back on 19 :p
[Samsung Galaxy A52 4G] jahangirbsmrau:
Same things happened to me on my A72. I tried today several times but failed.
[Samsung Galaxy A52 4G] Simon1511:
You may have messed up the steps. You need to install lineage, install Gapps and then format data right before booting the first time.

Formatting data as the absolute last thing is mandatory, otherwise you will end up in a bootloop as you wrote above.
[Samsung Galaxy A52 4G] jahangirbsmrau:
Done exactly what you said but failed.
[Samsung Galaxy A52 4G] Simon1511:
It works just fine for me here if I do it in that exact order. Possibly check if it boots for you without encryption enabled (it did just fine for me too).
[Samsung Galaxy A52 4G] RisenID:
Anyone using the latest lineage build, could you test if you can hear the difference between dolby aatmos on vs off? Trying to see if theres a bug on PE or not.
[Samsung Galaxy A52 4G] ofeking06:
the ota update work good on lineage 19.1 for galaxy a52/a72?
[Samsung Galaxy A52 4G] Simon1511:
If you disable encryption, yes. Otherwise a clean flash is needed.
[Samsung Galaxy A52 4G] AltugGND:
In the morning the alarm does not ring, the phone does not wake up.

Lineageos 19.1 / Galaxy A52
[Samsung Galaxy A52 4G] xinouch:
This is strange, it works well for me...

Though, when I get called, my phone doesn't wake up neither. I succeeded to make it work at one point, but it doesn't work anymore... Can it be related?
[Samsung Galaxy A52 4G] EPTIOS:
Hello, I loved this LineageOS ROM, however, I have a question. Is it possible to upgrade from May patch version 19.1 to future updates without losing phone files?

Sorry for the bad english, i'm using translator.
[Samsung Galaxy A52 4G] EPTIOS:
How to disable encryption?
[Samsung Galaxy A52 4G] EPTIOS:
And updates will come via OTA?
[Samsung Galaxy A52 4G] Simon1511:
Yes, upgrading should work fine.

Read the installation instructions in the initial post, the instructions to disable encryption are listed there.

No, not as long as this ROM is unofficial.
[Samsung Galaxy A52 4G] EPTIOS:
Thanks for answering my queries! :)
[Samsung Galaxy A52 4G] King'z:
I have the same issue, I already had the previous version of the rom installed then through TWRP I just flashed the the latest version, formatted data and rebooted and the same thing happened, reboots in vain then reboots again into recovery. I tried to wipe the caches but in vain as well, although it boots successfully without encryption.
[Samsung Galaxy A52 4G] Simon1511:
In the meantime I figured out what the issue is with encryption and came up with the following fix:

In addition to formatting the data partition you also need to wipe the metadata partition. Since our TWRP doesn't have an option for that I released new TWRP builds for A52 an A72 today with that feature enabled.

So install latest TWRP, install lineage, format data and wipe metadata. After that booting with encryption enabled will succeed.
[Samsung Galaxy A52 4G] xinouch:
So, I just tried to install with the last TWRP with wiping metadata after the install, and it works! Device is encrypted :D

Thanks a lot!!!

Also, it works well with Magisk 25.1

BTW the problem I have with the calls (no possibilities to answer) is still here, even after the reinstall and default settings... Am I the only one?

I've found a work around: when I get called, I call someone. Thus I have a popup saying I can't call now (because I am being called), and it makes the call notification appear, so I can answer \o/
[Samsung Galaxy A52 4G] Simon1511:
Hey people, I've been working on another update with some great changes!

The biggest changes in this build are the following ones:

1. I finally got audio with 2nd Sim card in calls to work!

2. The fingerprint sensor on Galaxy A72 is now working, thanks to...

3. Fingerprint dimming combined with Samsung's HBM!

Some may remember that I said earlier that it's likely not possible to make Samsung's fingerprint implementation in-kernel work on AOSP, though after spending my past few weeks on this I finally got it to work! The screen will now only light up the area around the fingerprint sensor instead of the whole screen (which was pure pain before, I know) and will partially dim the screen. Thanks to this the sensor on A72 works now! However you may need to hold your finger a bit tight to the sensor sometimes.

Also, the screen may flicker a little bit during fingerprint setup or unlocking, but I'm sure I'll get this sorted out in the future.

Downloads: A52 | A72

Changelog:

-June security patch
-Switched to using Samsung's HBM implementation instead of lighting up the whole screen when touching the fingerprint sensor
-Dim the screen if touching the fingerprint sensor
-Wake the screen if touching the fingerprint sensor during screen off or AOD instead of killing doze
-Fixed fingerprint sensor on A72 by dimming the screen (You may need to hold your finger a bit tight on the sensor)
-Correctly reset brightness on fingerprint errors
-Fixed the screen not turning on again if removing the phone from your ear during a phone call
-Added custom audio impl to fix audio in calls with Sim 2
-Disabled Dolby again (doesn't seem to work correctly for us)
-Re-enabled doze/deepsleep support
-Show correct fast-charging values
[Samsung Galaxy A52 4G] xinouch:
Congratulations and thanks a lot for the new release!

Just some dumb questions about how to install:

- If we do the update from an already encrypted 19.1, do we need to wipe / format /data and metadata?

- Is it possible, with encryption enabled, to do a backup of /data anyway and restore it with TWRP? (I know TWRP can't mount data, but maybe it can sort of memcopy it?)
[Samsung Galaxy A52 4G] Simon1511:
No need to wipe anything.

In terms of backups, they should work once TWRP supports decryption for Android 12, which should hopefully not take very long.
[Samsung Galaxy A52 4G] RisenID:
Ultra pro max dev.
[Samsung Galaxy A52 4G] ralanar:
Dual sim support works great! Thanks a lot for your work.
[Samsung Galaxy A52 4G] Moritz_pro:
The Rom won't start, the start sign appears but doesn't finish loading.

What can I do please help me.
[Samsung Galaxy A52 4G] RisenID:
Did you use the proper recovery or flash the service disabler
[Samsung Galaxy A52 4G] Moritz_pro:
the service disabler because the proper recovery didn't work.
[Samsung Galaxy A52 4G] RisenID:
Did you flash the disabler immidiately after the rom or did you reboot between the 2 things
[Samsung Galaxy A52 4G] Moritz_pro:
https://xdaforums.com/t/can-not-boot-any-more.4462175/#post-87128559

I flashed the twrp but it didn't work so i installed a new image I don't know the name but then I could boot into recovery mode then I couldn't boot to the system amore so i flashed service disabler now I can boot but I doesn't load.
[Samsung Galaxy A52 4G] Moritz_pro:
I installed this file with Odin
[Samsung Galaxy A52 4G] Simon1511:
Well, I would suggest you to follow the installation steps properly.

If you do that then you won't have any problems installing this ROM.
[Samsung Galaxy A52 4G] Peter_Petersen:
Hello together and hello Simon1511!

After so many years with our GS5 G900F (my family and me) we switched to the A52/4G 6GB/128GB, bacause it is a very good smartphone with a recognized developer for LOS in the background.

Thanks for your work and support!

Questions:

- in TWRP there is no 'system' partition, how do i do a full wipe to installiert LOS 'clean'?

- i update LOS 19.1 20220530 to 20220704 and after that, everytime i reboot i got back to TWRP. Do i habe to wipe data and metadata (updated TWRP) or only metadata?

- do you planning a support for the original Samsung S-View Cover? (GS5 it called flip-flap)

Bugs!?

- everytime i sit in the sun the display switches between brightness max to brightness min continously

That's enough for the first time...

WBR

Danny
[Samsung Galaxy A52 4G] Simon1511:
1. There is no system partition because this device uses dynamic partitions that can't be wiped directly. However dirty flashing any ROM on top of LineageOS will have the same effect as wiping system.

2. You don't have to wipe neither data nor metadata if updating from an older build. I can't blindly say why it's bootlooping for you, but for me dirty flashing worked fine.

3. Thanks for reminding me about that one, I'll hopefully get it fixed later on.
[Samsung Galaxy A52 4G] Moritz_pro:
I installed the VBMeta disabler but it still not works
[Samsung Galaxy A52 4G] Moritz_pro:
Sorry I am supid andI can't read sorry for wasting your time.
[Samsung Galaxy A52 4G] Moritz_pro:
Now I need you again. It worked, but I wanted to install Gapps too, but now it won't boot like before and when I do format data It says done but also Failed to mount '/system_root' (No such file or dictionary)

Download GApps for Custom ROM - (All Versions)

Install GApps for Android 14, 13, Android 12, 11, 10, 9. How to Flash Google Apps on LineageOS ROM. Open GApps Project Google Drive Links 2024.

www.droidthunder.com
[Samsung Galaxy A52 4G] Simon1511:
Those are Gapps for Android 12.0, but you need ones for 12.1. Check the first post of this thread, there are several different Gapps variations linked.
[Samsung Galaxy A52 4G] Moritz_pro:
have I to delete the wrong one (becuase it stucks again in the start animation) if yes how.
[Samsung Galaxy A52 4G] XThePravatoX:
I'm stuck in download mode loop, I've reached the point of updating TWRP from 3.5.0 to 3.5.2, but after unplagging and restarting with Down+Power it goes back to Download mode, where I proceed to flash the vbmeta_disabled.tar(AP) from Odin.

And even after this, unplugging and restarting it does still go back to the Download mode.

How can I unstuck my smartphone?
[Samsung Galaxy A52 4G] Simon1511:
First start with the correct TWRP version and follow the instructions there.
[Samsung Galaxy A52 4G] medoko:
Im not quite sure how to decide on the encryption...

Are there - besides the "my data is more safe/unsafe" - any disadvantages if i choose to encrypt (or the other way around, not to encrypt)?

To be more precise: TWRP (and i will use the A52 version of it from SImon1511): Can i backup and restore my phone with an encrypted phone ?

In some other LOS ports / projects (2 years ago) this wasnt possible ...
[Samsung Galaxy A52 4G] Simon1511:
Not really, the additional security is the only advantage.

Currently not since TWRP hasn't officially been updated for Android 12 encryption yet. If you're seeking to heavily backup and restore I would advise you to not use encryption.
[Samsung Galaxy A52 4G] medoko:
I already thought that this would be the answer. Thanks for the confirmation.. I will (sadly) stay un-encrypted ...
[Samsung Galaxy A52 4G] Peter_Petersen:
Hey Simon1511,

does split screen work for you?

In my case, double tap on home button, nothing happend. Long press on recent button, the same.

Settings are made in button menu.

WBR

Danny
[Samsung Galaxy A52 4G] xinouch:
So, this is what I do:

press on the "recent" button (the square)

long press on the icon of the app I want to split

tap on "show on top" or "free format" (I have it in French, may not be the exact English terms)

I think this behavior comes with the new gesture / no button feature.
[Samsung Galaxy A52 4G] kanopusbr:
Does the camera have stock rom functions?

stabilization and expanded field of view.
[Samsung Galaxy A52 4G] Simon1511:
The default camera app doesn't, but GCam is fairly close to stock camera.
[Samsung Galaxy A52 4G] Simon1511:
Hey, just released another update with some nice fixes.

Also, you can find unofficial builds of TWRP with en-/decryption support in the download section!

Downloads: A52 | A72

TWRP: A52 | A72

Changelog:

-Updated blobs to A525FXXU4BVG1 respectively A725FXXU4BVE3
-Implemented proper screen-off-fod support (Settings->Display->Lockscreen->Long press fingerprint sensor....)
-Improved FOD dimming values
-Imported HotwordEnrollment blobs to fix "OK Google"
-Switched to OSS camera provider
-Slightly decreased vibrator intensity
-Enable correct reading mode in LiveDisplay
-Add Dolby audio effect (Actually works this time)
-Excluded AudioFX to improve Dolby effect
-Built FlipFlap to fix flip covers (Thanks for reporting @Peter_Petersen
-Corrected brightness for SunlightEnhancement mode in LiveDisplay
-Built AdvancedDisplay for advanced display modes
-Set ZRAM size to 5GB to improve performance
-Switched to CAF USB audio configuration to fix audio in phone calls with USB headphones/headsets
-Enabled pickup gesture support
[Samsung Galaxy A52 4G] mariusmauxy:
Hi , i respect you work, you are doing a great job.

I haven't been doing this for 3 years now, so i must ask, what should i do to install the new build?

To be more specific, do i need to wipe something in twrp? ( sorry for noob questions)
[Samsung Galaxy A52 4G] Simon1511:
It's enough to just flash the new build without wiping anything if you have encryption enabled (It's enabled by default).

In case you flashed the services disabler you will have to flash that again.
[Samsung Galaxy A52 4G] mariusmauxy:
I don't know if i have encrption enabled, but i did flashed service disabler first time. thank you for you help.
[Samsung Galaxy A52 4G] nikolamus:
update good but camera make too bad picture very small megapixels
[Samsung Galaxy A52 4G] nikolamus:
picture megapixel must be 9000 6000
[Samsung Galaxy A52 4G] mariusmauxy:
I've notice that every time a make a call, it takes about 8-10 to initialize. Does anyone else has this issue?
[Samsung Galaxy A52 4G] Simon1511:
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.
[Touch HD General] ofiaich:
Hi!

I am wondering what languages will be likely to be present.

I just sold my iPod Touch and did find the Japanese input to be very good. I am hoping the same will be available for The HD !

On my TyTn II, I use CE-Star and have used Asukal's software, but I do hope Japanese is easy to 'call up'!

Any opinions welcomed !

Ofiaich :)
[Touch HD General] Luotyt:
Why not flash your phone in japan's ROM
[Touch HD General] ofiaich:
Hi,

I was thinking that, and yes, done a lot of reading but not flashed a rom before.

I am not sure if a Japanese rom offers full functions. I think the Japanese EMobile Kaiser is not fully functional and has many things disabled.

I do not necessarily need the menu's to be in Japanese.

Ofiaich :)
[Android Q&A, Help & Troubleshooting] yuri624:
I had an old 2011 MacBook Pro 13" that was broken. I tinkered some with it and converted the internal Trackpad and Keyboard to usb (using the original circuit).

On Windows (PC + Surface Pro 6): Works (trackpad works "only" was mouse, but works)

In my PC BIOS: Works

On MacOS (VM + MacBook Pro 2007): Works (trackpad works including all multi-touch gestures)

On Linux (Ubuntu): Works (trackpad works including multi-touch gestures)

Android 11 (Lenovo P11 Pro + Android X86 on PC): Only keyboard, no trackpad.

Android 10 (Samsung Galaxy S9 + Android X86 on PC): Only keyboard, no trackpad.

Android 9+8 (Android X86 on PC): Only keyboard, no trackpad.

I installed an Android app called "USB Device Info" and when connecting my keyboard/trackpad combo it correctly shows up as "Apple Internal Keyboard / Trackpad" (same as in Windows/MacOS/Linux).

Anyone here has an idea how to port the Linux driver (I read something about porting a Linux Kernel space driver to Android User Space?) to Android?

Or any other ideas? Cheers!View attachment 5463637
[Android Q&A, Help & Troubleshooting] yuri624:
So I still have no fix. But as if this wasn't enough... I now tried if it works on all the operating systems in a virtual machine.

Surprise surprise: Windows VM works, Linux VM works, MacOS VM works, Android_x86 VM...... WORKS.

It works in the VM but not native (used the same image)??? HOW? What kind of sorcery is this? Please help... Cheers
[Android Q&A, Help & Troubleshooting] yuri624:
I dug out the file for the driver (Apple USB BCM5974 (Macbook Air and Penryn Macbook Pro) multitouch driver):

https://android.googlesource.com/ke...id-goldfish-3.4/drivers/input/mouse/bcm5974.c

Apparently this is included in Android since 2013 and it offers functionality for exactly my trackpad model.

I'm desperately looking for help on this ;/
[Android Q&A, Help & Troubleshooting] yuri624:
Some time has passed and in the meantime I got a rooted Samsung Galaxy S10+ with Android 12 (also tried before on 11), but it's the same behaviour. Keyboard works, trackpad not at all.