[ROM] [S9/S9+] [UNOFFICIAL] [LineageOS 18.1] [Exynos] [Weekly]

Search This thread

Speedmatze

Senior Member
Apr 25, 2009
89
44
Just out of curiosity, before I dig into this further, have you tried using the MS Outlook app from the Aurora Store?
Yes, tried it and it is not great. More importantly though it is blocked as client from the Exchange server in question because of security issues. I could probably get around that by faking the client ID but that would not be worth the trouble for that app...
 

Neurotical

Senior Member
Feb 7, 2011
234
357
First of all: Congratulations to your new born! Best of all reasons to take a break and adjust to the new life.
Second: Still great to have you back.

Thank you for keeping our S9s alive with your continued ROM support.
I would just have one request:
I am using LOS with MicroG instead of Gapps and need MS Exchange connectivity to sync a calendar. Until LOS17.1 it was easy to get this to work with the standard Email app. Unfortunately that is no longer included in LOS18.
Would it be possible to include the old version into your ROM to get MS Exchange back (as described here )?
I tried checking out the link referenced: https://github.com/bananer/android_manifests/blob/master/apps_from_17.1.xml but it is no longer available. Is there another source for this manifest?
 

Neurotical

Senior Member
Feb 7, 2011
234
357
All trees are here https://github.com/ArrowOS-Devices
you can pick the commits to your tree or just use the same trees (common tree and kernel tree)

So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)
 
Last edited:
  • Like
Reactions: francoism90

CyderXDA

Senior Member
So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)
you can. and you don't need the android_hardware_samsung I think. Just use kernel, common trees, devices trees and vendor from arrow and build, then it should build and boot.
 
  • Like
Reactions: francoism90

king1990

Senior Member
Oct 13, 2012
506
873
So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)
https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)
https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?
https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)
hardware/samsung is not needed, we only uses livedisplay and touch hidl, I added livedisplay in this branch https://github.com/baddar90/android_device_samsung_universal9810-common/tree/aosp-livedisplay and will add touch hal later but to start up you can use the above repos until I make a clean los19 branch.
for vendor, use the one in arrowos devices will fix ok google.

The rom will compile and boot fine as tested before. Goodluck
 
  • Like
Reactions: francoism90

king1990

Senior Member
Oct 13, 2012
506
873

I tried building LOS 19, but I get a lot of SELinux errors everytime I compile it and it ends up in a bootloop when I want to use it.
the common tree does not look good at all , I don't think it will work like that. use my branch for livedisplay and all other repos from arrowos devices (don't use hardware/samsung).
 
  • Like
Reactions: francoism90

Speedmatze

Senior Member
Apr 25, 2009
89
44
I tried checking out the link referenced: https://github.com/bananer/android_manifests/blob/master/apps_from_17.1.xml but it is no longer available. Is there another source for this manifest?
Here are the contents of the xml file:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
   <!-- commented out in https://github.com/LineageOS/android/blob/lineage-18.1/snippets/lineage.xml -->
   <project path="packages/apps/Email" name="LineageOS/android_packages_apps_Email" revision="lineage-17.1" />
   <project path="packages/apps/Exchange" name="LineageOS/android_packages_apps_Exchange" revision="lineage-17.1" />
   <project path="packages/apps/UnifiedEmail" name="LineageOS/android_packages_apps_UnifiedEmail" revision="lineage-17.1" />
</manifest>
 

francoism90

Member
Dec 18, 2016
47
13
the common tree does not look good at all , I don't think it will work like that. use my branch for livedisplay and all other repos from arrowos devices (don't use hardware/samsung).
Thanks for your honest feedback. :)
I'll checkout livedisplay and others in hidl.

Just one question, should we also use vibrator and power? It seems to work fine using the ones seen in 9820.

Also about SELinux rules, I notice this is missing, why?

PS. I'm just trying to learn, just asking for feedback.
 
Last edited:

king1990

Senior Member
Oct 13, 2012
506
873
Thanks for your honest feedback. :)
I'll checkout livedisplay and others in hidl.

Just one question, should we also use vibrator and power? It seems to work fine using the ones seen in 9820.

Also about SELinux rules, I notice this is missing, why?

PS. I'm just trying to learn, just asking for feedback.
The vibrator and power hal are already precompiled and used in the tree. Selinux is not missing. Trees are enforcing, only encryption is the major bug.

First boot your build then you can modify the tree as you like using this tree as a base.

Also try to keep authorship , your commits in the kernel tree are without any authorship which is not encouragd in open source work.
 

francoism90

Member
Dec 18, 2016
47
13
The vibrator and power hal are already precompiled and used in the tree. Selinux is not missing. Trees are enforcing, only encryption is the major bug.

First boot your build then you can modify the tree as you like using this tree as a base.

Also try to keep authorship , your commits in the kernel tree are without any authorship which is not encouragd in open source work.
This is what I'm asking about SELinux (most of the things I'm comparing against 9820 sources):
Code:
BOARD_SEPOLICY_TEE_FLAVOR := mobicore
include device/lineage/sepolicy/exynos/sepolicy.mk
include device/samsung_slsi/sepolicy/sepolicy.mk
Also why is it pointing to private and not vendor? Aren't the policies 'vendor' related?

Thanks!
 

king1990

Senior Member
Oct 13, 2012
506
873
This is what I'm asking about SELinux (most of the things I'm comparing against 9820 sources):
Code:
BOARD_SEPOLICY_TEE_FLAVOR := mobicore
include device/lineage/sepolicy/exynos/sepolicy.mk
include device/samsung_slsi/sepolicy/sepolicy.mk
Also why is it pointing to private and not vendor? Aren't the policies 'vendor' related?

Thanks!
You don't need to modify anything if your aim to boot los19. Use arrow trees and you will be fine. However I can't help you with your trees specially when there are two devs working on completely new trees. I would suggest to use the available trees which are perfectly fine or wait till new trees are made public.
 

jer194

Senior Member
Feb 23, 2014
1,015
724
Thanks for maintaining this ROM!

For those who want to use microg instead of Google Apps,
would you mind to add Signature Spoofing Support from here:


lineageos4microg so far does not seem to provide ROMs for starlte
(probably because there is no official LOS 18.1).
 
Last edited:

Neurotical

Senior Member
Feb 7, 2011
234
357
Thanks for maintaining this ROM!

For those who want to use microg instead of Google Apps,
would you mind to add Signature Spoofing Support from here:


ineageos4microg so far does not seem to provide ROMs for starlte
(probably because there is no official LOS 18.1).

Code:
mkdir ~/spoofpatch && cd ~/spoofpatch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/android_frameworks_base-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/packages_apps_PermissionController-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/frameworks_base_config.xml


mkdir -p ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values && cp ~/spoofpatch/frameworks_base_config.xml ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values/config.xml
cd ~/android/lineage/frameworks/base && patch -p1 -i ~/spoofpatch/android_frameworks_base-R.patch
cd ~/android/lineage/packages/apps/PermissionController && patch -p1 -i ~/spoofpatch/packages_apps_PermissionController-R.patch

With this custom script I was able to successfully add in signature spoofing support (y)(y)(y)

Screenshot_20220120-225751_microG_Services_Core.png


I will be releasing a ROM update OTA in the next few hours :)
 
Last edited:

jer194

Senior Member
Feb 23, 2014
1,015
724
Cool, thanks a lot!

It also enables the 'google-less' exposure notification framework,
for the Corona Warn App eg.
 
Last edited:

Neurotical

Senior Member
Feb 7, 2011
234
357
Last edited:

HQwarp

Senior Member
Aug 16, 2011
77
9
Thank you @Neurotical for your effort on the building the ROM, for a moment I thought I needed to get back to the not so great Arrow OS. Congratulations on the newborn!

I see that there are attempts to use Arrow OS sources. Let me add two other features to the not working well list on Arrow OS and more reasons to use Lineage sources.

First, the build-in keyboard Arrow OS has doesn't support dictionaries and spell check for many languages that are supported build-in by LOS. Besides English, Spanish, and maybe another language, other languages have very basic or non at all support. It is important for people that love their privacy, especially now with your help with adding spoofing to the ROM.

Second, Arrow OS has a battery optimizer feature that has too many bugs, even if the feature is not enabled. In my setup, I needed to reformat my phone, because, of a bug that appears from time to time that prevents charging the battery. This is hugely inconvenient especially when this feature is disabled all the time and I never use it.
 

Speedmatze

Senior Member
Apr 25, 2009
89
44
FYI new update includes:
  • Signature spoofing support.
Available via OTA or OP.

Have a great evening :) :cool::giggle:
Just installed the new version. Exchange integration and signature spoofing are working nicely!
These additions of the last two build have just made (installation and update) life much easier for non-google users.

Thank you!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    FYI new update includes:
    • May 5 2022 AOSP Security Patch
    • Wireguard updates
    Now available via OTA or OP.

    Have a great day!

    :geek::coffee:(y)
    3
    FYI new update includes:
    • Kernel update 4.9.313 -> 4.9.315
    Now available via OTA or OP.

    Have a great day!

    👾😸🐒🌞
    2
    FYI new update includes:
    • Kernel update 4.9.311 -> 4.9.312
    Now available via OTA or OP.

    Have a great day!

    :geek::coffee:(y)
    2
    FYI new update includes:
    • Kernel update 4.9.312 -> 4.9.313
    Now available via OTA or OP.

    Have a great day!

    :coffee::geek::cool::p:D
    1
    Great ROM so far, very stable. Thank you for keeping this project going :)
    This update was the first time I got a error when downloading it from github and wanting to install it (zip file was corrupt). I hope redownloading does the trick.
    Is there a way to check for updates in the OTA updater and have older files available? For me it only shows the latest one.
    I hope re-downloading it fixes your issue. The only way to install older versions is through adb sideload the older ROM in recovery. Older versions can be found in the OP, or here. You can install it over your current one, no need for a format. You can keep all your data when downgrading.
  • 23
    2okPze5.png


    ROM DOWNLOADS:

    ROM INSTALL INSTRUCTIONS:
    • From OEM:
      • Lineage Recovery
      • Format /system + /data + /cache
      • Flash
      • Reboot
      • Root is not included. To root, install Magisk yourself.
    • From existing Unofficial weekly:
      • Use OTA, or
      • Sideload via ADB in recovery

    BASEBAND UPDATING:
    1. Install Samsung USB drivers
    2. Install Odin 3.14 (or later)
    3. Download updated baseband firmware from the XDA thread for your model phone.
    4. Unzip and re-pack "modem.bin" into a .tar file such as "modem.tar"
    5. Reboot phone into download mode
    6. Open Odin
    7. Load your modem.tar file into CP in Odin
    8. Start flash
    9. Reboot

    MICROG INSTALL INSTRUCTIONS:
    • In the F-Droid store add in the appropriate repo: https://microg.org/fdroid/repo per the official instructions.
    • Do the following, in this order:
      1. Install microG services core (F-Droid)
      2. Install microG services framework proxy (F-Droid)
      3. Install NLP backend, such as Mozilla location (F-Droid) or GSM Location (F-Droid)​
      4. Install Google Play Store (APK mirror) or FakeStore (F-Droid)​
      5. microG settings -> self check -> enable all features​
      6. microG settings -> location modules -> enable Mozilla Location Service​
      7. For background location permission go to your system settings and allow microG services core and your Mozilla NLP to access location all the time.
      8. For full notification support got to microG settings -> enable Google device registration, cloud messaging, and Google safety net.

    WORKING FEATURES:

    • GPS
    • NFC
    • Wi-Fi
    • Audio
    • HDMI
    • Camera
    • Ethernet
    • Bluetooth
    • MTP/ADB
    • Encryption
    • Glove Mode
    • Android Auto
    • OTA Updates
    • Call Recording
    • Mobile Network
    • SELinux Enforcing
    • Fingerprint Sensor
    • Signature Spoofing
    • Wireguard (via kernel)

    NOT WORKING FEATURES:

    • Iris Scanner
    • VoLTE

    CONTRIBUTORS:


    SOURCE CODE:

    REFERENCES:

    REQUIREMENTS:

    • Stock Samsung Oneui 2 - 2.5 (Android 10) Firmware. (Bootloader + Vendor)

    XDA DevDB Information

    • LineageOS 18.1, ROM for the Samsung Galaxy S9

    Version Information

    • Status: Stable
    • ROM Firmware Required: Oneui 2 - 2.5

    My work will always be free for everyone to use and I will never hide anything behind a paywall.


    * We are not responsible for anything that may happen to your phone by installing custom ROMs/kernels.
    * You do it at your own risk. You take responsibility upon yourself and are not to blame us or XDA.
    * Your warranty will likely be voided by installing custom ROMs.
    13
    Good day,

    I just want to take a moment to say thank you to everyone who has tried this ROM, given feedback, and even helped out along the way! It is with all of your help that I can keep the builds coming and I look forward to doing this for as long as I can for the S9 and the S9+ :) Our community deserves the best and that only happens when we all work together :)

    Have a great day, and thank you again to everyone in this community :)
    12
    Good day everyone!

    I have returned from a small vacation and time off caring for my newborn baby! He is healthy and well.
    I apologize for the brief hiatus, but I am back to continue providing updated kernels, security patches, and Lineage OS 18.1 for you all!

    What's new since the latest version:
    Kernel: 4.9.290 -> 4.9.297
    Security patch: November 5, 2021 -> December 5, 2021 (January 5, 2022 should be out soon)

    Now available via OTA or OP, as usual :)

    Have a great day!
    9
    Why don't You Maintain The ROM Officially ?.Love This ROM Very Much Hope it Gets Lineage OS 19
    I would love to maintain it officially. In fact I reached out to the Lineage team about doing just that in September last year.

    They responded back outlining how there are a lot of procedures to follow, including needing a team to manage the device tree and other repos. There were also some things that me not being a programmer just can't provide like being able to independently bug fix compile errors when changes are made by the LOS team that are incompatible with the S90/S9+. Right now I rely on the community to help with these fixes and I just copy them. It's worked so far because there are, humbly, more knowledgeable people maintaining device trees than I.

    That leaves me in a position where I am learning from the experts and this wonderful community in a collaborative effort to keep the LOS 18.1 going for the S9 and S9+ :)
    8
    A couple of questions as I am somewhat new:
    1. Why is this build unofficial resp. what is preventing this build to become official again (as starlte official was discontinued after LOS 17.1)?
    2. How trustworthy is an unofficial build compared to an official build?
    With regards to safety and trustworthiness:
    • Everything is open source so anyone can see what is going into the all the builds. This includes the kernel, Lineage OS, and Samsung device trees. These links are in the OP.
    • I don't make any changes of my own because I am not knowledgeable enough to do that, but I do copy kernel patches from the Linux Long-term Maintenance team run by Linus and Greg for the 4.9y branch; I can at least bug-test and roll them into the weekly ROM builds. Linus & Greg pretty much head up Linux entirely, so the patches they approve are as trustworthy as you can get :D
    • I also got the Wireguard kernel patch into this build, which is pretty awesome, but without the help of the contributors in the OP, I really wouldn't have been able to do it on my own.
    With regards to making it official:
    • I was using the official Lineage OS, but when the support for official status was dropped, I started learning how to build Lineage for unsupported devices. Then I came across Synt4x's repos, which gave me all the resources needed to build Lineage 18.1 for the S9 and S9+. I simply maintain kernel patches that come out weekly by the Linux Long-term Maintenance team (Linus & Greg et al.), work with the community here to maintain the device trees, and then compile the builds as often as needed.
    • After I got the hang of all this, I figured everyone who has an S9 or S9+ should be able to benefit form Lineage OS 18.1 support. These phones have great hardware and I think it a shame not to allow users the option to de-google it or take full control of it so soon after it has been released. Besides, the 4.9y kernel is going to be maintained until 2023. So I upgraded from a 3600 to a 5900x and 16gb RAM to 32gb RAM to speed up the builds (each build is only about 8 minutes now) and support the community!
    • I would like to see an official build, but I can't maintain it all by myself. I am not a programmer, and most of the code I look at is jibberish to me; I just trust the Linux team and Lineage OS team. So we need the community here to help me with build errors when the Lineage team makes changes to their OS; I'm not knowledgeable enough yet to tackle those problems on my own. But I am learning, and have successfully tackled two compile errors so far with the help of the community, and I've learned from them :D
    What you will get with this build, even though it is unofficial is:
    • Kernel updates straight from the Linux Long-term Maintenance team; this is very official and safe;
    • AOSP security patches straight from the Lineage group; this is very official and safe;
    • Lineage OS updates as they roll out; this is very official and safe;
    I literally can't do anything else because of my limited skillset.