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

Search This thread

carlosbellino

Member
May 19, 2012
6
0
Aarau
Okay, I tried making this brightness change to the props: https://github.com/Geoknyda/android...mmit/96f483d2998df8819903fb333620c927bf69cc95
Max is 255, so I reduced it to 250. Let me know if this solves your issue.

I uploaded the ROM here: https://github.com/Geoknyda/OTA/releases/edit/BETA
I assume you have an S9, but it you have an S9+, just let me know and I'll re-compile & re-upload for you.
My bad, forgot to mention that I have a S9+, thank you, ill be waiting for testing it
 

Neurotical

Senior Member
Feb 7, 2011
244
400
Okay, I tried making this brightness change to the props: https://github.com/Geoknyda/android...mmit/96f483d2998df8819903fb333620c927bf69cc95
Max is 255, so I reduced it to 250. Let me know if this solves your issue.

I uploaded the ROM here: https://github.com/Geoknyda/OTA/releases/edit/BETA
I assume you have an S9, but it you have an S9+, just let me know and I'll re-compile & re-upload for you.
OK the S9+ is up now. Let me know if this works for you.
 
  • Like
Reactions: carlosbellino

RoyaldArmer1331

New member
May 13, 2022
4
0
Hello, I'd like to report two glitches. It's a bit long so sorry about that.

The OS kills off the apps very often and I couldn't disable it. Every time I go and use the Mull browser, I can only load like 3 or 4 tabs before it starts reloading the earlier tabs. If I have too many processes open (like 3 or more that are apps like the browser, YouTube, etc. which are too little processes, honestly), then it starts killing my music app (Poweramp) despite it having battery optimization turned off. The OS only shows that about 2.7GB of 3.9GB RAM are being used, so I don't know what's going on. Is it a glitch or heavy battery optimization? It doesn't happen on my other phone (OnePlus 8T) that has official LineageOS loaded on it.

By the way, LineageOS recovery never self updated after I flashed it the first time, so I had to switch back to TWRP. This is another glitch, I believe.

Um, this is a feature request but is it possible that you can put the Night Light on the LineageOS ROM?

Also, do you plan to work on LineageOS 19 (Android 12) now that it has been released?
 

Neurotical

Senior Member
Feb 7, 2011
244
400
Hello, I'd like to report two glitches. It's a bit long so sorry about that.

The OS kills off the apps very often and I couldn't disable it. Every time I go and use the Mull browser, I can only load like 3 or 4 tabs before it starts reloading the earlier tabs. If I have too many processes open (like 3 or more that are apps like the browser, YouTube, etc. which are too little processes, honestly), then it starts killing my music app (Poweramp) despite it having battery optimization turned off. The OS only shows that about 2.7GB of 3.9GB RAM are being used, so I don't know what's going on. Is it a glitch or heavy battery optimization? It doesn't happen on my other phone (OnePlus 8T) that has official LineageOS loaded on it.

By the way, LineageOS recovery never self updated after I flashed it the first time, so I had to switch back to TWRP. This is another glitch, I believe.

Um, this is a feature request but is it possible that you can put the Night Light on the LineageOS ROM?

Also, do you plan to work on LineageOS 19 (Android 12) now that it has been released?
This is the first I am hearing of fast app clearing. The RAM usage sounds right. Perhaps there's a setting changed in the developer options, such as 'background process limit'? This could also be a cause of you using TWRP with a Lineage ROM. Lineage is programmed to work properly with its own Recovery.

The night mode feature can be found in the setting under LiveDisplay:
Settings -> Display -> LiveDisplay -> Display Mode

Screenshot_20220514-091807_LineageOS_Settings.png


The automatic mode will automatically set your color temperature to day/night mode based on sunrise/sunset in your time zone.

In the LiveDisplay settings, you can choose what color temp you want the Night mode to be:

Screenshot_20220514-091945_LineageOS_Settings.png


As for LOS 19, I will keep posting 18.1 so long as AOSP security updates are released by the Lineage team and kernel updates are released by the Linux Long Term Maintenance Team. For perspective, this ROM currently is running kernel 4.9.313, which is about 200 levels above most kernels running on S9/S9+ ROMs, usually 4.9.118. This is equivalent to about 10,000 patches of additional security, efficiency, and performance! I make sure to also update the kernel every two weeks as the Linux Long Term Maintenance Team releases new patches.
 
Last edited:
  • Like
Reactions: m0m0331

m0m0331

Member
Sep 5, 2019
6
0
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.
yes, it did. Sadly now OTA does not work. It just shows me the version from end of April. So yeah, I just go to github and dl from there. Not optimal but it works for me. The ROM is super stable and I'm very grateful for still beeing able to use LOS.
 

astrapotro

Member
Nov 22, 2017
7
2
Anyone has similar problems as me , when sharing usb connection in debian 11 / ubuntu 20.04 with this rom in s9?

Code:
May  5 14:32:51 ideapad kernel: [  155.998386] usb 1-3: new high-speed USB device number 7 using xhci_hcd
May  5 14:32:51 ideapad kernel: [  156.149202] usb 1-3: New USB device found, idVendor=04e8, idProduct=6863, bcdDevice= 4.00
May  5 14:32:51 ideapad kernel: [  156.149208] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May  5 14:32:51 ideapad kernel: [  156.149212] usb 1-3: Product: SAMSUNG_Android
May  5 14:32:51 ideapad kernel: [  156.149215] usb 1-3: Manufacturer: SAMSUNG
May  5 14:32:51 ideapad kernel: [  156.149218] usb 1-3: SerialNumber: 2c1400813e037ece
May  5 14:32:51 ideapad kernel: [  156.153815] rndis_host 1-3:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-3, RNDIS device, 6e:21:48:4e:3b:29
May  5 14:32:51 ideapad NetworkManager[775]: <info>  [1651753971.6849] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/9)
May  5 14:32:51 ideapad mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
May  5 14:32:51 ideapad mtp-probe: bus: 1, device: 7 was not an MTP device
May  5 14:32:52 ideapad gvfsd[5850]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
May  5 14:32:52 ideapad gvfsd[5850]: Android device detected, assigning default bug flags
May  5 14:32:52 ideapad systemd-udevd[5884]: Using default interface naming scheme 'v250'.
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3873] device (usb0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3918] device (usb0): carrier: link connected
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3955] device (usb0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4007] policy: auto-activating connection 'Conexión cableada 1' (787e76cf-5e07-316a-82ca-e64466949929)
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4029] device (usb0): Activation: starting connection 'Conexión cableada 1' (787e76cf-5e07-316a-82ca-e64466949929)
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4032] device (usb0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4041] manager: NetworkManager state is now CONNECTING
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4047] device (usb0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4059] device (usb0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4087] dhcp4 (usb0): activation: beginning transaction (timeout in 45 seconds)
May  5 14:32:52 ideapad avahi-daemon[732]: Joining mDNS multicast group on interface usb0.IPv6 with address fe80::39a3:a7b4:7e0b:4b25.
May  5 14:32:52 ideapad mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
May  5 14:32:52 ideapad avahi-daemon[732]: New relevant interface usb0.IPv6 for mDNS.
May  5 14:32:52 ideapad avahi-daemon[732]: Registering new address record for fe80::39a3:a7b4:7e0b:4b25 on usb0.*.
May  5 14:32:52 ideapad mtp-probe: bus: 1, device: 7 was not an MTP device
May  5 14:32:52 ideapad systemd[1]: Run anacron jobs was skipped because of a failed condition check (ConditionACPower=true).
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2838] policy: ipv6-pd: no device to obtain a subnet to share on usb0 from
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2841] device (usb0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2892] device (usb0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2899] device (usb0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2909] manager: NetworkManager state is now CONNECTED_LOCAL
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.3119] device (usb0): Activation: successful, device activated.
May  5 14:32:54 ideapad ModemManager[788]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3': not supported by any plugin
 

Racinghart91

Senior Member
Mar 18, 2013
657
60
Hi all,

Is installing microg mandatory ? Or is gapps included?

Just got a s9 that’s on Samsung rom.
 

cybermcm

Member
Oct 16, 2009
37
6
I recently played around with my old S9 (starlte) and tried Lineage 19, but didn't get past Google store install.
Now I wanted to try this rom, installed recovery from this thread, then cleaned all (in recovery) cache, data and system and installed rom.
But now my device reboots only in download mode. Tried it 3 times, no luck.
Any idea what I'm doing wrong?

Update (taken from other rom thread):
They changed the vendor. Probably because of that cause a lot of rom requires stock vendor. Just flash a stock vendor it will solve the problem.
 
Last edited:

ralrra

Member
Oct 4, 2015
23
2
Hi,
thanks for the great work first of all!
Recently i have a problem with the latest updates (S9 starlte). Since i don't use it on my daily phone I don't do regular updates. Did one Today (OTA) coming from a January version (don't know exactly which one).
OTA did load the version 20220606 and the update over TWRP recovery went fine but the system did not boot - stuck at the LOS boot animation.
I manually loaded version 20220615, same failure.
Then downgraded to version 20220420, this works like a charm.
Tested version 20220526 version as a test but same failure.

Any idea?
System itself is pretty standard, the only remarkable apps are shelter for using 2 profiles and root over Magisk.
Thanks!
 

Neurotical

Senior Member
Feb 7, 2011
244
400
I think there was a change in the Lineage OS that required a Lineage Recovery to be used. You may have to install the Lineage Recovery and try the install again. TWRP is not totally compatible with Lineage.
 

ralrra

Member
Oct 4, 2015
23
2
Thanks for the hint!
I tried it with the latest LOS recovery but the behaviour is exactly the same. The newer versions don't boot.
So it doesn't seem to be the recovery.
Any other ideas?

If i have more time, i try to find the bootlog but not sure, if/how i can access that, if the system does not boot....
 

m0m0331

Member
Sep 5, 2019
6
0
for me everything still works. I use twrp and the newest update from this magnificent ROM.
OTA still does not give me updates but hey, I can live without that. Funny thing is, I get the notification when an update is available but when I scan for it, nothing new shows up. So I just made a shortcut and added it to my homescreen.

I have encountered some weird lighting issue, where the Phone switches from full brightness in black mode to full brightness in this dark grey mode & apperance changes a bit. I only encounter it when full brightness is turned on - and the guide you posted above (post 484) fixed it. I never knew there was something like "outdoor mode".
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    FYI new update includes:
    • Kernel update 4.9.316 -> 4.9.317
    Now available via OTA or OP.

    Have a great day!

    🤩🥳👍🐸🐅🌟
    4
    FYI new update includes:
    • Kernel update 4.9.317 -> 4.9.318
    • June AOSP security update
    Now available via OTA or OP.

    Have a great day!

    :):):)
    3
    FYI new update includes:
    • Kernel update 4.9.318 -> 4.9.320
    Now available via OTA or OP.

    Have a great day!

    :):):)
  • 24
    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.