It does as long as you have Gapps Installed.
Was feeling lucky and tried it - I can confirm this ROM (with OpenGapps) is compatible with DJI Fly (in my case Mavic Mini) and DJI Go (in my case Phantom 3)!
From what I understand via the dev @Linux4 a clean install is best/required to move to Official.Hi all,
Should it be possible to update from the unofficial rom to the official rom via OTA? Or do I need to do a traditional installation (meaning heimdlall) with the official version first?
I'm currently running the unofficial version on this rom dated July 19th on my S10 and when I go to the phones Updater and refresh it says "no new updates found". Am I missing something here or is there actually no new updates yet available? I was reading the thread and understood there should be an update available dated August 6th.
My installation is a clean lineageos with no rooting, no spoofing, no magisk, no twrp and no google stuff.
All the previous updates I have done successfully via OTA when the ROM was in unofficial state.
See https://lineage.microg.orgThank you @Linux4 ! I have installed this ROM on my wife's new S10+. So far so good, got to transfer most things over from her previous phone.
Need to find a good solution for Signature Spoofing, appreciate any recommendations but don't intend to take this thread OT.
hello @Linux4 , when I open this file in the stock one ui rom with root browser, the key no. 703 is set as the bixby key, I set it to turn the screen on and off by typing POWER, but there is no place number 703 in these AOSP roms.
how can i find this bixby key in Aosp roms?
Is this thing only for the Lineage Recovery and not TWRP?You're either not on this ROM then or you decrypted /data which will NOT be supported in here.
Same applies to TWRP, it's not supported and it will likely cause issues - you're completely on your own if you use that.
Magisk's addon.d doesn't work at all on devices with encrypted /data ... Manually flashing vs using OTA won't change anything about that fact
Also just reflashing magisk after OTA is enough, modules won't be gone.
For Galaxy Wearable app to work run the following in a root shell,
either by using "adb root" and "adb shell" on your PC or in termux, connectbot etc after running "su" (needs e.g magisk)
mount -o remount,rw /
mount -o remount,rw /vendor
sed -i 's/samsung/google/g' $(find / -name build.prop)
Note: You may replace google with anything you like in the last command as long as it's not 'samsung'
Note: You will need to re-run this after every OTA
It's because you do not need vbmetaHi guys,
i'm preparing to install this official version and i'm wondering which vbmeta file should i use, if any? There is no mention of a vbmeta file in the instructions but i remember needing one when installing the unofficial version of this rom.
I'm currently running the unofficial version of this exact same rom on S10 so i believe i need to do a complete clean install to get this official rom into use, meaning installing the latest custom recovery including a vbmeta file, doing a complete factory reset and data wipe and then installing the official rom. Please correct me if i have misunderstood something.
Im new to here (but not so new with installing roms for androids) and readed many pages about this topic, interessing! And appreciated the work!
Well, had S5 for long time with lineageos and its such antic thing (many thanks to Lineageos, that why using for long time). So time for a new phone and bought an second hand S10 exynos. Shocked again about such Samsung and Google bloatware, immediatly went into this topic and Lineageos wiki to install this rom into.
One thing im stucked with is, succesfully flashed with Heimdall (have to unlock bootloader within download mode, otherwise, not flashable) with lineageos recovery image file. But i cant get into Lineageos Recovery mode after its flashed. So first while at download mode, pressing volume down and power button, when screen goes black, immediatly volume up + bixty + power button while cable is connected to my laptop, but it will pass every time to Samsung stock rom. Looked whole internet and youtubes videos and do it same. When going to recovery mode without flashing (from samsung itself), it works. Probaly new update (wich previous owner installed?) of samsung blocks, to get into Lineageos recovery mode? I mean, it does looks something is blocking me from to get into Lineage recovery mode from download mode.
I am following this guide: https://wiki.lineageos.org/devices/beyond1lte/install
Like this video, i did extactly (only the buttons part, to get into Lineage recovery mode) but it passing and going to Starting samsung stock rom:
I want to move to this rom but everytime I flash it ;
1. Flash lineage recovery
2. Format data
3. Flash rom.zip , gapps.zip and lygisk.zip
I have a lot of trouble with my Microsoft account. Like I'll go to sign into outlook etc but the screen just goes blank. Also 2FA doesn't work for me.
I'm currently using evolution x that also uses lineage recovery
However, I accidentally installed lygisk on it and the phone obviously wouldn't work properly, until I flashed magisk after a clean wipe, I Couldn't sign into Microsoft, XDA etc
It now works ok after flashing magisk
Am I missing something?
Thank you very much for the quick reply!
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.