yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] JustaNoobda:
OTA not working

So I'm new to this stuff , I have latest 3.3 twrp , modified vendor DTC5 whatever and magisk installed. Everything works fine , I'm on the 1st day build of this rom. The only major issue I found is that OTAs aren't working , it says *install error* when trying to install using the system updater. Then I tried flashing update using the lineage recovery , it flashed but took away my gapps , magisk and everything felt unusable so had to do a clean install. Can someone tell me exact steps on flashing this rom and the official or modified vendor , I have both. I just want working OTA with magisk. And what about twrp? Some people here are recommending the 3.2 v ig...why though...thanks a lot this rom is frikin amazing :)
[Samsung Galaxy S9 & S9+ Cross Device Development] -laughingman:
Hey guys, I'm planning to switch to this and and would like to ask you guys if my steps are wrong. I'm currently on ALEXNDR's rom U8DTC5.

Here are the steps:

1) Wipe Dalvik / ART Cache, System, Data, Internal Storage, Cache

2) Flash LOS 17.1

3) Flash gapps

4) Flash magisk
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I'm really happy using this ROM as my daily driver.

Right now only one thing is a little bit annoying:

I'm using a sd card as additional jnternal storage so some apps have been moved from the phone's internal storage to the sd card.

Additionally you can always start this process at settings>>storage>>internal storage>>hamburger menu>>migrate data.

With this change some of my apps started to be laggy and behave not as expected (e.g. only informing about new messages when opening the app).

I'm not sure if it's a ROM issue.

Perhaps I'm not the only one with this problem?
[Samsung Galaxy S9 & S9+ Cross Device Development] jfitie:
Just create an empty file named 'Android' in the root of your SD card on a PC before using it with your phone (or copy any file over and rename it). Works great for me. Reason this works is that the Android directory required for app storage can't be created by the OS because a file with the same name is there already.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Thanks for your help but I don't get it: What will your solution do exactly regarding to my problem?
[Samsung Galaxy S9 & S9+ Cross Device Development] crewpuk13th:
In my case

- have stock vendor from stock Samsung ROM

- Use TWRP 3.2.3 since it's the one recommended. 3.3 is a mess

- Have clean install, format data

- flash LOS 17.1, GAPPS and Magisk

- OTA will work only with lineage recovery AFAIK

- if you tend to use TWRP, you have to flash Ota update manually
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
Hi,

Here's my experience trying this out.

Had :

- Lineage OS 15.1 built from lineage sources

- "Full disk" encryption enabled

Did :

- (preparation : uninstall magisk, switch to release keys)

- flashed latest official Samsung BootLoader, Modem, Vendor (8DTC5) via TWRP

- flashed lineageos latest system+boot zip via TWRP

Result :

Bootloader worked ok.

Lineage loads and loads then reboots

Never got to the "enter your password to decrypt" screen

Rebooted to TWRP; rollbacked using a backup made just before. rolled back : cm, sboot, keystorage, param, modem, system, vendor, boot, etc.

So to everyone asking : Yes ! You can rollback the bootloader (and everything else it seems) to an earlier "bit version" using TWRP ! (very different version of BL)

Everything still works (though I'm still on 8.1) I even managed to keep my userdata intact.

Note : At no point during my operations did I use Odin flash mode, this may have an impact on wether you are able or not to flash an older bl afterwards

Hope that helped some.

EDIT :

I might try the devBase vendor see if it works with "full disk" encryption

LATER EDIT : flashing with twrp may not always work as some partitions may be silently read only and it might have been why it didn't work
[Samsung Galaxy S9 & S9+ Cross Device Development] Olangu:
You need stock vendor.
[Samsung Galaxy S9 & S9+ Cross Device Development] smorgar:
I second this. Finger print gesture would be a great addition to los 17.1. I am really missing it.

But more importantly the press hard on home button when screen is off to wake the device works fine. The problem is that the option to disable it is missing. Should be under settings > system > buttons if I understand correctly but it's not.

OneUI 2.0 is quite nice and many good features but it's still touchwiz and I have tried making the s9 my daily driver but it's not what it needs to be for me. Now with LOS it's a different story. LOS saves the day again :)

Thank you for a great rom!
[Samsung Galaxy S9 & S9+ Cross Device Development] Ish4:
The rom is amazing. Things that i really like super fast fingerprint scanner better than One UI 2.0. A real nice dark theme. Amazing customizations. And the main highlight the battery way better than the stock. Thanks :)
[Samsung Galaxy S9 & S9+ Cross Device Development] andromuks:
one more question

How about the camera? Does it support stock Samsung camera?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Custom ROM's that are not based on stock Samsung ROM's will never have stock Samsung cam because of closed stock Samsung sources.
[Samsung Galaxy S9 & S9+ Cross Device Development] ordeniz:
So which camera app do you recommend for best performance with LOS?
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
Open Camera (https:// f-droid . org/en/packages/net.sourceforge.opencamera/)
[Samsung Galaxy S9 & S9+ Cross Device Development] xo.en:
Asus cam. : )

com.asus.camera.

Open cam is good, but this one is better.

Problem is: you need los16 to install it, then upgrade to los 17.1...for some reason you cannot install it with 17.1...
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
Following my previous post, i just tried :

- synt4x rom

- this official ROM with devbase vendor

both exhibited the same behavior as before :

- bootloader ok

- lineage loading and loading then reboots

- never got to the decryption screen

rolled back OK

LATER EDIT : can be discarded as I did not use odin but blindly flashed with TWRP
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
Well I just did some incredible thing.

- Enabled ADB

- Granted root via magisk to "shell/adb" (#su)

- Rebooted Android to safe mode (less userdata activity)

- Dumped /dev/block/dm-0 (decrypted /data)

- e2fsck to clean/repair it (dirty dump)

(we now have an unencrypted /data dump)

- boot to TWRP

- flashed decrypted /data it over encrypted /data

And at the next boot Android (still 15.1 wanted to check first) re-encrypted my data :(

So yes I essentially decrypted my /data (and got it re-encrypted :/).

Is it something that I would recommend ? No. The dump is dirty by essence given that /data is mounted and in use. Plus flashing the whole 50G of the partition is very slow and must reduce the emmc life, maybe using sparse image would work.

Is there some hidden forceencrypt flag somewhere on Lineage ? I haven't found any.

EDIT :

Probably the "breadcrumb" file : /data/misc/vold/convert_fde (fde : full disk encryption)

I'll try again tomorrow with the file removed.

The goal for me is to have un-encrypted data to see if works better when upgrading to this lineage 17.1 version.
[Samsung Galaxy S9 & S9+ Cross Device Development] xo.en:
This rom is a jewel.

It may be not easy to settle, but when it is properly set, it works like a charm.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
What do you need to settle it?
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
have you a link?
[Samsung Galaxy S9 & S9+ Cross Device Development] ioctl0:
OEM Lock prevention

Hello!

For now I'm on self-built LOS 15.1. My S9 aim's to enter OEM Lock after installing custom firmware, so once I had to flash stock with loosing all data.

So, should I install RMM-State_Bypass or something like this while flashing LOS 17.1 to prevent OEM Lock on this, or subsequent OTA update?
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
https://www.apkmirror.com/apk/zenui-asus-computer-inc/camera-zenui-asus-computer-inc-2/

If you are on lineage 15.1 (like me) then I don't think you need any of what you mention.

EDIT : Some research showed me that I might be wrong, you should check in download mode what it tells your regarding RMM

For me : I have no mention of RMM and have OEM unlocked
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
Camera problem.

Thanks a lot for that, so for just everything works perfect less the rear camera, when i try to open it, the app just crash. I've installed de Open Camera app and de same happens with the rear camera, but front camera works perfect with Open Camera.
[Samsung Galaxy S9 & S9+ Cross Device Development] Olangu:
You can flash a vendor that don't enforce disk encryption if you like (but OTA won't work).
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
I know. Right now I'm trying to have a decrypted data partition (and keep what is on it ; which I managed to have, briefly) with LOS 15.1 to see if the upgrade to LOS 17.1 works (bootloop with encrypted data). I do want encrypted data after the upgrade.
[Samsung Galaxy S9 & S9+ Cross Device Development] OcainD:
Planing to install this rom, have a few questions.

Does it support dual sim galaxy s9?

Does it work with galaxy watch, galaxy buds and all the devices that need galaxy wearable app? I had issues with this in other aosp roms

Im currently on samsung one ui with android 10, do i just flash the rom via twrp after wiping?
[Samsung Galaxy S9 & S9+ Cross Device Development] Ish4:
No use. But use the open camera its as good as samsung camera.

---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------

No. But use the open camera its as good as samsung camera.
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
It seems my problem is not related to the encrypted state of userdata

With an de-encrypted one : same behavior (loads then reboots)

This time i had a look at last_kmsg.

What I seem to understand is :

The whole "system" boots in read only for some reason

I ran "e2fsck -v -f" on SYSTEM VENDOR USERDATA CPEFS EFS OMR ODM. All clean.

<14>[ 6.744557] [4: init: 1] init: Command 'mkdir /storage/emulated 0555 root root' action=init (/vendor/etc/init/init.samsungexynos9810.rc:12) took 0ms and failed: mkdir() failed: Read-only file system

Presented here is the first one. So lots of those errors

Then

<14>[ 7.634345] [4: init: 1] init: Received control message 'interface_start' for 'android.hardware.keymaster@3.0::IKeymasterDevice/default' from pid: 4157 (/system/bin/hwservicemanager)
<11>[ 7.634371] [4: init: 1] init: Could not find 'android.hardware.keymaster@3.0::IKeymasterDevice/default' for ctl.interface_start

The system retries and retries.

Then the TEE stops and a kernel panic ensues.

<3>[ 70.628881] [0:android.hardwar: 4272] Trustonic TEE: wait_mcp_notification: No answer after 20s
<3>[ 70.629251] [0:android.hardwar: 4272] Trustonic TEE: nq_dump_status: TEE halted. Status dump:

I guess I must be doing something wrong, no idea what though
[Samsung Galaxy S9 & S9+ Cross Device Development] joey21:
Rsap does not seem to work. To Bad since the Rest is perfect. Does anyone know a way ?
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
Dex? I don't think so, since Dex is proprietary software of Samsung and not a native AOSP feature.
[Samsung Galaxy S9 & S9+ Cross Device Development] raf99:
Bootloop after update

Hello everyone,

thank you so much for picking up the support for S9! :o:good::victory:

I came from LOS15.1, flashed latest stock and then installed LOS17.1 as described on the official page (w/ Lineage Recovery and Nano Gapps).

I did the update from 24th of April and today I tried to update 27th. This got me stock in the LOS loading screen and then the "Android could not be loaded. Your data may be corrupt". Tried to wipe cache to no avail, same thing:crying: I've sideloaded version 24th via ADB which let me start into LOS again :fingers-crossed:

Before I do another attempt, I was wondering if I can find out what went wrong? Are there log files I can check?

Thanks:o
[Samsung Galaxy S9 & S9+ Cross Device Development] ghnue:
/proc/last_kmsg
[Samsung Galaxy S9 & S9+ Cross Device Development] ioctl0:
Modem problems

Hello!

I had self-built LOS15, then I flashed bootloader, TWRP, modified vendor, LOS 17.1 and Magisk, RMM_Bypass_v3 without wiping data. Everything was OK except for radiomodule: device was unable to detect SIM cards and didn't show modem version in settings. At that, WiFi was working. I flashed last modem from here: https://xdaforums.com/galaxy-s9/how-to/basebands-modems-sm-g960f-g965f-t3858990 , wiped data, but modem still not works.

Update: It seems, problem was in RMM_Bypass. When I update Vendor again, modem alive. But for now WiFi is not working.

Update 2: I have to wipe data and internal storage to make WiFi work.
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
Rear camera not working

Rear camera is not working. When i try to open the camera app it show an (very quick that i can't read) error and close.

I've installed the OpenCamera App and the the same problem with rear camera, but here, if i switch to front facing camera it works perfectly.

Any one can help with this?

Besides this situation, lovin this rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] Andrw0830:
Are you on Q Bootloader, CP and vendor? I am on my starlte and using those and Camera works fine. Try and make sure you are on DTC5 version as that's what I am on and it works.
[Samsung Galaxy S9 & S9+ Cross Device Development] HansMampf:
Screen resolution - battery life

I feel the battery is discharging too quickly.

On which screen resolution are the devices running under LineageOS 17.1?

I didn't find a display resolution setting in LineageOS 17.1, just the DPI setting in the developer menu, but I don't think it's the same.

Is it possible to add the option under Settings> Display> Screen resolution , as described here?

https://www.sammobile.com/news/psa-galaxy-s9-arent-set-to-maximum-screen-resolution-by-default/

""...Samsung’s primary reason for setting the display to Full HD+ (2280×1080 pixels) by default is apparently battery life. As many of you might have noticed, however, there’s no perceivable battery life difference between Full HD+ and WQHD+ (2960×1440 pixels). Yes, Full HD+ is more than enough for everyday usage..."
[Samsung Galaxy S9 & S9+ Cross Device Development] ioctl0:
I can confirm these words :)

Following my tests, if phone shows physically the same picture (I have used terminal to dump very big file on the screen), there is no difference what virtual resolution is set.

Phone cannot change physical resolution. The only thing is a lesser CPU and GPU load while rendering sophisticated scenes in a lower virtual resolution. You will see power consumption difference only if you play heavy 3D games or something like this.
[Samsung Galaxy S9 & S9+ Cross Device Development] impassibile:
Im flashed los171 but stuck s9 logo
[Samsung Galaxy S9 & S9+ Cross Device Development] crewpuk13th:
tell me your step how did you flash this so we here can figure out the resolution of your problem
[Samsung Galaxy S9 & S9+ Cross Device Development] HansMampf:
battery life

ok than I forget about the disolay resolution. Thank you.

"battery life"

S.Th. is not good on my device (I just started with Lineage 17.1 on the S9+ yesterday).

I fully charged the battery, then removed the charging cable and did not use the device. After 2 hours, the battery was 5% less (still 95%) without using the device. I have not installed any gapps, in the settings under battery no app was shown that was consuming the battery.

If I do the same with my Sony XA2, I have 14 days of battery life, here with the S9 + it is less than 1.5 days. With the original Samsung Android software, it was about 1 day.
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
Yes, I had the version, Android 10 and OneUi 2.

Then, I followed this tutorial: https://wiki.lineageos.org/devices/starlte/install.

I downloaded the files from here: https://download.lineageos.org/starlte and i've downloaded the last version available: lineage-17.1-20200429-nightly-starlte-signed.zip and lineage-17.1-20200429-recovery-starlte.img

I've done the process all over again, reinstated the original Samsung version and did the process again to install LineageOS but the problem remains. : crying:
[Samsung Galaxy S9 & S9+ Cross Device Development] jorgespv:
The resolution in LOS is WQHD +. Take a screenshot and you'll see

Enviado desde mi SM-G960F mediante Tapatalk
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
Should i use TWRP or heimdall and adb sideload? Thanks for your help.
[Samsung Galaxy S9 & S9+ Cross Device Development] smorgar:
I went with Heimdall as the guide said:

https://wiki.lineageos.org/devices/starlte/install
[Samsung Galaxy S9 & S9+ Cross Device Development] Colemanuk:
I flashed the no encrypt file and have no ota updates. I know I can "export" then flash which works well but it won't update the recovery...

If I flash the original vendor file (approx 3gb) will it wipe my phone and I'll have to start again?
[Samsung Galaxy S9 & S9+ Cross Device Development] JoaoPCAzevedo:
I'm so dumb, i was installing the starlte version instead of star2lte :eek:
[Samsung Galaxy S9 & S9+ Cross Device Development] ioctl0:
You can use adb sideload to flash only *zip files in twrp. But, you can copy *img to phone from current firmware, and then flash them from twrp. I have put all files except for twrp itself to internal storage in advance using old firmware, and flashed them from twrp. TWRP *img itself I have flashed from running firmware, but you can do it with *img from bootloader with heimdall or odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] OcainD:
Hi, just tried to install this rom and got a bootloop.

i installed it in twrp 3.3.1 with full stock arm gapps.

what can i do?
[Samsung Galaxy S9 & S9+ Cross Device Development] ordeniz:
Gapps should be arm64, and pixel launcher force closes on stock gapps. I recommend pico.
[Samsung Galaxy S9 & S9+ Cross Device Development] OcainD:
i just did tried to flash without gapps, still having bootloop. any idea?
[Samsung Galaxy S9 & S9+ Cross Device Development] ordeniz:
Are you on Android Q?
[Samsung Galaxy S9 & S9+ Cross Device Development] OcainD:
i was on stock one ui android 10 and then installed twrp
[Samsung Galaxy S9 & S9+ Cross Device Development] ordeniz:
Then it must have something to do with TWRP installation.
[Samsung Galaxy S9 & S9+ Cross Device Development] Andrw0830:
No problem glad you've got it working!
[Samsung Galaxy S9 & S9+ Cross Device Development] huz_sid:
Recovery Update

How to update the LineageOS recover, or will the recovery update itself with the new nightly build??
[Samsung Galaxy S9 & S9+ Cross Device Development] intagaming:
Can we add some haptic feedback on hard pressing the home button? That would be more pleasing as to get nothing in return and doesn't actually know if it's actually registered.
[Samsung Galaxy S9 & S9+ Cross Device Development] HansMampf:
Battery life

I installed LineageOS 17.1 without gapps. No SIM card. only WiFi .

There are almost no programs running in the background.

My battery lasts 1.5 days. I lose about 2.5% battery per hour without the display being active.

That should not be so. The battery would have to lose almost nothing and last about 14 days.
[Samsung Galaxy S9 & S9+ Cross Device Development] Hack_AR:
What happened to the downloads? The versions after 0422 are no longer available?
[Samsung Galaxy S9 & S9+ Cross Device Development] ioctl0:
CPU freq, usage and hotplug

I have noticed, that LITTLE and big CPUs usage time is just the same. Here are some shell command's output:

# uptime

10:56:34 up 1 day, 11:36, 0 users, load average: 11.08, 11.24, 11.64

# cat /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state | awk '{ i=i+$2 } END {print "time " i/100/3600}'

time 11.9462

# cat /sys/devices/system/cpu/cpufreq/policy4/stats/time_in_state | awk '{ i=i+$2 } END {print "time " i/100/3600}'

time 11.9475

That means, that every wake up from the sleep mode make each of 8 CPU's work, even for low priority background tasks.

Is it possible to use CPU hotplug or something like this to wake up big CPUs only when they really needed?
[Samsung Galaxy S9 & S9+ Cross Device Development] droidsometimes:
That doesn't sound right indeed.

I'm also without Gapps, and very light usage, but WiFi is on half of the time, one SIM inserted and active, and so far it looks great.

Build is 20200425-nightly.
[Samsung Galaxy S9 & S9+ Cross Device Development] Hack_AR:
Do you have NFC enabled? That was a big deal for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] HansMampf:
BT and NFC is switched off, only WiFi is on, no SIM inserted
[Samsung Galaxy S9 & S9+ Cross Device Development] jamescarter117:
No Sim card detected

Hi mates,

Disclaimer: total noob here, first time flash a custom rom. Im in big trouble and in dire need of your help.

So, the latest update from SAMSUNG sucks a big time. In short, I lost ~30% battery overnight without any use, only wifi enabled. That is the trigger to made me switch to LOS.

Flashed by TWRP, but upon booting, no SIM card detected, and IMEI was null. Tried to restore the IMEI using phone dial, the app keep stopping.

I dont know what to to now. Please help.
[Samsung Galaxy S9 & S9+ Cross Device Development] droidsometimes:
Sounds like you might need start over?

Like, use Odin to flash stock firmware for your particular model (which you failed to mention) and your region. Try sammobile.com.

Plenty of info out there on how to do that.

(TBH not sure if anti rollback is a thing here, in case the firmware you download is older)

Also there's word out there that the last week of LOS 17.1 builds were broken, might want to keep that in mind.

Although, 20200425-nightly is working great here (no Gapps, no Magisk).
[Samsung Galaxy S9 & S9+ Cross Device Development] mmars:
2 issues with 30 April

Hello everyone,

detected the following issues:

Notification light not working

With the display switched off, the notification light does not blink for some apps: calendar (etar) and email (k9) as an example. It works only for missed calls, sms and weird enough for whatsapp. The vibration works fine tough. Am I missing something in the settings?

Whatsapp is uninstallable

Downloaded whatsapp.apk from the original whatsapp site, nothing happens when I tap on uninstall the first time, the second time the following warning appears: package installer keeps stopping.

Tested with the 30 April version of LOS17.1. Installed as described on the first page in this thread, phone not rooted and without gapps.

Thank you for this very smooth OS on S9.

Mar
[Samsung Galaxy S9 & S9+ Cross Device Development] ordeniz:
What's going on with the latest builds?
[Samsung Galaxy S9 & S9+ Cross Device Development] HazardsDE:
there is no camera delivered in last build? atleast i dont see one.
[Samsung Galaxy S9 & S9+ Cross Device Development] Colemanuk:
Ota not working results in error every time.

No matter if I use twrp 3.2.3 or lineage recovery.

I've formatted data and reinstalled twice now and still not working. Help! otherwise rom works fine.

I've used stock vendor from what I can tell...

A link to the files I need would be useful
[Samsung Galaxy S9 & S9+ Cross Device Development] jamescarter117:
Hi,

Thanks for your reply. My version is SM G960F

I am actually downloading the stock room version from Sammobile (painfully slow and unstable connection, but almost done now after 6 hours). I will do as you said then update later.

Cheer!