• 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

kubis111

Member
Oct 2, 2016
32
4
hello guys! :) i have a question
voLTE and voWIFI is NOT working on s10e right?
is that a problem regards "quality of life"/ "daily use" in your opinion?
thanks a lot!
in my country there are 2G (everywhere), 3G (around big cities and gradually ending), 4G (almost everywhere) ... the call can be made via 2G or 3G. Unfortunately, for example, when driving around larger cities where there are still 3G networks, they start a call to 3G, but the call cannot automatically switch to 2G, so the call ends. This is sometimes annoying. Another thing is that there is no internet during the call, so you can't find anything on the web, navigate Is offline, etc. It's simply one of the few compromises, but the reward will be, for example, great battery life.
 

zpunout

Senior Member
Aug 26, 2015
59
12
Samsung Galaxy S5
Moto G5 Plus
hello guys! :) i have a question
voLTE and voWIFI is NOT working on s10e right?
is that a problem regards "quality of life"/ "daily use" in your opinion?
thanks a lot!
For me, it's an issue I don't notice because my budget carrier drops back to 3G mode for phone calls anyway. I think it might be an issue in years to come when 3G is phased out, but only assuming VoLTE support never eventuates for the S10e
 

PenneVa

New member
Sep 21, 2021
2
0
Over the past days we (a colleague and myself) have installed LOS v18.1 on a Samsung s10e. We made some interesting findings.

First, our main focus was to have a rooted system, to have the device encrypted, and that rooting was also available in working profile.

We found that rooting by using the latest Magisk did not work in working profile. Further it was revealed that the Bromite browser could not install SystemWebView.

So this needed some testing. First we tried that same Magisk but on LOS v17.4. That didn't work neither as hoped. We went back to LOS v18.1 but using the older Magisk (sorry don't know the version). This combination also failed. Finally we then installed LOS v17.4 with that older Magisk. And bingo!

Now that mobile has LOS v17.4 installed and it is rooted, the device is encrypted, and working profile has root also.
BTW I, I was told that under LOS we can not have system encryption and rooting together. This has now being proven to be not so accurate.

BTW, SystemWebView from Bromite also works. But it has to be mentioned that this app had to be installed through Magisk.

I hope this feedback can help others to shortcut.
 

Spyop3

Member
Jun 29, 2010
29
9
Samsung Galaxy S10e
Over the past days we (a colleague and myself) have installed LOS v18.1 on a Samsung s10e. We made some interesting findings.

First, our main focus was to have a rooted system, to have the device encrypted, and that rooting was also available in working profile.

We found that rooting by using the latest Magisk did not work in working profile. Further it was revealed that the Bromite browser could not install SystemWebView.

So this needed some testing. First we tried that same Magisk but on LOS v17.4. That didn't work neither as hoped. We went back to LOS v18.1 but using the older Magisk (sorry don't know the version). This combination also failed. Finally we then installed LOS v17.4 with that older Magisk. And bingo!

Now that mobile has LOS v17.4 installed and it is rooted, the device is encrypted, and working profile has root also.
BTW I, I was told that under LOS we can not have system encryption and rooting together. This has now being proven to be not so accurate.

BTW, SystemWebView from Bromite also works. But it has to be mentioned that this app had to be installed through Magisk.

I hope this feedback can help others to shortcut.
Did you check in Magisk settings "multi-user mode" is set to "user independant"

I'm also using shelter to copy application in the work profile. I needed to copy microG there for instance
 

kubis111

Member
Oct 2, 2016
32
4
hi, is there a way to set a stronger flashlight? I mean the camera flash that shines more. In One UI BX action app such was the possibility. And one more question. It is probably a feature(bug?) of A11, but if I set the split screen on the search button, it is displayed incorrectly. I can only turn on this display "complicated" via the application icon in multitask.

For edit search button i use KeyMapper.
 

fil3s

Senior Member
Aug 30, 2014
1,314
186
42
bendigo
www.mobiledevices.cc
Hi

I softbricked my beyond1 trying to use updater. It was my fault, I interupted the system update but it was taking approx 2 hours and still wouldn't finish, so I force rebooted and tried to go to download mode upon reboot I got the error

couldn't do normal boot invalid kernel length

I stopped and thought about what I should do for a minute, since I could not get into recovery or download mode.

I did a quick Google search of the error and fixed it by ignoring the error and kept holding bixby and volume down to get into download mode and luckily it worked

That is all. Just thought I'd report it here for reference sake.

Cheers
 

vomad

Senior Member
Jun 8, 2017
119
45
Volgograd
Hi

I softbricked my beyond1 trying to use updater. It was my fault, I interupted the system update but it was taking approx 2 hours and still wouldn't finish, so I force rebooted and tried to go to download mode upon reboot I got the error



I stopped and thought about what I should do for a minute, since I could not get into recovery or download mode.

I did a quick Google search of the error and fixed it by ignoring the error and kept holding bixby and volume down to get into download mode and luckily it worked

That is all. Just thought I'd report it here for reference sake.

Cheers
I think you should boot into lineage recovery and just sideload full ROM without Gapps and reboot normal... No need to reboot to Odin if you've crashed system.
 

Keule-Tm

Senior Member
Oct 3, 2016
377
145
Berlin
Samsung Galaxy S10
Hi

I softbricked my beyond1 trying to use updater. It was my fault, I interupted the system update but it was taking approx 2 hours and still wouldn't finish, so I force rebooted and tried to go to download mode upon reboot I got the error



I stopped and thought about what I should do for a minute, since I could not get into recovery or download mode.

I did a quick Google search of the error and fixed it by ignoring the error and kept holding bixby and volume down to get into download mode and luckily it worked

That is all. Just thought I'd report it here for reference sake.

Cheers
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.
 
  • Like
Reactions: evilorb and fil3s

Linux4

Senior Member
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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.
    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.
    2
    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.
    We already have camera libs which enables RAW... Linux is going to add them in his build soon.
    2
    I have used dd for years with Linux and never seen a corruption issue. In fact I've never heard of it before today. (bs=1000 is not much better than the default)

    With the restore: I haven't tried piping data to adb for a few years, but the last time I did, it didn't work. (A bug of some sort in adb)

    To test it I would make sure you get the latest version of adb, plus you will need a copy of gzip on your computer. The syntax will look like this:

    gzip -c -d boot.dd.gz | adb shell "dd of=/dev/block/sda14 bs=65536"

    p.s. Make sure you have the ability to restore the partition by other means before testing this.

    Alternatively you can do a three step process like this:

    adb push -z any boot.dd.gz /
    adb shell "gunzip -c boot.dd.gz | dd of=/dev/block/sda14 bs=65536"
    adb shell rm boot.dd.gz


    Yes I increased it albeit to 1000 with only a minute time saving on the larger partition. I read somewhere that there's an increased chance of introducing errors with larger block sizes, though it is tempting. Are my restore commands correct?
  • 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