Thanks for reporting, I will check if it's an issue with that specific build or if dirty flashing is the issue here.
I will be interested to know as well as microG has produced a build with that version and it is now available via OTA update. I am holding off on updating via OTA until the mystery is solved.
I think my issue with the cell signal indicator being stuck is related to what some API functions return for the cell signal. Most cell-signal monitoring apps, including the system one (in SIM Status) report the same values forever. Some apps, using alternate cell-signal APIs, do report the correct values however. Hopefully this latest build will solve my problem.
Oh and another question: is there any way to increase/control the vibration strength? For me it is pretty weak. I can imagine in winter with my thighs numb I won't feel any vibrations... I tried every method I could find but to no avail. I don't see any build property for vibration strength either. Don't know if the stock ROM has this ability.
Last edited:
I'll check with both the latest LineageOS and MicroG builds.
Yes, stock ROM has a setting for that if I'm not wrong, I'll see if I can make it work on Lineage too.
Both the latest LineageOS and LineageOS for MicroG builds work just fine here. I also had no issues with the signal strength indicator.
Can I do an OTA update if I am using TWRP? When I touch Install on the update it says "This feature requires a compatible Recovery or updates will need to be installed manually.".
I must be doing something wrong here...
I just need to flash the LOS zip and reboot, right? No need to reflash Gapps nor Magisk, or wiping any caches?
With TWRP 3.7 it "worked" for me. In the worst case, the downloaded zip file is stored in `/data/lineageos_updates`, so you can manually flash it from TWRP
I think I read on a website that you need to wipe the Dalvik cache after flashing the LOS update zip.
I updated from https://download.lineage.microg.org/a52q/lineage-19.1-20220915-microG-a52q.zip to https://download.lineage.microg.org/a52q/lineage-19.1-20221016-microG-a52q.zip by downloading it in Updater app and manually flashing from `/data/lineageos_updates`. I also pressed the "Wipe Cache & Dalvik" afterwards. My A52 booted successfully into Lineage with no issues afterwards. Just remember with Magisk 25.2 all modules get disabled after doing ROM updates.
I am still having the same issue with my cell signal bar however. Very odd and annoying. The SIM status just shows the same values forever (they fluctuate a tiny bit after boot though). Hopefully I can find a solution for this. @Simon1511 do you know how I can investigate this? I am a developer but don't have experience in ROM development. Not sure if the relevant code is in LineageOS or proprietary by Samsung.
Hello, there is one thing about animation/effect in UI that I noticed. It is best visible on dark theme. Go to settings and click on any entry. The feedback animation which makes a button light up briefly is pixelated, grainy. It isn't smooth as on stock Rom. The same can be said about buttons in Quick Access list. It happens on light theme as well, but as the contrast is much lesser it's barely visible.
The code is most likely somewhere in LineageOS's sources, I wouldn't know where to search though. Can you possibly check if the same thing happens on normal LineageOS?
Yeah I noticed it too, it's happening on some of my other devices too. I'm not sure why it happens though.
Well, since I don't really have experience restoring backups with ROMs I am wary of reinstalling everything since it took a while to setup everything right on the MicroG build.
Not sure what to do. I will try to look at the LineageOS code. I was thinking maybe I can hook onto the TelephonyManager class and call the cell API functions that do work with XPrivacyLua but I don't know which app is responsible for displaying the signal status icon. Probably something under user 1000. Not sure if that will work since LSPosed doesn't like hooking onto system apps. I could also write an app that displays an icon as a notification but that would require permanent location permission and the icon would not be visible on the lockscreen...
In my experience, updating let's say week by week, all I did was wipe the two dalvik caches and that's it only once I had stopped updating it for about three months, the new one did not start and I had to wipe data this with other models, not the A52 I'm a bit complicated I haven't even unlocked the boot yet
GCAM UPDATE:
DOWNLOAD: https://www.mediafire.com/file/oh99...42.XXX_STABLE_V38FIX_SAMSUNG_PACKAGE.apk/file
DOWNLOAD: https://www.mediafire.com/file/oh99...42.XXX_STABLE_V38FIX_SAMSUNG_PACKAGE.apk/file
With the update from this week (21/10), I just let the LineageOS updater do all the job and it worked fine.
It downloaded the update and reboot the phone and automatically installed it. Gapps and Magisk are working fine too (though I have no modules installed).
Hello Simon1511, I still have the problem that the display jumps to minimum brightness in direct sunlight. In contrast, at minimum brightness (for example, when i use the phone as navigation sytem in the dark), the display jumps to maximum brightness. Both happen randomly. I have had this problem since I started using this ROM in July.
Another thing is that when I'm on Wi-Fi for hours, the mobile data connection no longer activates, so I have to restart the smartphone.
Both bugs also occur on my daughter's smartphone.
Does anyone have the same problems or a solution?
WBR
Danny
Another thing is that when I'm on Wi-Fi for hours, the mobile data connection no longer activates, so I have to restart the smartphone.
Both bugs also occur on my daughter's smartphone.
Does anyone have the same problems or a solution?
WBR
Danny
ho meny pixel is camera rec
What is the resolution of the camera with the original app?
I have one with stock ROM
0,5 Zoom 3000x4000 first cam
1x Zoom3468x4624 second cam
2x Zoom 3468x4624 second cam
Macro 1932x2576 right cam
Selfie 2448x3264
But can't find out to use the third cam in the row.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23
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)
- Make sure your device's bootloader is unlocked.
- If not done before, flash blank VBMeta with Odin in AP slot.
- Make sure to have the latest available version of TWRP/OrangeFox installed.
- If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
- Download the lineage build for your device from the link below and optionally download your preferred GApps package too.
- Flash the LineageOS zip using the "Install" button.
- Optionally, flash Gapps right after.
- Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
- Wipe metadata and cache partitions. This only has to be done once when you install LineageOS.
- 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: LineageOS 18.1
Passing SafetyNet/Play Integrity
- Follow this guide.
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_sm712516Announcement!
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.
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.org8Hey 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 protection8Hey 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 implementation8Update
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.
