yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] Tribux:
There is a chance to update link for twrp bootloader? :)
[G4 Android Development] steadfasterX:
leech server was just down for maintenance. try again.

-
[G4 Android Development] Tribux:
It's working now, Thanks ;)

Can you point me maybe which version should I choose if I have unlocked bootloader?
[G4 Android Development] steadfasterX:
the right one for your model and unlock method. as you don't told your model, no idea.

.-
[G4 Android Development] Tribux:
ough sorry, I have H815. I dont remember very good but i think i unlocked it with official way..but I see few versions on the server and there is few MB diffrences, which should I choose?
[G4 Android Development] steadfasterX:
well I guess you would remember when you would have used the unofficial unlock method (UsU) so you would choose h815_20p_bootloader_20p_modem_TWRP-flashable.zip in the folder 20p. I cannot recommend anything else then 20p for the h815.

but again: if you have UsU'd your device that file

will brick your phone

. so if I were you I would verify that before.

SALT (part of mAid) would show you if you have UsU'd your device or not (so official unlocked).

There is also another mostly unknown way of verifying when you are in TWRP. I have implemented a check for that and the result can be shown as:

adb shell
getprop ro.usu.device.unlockmode

.-
[G4 Android Development] Tribux:
WIll do that and confirm in TWRP ;) Thanks a lot, hopefully I will not fail anything :D
[G4 Android Development] steadfasterX:
before doing anything else I highly recommend that you do a TWRP backup which includes "Bootloader" (scroll down in the backup screen until you see it)

.,-
[G4 Android Development] Tribux:
I checked before and it was officialy unlocked. Everything work perfect for now, in my opinion much better than my previous pixel experience rom..I changed it mostly for better hotspot experience ;) If you know how to improve it let me know:)

THank You ;)
[G4 Android Development] rotoko:
It would be nice to do this rom for Google owners as well, not everyone wants a different version.
[G4 Android Development] steadfasterX:
what do you mean by that "Google owners" ? and also pls explain what you meant by "not everyone wants a different version"

.-
[G4 Android Development] rotoko:
I Sorry, I meant that when I want to use my Google email, it's blocked, I have it as a priority.

/e/OS is otherwise functionally excellent.
[G4 Android Development] steadfasterX:
Well you can still access your google mail by the /e/ mail client.

They even made a guide for that here: https://community.e.foundation/t/howto-add-a-gmail-id-from-the-mail-app/2807 with some notes about new changes here: https://community.e.foundation/t/e-os-mail-application-and-gmail/18390

I use FairEmail though bc it fits my needs better. Ofc you can add there your google mail as well.

if you really wanna use the gmail app itself I guess thats not possible though.

.-
[G4 Android Development] AlboTourus:
yeah, OTA, my bad :)

i have both mobile and wifi connections "no internet" with little cross over icon, tried different VPN servers with same result
[G4 Android Development] steadfasterX:
when you do not have an internet connection it explains why you cannot reach the OTA server. seems like a general connection issue on your site?!
[G4 Android Development] AlboTourus:
well, internet working on both. no problems with it. just that 204 answering server unavailable from my side for some reason
[G4 Android Development] steadfasterX:
what happens when you open the OTA url in a browser?

e.g.:

https://sfxota.binbash.rocks:8010/e-os/pie/api/v1/h815/custom/get
[G4 Android Development] AlboTourus:
Weird, after i opened it in browser, it start working fine, reporting about "no updates"

Btw did you changed "no internet" url? cause iirc by default it have to be some gstatic.org(google domain)
[G4 Android Development] steadfasterX:
eOS removes a lot of google call-home stuff like that one
[G4 Android Development] PH_Android:
No internet connection from WiFi (Connected, no Internet) and no mobile network on mine. Did not work after a factory reset.
[G4 Android Development] steadfasterX:
ah ok now I got it. after looking into the code I found that the connectivity check in pie was (is) pointing to https://connectivity.ecloud.global which indeed is not reachable (anymore).

I will fix that with the next build.

If you do not want to wait you can execute these commands in a terminal while your phone is connected via adb:

adb shell 'settings put global captive_portal_http_url "http://captiveportal.kuketz.de" '
adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de" '
adb shell 'settings put global captive_portal_fallback_url "http://captiveportal.kuketz.de" '
adb shell 'settings put global captive_portal_other_fallback_urls "http://captiveportal.kuketz.de" '

(source)

after a WiFi reconnect you should get the state "connected" again

A fix will be added with the next build by: commit
[G4 Android Development] PH_Android:
Thank you, this fix works.
[G4 Android Development] steadfasterX:
thx for the feedback! the above fix is included in the update released on 18th of May ;) (maybe keep an eye on the automation channel ;) )
[G4 Android Development] PH_Android:
Thank you, but downloading the update is taking long.
[G4 Android Development] steadfasterX:
yes thats normal when I build (same infra as the leech server)
[G4 Android Development] PH_Android:
Updated now, thank you again for the work
[G4 Android Development] PH_Android:
Hello. Issue solved, can now backup Viber chats to Google Drive. But I had to move to a different ROM (aoleary's crDroid v.9.14, Android 13) and install the latest (13 June 2024) MinMicroG Auto Builder via Magisk Canary.
[G4 Android Development] rotusa:
How stable is this rom?

Hi there!

Atm, I am using your los 16 on my h815(official unlocked). Now I would really want to un-google my device. Any information, how stable this rom is? Comparable to LOS16(which is really great)?

Thank you for your work.:good:
[G4 Android Development] steadfasterX:
Its based on los 16 so.. Other then that I prefer different gps and kernel stuff then in LOS.
[G4 Android Development] nubla:
Once again, thanks for your great efforts, steadfasterX. So far I'm liking /e/ and your defaults in the build, on this newly UsU'd LGH812. It's surprising how well a de-googled phone is working out of the box. I was expecting more challenges.

Btw, bluetooth is working fine for me, with pairing successful initiated in both directions.

Here's a list of current issues/questions/comments. Let me know if there is a more suitable subforum/thread.

The ODBLink app https://play.google.com/store/apps/details?id=OCTech.Mobile.Applications.OBDLink is not functioning quite right in /e/ when trying to download/install enhanced add-ons (free for the MX+). It used to work fine on stock. The internet connection is fine.. EDIT: Support for (in-)app purchases requires the Google Play Store.

The default phone dialer is failing to connect to my SIP account. How can I troubleshoot this too? In contrast, the Grandstream Wave app connected fine. https://play.google.com/store/apps/details?id=com.grandstream.ucm EDIT: The problem was special characters in the password. Setting a simpler password solved the problem.

How to enable automatic call recording for all calls? Ideally from all sources, especially SIP clients. I found a simple Call Recorder app on F-Droid https://f-droid.org/en/packages/com.github.axet.callrecorder/ but it did not record SIP calls, at least when using Grandstream Wave. EDIT: Seems call recording is increasingly difficult in android and requires root, or relying on individual apps' ability to record calls.

Is there a way to delete files/folders with the default file manager? I can't find how, and it would be a big shortcoming for a file manager.. EDIT: Long press on a file or folder and a delete (trash can) option appears at the top of the page. Long pressing also allows selecting multiple items.

Best camera apps? Is there GCam for the LG G4? At first I was a bit disappointed with the default camera app Open Camera, but as I learn more about it, I'm increasingly liking it. The documentation is helpful: https://sourceforge.net/p/opencamera/discussion/general/ EDIT: Still searching, but an old GCam port provides the best image quality so far: https://xdaforums.com/showpost.php?p=83531885&postcount=282 EDIT2: More GCam ports and 60FPS recording playback work after applying the video-lag fix for the G4.
[G4 Android Development] nubla:
What would be the best way to have support for (in-)app purchases? This requires Google Play Store. Details: https://github.com/microg/android_packages_apps_GmsCore/issues/617

There is a patched version of Play Store for microG which can be installed

manually: https://gitlab.com/Nanolx/microg-phonesky-iap-support

with the NanoDroid package with or without Magisk: https://gitlab.com/Nanolx/NanoDroid

I would prefer to avoid rooting, or using Magisk, or changing the system to the point of breaking OTA updates. What approach is recommended? Could it be included in the build?
[G4 Android Development] breversa:
NanoDroid’s patched Play Store can be installed through TWRP/SHRP without having to root or install Magisk, AFAICT.
[G4 Android Development] nubla:
Yes, but installing the NanoDroid package without Magisk makes changes to /system, which I'm guessing might break OTA updates or cause issues.

The NanoDroid-microG package (with or without Magisk) ends up overwriting the /e/ ROM's microG installation and settings.

When using the NanoDroid full package and specifying with the .nanodroid-setup configuration file to install only the Play Store (Phonesky) and not install microG, NanoDroid still ends up installing utilities and init files. Maybe I'm doing something wrong, but using this method I find no Play Store app installed afterwards.

By default NanoDroid has a lot of de-googling and reconfiguring procedures which, although great for most ROMs, are probably unnecessary and undesirable on /e/.

Still looking, but I haven't found a simple and clean solution yet.
[G4 Android Development] breversa:
I understand. I don't hesitate to root/Magisk my devices, but this has never broken OTA updates as far as I can remember.

But if you really, really only want to have the patched Play Store, why not ask [MENTION=7925618]nanol[/MENTION]x themselves on Gitlab ?
[G4 Android Development] nubla:
Have you done OTA updates for LG G4 LOS or /e/ builds? It does look like Magisk + NanoDroid would be the least disruptive method to get the patched Play Store, but I'm a bit hesitant about Magisk considering how deep its changes are and due to the FAQ:

According to the documentation it should be possible for NanoDroid (with or without Magisk) to install just the Play Store by using the provided custom configuration scripts, but either I'm doing something wrong or it's not working that way. Discussion is ongoing with Nanolx.

Since [MENTION=5545101]steadfasterX[/MENTION] built this /e/ ROM, it would be nice to hear an "official" recommendation of what might work best. If the ROM could be built with the patched Play Store that might be simplest for end users, since I imagine many others want (in-)app purchase support as well, though including the Play Store may go against the purest intentions of /e/... Still, it might be a pragmatic approach that many probably want, especially if enabling it can be made optional with it disabled by default.
[G4 Android Development] rotusa:
Android 10?

Hey, one more question: Is there any chance for Android 10/11 in the next time? I'm asking because I'm not such a fan of configuring my mobile phone, therefore I would wait switching over to /e os/ if there will be major updates.

Ty,
[G4 Android Development] breversa:
I’m pretty sure I did on my non-daily phone, without issue. :)

Also, often the "no support if using Magisk (or anything else)" by ROM maintainers means "even less support guaranteed, by if you show your willingness to investigate, report and/or document, I *might* help you anyway". If you have a collaborative mindset instead of a client one, you should be fine.

---------- Post added at 13:37 ---------- Previous post was at 13:32 ----------

You should head over to the /e/ Foundation forum and ask about it : https://community.e.foundation/

[MENTION=5545101]steadfasterX[/MENTION] "only" ports /e/ OS for the G4.
[G4 Android Development] steadfasterX:
Android 11 is far far away.

Android 10 (LOS) has been ported to the g4 almost a year ago already but still having big issues preventing a release, see here https://github.com/Suicide-Squirrel/issues_a10/issues/ so nothing which will be solved in the next weeks/months/maybe never. These are valid for /e/ as well ofc.

keep in mind that my builds use signature spoofing support in "restricted" mode, i.e. only apps which are included within the BUILD will get that permission.

I have absolute no experience with nanodroid though so no idea about what they do and how they inject but I can imagine that the "restricted" spoofing support might prevent things. check out the OP for a link and details on that.

about in-app purchases I am not sure what the best way would be tbh.

I would prefer that approach if that really works: https://community.e.foundation/t/root-aurora-store-install-methods/14939 in combination of https://community.e.foundation/t/tomtom-use-without-google-play-store/14095 . That comes with a drawback though: the possibility of getting locked/blocked by google bc of using an unsupported app store.

Check also this: https://community.e.foundation/t/purchased-apps-from-google-play-store/5982/8 (what applies to YALP applies to aurora as well). that thread might be an interesting read as well btw. and.. if you wanna read more: https://www.androidauthority.com/google-account-banned-1054640/

The phonesky approach won't work as well when doing that as a user: https://gitlab.com/Nanolx/microg-phonesky-iap-support . The reason is that my builds are SIGNED and so it will reject the patched store as I am the only one with access to the build private key (obviously). So that one would work only when including that in the build process and I am not sure if there would be any conflicts with any other component of /e/ or microG which is included.

last but not least selinux might step in here as well.
[G4 Android Development] nubla:
Aha! That explains why the NanoDroid system installation method fails: it needs signature spoofing permissions (which I don't know how to grant). For some reason I was under the impression that "restricted" mode of signature spoofing meant it is restricted to system apps, not just apps included within the BUILD manifest.

NanoDroid using the Magisk method works fine and then in-app purchase verification succeeds. The downside is that it also overrides other things in the build, like using it's own microg version and settings. Plus banking apps then warn about a rooted phone.

The Aurora Store trick with using Root installation method might be relatively simple if it works. But it still requires rooting the phone, which I'm trying to avoid if possible. Also, it's not clear to me what Root installation means: I certainly don't want the app installed as root or to have root permission. I suppose I could make a backup and try.

I'm thinking the cleanest approach for a user would be to include phonesky (patched Google Play Store) instead of fakestore in the build. Would you consider that? NanoDroid (optionally) installs a whole bunch of other apps/tools, including microg, and while that may be useful for some, I think it ends up being redundant for /e/. Would you consider trying to include only phonesky in the build? This way rooting is avoided and there is less chance of messing the system up with Magisk. I'd be happy to test and provide feedback.
[G4 Android Development] steadfasterX:
yes it seems including phonesky is the cleanest approach. I just don't know if there are any drawbacks doing so. whats your phone model? h815? UsU or official unlocked?

.-
[G4 Android Development] nubla:
h812 UsU
[G4 Android Development] steadfasterX:
ok that was tricky.. I now had the time (I didnt tbh but I wanted to finish that) to check Phonesky iap.

The thing is: that process will provide the google play store at the end (I had thought it would provide a bridge or something but anyways). The process is to download google play store, unpack, patch, re-pack, sign it. and what you get at the end is google play store working in /e/.

I went through all the steps manually as none of the automatic stuff worked for me and finally was able to get the patched and signed variant booted.. well that was not straight forward but the README is good enough to get it done.

anyways. my main concern with that is:

1) fully automating the above process is hard but it can be done manually and just added as prebuilt within the build process. problem: when something changes (new google play version, new patch, ...) it needs to be done again and that affects the whole build (may even fail due to that)

2) it adds a proprietary app (google play) and that is what I really do not like to have in /e/

what I can think of is

not

including phonesky but providing a package which the user can install if wanted...

one note: the current patches for phonesky are up to v20.9 (atm v24 is the latest) so that is never the latest and greatest play store available.

I was not able to fully test the patched play store though, just started , logged in, installed 2 apps - don't tested in-app purchases or anything else

maybe on next week I could provide a test-package for you to see if that would work or not.

.-
[G4 Android Development] nubla:
Many thanks for looking into this!!

Perhaps the author of phonesky-iap / NanoDroid could help with making the build easier to automate. He was very responsive on Github with microG / NanoDroid issues. I would ask if I knew what the issue was.

I agree that making the patched play store optional is a good idea, especially on /e/. In fact if you can find any way around having the play store for in-app purchase support, that would be fantastic, but it seems it is a hard requirement.

I also wonder if installing the play store to do the license verifications and then uninstalling the play store would work, at least for my case. If possible, I will test this.

Btw, I also contacted the developer of the one app I need that uses in-app license verification of hardware for downloading (free) add-ons, and they responded with:

Google or Amazon, what a choice. Good thing there is a third option.
[G4 Android Development] coldHbullet:
Help with mobile network

any one can help I lose my cellular network
[G4 Android Development] 4ngl09669:
This ROM is the best for LG G4, THX steadfasterx !
[G4 Android Development] breversa:
Hello [MENTION=5545101]steadfasterX[/MENTION] !

Is your leech.binbash.rocks down ? I wanted to check if there was any build newer than 20200826. :)
[G4 Android Development] steadfasterX:
thats another reason why my TG group (sfX Automation, see OP) exists ;)

.-
[G4 Android Development] breversa:
Err… okay, I guess. I'm not used to Telegram but I'll try and have a look. Thanks !
[G4 Android Development] llarr:
I have been enjoying this for about two weeks now but in the past couple days I've been trying to figure out an issue I have with idle power consumption. So I have been installed gsam, wakelock detector and betterbatterystats. So basically the phone never goes into deep sleep mode, just doze light/deep.

I'm not great with these things but I've narrowed things down I think and the culprit seems to be qcril_pre_client_init for the kernel wakelock. Googling around I see some references to it. There's one suggestion to use service menu to change settings for "fast dormancy" depending on whether my network provider supports it or not. Obviously no service menu on this ROM. But I didn't have to do that on stock and it seems like it might be wrong ally, since airplane mode doesn't seem to let the phone deep sleep either.

So I'm not sure where else to try to make the g4 go into deep sleep mode. If there's any suggestion on what to try or diagnose to see if there is some other issue? I haven't used other rom/versions to see if it is every non-stock or not. Cheers.
[G4 Android Development] llarr:
After googling around I found a suggestion that a soft reboot can fix this and it seems to since now my phone goes into deep sleep mode. I feel a bit silly but oh well.
[G4 Android Development] domx93:
Hi, I come from one year of LOS and today I installed /e/ because I want to try the de-google transition. I have a question, that I had also with LOS: there is a way to install the old LG camera app, or at least an app with the manual controls? I miss that camera...
[G4 Android Development] domx93:
sorry, I just found that in opencamera there are the manual controls (but I did not found them)! Wow this OS looks so great :D
[G4 Android Development] domx93:
Hi, I'm using /e/ now since several days and it's great, thanks so much steadfasterx! :D

I have had just some issues with the battery (the phone turned of when there was still 30% of battery, indeed than I turned on and it worked still some minutes, but probably it's just my old battery fault, I need more time to get an idea).

I have a request: is it possible to remove the option that the camera start pressing two times the power button? I often open it accidentally, and I haven't found the option in the menus...
[G4 Android Development] llarr:
Go to settings and look in gestures and you can turn off the camera shortcut.

I'd guess you might want to calibrate the battery for two cycles or whatever is recommended.
[G4 Android Development] domx93:
ah wow, it was super easy, thanks😅

yes, I also think I need to wait some cycles, and anyway I should change the battery because it's almost died...
[G4 Android Development] breversa:
@steadfasterX

/e/ OS Android Q is coming : https://community.e.foundation/t/e-os-q-alpha-builds-are-coming/20273

Do you plan on building it for the h815 ? :)
[G4 Android Development] steadfasterX:
Well if you can live without cam.... ;)

I build Q eos already for the samsung j5 since some months but the g4 suffers from the cam which we cannot solve it seems. That's why i have never released los 17... :(
[G4 Android Development] breversa:
:eek:

Dammit I didn't know about the camera problem… That's a real turn-down indeed. :-(
[G4 Android Development] steadfasterX:
Ya.. Some other minor stuff as well but cam is the deal breaker here..

Issues · LGgFour/android_issues

Issue tracker for LOS, eOS, AOSCP and any other custom ROM - Issues · LGgFour/android_issues

github.com
[G4 Android Development] breversa:
Would you care to build a last Pie version then ? Or is your e-1.0-p-20200826-CUSTOM-h815 build the latest already ?
[G4 Android Development] steadfasterX:
there is already a newer release (yesterday) ;) only posted in my TG group.. I may stop posting new release infos on XDA completely so better join ;) (find "automation" link my sig)
[G4 Android Development] SomeDooD123:
Loving this ROM after a few ours in! Thanks for keeping this device alive steadfasterX!!
[G4 Android Development] breversa:
Agreed with @SomeDooD123 : you did more to keep that device alive than anyone else. THANK YOU @steadfasterX !!!

If you eventually stop supporting it, I'll be hard pressed to select another device that has all the sustainable features I'm looking for :

- removable battery (would you buy a car where you can't fill the tank ? Me neither. But actually don't buy a car if you can help it :) )

- repairable (the G4 has a 6/10 on ifixit.com. Could be better, but could also be a lot, lot worse)

- unlockable bootloader

- /e/ OS-supported, or at least with either official or very good unofficial LineageOS support

So far, only the Fairphone 3 seems to check all the boxes.

Any other suggestion ?