yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] kurtn:
None
[Samsung Galaxy S 4 Unified Development] therob2:
I just want to notice me edit. A GT-I9505 with several reboots now did not show any reboot in other circumstances (other use-mode, no SIM, no SD) - maybe a clue?! I don't know... Will try 18.1 optimized in next days... Could make logcat with 17.1 until then - but from what?! Cheers.
[Samsung Galaxy S 4 Unified Development] therob2:
Are there any wifi-reconnects known yet (did not find any with search) with GT-I9515/jfvelte and LOS17.1-Nightly? I just have two (of 5) devices which show some reconnects on a 2.4GHz-only Wifi (FritzBox 7390) which has fine connection with others. Any hints or settings I should adjust on LOS17.1?
[Samsung Galaxy S 4 Unified Development] xperanto:
random black screen and freezes due to swap? need some confirmation.

Is it just me or does gt-i9505 with LOS 17.1 doesn`t have a swap partion,

# free -m
total used free shared buffers
...

Swap: 0 0 0

while default swappiness is set to 60 (out of 100).

# cat /proc/sys/vm/swappiness
60

After disableing swappiness with

# sysctl -w vm.swappiness=0

(must be root and won`t survive a reboot) i have never encountered any freeze/lag or short blackscreen for over two weeks now, which i normally do get sometimes while e.g. messaging.

Would be nice, if someone can try it and report. Maybe it`s just a coincidence...
[Samsung Galaxy S 4 Unified Development] vip5912:
I disabled swappiness.

I will test and let you know.
[Samsung Galaxy S 4 Unified Development] dfw123:
lineage 16 does not support too! Will it support sprint L720T in the future?
[Samsung Galaxy S 4 Unified Development] vip5912:
Unfortunately, the next day after turning off the swap, I have a regular reboot (freeze, horizontal stripes, reboot).

Image: 2021-03-18.
[Samsung Galaxy S 4 Unified Development] xperanto:
:( Thank you for your response.

if you want you can lower it to 19 with

# sysctl -w vm.swappiness=19

That`s what the guys from JDCTeam are using ( https://github.com/JDCTeam... )

Maybe this will at least reduce the issue...
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I'm - without blaming you - not very surprised of that.

(just) my thoughts:

when a software crashes, it is existential it is currently running and therefore *in* RAM.

a "sleeping" code in an swap file won't never crash.

so forcing the program code, and surely the faulty code too, to "stay" [1] in RAM doesn't lower the occurence of an crash.

Rather the opposite.

more to read regarding swappiness:

What Is Swappiness on Linux? (and How to Change It)

Swappiness in Linux has nothing to do with how much RAM is used before swapping starts. We tell you what it really is.

www.howtogeek.com

[1]

disabling swappiness doesn't (after reading the artice) mean swapping is also OFF
[Samsung Galaxy S 4 Unified Development] xperanto:
my thoughts were about Improper impementation of swap, especially when you don`t have a dedicated swap partition/file which can lead to crash.

Your assumption, that "sleeping code" in swap can`t lead to a software crash "and when a software crashes, it is existential it is currently running and therefore *in* RAM" is wrong in that way, that it could have been that currently running software overrides already mapped memory, what would lead to a crash when reloaded other code from swap.

edit: And please don`t forget, when swappiness is defined with "60" in kernel and there is no swap to be found, do you know if there is code which relies/depends on this entry? I don`t.
[Samsung Galaxy S 4 Unified Development] vip5912:
As I understand 19 is not the default value for VM_SWAPPINESS but it's enum of VM_SWAPPINESS variable.
[Samsung Galaxy S 4 Unified Development] xperanto:
yes, as the JDCTeam mentioned on github:

But there is no swapped on swap on this device, as you can check with

# free

it would be interesting to see if the issues also accure with an enabled swapfile, and luckily swap is already enabled in kernel.

To create a swap just insert an external sdcard (without adopting it to internal sdcard, just as "portable memory") if you haven`t already.

In terminal/shell, browse to it as root with

cd /mnt/media_rw/whatever-name-of-extsdcard

Create a e.g. a 1,1GB swapfile with

dd if=/dev/zero of=swapfile count=2100000

change permission with (just in case which filesystem you are using)

chmod 600 swapfile

make it a swapfile with

mkswap swapfile

and swap it on with

swapon swapfile

if you enter free, you will get an output like this now with swap enabled

Swap: 1075195904 0 1075195904

start using your phone as normal and swap is used but keep in mind, that after a reboot you have to swapon the file again.

If you are willing to try this, please leave swappiness at the default value 60.

external sdcard is of course slower than real RAM, but maybe enableing swap will at least have a positive effect on the issues.

Give it a try.
[Samsung Galaxy S 4 Unified Development] vip5912:
First, LineageOS 17.1 worked well until November 2020 without a swap. Therefore, the problem is not swapping.

Secondly, my SD card is formatted as Adopted SD and I cannot create a swap file on it.
[Samsung Galaxy S 4 Unified Development] NewIdenty:
Did the pink screen issue ever happen to anyone when their device was plugged in to USB? I dont recall it happening to me.

I've had the pink screen issue for years. The reboot issue though is new but only happens like once a month for me
[Samsung Galaxy S 4 Unified Development] vip5912:
There was a problem with the "pink screen" before, but now it is not (for me). The solution was power off / on.

The "freeze / strip / restart" problem arrived in November 2020. I have it about once a week.

I'm waiting LOS 18.1 (I think nobody will research and solve this problem in LOS 17.1).
[Samsung Galaxy S 4 Unified Development] Max Frost:
Hi , I'm running two SPH-L720 devices and have been on this rom for a good while. Sounds all work fine , audio music , calls , ringers etc. There are no sound issues whatsoever so I have to assume you either have a bad install , speaker failure or some other hardware problem. We have the same device and with mine working perfectly it simply can't be a problem with the rom. Try installing something else to see if you have sound again to verify it's not a hardware issue. Exactly what sounds are you missing ? All sounds or just certain ones?

On your Majisk question I'm on 20.4 but anything newer is fine too. The new version 22 has been combined with the manager so they'll always be synchronized versions going forward.

Interesting to note this sprint version doesn't seem to have a single problem like the reboots , pink screens or any of the problems that the other variants seem to be having. It's rock solid smooth and stable. The only single problem I know of is the location/data fault that occurs where starting an app that uses GPS knocks out mobile data . Hopefully at some point we'll be able wo work on that.
[Samsung Galaxy S 4 Unified Development] :
Wow! Thank you for the very detailed answers!

I am starting to think that it could be some kind of hardware problem. Maybe I'll let it have a look on some phone repair shops in my place.

For the magisk: Is there a need to delete the old magisk app if I were to flash a newer version? If so, would I still have to download the uninstaller and flash it? Or can I just uninstall it in the user interface?

Yeah, it's kind of unfortunate that my sprint version had this kind of issue. But I'll see what I can do. Thank you very much!
[Samsung Galaxy S 4 Unified Development] Max Frost:
What version Magisk manager (app) are you running and what version majisk are you currently rooted with ?
[Samsung Galaxy S 4 Unified Development] :
I have the Magisk Manager 5.3.0 and for the Magisk version, I have v14.0..

So do I have to reflash the Version 22? What can I do please? Thank you!
[Samsung Galaxy S 4 Unified Development] Max Frost:
Yeah those are pretty old. Just download version 22 . Then reboot into recovery and flash it. That will get you synchronized. If you were to just update the manager then it's going to tell you it doesn't work with Majisk versions before 20.4 so just make the jump to version 22 and you'll be good to go.
[Samsung Galaxy S 4 Unified Development] :
Yeah pretty outdated. Thank you very much for this. It's really a big help.
[Samsung Galaxy S 4 Unified Development] bersem:
the first official LOS 18.1 released !

https://download.lineageos.org/jfltexx

Thread:

https://xdaforums.com/t/official-lineageos-18-1-for-the-samsung-galaxy-s4-all-variants.4255313/

thanks @npjohnson
[Samsung Galaxy S 4 Unified Development] droi1:
this is great! hopefully reboot problems are gone :unsure:
[Samsung Galaxy S 4 Unified Development] x2k13:
Just updated, went smoothly. One thing though: How can I set the app drawer's raster seperately to 4 icons in a row with 5x5 on the home screen. I'm sure I did this on 17.1 but can't seem to find it again. Help 🤭

Edit: Nevermind found out. Screen zoom and font size weren't correct. Works now. 😀
[Samsung Galaxy S 4 Unified Development] bersem:
Dirty flash from official 17.1:

Wiped Cache, Dalwik ART Chache, System rebooted to TWRP:

1. Flashed LOS 18.1

2. OpenGapps

3. Magisk

Everything works well for now.

Regards !
[Samsung Galaxy S 4 Unified Development] x2k13:
I just noticed the screen recorder is gone from the recorder app, just audio? Did I miss something?
[Samsung Galaxy S 4 Unified Development] kurtn:
Quick settings tile?
[Samsung Galaxy S 4 Unified Development] x2k13:
Yes! Thanks. 🙂
[Samsung Galaxy S 4 Unified Development] massinius:
can I install edxposed in this room?

Can someone give me information
[Samsung Galaxy S 4 Unified Development] npjohnson:
please don't quote the OP, I have no clue, and can't support XPosed due to the fact it changes system behavior.
[Samsung Galaxy S 4 Unified Development] massinius:
Thanks for the information
[Samsung Galaxy S 4 Unified Development] johnmaster:
.

Old man now I am the one who will get you out of doubt. I have a recovery compatible with all the s4 that is installed by odin, I will leave it in the description, but I will also teach you how to convert the recovery.img that are only installed behind a recovery; for you to install it from Odin. The name of the program is: (Tar tool). Okay

Steps:

1) download Tar tool

2) the recovery that you have TWRP whatever, you will rename it to: recovery.img

3) now the recovery.img already renamed, it will move it into all the program files (tar tool)

4) already moved, it will touch the tar tool file called: imgToTar.MD5 and it will automatically create a recovery.tar ready to be flash by odin.

A copy of the original recovery will also be created called: recovery.back

To get it back to how it was, just rename it (back) to .img, it will look like recovery.img.

Ready I hope it works for you
[Samsung Galaxy S 4 Unified Development] Savatage76:
hello!
[Samsung Galaxy S 4 Unified Development] sjamie:
It is great that this aged yet capable device is still being supported! 🤙🏽
[Samsung Galaxy S 4 Unified Development] Fastback65:
Hi,

I have a galaxy S4 I9515 and i was wondering with what baseband version this lineage best work. I came from "I9515XXU1BOC3" and i updated it to newest "I9515XXS1BQD2".

Before i had alot mobile internet connection problems and now alot gps problems.

What baseband should i have?

I9515XXU1BOJ3 or something?

I am from belgium.

Thanks in advance

Tim
[Samsung Galaxy S 4 Unified Development] npjohnson:
newest
[Samsung Galaxy S 4 Unified Development] Fastback65:
Oke so my "I9515XXS1BQD2" should be fine then.

Thanks for reply.
[Samsung Galaxy S 4 Unified Development] Chase Whittemore:
Anyone have a link to 17.1? When i click on the original link it goes to 18.1.
[Samsung Galaxy S 4 Unified Development] pocketrule:
Talking about official lineageos builds: whenever there's a new version (here: 18), the former one is stopped (here: 17)
[Samsung Galaxy S 4 Unified Development] Chase Whittemore:
That's unfortunate. I was looking for a stable Android 10 ROM.
[Samsung Galaxy S 4 Unified Development] kurtn:
LineageOS 18.1 is stable enough. Maybe you can find unofficial 17.1
[Samsung Galaxy S 4 Unified Development] testerS4:
I also installed 18.1 on my i9515, with Magisk, LSPosed, GravityBox ...

It goes so far without errors.

However, I have to say that the performance has decreased. The delays in starting apps are already noticeable.

The processor probably reaches its limits with Android 11. The jump from 6 to 11 is also huge.

Nevertheless, thanks to the developers.

The i9515 is updated almost weekly and the latest security updates are included.

(sorry for Engl ... I use translators)
[Samsung Galaxy S 4 Unified Development] blaze2051:
here you go last of the A10 stable for the Tmobile variant

lineage-17.1-20201112-nightly-jfltexx-signed.zip | by Humax for Galaxy S4

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

Downloads for : Samsung Galaxy S4 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Samsung Galaxy S 4 Unified Development] HTC_S3:
4g is not working on this rom?
[Samsung Galaxy S 4 Unified Development] npjohnson:
1. 17.1 has been dead for years

2. 4G works fine if it works on stock.
[Samsung Galaxy S 4 Unified Development] Ivan_Meler:
Thread closed as per authors request
[Samsung Galaxy S 4 Unified Development] DerHimmel:
In fact, the screen turns black even when calling and does not light up at the end of the call. Do you have a solution? Thanks

Translated with Google translator I apologize for incorrect words and wrong sentences.
[Samsung Galaxy S 4 Unified Development] kurtn:
Ifixit.org
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
SPH-L720

I decided to do a clean install on my 2nd S4 Sprint variant . Clean flashed 4-04 date , open gapps . Phone boots fine but after booting up to setup it will reboot to recovery after about 10 to 15 seconds . It does this over and over like a cycle. Can't get past initial setup. I then restored my version 16 nandroid and dirty flashed like I did on my other device and it works fine . I suspect this might be a Lineage problem because version 17.1 does the exact same thing on my LG-G3's . The exact same thing in fact except when I dirty flash over the LG-G3's they continue the reboots after 10 to 15 seconds . So the S4's at least continue to work without the reboot to recovery issue . It's almost like reboot issue is some kind of script that reboots it to recovery. When it reboots to recovery if I power the device off from recovery then the device reboots into recovery when I power it back on . If it wern't for the same exact issue with a different Brand of phone and different model I'd suspect this particular build but it's not so the only common denominator is something to do with Lineage source in my opinion. Hope this helps . I am unable to upgrade the LG-G3's at this time because of this issue .
[Samsung Galaxy S 4 Unified Development] kurtn:
Looks like you have various problems. One might be: you let twrp install twrp app before booting into a new installed ROM. That leads to reboot into twrp after a few seconds of boot animation.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Nope , I've been flashing roms for years , I don't ever install the twrp app anymore . I'm not rebooting into twrp after a few seconds of boot animation . It's rebooting to twrp after the rom as a;ready booted up . I think you may be misunderstanding my post . Perhaps it could be twrp on the LG G3 and the S4 that's calling for the reboot , I don't know . Maybe something needs to be updated in twrp for 17.1 . If not I think something common to both the G3 and the S4 in Lineage source could be the problem . Like I mentioned before , two manufacturers doing the same exact thing , different builds , different developers , so it has to be either twrp or lineage source . Neither device can be clean flashed . Iv'e tried many many times . There's one common denominator doing the same thing to both of these (G3) (S4) devices .
[Samsung Galaxy S 4 Unified Development] Exodusnick:
You do a Clean Install when you want to switch from 16.0 to 17.1. To avoid mistakes that you take from 16.0 to 17.1.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Agree with you as I imagine paco does too but if we do clean installs we can't use the rom because of an unknown bug at this time .The only way we can use the rom is to dirty flash .
[Samsung Galaxy S 4 Unified Development] kurtn:
So you search for a common reason. Could it be GApps?
[Samsung Galaxy S 4 Unified Development] Exodusnick:
Yes there is a problem with the los server .

Because my build works without problems when I install Clean.

And the los build are not tested before.

They are simply chased through the build server and simply released without testing.

Playing the lottery is what it does.

I test my builds before I release them .
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Tested a reset

Just did a test . On the S4 that's working fine on the dirty flash I wanted to factory reset it to find out if it would boot back up and keep working or if it would revert to rebooting issue we're having with the clean flash . It did revert to rebooting after about 15 to 20 seconds . So now we know with a dirty flash over 16 we are able to use the phone without issue but if we factory reset to a clean state then we wipe out whatever is allowing the phone to work properly and replacing it with whatever the bug is .

---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------

I don't doubt yours works but I think this problem is device specific .
[Samsung Galaxy S 4 Unified Development] Exodusnick:
Where I know all this from

Is that the los team for example no jfvelte (GT-I9515/L) have to test.
[Samsung Galaxy S 4 Unified Development] DerHimmel:
Can you please explain a little better? Thanks
[Samsung Galaxy S 4 Unified Development] Exodusnick:
Mine works .

And I build with the same source as lineage os

And the image also for the normal s4 .
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
I had already tested that theory by flashing the rom without gapps . Still reboots on two Lg G3's and two Samsung S4's exactly the same way . It's definitely a Q related problem with a shared common issue .

---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------

Could it be something in the sprint device tree portion that would be found in both a Sprint LG G3 build and a Samsung S4 build then ?

---------- Post added at 04:11 PM ---------- Previous post was at 03:56 PM ----------

I'd be happy to test your build if it works with the JFLTESPR . I have a gut feeling it will likely do the same thing though .
[Samsung Galaxy S 4 Unified Development] Exodusnick:
I don't have the JFLTESPR device. I only build for devices that I really own and not like lineageos .

Have fun with your official lineageos builds :laugh:
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Yes, I know that best way to upgrade from an older ROM is to clean flash the new one. I did this with one of my S4 (i9505) - but failed (like for many others, too - escpecially with TWRP). Since I have no experience with LOS recovery and because of missing backup functionality, I decided to stay with TWRP). With my second S4, an i9515 VE, I then decided to do a dirty flash. Problems so far occurs with Frefox Klar (aka Firefox Focus) and Vivaldi Beta: sometimes freezing for both apps. Bluetooth pairing with car phone set worked; only bug is that no automatic coupling/pairing is possible, if you turn off and on again (but I don't know, if this is a general problem with Android 10 and not only with this LOS ROM).

Since I've made an backup of LOS 16, it#s no problem for me to go back to v. 16. I think it's normal that some mistakes/failures occur - important is to find a solution for them to overcome. With my thanx again for developpers I hope they go on with their work. Best wishes ... Paco

---------- Post added at 17:47 ---------- Previous post was at 17:37 ----------

Could it be, that the clean install problem with official LOS resulted with Gapps - since I know you concentrated with your builds on microG? (by the way: I used your Build with Los 14 and was very satisfied ! ;)
[Samsung Galaxy S 4 Unified Development] Exodusnick:
---------- Post added at 17:47 ---------- Previous post was at 17:37 ----------

[/COLOR]

Could it be, that the clean install problem with official LOS resulted with Gapps - since I know you concentrated with your builds on microG? (by the way: I used your Build with Los 14 and was very satisfied ! ;)[/QUOTE]

No are equal except that my builds signature spoofing patch is included.
[Samsung Galaxy S 4 Unified Development] qandres12:
Definitely something wrong with the builds.
[Samsung Galaxy S 4 Unified Development] Exodusnick:
Here even my build from 01.04.2020 works. With Clean Install.
[Samsung Galaxy S 4 Unified Development] kurtn:
Your proximity sensor is broken. So try to repair, or at least clean it.
[Samsung Galaxy S 4 Unified Development] qandres12:
I dont have that device. Mines the L720T. Clean install causes bootloops. I think the issue relates to just the Sprint variant.
[Samsung Galaxy S 4 Unified Development] Jervin Clain:
Wow, Very big thanks for all the devs for this! Hope all of you keep making our S4 updated ? thank you all!!
[Samsung Galaxy S 4 Unified Development] adammanson:
Device: Jfvelte (I9515)

Booted into Recovery, LineageOS 16.0 Recovery

wiped Data,Cache and System.

Installed Official LineageOS 17.1, 04-04-2020

Installed OpenGapps Nano, 03-04-2020

and everything works great, except there is one problem.

the Phone freezes randomly, becomes unresponsive for about a minute and then it comes back to normal.

As far as I used it, everything else works greatly (didnt try calls.)

Thanks for all the work
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
When you say bootloop are you saying your phone boots over and over from the LG screen back to the LG screen ? Mine is the L720 but it boots up successfully but then after about 20 seconds it restarts . Is that what yours is doing ?
[Samsung Galaxy S 4 Unified Development] qandres12:
When I try adb sideload I can only install the rom. Afterwards, the device isnt recognized by adb anymore to install gapps and magisk so those arent even installed. I make sure to factory reset/wipe system. Devices then boots up to the set up screen and I start putting in the WiFi login and then device shows a window saying "powering off". It tries to boot up again and goes to recovery. Lineage recovery tells me the system is corrupted and cant load, do a factory reset. A factory reset causes the same type of boot loop. I can install LOS16 no problem.
[Samsung Galaxy S 4 Unified Development] Exodusnick:
I installed everything via twrp .

I have never installed anything under adb.
[Samsung Galaxy S 4 Unified Development] qandres12:
I havent tried twrp. When I tried to install LOS16 with twrp it would tell me something along the lines that the zip wasnt meant for my device and it would fail to flash.

I'll give it a shot with 17.1 when I get home though. Cant tell you how many times I flashed to stock last night and tried to troubleshoot the rom flash. Clean, and dirty flashing variations.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
I'm flashing with TWRP and it's doing the same thing . You can try it but it's not going to work . We have a bug somewhere and until it's found this will happen . I've also never used adb to sideload anything . I'd wager almost any older legacy sprint device that Lineage is building Q for is having this happen including LG . That's why I think it's something in the source affecting more than this sprint device . I wish I still had my Linux laptop so I could do an adb logcat and then our Dev could see the problem . Do you have a linux laptop that you capture a log ? Maybe something is corrupting and that's why it's powering down and kicking us back to recovery ?