[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

[sbasil]

i did exactly this thing about permissive ... BUT ... i noticed now that at every reboot i need to do again this step if i reboot email lineageos app don't load email text message but only header, if i open a terminal on G4 and i did these steps i can read email text message .. if i reboot the problem is the same and i need to did this permissive steps

My h815 (WiFi and LTE)) started to work today with selinux set to enforced.. I suppose that the moon and stars are correcly aligned today or something, because I didn't do anything (knowingly). . :silly: LOS16 is pure gold!

 

[calavera2k]

I have the same problem that the permissive attitude is gone after a reboot.

 

[steadfasterX]

i did exactly this thing about permissive ... BUT ... i noticed now that at every reboot i need to do again this step if i reboot email lineageos app don't load email text message but only header, if i open a terminal on G4 and i did these steps i can read email text message .. if i reboot the problem is the same and i need to did this permissive steps

you missed the step 2 ! check the picture in this post at the top

anyone with los browser not working?

Sent from my LG-H815 using XDA-Developers Legacy app

I got GDroid and FDroid working but not downloading, too. anyone else?

with 10/07/2019 build, i think something is broken with excange (???) / imap protocol (???)

whan i setup some imap email account in email lineage os app and even gmail, i can see only email header, when i tap to see email message it load forever and nothing appear

any suggestion?

Hey guys,
during my further testings yesterday and today I found that there are sometimes strange issues.. It is not clear WHY that happens so it is hard to say if you get catched by it or not but its clear how to solve it (which you might not like).

Here I can open the browser, connect my email account, no WiFi issues etc.

but I had some issues which looked similar - but not always. There was no denials in the logs so it was not a selinux issue and I didnt had that before I played around with gapps (sorry I reject google crap as much as possible). Ok so I was able to re-produce bad behavior by flashing dirty.. sometimes by a new kernel, sometimes a new ROM version + gapps.

All my issues went to hell once I factory reset it (either factory reset or "full clean flash"). so it must have to do with the gapps.

If you have gapps installed you have to re-install gapps after flashing a new ROM build. If you haven't do that first.
If you still have issues I fear you have to go the "factory reset - way" and ensure you have everything backed up before ofc.
When there are still issues like that:
do a "full clean flash", boot without gapps, reboot to TWRP and flash gapps then first.

Hi @steadfasterX, should we wait a new build for the H815 ?

yes wait until the next build is recommended. It will have fixed 2 major gapps issues (device shown as "not certified" and a selinux perm issue).

I have the same problem that the permissive attitude is gone after a reboot.

sure. thats how it works. if you have an issue report it with a log as described in the build acnnouncement post (you missed step 2 here!

.-

 

[busattovini]

The Mail app has stopped working since I restarted the system, but the adb workaround fixes it. However, not for a reboot.

Sent from my LG-H815 using XDA Labs

 

[steadfasterX]

The Mail app has stopped working since I restarted the system, but the adb workaround fixes it. However, not for a reboot.

Sent from my LG-H815 using XDA Labs

no log, no fix. I repeated that multiple times now

.-

 

[calavera2k]

sorry steadfasterx. you are completely right. my mistake. I still look at what type of log you might need. I suppose a full boot log.

 

[steadfasterX]

sorry steadfasterx. you are completely right. my mistake. I still look at what type of log you might need. I suppose a full boot log.

no not a boot log...

set selinux to permissive
follow FAQ #1 (follow the "GUIDE" link there) and do whatever not worked without being permissive and share the log as described in that guide, too. In step 3 of that guide choose "option B)" which refers to an app specific issue (which is what you have)

.-

 

[rojanor]

Hi everyone,thanks for all the great work!!

I cant get the safetynet check to pass on my h815, this is what ive done:
Unlocked bootloader, flashed twrp, full wipe, v29a bootloader only, LOS, opengapps.

Is opengapps (any version) required to get safetynet to pass? Anything else?

I also tried v29a safetynet pass.img (flash to boot partition,right?) but OS wouldnt boot after flash..
Please help, thanks

 

[steadfasterX]

Hi everyone,thanks for all the great work!!

I cant get the safetynet check to pass on my h815, this is what ive done:
Unlocked bootloader, flashed twrp, full wipe, v29a bootloader only, LOS, opengapps.

Is opengapps (any version) required to get safetynet to pass? Anything else?

I also tried v29a safetynet pass.img (flash to boot partition,right?) but OS wouldnt boot after flash..
Please help, thanks

fixed in next build: https://github.com/Suicide-Squirrel/issues_pie/issues/24

 

[Gigio755]

you missed the step 2 ! check the picture in this post at the top

really really sorry, i didn't undersand that i should produce a log, sorry

I tried to do it in this way

option B) when you want to debug a specific Android issue (e.g. app crashes etc):
logcat -c -b all
logcat -b all
now reproduce the issue
when the issue occurred: CTRL + C in the terminal window

i just open lineageos email app, then tap on a message and after some seconds it load and load and load i press "ctrl + c" i hope to did it in the right way

 

[steadfasterX]

really really sorry, i didn't undersand that i should produce a log, sorry

I tried to do it in this way



i just open lineageos email app, then tap on a message and after some seconds it load and load and load i press "ctrl + c" i hope to did it in the right way

ok next time use paste.omnirom.org for pasting logs.. makes it easier on my site.
anyways. that error you have should be fixed in the next build as well.


.-

 

[polfrank]

@steadfasterX I have sent you a PM with logs of some apps that malfunction for me when SELinux is set to enforced. I hope that I have done it in the right way. I don't know if it helps but I hope so!

My setting is: latest build after a regular clean flash. I also flashed the latest gapps after the flash of the new rom. SELinux enforced, not encrypted. Magisk installed.

The ROM is working fine and seems stable in any other way. Thanks for your work!

 

[Gigio755]

ok next time use paste.omnirom.org for pasting logs.. makes it easier on my site.
anyways. that error you have should be fixed in the next build as well

Oh, ok! It was my the first time a did it, thank you for your patience and for your hard work :good:

 

[sperelli]

hi @steadfasterX, here is my log.
funny enough, after i set root to only adb (instead of app & adb) los browser worked.


EDIT: I see now I hadn't changed correctly selinux state to permissive, in the tests done this morning. In the end, selinux policy definitely is the culprit, not root state.

 

[busattovini]

no log, no fix. I repeated that multiple times now

.-

Sorry... I'll try to do a log next time. ??

Sent from my LG-H815 using XDA Labs

 

[busattovini]

Oh, so there's a new build out... Downloading. Thank you so much. OMG. Any advice about the installation? Can I do dirty flash?

Sent from my LG-H815 using XDA Labs

EDIT: NEW BUILD IS PERFECT. You're the greatest. Sorry for my inconvenience sometimes, I'm kinda anxious. I just want you to know that I truly admire your work and, even though I don't know who you are, I know you're amazing. Regards from Brazil!

 

[sbasil]

I installed the newest (07/11) version. Works great. Getting connected takes a little bit longer (3g/4g), but it works in the end (attachments). Netflix refuses to open (error 502-1019) unless selinux is set to permissive (before I had to install it from an apk, now it can be found in the store). Passes safety.net with flying colors. It's getting better greater by each new version.

Here's logcat info from Netflix: https://paste.omnirom.org/view/91da1288 (selinux permissive)
And here's another one: https://paste.omnirom.org/view/89ad9d50 (selinux enforced)

 

[TheCappn]

No it works perfectly here. read the FAQ in how to do a proper logcat (turn off wifi and follow the steps) and how to share it properly.


well maybe on your sticker (behind the battery), very likely on the original packaging..
sometimes it is named "Buyer code". In your particular case it would be one of UCL or UCK: https://lg-firmwares.com/lg-phone-firmwares-region-description/

you can also check one of those free imei check websites ( I do not trust any of them though ) or ask your local dealer if he can check for you.
You can also send a request to LG or your provider and based on the imei they all can provide you that information.
There is also a llittle chance that it is printed on the mainboard but I guess the chance is 20% only..

nevertheless the logcat from boot is required as well

.-

According to the sticker under the battery. My device is UCL.

I've attached a logcat from boot, with the baseband package flashed. Let me know if you need anything else.

 

[steadfasterX]

I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

Nevertheless:
This is the second round first of my unified device tree so I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

Pre-Cautions | Flashing instructions

1. Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
2. Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
3. Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
4. TWRP menu: "Mount" --> choose "System"
5. From a terminal execute:

   adb shell md5sum /system/etc/firmware/venus.mbn

6. Compare the value (last 4 characters is fully enough) with these:
   If you flash:
   h815, f500, h818, h819 it should be: ebc5d32c651bf061787e82258cf78a3c
   h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
   WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
   While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
7. Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
   or if the above checksum does not match:
   provide the recovery.log (FAQ #4 A)!!
   ... then flash the previous LOS version to get back to life.

New builds are cooking...

build errors can happen .. so it might take longer until everything completes (as I can fix build issues tomorrow first if any)

In progress (in that order):

Live - View: https://lets.binbash.it:8800/job/LG-G4/job/LOS-16.0/job/Build all LGE-G4 models/workflow-stage/

• H810

Done:

• H815
• H811
• H815 UsU
• VS986
• H812

Noteworthy Changes:

• several selinux policies updated
  If you encounter issues try this first:
  

  adb shell
  su
  (or adb root when enabled)
  setenforce permissive

  Try again and if the issue is gone when in permissive mode: provide me a logcat as described here
  
  
• wrild optimized (helper if rild crashes)
  
  
• safetynet passes without root
  
  
• Google play fixes
  
  
• and others ... and all the details
  

IMPORTANT:

• Taking a backup before is recommended - always
• As usual a "REGULAR CLEAN FLASH" is RECOMMENDED .
  See the FAQ #2 of this thread how to do a "regular clean flash": https://forum.xda-developers.com/g4/development/rom-lineageos-16-0-t3929082/post79502871

Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available..
The above fixes are brought to you by the Suicide Squirrel Team :victory:

ok enough of words, just one more thing:
FLASH and ENJOY that ultra stable, fast, smooth and best pie build for LOS - ever


.-

 

[steadfasterX]

@steadfasterX I have sent you a PM with logs of some apps that malfunction for me when SELinux is set to enforced. I hope that I have done it in the right way. I don't know if it helps but I hope so!

perfect. pls try again with the build from yesterday/today, I have just checked some of your logs and I think that should all should be fixed now. If not pls do that again. Thanks.

hi @steadfasterX, here is my log.
funny enough, after i set root to only adb (instead of app & adb) los browser worked.


EDIT: I see now I hadn't changed correctly selinux state to permissive, in the tests done this morning. In the end, selinux policy definitely is the culprit, not root state.

should be fixed with the latest build from today/yesterday. If not provide the log again, this time paste it to paste.omnirom.org as described in the guide. This makes it much easier on my site.

I installed the newest (07/11) version. Works great. Getting connected takes a little bit longer (3g/4g), but it works in the end (attachments). Netflix refuses to open (error 502-1019) unless selinux is set to permissive (before I had to install it from an apk, now it can be found in the store). Passes safety.net with flying colors. It's getting better greater by each new version.

Here's logcat info from Netflix: https://paste.omnirom.org/view/91da1288 (selinux permissive)
And here's another one: https://paste.omnirom.org/view/89ad9d50 (selinux enforced)

Thanks. Unfortunately that one will not be fixed with the current build. I will look at that next, thx for providing the log and in the correct manner (btw the permissive one is enough)

According to the sticker under the battery. My device is UCL.

I've attached a logcat from boot, with the baseband package flashed. Let me know if you need anything else.

perfect thx. will look into that asap


.-