[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]

H

hennymcc

Senior Member
Dec 7, 2014
374
1,662
0
Jun 18, 2017 at 11:32 AM
sbecker said:
Same problem for me. Here are my logs. HTH.

Regards and thanks

Sascha

P.S. I did a dirty flash and then went back to version of 25.05.2017.
Click to expand...
Sascha, the same "avc: denied" line is in your log. So the same question to you: did you create the log with the test ROM (lineage-14.1-20170616-UNOFFICIAL-kminilte)?

At least it seems to be the same denial for all with non-working SIM. We have to find out why the fix for it did not work.
 
S

sbecker

Member
Jun 6, 2009
20
7
0
Siegen
Jun 18, 2017 at 11:49 AM
hennymcc said:
Sascha, the same "avc: denied" line is in your log. So the same question to you: did you create the log with the test ROM (lineage-14.1-20170616-UNOFFICIAL-kminilte)?

At least it seems to be the same denial for all with non-working SIM. We have to find out why the fix for it did not work.
Click to expand...
Yes it was 20170616.
 
guntzog

guntzog

Senior Member
May 5, 2016
200
63
0
Jun 18, 2017 at 2:46 PM
Hey, I used @spookcity138 Kernel and the sim detecting bug is fixed and here is why as he replayed to me :
The only reason it "fixes" the sim issue is because I built my kernel with SELinux permissive as opposed to enforcing. The enforcing is what breaks the SIM detection. It is being worked on though as its what I prefer lol.
 

Attachments

A

a-dead-trousers

Senior Member
Jul 28, 2016
220
119
43
Jun 18, 2017 at 2:58 PM
Hi!

Just a small shot on the SIM card issue:
Which baseband version do you all use?
The latest from this source? https://forum.xda-developers.com/galaxy-s5-mini/general/baseband-sm-g800f-t3354355

@hennymcc isn't it be possible to rollout the baseband with the ROM? This way we can rule out a possible difference between your testing environment and that of the other users.

Just for your information:
I'm using the ROM from 15.06.2017 with test9 Kernel of @spookcity138 AND SELinux set to strict. I got no problem whatsoever.
 
guntzog

guntzog

Senior Member
May 5, 2016
200
63
0
Jun 18, 2017 at 3:09 PM
a-dead-trousers said:
Hi!

Just a small shot on the SIM card issue:
Which baseband version do you all use?
The latest from this source? https://forum.xda-developers.com/galaxy-s5-mini/general/baseband-sm-g800f-t3354355

@hennymcc isn't it be possible to rollout the baseband with the ROM? This way we can rule out a possible difference between your testing environment and that of the other users.

Just for your information:
I'm using the ROM from 15.06.2017 with test9 Kernel of @spookcity138 AND SELinux set to strict. I got no problem whatsoever.
Click to expand...
Because @spookcity138 kernel ain't enforcing, and that's what causes the issue as he explained to me.
 
A

a-dead-trousers

Senior Member
Jul 28, 2016
220
119
43
Jun 18, 2017 at 4:10 PM
guntzog said:
Because @spookcity138 kernel ain't enforcing, and that's what causes the issue as he explained to me.
Click to expand...
Yeah, but as I also have mentioned I switched it to strict enforcing and everything is still working. No denials, no SIM problems, no WIFI problems.
And as @hennymcc already checked the logs there has to be a problem with SELinux just on some devices and not all of them. So I thought something might differ and the only easy thing I could come up with was to check the baseband modems. The only other explanation would be a configuration difference. Like the bootloop with the fingerprint scanner I found out by chaning one setting at a time.

Oh, one other thing:
I'm also using Magisk v13 latest Beta. Maybe someone with the SIM card denials could give it a shot and check if this changes anything.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
 
guntzog

guntzog

Senior Member
May 5, 2016
200
63
0
Jun 18, 2017 at 5:31 PM
a-dead-trousers said:
Yeah, but as I also have mentioned I switched it to strict enforcing and everything is still working. No denials, no SIM problems, no WIFI problems.
And as @hennymcc already checked the logs there has to be a problem with SELinux just on some devices and not all of them. So I thought something might differ and the only easy thing I could come up with was to check the baseband modems. The only other explanation would be a configuration difference. Like the bootloop with the fingerprint scanner I found out by chaning one setting at a time.

Oh, one other thing:
I'm also using Magisk v13 latest Beta. Maybe someone with the SIM card denials could give it a shot and check if this changes anything.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
@spookcity138 this is interesting, same problem as you failed kernel tests
 
H

hennymcc

Senior Member
Dec 7, 2014
374
1,662
0
Jun 18, 2017 at 6:28 PM
a-dead-trousers said:
Yeah, but as I also have mentioned I switched it to strict enforcing and everything is still working. No denials, no SIM problems, no WIFI problems.
And as @hennymcc already checked the logs there has to be a problem with SELinux just on some devices and not all of them. So I thought something might differ and the only easy thing I could come up with was to check the baseband modems. The only other explanation would be a configuration difference. Like the bootloop with the fingerprint scanner I found out by chaning one setting at a time.

Oh, one other thing:
I'm also using Magisk v13 latest Beta. Maybe someone with the SIM card denials could give it a shot and check if this changes anything.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
As you already mentioned it is a problem with SELinux set to enforcing (=strict). The previously used permissive mode just printed out the error in the log but does not prevent a program from doing "malicious" actions. Enforcing really prevents programs from doing so. We need SELinux enforcing to pass safety net (without using magisk, ...). So setting the kernel to permissive by default is not an option. It is just a dirty hack and not a valid solution.

@a-dead-trousers: I also think that it is related to the baseband version. Especially it might be related to how the baseband was installed. From what I saw if you install the baseband together with stock ROM the stock ROM modifies the EFS partition on first boot after installation. This will not happen if the baseband is just installed separately with ODIN or TWRP which might cause a different (either bad or good) behavior.

We cannot bundle a baseband with the ROM - there are far too many of them. Different countries use different LTE frequencies and have custom country provider settings in the ROM. So everybody should use the correct baseband for his/her country.

That said we probably already found the SELinux rule which causes the SIM issue. I thought that the last ROM fixes it but as it turns out, it does not. As the problem does not occur with any device in our dev group it is a bit harder to get the right fix. Maybe it would be easier to try some fixes via chat.
 
S

StanleyNL

Guest
Jun 18, 2017 at 6:39 PM
hennymcc said:
As you already mentioned it is a problem with SELinux set to enforcing (=strict). The previously used permissive mode just printed out the error in the log but does not prevent a program from doing "malicious" actions. Enforcing really prevents programs from doing so. We need SELinux enforcing to pass safety net (without using magisk, ...). So setting the kernel to permissive by default is not an option. It is just a dirty hack and not a valid solution.

@a-dead-trousers: I also think that it is related to the baseband version. Especially it might be related to how the baseband was installed. From what I saw if you install the baseband together with stock ROM the stock ROM modifies the EFS partition on first boot after installation. This will not happen if the baseband is just installed separately with ODIN or TWRP which might cause a different (either bad or good) behavior.

We cannot bundle a baseband with the ROM - there are far too many of them. Different countries use different LTE frequencies and have custom country provider settings in the ROM. So everybody should use the correct baseband for his/her country.

That said we probably already found the SELinux rule which causes the SIM issue. I thought that the last ROM fixes it but as it turns out, it does not. As the problem does not occur with any device in our dev group it is a bit harder to get the right fix. Maybe it would be easier to try some fixes via chat.
Click to expand...
A funny thing to note is the fact that I don't have any issues related to SIM recognition, but I installed the boot.img you posted a while ago and guess what? It didn't recognize the SIM anymore.

It didn't really matter for me because I just restored the original kernel, but it might be interesting for testing purposes
 
Friedensfurz

Friedensfurz

Senior Member
Jan 31, 2016
277
229
0
NRW
Jun 19, 2017 at 7:22 AM
I have problems with the hall sensor waking my phone all the time.. Even though I disabled flipcover in settings, it still wakes up nearby a magnet.. ? Any ideas?
 
S

starbright_

Senior Member
Apr 11, 2010
1,111
175
83
Jun 19, 2017 at 8:18 AM
Last edited:
  • Like
Reactions: guntzog
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone