I wouldn't know, I'm a mere user here! But I'm sure @Simon1511 would have an idea.
Yes, feel free to report it on LineageOS's issue tracker.
Is there any workaround for reversed audio for Internet calls? Maybe you could change to aosp audio @Simon1511 ?
A fix is being worked on.
Currently there is no workaround for that and just "changing to AOSP audio" is by far easier said than done. A52 and A72 use a different audio configuration than what Qualcomm ships as default with 720G. Apart from that we still lack the source code for the built-in Amplifier which would require a lot of reverse-engineering, time, and trial-and-error.
Yes, all samsung phones have this problem (even older, such as a70). Most devs switch to aosp audio, but this has drawbacks such as echo in calls, low volume... Reverse engineering should not be easy (volte needs it too...)
Please contact me via PM here or via PM on my telegram account, we have a possible fix ready for the testing phase, and would appreciate your help in making sure that it works for yall.
Any others who are having issues ralated to call audio not being audible on bluetooth headphones, please feel free to do the same.
My telegram is - https://t.me/Ryzen5950XT
Thanks.
Hi there,
tonight i tried to update from lineageos 19.1 to lineageos 20
Somehow i must have missed something, because the phone does not boot the system anymore
I can boot into recovery, or into fastboot.
But when i start to system, i got the security error screen, with the following message in red:
SECURE CHECK FAILED : dtbo(11)
do you have any idea on what i should do to fix it?
Thank you in advance!
tonight i tried to update from lineageos 19.1 to lineageos 20
Somehow i must have missed something, because the phone does not boot the system anymore
I can boot into recovery, or into fastboot.
But when i start to system, i got the security error screen, with the following message in red:
SECURE CHECK FAILED : dtbo(11)
do you have any idea on what i should do to fix it?
Thank you in advance!
I have had the same message. Unfortunately I had to reinstall everything. (Back to stock and migrate to LOS again) However, the dtbo.img has recently been added to the LOS download page. I would try to flash the dtbo.img. It can't get any worse.
In the meanwhile i am back to stock again.
regards Klaus
This is how i ended also.
First I tried to flash the file dtbo.img via fastboot but i got an error: remote, folder does not exist.
So I flashed the stock rom from sammobile, amd from there did a hard reset and reflashed lineageos again.
The good news is that my phone is not a useless brick, but the bad news is that i need to reinstall everything again. Too bad, i was hoping to keep my setup...
Maybe Simon knows if there had been another solution?
First I tried to flash the file dtbo.img via fastboot but i got an error: remote, folder does not exist.
So I flashed the stock rom from sammobile, amd from there did a hard reset and reflashed lineageos again.
The good news is that my phone is not a useless brick, but the bad news is that i need to reinstall everything again. Too bad, i was hoping to keep my setup...
Maybe Simon knows if there had been another solution?
I've not had this issue on my own phone yet, but will check if there's a better solution.
If you want to get help, you really need to elaborate more. Describe what you expect to happen, and what *actually* happens.
Also, the brevity of your message makes you come across really entitled - nobody owes you anything, after all!
Nope, by default Wireguard is not supported by LineageOS and our kernel.
Hello!
I'm a lineageOS user for years and a user of this version for 2month now.
It's quite smooth and stable and I'm grateful that there's maintainers for this ROM!
I'm also glad to see that a fix for the bluetooth issue may come!
Unfortunatly I have a weird issue with the screen brightness.
When I unlock my phone the brightness change to a weird value !
Sometime it goes to max, sometimes to min ( and in full sunlight you cannot see anything on the screen)!
i don't think it is a luminosity sensor issue as the behaviour is the same when I disable the automatic brightness.
Also the slider to adjust the brightness in the notification bar isn't updated when the brightness changes....
Anybody face the same issue? Can I bring some log to determine the problem?
I'm a lineageOS user for years and a user of this version for 2month now.
It's quite smooth and stable and I'm grateful that there's maintainers for this ROM!
I'm also glad to see that a fix for the bluetooth issue may come!
Unfortunatly I have a weird issue with the screen brightness.
When I unlock my phone the brightness change to a weird value !
Sometime it goes to max, sometimes to min ( and in full sunlight you cannot see anything on the screen)!
i don't think it is a luminosity sensor issue as the behaviour is the same when I disable the automatic brightness.
Also the slider to adjust the brightness in the notification bar isn't updated when the brightness changes....
Anybody face the same issue? Can I bring some log to determine the problem?
You're probably unlocking your phone with fingerprint, right?
From what I see this is an issue with the HBM-mode (high brightness mode) used for fingerprint where it does not properly reset to the previous brightness.
I'll take a look at it.
Just found sth funny: in settings -> system -> languages -> languages -> add a language
The first 2 values are debug stuff I guess, and should be removed?
The first 2 values are debug stuff I guess, and should be removed?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13Good news!
I've been continuing on fixing bugs and tiny issues reported for a long time. Following issues have been addressed:
- Speaker and Earpiece output in VoIP calls (for example Whatsapp, Discord, etc) are no longer reversed
- Audio in phone calls with some bluetooth headphones or Smartwatches doesn't play from speaker/earpiece anymore
- The fingerprint icon on the lock screen no longer appears on top of the lockscreen text
- Removed Dolby audio effect as it didn't actually impact audio quality and in exchange added back AudioFX
- Improved vibration intensities
- Set FOD color to white (as on stock ROM)
- The screen now doesn't get darker when using FOD but instead keeps its brightness (fixes FOD on AOD failing)
- Prevent the screen from jumping to high brightness (and getting stuck there) after unlocking with fingerprint
- Switched back to Camera2 to fix pictures being ~100mb each
- Fixed "Extend compatibility" toggle in Hotspot settings
A few notes on above changelog:
We (@Ryzen5950XT ) and I have been working on the Bluetooth-phone-call-fix for around 2 months now and even now it still is not 100% rock solid. Sometimes you may encounter crackling audio for a few seconds when switching output devices or in rare cases even no audio in a call. We're still working on improving the general quality of this fix, but believe that it has become good enough to be usable as a daily driver.
In terms of the Camera issue where it produces ~100mb pictures: I've been able to track this down to an issue with CameraX support on our phones but so far have had no luck figuring out what exactly the culprit is. However, LineageOS guidelines require me to ship a fully working Camera app. Therefore I will (temporarily) have to ship the old, feature-less Camera2 instead of Aperture.
All these changes will be available starting from the next LineageOS builds for A52 and A72, which will most likely be 12th May (A52) and 13th May (A72).
And as always, please keep reporting bugs and inform me about possible improvements.3Just tested the last update.
No more brightness issue when I unlock with fingerprints, but the probleme seems to still exist when unlocking with the pattern. :-/
I also tested bluetooth audio issue with a Bose QuietConfort 35 II and at first the problem was the same.
Then I switched to phone speaker and go back to bluetooth during a phone call and the sound was played in the headphone.
Dont know yet if this behaviour will occurs each time, but at least I have a workaround!
Congratulation and thanks again for your work.3
As far as I know a similar issue existed on NcX, and there you could fix it by flashing the latest stock ROM firmware. Might wanna try that, guide is here.3
I flashed the latest stock firmware and the issue has been resolved. Thank you.2
Just scroll through the releases on that github repository until you find one that starts with A525F. They're sorted by date, so the first one you'll find is the latest firmware available. -
13Good news!
I've been continuing on fixing bugs and tiny issues reported for a long time. Following issues have been addressed:
- Speaker and Earpiece output in VoIP calls (for example Whatsapp, Discord, etc) are no longer reversed
- Audio in phone calls with some bluetooth headphones or Smartwatches doesn't play from speaker/earpiece anymore
- The fingerprint icon on the lock screen no longer appears on top of the lockscreen text
- Removed Dolby audio effect as it didn't actually impact audio quality and in exchange added back AudioFX
- Improved vibration intensities
- Set FOD color to white (as on stock ROM)
- The screen now doesn't get darker when using FOD but instead keeps its brightness (fixes FOD on AOD failing)
- Prevent the screen from jumping to high brightness (and getting stuck there) after unlocking with fingerprint
- Switched back to Camera2 to fix pictures being ~100mb each
- Fixed "Extend compatibility" toggle in Hotspot settings
A few notes on above changelog:
We (@Ryzen5950XT ) and I have been working on the Bluetooth-phone-call-fix for around 2 months now and even now it still is not 100% rock solid. Sometimes you may encounter crackling audio for a few seconds when switching output devices or in rare cases even no audio in a call. We're still working on improving the general quality of this fix, but believe that it has become good enough to be usable as a daily driver.
In terms of the Camera issue where it produces ~100mb pictures: I've been able to track this down to an issue with CameraX support on our phones but so far have had no luck figuring out what exactly the culprit is. However, LineageOS guidelines require me to ship a fully working Camera app. Therefore I will (temporarily) have to ship the old, feature-less Camera2 instead of Aperture.
All these changes will be available starting from the next LineageOS builds for A52 and A72, which will most likely be 12th May (A52) and 13th May (A72).
And as always, please keep reporting bugs and inform me about possible improvements.12
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
Make sure you are on OneUI 5 firmware before flashing this ROM, otherwise the installation will fail!
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, download vbmeta.img from the LineagOS website (A52 | A72) and pack it into a tar file.
- 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
A52 4G: download.lineageos.org
A72 4G: download.lineageos.org
Gapps (choose arm64 and 13.0):
FlameGapps Canary | NikGapps Canary | MindTheGapps
Old builds:
LineageOS 20
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_sm71254Good 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)4Update!
These will most likely be the last unofficial 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
