yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
I am using eOS, a fork of Lineage for microg, and I got the same issue, after their latest update.

I opened a bug on their repository attaching a log, which I do not understand since I am not a developer.

tethering USB no longer works after OTA update to e-1.16-t on Samsung a52q (#7452) · Issues · e / Backlog · GitLab

/e/ version: e-1.16-t-20231018342574-dev-a52q Device model(s): a52q Developer mode enabled: yes Device rooted: no Trackers blocker enabled: yes tethering USB...

gitlab.e.foundation

If you want to take a log try MatLibre
[Samsung Galaxy A52 4G] ChocolateAdventurouz:
It seems like a bug. It is trying to find something that simply doesn't exist, and it results in these errors from log (developer here lol)
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
I am also experiencing issues with the charge that sometimes does not start, it's not related to the cables or the chargers, a52q seems just "stuck"

as before, I opened a bug on eOS with the log

https://gitlab.e.foundation/e/backlog/-/issues/7493
[Samsung Galaxy A52 4G] Simon1511:
Sounds like charging control is enabled (Settings -> Battery -> Charging Control).

You can also check if software or hardware is to blame by checking if it charges on a PC, and by checking if MTP works while connected to a PC and charging "not working".

I'll also be taking a look at the USB tethering issue in the next few days.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Charging control is enabled with limit to 80%, next time I have the issue I try to change just that

Changing connection mode or charging devices (such a pc or a plug) does not start the charging.

MTP works fine but with no charging.

On stock I had no issues, but thing can breaks for sure so I cannot exclude an hardware failure at all without reverting to stock
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
With charging control enabled at 80% and battery level at 70%, I disabled charging control and the charging started. Enabled it again and the battery is still charging to 80%.

At this point, I do not believe it is an hardware issue, but you were right pointing to charging control
[Samsung Galaxy A52 4G] Simon1511:
Thanks for both your reports, I was able to identify the issue and just merged the fix: https://review.lineageos.org/c/LineageOS/android_device_samsung_sm7125-common/+/373013

USB tethering now works as expected. The next build (most likely releases on 13th) will have that fix included.
[Samsung Galaxy A52 4G] etmatrix:
I have a A72 4G with PixelExperience, I tried to writing mifare classic tag but doesn't work while read work well.

Has anyone ever tried to write a mifare with LOS 20?
[Samsung Galaxy A52 4G] Peter_Petersen:
hey together,

i have a big problem. since i eabled the 'color inversion' (i just wan't to see what's happened) under settings->accessibility->color and motion->colour inversion', my display is comletely dark.

if i restart (7 seconds power + volume down), the phone reboots and the screen switches off when the sim-card input appears.

i'm on los20-2023-12-04 with los-recovery.

up to here, the rom works PERFECT!!!

i have no idea, how to switch the colour inversion off. can i reset LOS without losing my data?
[Samsung Galaxy A52 4G] Simon1511:
This is an issue that I'm unable to fix currently.

As mentioned in this Reddit post you can disable Color Inversion using adb shell and a PC if you have ADB access enabled: Reddit Post

Sorry for the inconvenience.
[Samsung Galaxy A52 4G] Peter_Petersen:
hey Simon1511,

i read the reddit-post and tried to disabled the color inversion as desrcribed ist the post with the command 'adb shell settings put secure accessibility_display_inversion_enabled 0'.

i got the message '/system/bin/sh: settings: inaccessible or not found'.

usb-debugging ist disable in developer options and i have no chance to enable.

ok, since I knew that a new tile had been created in the drop-down menu, I tried in desperation to deactivate it blindly. unlock via fingerprint, pull down the drop-down-menu, swipe left and hit exactly the color-inversion tile. unbelievable!!! problem solved...

despite this, many thanks to all developer and tester for your work on LOS...
[Samsung Galaxy A52 4G] etmatrix:
I reply to myself, write mifare doesn't work on LOS 20 but works on samsung rom. Many other tags work read and write but mifare classic 1K no. It's absurd because it's just a command

Everytime with LOS something stop to work on my devices.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
eOS has been updated on 09 December, so tethering USB fix should be included.

Unfortunatley, tethering USB is still not working for me. Log provided

Thanks
[Samsung Galaxy A52 4G] Simon1511:
Sorry, but I only maintain LineageOS, not eOS.

Tethering works on my LineageOS builds (or at least did by the time I wrote the post above), but I can't really give any support for a ROM I don't maintain or that I didn't build.
[Samsung Galaxy A52 4G] etmatrix:
With PE original kernel and riseKernel on my A72, I have all sensors don't detect or doesn't working, Is it like this on LOS too?
[Samsung Galaxy A52 4G] Simon1511:
The sensors work just fine. Please use a more reliable App like AIDA64.
[Samsung Galaxy A52 4G] etmatrix:
Same situation:

No problem, maybe is PE or maybe something else. I switch to LOS, so when you will fix write mifare issue, will be more easy fix for me, I don't have to wait for the fix to arrive on PE. I installed PE only because it has google service integrated.
[Samsung Galaxy A52 4G] RisenID:
sounds like the persist partition is broken

try flashing this in recovery

as for ur mifare writing issue, all i have seen is you complaining it doesnt work. if you want simon or me to actually work on it, you will have to provide logs so we can actually look into it.
[Samsung Galaxy A52 4G] etmatrix:
thank you so much your persist fix the issue.

I have no idea how it could have been corrupted, perhaps when I restored PE.

I opened an issue on gitlab where I attached logs, Simon already know.

If you have suggestions I can test.

I tried after I restored persist but the issue still exist.
[Samsung Galaxy A52 4G] RisenID:
No problem, glad your issue got fixed.

Ah didnt see this at the time, did speak with simon tho, and as soon as fixes it on lineage, i will use his fix on pe as well.
[Samsung Galaxy A52 4G] m00ns0rr0w:
Hi,

just bought a used A52s and wanted to install LOS (probably). How far shall i update the running Android? Stay with the latest Android 13 and OneUI versions that are available? In the opening post the developer says:

Hm, just checked as i wasn't sure - Android 14 and OneUI 6.0 is already installed. Didn't pay attention. Is this a problem?
[Samsung Galaxy A52 4G] Simon1511:
This thread here is for the A52 4G, not for the A52s 5G (however I'm maintaining both of them). This is the correct thread: https://xdaforums.com/t/rom-13-0-encryption-official-lineageos-20-for-a52s-5g.4574453/

Yes, this is a problem. My LineageOS 20 builds for A52s only support OneUI 5. If your phone is already on OneUI 6 based firmware, your wifi and fingerprint will stop working on LineageOS 20. Unfortunately you'll have to wait until there are LineageOS 21 builds that support OneUI 6 firmware.
[Samsung Galaxy A52 4G] xinouch:
Hello, and merry Christmas / happy New Year!

I can't make RCS work in Google Message. It says "chat RCS connected" for my phone number, but whenever I talk with someone with RCS activated, it only sends SMS.

I also installed Google Carrier Services.

Any idea here? Can it be because LOS on Samsung devices doesn't support VoIP/WIFI?
[Samsung Galaxy A52 4G] Simon1511:
This could be it. However, I'm not very experienced with Google Messages / RCS at all, so it might as well be something different.
[Samsung Galaxy A52 4G] xinouch:
OK thanks. I'll try to investigate.

If anybody made RCS work, I'd be happy to know :)
[Samsung Galaxy A52 4G] RisenID:
I think google itself is having some issues with it, im having trouble chatting via rcs on my google pixel device as well. It keeps going to sms with no way to force rcs.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Hi,

I would like to update the firmware of my a525f eux.

Do the 3 files provided following the lineageos instructions work fine also on LineageOs forks like eOS?

Reading the thread it seems they have been got from the original firmware without any modification, so I assume they are fine, am I wrong?

Thanks
[Samsung Galaxy A52 4G] Simon1511:
Yes, they will work on eOS too.
[Samsung Galaxy A52 4G] parasympathetic_foresaid:
Updating to the latest Samsung firmware solved my USB tethering issue
[Samsung Galaxy A52 4G] xinouch:
Hello,

About updating the firmware: in the github repo, the last version is A525FXXS6EXA1, which is apparently a Android 14 build for Russia (see https://www.sammobile.com/samsung/galaxy-a52/firmware/#SM-A525F).

So, 2 questions:

Is it safe to install firmware for Android 14 while using this current LOS 20 version?

Should I take the last EUX version (I live in Europe) or can I take a Russian version (they seems to be more up to date)?
[Samsung Galaxy A52 4G] Simon1511:
Yes, you can install Android 14 firmware if you want. Though in my opinion there isn't really a reason to do so as Android 13 firmware works fine with any of the Android 14 ROMs too. I wouldn't necessarily update if there isn't any need for it.

The latest EUX version is still based on Android 13, whereas the Russian one is already Android 14. As far as I know there shouldn't be any issues using the russian one as it's the same phone, just with different regional configuration (preinstalled apps, CSC features, ...)
[Samsung Galaxy A52 4G] xinouch:
OK Thanks.

My current problem is that each time I update, the application Signal doesn't work and I need to do some hacky things that may or may not work, like rebooting, reinstalling Magisk, reinstalling GApps...

I was hoping updating the firmware may somehow fix this. I'll do some tests with the next week's update.
[Samsung Galaxy A52 4G] zupert:
I have the same problem!

Last time i tried everything. In the end, what worked is to force teminating the application, restart the phone, and open Signal again.

Not sure if it is something reproducible or some random thing though...
[Samsung Galaxy A52 4G] King'z:
Hi, does it support video output to a monitor using a USB-C to HDMI cable ? I have the Samsung A52 4G with Lineage OS 20.0 installed on it.
[Samsung Galaxy A52 4G] Simon1511:
This phone does not support HDMI output via USB-C.
[Samsung Galaxy A52 4G] SuperUser008:
Will there be a LOS 21 for this phone someday?
[Samsung Galaxy A52 4G] wojtekojtek:
No, a52 doesn't support video output.
[Samsung Galaxy A52 4G] Simon1511:
LineageOS 21 is now officially available!

A52 builds are already out, A72 ones will be later today or tomorrow A72 ones are out too.

That also means that LineageOS 20 is now end of life for this phone.

Link: https://xdaforums.com/t/rom-14-0-encryption-official-lineageos-21-for-a52-4g-and-a72.4657332/
[Samsung Galaxy A52 4G] xinouch:
Wow I didn't expect it this fast! Thanks a lot!!
[Samsung Galaxy A52 4G] aleks20151972:
hello. it costs crdroid 9.7 tell me if i want to put lineageos20 (13 android) then i need 1.date format 2.flash zip 3.clean up metadata and cache. right?
[Samsung Galaxy A52 4G] aleks20151972:
hello. it costs ctell me if i want to put pixelexpence(13 android) then i need 1.date format 2.flash zip 3.clean up metadata and cache. right?
[Samsung Galaxy A52 4G] aleks20151972:
When moving from one Roma to another how to install correctly? (crDroid on los or pixel 13android)
[Samsung Galaxy A52 4G] Simon1511:
All your questions are answered by "Installation Instructions" in post #1.
[Samsung Galaxy A52 4G] aleks20151972:
thanks
[Samsung Galaxy A52 4G] aleks20151972:
hello. tell me on lionege 20-21 sms coming with a delay? (for 5-6 minutes on CRDroid 9.7 with a delay) after payment in the store
[Samsung Galaxy A52 4G] thefallenghost:
Hi @Simon1511,

I am currently using your LOS 19.1 latest build and would like to upgrade to 20 on A52M/DS, but am not sure I understand how to do this by searching through this thread.

I am not used to flashing new images manually and am apprehensive of the idea of flashing the stock ROM first to upgrade to LOS 20 afterwards.

Could you please post exact instructions as to how to perform the upgrade from 19.1 to 20 and keep all data? I am using microg.

Many thanks,

Daniel
[Samsung Galaxy A52 4G] Simon1511:
All the information you need is on the lineage wiki.

First this: https://wiki.lineageos.org/devices/a52q/fw_update/ (note that depending on the firmware you flash you'll update to Android 14 bootloader/modem firmware)

Then https://wiki.lineageos.org/devices/a52q/upgrade/
[Samsung Galaxy A52 4G] thefallenghost:
=

This means in step #8 here https://wiki.lineageos.org/devices/a52q/upgrade/ I should flash magisk and then microg (and hopefully upgrade them before moving to LOS actually)?
[Samsung Galaxy A52 4G] Simon1511:
Yes and yes.
[Samsung Galaxy A52 4G] thefallenghost:
=

This means in step #8 here https://wiki.lineageos.org/devices/a52q/upgrade/ I should flash magisk and then microg (and hopefully upgrade them before moving to LOS actually)?

Sorry 2 more questions:

1) I have TWRP as my recovery image currently: what should I do differently than what's under https://wiki.lineageos.org/devices/a52q/upgrade/ ?

2) If I am uxing XprivacyLua, I guess that is not impacted by the 19.1 -> 20 upgrade other than making sure Magisk modules and LSPosed are working properly after the upgrade?
[Samsung Galaxy A52 4G] wojtekojtek:
I always flash magisk after flashing rom, because rom overwrites your boot.img and you will lose root, idk about microg

1) You can keep it, if you want update using TWRP, just reboot to recovery, click install, select file and confirm.

2) Check if XprivacyLua supports Android 13, LSPosed works in 13 and it stops working in 14 QPR2, so you need modified version to make it working in 14.
[Samsung Galaxy A52 4G] RisenID:
did you enable night light?
[Samsung Galaxy A52 4G] weim1:
Yes. It seems this was the issue. I disabled it and now it works. Thanks!
[Samsung Galaxy A52 4G] AmiraliBeast:
This rom support 64MP camera?
[Samsung Galaxy A52 4G] RisenID:
Nope, blame samsung.
[Samsung Galaxy A52 4G] AmiraliBeast:
Hi. I want install this rom for daily use (I am A student) .

I want to know if I can install this rom for a few year?
[Samsung Galaxy A52 4G] RisenID:
Should be fine, remember to install gapps if you need them
[Samsung Galaxy A52 4G] AmiraliBeast:
i found a way to use 64MP camera on every custom rom!!!!!!!

on that rom it work but with SIXTEEN kernel

i need a A52F/DS to test this (i have a52f)

And rom is toooooooo slow

i like it but look at pixel experience
[Samsung Galaxy A52 4G] Simon1511:
Not related to the ROM itself. PixelExperience just sets the default animation speed to 0.85 which makes the phone feel by far faster.
[Samsung Galaxy A52 4G] RisenID:
Just saying, just because camera app says 64mp mode, the photo might not be 64mp
[Samsung Galaxy A52 4G] AmiraliBeast:
Hi. Again 😂

I have Galaxy buds 2 but when I install galaxy wearable and finish setup app crash

When buds not connected app open but just not connected when I open buds case it stop working
[Samsung Galaxy A52 4G] Simon1511:
Update!

These will most likely be the last

un

official builds of LineageOS 20 since LineageOS upgraded a lot of their devices officially to 20 yesterday. A52 and A72 haven't been officially moved to 20 yet, but I'm working on it!

Downloads:

A52: MEGA

A72: MEGA

Changelogs:

The camera app (Aperture) now supports using the aux cameras (Ultrawide/Macro/Telephoto)

Enabled multiple vibration strength levels

Enabled colour modes in settings instead of using LiveDisplay's display modes

Better ZRAM management

NightLight and ExtraDim are now toggled off/back on when unlocking with fingerprint

Support for OneUI 5 firmware

OneUI 5 firmware is required now, otherwise installing the ROM will fail
[Samsung Galaxy A52 4G] xinouch:
Wow thanks a lot! Sounds very promising!

I'll wait the official as it should happen soon.

Does it mean that if we want to upgrade from LOS 19.1, we first need to reinstall the official ROM to get the latest OneUI?

Also, it seems you did some work on the cameras. Do you recommend to use the default app now? Or do you use GCAM?
[Samsung Galaxy A52 4G] RisenID:
A reinstall would be the easiest method.

When it comes to photos and camera apps, what looks good is very subjective. Aperture camera app is indeed very nice now, try both and decide which you want to use ig.
[Samsung Galaxy A52 4G] Rampler:
Ok, do we have to install all parts (AP,BL,CP,CSC,HOME) via ODIN ?

Can a flash directly the LOS recovery after flashing stock rom without booting ?

Is it possible to restore settings with seedvault (made with LOS 19.1) ?
[Samsung Galaxy A52 4G] shawgluz:
There is still no fix so that the call sound does ring? I deactivate notification sound and system so that it does not ring every time but when they call me it does not ring, which I should do

In the same way, the fingerprint system has not yet been fixed, if it quickly detects the fingerprint and avoids raising the brightness to the maximum?
[Samsung Galaxy A52 4G] Simon1511:
Yes, flash full stock ROM, you can just install the vbmeta_disabled.tar and Lineage recovery right after.

In case of Seedvault, I haven't used it yet, but restoring should work.

I still can't reproduce your call sound issue and so far you are the only one reporting that bug.

In case of fingerprint, that bug does not happen if you leave the finger on the screen instead of touching multiple times.
[Samsung Galaxy A52 4G] shawgluz:
Yes. Can you try, if I remove sounds from "system" and "notifications" it only remains to accept multimedia sound and calls, right? but if someone calls me it doesn't ring, it only vibrates and I have to deactivate the other sounds because I don't like it, in stock rom everything works fine but in any custom rom in a52 I get that sound error

It is that it does not detect the fingerprint as such, in stock it does not take so long to detect either, I have even come to think that my finger is deformed or that hahaha
[Samsung Galaxy A52 4G] hamudistan:
When've flashed stock 13 firmware, should I boot it once, or can I flash twrp and lineage direct afterwards and boot then?
[Samsung Galaxy A52 4G] Simon1511:
You can flash TWRP and LineageOS right after flashing stock Android 13.
[Samsung Galaxy A52 4G] hamudistan:
Great, no pain with OneUI
[Samsung Galaxy A52 4G] hamudistan:
New camera app works great, would be even better with possibility to store on sd card
[Samsung Galaxy A52 4G] hamudistan:
@Simon1511 I've used this build now for a while and once again I'm amazed how smooth it works.

Thanks for your work, carry on and good luck in making it offical
[Samsung Galaxy A52 4G] Simon1511:
Good news, LineageOS 20 just hit Official!

The first build for A52 4G was released just this morning, the first A72 build will approximately release tomorrow (Saturday, 21 January).

This means that there will be

no more

LineageOS 19.1 builds.

If you are currently using official 19.1 you should be able to just upgrade to official 20 through Settings -> System -> Updater. If you are currently using unofficial 20 you will have to flash the first official build manually to get OTA's.

Downloads:

A52 4G

A72 (tomorrow)
[Samsung Galaxy A52 4G] Rampler:
Does it mean that if we want to upgrade from LOS 19.1, we dont need to reinstall the official ROM to get the latest OneUI? (as mentioned in post #35)
[Samsung Galaxy A52 4G] Simon1511:
No, you won't need to reinstall OneUI. Since only OneUI 5 based firmware is required you can just flash this here in Odin, depending on your phone model: https://github.com/Simon1511/a52q-a72q-fw/releases

This essentially just continues the firmware, which means you can flash that in Odin and then right after dirty flash LineageOS 20, without needing to flash a recovery, vbmeta disabler and so on again.
[Samsung Galaxy A52 4G] daniel997:
@Simon1511 Hello Simon! I have a Samsung Galaxy A52 4G and i previously installed LineageOS 20 UNOFFICIAL build with Nikgapps Core using TWRP, but i have encountered quite a few bugs that im reporting below:

1. Low brightness between 0 and 70%

2. Low call volume

3. Flashlight stops working and the only workaround is a reboot

4. Battery sometimes does not charge

5. Dolby atmos does not work as intended the device volume goes up and down randomly when listening to any video

6. Fast charge makes alot of heat, this does not happen on ONEUI 5

Are those known bugs or did i do something wrong?

Right now ive returned to ONEUI 5 but im tempted to install the official lineageos 20 to see if they have been fixed.

Thank you for your time reading this,

Daniel
[Samsung Galaxy A52 4G] Simon1511:
That's technically AOSP calculating brightness different than OneUI does, not sure if I can do anything about that. So far it has been like this on all of my phones running any AOSP ROM.

I.. don't think so? For me it's absolutely fine, even if sound in general is not as loud as on OneUI it's still loud enough in my opinion.

First time I hear about that. Sounds more like an issue with one of your Apps keeping the camera open in the background or just a bad flash. You might wanna try killing the cameraserver using this app called "KillCamera" and see if that helps.

Also, first time I hear about that. Sounds more like faulty USB port/charger. Have you tried different chargers (especially stock Samsung chargers) yet?

I haven't encountered that yet either, might check later.

That's a known bug, but I haven't figured out yet what causes it.

If all those issues existed on the unofficial builds there won't be much difference on the official version.
[Samsung Galaxy A52 4G] Rampler:
Sorry i get the following message: (using official 19.1)

Update blockiert

Dieses Update kann mit der Updater-App nicht installiert werden. Für weitere Informationen lies bitte http://wiki.lineageos.org/devices/a52q/upgrade .
[Samsung Galaxy A52 4G] Simon1511:
Have you installed OneUI 5 firmware/bootloader before? I'm asking because I implemented a check for that so installing LineageOS 20 with OneUI 4 bootloader/firmware will fail.
[Samsung Galaxy A52 4G] Rampler:
No, i haven't ..

Could yo please confirm these steps: (coming from LOS19.1)

- install AP,BL,CP with Odin, downloaded from https://github.com/Simon1511/a52q-a72q-fw/releases

- boot/start phone and install LOS20 via updater

Right ?
[Samsung Galaxy A52 4G] Simon1511:
Yep, that should work. If not try installing LineageOS 20 manually, after that the Updater should definitely work.
[Samsung Galaxy A52 4G] greedykangaroo:
I also got the message. Now I just installed the files linked in this thread (https://github.com/Simon1511/a52q-a72q-fw/releases/tag/A525FXXU4CWA2) apparently successfully through Odin; however the updater still shows the same message.

Ill then install LineageOS 20 manually
[Samsung Galaxy A52 4G] Simon1511:
Thank you too for reporting that, I'll check if that's an issue with my LineageOS builds or with the LineageOS Updater app itself.
[Samsung Galaxy A52 4G] Rampler:
I am to stupid, now i get:

Cant load android system. Your data may be corrupt. If you continue to get this, you may need to perform a factory data reset and erase all user data stored on this device...

Ok, i have done a factory reset...

Restored all data with seddfault ..

All google stuff have problems during restore ..

Should I have installed mindthegapps for android 13 ?
[Samsung Galaxy A52 4G] Simon1511:
Yes, Android 12 will not work on Android 13, only Android 13 ones will.
[Samsung Galaxy A52 4G] hamudistan:
Update from unoffical to offical went through without any problem. Cool work man 👍