Regarding to my Google Assistent problem, the following information maybe useful.
No root, no magisk are installed.
Note: Login to the "WELT" News app does not work either, it appears when you try to log in that an error has occurred
regards Klaus
No root, no magisk are installed.
Note: Login to the "WELT" News app does not work either, it appears when you try to log in that an error has occurred
regards Klaus
Last edited:
I created a guide to fix such issues earlier: https://telegra.ph/Passing-safetynet-with-Magisk-v24-and-newer-03-03
The guide will definitely fix the CTS profile matched issue. Not sure if it fixes the LOCK_BOOTLOADER issue either, but maybe adding that app to Magisk's DenyList helps.
At the moment I don't have Magisk installed (only Lineageos + Lineageos Recovery + MindTheGapps). So I'm wondering about the failed reporting of the cts profile. I thought without Magisk, without root, everything is fine.. You recommend using Magisk even if I don't want root privileges just to solve the CTS problem?
Hi, first of all, thanks for your help. 
OK, now i have installed magisk with your guide.
Now all item's inside SaftyNet Check are green.
App Welt is also running, shame on me, it was only a Pihole problem. Sorry for that.
The only issue for now is the Google Assistant, see #317. (Google Assistant Hey Google is grayed out)
OK, now i have installed magisk with your guide.
Now all item's inside SaftyNet Check are green.
App Welt is also running, shame on me, it was only a Pihole problem. Sorry for that.
The only issue for now is the Google Assistant, see #317. (Google Assistant Hey Google is grayed out)
Last edited:
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
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
Last edited:
Pixel experience is an entirely different rom to lineage os and has many differences. The device trees themseleves are based off of simons work, but my builds are completely seperate and not related to the lineage os builds posted here.
You can also find them here on xda
[ROM][13][ENCRYPTION][Official] Pixel Experience for A52 4G and A72
/* * 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...
forum.xda-developers.com
As for the hotword enrollment, it indeed does work fine on pixel experience, due to source differences related to handling of gapps
Yes,
Android Version 12
LineageOS-Version 19-20221209-NIGHTLY-a52q
Baseband A525FXXU4BVG2
I have tested the Headset TATRONICS SoundElite 72 again with different Mobiles..
- Redmi Note 9 (Android 11) Miu
- Redmi Note11 (Android 12) Miu
- Redmi Note 5 (Android 8) LineageOs
Headset is working with all above...
As far as I can tell it's an issue with A2DP, I'll look into it once I can.
For a quick test, i disbaled already "bluetooth-A2DP-Hardware-Offload" in the settings, but unfortunately without success
I have installed the Lineageos via the guide on the lineageos website, with success. There is no topic with vbmeta installation on their webpages.
After that I read in this thread that you should do the vbmeta_disabled installing before custom rom installation. Should or could a install the vbmeta right now, while lineageos is already running (with lienageos recovery) ?
After that I read in this thread that you should do the vbmeta_disabled installing before custom rom installation. Should or could a install the vbmeta right now, while lineageos is already running (with lienageos recovery) ?
Last edited:
OK, i will answer myself. (found somewhere on the www)
After flash is complete the phone will automatically reboot and enter the stock recovery mode. It will prompt you to reset the device because the VBMeta signature has been changed.
Therefore vbmeta should be installed before installing the custom rom ...
After flash is complete the phone will automatically reboot and enter the stock recovery mode. It will prompt you to reset the device because the VBMeta signature has been changed.
Therefore vbmeta should be installed before installing the custom rom ...
Last edited:
I saw in the latest versions that lots of Bluetooth related commits went through, but the issue is still there : for a phone call, the soud is coming from the phone instead of the headset.
very good, if you remember a few weeks ago I had commented that I was not sure if I should stop since I work with my mobile, (and I did not have the opportunity to do the processes because I have to ask someone for a pc) the A52 received the update of Android 13, do you think if I update there will be a problem when I want to install Lineage?
I also have no problem staying on Android 12 until I can install 13 but I wanted to ask that, Regards
I also have no problem staying on Android 12 until I can install 13 but I wanted to ask that, Regards
The Installation instructions says:
Warning: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Warning: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
@Simon1511
is there a chance to get the bluetooth bug fixed ?
Can you reproduce the error?
Can we help ?
is there a chance to get the bluetooth bug fixed ?
Can you reproduce the error?
Can we help ?
As I said, I'll look into it once I can. Being impatient and asking every few days won't help.
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:
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_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.
