yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] DiamondJohn:
That was perfect:good:, from my weak (and cautious) understanding, the SELinux statements (FYI) that came from your logs (I have an automated excel spreadsheet to convert them, with Notepad++ to extract them from the multiple files) provides the following. The green are possibilities, the blue look good to me at first glance, the red are suspicious where some app is trying to possibly do a little more than it possibly should be allowed to do, but is (under permissive). However, disallowing (ie switching to enforcing) may break the apps functionality. A lot of the un-trusted app issues were triggered by Jelly (ie the browser), which I was surprised is registered as untrusted. But I guess it only asked for read and get attribute, not write, delete or exec.

[COLOR="Green"]allow mpdecision mpdecision:capability { sys_ptrace };[/COLOR]
[COLOR="DarkOrange"]allow shell spcomlib_prop:file { getattr };
allow shell spcomlib_prop:file { open };
allow shell vendor_rild_libpath_prop:file { open };
allow shell wcnss_prop:file { getattr };
allow shell wcnss_prop:file { open };
allow shell wififtmd_prop:file { getattr };
allow shell wififtmd_prop:file { open };
allow shell wififtmd_prop:file { read };
[/COLOR][COLOR="DarkSlateBlue"]allow system_app installd:binder { call };
allow system_app netd:binder { call };
allow system_app storaged:binder { call };
allow system_app wificond:binder { call };[/COLOR]
[COLOR="Red"]allow untrusted_app proc:file { getattr };
allow untrusted_app proc:file { open };
allow untrusted_app proc:file { read };
allow untrusted_app_25 kgsl_debugfs:file { getattr };
allow untrusted_app_25 kgsl_debugfs:file { open };
allow untrusted_app_25 kgsl_debugfs:file { read };
[/COLOR]
[Galaxy S 4 i9506 Android Development] wkwk:
I have it set to enforcing via magisk script, everything is working fine.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
from what I have heard, there is a lot of disagreement if it is really running enforcing. A lot of Magisk is about reporting something different to what is actually the case (eg hiding root from apps). ie it may be reporting its running enforcing, when in reality its still running permissive. Simply because there are denials, does not necessarily mean that you would notice anything. However, it begs the question how you are not noticing any issues; unless its actually running permissive (nothing different implies nothing changed). If there are no expected issues, I would of also expected the dev to switch to enforcing as well in his build, which he hasn't. Suspicious.:eek:

Something that came to mind as a possible test that I would personally do is, ViperFX is known for only working in permissive status; if the correct adjustments to SELinux policies are NOT made either in the kernel or as a bootscript/Magisk module. So, I am thinking, if ViperFX (not installed via Magisk, but as a standard app) can be run in permissive mode on the ROM, but stops working as soon as you use Magisk to switch it to enforcing, then chances are (after checking the logs) that it actually does change the SELinux mode.:confused: Not simply reporting back that its enforcing, when it is not. Not 100% definitive, except for the failure case I guess (which is what you wish to prove ie it stops when Magisk is set to enforcing, but works in permissive), but, i think its a reasonable test due to its ease. That is if you know the correct steps to install Viper as a standard app without a Magisk module.
[Galaxy S 4 i9506 Android Development] tester_95:
Recording video works not only in Footej Camera but also in the Google Camera (ver. 4.1.006 and olders) if you previously change the quality from 1080p to 720p.
[Galaxy S 4 i9506 Android Development] :
Thanks for the tip. I tried a lot of camera apps, but no luck (except footej, which is a very good app anyway). But it's always good to have options to choose from.
[Galaxy S 4 i9506 Android Development] kyasu:
Currently, I don't use any repopicks. I only use the attached my patch.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
hmmm... :confused: ... I haven't tested my build (of crDroid) but there appears to be at least one explicit repopick for the GPS (or uncommited code)

#GPS Fixes
repopick 208723 -f -P device/samsung/msm8974-common/ # GPS Fixes commit 399e9af https://github.com/LineageOS/android_device_samsung_msm8974-common/commit/399e9af90aa328a4e634e19d8669b25359cc4069

This repopick changes (among other things) the new gps.conf file, as confirmed a few posts up, which is different to what is in your source on guthub.:confused:

NB:I am building crDroid from your device tree, so I appear to need to force it to the correct project

I also went through the changes on LineageOS device version, and also added the following. I don't know if they are ok to bring in, but it builds.

#GPS Fixes
repopick 208723 -f -P device/samsung/msm8974-common/ # GPS Fixes commit 399e9af https://github.com/LineageOS/android_device_samsung_msm8974-common/commit/399e9af90aa328a4e634e19d8669b25359cc4069

# android-o-mr1-camera-hal1-lineage-15.1
repopick 206426 -f -P vendor/lineage # soong_config: Add TARGET_HAS_LEGACY_CAMERA_HAL1 variable
repopick 206427 -f -P frameworks/av # camera/media: Support for legacy camera HALv1
repopick 206428 -f -P system/sepolicy # Add rules required for TARGET_HAS_LEGACY_CAMERA_HAL1

# msm8974-common:sepolicy (appears now/already merged into source)
repopick 210314 -f -P device/samsung/msm8974-common/ # msm8974-common: sepolicy: Resolve misc denials
repopick 209588 -f -P device/samsung/msm8974-common/ # msm8974-common: sepolicy: Allow mediaextractor r_file_perms to fuse:file

Anyway, don't concern yourself too much at this stage, except maybe the GPS issue.;)
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180407-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source (April 2018 Security Patch).

Changes:

https://github.com/kyasu/android_device_samsung_ks01ltexx/commits/lineage-15.1

https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-15.1
[Galaxy S 4 i9506 Android Development] Raitsa:
Hey guys.

I got the 10.3.2018 version installed and working smoothly but whats the recommended way to update to the latest build?
[Galaxy S 4 i9506 Android Development] jegogo99:
I have signal problems with last build. I'll try it again making clean install

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] tester_95:
Flashlight does not work after the last upgrade.
[Galaxy S 4 i9506 Android Development] :
Everything working fine here. Also AudioFX is suddenly working, who knows why :laugh:
[Galaxy S 4 i9506 Android Development] jegogo99:
Working fine to me

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] tester_95:
Now it works for me when I did downgrade :)

---------- Post added at 03:23 PM ---------- Previous post was at 03:18 PM ----------

AudioFX works me only with AIMP :)
[Galaxy S 4 i9506 Android Development] :
AudioFX has never worked for me with this rom. But with the latest build it works for Spotify (and therefore also with most other players I guess). I really like the app and prefer it over viper and other equalizers. :good:
[Galaxy S 4 i9506 Android Development] xeta1122:
My baseband always unknown every 2 or 3daysand my wifi also always disconnected . . .did i need to downgrade to what version?. . My phone is Korean Variant E330S . . TIA guys
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Is it the simplicity/spartan nature (ie just get the job done with no fuss) or do you actually prefer the sound?
[Galaxy S 4 i9506 Android Development] wkwk:
The screen wake delay increase I felt existed in the last build has now gone back to what it was previously. Again this is what I perceived, could very well be placebo.
[Galaxy S 4 i9506 Android Development] marcinadd:
I had seen on changelong and I didn't find something about NFC changes, so Google Pay doesn't work as before, Right?
[Galaxy S 4 i9506 Android Development] tsuippa:
gps will no longer work

The latest update, the gps will no longer work. The first version worked best on gps and after that it has had to wait 5-10min to find the positioning. The latest update did not even find the positioning for 15 minutes in anticipation.
[Galaxy S 4 i9506 Android Development] pawpawel:
when you connect, you can not see who is calling, the image disappears !!
[Galaxy S 4 i9506 Android Development] jegogo99:
I,m using 20180113 build. For me it's the most estable for now if you install oficial gapps

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] kyasu:
lineage-15.1-20180414-UNOFFICIAL-ks01ltexx.zip

New build is available (See the first post).

Sync with the latest LineageOS source.

Video recording is working but has some dropped pixels on the right of the frame (vertical stripes)

Changes:

https://github.com/kyasu/android_device_samsung_ks01ltexx/commits/lineage-15.1

https://github.com/kyasu/android_kernel_samsung_msm8974/commits/lineage-15.1
[Galaxy S 4 i9506 Android Development] lospuegos:
:laugh::fingers-crossed:
[Galaxy S 4 i9506 Android Development] wkwk:
Google pay is working with previous version.

Hi all, just thought I'd let you guys know that I was able to use google pay with rom dated 7th April. Yet to try with latest version (haven't upgraded to latest rom).

Steps taken -

1. Launch Google pay

2. Press home button, send app to background

3. Lock phone with power button

4. Wake phone, take it near POS terminal.

Thereafter I tried again without relaunching the app/sending to background and it still worked.

Thanks Kyasu, this rom is brilliant. Breathing new life into a 6 year old phone- blows everyone's mind this device is current and at peak performance even today.
[Galaxy S 4 i9506 Android Development] pawpawel:
Call you normally nothing disappears?
[Galaxy S 4 i9506 Android Development] ravindu20000:
Please make stable for Korean S4 SHV-e330
[Galaxy S 4 i9506 Android Development] wkwk:
I have an shv e330s, I don't have any issues using this rom. Barring a delayed splash screen and rare multiple boots at the splash screen (1 bootloop cycle before it boots normally) .
[Galaxy S 4 i9506 Android Development] k3mot:
hello, I have a question which versions of gaaps should be downloaded, because ARM can not be downloaded from first post :/ x86 versions? I ask becasue i9506 is an ARM platform.
[Galaxy S 4 i9506 Android Development] :
You have to download arm version. Why can't you download the zip? The website does not appear to be out of service for me.
[Galaxy S 4 i9506 Android Development] k3mot:
Now it's Ok :) thanks :) earlier i can't download it :(
[Galaxy S 4 i9506 Android Development] pawpawel:
http://opengapps.org/?api=5.1&variant=nano
[Galaxy S 4 i9506 Android Development] DiamondJohn:
When I have had issues with some sites not being available, I have found using the TOR browser will often work around it. I also have a vague memory of being able to download the latest builds from their Github project; sorry, but I don't have the links for that, just a vague memory of its possible existence.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Favor, check gps.conf file contents

For anyone running the latest build lineage-15.1-20180414-UNOFFICIAL-ks01ltexx.zip, could you please let me know if the /system/etc/gps.conf file has the following first line:

#Uncommenting these urls would only enable

or this as the first line.

XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin

or something else completely?:confused:
[Galaxy S 4 i9506 Android Development] supachris:
The urls have to be commented out with # otherwise the assisted gps will not work. This was a generic change in 15.1

Nevertheless you can modify the timestamp server urls to your nearest in order to get quick gps fix.
[Galaxy S 4 i9506 Android Development] :
I have the second line in my gps.conf (XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin).
[Galaxy S 4 i9506 Android Development] DiamondJohn:
And thats why I asked, as the device tree for our device was specifically changed to revert the commit, with different URL source values than was previous used.

You can see the history at https://github.com/kyasu/android_device_samsung_msm8974-common/commits/lineage-15.1/gps/etc/gps.conf NB: Other associated files / code were also changed in combination to make it work, not simply this one single file. Changing the one single file would be expected to negatively affect your GPS functionality. The following shows the group of changes that went in together to make the new values work as a whole. https://github.com/kyasu/android_de...d78fc41#diff-b95972a09ea19f5e627e357f184e76c4
[Galaxy S 4 i9506 Android Development] supachris:
Strange. I use my own gps.conf file (with commented out the xtra servers) and overwrite the file after each update. This works since the change and I get GPS fix in a few seconds. With kyasu´s gps conf the a-gps is not (properly) working, the fix takes at least two minutes.
[Galaxy S 4 i9506 Android Development] kyasu:
Hi, I'm currently using the lineageos msm8974-common tree. See: https://github.com/kyasu/android_de...mmit/a0f4c6eae0c17709eb030f77877bf3b961a7fe69
[Galaxy S 4 i9506 Android Development] darkness:
thank you :good:
[Galaxy S 4 i9506 Android Development] DiamondJohn:
:good:Thanks, that would explain my confusion, at least help a little... :o And from memory, I also including some extra commits from that branch; which would help confirming I guessed right to include them.
[Galaxy S 4 i9506 Android Development] nhihoppro:
LTE A e330L stuck logo SS bootloop
[Galaxy S 4 i9506 Android Development] eccko:
Hi, Gapps work ?
[Galaxy S 4 i9506 Android Development] Mickeyvdb:
Same happened to me.

After cooling down a bit after flashing was done, rebooting was ok.

At least that worked for me.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I am not running Oreo myself as a daily, with one of the reasons being that I haven't explicitly seen Substratum working on the Oreo ROMs for our device, and I always thought it was not even enabled in pure LOS.

However, in your attached image, it appears you have some dark theme installed; I am assuming the screenshot is part of the default setting's app, which I would of expected to have a white background:confused:.

Did you need to do anything to enable this dark theme? or is the feature built into LOS Oreo?
[Galaxy S 4 i9506 Android Development] darkness:
the feature built into LOS Oreo I USE black wallpaper
[Galaxy S 4 i9506 Android Development] :
It's build in. You can choose system accent color and a light or dark theme. However substratum works too.
[Galaxy S 4 i9506 Android Development] derflasher:
I recently flashed this ROM - amazing! Thanks kyasu! You do a fantastic job!
[Galaxy S 4 i9506 Android Development] Vickeey:
Thanks KYASU for this Awesome ROM
[Galaxy S 4 i9506 Android Development] pawpawel:
does my screen go off during calls? and you can not see anything? some advice
[Galaxy S 4 i9506 Android Development] supachris:
After some time my Bluetooth connection to the car stereo drops and some time later the "Bluetooth" system app is being closed and no BT is available until reboot. Does anyone have this issue too?
[Galaxy S 4 i9506 Android Development] jegogo99:
Bluetooth works fine for me with last build when I connect to car stereo

Enviado desde mi GT-I9506 mediante Tapatalk
[Galaxy S 4 i9506 Android Development] wkwk:
Happened to me once till now. I cleared Bluetooth app memory and rebooted, hasn't happened since.
[Galaxy S 4 i9506 Android Development] pawpawel:
when making connections, the image disappears, how does someone else repair it?
[Galaxy S 4 i9506 Android Development] ONjA:
Hi, I've got kernel compilation error for linage 15.1:

I build using command:

Does anyone know how to fix these errors?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I haven't built LOS for this device in a while, but have built it for a number of devices (although previously 14.1 for the other devices and 15.1 for this device) and do a build of Oreo crDroid (LOS based). Post your Local Manifest, or compare it to mine; and be sure to tell me if you think I have something wrong. Mine appears to work with crDroid.:good:

My build steps are very different to yours (and are possibly not the best or simply wrong) but they work and are a carry-over from all the previous ROMs I have built, successfully, including for two other devices and also for 4+ different ROMs.

The below is a bare bones of the steps I *think* I took building LOS successfully. I have also attached my Local Manifest for your reference. Obviously I have the source in ~/android/lineage and do a repo sync before each build wiping / resetting any local code changes I have made. ie The repo stuff is totally optional.

I Hope this helps. NB: [MENTION=4861355]kyasu[/MENTION] has switched back over to the LineageOS tree for one of the device sources. ie its different than whats in the OP.

cd ~/android/lineage/;

repo forall -c git reset --hard;
repo forall -c git clean -fdx;
repo forall -c git checkout -f;
repo sync -fc --force-sync --force-broken --no-clone-bundle --no-tags;

source build/envsetup.sh;
lunch lineage_ks01ltexx-userdebug;
make clobber;
croot;
brunch lineage_ks01ltexx-userdebug;

Feel free to tell me here if I am doing anything wrong or questionable.:D

---- edit

I just remembered this readme kyasu pointed me to.

https://github.com/kyasu/android_device_samsung_ks01ltexx/blob/lineage-15.1/README

FYI i get >75000 steps on the build
[Galaxy S 4 i9506 Android Development] ONjA:
Thanks for reply, but I only need to build kernel, not the whole LOS system from this repo:

https://github.com/kyasu/android_kernel_samsung_msm8974

This repo has build_kernel.sh in its root, which is a build procedure. We put configs there and run.

I had no problem to build kernel in times of CM13, but now these errors appear. Googling says I am not the only one, but I found no solution.
[Galaxy S 4 i9506 Android Development] achlys75:
Just a quick 'Thank you!'

The build works perfectly and smooth.

I just switched from the old official 14.0 builds and made a complete reinstall to these builds and everything worked fine.
[Galaxy S 4 i9506 Android Development] eccko:
After install system and gapps, I try to open google store and stuck on " services google store stopped working " any solution ?
[Galaxy S 4 i9506 Android Development] DiamondJohn:
I once tried to build only the kernel (Nougat for another device) and it came up with a compile error on the source code, even though compiling the whole ROM I had no compile errors, which of course included the same Kernel source code:silly:.

Although a lot more than needed, what I have done to get the kernel is to simply build the whole ROM, but only use the boot.img file. From memory someone used the technique to apply my Nougat kernel included in my RR ROM against a LineageOS ROM. I know it does brings in more than the kernel itself, but at least I could update the kernel (added cpu govs and IO schedulers) without flashing the whole ROM, and having to re-initialise all my apps or system settings/changes etc. ie the ROM stays fixed.

You may also like to try to get help from the threads:

[GUIDE][COMPLETE] Android ROM Development From Source To End

[REFERENCE] How to compile an Android kernel

[Tutorial] Building Your First Kernel

---------- Post added at 11:03 AM ---------- Previous post was at 10:55 AM ----------

To know what is actually going on, on your phone, since no-one else appears to be having the same issue, take a logcat, and place it on a site like www.hastebin.com
[Galaxy S 4 i9506 Android Development] eccko:
Okay, here is logcat http://pastebin.pl/view/325cc424 and here https://4programmers.net/Pastebin/8693
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Which GApps did you install? version and date.
[Galaxy S 4 i9506 Android Development] KonC13:
Random reboot

Hi, everything is great in this rom but i have some random reboots on my device , anyone to help?
[Galaxy S 4 i9506 Android Development] eccko:
22 april 2018 .. I downloaded and install from here http://opengapps.org/ i pick ARM, 8.1 and pico.
[Galaxy S 4 i9506 Android Development] marcinadd:
Try to wipe system before flashing.
[Galaxy S 4 i9506 Android Development] eccko:
I'm not idiot. I do full wipe before flashing los 15.1
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Have you by any chance encrypted your device? Your logs appear to indicate such. If so, maybe try without encryption.:confused:

E AndroidRuntime:[COLOR="Red"] FATAL EXCEPTION[/COLOR]: highpool[0]
E AndroidRuntime: Process: com.google.android.gms, PID: 23677
E AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String[] com.google.android.gms.org.conscrypt.NativeCrypto.get_cipher_names(java.lang.String) (tried Java_com_google_android_gms_org_conscrypt_NativeCrypto_get_1cipher_1names and Java_com_google_android_gms_org_conscrypt_NativeCrypto_get_1cipher_1names__Ljava_lang_String_2)
E AndroidRuntime: at com.google.android.gms.org.conscrypt.[COLOR="DarkOrange"]NativeCrypto.get_cipher_names[/COLOR](Native Method)
E AndroidRuntime: at com.google.android.gms.org.conscrypt.NativeCrypto.<clinit>(:com.google.android.gms@12529046@12.5.29 (090300-192802242):8)
E AndroidRuntime: at com.google.android.gms.org.conscrypt.OpenSSLContextImpl$TLSv12.<init>(Unknown Source:0)

Thats pretty recent so I do not think that is your issue.;)

hey, no-one called you an idiot, he probably was simply to lazy to pre-fix it with "in case you didnt".
[Galaxy S 4 i9506 Android Development] eccko:
I don't encrypt My phone never.. :rolleyes:
[Galaxy S 4 i9506 Android Development] marchnz:
Outstanding standby battery life. Very well done thanks [MENTION=4861355]kyasu[/MENTION]
[Galaxy S 4 i9506 Android Development] DonAndress:
Meaning how long with what usage?
[Galaxy S 4 i9506 Android Development] Andrugz:
How do i install the builds? i tried to flash with TWRP bút it gives me an error
[Galaxy S 4 i9506 Android Development] :
Update twrp and try again.
[Galaxy S 4 i9506 Android Development] DiamondJohn:
Post the actual error text/log.
[Galaxy S 4 i9506 Android Development] Siggi0904:
Hello,

after the information that the developing of 14.1 is stopped I'd like to migrate from LE 14.1 to 15.1.

Is these 15.1 daily usable?

How can I migrate to 15.1 if I use the LE 14.1 build from kyasu?

I'd like to get a stp by step. I'm not 100% familar with all these tools and steps.

Great thanks.
[Galaxy S 4 i9506 Android Development] supachris:
Yes, I use it as daily driver. Except the video recording bug and the wakeup delay there are no issues so far.

You have to do a clean install.

Wipe all data and upgrade with twrp. Do a backup before. You can also use Titanium backup for backup your apps and data in 14.1 and restore in 15.1

---------- Post added at 09:14 PM ---------- Previous post was at 09:14 PM ----------

Is the ChromeCast working with this ROM? I want to buy one...
[Galaxy S 4 i9506 Android Development] wkwk:
Yes.
[Galaxy S 4 i9506 Android Development] najdv:
Still problem with whatsapp (micro)

With all lineageos version 14.1 and 15.1 I always have a problem with the microphone when I use whatsapp. And it does not come from my phone because I delivered the official lollipop 5.0.1 rom and my microphone is working properly and my contacts tell me that he hears me very well so that confirms that it is a concern with your rom. Thank you
[Galaxy S 4 i9506 Android Development] :
I don't have this problem. So you can't simply blame it on this rom.