Simon1511 said:

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).

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.

seam0nster said:

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.

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.

Simon1511 said:

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

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!

bluKae said:

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!

Click to expand...

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

This has been fixed on the newer unofficial and official 20 builds though.

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.

bluKae said:

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.

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.

Simon1511 said:

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.

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!)

bluKae said:

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.

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.

Flyos said:

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.

Sorry, currently there is no workaround for that.

ceoofacerbutnot said:

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.

Yes, it runs smoother than stock ROM.

Rampler said:

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..

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.

Rampler said:

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..

After installing recovery manually (via odin), the version will be shown correct.

Simon1511 said:

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.

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.

Rampler said:

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.

No, currently that's not possible.

Simon1511 said:

Sorry, currently there is no workaround for that.

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