yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] Simon1511:
Update

14-11-2022: A52 (MEGA) | A72 (MEGA)

Changelog

-Latest LineageOS sources with November security patch
-Switched to using latest clang
-Switched to R RIL blobs to fix signal strength indicator
-Replaced LineageOS livedisplay display modes with AOSP display modes
-Added tap-to-show AOD setting (Settings->System->Gestures->Touchscreen Gestures)
-Improved auto brightness behavior with high screen brightness
-Selinux Enforcing
-The stock camera app now supports using aux cameras (ultrawide, macro, tele cameras)
-Limited proximity sensor range in which the sensor activates when touching the screen
[Samsung Galaxy A52 4G] weim1:
Rom runs really good on A72 but the fingerprint sensor stopped working all of a sudden. Is it common?
[Samsung Galaxy A52 4G] SuperUser008:
Done that with adb. Unfortunately the same error with the corrupt data appears and the phone starts in recovery...
[Samsung Galaxy A52 4G] Simon1511:
I'm honestly out of ideas then..
[Samsung Galaxy A52 4G] SuperUser008:
No worries. I finally did factory reset. For the most data I have backups. At least I have a working phone again with LineageOS. Thank you very much for your support.
[Samsung Galaxy A52 4G] e1d3rx:
Hi everyone, i'm not a native english speaker so i'm using Google Translate in case i misspell something and if do, i'm sorry.

I've got a question, here it says "Make sure you are on OneUI 5"

I am in OneUI 5.1, can i still install it in this version?

Thanks.
[Samsung Galaxy A52 4G] Simon1511:
Yes, OneUI 5 is just the minimum required version.
[Samsung Galaxy A52 4G] sxjg23:
there's a bug (tested on latest lineage-20.0-20230601) that still exists since a long time:

when switching between users, if the user has a pin as screen lock, the brightness is at minimum.

unable to see when there's sunlight.
[Samsung Galaxy A52 4G] Simon1511:
I have another great set of news!

This weeks builds will have following changelog:

Increased vibration patterns and working vibration control in Settings

Properly fixed BT phone calls - works just like on stock ROM now

Properly fixed VoIP calls (bluetooth VoIP calls work and speaker and earpiece arent swapped anymore; no weird lags or sound issues anymore)

Addressed a few SeLinux denials

Slightly better USB configuration

Updated vendor blobs and fingerprint to A525FXXS5DWD1 respectively A725FXXS5DWD2
[Samsung Galaxy A52 4G] wojtekojtek:
Cool! I installed it before this update and I want to ask you something:

1) when AOD was enabled and it was showing clock, after some time it showed green artifacts, idk what it was.

2) it is possible to add weather on lockscreen and AOD like in PixelExperience+?

3) How to port samsung apps, like camera, I miss it so much..., or what config should I use on gcam to make it working like stock

Anyways, good work !! ^^
[Samsung Galaxy A52 4G] Simon1511:
Are you on the latest stock firmware? Other people reported this too and fixed it by updating to the latest firmware.

There might be apps for that on the Play Store, however that's just a guess.

You can't. Especially Samsung Camera won't ever work since it highly depends on Samsung specific framework stuff. Some apps (and only some) can be installed from Play Store though.
[Samsung Galaxy A52 4G] wojtekojtek:
1) I was on latest ( after discovering this bug I just switched to ncx rom)

2) I tried to find some, there was also xposed one but it was outdated, these without xposed were showing it using notifications, I dont like it.

3) I need only samsung camera, but if its not working... I will try to live without it ☺️

edit:

Thanks for fixing fingerprint light!

It was very annoying! :D

I have another issue -

my phone is overheating... :<
[Samsung Galaxy A52 4G] MacBez:
I'm just not using it because I can't certify the device in the playstore
[Samsung Galaxy A52 4G] ethical_haquer:
Check out @Displax's Universal Safteynet Fix. If you install GAPPS of some sort and this, you should be able to pass SafteyNet. Let me know if you have any questions and want more detailed answers. You were talking about passing SafteyNet/Play Integerty API, right?
[Samsung Galaxy A52 4G] MacBez:
but if i don't install GAPPS i won't have play store. How can I install my apps?
[Samsung Galaxy A52 4G] ethical_haquer:
I recommend installing BiTGApps. Let me know if you want more info. :)
[Samsung Galaxy A52 4G] MacBez:
Do I need to install magisk and pass the safety model to be able to certify the device in the playstore? Would it be possible without root?
[Samsung Galaxy A52 4G] ethical_haquer:
What exactly do you mean by

Sorry, I don't use it myself! :)
[Samsung Galaxy A52 4G] atahanacar:
I'm having problems with the fingerprint unlocking the phone by itself in my pocket. I don't know if this is a hardware issue or a problem with this rom, but it started happening very recently. I only realized it today. Does anyone else also have this issue?
[Samsung Galaxy A52 4G] Flyos:
Yes, you would need Magisk. I don't think it can be done without root!
[Samsung Galaxy A52 4G] amaicock:
Same. I don't know how it's happening
[Samsung Galaxy A52 4G] Geitekont:
Hello, I have a question. I can't enable my NFC; the switch button for NFC stays greyed-out, and I can't activate it by swiping it to the right.

I flashed the latest LineageOS version, lineage-20.0-20230630-nightly-a52q-signed.zip, along with NikGapps-full-arm64-13-20230627-signed. My TWRP version is 3.6.2_12-0.

Additionally, I flashed vbmeta.img (found on the same download page as the LineageOS file) using Odin after installing LineageOS. I hoped that flashing vbmeta.img would solve my NFC problem, but I didn't realize that I probably needed to flash vbmeta beforehand. I searched the internet for a solution, but I couldn't find one, so that's why I'm asking here.

Thanks in advance.

Small update: i thought lets give Pixel Experience a try see if NFC works, got a error installing it. I am not using android 13 based firmware. Is there a way to flash android 13 based firmware ? Or do I need to go back to Samsung's software again to accomplish it?
[Samsung Galaxy A52 4G] Simon1511:
Please follow this guide on the LineageOS website to update your phone's firmware to the latest Android 13 based stock firmware and give me a short feedback if NFC works afterwards.

Also just to make sure, you are indeed trying to enable NFC, and not Android Beam? Android Beam has been deprecated for longer now but Google still left the option there, even though it doesn't work.
[Samsung Galaxy A52 4G] Geitekont:
Tx man that did the trick. NFC is working now. Again tx :)
[Samsung Galaxy A52 4G] SuperUser008:
Hi,

does the built-in screen cast work?

An iPhone works with the same TV, same network over AirScreen, so there must be something with the A52 device.
[Samsung Galaxy A52 4G] NRG-ONE:
Hello, I joined here, because I was looking for a used phone in good condition that was relatively recent and was specially compatible with LineageOS 20, and at the same time it was supported for VoLTE by all the phone operators in my country (I live in Italy), since I don't have fiber, my choice based on what was found fell on the Samsung A52 4G (SM-A525F) and I didn't expect, having found it in the lineageOS site officially supported, to encounter what happened to me...

I installed from the official lineageOS 20 site, after I had updated as the guide says to the latest version of Android 13 with ONE UI 5.1...

I used Odin as the guide explained, and I was able to install everything...

WHEREAS, with ONE UI 5.1 the VoLTE and VoWIFI were working, but after installing LineageOS, only VoLTE kept working for me, while the VoWIFI function was no longer tracked in the phone with the same carrier...

I have a second SIM that was working with Volte but in this second SIM that I put in only after installing LINEAGEOS, the Volte stopped working...LTE appears but when calling the call switches to 2g...

While with the first SIM (Very Mobile) the volte kept working... BUT...

Unfortunately with both SIMs plugged in I immediately encountered problems with the phone's dual sim management because if I wanted to deactivate one then they would no longer reactivate and I would have to either reboot or reinsert the SIMs which with ONE UI instead I could deactivate and activate either SIM as often as I wanted...

I know it is often recommended in cases there are problems to do a factory reset of LineageOS...

Well after the factory reset even my princiapal SIM (Very mobile) lost the VoLTE of the operator.... when I call, the call automatically switches from LTE (4G) to 3G...

I'm desperate because I had gotten this phone specifically because it was in the lists of all operators in my country compatible with their VoLTE services and I need it so much because I can't work without.... using the pc only in hotspot with the phone...

How can I do this? Is it possible to reinstall original ONE UI 5.1 or should I throw the phone away!!!?

I hope you understand that before at least with the SIM with which I had installed lineageOS the VoLTE had continued to work... but the factory reset ruined everything! I did not expect it.... what can I do?

Thanks to those who can help me, sorry for my bad English....
[Samsung Galaxy A52 4G] ShaDisNX255:
Unfortunately for you, VoLTE and VoWiFi do not work on AOSP ROMs on Samsung devices

This has been the case for years now.

It's included in the bug list, please make sure you read through it again
[Samsung Galaxy A52 4G] NRG-ONE:
Thank's for your answer...but, about what you said i learn it only now because i found this post only after the issue... because in the guide on the official LineageOS site for Samsung A52 and LineageOS 20, it said that you just have to make sure that the VoLTE works and used at least in place on ONE UI, otherwise it would be lost... in fact to me the VoLTE worked after installation at least on the SIM I had inside when I installed...

So it didn't say in the official guide for lineageOS20 that it couldn't be done... that's why I trusted.

So, it's there a way to reinstall the original firmware by samsung with the original ONE UI 5.1 rom?

I see that there is a site as the next that enable to download it:

Samsung Galaxy A52 Firmware Download SM-A525F HUI Free Download

Samsung Galaxy A52 Firmware Download SM-A525F Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com
[Samsung Galaxy A52 4G] ShaDisNX255:
I don't know where you got this information

According to LineageOS's GitHub, VoLTE isn't a requirement to be considered Official

Only calls, text, data and emergency calls which are all still possible in this phone

You can check here: LineageOS Official Device Support Requirements

I'm almost certain that if anywhere in Lineage's website you read about VoLTE being required, Samsung devices are excempt since VoLTE doesn't work on any Samsung device in Lineage

This has been the case for years now
[Samsung Galaxy A52 4G] ShaDisNX255:
Yes, you can flash official Samsung firmware using Odin

There should be plenty of guides in Google and YouTube on how to do this, since it's the same method across all Samsung devices
[Samsung Galaxy A52 4G] NRG-ONE:
You are giving me hope, but excuse me if I insist, are you sure it can be done after unlocking the phone and rooting it without brick the phone? Because I had read on a thread (I think on REDDIT) that it was no longer possible to go back with this model, due to Samsung's control restriction... ?!?

if you confirm me positively I can go back to the original samsung stock rom (I used Odin to flash LineageOS 20) and with the "volte"active I can try to return to LineageOS 20 again without doing the factory reset that had deleted the VoLTE..
[Samsung Galaxy A52 4G] Simon1511:
As ShaDisNX255 already said, VoLTE and VoWifi have been broken on Samsung phones for an eternity and will probably stay broken.

Same thing as with VoLTE/VoWifi. This has been broken for years too and has never been fixed by anyone.

No, that's not true.

You can always revert to stock ROM, however Knox-related features (such as Secure Folder, Samsung Health, Secure Wifi, Samsung Pay) will forever be broken, even if you flash the original firmware and re-lock the bootloader. That happens since there is a small eFuse on the motherboard that gets tripped once you flash custom firmware. So it would probably not make much sense to sell the phone again as it will never be in its full "stock" state again.

To flash the stock ROM, simply download the firmware from any website (like samfw.com) or download it with a tool like Samloader or Frija or similar. Extracting that firmware file will then give you several files which you'll need to load into Odin in the respective buttons/tabs and wait for it to finish flashing.
[Samsung Galaxy A52 4G] NRG-ONE:
Thank you very much for all your explanations... so can I use TWRP recovery for samsung A52 4g With ONE UI 5.1 and all android 13 based roms as LineageOS 20?

Because on TWRP site they write that it's since android 12 but I seen a youtube video where they used Twrp to install lineageOS20 on a samsung A30...

For me working with ODIN is very uncomfortable... but reading the guide on lineageOS site, it was suggested only odin with windows pc to work...

Regarding to come back on stock rom is only for Volte, i need it... it's indispensable for me... once "VoLTE" is come back i can try to pass again to lineageOS hoping that "Volte" remains active as last time since i deleted it with a factory reset... do you think isn't a good idea?

excuse my bad english...
[Samsung Galaxy A52 4G] Simon1511:
As the TWRP guide says, Android 11, 12 and 13 are supported.
[Samsung Galaxy A52 4G] NRG-ONE:
thanks again, but if I start from my situation. from unlocked rooted phone with lineageos installed, i can use ADB shell from my mac to install TWRP?

su

dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery

Is it correct way to install directly TWRP on my SM A52 and after that I can use it to install from phone without a pc-mac also the stock ONE UI rom?
[Samsung Galaxy A52 4G] Simon1511:
Yes, that works, as long as you have root access on the phone.

The correct way to install TWRP would be to flash it using Odin, however the dd way works too.

However, installing the stock ROM only works with Odin. You might have luck with Heimdall on your Mac, but Heimdall is.. lets say mostly not easy to get to work.
[Samsung Galaxy A52 4G] xinouch:
For your information, after updating to latest LOS lineage-20.0-20230721-nightly-a52q-signed.zip, Signal was not working anymore. It acted as if it didn't have internet access (even though it had!). Rebooting did nothing.

I had to update the latest NickGapps 20230716 and after it worked (I was on 20230529, and I am using Core version).

IDK why and I wonder what happens if you don't use Gapps...

EDIT: Actually, it may be the update of TWRP that fixed it as I did both at the same time...
[Samsung Galaxy A52 4G] ULTRA90:
can anyone make a guide for galaxy s23 ultra?
[Samsung Galaxy A52 4G] ShaDisNX255:
You are in the wrong thread
[Samsung Galaxy A52 4G] ethical_haquer:
This is a custom ROM, Lineage OS, for the A52 4G and A72. What do you mean, you want to do something to your S23?
[Samsung Galaxy A52 4G] ULTRA90:
i want to install lineage in my galaxy s23 ultra
[Samsung Galaxy A52 4G] ULTRA90:
Ok sorry..
[Samsung Galaxy A52 4G] Simon1511:
As already pointed out by others, this thread (and forum) are for Galaxy A52 4G and A72, and not Galaxy S23 Ultra. LineageOS for A52 4G and A72 only works on these two phones and not on anything else. Please refer to the Galaxy S23 Ultra forum here for S23 Ultra specific Mods, ROMs, etc.
[Samsung Galaxy A52 4G] xinouch:
Since last update, it is possible to unlock the phone with fingerprint from the lock screen, turned off screen AND (this is new) the ambiant display 😁

Thanks for all the work!
[Samsung Galaxy A52 4G] Simon1511:
Great news!

LineageOS' "new" Camera app (Aperture) will finally return with the next update! (Friday/Saturday)

Following issues have finally been addressed:

Pictures now have proper size (instead of always being 96mb per pic)

4k recording works now

Unfortunately I still haven't been able to figure out how to make 60FPS recording work, but I'm sure I will some day.
[Samsung Galaxy A52 4G] ethical_haquer:
I still can't wait to return to this ROM Simon! Nice work!
[Samsung Galaxy A52 4G] LordAdnan996:
Great news! Is camera fix in this 25.8 build or next?
[Samsung Galaxy A52 4G] Simon1511:
Yesterday I said it will return on Friday, which is today;)
[Samsung Galaxy A52 4G] jhonpellas:
I am very interested in trying this rom, I just unlocked the bootloader of my A52 and I am trying all the CUSTOM ROMs I find, I know that LinageOS is one of the best, I appreciate your enormous contribution to this community, friend!
[Samsung Galaxy A52 4G] Flyos:
I can confirm that the bug of large-size pictures is fixed with Aperture, but it still remains with OpenCamera. Anyone has an explanation for this? It's totally bearable of course, not complaining, but Open Camera allows for using the Wide Angle and Macro lenses which, as far as I can see, Aperture doesn't.
[Samsung Galaxy A52 4G] Simon1511:
That's because I reported the bug (huge JPEG sizes) to Google's CameraX support directly and they merged a fix into the CameraX framework.

So, unless OpenCamera updates to the latest CameraX release you won't get it fixed, in which case you'll probably have to wait for them to do it.

Aperture lets you use both Macro and Wide lenses too. They both just appear as another zoom level (see attached image; .6 is Wide, the second 1x is Macro).
[Samsung Galaxy A52 4G] Flyos:
OK, thanks for the details (and for the fix of course!).

Ooooh, I didn't realise that! I might not need Open Camera after all then! Thanks!
[Samsung Galaxy A52 4G] occ2008:
For me screen cast don't work unfortunately.

Its see the TV, trying to connect (I allow connection on TV on question) and no success.

Cast to PC (win11) suddenly works.

Wifi Direct (manually) with TV connects sucessfully. Screen Cast - no :(

P.S. Cast from this phone on Stock ROM (OneUI5.1) to this TV (LG WebOS) works perfectly.
[Samsung Galaxy A52 4G] atahanacar:
I have a problem. When the screen is "off", the fingerprint sensor still works which results in my leg being scanned multiple times and the PIN keypad coming on while the phone is in my pocket. It gets very annoying as random keys get pressed and the haptic feedback makes me assume I received a message or a call, or even worse random emergency numbers might get called. This used to not be a problem in previous versions because the fingerprint reader didn't work when the screen was "off". If possible, adding an option to disable the reader when the screen is off or on ambient display would fix this problem.
[Samsung Galaxy A52 4G] Flyos:
You can disable it in the configs: System > Gestures > disable something like long press on the fingerprint reader to wake up.
[Samsung Galaxy A52 4G] atahanacar:
That doesn't disable it if you use fingerprint to unlock. Edit: that setting only works with always on display disabled.
[Samsung Galaxy A52 4G] Flyos:
Hm, it does on my phone. I have to wake it up using the power button, then unlock it with fingerprint. With this option enabled, I can press my finger to wake it up and unlock it in one go, but it suffers from the pocket wake-ups you describe.
[Samsung Galaxy A52 4G] atahanacar:
Do you have always on display enabled?
[Samsung Galaxy A52 4G] Flyos:
No, it is disabled, sorry, I should have mentioned this.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Do you also have to actually use roaming before installing Lineage?
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Hi,

short version:

how can I check if my OS is using the camera X framework fixed version?

long version:

I installed eOS on a52q, a fork of LineageOS with microg. Their latest version is [e-1.15-t-20230917331436-dev-a52q.zip](https://images.ecloud.global/dev/a52q/e-1.15-t-20230917331436-dev-a52q.zip) which is Android 13 build on 2023 Sep 17 by them.

I am having camera issues with selfie recognition of Revolut (European bank) and the jpg too big. Before trying reverting to stock, installing LineageOS microg and recover all my data, I would like to check if my version is old and still not fixed, or if there something else behind my issues.

Also my eOS version is shipped only with OpenCamera, so I have no idea if Camera X is present.

Thanks

Luca
[Samsung Galaxy A52 4G] Simon1511:
It's not the OS that needs the fix.

The apps you're using need the fix, if they integrated CameraX. For example, you could pull Aperture.apk (default LineageOS camera app) from a lineage build and manually install it because Aperture has the fix applied. But that wouldn't automatically fix it for every app.

In the end it all comes down to app maintainers updating their apps to the latest version of the CameraX framework. Nothing we can do too much about.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Ok, nothing will change even if I switch to LineageOS since the issue is Revolut.

I made a log with MatLibre during the selfie recognition process and searched for "camerax" and "camx":

W/revolut.revolut(1820): Long monitor contention with owner CameraX-core_camera_1 (2489) at void android.hardware.camera2.impl.CameraDeviceImpl.close()(CameraDeviceImpl.java:1441) waiters=0 in void android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks.onCaptureStarted(android.hardware.camera2.impl.CaptureResultExtras, long) for 213msX

E/CamX (875): [ERROR][CORE ] camxnode.cpp:6372 FinalizeInitialization() Node::JPEGEncodeLiveSnapshotPreview_IFE0 maxImageBuffers(8) from link properties should be atleast requiredMaxImageBuffers(10). So replacing maxImageBuffers with requiredMaxImageBuffers

these are just some, but Revolut is using camera X.

Is there a way to find its version in the log?

Thanks
[Samsung Galaxy A52 4G] Simon1511:
You might be able to figure it out by decomping the app with Apktool and searching for it in the Smali code. But that's just a guess.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
I unzipped the apk pulled from my devices, searched for "camera" and got some interesting files:

androidx.camera_camera-core.version

androidx.camera_camera-view.version

androidx.camera_camera-video.version

androidx.camera_camera-camera2.version

androidx.camera_camera-lifecycle.version

inside all of them it's written only "1.1.0", while the latest stable is 1.3.0

So at least Revolut should update CameraX to see if this fix my issue. Now I can contact them again with something in my hand.

Thanks
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
auto brightness issue

when using the light theme in a darker environment, the brightness start to change rapidly up and down without reaching a stable value.

This does not happen with the dark theme or when the top of the screen has a dark colour. In my opinion, this means the light from the top of the screen is interfering with the brightness sensor. However, I did not have this issue with the stock ROM.

I attach 2 screencasts to show how the brightness value is changing (but the links expire in 30 days)

Lufi - Disroot file uploader

upload.disroot.org

Lufi - Disroot file uploader

upload.disroot.org
[Samsung Galaxy A52 4G] Simon1511:
This has been a known issue ever since I made AOSP run on this phone.

Until now I haven't found any workaround for this, and I'm unsure if I ever will.
[Samsung Galaxy A52 4G] ChocolateAdventurouz:
Not sure if it has been reported, or it is an issue from my side, but while WiFi hotspot is working normally, USB tethering won't. My PC would pick it up normally as a network device, but the phone (Galaxy A72) won't give any internet access either by mobile data or WiFi to it.