[ROM] LineageOS 17.1 for S10E/S10/S10+ Exynos

Search This thread

bym22028

Member
Jan 31, 2021
6
2
I try to disable A-GPS
I only found one gps file so far: /etc/gps_debug.conf
SUPL_HOST and SUPL_PORT is commented out there (by default). I saw on some websites that it uses default values if it is commented out (then it is not disabled).

On the other hand I tried "tcpdump -i any -s0 port 7275" and there were no packages (seems it is really disabled by default).

Could someone confirm?

Sorry if it is already mentioned. Did not find a possibility to search here...
 
Feb 11, 2021
11
1
Not Working
- VoLTE and VoWiFi

---


Hi!

Please,
someone can explain which functions VoLTE and VoWiFi impact?

For example, voice in calls by Skype, WhatsApp, Google Meet and Instagram will not work?

Thanks.
 

stasukas

Member
Feb 10, 2016
11
3
Please,
someone can explain which functions VoLTE and VoWiFi impact?

For example, voice in calls by Skype, WhatsApp, Google Meet and Instagram will not work?

VoLTE and VoWiFi are using by some mobile operators to carry ordinary voice calls through LTE and WiFi instead of ordinary GSM. VoLTE is extending quality of voice calls. VoWiFi could be used when you have very low GSM signal or you at roaming. Your mobile operator must support this technologies if you want to use it.
This technologies are not affect any voice and video conferencing through Internet connection e.g. Skype, WhatsApp, Google Meet, etc.
 
  • Like
Reactions: Pedro.Paschuetto
Feb 11, 2021
11
1
VoLTE and VoWiFi are using by some mobile operators to carry ordinary voice calls through LTE and WiFi instead of ordinary GSM. VoLTE is extending quality of voice calls. VoWiFi could be used when you have very low GSM signal or you at roaming. Your mobile operator must support this technologies if you want to use it.
This technologies are not affect any voice and video conferencing through Internet connection e.g. Skype, WhatsApp, Google Meet, etc.

Great!

Thank you, stasukas. 👊👊
 

ThaiSon96

New member
May 26, 2013
3
0
Hello Ivan,

I am currently running newest stock Android 11 on my S10+ exynos.
I rooted it with Magisk and then flashed TWRP after patching TWRP.img with Magisk.
Unfortunately I am not that experienced, but I am very unsatisfied with the performance on Android 11.
My question is: Can I flash Lineage OS 17.1 with magisk patched TWRP? Will Magisk still work and does it work under Android 11?

Thanks in advanced and big thumbs up for your Custom ROM.
 

Keule-Tm

Senior Member
Oct 3, 2016
389
151
Berlin
Samsung Galaxy S10
Hello Ivan,

I am currently running newest stock Android 11 on my S10+ exynos.
I rooted it with Magisk and then flashed TWRP after patching TWRP.img with Magisk.
Unfortunately I am not that experienced, but I am very unsatisfied with the performance on Android 11.
My question is: Can I flash Lineage OS 17.1 with magisk patched TWRP? Will Magisk still work and does it work under Android 11?

Thanks in advanced and big thumbs up for your Custom ROM.
You don't need to patch TWRP with this ROM. Just install the boot image (in the same folder). In TWRP you'd navigate to the place where you stored it, then tap on "Install image" (or something like that), select the image and profit.
 
  • Like
Reactions: JC-LGMS

ThaiSon96

New member
May 26, 2013
3
0
You don't need to patch TWRP with this ROM. Just install the boot image (in the same folder). In TWRP you'd navigate to the place where you stored it, then tap on "Install image" (or something like that), select the image and profit.

Hey Keule, thanks for your quick reply. I thought no one is active here anymore haha.
Well okay, I will flash the ROM.zip with TWRP normally.
But I will surely lose root access with Magisk right? If yes, how do I get root access under Lineage OS 17.1 again?
I assume you are from Germany, if you want you can send me a private message too! ;-)

Best regards
 
Sep 3, 2015
17
6
Samsung Galaxy S10
hi,
i noticed that the camera launch that i mapped as short press action on the search button (bixby button) starts by itself in standby.
in the last week it happed twice when the device was in standby on the desk.
im on build 17.1-20210112.
has anyone the same issue?
 

Keule-Tm

Senior Member
Oct 3, 2016
389
151
Berlin
Samsung Galaxy S10
Hey Keule, thanks for your quick reply. I thought no one is active here anymore haha.
Well okay, I will flash the ROM.zip with TWRP normally.
But I will surely lose root access with Magisk right? If yes, how do I get root access under Lineage OS 17.1 again?
I assume you are from Germany, if you want you can send me a private message too! ;-)

Best regards
If you flash the image (beyondXlte-boot-magisk.img, where X is one of 0, 1, 2, according to your device), you will of course get root access.
Yup, from Germany. But PMs will help noone but you, where answering questions here might help more people 😉
 

twilightpath

Member
Oct 27, 2014
18
1
Updating TWRP past twrp-3.5.0_9-2 is causing the phone to go into Download mode and giving a DL error. To fix, I have to flash twrp-3.5.0_9-2 in Odin. Anyone know what's going on? The error happens with both twrp-3.5.0_9-3 & 4.
 

xdagee

Senior Member
Sep 4, 2012
1,773
1,633
Accra
xdagee.github.io
Updating TWRP past twrp-3.5.0_9-2 is causing the phone to go into Download mode and giving a DL error. To fix, I have to flash twrp-3.5.0_9-2 in Odin. Anyone know what's going on? The error happens with both twrp-3.5.0_9-3 & 4.
This is happening because you're on Android 10 FW & you want to update to the latest twrp which is supported on Android 11 Only FW. So what do you do? Stick to twrp-3.5.0_9-0 which is support on Android 10 FW DTK9* DTL1* or update your FW to Android 11 EUA4* EUB1* FUBD* then you can use the latest version of twrp.
 

goodflood

Senior Member
Aug 25, 2012
206
34
Hello!

Currently on

ROM: 17.1 December patch level​
Baseband/Bootloader: DTJA​
Magisk: 21.1​
TWRP: 3.4.0_9-3​

Do I normally update to latest:

ROM: 17.1 Jan patch level with Feb 22 boot-image: https://mega.nz/folder/fXwFhIha#dpIJg2UA0lxPKZs9y8EdhQ/folder/6OpgmART

And,

Baseband/bootloader: Are Odin flashable files available somewhere?

Thanks!
 

xdagee

Senior Member
Sep 4, 2012
1,773
1,633
Accra
xdagee.github.io
Hello!

Currently on

ROM: 17.1 December patch level​
Baseband/Bootloader: DTJA​
Magisk: 21.1​
TWRP: 3.4.0_9-3​

Do I normally update to latest:

ROM: 17.1 Jan patch level with Feb 22 boot-image: https://mega.nz/folder/fXwFhIha#dpIJg2UA0lxPKZs9y8EdhQ/folder/6OpgmART

And,

Baseband/bootloader: Are Odin flashable files available somewhere?

Thanks!
 

starbright_

Senior Member
Apr 11, 2010
1,370
230
May I ask you about voice phone quality via GMS/Whatsapp ? I am atm in LOS18 my observations are:
* volume is very low ((only workaround is the speaker below - but that is not what I want)
* my counterparts (not me) report echos
Is this different in 17.1?

My previous phone was an A3(2017) - this struggle some with echos two but could be finally fixed. So I guess this is something that can be solved.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 109
    k5tUT1V.png

    LineageOS 17.1 for Galaxy S10 Series

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */


    Working:
    - Wifi
    - Sound
    - mali drivers
    - USB tethering
    - Video Playback
    - Fingerprint Sensor
    - Ril (Mobile data,calls, sms and stuff)
    - Sensors
    - Bluetooth
    - Wifi HotSpot
    - MTP
    - 2D and 3D gpu acceleration
    - HW encoding/decoding
    - GPS
    - Cameras (All of them)
    - HWcomposer (HWC)
    - Signal indicator
    - Double tap to wake
    - Wireless PowerShare

    Not Working
    - VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework


    To properly report a bug (Please dont report things already on the Not Working list)
    a) Logcat
    b) /proc/last_kmsg (or /proc/kmsg)
    c) /data/tombstones
    d) dmesg

    Please do not report bugs if you have performed any system modifications excluding gapps installation



    Installation instructions


    Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
    Download Q twrp from this thread
    flash twrp as per given instructions
    if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
    wipe cache, dalvik cache and system
    flash LineageOS
    If you want to have gapps flash them right after flashing the rom before first booting
    Reboot the device

    Downloads:
    Google drive
    Mega.nz
    (Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
    sha256 checksums

    Code:
    93ca94478bd8fa8e95fd513d8aae82b8e3aa0d21484e31ba2098c1e5e6693990  lineage-17.1-20210112-UNOFFICIAL-beyond2lte.zip
    afb505986373bbeb10ade91f67765d800f504a933c6b94d88c4013382ab32270  lineage-17.1-20210112-UNOFFICIAL-beyond1lte.zip
    06a334e091bdaac91f6c64559b5c9746559178facc7364b5676c39ddaa826a18  lineage-17.1-20210112-UNOFFICIAL-beyond0lte.zip
    
    4668a9cc55f6135403120370e668548a  beyond2lte-boot-magisk.img
    4954c5f2cbedbc2bbd90362745d93a1d  beyond1lte-boot-magisk.img
    84ec49e64560477e1df87417dbc4890e  beyond0lte-boot-magisk.img


    If you need general help or questions feel free to join Telegram group

    Gapps
    READ BEFORE INSTALLING MAGISK

    I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
    if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler





    Based On Android Q
    Changelog

    01.12.2021.
    - Merged january security update
    - Updated magisk boot image to magisk 21.2
    - Misc performance and security updates

    12.12.2020.
    -Merged december security update
    - Merged december vendor security update
    - Updated magisk images to 21.1
    - Synced with los source

    11.09.2020.
    - Updated vendor to XXU9DTJA
    - Switched to more calibrated sensor for Adaptive Brightness
    - Merged November 2020. Security update
    - Synced with LOS source

    10.08.2020.
    - Updated vendor to FXXS9DTI8
    - Fixed camera and bt issues present in previous build
    - Merged october 2020 security update
    - Synced with LOS source
    - Updates magisk images to latest canary build (turns out it was more stable than beta version)

    09.10.2020.
    - Merged OneUI 2.5 Kernel and vendor (DTH7)
    - Enabled 5GHz tethering
    - Updated Magisk images
    - Merged September 2020 Security update
    - Tuned little core optimizations
    - Enabled vibrator intensity control (under accesibility)
    - Misc performance and stability improvements
    - Synced with LOS source

    08.05.2020.
    - Imported G97*FXXU8CTG4 vendor changes
    - Merged August 2020 system and vendor security updates
    - Improved system security and stability
    - Synced with LOS source (Check out new extended volume panel)


    07.08.2020.
    - Imported G97*FXXS7CTF3 vendor changes
    - Merged July 2020 security update for both system and vendor
    - Misc performance and stability improvements

    06.11.2020.
    - Merged G97*FXXU7CTF1 kernel source
    - Imported G97*FXXU7CTF1 vendor changes
    - Removed proximity from always on display (again)
    - Updated magisk images to G97*FXXU7CTF1
    - Camera and wifi stability and performance improvements
    - HWC stability and performance improvements
    - Fixed issue where USB tethering under linux would cause kernel panic
    - Synced with LOS source

    06.03.2020.
    - Merged June 2020 System security patch
    - Merged June 2020 Vendor security patch (G97*FXXU3ASJD)
    - Improved completely back theme
    - Misc performance improvements
    - Synced with LOS source

    05.21.2020.
    - Fixed DT2W on AOD
    - Added completely black theme (You can access it thru styles settings entry)
    - Removed blinking proximity sensor from AOD
    - Added usb trust hal that can prevent usb devices from being used if plugged in while device is locked
    - Exposed mdnie screen tuning modes
    - Moved pin entry area above fingerprint on s10 and s10+ so they dont overlap with sensor
    - Cleaned up DT2W implementation
    - Added high touch sensitivity mode (Glove mode) (This can also help when using screen protectors)
    - Implemented mDNIe powered color calibration (Settings>Display>LiveDisplay)
    - Implemented color profiles so you can use natural colors if you wish to do so (Settings>Display>LiveDisplay)
    - Next update should add even more color modes powered by mDNIe like negative and greyscale
    - Updated magisk kernel images
    - Synced with LOS source

    05.15.2020
    - Fixed boot on latest CTD1 firmware
    - added ctd1 dtbo
    - exposed all camera instances to external apps
    - started working on HRM sensor
    - merged CTD1 kernel source
    - updated magisk images
    - misc performance and stability improvements

    05.05.2020.
    - Merged G97*FXXS5CTD1 blobs with may 2020 security update
    - Merged may 2020 system security update
    - Fixed usb tethering issues

    04.14.2020.
    - Fixed significant motion sensor detection
    - merged April system security update
    - Added vbmeta into the zip
    - Removed unused radio(ril) interfaces
    - Merged Note and s10 5g kernels into same tree for easier maintanance
    - Switched to source built dtbo
    - Updated magisk kernel images

    03.31.2020.
    - April vendor security update (System is still march as april tags havent been released on aosp yet)
    - Rebased kernel on top of G97*FXXU4CTC9
    - Added dt and dtbo images to rom
    - merged G97*FXXU4CTC9 vendor binaries
    - Removed simstat service as samsung fixed dual sim device detection
    - Updated boot images to Magisk 20.4
    - Misc performance and stability improvements

    03.03.2020.
    - Merged march system security update
    - Merged latest feature drop
    - Synced with los source
    - merged G97*FXXS4BTB3 vendor binaries

    02.27.2020.
    - Fixed camera cutout on S10
    - Enabled proximity sensor in all apps with proper permissions
    - Rewrote sensor impl
    - Removed unused parts of lights hal
    - Added vendor to the build (This is why rom is larger now)
    - Cleaned up lights overlays and power hal handling
    (This means vendor partition also gets built from source and can be more customized per aosp needs
    instead of relaying on bind mounting over existing drivers)

    02.19.2020.
    - Fixed BT calls on some devices that had issues with WBS
    - Fixed issue where on clean install or after factory reset there were no default notification sounds and ringtones set
    - Synced with LOS source

    02.11.2020
    - Merged 4BTA8 kernel source
    - Merged February security update
    - Fixed MTP/USB tethering while ADB is enabled
    - Synced with LOS source

    02.05.2020.
    - Rebased kernel on top of samsungs G975FXXU3BSKO source
    - Fixed kernel not properly reporting deep sleep state to userspace
    - Reimplemented sensor reporting to allow access to proximity sensor to more apps
    - Updated build fingerprint to Q one
    - Updated TARGET_BOARD_PLATFORM flag to reflect samsungs changes to same
    - Removed releasetools which was failing on new-ish twrp releases anyway
    - Removed P vndk libs
    - Fixed power hal race condition
    - Fixed manual network selection
    - Performance and stability improvements

    26.11.2019.
    - Added FOD icons for S10 and S10+
    (This will show up any time system or app needs to use fp sensor and will help users locate the sensor)
    - Fixed detection of dual sim devices
    - Misc performance and stability improvements

    20.11.2019.
    - Initial public release



    XDA:DevDB Information
    [ROM] LineageOS 17.1 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10

    Contributors
    Ivan_Meler
    Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-17.1

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Any stock Q firmware, Latest is recommended

    Version Information
    Status:
    Stable
    Current Stable Version: 1.7.5
    Stable Release Date: 2020-11-09

    Created 2019-11-20
    Last Updated 2020-11-09
    41
    Reserved

    Magisk boot images are provided within each device folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy

    Do note that you will have to reflash magisk boot image when updating rom
    37
    New build is up sorry for delays on this one but there was weird bug caused by samsungs power hal which took way longer than it should to be fixed, Magisk is independent of recovery as promised you can read more info about it in 3rd post on main page, There are a lot of other smaller improvements all around, Rest of the source for developers to compile other roms will be up soon (Just doing some final cleanup of proprietary bits and pieces)

    Also big thanks to anyone who supported this project by covering build server cost and stuff and I'm really sorry for delays with this build but things should be pretty straightforward from this point
    30
    Reserved

    Reserved
    28
    New update is almost ready for release from extensive testing i only noticed 1 small issue that needs to be fixed before release(that being sec power hal)

    And more great news is that you won't need any custom recovery for magisk root anymore as it will reside within boot images for those that want to use it, that also means there won't be need to reboot to recovery/hold key combo to boot rooted with magisk