[TODAYS-SEC-PATCH-LEVEL][ROM][UNOFFICIAL][P][UsU/non-UsU] /e/ OS | BYE Google, HELLO Privacy!

[pealfa]

Hello.
On my LG G4-H815 GPS does not work at all on /e/OS 1.8.1 or lineageOS 1.8.1 (also not on Samsung S4 - jfvelte).
Is there anything I can do?

 

[steadfasterX]

The /e/OS website currently indicates Android 11 is the end result at least for the Murena phones that come installed with /e/OS. Is this also true these CUSTOM builds for the G4? I recently learned I need Android 10 for using a new app for work.

Edit - Perhaps this was a dumb/naive question. My apology for this. This morning I thought that it may not make sense to need/use a Google Play Store App (Duo Mobile) for this Os. If it can accommodate this app then great if not I may be required to use LOS.

The e OS website indicates PIE as the latest official build for the g4. (see OP). This thread is about PIE even for the custom builds I offer.
There are more versions avail though:

A11: https://forum.xda-developers.com/t/...-vs986-e-os-bye-google-hello-privacy.4478815/

A10: https://forum.xda-developers.com/t/...s991-h81x-us991-vs986-lineageos-17-1.4397805/

All my custom builds come with google play installed. this app can be disabled if wanted though. Pls check Difference from pure /e/ or: why are the builds CUSTOM? topic in the OP for details.

Hello.
On my LG G4-H815 GPS does not work at all on /e/OS 1.8.1 or lineageOS 1.8.1 (also not on Samsung S4 - jfvelte).
Is there anything I can do?

there is no 1.8.1 version neither for eOS nor for LOS. this thread is about PIE which is A9. if you have issues with any other version report in the proper thread. also I do not support Samsung S4 . and this is the complete wrong section to report issues on Samsung phones anyways.

 

[steadfasterX]

Any one else have an issue with camera? Its always busy by process id:0. i can run it only once after reboot, and after every try to open camera shows the error, all other apps could not access it also. i tried to disable all apps permission to camera without success. could you recommend any solution for this.
flashlight unavailable also from topbar icon and from apps
it feels like it started from switching to titan kernel, but i`m not sure its a reason

are you sure that you have the correct bootloader stack installed? See Requirements topic in the OP

 

[thachdangss]

Hi all, I couldn't find the rom for F500_usu'd, is there a version for that variant, or it can use with other variants, thank you, and sorry for the noob question.

 

[steadfasterX]

Hi all, I couldn't find the rom for F500_usu'd, is there a version for that variant, or it can use with other variants, thank you, and sorry for the noob question.

flash the h815_UsU one. as long as you do not have a frankenstein it should went just fine.

 

[LinuxFan82]

Hi steadfasterX, thanks for your awesome work!

Today I replace LineageOS 16.0 with e-0.23-p-20230317-CUSTOM-h815.zip. Before I flashed SHRP_v3.1_stable-Official_g4-1676585551.zip and h815_20p_bootloader_20p_modem_TWRP-flashable.zip and wiped all partitions except "Encryption metadata" and then did "Format data".

I see the "e" with a bouncing ball and for a second a message popping up "Factory reset - rebooting..." and then my phone reboots into recovery.

Tried flashing everything again to no avail.

The first three digits of my serial number are 602.

 

[steadfasterX]

Hi steadfasterX, thanks for your awesome work!

Today I replace LineageOS 16.0 with e-0.23-p-20230317-CUSTOM-h815.zip. Before I flashed SHRP_v3.1_stable-Official_g4-1676585551.zip and h815_20p_bootloader_20p_modem_TWRP-flashable.zip and wiped all partitions except "Encryption metadata" and then did "Format data".

I see the "e" with a bouncing ball and for a second a message popping up "Factory reset - rebooting..." and then my phone reboots into recovery.

Tried flashing everything again to no avail.

The first three digits of my serial number are 602.

hm yea 602 is likely affected by the ILAPO but that is not certain.
when issues like these happen it is crucial important to use the factory reset in recovery as required stuff happens in the background when doing that.

so:

1. in recovery: factory reset
2. in recovery: format data
3. reboot recovery
4. flash the ROM
5. boot
6. if it still fails grab the boot logs (FAQ #7)

 

[LinuxFan82]

Thanks for your fast reply. I did what you said:
1. in recovery: factory reset
2. in recovery: format data
3. reboot recovery
4. flash the ROM
5. boot

Still "e with bouncing ball", then reboots to recovery.

Tried to grab the logs:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt

adb: error: failed to stat remote object '/cache/debug/boot_lc_kernel.txt': No such file or directory

/cache is mounted, but there's no folder "debug", only "backup", "backup_stage", "lost+found" and "recovery".

In "recovery" there's a last_log.gz and log.gz.

I did "Advanced / Copy Logs" but it looks like that's only a log of the recovery.

Recovery.log: https://bpa.st/KTEFU

Here is "adb shell dmesg" from within Sky Hawk: https://paste.systemli.org/?7bcb90c790ab61d4#FKLuVR6Dv2xbozmciWtZzskKhERFRPkw3iYpbVSQjRiY

 

[LinuxFan82]

removed

 

[LinuxFan82]

removed

 

[steadfasterX]

Thanks for your fast reply. I did what you said:
1. in recovery: factory reset
2. in recovery: format data
3. reboot recovery
4. flash the ROM
5. boot

Still "e with bouncing ball", then reboots to recovery.

Tried to grab the logs:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt

adb: error: failed to stat remote object '/cache/debug/boot_lc_kernel.txt': No such file or directory

/cache is mounted, but there's no folder "debug", only "backup", "backup_stage", "lost+found" and "recovery".

In "recovery" there's a last_log.gz and log.gz.

I did "Advanced / Copy Logs" but it looks like that's only a log of the recovery.

Recovery.log: https://bpa.st/KTEFU

Here is "adb shell dmesg" from within Sky Hawk: https://paste.systemli.org/?7bcb90c790ab61d4#FKLuVR6Dv2xbozmciWtZzskKhERFRPkw3iYpbVSQjRiY

hm ok a new build will arrive soon which has the whole boot debugging part re-worked. If nothing bad happens it will come today

 

[f_4Strings]

Hello, here is a new /e/OS entry! I successfully flashed the /e/OS Custom (e-0.23-p-20230705-CUSTOM-h815_usu) on my Usu unlocked H815. Following the instructions in the OP the installation process went smoothly and flawlessly.
The OS runs smooth and the battery lasts long so that my G4 got new (google-less) life!
Thank you @steadfasterX .

SIM card and Carrier detected but I had to insert manually the APN to get phone and mobile data services. Bluetooth works as well.
EDIT: GPS works, too (made a quick test with Magic Earth)

So far I didn't flash the "G4-VideoLag-Fix" since it seems that I don't need it. In fact, I tried to run youtube videos on newpipe and they run flawlessly at 720p/60fps and in quite well even at 1080p/60fps.
Does the "G4-VideoLag-Fix" allow to make video recordings at 60fps, too?

I guess this /e/OS custom build is using OpenGL and not SkiaGL.

adb shell getprop debug.hwui.renderer
...returns
OpenGL

Should I switch to SkiaGL for video/graphical improvement?

 

[steadfasterX]

Hello, here is a new /e/OS entry! I successfully flashed the /e/OS Custom (e-0.23-p-20230705-CUSTOM-h815_usu) on my Usu unlocked H815. Following the instructions in the OP the installation process went smoothly and flawlessly.
The OS runs smooth and the battery lasts long so that my G4 got new (google-less) life!
Thank you @steadfasterX .

SIM card and Carrier detected but I had to insert manually the APN to get phone and mobile data services. Bluetooth works as well.

So far I didn't flash the "G4-VideoLag-Fix" since it seems that I don't need it. In fact, I tried to run youtube videos on newpipe and they run flawlessly at 720p/60fps and in quite well even at 1080p/60fps.
Does the "G4-VideoLag-Fix" allow to make video recordings at 60fps, too?

I guess this /e/OS custom build is using OpenGL and not SkiaGL.

adb shell getprop debug.hwui.renderer
...returns
OpenGL

Should I switch to SkiaGL for video/graphical improvement?

the videofix zip is for those having even issues on lower fps so no need to flash it . if you decide to flash it there is no way back though and you need to flash it always again after any ROM upgrade or change.

you can switch to skia on-the-fly without reboot and check if that improves things for you. it does not hurt to try while skia might improves quality it has issues like screen flickering etc

 

[f_4Strings]

I've noticed that opening the "Open Camera" makes two ports listening on the tcp protocol. Here the netstat output:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name
tcp    0       0    0.0.0.0:55555    0.0.0.0:*    LISTEN       -
tcp    0       0    0.0.0.0:55556    0.0.0.0:*    LISTEN       -

Closing the app doesn't close the two listening ports. The only way to close them is to reboot.
It seems that there's no in/out internet traffic for the Camera app according to Privacy Guard (no alert received), so the listening ports "seem" harmless....

I really would like to know more about that for having the chance to learn more! Even more of what I could learn in the last twenty days knowing all at once "/e/OS", SALT, the mAid linux distro and the Usu unlock procedure!
(Thank you again @steadfasterX).

The argument has already been dealt here: https://forum.xda-developers.com/t/...ageos-15-1-14-1.3782722/page-52#post-78340136
Renaming the "libmmcamera_tuning.so" solves the issue of the "...opening ports" but I don't know if it breaks something in the Camera app and if it could be considered a "clean" solution. Applying the patch wouldn't be a quick and easy solution for me.

Is it worrying or harmless having those open listening ports and would it be worthy applying the patch?

 

[steadfasterX]

I've noticed that opening the "Open Camera" makes two ports listening on the tcp protocol. Here the netstat output:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name
tcp    0       0    0.0.0.0:55555    0.0.0.0:*    LISTEN       -
tcp    0       0    0.0.0.0:55556    0.0.0.0:*    LISTEN       -

Closing the app doesn't close the two listening ports. The only way to close them is to reboot.
It seems that there's no in/out internet traffic for the Camera app according to Privacy Guard (no alert received), so the listening ports "seem" harmless....

I really would like to know more about that for having the chance to learn more! Even more of what I could learn in the last twenty days knowing all at once "/e/OS", SALT, the mAid linux distro and the Usu unlock procedure!
(Thank you again @steadfasterX).

The argument has already been dealt here: https://forum.xda-developers.com/t/...ageos-15-1-14-1.3782722/page-52#post-78340136
Renaming the "libmmcamera_tuning.so" solves the issue of the "...opening ports" but I don't know if it breaks something in the Camera app and if it could be considered a "clean" solution. Applying the patch wouldn't be a quick and easy solution for me.

Is it worrying or harmless having those open listening ports and would it be worthy applying the patch?

well yea that is a thing here. It seems libmmcamera_tuning.so should never go into a (final) ROM.

All refs I found to that library and its calling functions (https://gitlab.com/search?search=tu...815852&search_code=true&repository_ref=master) are related to internal tests and nothing we want to have in productive. Likely they use it for internal test communication and that's also why you do not see any traffic there. Having ports like that open is really not cool though.

so yes removing/renaming that file should not cause any issues (I am 99.9999% sure), while it would be good if you can test everything is still working after a reboot (if you haven't already).

that means rename:
- libmmcamera_tuning.so

then reboot, test and if all is fine do the same for:
- libmmcamera_tuning_lookup.so

Also try at least 1 other camera app just to be sure. The only "test" needed is to see if you can start the camera, take a pic and video. if that is working fine (which I am pretty sure it is) then we can remove that lib completely.

thanks for the investigation and feedback!

 

[f_4Strings]

well yea that is a thing here. It seems libmmcamera_tuning.so should never go into a (final) ROM.

All refs I found to that library and its calling functions (https://gitlab.com/search?search=tu...815852&search_code=true&repository_ref=master) are related to internal tests and nothing we want to have in productive. Likely they use it for internal test communication and that's also why you do not see any traffic there. Having ports like that open is really not cool though.

so yes removing/renaming that file should not cause any issues (I am 99.9999% sure), while it would be good if you can test everything is still working after a reboot (if you haven't already).

that means rename:
- libmmcamera_tuning.so

then reboot, test and if all is fine do the same for:
- libmmcamera_tuning_lookup.so

Also try at least 1 other camera app just to be sure. The only "test" needed is to see if you can start the camera, take a pic and video. if that is working fine (which I am pretty sure it is) then we can remove that lib completely.

thanks for the investigation and feedback!I went through all the steps and did some quick tests by trying the 'standard', 'HDR', 'macro' and 'EV filter' photo modes on both jpg and raw (dng) files. I also tried some FHD videos. I didn't notice any significant difference from having (or not having) the two shared libraries, but the two closed ports

Thank you very much for your detailed answer!
I went through all the steps and, after renaming the two shared libraries (in two different steps), I did some quick tests (for each step) by trying the 'standard', 'HDR', 'macro' and 'EV filter' photo modes on both jpg and raw (dng) files. I also successfully took some FHD videos. I didn't notice any significant difference from having (or not having) the two shared libraries, but the two closed ports!!

I rebooted twice, and tested twice for each library renaming. Maybe I could be wrong, as I only checked a few options for photos and videos, but everything seems to be working fine; there are many combinations for "Open Camera" photos and videos options that would take time to test yet, but "...probably" if there were problems they would have already occurred in these quick tests.

At last, I installed "Libre Camera" from the FDroid repository and it worked fine too, by making photos and videos using the two cameras (front and rear).

 

[steadfasterX]

Thank you very much for your detailed answer!
I went through all the steps and, after renaming the two shared libraries (in two different steps), I did some quick tests (for each step) by trying the 'standard', 'HDR', 'macro' and 'EV filter' photo modes on both jpg and raw (dng) files. I also successfully took some FHD videos. I didn't notice any significant difference from having (or not having) the two shared libraries, but the two closed ports!!

I rebooted twice, and tested twice for each library renaming. Maybe I could be wrong, as I only checked a few options for photos and videos, but everything seems to be working fine; there are many combinations for "Open Camera" photos and videos options that would take time to test yet, but "...probably" if there were problems they would have already occurred in these quick tests.

At last, I installed "Libre Camera" from the FDroid repository and it worked fine too, by making photos and videos using the two cameras (front and rear).

Perfect thanks. Thats fine. I will remove those in my next builds!

g4-common: remove debugging blobs · LGgFour/proprietary_vendor_lge@c47f3a4

libmmcamera_tuning.so: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name tcp 0 0 0.0.0.0:55555 0.0.0.0:* LIS...

github.com

g4-common: remove debugging blobs · LGgFour/proprietary_vendor_lge@b03f3cb

libmmcamera_tuning.so: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name tcp 0 0 0.0.0.0:55555 0.0.0.0:* LIS...

github.com

g4-common: remove debugging blobs · LGgFour/proprietary_vendor_lge@6998027

libmmcamera_tuning.so: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name tcp 0 0 0.0.0.0:55555 0.0.0.0:* LIS...

github.com

g4-common: remove debugging blobs · LGgFour/proprietary_vendor_lge@bd31a07

libmmcamera_tuning.so: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program Name tcp 0 0 0.0.0.0:55555 0.0.0.0:* LIS...

github.com

 

[f_4Strings]

Hi, I did a full clean install, not rooted (not installed Magisk, neither Exposed). The system runs smooth and flawless but I am experiencing some strange reboots that only occur when I take my G4 outdoors, such as leaving it in my pocket.
I haven't experienced any reboots when the phone is stationary, so I think it's something to do with movement. For this reason I think the reboots could also be caused by the Nano-Sim adapter (I tried two anyway), loose plastic due to age or faulty battery contacts.

However, I pulled the files in /sys/fs/pstore and noticed (in the console-ramoops-0 file) the presence of some warnings and kernel call traces related to the cpu up to the message:

Reboot auto-fsync: panic - force flush!
Rebooting in 15 seconds..

I attach the pstore.tgz and the PMSG log in a readable format in the hope that reading them will reveal some useful information!

Notes:
1. the /cache/debug directory does not exist
2. these reboots have nothing to do with the fact that I renamed "libmmcamera_tuning.so" and "libmmcamera_tuning_lookup.so" a few days ago; on the contrary the "Open Camera" app continues to work fine even after further testing!

 

[steadfasterX]

re 1: pls check /persist - the path has moved (fixing the faq asap) EDIT: updated the FAQ
re 2: thx for the crash logs. the reason is:

> Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

that occurs in 2 scenarios only (at least what I found):

1. when you are not running the latest modem firmware (e.g. 20p for h815)
2. when UsU'd but not using an UsU compatible ROM

so most likely the first one applies in your case. are you really on 20p? If you are not sure flash the TWRP zip (see Requirements topic of this thread)

 

[f_4Strings]

re 1: pls check /persist - the path has moved (fixing the faq asap) EDIT: updated the FAQ
re 2: thx for the crash logs. the reason is:

> Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

that occurs in 2 scenarios only (at least what I found):

1. when you are not running the latest modem firmware (e.g. 20p for h815)
2. when UsU'd but not using an UsU compatible ROM

so most likely the first one applies in your case. are you really on 20p? If you are not sure flash the TWRP zip (see Requirements topic of this thread)

My original firmware before the Usu procedure was:
LGH815AT-00-V20p-EUR-XX-APR-03-2018+0

Please, is this the correct stock rom version to get a 20p modem firmware version? This stock rom version was the latest Marshmallow available for my H815.

Then, after unlocking Usu, I flashed the rom e-0.23-p-20230705-CUSTOM-h815_usu.zip and I did a full clean install.

Given that, should I flash the h815_UsU_20p_bootloader_20p_modem_TWRP-flashable.zip?

I attach the files in /persist/boot_debug although they refer to a reboot I did voluntarily afterwards and not immediately after the kernel panic. However, the G4 was never turned off in the meantime.

Thank you! I really hope to solve this as I really like your /e/OS!