thank you so muchheimdall is a pain for windows. odin is much easier to deal with.
first, rename the lineage recovery to recovery.img, and pack it into a tar file
flash the tar file into AP using Odin, turn off autoreboot
after flashing the recovery, turn off the device using volume down + power, then quickly hold volume up + bixby + power to reboot straight into recovery. if you did it correctly, you'll boot into lineage recovery. if not, you will have to start again from flashing via odin (note that the USB cable needs to still be connected for the button combinations to boot you into the proper modes)
when you have loaded into the recovery, wipe and format your data partition. then, get adb on your computer and use adb sideload to flash the lineageOS zip. it will go up to 47% then show an error. that is expected and is normal.
flash gapps and magisk/lygisk similarly if necessary
when done, reboot into system. everything should work fine from there.
I don't know for sure how building a custom OS works, but I think as development of LOS on a particular device evolves, OEM binaries of proprietary source code which may have been used for managing such things in early development later get replaced with an open source coded equivalent. Someone please correct me if I'm wrong.Can't control bluetooth volume from car stereo.
I'm reading alot about codecs and such but just can't understand how my same phone could work perfectly when it was stock android 10 but now when I install lineagos on the same device, I am not able to use that same codec to get it working correctly to control the volume with my stereo unit.
thanks for any help
Could be a setting such as "Lift to wake", or "wave to show time". I can't remember if the S10 has these settings exactly. Have you tried typing into the search bar in the settings words such as "wake" or "show"?
I fixed it by removing google dialer
The official Samsung ROM makes the AOD shift by a couple of pixels every minute to prevent/lessen the burn in.
so you are saying that maybe this is not possible to somehow install the audio codec from the stock one ui which had a working bluetooth car stereo communcation button function, onto this LOS rom?I don't know for sure how building a custom OS works, but I think as development of LOS on a particular device evolves, OEM binaries of proprietary source code which may have been used for managing such things in early development later get replaced with an open source coded equivalent. Someone please correct me if I'm wrong.
I didn't know that
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem
TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadaysHi Linux4,
Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.