[ROM][GT-I9506][ks01ltexx] LineageOS 17.1 UNOFFICIAL for the Galaxy S4 LTE-A

[DualJoe]

The implementation itself could be buggy. No one knows which side effects are involved. The safest way is to not enable it at all in the first place. It already starts with the kernel cmdline.
I hope this issue is done in 1-2 weeks (or next release) anyway. I have no plans to keep this patch alive. It will be merged or not.

Is your app able to verify oom's? Maybe SystemUI (and other system apps) are not in the right class.

 

[DiamondJohn]

The implementation itself could be buggy. No one knows which side effects are involved. The safest way is to not enable it at all in the first place. It already starts with the kernel cmdline.

Using boot scripts enable the whole systemless thing and also can survive a dirty flash or Magisk update. I have been using a script similar to the above for over 5 years across multiple devices and android versions / ROMs.

I hope this issue is done in 1-2 weeks (or next release) anyway. I have no plans to keep this patch alive. It will be merged or not.

I wouldn't hold your breath, once ZRam gets into a device, it usually stays. And hence I have been using boot scripts for so long.The device I used when ZRam was first introduced into Android would be completely unusable due to extreme lag in absolutely EVERYTHING. Note, with swap, you have many settings to adjust how it is used by the OS. On / Off is not your only choice.

Is your app able to verify oom's? Maybe SystemUI (and other system apps) are not in the right class.

OOM has to do with processes being killed due to Out Of Memory. I think you would be best to consider Nice, which is thread priority. And possibly also look at the IO nice. And yes, my app handles all three.:good:

 

[DualJoe]

Thanks for your explanations. I'm sure the problem will be solved soon.

 

[HasankaSanjana98]

Works fine with The Korean Galaxy S4 LTE-A (SHV-E330S/K/L)Korean

Thank you so much.

 

[DualJoe]

Here is the patch to disable zram.

I'm not all too convinced this is the final solution. It got better at best but it's still there. I played with minfree settings as well. Lower values get worse, higher values don't change anything. I will create some systraces next.

 

[DiamondJohn]

I'm not all too convinced this is the final solution. It got better at best but it's still there. I played with minfree settings as well. Lower values get worse, higher values don't change anything. I will create some systraces next.

I saw/see the lag on my Oeo ROM qwhen pulliung down the quick settings. I *think* I tried messing with ZRam and that didn't stop it. The difficult point was that the lag was not always happening, so any change would require giving it a few days before I could say it was definitely gone. And from memory, ZRam did not do it. I *think* I also tried messing with Nice values (ie thread priority) of the System UI thread, and that didn't fix it either. The convuluting factor is that because it does not happen every time, a change does not necessarily mean you actually fixed it.

 

[Mikhail Korolev]

Could someone please check if it is possible to get a lock on glonass satellites with this ROM?

 

[kyasu]

lineage-17.1-20200607-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).
Sync with the latest LineageOS source (June 2020 Security Patch).
Disable ZRAM and ZCACHE.

Changes:
https://github.com/kyasu/android_device_samsung_ks01ltexx/commits/lineage-17.1
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-17.1

 

[DiamondJohn]

Could someone please check if it is possible to get a lock on glonass satellites with this ROM?

I have tried many ROMs for the S4, and I only once got a connection to a GLONASS satellite using some stock samsung firmware (cant remember which one). All the ROMs I have tried including LOS, can see the GLONASS sats, but do not use them for a fix.

I had a similar issue with my previous phone (basically a moto XT907). It could see the GLONASS satellites, but did not use them for a fix. I thought it may of been a USA-Russia thing, but my mother has a new phone and it connects to GLONASS as well as a few more.

 

[Kryga-i9506]

Need your help (Solved)

Hello, i got a second GT-I9506 and installed this build following the instructions.

- twrp-3.3.1-1-ks01ltexx.tar did not boot to recovery
- used twrp-3.3.1-0-ks01lte.img.tar instead of

My GT-I9506 does not boot system. On startup only the logo appears and one yellow line at top of the screen. This line reads "Set Warranty Bit : kernel". That status does not change; waited more than 30 minutes.

I tryed flashing again, but the error remains.

Found that format data gives error
E:Unable to wipe '/data' -- unknown file system 'auto
Unable to format to remove encyption.



Update1 2020-06-13 16:00:
Managed to install stockrom I9506XXUDOK2_I9506TNZDOK1_I9506XXUDOJ3_HOME.tar.
My GT-I9506 ist now booting to stockrom.

Update2 2020-06-13 14:20:
Solved
With stockrom from Update1 i could install twrp-3.3.1-1-ks01ltexx.tar and boot to it.
From there i could install lineage-17.1-20200607-UNOFFICIAL-ks01ltexx.zip and open_gapps-arm-10.0-pico-20200612.zip.
My GT-I9506 ist now booting this build.

 

[fichatel]

Hello,
Because of a unresolved problem for sending MMS with an older version, i decide to try a fresh install with this last 17.1 release.
I was previously using a v14.x version, and there where some fine applications permissions configuration features. For example,
I could avoid some apps starting after system start, or prevent some apps running in background. It was great to save battery.
It was available in Confidentiality menu.
Did this disappear in Lineage os 17 ?

 

[Kryga-i9506]

Hello,
Because of a unresolved problem for sending MMS with an older version, i decide to try a fresh install with this last 17.1 release.
I was previously using a v14.x version, and there where some fine applications permissions configuration features. For example,
I could avoid some apps starting after system start, or prevent some apps running in background. It was great to save battery.
It was available in Confidentiality menu.
Did this disappear in Lineage os 17 ?

I am not yet allowed to post links; so try google with "how-do-i-stop-apps-from-auto-starting-on-android"

 

[NoxCivi]

lineage-17.1-20200607-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).
Sync with the latest LineageOS source (June 2020 Security Patch).
Disable ZRAM and ZCACHE.

Thanks kyasu, this Build runs pretty stable. I had random Wifi/BT errors with the previous one.

 

[[email protected]]

So, after using this rom for a while as my daily driver, here is my takeaway:

• Most stuff works fine
• Issues with the SD Card:
  • Can't use it for adopted storage:

    Attempt to invoke virtual 'method java.lang.String android.os.storage.VolumeInfo.getId()' on a null object reference

  • When using it as an external storage, any app that uses the storage access framework fails to write files on the SD card (they can create folders, create files, but these will be 0B). Apps not using the SAF (writing to data/) are fine. Example: try copy/pasting with Material files or the LineageOS file manager, taking a picture with Open Camera.
  • Same issue with the LOS "snap" camera as everyone else: it saves files under data/ thus they do not appear in the gallery. The app can't open them either. But at list it saves them I use Simple gallery pro to view the files.
• Deterministically crashes in specific applications (I confirm that disabling SELinux with setenforce 0 doesn't fix it), logcats at cloud.mayeul.net/s/7YPoRH9JiiY7r5C (sorry for my upload speed, it'll get better in ~december):
  • Mozilla stumbler, when uploading results
  • Open Camera, when taking a HDR picture, or saving a panorama
  • Possibly others, that I don't recall now.
• I couldn't unlock carrirs using this ROM
• GPS fix is quite slow to obtain (not using NLP)
• Compass is quite unreliable

The above issues are with version 200501. Not sure if fixed with a later version, I will upgrade and edit. Zram was working fine for me, I'm sad to see it leaving

I will see if I cannot mainline the kernel, if I have time to do so.

Coming from LOS 15.1 I noticed my SD card formatted with F2FS is no longer recognized. Neither the twrp-3.3.1-1 recovery nor the 17.1 system seem to support F2FS on external (=real) SD cards.
Is this a bug of this ROM or a dropped feature in LOS 17.1?

Well, formatting the SD card to f2fs on my computer and inserting it works, I can read/write it, with the caveats listed above.

 

[f.a.tonmoy]

Magisk, Xposed, and Substratum.
Do these things work properly?

 

[[email protected]]

Magisk, Xposed, and Substratum.
Do these things work properly?

Magisk works fine (I mostly use it for the F-droid privileged extension that doesn't work as-is on Lineage 17.1), I haven't tested the others.

 

[f.a.tonmoy]

I'm getting This "set warranty bit: kernel" error.
how to fix this without going back to stock?

 

[DiamondJohn]

I'm getting This "set warranty bit: kernel" error.
how to fix this without going back to stock?

Is this the flag displayed on the bootloader screen, notifying you that you have unlockled your bootloader? if so, then it is not an error.

 

[f.a.tonmoy]

Is this the flag displayed on the bootloader screen, notifying you that you have unlockled your bootloader? if so, then it is not an error.

Yea I got that.
While I was on Nougat, I used amplify, powernap ta boost battery life.
What should I do on Android 10?
battery drains quite a lot on standby.
Currently just underclocked the CPU and installed naptime.

 

[DiamondJohn]

Yea I got that.
While I was on Nougat, I used amplify, powernap ta boost battery life.
What should I do on Android 10?
battery drains quite a lot on standby.
Currently just underclocked the CPU and installed naptime.

Look into:
https://forum.xda-developers.com/showthread.php?t=1179809

And also at your doze
https://forum.xda-developers.com/showpost.php?p=82064461&postcount=264