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

[ROM][OFFICIAL] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

kevin#34

Member
Sep 23, 2017
32
5
Rome
Hi, I am going to install lineage 18.1 (beyond1lte) on a brand-new S10 SM-G973F, is that feasible, or do I need to wait 7 days to unlock the phone? (I experienced this on my previous S9..)
also, before flashing the phone, do you suggest to update the system to the latest available update from Samsung?
thanks

just installed 18.1 following the instructions provided by Lineage website, everything went fine and the phone seems to run perfectly… now I just need to do a proper set-up (fingerprints, apps ecc)
 

LaDrOIdBoy

Senior Member
Jan 23, 2011
87
19
Loving LOS so much but does anyone else have issues with the camera not focusing? Really weird problem, it worked fine when the phone was stock so I don't think it's a hardware issue

I know GCam isn't supported but I did try chucking that on there which got focusing working for about a day, but it's stopped again

Tried reboots obviously and clearing the data from the built-in camera app, any suggestions?
 
  • Like
Reactions: zpunout

netmaniack

Senior Member
Oct 30, 2011
409
145
Liepāja
Loving LOS so much but does anyone else have issues with the camera not focusing? Really weird problem, it worked fine when the phone was stock so I don't think it's a hardware issue

I know GCam isn't supported but I did try chucking that on there which got focusing working for about a day, but it's stopped again

Tried reboots obviously and clearing the data from the built-in camera app, any suggestions?
I have only issues whit telephoto lense in opencamera at close distance.
 

helgi1507

New member
Sep 7, 2021
2
0
Loving LOS so much but does anyone else have issues with the camera not focusing? Really weird problem, it worked fine when the phone was stock so I don't think it's a hardware issue

I know GCam isn't supported but I did try chucking that on there which got focusing working for about a day, but it's stopped again

Tried reboots obviously and clearing the data from the built-in camera app, any suggestions?
I can confirm this issue.
You can try to enable HDR in stock camera app, in my opinion it could be better results.

Another suggestion is to try open camera app.
 

kevin#34

Member
Sep 23, 2017
32
5
Rome
just installed 18.1 following the instructions provided by Lineage website, everything went fine and the phone seems to run perfectly… now I just need to do a proper set-up (fingerprints, apps ecc)
after a full day of use, no big remarks, but compared with my previous Galaxy S9 (with Lineage obviously) I noticed:

- no 4G option available, just LTE (LTE technically speaking not equal to 4G)
- overall volume level (calls, video, notification etc) seems a bit lower than S9 one
- no function can be assigned to the Bixby button
- text size miss the "very big" option (useful for presbyopic like me🤭), "big" is the maximum setting
 
Last edited:

Linux4

Senior Member
after a full day of use, no big remarks, but compared with my previous Galaxy S9 (with Lineage obviously) I noticed:

- no 4G option available, just LTE (LTE technically speaking not equal to 4G)
- overall volume level (calls, video, notification etc) seems a bit lower than
- no function can be assigned to the Bixby button
- text size miss the "very big" option (useful for presbyopic like me🤭), "big" is the maximum setting

- Android makes no difference between LTE and 4G in the UI - it can either always show LTE for both 4G and LTE or 4G for both... First one has been done here.
- This is also the case on your S9 and most other samsungs.
- It's called Menu button in settings.
- It is there.
 

kevin#34

Member
Sep 23, 2017
32
5
Rome
- ok, I was confused because Lineage on my S9 was showing 4G and not LTE, thought it should have been the same on S10 too
- with volume set to max, it seems not as loud as my previous S9 (especially audio of calls and music/video) , but maybe it's just an impression
- if I assign a function to the home button (for example, split screen with a short press), it doesn't work :unsure:
- even set to biggest size, the text look smaller than what is on S9 :unsure:
 
Last edited:
  • Like
Reactions: datapanik

heni63

Senior Member
Dec 26, 2017
79
21
After using this ROM for a while I have noticed two major issues:

1. In ear speaker is at least 3-4db too low, it is hard to hear other person while calling.

2. Proximity sensor is not working correctly. When I pick up call most of times my screen stays on. As this phone have 8cm range sensor it should work fine.

Otherwise port is great, thx for spent time on it. Touchscreen feels too responsive and not that precise if we compare OneUI whit LOS, but its not that bad and expected.
Hey, didn't notice that screen precision, but now that I think about it makes sense and I noticed it without realizing it really lol. Or maybe it's my brain (and my display in general is bad, The response time sometimes is really high, but also in One UI, I think it defective.)

Maybe you can try "Touch screen repair" There is one in blue and one in white, I think thethe white one is the better, maybe it helps you.
 

vomad

Senior Member
Jun 8, 2017
119
45
Volgograd
How to remap Bixby button? I used (as usual) mt manager to edit /vendor/usr/keylayout/gpio.keys - key 703 from MENU to POWER. And.... nothing happens :) What's wrong with it??
 

kevin#34

Member
Sep 23, 2017
32
5
Rome
I tried me too, no way.. the only function I can assign to the Biby button is the one to "wake-up" the screen, all the remaining functions listed in the menu (by short/long pressing the Bixby button) are not working🤷‍♂️
 

zpunout

Senior Member
Aug 26, 2015
58
12
Samsung Galaxy S5
Moto G5 Plus
Anyone else having issues with 4G/LTE connectivity and not recognizing external sdcard? Doesn't seem to be any mention of it in this thread. I have tried resetting the network settings and tried going into recovery to format cache. Unless someone here has any other ideas, I'll be reinstalling stock OS and see if the issue persists. I haven't ruled out a hardware fault neither as the S10e I'm using was recently purchased in used condition. I should have tested it for a day or two before installing LineageOS. 😐
 

J4son82

Member
Jun 2, 2021
9
10
MUC
Anyone else having issues with 4G/LTE connectivity and not recognizing external sdcard? Doesn't seem to be any mention of it in this thread. I have tried resetting the network settings and tried going into recovery to format cache. Unless someone here has any other ideas, I'll be reinstalling stock OS and see if the issue persists. I haven't ruled out a hardware fault neither as the S10e I'm using was recently purchased in used condition. I should have tested it for a day or two before installing LineageOS. 😐

No problems with 4G/LTE here...and I have an external SD card for my music, so this works too
 
  • Like
Reactions: zpunout

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Any way around it? I like this rom but if updater is gonna get stuck because I'm using magisk I had to change back kraken rom 🥲 not that I prefer aoskp

    You could join the telegram group to find some early access build of some magisk fork that has addon.d working with FBE (topjohnwu is not even willing to merge an already existing fix as seen here: https://github.com/topjohnwu/Magisk/pull/3037)
    Other than that you could install magisk by just patching boot.img in the app instead of sideloading it in recovery (for now) which should make it not install addon.d.
    4
    I do the same with every OTA: let the system install it, seeing that it does not finish in 2-3 or so minutes, reboot (but not to recovery, just a simple reboot via holding power&vol- for >7s) - and there's the viola! A hack for sure, but it works.

    Being stuck is caused by magisk's broken addon.d just in case you wonder why it happens
    3
    First off, thank you for making this.
    Been using the microg fork for a couple of days, so I thought I'd share a list of things that I had/have issues with or that don't work.
    Most of these issues should also be present on this official ROM, as it's just the google services backend that's different.
    I'm also new to modern smartphone ROMs, so please don't bash me if I say something dumb.

    Using on an S10+ Exynos. SM-G975F
    Installation went just fine on Arch Linux.

    Lockscreen/locked related:
    Always on Display doesn't shift the clock every minute, so there's a chance of burn-in.
    Always on Display has a clump of maybe 5 pixels next to the front cameras that constantly blink green.
    Wave to wake up doesn't work.

    Microg related, had to install DroidGuard Helper from FDroid to get the fingerprint sensor working. Works well and much quicker than on the stock Samsung ROM.

    Random issues:
    Status bar doesn't change to a dark font with a light wallpaper. Works just fine in apps.
    Adaptive brightness seems to be having issues actually doing anything, very often.
    There are no built-in torch intensity settings.
    Most likely microg related, doesn't automatically pick up auth codes from SMS as there's no daemon for it.

    Frequently asked about features:
    Wireless hotspot working just fine.
    5GHz wifi working just fine.
    Bluetooth working just fine. No issues with wireless earbuds, paired instantly.
    LTE working as expected, signal is fine. Central EU. TMobile network.

    Camera:
    Stock camera app doesn't let you change lenses or video framerate to 60 fps.

    Using the GCam fork mentioned somewhere above "MGC_8.1.101_A9_GV1r_MGC"
    Wide angle lens working, normal lens working, no telephoto.
    Both front cameras working
    Takes some time to switch between any of these.
    You can force [email protected] video with stabilization and all the nice things in the settings.
    No 4K video for the front cameras, it caps at [email protected]

    Not tested:
    NFC/Contactless Payments.
    Dual sim
    SD card slot
    USB hotspot.
    Sensor that checks for liquid in the charging port.
    Samsung's pointless oxygen levels in blood / heartbeat sensor.
    "Pedometer".
    Gyro/etc. for VR.
    3
    ok, thanks, I guess no countermeasure can be adopted... (?)
    Try installing this as a system app, by making a folder /system/app/SamsungDAP and putting the APK inside
    2
    -z: enable compression with a specified algorithm (any, none, brotli)

    i.e. It compresses the data before sending it to reduce network backup time. Does not compress the final userdata image stored on the disk.

    There is no way to separate out the data because the partition is encrypted.

    The userdata.img will be big because it makes a complete clone of the userdata partition including internal storage.

    What I do to reduce backup size is to set the backup target folder flag (in Windows) to compress. This makes a massive difference to the file size and even the backup time. In my case the uncompressed userdata.img is 110GB, but the space used on the hard drive is 2.1 GB. Total backup time is around 12 mins.

    You can also use "dd" with "gzip" to make the backup and compress the data too.
  • 30
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions:
    Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
    Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.

    Downloads:

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:


    Support
    Telegram group

    Contributors
    Linux4
    Source Code: https://github.com/LineageOS
    Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
    5
    Any way around it? I like this rom but if updater is gonna get stuck because I'm using magisk I had to change back kraken rom 🥲 not that I prefer aoskp

    You could join the telegram group to find some early access build of some magisk fork that has addon.d working with FBE (topjohnwu is not even willing to merge an already existing fix as seen here: https://github.com/topjohnwu/Magisk/pull/3037)
    Other than that you could install magisk by just patching boot.img in the app instead of sideloading it in recovery (for now) which should make it not install addon.d.
    5
    First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
    Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem

    Hi Linux4,
    Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.
    TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadays
    Especially that it's heavily touching /data isn't good on devices with FBE, like on this ROM, TWRP randomly messes up FBE policy (especially on OTAs it seems) rendering the device unbootable without wiping (which is why OP says using TWRP = data loss) which is what I referred to with (soft)"brick"
    Not to talk about that crap not even properly formatting data on standard "factory reset" which makes it not boot on this ROM.
    Also applies to other devices using FBE encryption including Tab S6 Lite and S20 series.
    Older devices that use legacy FDE instead don't seem to have similar issues afaik.

    PS: TWRP looses most of it's "features" with encrypted userdata.
    5
    my safetynet fails, is there any way to make it pass? s10 exynos

    First you need to install magisk and then:


    1) Enable settings MagiskHide
    2) install MagiskHide Props Config(Magisk module)
    3) Open the terminal
    4) su
    5) Type "props"
    6) Edit 1 fingerprint of the device
    7) Choose a certified fingerprint
    8) 21 Oneplus
    9) Find an Android 11 device (OnePlus 8T global 44)
    10) Follow the instructions
    11) Restart
    12) Clear Google Play Store Data
    13) Check SafetyNet (should pass)
    14) Open MagiskHide (Magisk -> Tap on the Shield symbol)
    15) Check all apps that do not require root privileges
    4
    I do the same with every OTA: let the system install it, seeing that it does not finish in 2-3 or so minutes, reboot (but not to recovery, just a simple reboot via holding power&vol- for >7s) - and there's the viola! A hack for sure, but it works.

    Being stuck is caused by magisk's broken addon.d just in case you wonder why it happens