Well, as writen in Magisk tutorial you normally shouldn't use this option.
No I dont have that problem, I can switch from nth, to direction of travel etc without problem. osmAnd 3.9.10 from fdroid
I dont even notice a temp change on LOS 18.1, but i make a habit of "force stop" apps after I have finished with them. Settings > apps and notifications .. this displays the last 3 apps, click on the app > force stop. frees up phone resources. Yes, you can force stop "phone" and "messaging" service too, phone still receivces incoming / make outgoing calls, and SMS likewise. Just "force stop" after the conversation. Battery live depends on my use, but I go all day at screen 55%, and using Pixel Battery Saver app ( adds small black dots that you cant see ) and permanent dark mode - even in daylight its fine. bluetooth off, location off, wifi off, data off when not needed. you get prompted to turn data on for MMS messages. Email needs data obviously, 9 Plus.
I could certainly be wrong, but I think custom roms will typically fall under "legacy support". The tutorial also seems to focus completely on stock roms and using Odin for flashing which doesn't apply (or isn't necessary?) for custom roms.
crDroid has a firmware link for the S9/S9+ that references PDA, CSC, and modem direct installs for Odin and TWRP. I don't see anything for Vendor, but you may try backing up the current VENDOR partition and using TWRP to flash a new vendor.img from the latest stock rom. Make sure you aren't changing Android version.
Well, some people reported software brick on camera after using it, so I don't know anymore. But as far I remember it was working fine for me. And yes, it's for twrp, but I don't remember if its only libs for front camera or u will find as well the apk in config folder.
github.com
github.com
Just take the latest date and choose the version for your model at 'Assets'.
I lost baseband after flashing this rom. No imei. Any solution?
REQUIREMENTS:
- Stock Samsung Oneui 2 - 2.5 (Android 10) Firmware. (Bootloader + Vendor)
INSTRUCTIONS:
- Lineage Recovery or TWRP
- Format /system + /data + /cache
- Flash
- Reboot
WORKING:
- Wi-Fi
- Bluetooth
- Mobile Network
- GPS
- NFC
- Audio
- Camera
- Fingerprint Sensor
- HDMI
- Ethernet
- MTP/ADB
- Call Recording
- Encryption
- SELinux Enforcing
- Android Auto
- Glove Mode
- OTA Updates
BROKEN:
- Iris Scanner
- VoLTE
DOWNLOADS:
XDA:DevDB Information
LineageOS 18.1, ROM for the Samsung Galaxy S9
Version Information
Status: Stable
ROM OS Version: Android 11
ROM Kernel: Linux 4.9.118
ROM Firmware Required: Oneui 2 - 2.5
Contributors
synt4x.93
Source Code: https://github.com/synt4x93/
Created: 16-12-2020
Last Updated: 21-03-2021
hopefully made a backup beforehand? Without that, never fumble with the device.
Hi,
mkdir -p ~/bin
mkdir -p ~/android/build
mkdir -p ~/android/build/src
mkdir -p ~/android/build/ccache
mkdir -p ~/android/build/keys
mkdir -p ~/android/build/logs
mkdir -p ~/android/build/zips
mkdir -p ~/android/build/manifestscurl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo“if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi”cd ~/android/build/src
git config --global user.email "you@example.com"
git config --global user.name "Your Name"source ~/.profile
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1repo syncPRODUCT_PROPERTY_OVERRIDES += \
lineage.updater.uri=https://raw.githubusercontent.com/<Your_username>/OTA/lineage-18.1/starlte.json...
<project name="synt4x93/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-18.1" />
...repo syncsubject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
cd ~/android/build/src
for x in releasekey platform shared media networkstack testkey; do \
./development/tools/make_key ~/android/build/keys/$x "$subject"; \
done
make a copy of the “keys” directory and keep it safe.docker pull lineageos4microg/docker-lineage-cicddocker pull pakaoraki/docker-lineage-cicddocker run \
-e "BRANCH_NAME=lineage-18.1" \
-e "DEVICE_LIST=starlte" \
-e "INCLUDE_PROPRIETARY=false" \
-e "SIGN_BUILDS=true" \
-v "~/android/build/src:/srv/src" \
-v "~/android/build/zips:/srv/zips" \
-v "~/android/build/logs:/srv/logs" \
-v "~/android/build/ccache:/srv/ccache" \
-v "~/android/build/keys:/srv/keys" \
-v "~/android/build/manifests:/srv/local_manifests" \
pakaoraki/docker-lineage-cicd{
"response": [
{
"datetime": 1627204505,
"filename": "lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"id": "39b85208c5c30edfafd983673a703d60",
"romtype": "UNOFFICIAL",
"size": 608774193,
"url": "https://github.com/<username>/OTA/releases/download/<tag>/lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"version": "18.1"
}
]
}I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks
To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L2435th July security update ready on this build if you are compiling your own.
How to check when its available besides going thru the make process and checking
~/android/build/core/version_defaults.mk
once complete for the security update date ?
Also checking the
//source.android.com/security/bulletin
for the monthly date and
https://lineageos.org/blog/
changelog
isnt helpful. How to know what patch is ready to build before I go thru the whole process ???
Need to keep the device patched to the latest at all times to be able to use as a daily for work
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.
