Development [ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72

Search This thread

Flyos

Member
Nov 8, 2014
19
5
Is it possible that the "call output on bluetooth not working" bug could be circumvented by using a call app different the from LineageOS stock one?
 
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.

The last 19.1 builds will continue to be available on a mirror hosted by me, you can find it here.

Link to LineageOS 20 thread: https://forum.xda-developers.com/t/...cial-lineageos-20-for-a52-4g-and-a72.4501577/
 

nikolamus

Member
Nov 11, 2020
25
1
please help me I installed Lineageos20 and gapps but I don't have internet on google play google play is ofline
 

MarioRS

Member
Jan 28, 2023
6
0
Hi,
i have to report a bug, maybe.
Bluetooth for phone calls does not work.
Play music works fine via Bluetooth.
I can choose bluetooth in the phone dialog, but sound comes still from phone speaker.
Of course, i checked settings for bluetooth device, (HD-Audio,Telefonanrufe,Medien-Audio,Kontaktfeigabe) is allowed.

EDIT:
- TATRONICS SoundElite 72 does not work
- JBL TUNE230NC TWS is working Hi
Hi, similar problem here. With bluetooth connection in my car, audio is played over car audio, the phone is not. Bluetooth dialog is active but sound comes out on the phone.

a52q with LineageOS 20 official and Skoda Superb bluetooth connection.

Hope this can be fixed!

Thanx & best regards, Mario
 
Last edited:

manhnct

Member
May 18, 2014
7
2
Hi Mr. @Simon

I've tried to flash your FW on Samsung A52, and it seems to work perfectly.
On other hand, I've flashed and tested the lastest Pixel Experienced GSI firmware (Pixel Experience 12.1 v416) on a Samsung A52 device. And I found that the problem of no sound when calling on SIM 2 still exists on the treble GSI firmware.

As in your release notes, I see that you'd fixed that issue since 07/2022 (please see the attached image). I understand that this issue may be the problem in GSI Firmware, but could you please share the patch or commit link to fixed that issue? I'd like to try to apply this patch in to GSI firmware.

Thank you.

1679686336362.png
 

Ryzen5950XT

Senior Member
Mar 16, 2022
309
288
Samsung Galaxy A52 4G
Hi Mr. @Simon

I've tried to flash your FW on Samsung A52, and it seems to work perfectly.
On other hand, I've flashed and tested the lastest Pixel Experienced GSI firmware (Pixel Experience 12.1 v416) on a Samsung A52 device. And I found that the problem of no sound when calling on SIM 2 still exists on the treble GSI firmware.

As in your release notes, I see that you'd fixed that issue since 07/2022 (please see the attached image). I understand that this issue may be the problem in GSI Firmware, but could you please share the patch or commit link to fixed that issue? I'd like to try to apply this patch in to GSI firmware.

Thank you.

View attachment 5871357
Why gsi when we have official pixel experience builds for the a52?
 
Hi Mr. @Simon

I've tried to flash your FW on Samsung A52, and it seems to work perfectly.
On other hand, I've flashed and tested the lastest Pixel Experienced GSI firmware (Pixel Experience 12.1 v416) on a Samsung A52 device. And I found that the problem of no sound when calling on SIM 2 still exists on the treble GSI firmware.

As in your release notes, I see that you'd fixed that issue since 07/2022 (please see the attached image). I understand that this issue may be the problem in GSI Firmware, but could you please share the patch or commit link to fixed that issue? I'd like to try to apply this patch in to GSI firmware.

Thank you.

View attachment 5871357
This here is the patch. Most likely you've been using the PixelExperience GSI with the stock ROM vendor which does not include this fix.

Also as Ryzen5950XT said, we have officiall source built PixelExperience for A52 that has this issue fixed too.
 

manhnct

Member
May 18, 2014
7
2
Why gsi when we have official pixel experience builds for the a52?
Because I see thise issue (no audio sound when call in SIM 2) exists not only on A52 but also on other devices model such as Samsung S22 Ultra with GSI firmware. I guess all Samsung model which are using Qualcomm chipset have this issue. This issue has also been reported on the treble GSI Firmware (phh_treble 2008, or phh_treble 2013 - calls on SIM 2 does not work) but still not fixed. So that I just want to try to check.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device.
    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    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.

    Working
    • Audio
    • Wifi
    • Hotspot
    • Calls
    • WifiDisplay
    • Bluetooth
    • OMX
    • Camera
    • NFC
    • Fingerprint
    • Screen-Off-FOD
    • Mobile data
    • GPS
    • DT2W
    • ...

    Bugs
    • VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)
    • Audio output in VoIP calls is swapped (WhatsApp, Discord, etc)
    • On some bluetooth Watches/Earphones In-Call sound is played from the phone's speaker/earpiece

    Installation instructions

    Recommended
    Follow the guide on the LineageOS website: A52 4G | A72

    Alternative way (TWRP/OrangeFox)
    1. Make sure your device's bootloader is unlocked.
    2. If not done before, flash blank VBMeta with Odin in AP slot.
    3. Make sure to have the latest available version of TWRP/OrangeFox installed.
    4. If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
    5. Download the lineage build for your device from the link below and optionally download your preferred GApps package too.
    6. Flash the LineageOS zip using the "Install" button.
    7. Optionally, flash Gapps right after.
    8. Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
    9. Wipe metadata and cache partitions. This only has to be done once when you install LineageOS.
    10. Reboot

    Downloads
    You can find them here on a mirror hosted by me.

    Gapps (choose arm64 and 12.1/12L): MindTheGapps | OpenGapps canary | FlameGapps Canary | NikGapps Canary

    Old builds:
    18.1

    Support
    Donations
    They aren't necessary, but if you like my work feel free to send me or LineageOS a donation.

    Credits
    To...
    • Me, for spending my time on this project
    • Whoever made the VBMeta disabler
    • @Grarak for his fingerprint fix for A70 and DT2W fix
    • @TheLeo2307 for testing on his A72
    • @miamighost for testing on his A52
    • Maybe more, feel free to tell me if I forgot someone

    Source Code: https://github.com/LineageOS/android_kernel_samsung_sm7125
    16
    Announcement!
    A52 4G and A72 are now officially supported by LineageOS!

    From now on new builds will be released weekly on LineageOS' website. That means every week there will be new official builds for both devices.
    New builds for A52 4G will currently release on every Friday and for A72 on every Saturday.

    What are the differences between the unofficial and the official versions?
    • The official versions will be updated frequently (every week) with the latest changes from LineageOS.
    • They have OTA-Update support built-in, which means you will be able to easily update to newer versions using the Updater found in Settings->System->Updater.
    • Also, as mentioned by @thatdevsherry and a few other people, hotspot accidentally went broken in the last unofficial build. This has been fixed on the official ones.
    • Macro (A52 and A72) and Tele (A72 only) cameras are now accessible by Gcam, which wasn't working before.
    How do I update to the official version?
    You should be able to just dirty flash the official build over the unofficial ones.

    Apart from that, all device trees and the kernel can be found on github.com/LineageOS and review.lineageos.org. Feel free to contribute!

    Downloads
    A52 4G: download.lineageos.org | wiki.lineageos.org
    A72 4G: download.lineageos.org | wiki.lineageos.org
    8
    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:
    Code:
    -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
    8
    Hey people, thanks for waiting patiently and reporting bugs. Lineage 19 is now available with a long list of bugfixes and improvements!

    Before installing, make sure to be on OneUI 4 firmware and have OrangeFox or TWRP 3.6 or newer installed, otherwise you will end up in a bootloop.

    Also, this build contains an unofficial implementation of monet. Feel free to give me feedback on this.

    In addition the device trees are now available on my Github!

    Downloads: A52 | A72

    Changelog:
    Code:
    -Updated to Lineage 19.0
    -February security patch
    -Updated all blobs and configs to A525FXXS4BVA2 (Android 12)
    -Updated kernel to A525FXXU4BUL8 (Android 12)
    -Unified more blobs
    -Fixed screen rotation on A72
    -Switched to AOSP WifiDisplay implementation
    -Corrected status bar padding
    -Built more blobs from source
    -Switched to Clang r383902
    -Disabled APEX compression
    -Switched to UDFPS
    -Fixed FOD on AOD
    -Make FOD stay always on for working FOD on AOD
    -Increased the amount of time the screen lights up when touching the fingerprint sensor
    -Switched to stock health blobs
    -Overall cleanup
    -Enabled F2FS support for system partition
    -Switched to newer AIDL libperfmgr power HAL
    -Updated vibrator to AIDL to switch to manifest level 5 and match stock
    -Fixed audio in bluetooth phone calls on A52 (for somehow still broken on A72)
    -Imported APTX BT encoder from Pixel 5
    -Enabled unofficial monet implementation
    8
    Update

    13-01-2022: A52 (MEGA) | A72 (MEGA)

    Lineage recovery: A52 (MEGA) | A72 (MEGA)

    Changelog
    Code:
    -Latest lineage sources with december security patch (january one wasn't released yet)
    -Updated blobs to A525FXXU4AUJ2
    -Added initial A72 support -- see more information below
    -Switched to OSS fingerprint HAL by @Grarak
    -Cleaned up unused config files
    -Built lineage recovery for both devices
    -Added missing overlay for the system to know that we have a notch
    -Built more blobs from source
    -Fixed A2DP offload and switched to AOSP bluetooth audio implementation
    -Correctly boost brightness when the fingerprint sensor is touched
    -Fixed fingerprint sensor not working when screen brightness is low
    -Corrected size and position of the fingerprint sensor (And yes, the sensor is REALLY that big)
    -Disabled screen off FOD for now since it doesn't work anyway
    -Limit fingerprints to max 4 per user
    -Temporary disabled FMRadio since it somehow broke with latest sources
    -Built QCOM audio effects from source

    Some notes regarding A72 support
    Since I don't have an A72 here it was kinda hard to blindly support it. But first I wanna thank @madseason.live and Leo on Telegram for testing my builds on their A72's. Even though both of them did good testing, we didn't succeed in getting the fingerprint sensor to work. A72 uses a different sensor and driver than A52 does and without having the device here by myself it's hard to fix that without knowing what the actual issue is. It only works for setting up a fingerprint, but actually unlocking the phone with it doesn't work. Additionally, for somehow screen rotation is flipped by 90° which makes no sense at all since A52 and A72 use the same sensors except for fingerprint and camera. If someone has an idea or wants to contribute, feel free to contact me.