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

bintoito

Member
Nov 2, 2010
21
1
0
hi guys,
how do I root this version...? really sorry for the noobness, but my quick searches just returned me what I think are "false" results...
 
Feb 18, 2020
3
0
0
Not stable yet

Lineage 17 is quite buggy on ks01ltexx, so I will switch back to 16 for a while.

Some of my experiences are (in 7 days):
- System hang for 2 or 3 seconds when pulling down the status bar.
- System hang for ~2 seconds when lowering or raising the volume.
- If you lower or raise the volume YouTube or any other media playback (video, music) will lag and the system will hang for ~3 seconds.
- Some of the apps you opened will disappear in the recent apps menu but when you launch them again from your home menu then they will reappear.
- Android's stock keyboard takes ~2 seconds to pull up for you to start writing, and in the mean time the system will hang.
- Rarely, when you open any app the system will hang (happened rarely).

Regards to all the hardworking devs! <3
 

Alienns

Senior Member
May 13, 2013
137
25
0
Belgrade
Installed, latest Modem, Latest TWRP - Full wipe than installed lineage-17.1-20200221. For now it`s working very good. No keyboard lag or any major lag. For now i`ll use without gapps :) Got other source for new apk-s.
 

Thisu

Senior Member
Mar 3, 2016
79
20
0
Anyone noticed that "Home Settings > Hidden & Protected Apps" is not accessible?
Fixed!

And the OS feels much smoother now..

---------- Post added at 05:30 AM ---------- Previous post was at 04:41 AM ----------

lineage-17.1-20200307-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).
Sync with the latest LineageOS source (March 2020 Security Patch).
SELinux is enforcing.

Changes:
https://github.com/kyasu/android_device_samsung_ks01ltexx/commits/lineage-17.1-test
https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-17.1-test
Got an issue! The internal storage is no longer accessible within the Android System ?

Could this be due to selinux enfircing?
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,498
3,557
243
Sydney

Thisu

Senior Member
Mar 3, 2016
79
20
0
I have not flashed the ROM, But to check for SELinux denials, you can see these in a LogCat

To avoid having to type into ADB etc. I have added the feature to the following app I build.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260

You can find the SELinux logs within the menu, under:
Logcat>Logcats>Filter By Level>Logcat - SELinux
That was the exact issue, It was fixed after setting SELinux to permissive.
 

Thisu

Senior Member
Mar 3, 2016
79
20
0
If you post the log, you may assist the dev fix it.
HTML:
 03-08 18:26:48.789  6051  6051 W Binder:6017_4: type=1400 audit(0.0:1249): avc: denied { read open } for name="0" dev="mmcblk0p26" ino=130305 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:media_data_file:s0 tclass=dir permissive=0
03-08 18:27:42.139  6520  6520 W bromite.bromite: type=1400 audit(0.0:1253): avc: denied { getattr } for path="/data/media/0" dev="mmcblk0p26" ino=130305 scontext=u:r:untrusted_app:s0:c141,c256,c512,c768 tcontext=u:object_r:media_data_file:s0 tclass=dir permissive=0
03-08 18:27:43.179  6520  6520 W bromite.bromite: type=1400 audit(0.0:1303): avc: denied { search } for name="0" dev="mmcblk0p26" ino=130305 scontext=u:r:untrusted_app:s0:c141,c256,c512,c768 tcontext=u:object_r:media_data_file:s0 tclass=dir permissive=0
03-08 18:27:47.929  6655  6655 W opjohnwu.magisk: type=1400 audit(0.0:1347): avc: denied { getattr } for path="/data/media/0" dev="mmcblk0p26" ino=130305 scontext=u:r:untrusted_app_27:s0:c89,c256,c512,c768 tcontext=u:object_r:media_data_file:s0 tclass=dir permissive=0
03-08 18:28:15.236  7202  7202 W opjohnwu.magisk: type=1400 audit(0.0:1593): avc: denied { getattr } for path="/data/media/0" dev="mmcblk0p26" ino=130305 scontext=u:r:untrusted_app_27:s0:c89,c256,c512,c768 tcontext=u:object_r:media_data_file:s0 tclass=dir permissive=0
03-08 18:28:17.833  7279  7279 W magisk.bin: type=1400 audit(0.0:1663): avc: denied { read } for name="/" dev="tmpfs" ino=9242 scontext=u:r:untrusted_app_27:s0:c89,c256,c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
03-08 18:28:18.856  7353  7353 W magisk.bin: type=1400 audit(0.0:1665): avc: denied { read } for name="/" dev="tmpfs" ino=9242 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
03-08 18:29:29.903  8195  8195 W magisk.bin: type=1400 audit(0.0:1699): avc: denied { read } for name="/" dev="tmpfs" ino=9242 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
This is the logcat before SELinux was set to permissive.
 

thorti1

Member
Jul 25, 2019
10
3
3
Screen Casting

Is it possible to implement a TV / Screen Casting / Mirroring feature in a new release that works? Thanks for the great ROM.
 

grbgdn

New member
Mar 8, 2020
4
0
1
Guys if you have a problem with GPS, then most likely the reason is poor contact with the gps antenna. Look on youtube video "How to fix your Samsung Galaxy S4 GPS"
This solved the bad signal problem.
Thanks kyasu for the work. I'm still using my S4 with this rom.
 

kyasu

Senior Member
Sep 23, 2012
485
2,219
123
Tokyo
Fixed!

And the OS feels much smoother now..

---------- Post added at 05:30 AM ---------- Previous post was at 04:41 AM ----------



Got an issue! The internal storage is no longer accessible within the Android System

Could this be due to selinux enfircing?
I don't have a such issue.
The internal storage is accessible without any trouble.