• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)

Search This thread
Magisk: Yes. Many rely on AFWall+ to block certain apps or use AdAway as an Adblocker. uBlockOrigin is no valid replacement as it only blocks ads in the browser, but not in apps.

microG: I personally do not use miroG or other google services. Also it is easily installed after flashing LOS for those who want it.
If anyone wants a great adblocker for Android, try Blokada. It acts as a VPN for the device's whole internet connection and blocks all ad and tracker domains. You can customize what is blocked so that certain social media sites still work, or don't! It's a great app and there are very few downsides to using it.
 

Keule-Tm

Senior Member
Oct 3, 2016
381
146
Berlin
Samsung Galaxy S10
If anyone wants a great adblocker for Android, try Blokada. It acts as a VPN for the device's whole internet connection and blocks all ad and tracker domains. You can customize what is blocked so that certain social media sites still work, or don't! It's a great app and there are very few downsides to using it.
One difference to using AdAway et al is that Blockada requires a process to run, while hosts list based blocker don't need to run in the background.
 

realityexists

Member
Jul 7, 2017
17
0
I updated my S10e to v1.4 and firmware XXS9DTK9 and now my front camera is no longer working.

The rear camera works. When I switch to the front camera the preview image is simply all black, as if the camera was taped over. When I press the same icon to switch back to the rear camera the app freezes for a few seconds, then exits, but when I restart the Camera app it has switched back to the rear camera (which works). I can't be 100% sure that this started when I updated to v1.4, but I haven't tried the front camera since then and can't think of what else could have caused this. I was previously using v1.0 and the front camera worked.

I tried rebooting and power off, of course. Tried clearing the Camera app cache and storage, wiping the cache partition - no change. Has anyone else run into this? Any ideas how to fix it?

In addition to this problem backing up with TWRP fails with

Can not create '/data/media/0/TWRP' folder (Required
key not available).
Failed to make backup folder


I believe this is because /data/media/0 is encrypted - if I browse it in TWRP File Manager the directory names look like gibberish. I removed the PIN prior to rebooting into TWRP (set Screen Lock to "None") and TWRP does not prompt me for a password when it boots, but the data is still encrypted. With v1.0 of this ROM removing the PIN was enough to do a backup - I did this many times. How do I fix this now, with v1.4?

Would appreciate any help with the front camera, too, or at least reports of whether it works for others.
 

doeternietoe

Senior Member
Dec 31, 2010
70
27
In addition to this problem backing up with TWRP fails with



I believe this is because /data/media/0 is encrypted - if I browse it in TWRP File Manager the directory names look like gibberish. I removed the PIN prior to rebooting into TWRP (set Screen Lock to "None") and TWRP does not prompt me for a password when it boots, but the data is still encrypted. With v1.0 of this ROM removing the PIN was enough to do a backup - I did this many times. How do I fix this now, with v1.4?

Would appreciate any help with the front camera, too, or at least reports of whether it works for others.
Your problem with twrp not being able to decrypt data and not even asking for a password sounds a lot like a problem I posted about in this thread and the twrp thread earlier. I don't have any solution, but your problem doesn't seem to be an isolated one.

As for the front camera, I have updated my phone from beta2 all the way to 1.4 and I think my front camera is still working, at least in opencamera. In gcam it doesn't show a preview, but I don't think gcam worked for my front cam any previous install.

So have you tried any other camera apps? If there is a freeze or crash you might also want to try logcat to find the problem.
 

realityexists

Member
Jul 7, 2017
17
0
So have you tried any other camera apps? If there is a freeze or crash you might also want to try logcat to find the problem.



I tried Open Camera and Simple Camera and they both fail as well - the preview image freezes, though the app doesn't crash and I can still go into settings or press the shutter button. When I do (on the front camera), Simple Camera shows this:



Code:
An error occurred: Capture picture android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): flush:1529: Camera 1: Error flushing device: Broken pipe (-32)



logcat has a lot of stuff, but this looks relevant (also pressing the shutter in Simple Camera)



Code:
--------- beginning of crash
01-24 10:38:35.968  5281  5789 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 5789 (HwBinder:5281_2), pid 5281 ([email protected])
01-24 10:38:36.013  3135  3135 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-24 10:38:36.013  3135  3135 F DEBUG   : LineageOS Version: '17.1-20201217-UNOFFICIAL-beyond0lte'
01-24 10:38:36.013  3135  3135 F DEBUG   : Build fingerprint: 'samsung/beyond0ltexx/beyond0:10/QP1A.190711.020/G970FXXS9DTK9:user/release-keys'
01-24 10:38:36.013  3135  3135 F DEBUG   : Revision: '26'
01-24 10:38:36.013  3135  3135 F DEBUG   : ABI: 'arm'
01-24 10:38:36.013  3135  3135 F DEBUG   : Timestamp: 2021-01-24 10:38:36+0100
01-24 10:38:36.013  3135  3135 F DEBUG   : pid: 5281, tid: 5789, name: HwBinder:5281_2  >>> /vendor/bin/hw/[email protected] <<<
01-24 10:38:36.013  3135  3135 F DEBUG   : uid: 1047
01-24 10:38:36.013  3135  3135 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-24 10:38:36.013  3135  3135 F DEBUG   : Abort message: 'ASSERT(m_transitState):Failed to wait Other state. curState 3 newState 5'
01-24 10:38:36.013  3135  3135 F DEBUG   :     r0  00000000  r1  0000169d  r2  00000006  r3  e815e7d8
01-24 10:38:36.013  3135  3135 F DEBUG   :     r4  e815e7ec  r5  e815e7d0  r6  000014a1  r7  0000016b
01-24 10:38:36.013  3135  3135 F DEBUG   :     r8  e815e7e8  r9  e815e7d8  r10 e815e808  r11 e815e7f8
01-24 10:38:36.013  3135  3135 F DEBUG   :     ip  0000169d  sp  e815e7a8  lr  ebffb2b3  pc  ebffb2c6
01-24 10:38:36.041  3135  3135 F DEBUG   : 
01-24 10:38:36.041  3135  3135 F DEBUG   : backtrace:
01-24 10:38:36.041  3135  3135 F DEBUG   :       #00 pc 0005f2c6  /apex/com.android.runtime/lib/bionic/libc.so (abort+166) (BuildId: 51611c36f0526c4396f6466a688e4d47)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #01 pc 00005a31  /system/lib/liblog.so (__android_log_assert+176) (BuildId: 5308d97a8ae4abb015fa115d4dabe0b0)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #02 pc 0011c355  /vendor/lib/libexynoscamera3.so (android::ExynosCamera::m_transitState(android::ExynosCamera::exynos_camera_state)+580) (BuildId: 0a0fde6ed3757d8090ecd611350a59ee)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #03 pc 001413cb  /vendor/lib/libexynoscamera3.so (android::ExynosCamera::flush()+166) (BuildId: 0a0fde6ed3757d8090ecd611350a59ee)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #04 pc 000060e7  /vendor/lib/hw/camera.exynos9820.so (android::HAL3_camera_device_flush(camera3_device const*)+114) (BuildId: 6b96a6b7ed23bc48cf4aa45dfee0fdad)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #05 pc 0001b773  /vendor/lib/[email protected] (android::hardware::camera::device::V3_2::implementation::CameraDeviceSession::flush()+78) (BuildId: 7726f9918ef1b3a85d367c83b2ff73a0)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #06 pc 00016215  /vendor/lib/[email protected] (android::hardware::camera::device::V3_2::implementation::CameraDeviceSession::TrampolineSessionInterface_3_2::flush()+4) (BuildId: d19539e05fd6333419eeccf94be526a4)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #07 pc 00020237  /system/lib/vndk-29/[email protected] (android::hardware::camera::device::V3_2::BnHwCameraDeviceSession::_hidl_flush(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+122) (BuildId: fa0cc723f7d35a648b719d0b6da936e5)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #08 pc 0002548d  /system/lib/vndk-29/[email protected] (android::hardware::camera::device::V3_5::BnHwCameraDeviceSession::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+756) (BuildId: 7139378faa53fabcd667413f21169313)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #09 pc 00068bb7  /system/lib/vndk-sp-29/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+46) (BuildId: ff0694fcafdef328d0f325d2956f8786)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #10 pc 0006b0ed  /system/lib/vndk-sp-29/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+924) (BuildId: ff0694fcafdef328d0f325d2956f8786)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #11 pc 0006c277  /system/lib/vndk-sp-29/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+110) (BuildId: ff0694fcafdef328d0f325d2956f8786)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #12 pc 00076c91  /system/lib/vndk-sp-29/libhidlbase.so (android::hardware::PoolThread::threadLoop()+12) (BuildId: ff0694fcafdef328d0f325d2956f8786)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #13 pc 0000d8ab  /system/lib/vndk-sp-29/libutils.so (android::Thread::_threadLoop(void*)+182) (BuildId: 5f310efbe91d136f5f340d12a4382a92)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #14 pc 000a6bd3  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+20) (BuildId: 51611c36f0526c4396f6466a688e4d47)
01-24 10:38:36.041  3135  3135 F DEBUG   :       #15 pc 00060773  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: 51611c36f0526c4396f6466a688e4d47)
01-24 10:38:36.346  5632  5863 W NativeCrashListener: Couldn't find ProcessRecord for pid 5281



When I use the default LOS camera app and press the shutter I get this in logcat instead:



Code:
...
01-24 10:59:42.238  5623  5718 W System.err: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.iso_exp_priority.select_priority')
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.CameraMetadataNative.getBase(CameraMetadataNative.java:523)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.CameraMetadataNative.get(CameraMetadataNative.java:413)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.CameraMetadataNative.get(CameraMetadataNative.java:396)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.CaptureRequest$Builder.get(CaptureRequest.java:862)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.util.VendorTagUtil.isSupported(VendorTagUtil.java:78)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.util.VendorTagUtil.isIsoExpPrioritySelectPrioritySupported(VendorTagUtil.java:140)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.util.VendorTagUtil.setIsoExpPrioritySelectPriority(VendorTagUtil.java:135)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.CaptureModule.applyIso(CaptureModule.java:6327)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.CaptureModule.applyCommonSettings(CaptureModule.java:3270)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.CaptureModule.initializePreviewConfiguration(CaptureModule.java:5870)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.CaptureModule.access$3200(CaptureModule.java:163)
01-24 10:59:42.239  5623  5718 W System.err:     at com.android.camera.CaptureModule$8.onConfigured(CaptureModule.java:1547)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.CallbackProxies$SessionStateCallbackProxy.lambda$onConfigured$0$CallbackProxies$SessionStateCallbackProxy(CallbackProxies.java:53)
01-24 10:59:42.239  5623  5718 W System.err:     at android.hardware.camera2.impl.-$$Lambda$CallbackProxies$SessionStateCallbackProxy$soW0qC12Osypoky6AfL3P2-TeDw.run(Unknown Source:4)
01-24 10:59:42.239  5623  5718 W System.err:     at android.os.Handler.handleCallback(Handler.java:883)
01-24 10:59:42.239  5623  5718 W System.err:     at android.os.Handler.dispatchMessage(Handler.java:100)
01-24 10:59:42.239  5623  5718 W System.err:     at android.os.Looper.loop(Looper.java:214)
01-24 10:59:42.239  5623  5828 I CCodecConfig: query failed after returning 7 values (BAD_INDEX)
01-24 10:59:42.239  5623  5718 W System.err:     at android.os.HandlerThread.run(HandlerThread.java:67)
01-24 10:59:42.239  5623  5828 D CCodecConfig: c2 config diff is Dict {
01-24 10:59:42.239  5623  5828 D CCodecConfig:   c2::u32 coded.bitrate.value = 64000
01-24 10:59:42.239  5623  5828 D CCodecConfig:   c2::u32 input.buffers.max-size.value = 32768
01-24 10:59:42.239  5623  5828 D CCodecConfig:   c2::u32 input.delay.value = 0
01-24 10:59:42.239  5623  5828 D CCodecConfig:   string input.media-type.value = "audio/vorbis"
01-24 10:59:42.239  5623  5828 D CCodecConfig:   string output.media-type.value = "audio/raw"
01-24 10:59:42.239  5623  5828 D CCodecConfig:   c2::u32 raw.channel-count.value = 1
01-24 10:59:42.239  5623  5828 D CCodecConfig:   c2::u32 raw.sample-rate.value = 48000
01-24 10:59:42.239  5623  5828 D CCodecConfig: }
01-24 10:59:42.239  5623  5718 D VendorTagUtil: vendor tag org.codeaurora.qcamera3.iso_exp_priority.use_iso_exp_priority is not supported
...
 

realityexists

Member
Jul 7, 2017
17
0
Your problem with twrp not being able to decrypt data and not even asking for a password sounds a lot like a problem I posted about in this thread and the twrp thread earlier. I don't have any solution, but your problem doesn't seem to be an isolated one.

OK, good to know that at least, thanks. Looking through your post history, I see
that Sheffield Steve wrote on 26-Dec: "Normally, your problem [being unable to decrypt the data partition] is caused by not doing a Wipe (full format) after installing TWRP/LineageOS."

Indeed, I did not do a full wipe when upgrading from v1.0 to v1.4. Was I supposed to? The instructions in the original post say "Updating LinageOS is a lot less work and you can keep all user data... Wipe dalvik and cache".
 

doeternietoe

Senior Member
Dec 31, 2010
70
27
OK, good to know that at least, thanks. Looking through your post history, I see
that Sheffield Steve wrote on 26-Dec: "Normally, your problem [being unable to decrypt the data partition] is caused by not doing a Wipe (full format) after installing TWRP/LineageOS."

Indeed, I did not do a full wipe when upgrading from v1.0 to v1.4. Was I supposed to? The instructions in the original post say "Updating LinageOS is a lot less work and you can keep all user data... Wipe dalvik and cache".
Back when I installed BETA2 of this ROM I did a full wipe, but since then I've always just flashed the new ROMS, without doing a full wipe. This is how the ROMS are meant to be used and until very recently every single update worked as expected. It's only now that I find TWRP data decryption is broken, but apart from that everything's fine.

There might be a small chance that something goes wrong when we skip a (few) version(s). For instance I opted out of the update with the broken bluetooth audio. You skipped quite a bit more than that. I can see no good reason why this would be a problem, but it is the only thing I can think of right now. Maybe modpunk can shed some light on this...
 

elmØ

New member
Jan 30, 2021
1
0
Successfully flashed the S10e with 17.1 using Heimdall, I just want to give a big thank you to all the devs and supporting community for your awesome work. It works fine as hell and battery life is soon much better 🤩.
 

Midyr

Senior Member
Nov 19, 2011
88
6
Mainz
Hello,

I try to use Android Auto for the first time.
My car don't recognized my phone nor the phone as usb drive.

I'm on 20201113


I tried also an other phone, which is working.

Any hint to use AA?

Thanks

Midyr
 

El3ndil

Member
Jan 17, 2021
14
1
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.
Should I install 17.1 while waiting 18.1, or it is a matter of days?

If I install 17.1, will a format of the data partition be needed in order to update to 18.1?

Edit: I am coming from then Ivan lineage 18.1. I am willing to move to this ROM, but I don't understand at all the firmware part. What should I do? Updating the firmware before installing the suggested twrp?
Edit2: I Checked the baseband version and it is the same as the one suggested... So I guess I am fine just reinstalling your suggested twrp and then flashing...
 
Last edited:

DerSteppo

Senior Member
Aug 10, 2017
202
52
Frankfurt
ASUS ZenFone 8
Hey modpunk, I just wanted to know if you would like to give us a little update on your upstream efforts. If I am reading correctly, all of them have been approved / merged, right? Is it likely to see official LOS status for our devices at some point?
 

El3ndil

Member
Jan 17, 2021
14
1
Installed some days ago and had almost no problem. I am using it with magisk but without gapps.. Great rom, very stable. I removed stuff I don't use with the magisk module debloater, such as the jelly browser, aurora store, mozilla backend etc. The only one that still appears in fdroid is unifiednlp (I removed it but it is still shown)

Only experiencing some issues with the brightness auto setting. It adjusts very quickly (and it is a good thing, because in other roms I tried it was almost unuseful), but sometimes stucks with a low brightness. But it might be a problem of one of the sensors of my phone, because I have always had problems e.g. with proximity sensor even with the stock rom
 

VoLTz4Dayz

Member
Oct 27, 2013
15
0
Hey XDA,
I'm currently running Ivan's LOS 17.1, but would like to switch to this instead - do I need to flash stock firmware before attempting to install? Or can I simply flash your TWRP and then install? XXS9DTK9 (I'm running XXU9DTJA) is apparently required, but I am only able to find this firmware with German CSC, yet I'm not from Germany... Unsure how to continue.
 

WalterCool

Senior Member
Jan 15, 2012
146
32
HTC 10
Sony Xperia XZ1
Hey XDA,
I'm currently running Ivan's LOS 17.1, but would like to switch to this instead - do I need to flash stock firmware before attempting to install? Or can I simply flash your TWRP and then install? XXS9DTK9 (I'm running XXU9DTJA) is apparently required, but I am only able to find this firmware with German CSC, yet I'm not from Germany... Unsure how to continue.

You should be able to use any ROM, as long it contains that version. Check on https://www.sammobile.com/ . I'm using a Switzerland ROM for example.
 

Midyr

Senior Member
Nov 19, 2011
88
6
Mainz
Hello,



I played a little bit with Opengapps (dowdgrade to an older stock version and back to newest pico and reinstall Lineageos.

After that, if I have set any kind of display protction in place, (password, pin, patterns) the device reboots after screen lock and type-in the password/patterns...


If I disable password or use swipe , every things ok.


What could the problem be?


Thanks

Midyr
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    - - - - - -
    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

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

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.14.236
    ROM Firmware Required: XXSBFUF3
    Based On: LineageOS
    26
    REQUIRED FIRMWARE: XXSBFUF3


    CHANGELOG


    2021-07-23 | 2.2
    • Update to Linux 4.14.239

    2021-06-23 | 2.1
    • Update to Linux 4.14.236
    • Fixed GPS
    • Improved autobrightness (Thanks to linux4)

    2021-06-07 | 2.0
    • Added support to disable fast charging
    • Kernel fix to disable the touchscreen during handheld phone calls
    • Improved auto-brightness
    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.
    17
    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.