yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] nubla:
Will App Lounge be added or will it replace aurora store? Seems like it tries to incorporate aurora, cleakapk, and exodus-privacy.
[G4 Android Development] 1captainjacknotsparrow1:
1) Can I disable the e-appstore without root access? Because I tried, but couldn't. The "deactivate-button" was greyed out.

2) What do you mean with "App-Lounge" from your other post? There was already an app installed called "App Lounge" on your normal build and I thought that this is the normal e-appstore. I'm a little bit confused here. Could you please explain it a litte more detailed? Or do you mean a new version of "App-Lounge"?

3) Will this "new" app or new version of "App-Lounge", also like in point 2 mentioned it was already there, solve this problem with the appstore, since it will be just Aurorastore with a different name?

4) You mentioned in your LineageOS-16-thread that there will be no security updates since LineageOS doesn't support version 16 anymore. Does this apply to your eos-rom since it is build on LineageOS16 and there will be also no security updates anymore?

thanks in advance
[G4 Android Development] steadfasterX:
Re1: yes by using shrp/twrp. Mount system, use the file browser or adb shell to navigate to system/app/Apps and rename Apps.apk to Apps.apk.disabled.

Then ensure you wipe cache and dalvik and its gone on next boot.

Re2: the project removed their app store and replaced it by a branded Aurora named Apps Lounge recently (a very good decision imho).

Re3: yes

Re4: yes and no. As long as the code base does not change i don't create new builds which means LOS won't get new builds likely but eos might get them. The reason is that eos still backports some stuff (like the apps lounge) to pie but that might stop at any time soon, too. I am not aware of attempts by the e foundation to backport sec patches on their own so i assume this ain't gonna happen (there's already a big gap).
[G4 Android Development] nubla:
Is P still the latest working e-OS build for the G4? Is it likely for any newer version of android (e-OS) to make its way for the G4 or are there still blocking issues?
[G4 Android Development] steadfasterX:
Only blocking issue is time ;) but yes its planned
[G4 Android Development] nubla:
Incredible, it's here!! Thanks so much!

https://xdaforums.com/t/rom-unoffic...-vs986-e-os-bye-google-hello-privacy.4478815/

Is there anything special that needs to be done to go to a11 from a9, compared to regular a9 updates?

Will the system updater in a9 see the a11 update? Right now the manual check in e-os 0.23-20220805 just spins and doesn't find any update.
[G4 Android Development] steadfasterX:
No, there is no OTA support available upgrading from a9 to Android 11. While it is technical possible I do not support it as we had so many changes which requires full clean flash anyways.

And as we are here in the Android 9 thread 😉 here a sneak preview for the upcoming Android 9 build:
[G4 Android Development] nubla:
A full clean flash and not a regular flash, as described in FAQ #02, meaning app and user data must be erased?

Recommendations for which app to use for data backup, such as Neo Backup? https://f-droid.org/en/packages/com.machiav3lli.backup/
[G4 Android Development] steadfasterX:
Yes thats what happens. Everything will be removed. Every app and even everything you've downloaded, all pics videos, really everything .

Well I'm extreme about backup as i use

1) Migrate app (choosing non TWRP method within)

2) TB + encryption + upload to cloud + OTG USB storage as my first fallback backup

3) Neo + manual upload to my nextcloud as my second fallback

In all my restore scenarios I've suceeded in 90% of all cases with 1) and needed for the rest 2). Never needed Neo until now so i can't say how reliable it is.

Non of this will save your pictures / videos though but I've them in my nextcloud auto uploaded .
[G4 Android Development] nubla:
What is 1) Migrate app ?

I guess this upgrade requires some care and forethought, with no backup solution grabbing everything including pics, documents, etc. I definitely want to make sure I'll be able to migrate my Signal app for example.

Bit of a side note, but since encryption was mentioned, is it safe to encrypt the phone? I thought there could be some potential issues with TWRP/SHRP backups when encryption, or even lock screen pattern/pins, is used. Because of that doubt I avoided encryption even though I'd like to use it, and I disable the lock screen pattern before each TWRP/SHRP backup.
[G4 Android Development] steadfasterX:
Migrate is unfortunately not under active dev anymore but still working fine (for me): https://xdaforums.com/t/app-root-5-0-1st-nov-2020-migrate-custom-rom-migration-tool.3862763/

It has the option to create TWRP zips which can be flashed directly in TWRP but that never works reliable for me. but when you have rooted you can restore directly within the ROM.

Encryption on pie is supported but like with switching to another ROM or before upgrading it is HIGHLY recommended to backup everything before.

If your question is about a11 and encryption ask in the a11 thread ;) (spoiler: read the known issues there).

The lockscreen thing is something which I never had in the past but saw ppl struggling there. Keep in mind that you cannot fix that issue if your device is encrypted as TWRP/SHRP cannot decrypt /data where the fix must have access to.

Keep also in mind that TWRP backups are not backing up your internal storage (every backup run will show that in red color)! ONLY for system, boot, bootloader stack its a PERFECT solution but not for data backup. thats why you still cannot backup your apps in TWRP/SHRP these days and even when there are hacks allowing to do so I wont trust any of them. The only reliable way is using root + a trustworthy app within Android to create backups of your apps and app data. imho.
[G4 Android Development] steadfasterX:
thanks to @sdembiske I've noticed that we can still get Security Patches for pie. not in an official manner but well still from the LOS gerrit.

Thanks again dude and so we have new builds now for eOS pie on the latest and greatest patch level 2022-08-05 :)

also new in these build(s):

- wifi /bt mac fix

- switched to the latest and greatest TITAN kernel branch

have fun..
[G4 Android Development] nubla:
Awesome! Especially since I think I will stay on eOS pie for now until A11 features/functionality like auto brightness, NFC, and selinux get sorted out. https://github.com/LGgFour/android_issues/issues?q=is:issue+is:open+label:android_11

What is the TITAN kernel branch and its benefit?
[G4 Android Development] steadfasterX:
Titan branch is a unified branch working with android 9-12 made by @aoleary . This eases up kernel dev and so all stuff fixed is avail for all android versions
[G4 Android Development] MorganXYZ:
Hi @steadfasterX , Cry for help here - I've been rocking along v happily with your /e/os (last but one version, reading over the recent posts) and I just tried to boot it a couple of times without sufficient power and it's really taken a dive - it's only booting into recovery or fastboot. Booting into system causes an 'e' and bouncing ball - it seems to timeout without any progress before rebooting into recover. What's your recommended way back to happiness. Thanks for all the hard work - it's awesome keeping this old soldier marching on.
[G4 Android Development] steadfasterX:
What are the first 3 digits of your serial ? Its printed on a sticker behind the battery.

If this is the ilapo or not can be tested by following the X cores guide and building an ilapo boot image of your current ROM. If it boots with just 2 cpus enabled you can be 100% safe that it is.
[G4 Android Development] MorganXYZ:
Thanks @steadfasterX for getting back so early on a Sunday - not at church?! :giggle:

First 3 serial digits: 609

Hmm, just searched ilapo and can't say I'm excited by possibility of hardware fault bootloop... Can you point me at the 'X cores guide'? Thanks heaps, M
[G4 Android Development] MorganXYZ:
Could this thread be the answer:

LG G4 fails to complete LOS 14.1 boot after battery drained to zero [Fixed]

?

It sound familiar with totally drained battery, booting to twrp etc

Thx
[G4 Android Development] steadfasterX:
this has everything about it incl a link to the X cores guide: https://xdaforums.com/t/guide-ilapo...xit-list-index-for-all-known-methods.3667688/

but.. as you have a 2016 device of September it is very unlikely the cause. yes that link you mentioned can be VERY likely the cause on your device as well so give it a try first.

The only other option I know: If you have a full backup of your data (incl pics etc) then the first option would to format(!) data and doing a clean flash as written in the FAQ.

PS: no church at 7 am here ;) I had written that during my morning walk ;)
[G4 Android Development] steadfasterX:
At this stage we should move on to an own topic as all this has nothing to do with UsU itself. So pls create an own thread for this problem.

/sdcard is just a link to /data/media/0 which is actually your internal storage.

A full backup can be done by

adb pull /data fullbackup

and just the internal storage with

adb pull /data/media/0 internalstorage

The difference between the two is that the first one will also Backup eveything including every app , internal storage and App data and so will be extreme big while the second one will just backup your user data / internal storage (pics, videos, downloads,...).

There's no guarantee that the backup with the first can be fully restored but if you wanna go safe it's still the best option as you don't miss a bit. If you don't care about your app and app configs etc then the second one is the better choice.

A lot has changed since i helped that user in the linked topic. E.g. when you have a current ROM installed you will have boot logs helping in trouble like that: in TWRP ensure /cache is mounted and grab all debug logs from the /cache partition. Share these in your new thread ;)
[G4 Android Development] MorganXYZ:
This noise ends here...

... And, continues here:

flat battery - corrupted filesystem - boot loop (unlikely ilapo)
[G4 Android Development] nubla:
It's been quiet here lately but thanks so much for keeping your e-OS ROM updated with the latest security patches @steadfasterX !

I did the OTA for 20230217.142118 CUSTOM and nearly everything looks fine, except that Lawnchair v12.1.0 Alpha 4 (12010005) (icon with sun in front of lawn chair, app.lawnchair) constantly crashes. I guess that's a risk with apps that aren't maintained frequently. Not sure this has anything to do with the ROM.

Luckily I still had the old Lawnchair v1.2.1.2001 (icon with sun behind lawn chair, ch.deletescape.lawnchair.plah) and managed to switch to it and it's running ok.
[G4 Android Development] breversa:
As an alternative, have you tried Neo Launcher : https://apt.izzysoft.de/fdroid/index/apk/com.saggitt.omega ?
[G4 Android Development] steadfasterX:
Hey, pls when sharing logs use a paste service, always. Hm I have upgraded without any issue but well. could you try to long press the lawnchair icon -> app info -> clear data & cache (ofc that will reset the settings of that app though)
[G4 Android Development] nubla:
No I haven't, but thanks for the suggestion. Good to know about Neo Launcher.
[G4 Android Development] nubla:
Clearing data & cache fixed it! (cache alone was not enough) Weird, maybe the settings got corrupted somehow. All is well now.

Got it, next time I'll use a paste service.
[G4 Android Development] pizza_alarm:
I'm still struggling with UsU ROMS on my H815 although I made a full clean install. I tested e-0.23-p-20230217-CUSTOM-h815_usu and e-1.8.1-r-20230214-CUSTOM-h815_usu, but I could not make or receive phone calls on both versions. Is it possible to make some kind of fail-safe tabula rasa installation?
[G4 Android Development] steadfasterX:
The instructions are kind of fail safe. If they don't work u are not following it briefly or its a device issue. In both cases nothing really nothing can be said without logs. In this case the boot logs (see faq)
[G4 Android Development] pizza_alarm:
What I understood so far:

1. First I need a modem file that I could either download or extract from the original ROM via

LG Firmware Extract Tool, SALT or KDZTools. KDZTools extracts 3 modem files: modem, modemst1 and modemst2. I only

need the modem file.

Installation with fastboot flash modem modem.bin

If I have missed something please correct me.

Do I need to root the phone in order to execute a command like adb pull /cache/debug/boot_lc_crash.txt ?
[G4 Android Development] steadfasterX:
sorry for the delay..

so

1. correct, modemstX is not modem and you need modem only.

2. fastboot flash modem modem.bin is fine

3. u dont need root for grabbing the logs but a recovery like SHRP or TWRP. so boot once. reboot to recovery, grab the logs (not just crash ofc)
[G4 Android Development] AlboTourus:
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
[G4 Android Development] RVC46:
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.
[G4 Android Development] 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?
[G4 Android Development] steadfasterX:
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://xdaforums.com/t/rom-unoffic...-vs986-e-os-bye-google-hello-privacy.4478815/

A10: https://xdaforums.com/t/rom-unofficial-a10-f500-ls991-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.

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.
[G4 Android Development] steadfasterX:
are you sure that you have the correct bootloader stack installed? See

Requirements

topic in the OP
[G4 Android Development] 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.
[G4 Android Development] steadfasterX:
flash the h815_UsU one. as long as you do not have a frankenstein it should went just fine.
[G4 Android Development] 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.
[G4 Android Development] steadfasterX:
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)
[G4 Android Development] 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
[G4 Android Development] LinuxFan82:
removed
[G4 Android Development] steadfasterX:
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
[G4 Android Development] 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?
[G4 Android Development] steadfasterX:
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
[G4 Android Development] 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://xdaforums.com/t/rom-unoffic...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?
[G4 Android Development] steadfasterX:
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!
[G4 Android Development] f_4Strings:
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!! :D

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).
[G4 Android Development] steadfasterX:
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