[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

[nubla]

NOTE:
Unfortunately you have to disable selinux before OTA flashing will work (I promise .. one day.. OTA will just work lol).
follow FAQ #1 to find the guide on how to disable selinux (follow just that then start the OTA).

Where is that FAQ? Maybe I'm blind but even Ctrl-F didn't find any instructions on disabling selinux.

If I understood correctly, the required steps to upgrade for UsU'd devices is:
1. Follow the workaround from here.

1. apply OTA and watch briefly after pressing INSTALL
2. as soon as the device shuts down: take out the battery
3. power on and let it boot -> TWRP will pop-up and the OTA will be
applied.

2. Then update recovery to the latest, eg. TWRP 3.5 Preview 258 https://leech.binbash.rocks:8008/TWRP/g4/

Is that correct?

I can't wait to test Phonesky (in-)app purchase support!

 

[tullyp]

On vs986, I downloaded new OTA update, /e/OS 1.0-20210119, but when hit install get "install error". To try this I uninstalled magisk and have latest 258 twrp. I need magisk to use auto dialer rilvoicefix so I'm reinstalling magisk. OTA is more work than just reflashing for me so where is the e/ update stored so can I just flash it?
@tullyp

 

[nubla]

where is the e/ update stored so can I just flash it?

/data/lineageos_updates

 

[tullyp]

/data/lineageos_updates
[/QUOTE

/data/lineageos_updates

Ya, found it, forgot I deleted magisk and could not find. Dumb...

 

[nubla]

Where is that FAQ? Maybe I'm blind but even Ctrl-F didn't find any instructions on disabling selinux.

If I understood correctly, the required steps to upgrade for UsU'd devices is:
1. Follow the workaround from here.


2. Then update recovery to the latest, eg. TWRP 3.5 Preview 258 https://leech.binbash.rocks:8008/TWRP/g4/

Is that correct?

I can't wait to test Phonesky (in-)app purchase support!

I got adventurous and tried updating to /e/ 1.0-20210119 without disabling selinux. The workaround worked, and the updated system booted even with TWRP 3.4.0 preview 230. No boot loops. I updated it to 3.5.0_9 preview 258 anyway.

As for changes:
- There is a slight difference in appearance, with the colors appearing more saturated (eg. the blue system fonts in settings).
- There is an allow/deny dialog that keeps coming up sometimes with only a cloud notification symbol/icon, but no explanation of what it is requesting to allow or deny. Confusing.
- I don't notice Phonesky / patched Google Play Store available? Did I miss something or was this discussed option not included?

 

[Tribux]

Thanks for new update I didn't read it propeerly before and had to flash everything from the begining Now I disabled selinux with adb..
TWRP updated
One question after update should I do some cleaning fromTWRP or use it right away?

 

[Tribux]

Where is that FAQ? Maybe I'm blind but even Ctrl-F didn't find any instructions on disabling selinux.

You probably found or warkaround but here is the FAQ :
FAQ #01 SELinux disable

 

[nubla]

You probably found or warkaround but here is the FAQ :
FAQ #01 SELinux disable

Aha, it's in the FAQ of a different ROM Thanks for finding it!

adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive

PS. What issues did you have with the upgrade without disabling selinux? I didn't disable it and so far my upgrade appears to be just fine.

 

[LouMinartey]

No SIM card detected after OTA from 15 Dec 20 build to 19 Jan 21 - Non USU'd H815 on 20p modem, OTA performed by SHRP

EDIT: Flashed Modem, no fix

EDIT2: Clean flashed build 20210120, no fix

EDIT3: Clean flashed build 20201215, SIM card detected. Phone working again

 

[tullyp]

Verizon vs986, flashed just system first of 20210120, no SIM detected. flashed back to previous system 20201215, got service. Then tried full clean flash. No SIM detected. No service. Flash back to previous version 20201215. Get service again.
@tullyp

 

[steadfasterX]

As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..

 

[nubla]

As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..

Wait, buggy builds are being pushed to OTA??

I'm currently on 20210119, but I use it without a SIM, so I can't confirm others' issues with that.

I don't have Telegram and don't want to be forced to join just to use /e/...

 

[tullyp]

New 20120121 build does get cell service on my Verizon vs 986! What a quick fix!
Thx @steadfasterX

 

[tullyp]

As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..

I did join, that's where I saw 20210120

 

[Tribux]

Aha, it's in the FAQ of a different ROM Thanks for finding it!




PS. What issues did you have with the upgrade without disabling selinux? I didn't disable it and so far my upgrade appears to be just fine.

It just did not want to go through, showed me warning sign and messeage on top task bar "installation error", that's why i thought that I should disable selinux and after that while phone connected to PC, it worked for me from OTA, kind of because it went to twrp and autoinstalled..

As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..

Thanks for info. I will check out the group

 

[steadfasterX]

Wait, buggy builds are being pushed to OTA??

I'm currently on 20210119, but I use it without a SIM, so I can't confirm others' issues with that.

I don't have Telegram and don't want to be forced to join just to use /e/...

Well first of all I am not LG. I'm doing this alone and do not have a team of testers who verify everything is working after every build. Second the whole process of Building and pushing out to OTA is fully automated so there's always a VERY rare chance that something is going wrong here when an issue occurs during the build process. That was the case with that build version.

To be crystal clear bigger changes like the latest ones regarding the RIL stack have been tested before I pushed it out of course. But my tests are done on a single build always not on the build during the automated build process. The chance that they differ is very rare but it exists.

You're not forced to join. Absolutely not. It is just an offer and you are totally free to take it or leave it. It's just that important information and change logs are pushed there only (or at least more early).

if you don't want to join I would recommend to wait at least one week before doing an OTA. usually that is enough to let other users find bigger issues and so let me make a new build or removing it from the OTA server.

 

[nubla]

if you don't want to join I would recommend to wait at least one week before doing an OTA.

Ok, that works. It would be nice to see changelogs here too, but I get that it's annoying to keep info synchronized in multiple places. It's cool that the build is fully automated.

Could you perhaps just let me know if/when the (in-)app purchase support patched Phonesky makes it into a build? The inability to use one important app (OBDLink) that requires that support is the only thing holding me back from full enjoyment of the setup.

Otherwise, I'm super happy with the LG G4 and your /e/ builds. Thanks for continuing to support it.

 

[LouMinartey]

These things happen, always gonna get the odd bad egg. I could've just restored a backup but I wanted to make sure I hadn't FUBAR'd it myself and a little troubleshooting goes a long way. Thanks for keeping my zombie-ass half-dead-CPU G4 alive, it overheats itself to pieces on most other roms if I don't disable some cores (Thanks, Google)

 

[llarr]

On latest - 21 January update, did notice this behaviour on earlier versions though.

I have noticed something odd and could use some advice narrowing it down. Basically if I turn the wifi on at 8am - 8.30am in the morning (GMT) and then leave the phone to idle, there's maybe a 50% or more chance there will be excess battery drain to the tune of 6.5% battery per hour.

Never had this issue when turning the wifi on in middle of the day or the evening or leaving the wifi on overnight and then throughout the next day.

Looking at battery stats it seems to be phantom drain that isn't associated with anything in particularly, but it does stop as soon as I turn wifi off.

The phone stats claim the cpu is in deep sleep during this. I wonder if there is some sort of update check scheduler. Maybe my phone goes crazy renegotiating its wifi connection for some reason under these specific circumstances. Any tips, basically my work around is to try to remember to check the phone after 20-30mins and if it has dropped 2-3% while idle then toggle the wifi and that tends to fix it. Very odd.

 

[steadfasterX]

On latest - 21 January update, did notice this behaviour on earlier versions though.

I have noticed something odd and could use some advice narrowing it down. Basically if I turn the wifi on at 8am - 8.30am in the morning (GMT) and then leave the phone to idle, there's maybe a 50% or more chance there will be excess battery drain to the tune of 6.5% battery per hour.

Never had this issue when turning the wifi on in middle of the day or the evening or leaving the wifi on overnight and then throughout the next day.

Looking at battery stats it seems to be phantom drain that isn't associated with anything in particularly, but it does stop as soon as I turn wifi off.

The phone stats claim the cpu is in deep sleep during this. I wonder if there is some sort of update check scheduler. Maybe my phone goes crazy renegotiating its wifi connection for some reason under these specific circumstances. Any tips, basically my work around is to try to remember to check the phone after 20-30mins and if it has dropped 2-3% while idle then toggle the wifi and that tends to fix it. Very odd.

well I think u know the answer. we need to take a look into the log when that happens (FAQ #1). When that happens again follow "Specific Issue", let it run for a while and then turn off wifi (logcat still running but note the exact time) and turn it on again, then let it run again for a a while.