[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

[x2k13]

Another strange problem :

Have regularly "Missing SD Card" : the SD is a Sandisk ultra 128Gb class10 (A1) a new one of course.

The SD card is treated as "internal" not external.

it's a Known problem ?

I try to do the same thing (as internal) with Lineage OS 17.1 latest ROM on an another Phone, same problem :0x
Set the SD card , data transfer , no problem.
Restart the phone (because i need to put a Sim)

BAM : "Missing SD card"

Look if SD card is well inside the SD Port, no dust, etc.... No physical problem.

Try to restart the phone : a notification say "Carte SD Sandisk" is missing and still remain permanent now

I've had this a lot with adopted storage (sd-card formatted as internal storage).
In the end I got fed up with it and just use it as external sd-card. Since then that issue never occurred again.

 

[DoZe22]

I've had this a lot with adopted storage (sd-card formatted as internal storage).
In the end I got fed up with it and just use it as external sd-card. Since then that issue never occurred again.

Thanks for this reply. Hope this bug can be solved in next release.

it's V-E-R-Y helpful with 16Gb version.

32Gb version of Sm-G900F is more than hard to find !

 

[curiousrom]

Have regularly "Missing SD Card" : the SD is a Sandisk ultra 128Gb class10 (A1) a new one of course.

The SD card is treated as "internal" not external.

Hope this bug can be solved in next release.

It won't be fixed anytime soon.

See the dev's quote in this post: LineageOS 18.1 for S5 Performance & Adoptable Storage
***

 

[Hasan1122behj]

Some problem or bug in " split screen "

 

[vinfraxd]

@haggertk grazie per il tuo fantastico lavoro!! Una domanda: perché i gesti di navigazione non sono abilitati per impostazione predefinita? Devo modificare il file build.prop per ottenerlo ..

Saluti !

SO HOW tO enable gestures?

 

[curiousrom]

S5 On-screen Navigation bar & Gestures

SO HOW tO enable gestures?

The only options for the S5 by default on LineageOS 18.1 are found in Settings > System > Gestures and > Settings > Display > Advanced > Tap to sleep: Double-tap on the status bar or lockscreen to turn off the display.

Devices like the S5 do not have > Settings > Buttons > Navigation bar options nor on-screen navigation buttons nor > System > Advanced > Gestures > System navigation > Gesture navigation options because they have physical navigation capacitive buttons.

It can be enabled with the [MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more and adding qemu.hw.mainkeys=0 to the build.prop and reboot.

Or use adb root to add qemu.hw.mainkeys=0 to /system/build.prop as described here. Note that =1 disables it.

While I tested this on my S5 G900M klte as seen in the screenshots, I don't use that because of the loss of screen real-estate & the physical buttons are working fine.
***

 

[vinfraxd]

S5 Barra di navigazione e gesti sullo schermo



Le uniche opzioni per l'S5 per impostazione predefinita su LineageOS 18.1 si trovano in Impostazioni > Sistema > Gesti e > Impostazioni > Display > Avanzate > Tocca per dormire: tocca due volte la barra di stato o la schermata di blocco per disattivare il display.

Dispositivi come l'S5 non hanno > Impostazioni > Pulsanti > Opzioni della barra di navigazione né pulsanti di navigazione sullo schermo né > Sistema > Avanzate > Gesti > Navigazione del sistema > Opzioni di navigazione dei gesti perché hanno pulsanti capacitivi di navigazione fisica.

Può essere abilitato con [MODULE] MagiskHide Props Config - SafetyNet, modifiche prop e altro e aggiungendo qemu.hw.mainkeys=0 a build.prop e riavviare.

Oppure usa adb root per aggiungere qemu.hw.mainkeys=0 a /system/build.prop come descritto qui . Nota che =1 lo disabilita.

Mentre l'ho testato sul mio S5 G900M klte come si vede negli screenshot, non lo uso a causa della perdita di spazio sullo schermo e i pulsanti fisici funzionano bene.
***

Thank you a lot. I will do it soon

 

[vinfraxd]

S5 On-screen Navigation bar & Gestures



The only options for the S5 by default on LineageOS 18.1 are found in Settings > System > Gestures and > Settings > Display > Advanced > Tap to sleep: Double-tap on the status bar or lockscreen to turn off the display.

Devices like the S5 do not have > Settings > Buttons > Navigation bar options nor on-screen navigation buttons nor > System > Advanced > Gestures > System navigation > Gesture navigation options because they have physical navigation capacitive buttons.

It can be enabled with the [MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more and adding qemu.hw.mainkeys=0 to the build.prop and reboot.

Or use adb root to add qemu.hw.mainkeys=0 to /system/build.prop as described here. Note that =1 disables it.

While I tested this on my S5 G900M klte as seen in the screenshots, I don't use that because of the loss of screen real-estate & the physical buttons are working fine.
***

ok bro so with adb i do not know why, but when i use adb root it doesn't work.
I also used buil prop from play store but when i modify the file (and save) in app i have error.
SO i use the magisk module but with termux (emul.) i can't see the effect of changes.
Termux>su>props>5>qemu.hw.mainkeys=0>y> reboot
I used this. But nothing changes...There is a magisk module to activate gesture?

 

[curiousrom]

Re: S5 On-screen Navigation bar & Gestures

ok bro so with adb i do not know why, but when i use adb root it doesn't work.
I also used buil prop from play store but when i modify the file (and save) in app i have error.
SO i use the magisk module but with termux (emul.) i can't see the effect of changes.
Termux>su>props>5>qemu.hw.mainkeys=0>y> reboot
I used this. But nothing changes...There is a magisk module to activate gesture?

With props first you add qemu.hw.mainkeys then you add the value 0 and reboot. (screenshots)

It works because I did it to update the screenshots I posted above.

If you need help with MagiskHide Props Config read the OP or ask in that thread.
***

 

[vinfraxd]

Re: S5 Barra di navigazione su schermo e gesti



Con props prima aggiungi qemu.hw.mainkeys quindi aggiungi il valore 0 e riavvia. (screenshot)

Funziona perché l'ho fatto per aggiornare gli screenshot che ho pubblicato sopra.

Se hai bisogno di aiuto con MagiskHide Props Config, leggi l'OP o chiedi in quel thread.
***

Brother thank you very much. You saved me. However you are right. A lot of space is lost. I go back to the original Laos with stock build.prop anddddddddddddddddddddddddd: LOL! All is BUGGED! AHAHAHAHAHAH. So I lost the gesture (back), I lost the gesture settings, but the gesture for recent apps (swipe up from the center) doesn't disappear! Well that's the only thing I want so I left this (also because I don't know how to remove it now ahahahahaha)






PS. Sorry for my english. My bad

 

[AloneDisaster]

So I lost the gesture (back), I lost the gesture settings, but the gesture for recent apps (swipe up from the center) doesn't disappear! Well that's the only thing I want so I left this (also because I don't know how to remove it now ahahahahaha)

You can disable it bro

su
cmd overlay disable com.android.internal.systemui.navbar.gestural

Type this in terminal if rooted or

adb shell
cmd overlay disable com.android.internal.systemui.navbar.gestural

This if not rooted via adb

 

[vinfraxd]

You can disable it bro

su
cmd overlay disable com.android.internal.systemui.navbar.gestural

Type this in terminal if rooted or

adb shell
cmd overlay disable com.android.internal.systemui.navbar.gestural

This if not rooted via adb

Thank you bro. You know also how to rotate lock screen without root? I have note 9 on stock ROM

 

[chillipig]

i have a similar problem, i have 2GB of free space in internal storage, but sometimes the phone decide that the internal memory is full and writes "no free space".... after a reboot is geting all normal... I'm on the 14112021 build, maybe was corrected the problem on newer build....

Thought I'd give it another go with TWRP 3.6.0_9 and lineage-18.1-20220109 but no difference. Clean install and opengapps pico, storage shows 12gb free but Google play says no space

 

[curiousrom]

"Clean Install" & No Space says Google Play?

Thought I'd give it another go with TWRP 3.6.0_9 and lineage-18.1-20220109 but no difference. Clean install and opengapps pico, storage shows 12gb free but Google play says no space

What is the full name of the Open GApps file that you installed?

Are you are trying to download huge 100 MB apps?

If you sideloaded Open GApps it automatically creates a log named open_gapps_log.txt in the internal sdcard folder.

If you copied to the device the GApps...zip package & installed it from there manually using the recovery then the "open_gapps_log.txt" is created in the same location as the GApps...zip package.

Maybe you could attach that log to a post? Zip it if you have issues attaching it to a post.

What do you mean exactly by a clean install? Format Data is better than a simple wipe Data if you want a really clean install. (screenshot)

See Clean Install with TWRP.

From TWRP FAQ: What is a data/media device?:

"...In TWRP we also have a wipe internal storage option that rm -rf's the media folder and a "Format Data" option that formats to recreate the entire file system in case something goes completely wrong or to remove device encryption."

Format Data adds an empty encryption footer after the end of the Data partition for some future encryption related data if enabled.

Format data will destroy the content of your internal storage so backup to external SD card or computer before doing it.
***

Try with MindTheGApps instead of Open GApps. See the bottom of this post about optimizing MindTheGapps which I installed on my S5 G900M.
***

 

[twindragon6]

Any word yet on F2FS and EXT4 external SD Card support yet?!? My Samsung Galaxy S5 (SM-G900V) only has 2GB of RAM and 16GB of storage. Right now it corrupts the crap out of the EXFAT partition at random. Maybe could we get some additional file system support for BTRFS, XFS, ZFS and others? How about any journaling file system support for the SD Card?!?

 

[rellieberman]

Anyone having issues with the alarm clock not ringing on time, or not at all?

 

[Massedil]

Anyone having issues with the alarm clock not ringing on time, or not at all?

Very rarely it happens to me too.

 

[rellieberman]

It happens to me quite often. Where can i find error messages/logs that will help figure out what causes this issue?

 

[Massedil]

It happens to me quite often. Where can i find error messages/logs that will help figure out what causes this issue?

I don't know... May be with "adb logcat" ? I suspect it is linked with the phone not exiting doze mode properly to trigger the alarm.

I have tried the app "Hourly Reminder" (https://f-droid.org/en/packages/com.github.axet.hourlyreminder/) to test if the phone works fine with alarms. I have set an alarm every ten minutes and the app says "Your device does not fire alarms properly". Effectively some alarms are totally missed or delayed.

There is also the app "DontKillMyApp" (https://f-droid.org/en/packages/com.urbandroid.dontkillmyapp/) that do some tests, but I haven't tried.

 

[EuK_V]

Anyone having issues with the alarm clock not ringing on time, or not at all?

I can confirm similar behavior. I haven't had issues with the alarm, but the timer didn't ring several times. In my case I think I resolve the issue adding the Clock app to the "Ignore list" in the task manager I use. Since then I haven't had missed timer rings (I use timer on a daily basis).

I have tried the app "Hourly Reminder" (https://f-droid.org/en/packages/com.github.axet.hourlyreminder/) to test if the phone works fine with alarms. I have set an alarm every ten minutes and the app says "Your device does not fire alarms properly". Effectively some alarms are totally missed or delayed.

I tried "Hourly Reminder" app - had no errors - the alarm is working.
My device is SM900FD (klteduos).