[ROM][EXYNOS] LineageOS 17.1 for S10e|S10|S10+ - v1.4 (UPDATE: 2020-12-17)

Search This thread

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
- - - - - -
This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
- - - - - -


lineage_17.1_banner.jpg

FEATURES

We provide a secure and up to date ROM, check the Lineage Trust status of your phone!

Secure ROM

  • Fine-grained SELinux policy
  • Latest 4.14 Linux Kernel release
  • Improved performance
  • Wireguard support
  • USB restrictions
  • AES-256-XTS File Based Encryption (FBE)
  • Signed with developer keys

Nice features

  • FDroid and AuroraStore preinstalled
  • Bluetooth phone calls

lineage_version.png
lineage_trust.png


KNOWN ISSUES

Don't be scared by the "BETA" label. Our ROMs are always rock solid.

  • Some audio effects are missing
  • Miracast not working
  • Wideband SCO
  • IMS not working (No AOSP solution yet)

Some minor issues are described in the FAQ below.

DOWNLOAD

You can download the latest version under the following links:

S10e
S10
S10+


INSTALLATION

Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.

Make sure you select: Zip signature verification.

This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.

SECURITY ADVICE

Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
Do not flash Multi Disabler on this ROM!


What a Wurst!

This ROM is developed by derf elot, linux4 and modpunk

XDA:DevDB Information
lineage_s10_exynos, ROM for the Samsung Galaxy S10

Contributors
modpunk, derf elot, linux4
Source Code: https://github.com/whatawurst

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: XXS9DTK9
Based On: LineageOS

Version Information
Status:
Stable
Current Stable Version: v1.4
Stable Release Date: 2020-12-14
 
Last edited:

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
REQUIRED FIRMWARE: XXS9DTK9

CHANGELOG


2021-01-xx | 2.0
  • Added support to disable fast charging
  • Kernel fix to disable the touchscreen during handheld phone calls
2020-12-17 | 1.4
  • Add support for glove mode

2020-10-26 | 1.3
  • Update to Linux 4.14.206


2020-10-26 | 1.2
  • Update to Linux 4.14.202
  • Added Seedvault (Video)
  • Fixed bluetooth regression
  • Fixed NFC service registration (SELinux denials)
  • Fixed camera issues
  • Fixed LineageOS recovery

2020-09-11 | 1.1
  • Update to Linux 4.14.196
  • Added Kernel changes from CTG4 (fixes usb audio issues)
  • Improved DT2W support (thanks linux4)
  • Fixed camera access to some sensors

2020-08-08 | 1.0
  • Update to Linux 4.14.192
  • Performance improvements
  • New thermal HAL for better overheating protection
  • Fixed light sensor auto-brightness
  • Fixed extended-length NFC (required for ePerso App)

2020-07-13 | RC2
  • Update to Linux 4.14.188
  • Fixed reboot issue with new Power HAL
  • Fixed crash issue with power HAL
  • Update to latest Security release
  • Removed su for adb root

2020-07-06 | RC1
  • Update to Linux 4.14.187
  • Performance improvements (new power HAL)

2020-06-17 | BETA3
  • Update to Linux 4.14.184
  • Update to Wireguard 1.0.20200520
  • Fixed HDR support
  • Upstreamed vibrator service implementations

2020-05-20 | BETA2
  • Update to Linux 4.14.177
  • Added Wireguard support
  • Added support for L1 widevine security level (Netflix etc.)
  • Added in-screen fingerprint support for S10(+)
  • Added "Wireless Powershare" support
  • Get the full list of sensors working, including tilt, rotation_vector, game_rotation_vector and pick_up_gesture
  • Fixed USB tethering
  • Fixed wifi hotspot
  • Fixed proximity sensor
  • Fixed phone calls over bluetooth
  • Fixed phone off charger with nice animation now

2020-04-14 | BETA1
  • Update to Linux 4.14.175
  • Added magisk building support
  • Added USB Trust HAL
  • Added "Always On Display" quick setting tile (merged upstream)
  • Fixed performance issues
  • Fixed video calls (e.g. in Signal)
  • Fixed proximity sensor
  • Fixed significant motion sensor

2020-04-05 | BETA0.1
  • Fixed Play Store
  • Fixed permission list
  • Added missing vendor properties
  • Fixed product definitions

2020-04-03 | BETA0
  • Initial release


OUR UPSTREAM EFFORTS

 
Last edited:

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
Features + Known Bugs Summary:
This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.


Ratings Description
  • ++ perfect (in depth tested, performs like stock or better)
  • + good (lighly tested only or has minor flaws but is good enough for normal use)
  • o ok (can be used with some limitations)
  • - broken (doesn't work at all)
  • x not supported (unlikely to be implemented, relies on samsungs closed source code)
  • ? can't test, please give feedback

Performance
  • ++ geekbench 5 score: 2267 (gsmarena stock: 2141)
  • ++ antutu v8.4.1 score: 403909 (gsmarena stock: 389694)

Speed (values in MB/s, sr =seq. read, sw = seq. write, rr = random read, rw = random write)
  • ++ internal SD 128GB
    • AndroBench5: sr 815.0, sw 193.1, rr 138.7, rw 24.7 (= notebookcheck stock)
    • CPDT 1GB: sr 735.3, sw 139.2, rr 19.2, rw 4.52
  • ++ external SD, 128GB Samsung Evo Plus
    • Androbench5: sr 68.2, sw 34.5, rr 5.75, rw 2.56
    • CPDT 1GB: sr: 75.2, sw: 29.5, rr: 4.08, rw: 1.71
  • ++ USB 3.0 MTP, sw 105MB/s (PC CrystalDiskMark -> mtpdrive -> internal SD)
  • ++ USB 3.0 OTG, sw 105MB/s (Sandisk Extreme 64GB -> internal SD, 10.8GB file, 102s)
  • + bluetooth file transfer, 0.1MB/s (29MB; from other phone 4m42s, from PC 5m24s) (theoretical max. is 0.3 for BLE4.0, 0.8 for BLE4.2 and 1.4 for BLE5.0)

Connectivity
  • ++ phone calls, 3G, LTE; also with dual sim
  • ++ wifi (delivers 50Mb/s, the maximum my provider supports)
  • ++ bluetooth (file transfer to phone & pc; headphons incl. mic; speakers; keyboard incl. special keys)
  • ++ NFC (only card read tested)
  • x VoLTE

Screen
  • + 10 finger multitouch, "high touch sensitivity" mode not available
  • ++ full brighness range available
  • ++ double tap to wake
  • + AOD works, but might be dimmer than stock and brightness cant be changed. While active the proximity sensor is used an its LED blinks dimly next to the camera

Sound
  • ++ dual laudspeaker for media, quality as expected, high volume selectable
  • + earpiece (no in depth test)
  • + headphones (3.5mm jack) have clean audio, high volume selectable, limited to 16bit/48kHz (instead of 24bit/192kHz) possibly by ROM
  • + build-in mic, limited to 16bit/48kHz (instead of 24bit/192kHz), volume should be normal (test)
  • + headphone mic, limited to 16bit/48kHz (instead of 24bit/192kHz)
  • + some external DACs supported, limited to 24bit/48kHz; (reported by @El Dun)

Camera (with opencamera + camera API v2)
  • ++ wide, ultrawide, front, front-crop
  • ++ PDAF autofocus, face tracking optional (main + front camera, ultrawide is always fixed focus)
  • ++ manual setting for exposure/ ISO/ shutter/ focus
  • ++ raw files option (main camera)
  • ++ optional HDR
  • + dual apperature (main camera), only manual switch (default f1.5)
  • + video up to 2160p/30fps, 1080p/30fps (all cameras should support 60fps, but OpenCamera only produces 30fps files)
  • + 1080p/240fps (main)/ 1080p/120fps (front) high speed/ slow-mo works in stock cam + GCam
  • x no 720p/960fps super slo-mo
  • x no supersteady
  • - S10, S10+: no telephoto camera (details + help wanted)
  • x S10+: no front depth camera

Sensors
  • ++ gps, quick fix with A-GPS data
  • + fingerprint (all variants), can glitch during setup (see bug list)
  • ++ accelerometer, gyroscope, magnetometer, pressure, light (front) (all values are within tolerance)
  • + light sensor, but only the front/ under-screen sensor, not the rear sensor
  • ++ IR/RGB sensor outputs values for IR/Red/Green/Blue/Clear (test) (COM.SAMSUNG.SENSOR.LIGHT_IR)
  • ++ grip sensor
  • + front proximity (makes only one measurement per second, if you put it quickly to your ear it may touch the screen before it's turned off; reported by @Lav64)
  • ++ software sensors: step counter, rotation vector, gravity, linear acceleration, compass
  • ++ S10/S10+ heart rate/ SpO2 (confirmed by @Ned)
  • o several software sensors don't produce data, but don't do it on stock either. Affected are the IDs: PICK_UP_GESTURE, COM.SAMSUNG.SENSOR.PROXIMITY_POCKET, COM.SAMSUNG.SENSOR.HALLIC, COM.SAMSUNG.SENSOR.BIO_IR (proof thanks @Brembo109, more info from modpunk)

Charging & Battery
  • ++ 15W quick charge
  • ++ 4.75W reverse charge (with USB OTG adapter)
  • + 7.5W+ qi-wireless charge (limited by my charger)
  • + 2.5W+ reverse qi-wireless charge (limited by the receiver IC BQ51013)
  • + low 40mW idle power consumption (details)
  • + ACCA (advance charging controller app) works with limited settings

Misc
  • ++ all buttons, bixby can be reprogrammed (workaround for other functions)
  • ++ wired headphone buttons (pause/play, vol+, vol-)
  • + flashlight has only one brighness option (instead of 5 on stock)
  • - S10e: no fingerprint swipe up/down geture, not even with 3rd party app "Quick Fingerprint Geture"

Known bugs:
  • when phone is shut down, it reboots instead (fixed in RC2)
  • reboot to recovery boots directly into system (fixed in RC2)
  • reboot takes long, about 30s (fixed in RC2, now it only takes a few seconds)
  • double tap to wake not always working (should be fixed in RC2)
  • holding fingerprint too long during setup can cause problems details
  • in full screen apps there may be a black bar to hide the camera cutout which can not be disabled (details, workaround)
  • high sensitivity touch screen / "glove mode" not available (details)
  • bixby-button hold-shortcut does not work (details)
  • google backup does not work with 4x4 or 5x5 pattern. This is an LineageOS issue, but important enough to deserve a note here. (details (thanks @Ivo_Todorov)


Installation:

How do I install this ROM on my phone for the first time?
Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.

  • Confirm the firmware version
    • Check the top of the ChangeLog which firmware version is required for the ROM release to work well
    • Go to settings/software-update and update only if the new version matches the requirement!
    • Alternative: flash with odin/heimdall (details see below)
  • Unlock your device
    • Backup all data, unlocking will factory reset your phone
    • Enable developer mode to and enable the OEM-unlock switch there
    • Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
    • Follow instructions on-screen
    • Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
    • Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
  • Install our TWRP (official thread) | more details (thanks @AndrOdin)
    • Download our TWRP recovery and the vbmeta-disabled.img file
    • Unpack the .xz file with 7zip
    • Check integrity of TWRP (optional, but important for security)
    • Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
    • Install Samsung USB drivers and odin, (direct link)
    • Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
    • Turn off device, boot to bootloader and, once odin detects it, click "Start"
    • When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
    • When the secondary warning appears, release everything but VolumeUp
    • Swipe slider to allow for modification
  • Install LinageOS
    • copy the ROM ZIP file an external SD card
    • Boot into the recovery
    • Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
    • Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
    • Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
    • Optional: Flash GAPPS (e.g. OpenGAPPS)
    • Reboot to system

How do I update LineageOS?
Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:

  • Backup all important files optional, but very helpful if something goes wrong)
  • Remove any pin/password/pattern to prevent "retry after 86400 seconds"
  • Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
  • Boot into the recovery, do not reboot until you've installed the new ROM and firmware
  • Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
  • (Optional: Update GAPPS to the latest version)
  • Wipe dalvik and cache
  • Reboot to download
  • Flash new firmware with instructions below
  • (Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
  • Reboot to system


How do I update the firmware?
On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.

How do I update the firmware manually?
Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:

If you use Heimdall:

  1. Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
  2. Extract the package
  3. Flash the firmware files with this command:
Code:
heimdall flash \
    --BOOTLOADER sboot.bin \
    --PARAM param.bin \
    --UP_PARAM up_param.bin \
    --CM cm.bin \
    --KEYSTORAGE keystorage.bin \
    --UH uh.bin \
    --DTB dt.img \
    --RADIO modem.bin \
    --CP_DEBUG modem_debug.bin

If you use Odin:
  1. Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
  2. Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
  3. Flash the 3 files with Odin (tested with latest Odin 3.14.x)

You can download the repacked firmware from the links below.
  1. S10
  2. S10e
  3. S10+

If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:

  1. From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
  2. CP_G97?FXX*.tar.md5
  3. Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4


Try again after 86400 seconds?
With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)

You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.



3rd Party Software:

How do I install Google apps?
You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.

Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!


Can I use GPay? What about other banking apps
GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).

Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!

How do I get MicroG with this ROM?
MicroG is an open source alternative to GAPPS. , but unfortunately not recently updated and therefore not recommended.

If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14 . Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)


Does this ROM have root?
Not by default. If you need root (eg. for AFWall) you can get it through Magisk.

How do I install Magisk?
Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!

Option 1 (recommended):

  • Download the boot image for Magisk: S10e -- S10 -- S10+
  • Verify the integrity of the file -> See INTEGRITY
  • Unzip the boot image using xz or p7zip
  • (Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
  • Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
  • Install https://******************/

Option 2:


Which camera app do you suggest?
OpenCamera:
Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
  • All cameras supported (except telephoto, this is a issue with the ROM)
  • Manual change of exposure, aperture, shutter speed, ISO
  • The (main) developer uses an S10e himself so you can expect good HW support :p
You can get it from F-Droid or Play Store

GCam Variants:
There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).

In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
  • simpler user interface
  • better single-shot HDR
  • better panoramas + photospheres
  • SlowMo video (1080p @120/240fps)
I've also written a more detailed comparison. You can have both camera apps installed at the same time, so you can always choose the better one depending on the scenario.


Getting Help:

General:
Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here :) We do this in out free time and it may take us some time to answer, so please be patient.

How to report a bug?
To fix any bug we first have to be able to reproduce it. Please include all relevant information:
  • device (S10e/S10/S10+)
  • ROM version
  • is gapps/ microg/ magisk installed?
  • steps to reproduce the issue

When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).

How to create a logfile?
To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:

  • install adb drivers
  • open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
  • Connect your phone via USB
  • Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
  • Clear the log using: adb logcat -c
  • Start loggingwith: adb logcat | tee beyond.log
  • Reproduce the issue
  • Stop logging by pressing CTRL+c
  • Send us the log (in a PM)

How do I enable USB Debugging?
To enable USB Debugging you need to do the following steps:

  • Go to Settings -> About Phone
  • Look for Build number
  • Tap on Build Number several times till you get the message that Developer Options have been enabled
  • Go to Settings -> System -> Advanced -> Developer Options
  • Enable USB Debugging


About this FAQ:
This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.

Changelog:
20200813 (v1.0)
  • update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
  • update: firmware update section (thanks @Stef4n82!)
  • update: ROM update section
  • update: getting help section, rewritten for clarity
  • update: proximity sensor, slow sample rate (thanks @Lav64)
  • update: audio section with my test and @El Dun's report
  • add: gpay/safetynet explanation
  • change: link formating to stay under the 30k character limit

20200809 (RC2)
  • update: audio output with limited frequency range, limited DAC support (thanks @El Dun)
  • update: double tap to wake works well, used it for a few weeks now without issues
  • update: "86400 seconds" section (thanks @Exilion90)
  • add: links to each version of this FAQ, just click one of the datecodes
  • add: ACCA to feature list
  • add: ADO works kinda
  • add: dual sim to feature list (thanks @Exilion90)
20200802 (RC2)
  • update: microG section (thanks @ichmyselfandi)
  • update: unlock instructions, setup with wifi required (thanks @Lunat1c)
  • update: "86400 seconds" section (thanks @Lunat1c & @Stef4n82)
  • add: gapps/ microg/ google framework requirement for the GCAM (thanks @KanyT & @ned14)
  • add: bug google backup pattern with 4x4 or 5x5 pattern (thanks @Ivo_Todorov)
  • fix: twrp "more details" link (thanks @Lunat1c)
20200719 (RC2)
  • update: rgb light sensor, all channels working
  • update: software sensors don't output values on stock either (thanks @Brembo109)
  • add: gcam information (thanks @ned14)
  • add: grip sensor
  • add: microg appendum (thanks @ned14)
  • add: workaround for black status bar in fullscreen
  • add: bug no glove mode (thanks @raggatip)
  • add: bug bixby button hold shortcut (thanks @Lav64)
20200713
  • update: feature/ bug list (previously called working/ not working) with fixed from RC2
  • update: instructions for microG (thanks @ned14)
  • update: magisk install instructions
  • update: wireless power share works fine, the phone just didn't like the synthetic load I used for testing
  • add: black bar on camera cutout in fullscreen apps (thanks @Sradgads)
20200707 (RC1)
  • update: section "get help" with copy & paste template
  • update: font for cmd to Courier New
  • confirm: removing pin/password/pattern solves the 86400 second wait delay (thanks @fishnetfancy)
  • add: working/not working section
  • add: this changelog
  • add: telephoto lens not working (thanks @Ned)
  • add: several RC1 issues (thanks @angela5246)
  • add: vbmeta_disabled note to firmware instructions (thanks @okloloi)
  • add: reminder to update Magisk alongside lineage (thanks @fishnetfancy)
20200705 (Beta3)
  • first FAQ update by me (ctrej)
  • change: order to the "natural" installation flow
  • change: install section into a more detailed checklist (thanks @AndrOdin)
  • add: sub-sections (install/ 3rd party/ support)
 
Last edited:

angela5246

Senior Member
Mar 27, 2020
62
13
Great news, thanks a lot. Your work is much appreciated.

I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?

Again, thank you very much for your effort.
 

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
Great news, thanks a lot. Your work is much appreciated.

I run LOS from 31.03. from Ivan now. Can I easily flash yours now? As I see Ivan includes vendor files in his release. Is this something I need to consider before flashing your version? And last but not least - I would like to build from your sources. Mainly because I dont want to have Aurora and Fdroid included. Is there a recipe ready for building from scratch?

Again, thank you very much for your effort.

If you switch, you have to format /data I'm sorry. We decided to go with AES-256-XTS encryption for this ROM and also the code is signed with my developer keys! There are package signature checks in place for apps which would prevent you to use the ROM.

If you want to build it yourself, instructions are in the beyond0lte README.

However you can just go to Settings -> Apps and disable FDroid and AuroraStore.

Also I've added and AOD (Always On Display) Quicksetting Tile, but this hasn't been merged upstream yet. You might want to pick those changes.
 
Last edited:

BratoMo225

Senior Member
Sep 20, 2014
130
19
Mostar
I cant flash it. Im using latest twrp 103
 

Attachments

  • Screenshot_2020-04-03-03-44-34.png
    Screenshot_2020-04-03-03-44-34.png
    128.6 KB · Views: 1,347
  • Screenshot_2020-04-03-03-38-02.png
    Screenshot_2020-04-03-03-38-02.png
    205.7 KB · Views: 1,329

BratoMo225

Senior Member
Sep 20, 2014
130
19
Mostar
No. The one i downloaded from ianmcd thread.

---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------

Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what
 

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
No. The one i downloaded from ianmcd thread.

---------- Post added at 09:26 AM ---------- Previous post was at 09:06 AM ----------

Well now after flashing your twrp, and restarting into recovery mode, my phone wont turn on. It says Could not do normal boot invalid kernel length. When i connect my phone to pc, it just loop restarts. now what

Did you also flash a vbmeta image which disables vbmeta checking?
 
  • Like
Reactions: Meemo23

derf elot

Senior Member
May 7, 2011
842
1,831
can i flash magisk via twrp or are there any extra steps i need to do before it will work?

I'll upload a boot.img which is pre-patched for Magisk 20.4. You can flash this via twrp and Magisk should work, just need to install the Magisk Manager.

edit: Here it is https://www.androidfilehost.com/?fid=4349826312261761185 Unzip the file. If you wish, you can verify it using gpg, then flash the boot.img via TWRP.
 
Last edited:

vomad

Senior Member
Jun 8, 2017
108
44
Volgograd
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....
 

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,546
What about Live display settings in this build? Does it have different color profiles (sRGB for example as it was on S9 series LOS 15.1/16/17.1) or not? Ivan's ROM has only standard "vivid" gamma and white balance correction....

Live display is fully working. derf elot fixed the last bit yesterday iirc. The manifest entry was wrong for one part of livedisplay.
 
  • Like
Reactions: Meemo23 and vomad

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Hi, does anyone know how Modpunk has created the Magisk pre-patched boot images?

    I went through the Magisk docs and it says since our device's boot image doesn't have a ramdisk and System-as-root is 'Yes', we are supposed to patch recovery images. This isn't a new change, the old docs for Magisk v20.4 that v1.4 rom is pre-patched with also notes the same.

    I have checked the vanilla boot image and Magisk boot image for v1.4 and neither has a ramdisk, so I was wondering how!

    I have built v2.0 image for 17.1 branch (S10e) and uploaded them here.
    Kernel: 4.4.212
    Android Security Patch Level: March 2021
    3
    As fishnetfancy has no doubt discovered by now, quite a number of people have recently experienced problems with TWRP reading encryption after an update of this ROM. I also had problems, and I can confirm that the recovery uploaded by lakkimsetty.baba does in fact solve the problem for me. Thanks for that!

    It's still unclear to me why some users have problems using the modpunk TWRP with 1.4 of this ROM and others have not. But I suspect it might have something to do with skipping versions, as that seems to be the uniting factor (correct me if I'm wrong).

    @kybsmds
    I still hope that modpunk will return and continue development. It is taking quite a bit of time now, but he still could return and I still expect that this ROM will continue. It could even be picked up by other devs. Personally, I'm also interested in the /e/ build, but that thread also seems to have quieted down... Bottom-line: I'll be waiting in (relative) silence a bit longer.
    3
    I am wondering what the best way forward would be. I have owned many Samsung devices (both, tablets, and phones) and they have all fallen off the Lineage support sooner or later. Usually this does not happen as quickly as it did with the S10+ (from what I gather development of this ROM has now ceased?) and I am absolutely not blaming any of the developers who dedicate so much of their time and effort to creating and maintaining phone support - in fact I am just grateful they keep this community project going and I can choose a non-Google alternative for me and my family.

    But going forward I do wonder how to best pick a phone that may have slightly longer support from devs (can't believe S5 is still being suppoorted!). Possibly thinking of switching to Google Pixel in the future - does anyone have thoughts on what might be a good phone in the future?
    There's a lot of options how to go forward. In my opinion, it's best not to rely on 3rd party developers like Crdroid or Ivan Meler etc. Meler for example basically deactivates SELinux and phone encryption, and he also does not release his sources. Best thing would be to stick to devices that get a lot of attention from official LOS developers. Google phones are supported quite well, Oneplus is also a good bet in this regard. There might be some Xiaomi devices too that get a lot of attention these days. In any case, I sure hope that @Linux4 will push his commits to the official LineageOS repo, and if they get accepted, and if he is willing to take over support, we might see 18.1 for S10 becoming officially supported by LineageOS.

    If I am not mistaken Modpunk could build some kind of transition rom which would be then possible to upgrade with another rom. I think CyanogenMod/LineageOS did some transition builds when they took over from CyanogenMod. However - pure speculation on my side - Modpunk might have lost his interest and/or phone. I can see he is quite active on other, non-phone related, projects on github.
    2
    Thanks @flortsch, you are right! Modpunk has already set it up that way. I guess the next step is to update it to Magisk v22.1, set the flags and rebuild.
    2
    I just sold my Galaxy S10e and bought a used Pixel device.
    After trying GrapheneOS, I can wholeheartly recommend it. Automatic update, encryption, hell, even a locked bootloader! And it feels even slimmer than LineageOS.

    On top 4-5 years of assured support from a whole community. I hate to buy a phone from google, but it is the most secure Android out there IMHO.
  • 58
    - - - - - -
    This project provides LineageOS with SELinux for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
    - - - - - -


    lineage_17.1_banner.jpg

    FEATURES

    We provide a secure and up to date ROM, check the Lineage Trust status of your phone!

    Secure ROM

    • Fine-grained SELinux policy
    • Latest 4.14 Linux Kernel release
    • Improved performance
    • Wireguard support
    • USB restrictions
    • AES-256-XTS File Based Encryption (FBE)
    • Signed with developer keys

    Nice features

    • FDroid and AuroraStore preinstalled
    • Bluetooth phone calls

    lineage_version.png
    lineage_trust.png


    KNOWN ISSUES

    Don't be scared by the "BETA" label. Our ROMs are always rock solid.

    • Some audio effects are missing
    • Miracast not working
    • Wideband SCO
    • IMS not working (No AOSP solution yet)

    Some minor issues are described in the FAQ below.

    DOWNLOAD

    You can download the latest version under the following links:

    S10e
    S10
    S10+


    INSTALLATION

    Put the zip file of the ROM on your external SD card boot into recovery. If you use our TWRP recovery, you should use that one to flash the ROM.

    Make sure you select: Zip signature verification.

    This will verify that the signature of the ROM will match the one in TWRP recovery. A more detailed step by step description is in the FAQ below.

    SECURITY ADVICE

    Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
    Do not flash Multi Disabler on this ROM!


    What a Wurst!

    This ROM is developed by derf elot, linux4 and modpunk

    XDA:DevDB Information
    lineage_s10_exynos, ROM for the Samsung Galaxy S10

    Contributors
    modpunk, derf elot, linux4
    Source Code: https://github.com/whatawurst

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: XXS9DTK9
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Current Stable Version: v1.4
    Stable Release Date: 2020-12-14
    26
    REQUIRED FIRMWARE: XXS9DTK9

    CHANGELOG


    2021-01-xx | 2.0
    • Added support to disable fast charging
    • Kernel fix to disable the touchscreen during handheld phone calls
    2020-12-17 | 1.4
    • Add support for glove mode

    2020-10-26 | 1.3
    • Update to Linux 4.14.206


    2020-10-26 | 1.2
    • Update to Linux 4.14.202
    • Added Seedvault (Video)
    • Fixed bluetooth regression
    • Fixed NFC service registration (SELinux denials)
    • Fixed camera issues
    • Fixed LineageOS recovery

    2020-09-11 | 1.1
    • Update to Linux 4.14.196
    • Added Kernel changes from CTG4 (fixes usb audio issues)
    • Improved DT2W support (thanks linux4)
    • Fixed camera access to some sensors

    2020-08-08 | 1.0
    • Update to Linux 4.14.192
    • Performance improvements
    • New thermal HAL for better overheating protection
    • Fixed light sensor auto-brightness
    • Fixed extended-length NFC (required for ePerso App)

    2020-07-13 | RC2
    • Update to Linux 4.14.188
    • Fixed reboot issue with new Power HAL
    • Fixed crash issue with power HAL
    • Update to latest Security release
    • Removed su for adb root

    2020-07-06 | RC1
    • Update to Linux 4.14.187
    • Performance improvements (new power HAL)

    2020-06-17 | BETA3
    • Update to Linux 4.14.184
    • Update to Wireguard 1.0.20200520
    • Fixed HDR support
    • Upstreamed vibrator service implementations

    2020-05-20 | BETA2
    • Update to Linux 4.14.177
    • Added Wireguard support
    • Added support for L1 widevine security level (Netflix etc.)
    • Added in-screen fingerprint support for S10(+)
    • Added "Wireless Powershare" support
    • Get the full list of sensors working, including tilt, rotation_vector, game_rotation_vector and pick_up_gesture
    • Fixed USB tethering
    • Fixed wifi hotspot
    • Fixed proximity sensor
    • Fixed phone calls over bluetooth
    • Fixed phone off charger with nice animation now

    2020-04-14 | BETA1
    • Update to Linux 4.14.175
    • Added magisk building support
    • Added USB Trust HAL
    • Added "Always On Display" quick setting tile (merged upstream)
    • Fixed performance issues
    • Fixed video calls (e.g. in Signal)
    • Fixed proximity sensor
    • Fixed significant motion sensor

    2020-04-05 | BETA0.1
    • Fixed Play Store
    • Fixed permission list
    • Added missing vendor properties
    • Fixed product definitions

    2020-04-03 | BETA0
    • Initial release


    OUR UPSTREAM EFFORTS

    21
    Features + Known Bugs Summary:
    This ROM does already support most features of the hardware. If you need specific features, please check the list below. Each feature was manually tested, so it is possible that it does not match your experience with the ROM. In this case please tell us, see the "Getting Help" section at the end of this post.


    Ratings Description
    • ++ perfect (in depth tested, performs like stock or better)
    • + good (lighly tested only or has minor flaws but is good enough for normal use)
    • o ok (can be used with some limitations)
    • - broken (doesn't work at all)
    • x not supported (unlikely to be implemented, relies on samsungs closed source code)
    • ? can't test, please give feedback

    Performance
    • ++ geekbench 5 score: 2267 (gsmarena stock: 2141)
    • ++ antutu v8.4.1 score: 403909 (gsmarena stock: 389694)

    Speed (values in MB/s, sr =seq. read, sw = seq. write, rr = random read, rw = random write)
    • ++ internal SD 128GB
      • AndroBench5: sr 815.0, sw 193.1, rr 138.7, rw 24.7 (= notebookcheck stock)
      • CPDT 1GB: sr 735.3, sw 139.2, rr 19.2, rw 4.52
    • ++ external SD, 128GB Samsung Evo Plus
      • Androbench5: sr 68.2, sw 34.5, rr 5.75, rw 2.56
      • CPDT 1GB: sr: 75.2, sw: 29.5, rr: 4.08, rw: 1.71
    • ++ USB 3.0 MTP, sw 105MB/s (PC CrystalDiskMark -> mtpdrive -> internal SD)
    • ++ USB 3.0 OTG, sw 105MB/s (Sandisk Extreme 64GB -> internal SD, 10.8GB file, 102s)
    • + bluetooth file transfer, 0.1MB/s (29MB; from other phone 4m42s, from PC 5m24s) (theoretical max. is 0.3 for BLE4.0, 0.8 for BLE4.2 and 1.4 for BLE5.0)

    Connectivity
    • ++ phone calls, 3G, LTE; also with dual sim
    • ++ wifi (delivers 50Mb/s, the maximum my provider supports)
    • ++ bluetooth (file transfer to phone & pc; headphons incl. mic; speakers; keyboard incl. special keys)
    • ++ NFC (only card read tested)
    • x VoLTE

    Screen
    • + 10 finger multitouch, "high touch sensitivity" mode not available
    • ++ full brighness range available
    • ++ double tap to wake
    • + AOD works, but might be dimmer than stock and brightness cant be changed. While active the proximity sensor is used an its LED blinks dimly next to the camera

    Sound
    • ++ dual laudspeaker for media, quality as expected, high volume selectable
    • + earpiece (no in depth test)
    • + headphones (3.5mm jack) have clean audio, high volume selectable, limited to 16bit/48kHz (instead of 24bit/192kHz) possibly by ROM
    • + build-in mic, limited to 16bit/48kHz (instead of 24bit/192kHz), volume should be normal (test)
    • + headphone mic, limited to 16bit/48kHz (instead of 24bit/192kHz)
    • + some external DACs supported, limited to 24bit/48kHz; (reported by @El Dun)

    Camera (with opencamera + camera API v2)
    • ++ wide, ultrawide, front, front-crop
    • ++ PDAF autofocus, face tracking optional (main + front camera, ultrawide is always fixed focus)
    • ++ manual setting for exposure/ ISO/ shutter/ focus
    • ++ raw files option (main camera)
    • ++ optional HDR
    • + dual apperature (main camera), only manual switch (default f1.5)
    • + video up to 2160p/30fps, 1080p/30fps (all cameras should support 60fps, but OpenCamera only produces 30fps files)
    • + 1080p/240fps (main)/ 1080p/120fps (front) high speed/ slow-mo works in stock cam + GCam
    • x no 720p/960fps super slo-mo
    • x no supersteady
    • - S10, S10+: no telephoto camera (details + help wanted)
    • x S10+: no front depth camera

    Sensors
    • ++ gps, quick fix with A-GPS data
    • + fingerprint (all variants), can glitch during setup (see bug list)
    • ++ accelerometer, gyroscope, magnetometer, pressure, light (front) (all values are within tolerance)
    • + light sensor, but only the front/ under-screen sensor, not the rear sensor
    • ++ IR/RGB sensor outputs values for IR/Red/Green/Blue/Clear (test) (COM.SAMSUNG.SENSOR.LIGHT_IR)
    • ++ grip sensor
    • + front proximity (makes only one measurement per second, if you put it quickly to your ear it may touch the screen before it's turned off; reported by @Lav64)
    • ++ software sensors: step counter, rotation vector, gravity, linear acceleration, compass
    • ++ S10/S10+ heart rate/ SpO2 (confirmed by @Ned)
    • o several software sensors don't produce data, but don't do it on stock either. Affected are the IDs: PICK_UP_GESTURE, COM.SAMSUNG.SENSOR.PROXIMITY_POCKET, COM.SAMSUNG.SENSOR.HALLIC, COM.SAMSUNG.SENSOR.BIO_IR (proof thanks @Brembo109, more info from modpunk)

    Charging & Battery
    • ++ 15W quick charge
    • ++ 4.75W reverse charge (with USB OTG adapter)
    • + 7.5W+ qi-wireless charge (limited by my charger)
    • + 2.5W+ reverse qi-wireless charge (limited by the receiver IC BQ51013)
    • + low 40mW idle power consumption (details)
    • + ACCA (advance charging controller app) works with limited settings

    Misc
    • ++ all buttons, bixby can be reprogrammed (workaround for other functions)
    • ++ wired headphone buttons (pause/play, vol+, vol-)
    • + flashlight has only one brighness option (instead of 5 on stock)
    • - S10e: no fingerprint swipe up/down geture, not even with 3rd party app "Quick Fingerprint Geture"

    Known bugs:
    • when phone is shut down, it reboots instead (fixed in RC2)
    • reboot to recovery boots directly into system (fixed in RC2)
    • reboot takes long, about 30s (fixed in RC2, now it only takes a few seconds)
    • double tap to wake not always working (should be fixed in RC2)
    • holding fingerprint too long during setup can cause problems details
    • in full screen apps there may be a black bar to hide the camera cutout which can not be disabled (details, workaround)
    • high sensitivity touch screen / "glove mode" not available (details)
    • bixby-button hold-shortcut does not work (details)
    • google backup does not work with 4x4 or 5x5 pattern. This is an LineageOS issue, but important enough to deserve a note here. (details (thanks @Ivo_Todorov)


    Installation:

    How do I install this ROM on my phone for the first time?
    Below you find a brief checklist of the required installation steps. Installation is more complicated than other ROMs because we take device security very seriously. If you are unfamiliar with installing custom roms , please click the links and read the additional details there.

    • Confirm the firmware version
      • Check the top of the ChangeLog which firmware version is required for the ROM release to work well
      • Go to settings/software-update and update only if the new version matches the requirement!
      • Alternative: flash with odin/heimdall (details see below)
    • Unlock your device
      • Backup all data, unlocking will factory reset your phone
      • Enable developer mode to and enable the OEM-unlock switch there
      • Turn off device and boot to bootloader (hold VolumeDown + Bixby, then connect USB cable)
      • Follow instructions on-screen
      • Finish the initial setup after unlock. You must connect to WiFi, but can skip everything else. Do not specify a pin/pattern during setup afterwards, otherwise TWRP may cause the "try again after 86400 seconds" issue (see below)
      • Confirm in the settings that the bootloader is actually unlocked. (greyed out, telling you its unlocked)
    • Install our TWRP (official thread) | more details (thanks @AndrOdin)
      • Download our TWRP recovery and the vbmeta-disabled.img file
      • Unpack the .xz file with 7zip
      • Check integrity of TWRP (optional, but important for security)
      • Rename files to recovery.img and vbmeta.img; then pack both files together in a .tar archive with 7zip
      • Install Samsung USB drivers and odin, (direct link)
      • Start odin as admin, disable "Auto Reboot" and click "AP "to select the .tar archive
      • Turn off device, boot to bootloader and, once odin detects it, click "Start"
      • When the screen turns off, immediately hold (and keep holding) VolumeUp + Bixby + Power to enter recovery mode
      • When the secondary warning appears, release everything but VolumeUp
      • Swipe slider to allow for modification
    • Install LinageOS
      • copy the ROM ZIP file an external SD card
      • Boot into the recovery
      • Wipe cache + dalvik (wipe->advanced and select cache + dalvik)
      • Format data (wipe->format data, use the dedicated button, wipe->advanced does not work)
      • Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
      • Optional: Flash GAPPS (e.g. OpenGAPPS)
      • Reboot to system

    How do I update LineageOS?
    Updating LinageOS is a lot less work and you can keep all user data. The process is similar to the last part of the installation:

    • Backup all important files optional, but very helpful if something goes wrong)
    • Remove any pin/password/pattern to prevent "retry after 86400 seconds"
    • Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
    • Boot into the recovery, do not reboot until you've installed the new ROM and firmware
    • Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
    • (Optional: Update GAPPS to the latest version)
    • Wipe dalvik and cache
    • Reboot to download
    • Flash new firmware with instructions below
    • (Optional: if you use Magisk, flash the new BOOT file. You can also do this in previous step instead of using Stef4n82's "BL.tar" file.)
    • Reboot to system


    How do I update the firmware?
    On the stock ROM you can update from the settings menu. You can't do this on lineageOS (yet), so ypu need to use use Odin or Heimdall instead.

    How do I update the firmware manually?
    Thanks to @Stef4n82's new instructions and repacked firmware files installation is easier than ever. Below you find a copy of his post:

    If you use Heimdall:

    1. Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Heimdall_????.tar.gz"
    2. Extract the package
    3. Flash the firmware files with this command:
    Code:
    heimdall flash \
        --BOOTLOADER sboot.bin \
        --PARAM param.bin \
        --UP_PARAM up_param.bin \
        --CM cm.bin \
        --KEYSTORAGE keystorage.bin \
        --UH uh.bin \
        --DTB dt.img \
        --RADIO modem.bin \
        --CP_DEBUG modem_debug.bin

    If you use Odin:
    1. Download the latest firmwarepackge for your device: "G97?F_Firmwareupdate_Odin_????.zip"
    2. Extract the package and you will get an AP.tar, a BL.tar and a CP...tar.md5
    3. Flash the 3 files with Odin (tested with latest Odin 3.14.x)

    You can download the repacked firmware from the links below.
    1. S10
    2. S10e
    3. S10+

    If you don't want this repacked firmware packages and want to download the whole firmware by your own. Make sure if you flash it via Odin that you use this files:

    1. From AP_G97?FXX*.tar.md5 take the dt.img and create a new AP.tar
    2. CP_G97?FXX*.tar.md5
    3. Extract BL_G97?FXX*.tar.md5 and create a new BL.tar without the vbmeta.img.lz4


    Try again after 86400 seconds?
    With newer version of the Samsung blobs, if you unlock the storage (/data) with TWRP (ie. you enter your pin/password/pattern in TWRP), the trustzone thinks it is a failed attempt and will lock the storage unlocking for 1 day (86400 seconds). To prevent this do not enter your pin (press cancel) and you can still flash an update. If you tripped the trustzone you can either wayt for 1 day to unlock your device (do not power it off) or try rebooting the phone a few times (thanks @Stef4n82), or this slightly more detailed guide (thanks @Exilion90)

    You can prevent this completely by removing any pin/password/pattern before entering recovery. This does remove all stored fingerprints, so you'll have to set the up again after the update.



    3rd Party Software:

    How do I install Google apps?
    You can download and install the Google Apps from Open Gapps Project. You need ARM64 and 10.x. We suggest to always use the pico package. If you need additional apps you find them in the Play Store.

    Put the Open Gapps ZIP file on your SD card and flash it directly after you flashed LineageOS and before the first boot!


    Can I use GPay? What about other banking apps
    GPay as well as some other banking apps check if the device passes safetynet and will not start if it doesn't. Safetynet fails when the bootloader is unlocked and therefore this ROM will not run GPay and other applications that need it. This official LineageOS statement explains why safetynett will never by bypassed (by default).

    Safetynet used to be easy to bypass with Magisk, but since an Update eralier this year Google uses the TPM module and that can't be circumvented easily. However there might be a workaround with "MagiskHide Props Config", please check out this post and this one. (thanks @Stef4n82) Please note that this has not yet been tested and we can not provide any support. If you got it working on your device, please share how you've done it so we can add it here!

    How do I get MicroG with this ROM?
    MicroG is an open source alternative to GAPPS. , but unfortunately not recently updated and therefore not recommended.

    If you want to install it anyway, read this guide by @JoeRifle and this post (appendum) by @ned14 . Update: It has been reported that the new MicroG version works without issues. (thanks @ichmyselfandi)


    Does this ROM have root?
    Not by default. If you need root (eg. for AFWall) you can get it through Magisk.

    How do I install Magisk?
    Important security Advice: Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!

    Option 1 (recommended):

    • Download the boot image for Magisk: S10e -- S10 -- S10+
    • Verify the integrity of the file -> See INTEGRITY
    • Unzip the boot image using xz or p7zip
    • (Needed for Odin) Rename the file to boot.img and use 7zip to pack it into a .tar file
    • Flash the boot image to the BOOT partition using Odin, Heimdall or TWRP
    • Install https://******************/

    Option 2:


    Which camera app do you suggest?
    OpenCamera:
    Great open source app that supports a lot of the camera's features with the camera API v2 (select this option in the settings):
    • All cameras supported (except telephoto, this is a issue with the ROM)
    • Manual change of exposure, aperture, shutter speed, ISO
    • The (main) developer uses an S10e himself so you can expect good HW support :p
    You can get it from F-Droid or Play Store

    GCam Variants:
    There is no "official" GCam for this ROM, but there are some that work. Please read this excelent post by @ned14 for more details. The current recommendation is "GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk" from (IDan). You need GAPPS, microG (post) or the Google Service Framework(post).

    In comparison to OpenCamera it sacrifices manual controls + extra lenses for:
    • simpler user interface
    • better single-shot HDR
    • better panoramas + photospheres
    • SlowMo video (1080p @120/240fps)
    I've also written a more detailed comparison. You can have both camera apps installed at the same time, so you can always choose the better one depending on the scenario.


    Getting Help:

    General:
    Before you post, please check this FAQ, use the search function and skim the few last pages of this thread. We want LinageOS to work on your device, that's the whole point of this thread, but this way you can get the fastest help. If you did not find an answer, feel free to ask here :) We do this in out free time and it may take us some time to answer, so please be patient.

    How to report a bug?
    To fix any bug we first have to be able to reproduce it. Please include all relevant information:
    • device (S10e/S10/S10+)
    • ROM version
    • is gapps/ microg/ magisk installed?
    • steps to reproduce the issue

    When in doubt it's better to include to 0much information than too little. A good example is @Sheffield Steve's bug report. Check out Simon's "How to Report Bugs Effectively" to write even better reports (and thus get better help).

    How to create a logfile?
    To get an even better insight into your issue, a logfile can help us a lot. On Android this is called "logcat". Short logcats are best. They contain less fluff which makes finding the issue easier. Here are the steps how to create a log with adb:

    • install adb drivers
    • open cmd and navigate to the adb file eg. cd C:\Users\<user>\Desktop\platform-tools
    • Connect your phone via USB
    • Select "Allow USB Debugging" on the popup on the phone (see below how to activate it)
    • Clear the log using: adb logcat -c
    • Start loggingwith: adb logcat | tee beyond.log
    • Reproduce the issue
    • Stop logging by pressing CTRL+c
    • Send us the log (in a PM)

    How do I enable USB Debugging?
    To enable USB Debugging you need to do the following steps:

    • Go to Settings -> About Phone
    • Look for Build number
    • Tap on Build Number several times till you get the message that Developer Options have been enabled
    • Go to Settings -> System -> Advanced -> Developer Options
    • Enable USB Debugging


    About this FAQ:
    This FAQ is originally written by modpunk and partly maintained by me (ctrej) to reduce modpunk's workload. We try to keep the FAQ as up-to-date as possible, but it may lag a few days behind. Please read the last posts in this thread for latest information.

    Changelog:
    20200813 (v1.0)
    • update: this changelog, now with ROM version at time of posting and a hide section for older changelogs
    • update: firmware update section (thanks @Stef4n82!)
    • update: ROM update section
    • update: getting help section, rewritten for clarity
    • update: proximity sensor, slow sample rate (thanks @Lav64)
    • update: audio section with my test and @El Dun's report
    • add: gpay/safetynet explanation
    • change: link formating to stay under the 30k character limit

    20200809 (RC2)
    • update: audio output with limited frequency range, limited DAC support (thanks @El Dun)
    • update: double tap to wake works well, used it for a few weeks now without issues
    • update: "86400 seconds" section (thanks @Exilion90)
    • add: links to each version of this FAQ, just click one of the datecodes
    • add: ACCA to feature list
    • add: ADO works kinda
    • add: dual sim to feature list (thanks @Exilion90)
    20200802 (RC2)
    • update: microG section (thanks @ichmyselfandi)
    • update: unlock instructions, setup with wifi required (thanks @Lunat1c)
    • update: "86400 seconds" section (thanks @Lunat1c & @Stef4n82)
    • add: gapps/ microg/ google framework requirement for the GCAM (thanks @KanyT & @ned14)
    • add: bug google backup pattern with 4x4 or 5x5 pattern (thanks @Ivo_Todorov)
    • fix: twrp "more details" link (thanks @Lunat1c)
    20200719 (RC2)
    • update: rgb light sensor, all channels working
    • update: software sensors don't output values on stock either (thanks @Brembo109)
    • add: gcam information (thanks @ned14)
    • add: grip sensor
    • add: microg appendum (thanks @ned14)
    • add: workaround for black status bar in fullscreen
    • add: bug no glove mode (thanks @raggatip)
    • add: bug bixby button hold shortcut (thanks @Lav64)
    20200713
    • update: feature/ bug list (previously called working/ not working) with fixed from RC2
    • update: instructions for microG (thanks @ned14)
    • update: magisk install instructions
    • update: wireless power share works fine, the phone just didn't like the synthetic load I used for testing
    • add: black bar on camera cutout in fullscreen apps (thanks @Sradgads)
    20200707 (RC1)
    • update: section "get help" with copy & paste template
    • update: font for cmd to Courier New
    • confirm: removing pin/password/pattern solves the 86400 second wait delay (thanks @fishnetfancy)
    • add: working/not working section
    • add: this changelog
    • add: telephoto lens not working (thanks @Ned)
    • add: several RC1 issues (thanks @angela5246)
    • add: vbmeta_disabled note to firmware instructions (thanks @okloloi)
    • add: reminder to update Magisk alongside lineage (thanks @fishnetfancy)
    20200705 (Beta3)
    • first FAQ update by me (ctrej)
    • change: order to the "natural" installation flow
    • change: install section into a more detailed checklist (thanks @AndrOdin)
    • add: sub-sections (install/ 3rd party/ support)
    20
    JFYI: I'm working on LineageOS 18.1 however I didn't have had time to work on it the last two weeks. Next week will be better.
    16
    What is difference between this and Ivan's lineage os?

    The most obvious one is that we provide SELinux enforcing and care about security and privacy. For the rest I can't give you an answer as Ivan doesn't want to release the source of his device tree. It would be great if Ivan would join our effort and contribute.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone