yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy M52 5G] DominguesPJ:
Thank you for your great work I will appreciate this but being solved very much believe me !

On another note since upgrading to LOS21 the phone seems to crash when exiting an app back to the launcher , I have tried switching from my usual Microsoft Launcher to Trebuchet but it still happens. The app goes away, I can use the notification drawer but I cannot click on anything or interact with the launcher , also when I try to open settings from the drawer when this is happening it sometimes works and I can force that launcher to exit sometimes it doesn't, when I force close the launcher everything works again.

Any clues ? Should I collect some logs to help ? ( If so what is the best way please )

Again thank you for all the hard work!
[Samsung Galaxy M52 5G] halofighteres:
Is there a way to force apps to run full screen i see the option in the settings but there's nothing there
[Samsung Galaxy M52 5G] Simon1511:
Did you upgrade from 20? If yes then that's probably the cause. Check logs and see what makes it crash and delete that from /data.
[Samsung Galaxy M52 5G] DominguesPJ:
Yup I did, will do that and see if it gets fixed . Thanks!
[Samsung Galaxy M52 5G] RoG khenwaY:
I did a Clean Installation from Samsung Stock A13 ROM to Lineage OS 21....but my Google Assistant is not working it says

This Device is unsupported

Is it a Common problem that will be fixed in upcoming Update or is there any other fix for this ?
[Samsung Galaxy M52 5G] RoG khenwaY:
Yup You are right...at that time my Cable was not connected to the device...

i tried everything but it didn't work eventually i thought of plugging in the cable and give it a try...and it worked! Loll...btw

Thnx for Replying
[Samsung Galaxy M52 5G] tanmay5:
Dear simon

Bugs I want to report in the latest update

1. Call/Phone app is freezing while calling and phone hangs for around 6 to 10 secs sometime crashes. Tried with another app no success

2. Previously teams voice calls were working but after update I can't hear other persons voice of caller and also in video same thing happened

However WhatsApp calling is broken

Thanx
[Samsung Galaxy M52 5G] DominguesPJ:
So after eagerly waiting for the build to be done ( I waited for Sunday midnight don't judge me I really wanted this fixed 😅) unfortunately the issue is still here, cannot make teams / Whatsapp or messenger calls 😔
[Samsung Galaxy M52 5G] Simon1511:
Just tested this on my own M52 again with a clean installation of the latest build and I've had no issues at all with WhatsApp audio. Others could hear me just fine (regardless of handset/speaker mode) and vice versa.
[Samsung Galaxy M52 5G] DominguesPJ:
Strange, that must mean something is left on the device after upgrading thats still causing the issue. What is the best way for me to help you debug this ?
[Samsung Galaxy M52 5G] Simon1511:
Running

adb logcat -b all | grep -i audio_route

while calling should be helpful.
[Samsung Galaxy M52 5G] tanmay5:
Dear Simon,

Now google from left of the home screen is refreshing forever. However the google app is working fine. Screen shot attached

Pls fix
[Samsung Galaxy M52 5G] DominguesPJ:
Hey @Simon1511 ! So I finally got a reproducible way of triggering the issue as well as some logs during the issue following your logcat grep suggestion.

So the issue seems to be triggered by receiving a call while playing something over the loudspeaker (multimedia like youtube). When that happens it just stops working until you reboot your phone.

It doesn't seem to happen if you're the one initiating the call.

I don't know much about this stuff but reading through the logs while it's happening in real time I would say the culprit is something called echo-reference speaker. It also matches the behaviour as I said before it's almost like the phone is aggressively trying to avoid echo and so It simply doesn't play the voice of the other person or allow the microphone to pickup sound from our end.

I would also guess since it seems to happen only when we are the ones receiving the call, it has something to do with timing, trying to guess when it should be canceling echo vs freely playing sound in the wrong order.

Hope this helps diagnosing. I am on the latest firmware and LOS update btw.

Tell me if you need further information and sorry for the delay but it was hard to find the time and place and find out a way to cause the error ^^

Thank you !
[Samsung Galaxy M52 5G] wltay04:
This custom ROM can use banking apps?
[Samsung Galaxy A73 5G] Simon1511:
LineageOS is a free, community built, aftermarket firmware distribution of Android 14, 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.

/*
* 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 A73 5G (A736B, A736B/DS) are supported.

Working

RIL

5G

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)

Maybe more, feel free to report

Requirements

Any OneUI 5 or OneUI 6 firmware, doesn't matter the version.

Installation instructions

Recommended

Follow the guide on the LineageOS wiki.

Downloads

Download: download.lineageos.org

Wiki: wiki.lineageos.org

Gapps:

MindTheGapps

Support

Telegram

Donations

They aren't necessary, but if you like my work feel free to send me or LineageOS a donation to keep me/us motivated.

Credits

To...

Me, for spending my time on this project

Everyone who helped in funding me this phone

@BlackMesa123 for his help with getting QKGI to work and general help

All the testers

Maybe more, feel free to tell me if I forgot someone

Source Code: https://github.com/LineageOS/android_kernel_samsung_sm7325
[Samsung Galaxy A73 5G] megacar@gmail.com:
thanks a lot!

Will it be possible to dirty flash official los21 once is out over this version with keeping the settings and apps?

Assuming you remain the maintainer of the official los21 for this device

Just to be clear, I am not asking for any promises or guarantees, just asking theoretical, in your opinion, how different will the final 21 version be compared to this current let's call it "beta"

edit: if this will not be possible, what about doing a backup (builtin LOS backup) and restoring it?
[Samsung Galaxy A73 5G] Simon1511:
Yes.

Probably not too different as most features are already added.
[Samsung Galaxy A73 5G] megacar@gmail.com:
fantastic! can't wait to flash it as I cant stand samsung one UI and google services on the phone :)

sorry to see such low enthusiasm these days, in the olden days this thread would already have 4 pages of posts :)

I still hope you won't give up doing this even with such low number of us {l}users interested :)
[Samsung Galaxy A73 5G] Ali_samsung110:
Thank you

Simon1511​

I will install this
[Samsung Galaxy A73 5G] megacar@gmail.com:
I have installed it and daily driving it since yesterday. Works great, day driver ready, stable, no major bugs.

2 minor issues noticed

- usb file transfer does not work until you reboot the phone. When connected, it only charges and does not allow file transfer or usb debugging. After phone reboot with cable connected everything works. You only need this when initially setting up the phone, so no big deal

EDIT: with usb debugging enabled, this does not happen, so usb file transfers work fine

- dual sim management - after disabling a sim, reboot is required to enable it again

EDIT: I guess this is related to the fact that dual sims are always active and cannot be disabled in AOSP (AFAIK) - at least not on samsung.

So basically disable button just hides the network status icon of the sim, but you can still receive calls and sms on that sim. So this can be completely removed from the settings as it never really worked.

This is related to WG - Android14 incompatibility:

- VPN tile in quick settings does not activate wireguard tunnel, even though permission enabled within wireguard (let other apps control the tunnels).

https://www.reddit.com/r/WireGuard/comments/18wrhpr

P.S. I'm running it clean no gapps, as God intended it to be :)
[Samsung Galaxy A73 5G] droidkeyboardfan12:
@Simon1511 hey. Thanks for your support and hard work.

Now that you are developing LOS21 will you still work on LOS20? That Network bug is kind of annoying. Or should we just upgrade to LOS 21.

Also please don't burn yourself out. Thanks to your work this has become a great usable phone. I hope to see more of your work in the future
[Samsung Galaxy A73 5G] Simon1511:
I don't know yet. I haven't made any progress on that specific issue.
[Samsung Galaxy A73 5G] droidkeyboardfan12:
Is LOS 20 now no longer developed? i got an update notification but now its only LOS 21
[Samsung Galaxy A73 5G] Simon1511:
Yes, LineageOS 21 is now officially out for A73. 20 will no longer get updates.
[Samsung Galaxy A73 5G] megacar@gmail.com:
clean installed the build from 22FEB

- fingerprint not working (cannot enroll, there was a problem, please try again later)

- after every reboot getting "Music is not responding" kill or wait

(didnt have these issues in your unofficial build, fingerprint was working..)
[Samsung Galaxy A73 5G] Simon1511:
Thanks for the report, I'm currently investigating why this is happening.
[Samsung Galaxy A73 5G] megacar@gmail.com:
have you seen this

Fingerprint reader broken on LOS21 (#6741) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Fingerprint service to start and run. Current Behavior Fingerprint service...

gitlab.com

happening on another device....
[Samsung Galaxy A73 5G] Simon1511:
This is a different issue on another device which is not related to our issue.
[Samsung Galaxy A73 5G] Simon1511:
Would you mind flashing this in recovery and giving me a short feedback if it fixed the issue? Thanks.
[Samsung Galaxy A73 5G] megacar@gmail.com:
flashed it, it was complaining that its unsigned or signature verification failed, installed anyway, now it behaves different but still doesnt work.

now there is no errors, it starts the enrolling process, and says hold your finger until you feel the vibration, but there is no vibration. i keep pressing the finger, circle where the sensor is changes color to light white, tried pressing it many times but nothing happens. he cannot enroll the finger. after some attempts the phone reboots (its a quick reboot without going to samsung bootloader screens, just reboots the LIneageOS). After this quick reboot, fingerprint option is gone. no way to enroll. then I can do a full reboot, fingerprint shows up again, but behaves the same as described in the beginning.
[Samsung Galaxy A73 5G] megacar@gmail.com:
I noticed something else, probably unrelated to this, but you never know...this was happening on the old (unoficial) build as well. the status bar on top has some 2 blinking dots - just left of selfie camera, those 2 dots just blink very fast all the time, not sure what is it, but I didnt notice any battery drain or any issues so I just ignore them...
[Samsung Galaxy A73 5G] Simon1511:
These are the proximity and light sensors. I haven't figured out how to "hide" those yet. They don't have any negative impact on the ROM.
[Samsung Galaxy A73 5G] megacar@gmail.com:
nice, good to know what is it :)
[Samsung Galaxy A73 5G] megacar@gmail.com:
I see new build is up, it has some mention of fingerprint change for samsung

https://review.lineageos.org/c/LineageOS/android_hardware_samsung/+/383753

Does it fix our issue? Doesn't seem to address this issue, but possibility to enroll more fingers..

Edit: installed the update, fingerprint still doesnt work
[Samsung Galaxy A52s 5G] m00ns0rr0w:
Great! Will test it when there's some time...
[Samsung Galaxy A52s 5G] schippox:
Hi. Big THX. Runs great since 4 hours. I patch the Boot.IMG with Magisk. No probs. Great work!!!!
[Samsung Galaxy A52s 5G] m00ns0rr0w:
before proceeding i have 2 questions...

1) will this become an official LOS release (again)?

2) what's the recommended way for linux users? Odin won't work (unless one wants to use/try wine). Use heimdall? Or is a windows computer recommended (or necessary)?

long time ago i installed LOS on a samsung S5, but not sure anymore how i did this :unsure:
[Samsung Galaxy A52s 5G] Simon1511:
Most likely yes, once LineageOS 21 becomes officially stable.

There's Odin for Linux that has been leaked from Samsung. I've been using it for some time and it works great.
[Samsung Galaxy A52s 5G] m00ns0rr0w:
Hmm... ok, i just got to the odin part and am somehow stuck or unsure how to continue. Checked the LOS 20 thread of this device and the odin thread, but... :unsure: The official doc says:

"Check the box labeled next to the button labeled “AP”, and then click the “AP” button.

In the menu that pops up, select the newly created custom VBMeta .tar file."

checking odin4 tool (via odin4 -h) for AP:

"-a Add AP image file"

So the command should be: "odin4 -a vbmeta.img" ?

Ah, and the device doesn't show up via "odin4 -l". Does the device need to be in download mode for usage with odin? Wiki isn't clear here...

Sry for all the questions... :)

edit says: i checked the TWRP thread of this device; there:

"Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).

Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button."

so correct would be: boot to download mode, then run odin4 with the above command and ... that's it?
[Samsung Galaxy A52s 5G] Simon1511:
No, odin4 -a vbmeta.tar

If you run odin4 -h it will show you detailed usage information. It also explains that you need to edit some file for it to detect your phone properly. That help page can also be found in the first post of the thread I shared above.

Yes, it needs to be. And the wiki does state that it needs to be in download mode.

Yes and no. You need to use that above command to flash a disabled VBmeta image, and after that flash a custom recovery like TWRP or LineageOS recovery. Normally you would flash these one by one, however, as I recently learned you can also flash both at the same time with odin4 -a recovery.tar -b vbmeta.tar.
[Samsung Galaxy A52s 5G] m00ns0rr0w:
Ah, now the fog is clearing up a little bit...

ok, flashed vbmeta.tar and recovery.tar

odin4 -a recovery.tar -b vbmeta.tar
Check file : recovery.tar
Check file : vbmeta.tar
/dev/bus/usb/001/032
/dev/bus/usb/001/032
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
Close Connection

then reboot to recovery -> "Apply update from ADB" -> then sideload of your file:

adb sideload lineage-21.0-20240107-UNOFFICIAL-a52sxq.zip
Total xfer: 1.00x

But on the phone there's an error - signature verification failed:

View attachment 6053966

hmm... and in the upper part of the screen:

"WARNING: Previous installation has failed.

Your device may fail to boot if you reboot or pwer off now"

Hmm... what went wrong?

Phone was on Android 14 and OneUI 6.0, latest december patch.
[Samsung Galaxy A52s 5G] Simon1511:
This is due to it being an unofficial builds as those aren't signed using LineageOS's private keys.

I think a build of lineage recovery for LineageOS 21 should do the trick. Can you try this one? https://downloads.simon1511.de/s/wKfnN4BcZpqAYXA
[Samsung Galaxy A52s 5G] m00ns0rr0w:
ok, did a try... boot into download mode and flash again; odin output (slightly different):

odin4 -a recovery.tar -b vbmeta.tar
Check file : recovery.tar
Check file : vbmeta.tar
/dev/bus/usb/001/039
/dev/bus/usb/001/039
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
recovery.img
vbmeta.img
Close Connection

Then reboot into recovery, wipe/reset and sideload; command line is ok, but same error on the device again.
[Samsung Galaxy A52s 5G] Simon1511:
Are you sure the lineage 21 zip isn't corrupted? It works just fine for me here.
[Samsung Galaxy A52s 5G] m00ns0rr0w:
re-downloaded the LOS zip file and sideload again - same error. error message in the upper half of the device:

View attachment 6053978

hmm... 2 times downloaded via vivaldi, now download zip with firefox and test again - same error.

as i don't think that someone is manipulating my downloads... no idea. sry, off for today, i'll leave the device in recovery and could continue tomorrow late afternoon (CET). maybe you have an idea...worst case: flash stock firmware and restart from scratch.

thx so far :)
[Samsung Galaxy A52s 5G] Simon1511:
You are using the stock Samsung recovery in that picture..... You can absolutely ignore that one. At this point I would suggest just going with TWRP.
[Samsung Galaxy A52s 5G] m00ns0rr0w:
Strange... does that mean that the flash of the LOS recovery failed somehow?

Anyway, continued with TWRP. Flashed TWRP and ... damn, that's always a quick, sudden reboot when flashing recovery, gotta remember that... TWRP was installed, boot into it and then i installed your system via adb sideload, wiped cache/metadata and ... taadaaaa! Now it worked.

So... setup running, will continue with install and do some testing. Thx! :)
[Samsung Galaxy A52s 5G] oakvx:
Try with TWRP, for me worked just fine
[Samsung Galaxy A52s 5G] monlock:
what about the battery backup?
[Samsung Galaxy A52s 5G] luke panic:
I had the A52s lying around and decided to try a few roms. This one is awesome! Thanks a lot! I am using it productively and haven't faced any big issues as of yet. Only one small thing: Registering more than one finger print will make finger print detection unusable. That's ok.

I did also flash mindthegapps and use Magisk with LSposed. Use LP for purchase emulation with satisfying results dispite Android 14.

Please maintain :)
[Samsung Galaxy A52s 5G] luke panic:
View attachment 6055545

View attachment 6055546
[Samsung Galaxy A52s 5G] Tuned modified:
Does this have the unlimited back up photos (google photos)
[Samsung Galaxy A52s 5G] Simon1511:
No, it does not.
[LG V30 Questions & Answers] Open.Orange:
Excuse me, I've a wired problem (logs as follows) while trying to compile a kernel with KernelSU support of LG V30.

Here's my steps but it returns errors in the end, and I've no idea why.

Could anyone give me a hand? I'll appreciative your help. :)

ERROR LOGS

warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_APPLETOUCH which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_BCM5974 which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_SYNAPTICS_USB which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_GADGET) selects LGE_USB_FACTORY which has unmet direct dependencies (USB_GADGET && LGE_USB_GADGET && LGE_PM_LGE_POWER_CLASS_CABLE_DETECT)
warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_APPLETOUCH which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_BCM5974 which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_SUPPORT_LIST_INPUT) selects MOUSE_SYNAPTICS_USB which has unmet direct dependencies (!UML && INPUT && INPUT_MOUSE && USB_ARCH_HAS_HCD)
warning: (LGE_USB_GADGET) selects LGE_USB_FACTORY which has unmet direct dependencies (USB_GADGET && LGE_USB_GADGET && LGE_PM_LGE_POWER_CLASS_CABLE_DETECT)

Environment：Canonical Ubuntu 22.04 Minimal with AMD EPYC 7551 Processor

Kernel source is obtained from http://opensource.lge.com/
[Samsung Galaxy S7 Active Questions & Answers] SteveRedmond:
hi guy i have s7 active and it suck on android 8 , i cannot downgrade , i try all method on xda but odin just error , this is my imel 352333080455404 , all cellular work ok , i was try odin mod but it like befor , i want to root my device it at&t version , thanks for reading
[Samsung Galaxy S7 Active Questions & Answers] Topo's:
It seems like you're having difficulties downgrading your Samsung Galaxy S7 Active to an older Android version, and you're interested in rooting your device. It's important to note that rooting and modifying your device's software can carry risks, and it may void your warranty. Additionally, the process can vary based on the device model and carrier restrictions. Here's a general guide, but make sure to follow the instructions carefully and understand the potential consequences:

### Rooting the AT&T Samsung Galaxy S7 Active:

**1. Check Software Version:**

- Ensure that your device is running the latest available firmware version.

**2. Unlock the Bootloader (if required):**

- Check if your device's bootloader needs unlocking. Note that not all devices or carriers allow bootloader unlocking.

- If permitted, follow the official bootloader unlocking process for your device.

**3. Download Required Files:**

- Download the necessary files, including Odin and the correct TWRP recovery image for your device model.

**4. Enable Developer Options:**

- Go to "Settings" > "About phone" > tap "Build number" seven times to enable Developer Options.

**5. Enable OEM Unlocking:**

- In Developer Options, enable "OEM unlocking."

**6. Flash TWRP:**

- Use Odin to flash TWRP recovery to your device. Follow specific instructions for your device model and TWRP version.

- Boot into recovery mode using the key combination (often Volume Up + Power + Home).

**7. Backup Your Data:**

- Before rooting, it's essential to back up your data to prevent any loss during the process.

**8. Root Your Device:**

- Flash a root package (such as Magisk) using TWRP recovery.

- Reboot your device, and it should now be rooted.

### Important Considerations:

- **Warranty Void:** Rooting your device may void its warranty. Be aware of the consequences.

- **Custom ROMs:** Once rooted, you can explore custom ROMs for your device if you're interested in running a different Android version.

- **AT&T Restrictions:** Keep in mind that AT&T devices often have restrictions, and they might not be as developer-friendly as unlocked models.

- **Bricking Risk:** Improperly following the rooting process can lead to bricking your device. Ensure that you understand the instructions and proceed at your own risk.

For device-specific details and updated information, it's recommended to check the XDA Developers forum for your specific Galaxy S7 Active model and carrier. They often have dedicated threads with step-by-step guides and solutions tailored to your device.
[Samsung Galaxy S7 Active Questions & Answers] SteveRedmond:
but i cant unlock bootloader becáuse it at&t version , but i can turn on oem unlock