yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] Koubiacz:
Hi,

I just installed this ROM to give a second life to my LG G4.

Overall I find it good but some applications do not work.

Apps didn't work, I uninstalled it via adb to use something else.

Maps doesn't work, but I can't find how to remove it. How can I do it?

Edit : I also just realized that it is impossible to install applications with Aptoide
[G4 Android Development] steadfasterX:
What means "does not work"? Did you also checked the FAQ for replacement apps ? Maybe there is something useful there.
[G4 Android Development] Koubiacz:
I can install Apoide via the apk but when I want to install an application from the store (Aegis or maps), it displays "Something went wrong".

With the "APPS" application preinstalled, as I want to install an application from the store (ex maps), "APPS" crashes.

Before installing the ROM I did a complete wipe (I formatted all partitions completely) as it was indicated in the FAQ
[G4 Android Development] Koubiacz:
Searching on my side, I have the impression that the storage is badly detected. When I launch the gallery I get an error message "No memory, no external storage detected".

I did the test with 2 SD cards, formatted with the phone.

Maybe that's what makes the applications bug?
[G4 Android Development] steadfasterX:
Hard to say without logs.. Read the FAQ..
[G4 Android Development] DarrenNewsgroup:
I am trying to resurrect my old H815 but first I need to get some data off it. It currently has an official unlocked Nougat bootloader, rooted v29a firmware with a pattern lock. I can't remember the pattern lock so I thought "boot into TWRP and remove the pattern files" (gatekeeper?).

That is where I have now got stuck.

To boot into TWRP I used to hold down VolumeDown+Power until the first LG logo appeared then release power button for a second then press it again whilst keeping the VolumeDown key pressed at all times. With the Nougat bootloader I now get a warning message that the phone could not be checked for corruption. Part of this message involves pressing the Power which, at this point, I am already pressing. I tried several combinations and trying to release the Power button at different stages but could never boot into TWRP. As I can't remember the pattern lock I cannot bit into the phone normally and then select BOOT TO RECOVERY so without the correct key press sequence I am stuck in a chicken and egg situation.

Can someone help me? Is it actually possible to get back into TWRP in my setup?

Thanks

Darren
[G4 Android Development] Koubiacz:
Hi,

I tried to follow the procedure in the FAQ, but in the /sys/fs/pstore/ folder (in root) there is absolutely nothing as files.

There is no other precise information in the FAQ.

I don't know much about this ROM, is there a place where logs are stored, like a /var/log under Linux?
[G4 Android Development] breversa:
Hello @DarrenNewsgroup,

Since your issue is not /e/ OS-spetific, you May have better luck posting it in the generic G4 troubleshooting subforum.

Also, providing the full message and picture of it could help greatly.
[G4 Android Development] Koubiacz:
Hi,

Sorry for the delay I had a week... complicated

boot_lc kernel

https://paste.systemli.org/?e62ac1aaa5228961#GAQ4XuRxKt92YSmf2qTGQsNDx2CdRUnL4NVTSYFmAuXJ

lc_full

https://paste.systemli.org/?5ab0de708644a640#EMjJ4tZkF9ZfCaFsKut6JgxbvnYZ2DJRyzRbZNJ4ns6k

lc_crash is empty
[G4 Android Development] Tribux:
@steadfasterX HI, what is the latest update?

I have 1.0-20210307, and OTA doesn't detect anything else :/
[G4 Android Development] nubla:
See post https://xdaforums.com/t/rom-unoffic...le-hello-privacy.4142021/page-8#post-84866689

In particular:

But besides that, OTA is not checking for updates automatically for me on v0.17-20210607. Last checked is June 30, 2021 which was done manually.
[G4 Android Development] Tribux:
oough, I have not been here for too long :/

Thank you ;)

What source is more updated now or which one should I choose for update :)

https://leech.binbash.rocks:8008/e-os/pie/h815/?C=M&O=A

or

https://images.ecloud.global/dev/h815/
[G4 Android Development] nubla:
The dates show that.

Only you know the answer to this. eg. I prefer steadfasterX's custom builds instead of unofficial and official ones:
[G4 Android Development] steadfasterX:
;)

Edit:

Details in the automation TG group
[G4 Android Development] nubla:
zomgomgomg!!

What a great feature for those with paid/licensed apps! Is it possible to enable/disable it?

So far I've been using phonesky from nanodroid as a magisk module: enable to get phonesky to let the paid/licensed app to verify its license, then disable the module to avoid google's play store doing it's thing too much. I haven't had issues, but maybe I'm lucky in that the one such app I need turns out to require verifying the license just once.
[G4 Android Development] steadfasterX:
I would say simply sign out when you are done and it should not doing anything. To be 100% sure: open the app settings and choose "disable" ;)
[G4 Android Development] nubla:
Awesome! So flexible.
[G4 Android Development] BY_2020:
Hey!

was using steadfasterX-LOS-16 and worked fine. Great work!

Now i want to give /e/ a try but encountered a major issue.

When calling somebody my H815 (official unlocked, non-usu, 20p, full clean installed e-0.18) says "Calling..." about 20 sec but no ringtone/sound and no connection established.

USSD-Codes don't succeed. LTE Mobile Data works fine.

PrivateBin

Besuche diesen Link um das Dokument zu sehen. Wird die URL an eine andere Person gegeben, so kann diese Person ebenfalls auf dieses Dokument zugreifen.

privatebin.at

(P.S. ist there any AudioFX substitute? i miss it)
[G4 Android Development] steadfasterX:
this does not happen on LOS 16 ?

does it make a difference when using the speaker instead of the earpiece?

if possible can you try with a headset just to exclude any issues in that area..

then last but not least: try the latest /e/ 0.17 build as well pls
[G4 Android Development] Anthonyucky:
H
[G4 Android Development] BY_2020:
Yes

No

Same issue with headset

checking.... same issue (e-0.17-p-20210607-UNOFFICIAL-h815)

PrivateBin

Besuche diesen Link um das Dokument zu sehen. Wird die URL an eine andere Person gegeben, so kann diese Person ebenfalls auf dieses Dokument zugreifen.

privatebin.at
[G4 Android Development] nubla:
Upgraded to e-0.18 and it's looking great. The update went smoothly, and I dunno if it's just me but it feels snappier than the previous version.

Generally no issues to report so far except that Play store doesn't want to launch. It stays stuck on the splash screen:

I cleared the app's cache and storage, signed into my google account on the phone (shudders), and didn't notice relevant errors or messages in logcat. Any ideas?
[G4 Android Development] steadfasterX:
Tbh I was not able to test it on the g4. It worked on the j5 and OP7T so didn't expect an issue here.. Well but the g4 always need some extra sausage.. Anyways could you pls set selinux to permissive and follow FAQ 1 - "specific issue" and share the log
[G4 Android Development] nubla:
Hope it helps https://paste.centos.org/view/07995bd6
[G4 Android Development] steadfasterX:
That was helpful thx. I guess this is the related reason:

GmsAuthenticator: java.lang.SecurityException: Permission Denial: reading org.microg.gms.settings.SettingsProvider uri content://org.microg.gms.settings/auth from pid=0, uid=1000 requires the provider be exported, or grantUriPermission()

will look into that asap.
[G4 Android Development] steadfasterX:
@nubla ok found the issue. first I thought it is a missing permission xml but it turns out there is a bug in the current implementation of GmsCore.. (details)

fix (will hopefully be included in the next build):

1. download: this

2. update it like that:

adb root
adb remount
adb push com.google.android.gms-212158042.apk /system/priv-app/GmsCore/GmsCore.apk

3. reboot

you can do the above also in TWRP/SHRP of course.

After that Phonesky will run just fine.
[G4 Android Development] nubla:
Thanks for the quick diagnosis.

I did the above after rebooting the phone into TWRP because otherwise "adb root" complains with "adbd cannot run as root in production builds".

However, after rebooting the phone, Phonesky still does not launch and the logcat has the same warning "GmsAuthenticator: java.lang.SecurityException: Permission Denial: reading org.microg.gms.settings.SettingsProvider uri content://org.microg.gms.settings/auth from pid=0, uid=1000 requires the provider be exported, or grantUriPermission()"

Does the adb push com.google.android.gms-212158042.apk persist after rebooting from TWRP?
[G4 Android Development] steadfasterX:
when doing it via TWRP you need to

1. mount system (hopefully thats the reason why it fails for you) in TWRP manually

2.

adb push com.google.android.gms-212158042.apk /system/priv-app/GmsCore/GmsCore.apk

3. also clearing dalvik cache might be needed as well

then it should do.

the error you got in Android is likely you have either magisk installed (then adb shell + su is the same) or adb root is not enabled in developer settings
[G4 Android Development] nubla:
Bingo! Right on both counts. I needed to mount System in TWRP manually first, and I have magisk installed. Phonesky is now working after:

Boot into TWRP

Go to Mount -> check the box next to System

adb push com.google.android.gms-212158042.apk /system/priv-app/GmsCore/GmsCore.apk

Cleared dalvik and cache for good measure, though not sure this was necessary

Upon rebooting, there was a popup asking to allow or deny notifications for the Play store. Also, confirmed in App Manager that the version for com.google.android.gms is 212158042 (it was not last time without mounting System).

Confirmed that the OBDLink app is now happy to check for "in-app purchase" addons with the modified Play store in place! Success!
[G4 Android Development] steadfasterX:
Finally .. After a looong journey ;)
[G4 Android Development] steadfasterX:
BREAKING NEWS

LG G4 devices are now (ok since a while already) available as OFFICIAL builds!

That means:

I do NOT provide UNOFFICIAL builds anymore (well maybe in rare cases only)

I still continue providing CUSTOM builds

If you are currently on an UNOFFICIAL build then you likely want to move to OFFICIAL now.

Have fun:

Info about LG G4 (AT&T) - h810_usu

Info about LG G4 (T-Mobile) - h811

Info about LG G4 (Canada) - h812_usu

Info about LG G4 (International) - h815

Info about LG G4 (AR,PX,L,P,T) - h815_usu

Info about LG G4 (Verizon) - vs986_usu
[G4 Android Development] breversa:
@steadfasterX YOU'RE AWESOME !!! After years of warning us that "Nope, OFFICIAL's not gonna happen", you did it !!!

I may be fanboying here, but you're my #1 favorite XDA dev. I can only thank your posts once, but I wish I could do it as many times as I've flashed your ROMs to keep my h815 up-to-date for years !!! :love: :love: :love:
[G4 Android Development] Star.H.CH:
Why nexus5x have android 11 ,but lg g4 on pie, these phones have some soc
[G4 Android Development] steadfasterX:
we have A10 working on the G4 for almost 2 years now but never released as we are not able to get the camera working. We had help from different ppl but no one is able to fix that issue.
[G4 Android Development] Star.H.CH:
Thank you for working on g4,

My g4 hardware camera is broken ,& not important , can relase android r or q for g4 ,to work without camera??
[G4 Android Development] nubla:
Anyone else not getting automatic (weekly) checks for updates?
[G4 Android Development] nubla:
Is there a problem with the URL for the OTA update? I see this failure message when trying to refresh manually, even though internet is working.

Logcat shows:
[G4 Android Development] steadfasterX:
as mentioned in my TG group the OTA service has moved to HTTPS and I expected issues like that.

so could you pls try again now?

thanks for reporting

sfX
[G4 Android Development] nubla:
Unfortunately no change.
[G4 Android Development] steadfasterX:
The log please :)
[G4 Android Development] nubla:
But of course.

EDIT: For some reason attachments aren't showing up, so here's a paste: https://paste.centos.org/view/c5e1d7eb
[G4 Android Development] steadfasterX:
could you do this please:

1. set the check to daily

2. on the NEXT day grab the log as described in FAQ #1 and here ONESHOT issue

3. share that log (please ensure it wont get deleted too quickly! either attach it here or create a gist at github or similiar)
[G4 Android Development] nubla:
I did step 1 yesterday, but today when I checked for system updates manually it did not give an error and showed the available update! Do you still want the log?

About the short expirations on pastes, I generally shy away from leaving them up indefinitely in case I forgot to edit out sensitive info in the logs. It would be nice if they could be automatically sanitized. Even better if they could be sent directly and not made public.
[G4 Android Development] steadfasterX:
You can do private gists on github and share that by PM if you like.

Anyways yes i reverted a change regarding the OTA to make it work again.

Yes i want the log to investigate the issue where the automatic update check is not working.

This happens in the night so it would be good having that log in the morning.
[G4 Android Development] nubla:
Is there a specific time when the update check is expected to happen?

Right now I upgraded to the latest e-0.19-20210927 ROM (and switched to SHRP!), and I'll monitor whether the update check timestamp changes once 24-48 hours have elapsed.
[G4 Android Development] nubla:
@steadfasterX Update check didn't happen for over 24 hours even with it set to daily. PM'ed you the logcat. Hope it helps.
[G4 Android Development] steadfasterX:
ok weird. I can't test it atm on my site but I saw 2 refs both pointing to the same solution:

Go to apps, display systemapps, and clear the cache of updater

(https://forum.fairphone.com/t/lineageos-15-1-auto-update-check-not-working/46495/7 and https://gitlab.com/LineageOS/issues/android/-/issues/53)

maybe that helps in your case as well?! Can't see any obvious issues in the log..
[G4 Android Development] nubla:
Ok, updater cache cleared. Let's see what happens tomorrow. I didn't notice issues in the log either. I tried a manual check and it did not give errors either.

Btw, the updated e-0.19-20210927 is working well. I don't notice much difference other than a new bouncy effect at the end of the apps list.

The biggest change is that waking the phone from taps on the screen works much better than before! Was something done about that? At least with the two previous releases, the problem with touches not waking the screen had gotten worse.
[G4 Android Development] steadfasterX:
well that is a random thing. sometimes it is better then other times. and no there was nothing done about that specific topic.
[G4 Android Development] nubla:
Weird, but I'll take it!
[G4 Android Development] llarr:
Hihi, just updated to the most recent version of the custom rom (0.19-20210927). I've tried looking around to figure out why but I notice it has the Play Store now. Presumably that is a custom vs unofficial/official eos thing?

Also I figure Lawnchair is included now? because I have two instances of it, presumably because I installed it on a prior version of the os and now it is included? One version has my old layout intact so it's all good.

All looks fine so far, hoping the one commit I see for the g4 about checking wifi every 5 minutes instead of 15 secs fixes the occasional random behaviour I've seen.

Really just curious about the Play Store thing, Cheers.
[G4 Android Development] nubla:
Play Store / patched Phonesky is a long requested feature to be able to use (in-)app purchase license verification, which works only with Play Store. You can go to Apps and disable it if you don't want it.

And yes, the new version of Lawnchair is included in the build.

Btw these changes came in the previous release.
[G4 Android Development] steadfasterX:
See https://xdaforums.com/t/rom-unoffic...ye-google-hello-privacy.4142021/post-85449321

Also i have updated the OP with these details
[G4 Android Development] llarr:
Ok that is cool and yeah my phone didn't autoupdate/notify about updates and so I skipped one version I think.
[G4 Android Development] nubla:
Yeah automatic update checking is still in troubleshooting and not working.
[G4 Android Development] AlboTourus:
Hey. Faced with something weird issues after Full Clean Install.

Installed recent 19 version. Have Apps application installed(guess its /e store), have NO fdroid and NO aurora installed.

Also have no access to file system for some reason(Cant open download and TWRP dirs in Files app)
[G4 Android Development] steadfasterX:
CUSTOM or UNOFFICIAL?
[G4 Android Development] AlboTourus:
Omg... i was blind. installed unofficial and was pretty sure its custom... sorry

Just not paid enough attention to file names and downloaded top one in filelist
[G4 Android Development] MorganXYZ:
Q on SMSs restore...

First, big thanks to @steadfasterX for keeping me in my LG G4

Where is the SMS/MMS message db in /e/OS? I've got (what I think is) a message db out of TiBU from 22.06.21 called bugle_db. I can "read" it with 'DB Browser for SQLite' but have no idea where to put it back in the LG G4 running /e/OS which I installed 22.06.21.

My TiBU no longer works without it's google play authentication :-/

The db bugle_db is some 5.2MB - so there's something in there... According to this www.fonepaw.com, the messages should be at /data/user_de/0/com.android.providers.telephony/databases/mmssms.db but I found bugle_db under /data/data/com.android.messaging/./databases/ when unpacked from the TiBU file com.android.messaging-20210622-014848.tar.bz2. And, when I unpacked TiBU's com.android.providers.telephony-20190101-023553.tar.bz2 mmssms.db wasn't under /data/user_de/0/com.android.providers.telephony/databases/ but might have been under /data/data/com.android.providers.telephony/./databases/ (because that's what com.android.providers.telephony-20190101-023553.tar.bz2 unpacked) if it existed, but it didn't... However, on my phone /data/user_de/0/com.android.providers.telephony/databases/mmssms.db does exist and is 840kB. So:

1. Does bugle_db contain my SMSs?

2. If it does, where should it be restored to?

3. If it doesn't, what does it contain? (Just out of curiosity...)

4. And, if it doesn't, what would my SMSs be called in my TiBU? (Not out of curiosity!)

5. Is there any way to read the SMSs outside of

Any help would be really appreciated
[G4 Android Development] hdfpl:
hello

does the rom version from official /e/ site have the same bugs as this (custom) version?
[G4 Android Development] steadfasterX:
OFFICIAL means 1:1 the same ROM as UNOFFICIAL (!! CUSTOM is different as explained in the OP) just signed with OFFICIAL keys and build and offered on OFFICIAL servers.
[G4 Android Development] steadfasterX:
yes there is.

you have to set it to daily, then reboot and then check the log like that:

adb shell
logcat -b all | grep UpdatesCheckReceiver

you will find a line like this:

then on that time (which is ~24 hours after that reboot usually) do a logcat again (adb logcat -b all) and find the time mentioned. share it from 1 minute before and the next 30 lines.

just for the record: I have tested the above just fine on LOS 16. Hadn't had the time yet to test it on /e/ but maybe you can.
[G4 Android Development] nubla:
@steadfasterX Sent you a PM. There are some messages of processes being killed, like:

I ActivityManager: Process com.android.settings (pid 3939) has died: cch+2CEM
I am_proc_died: [0,3939,com.android.settings,902,18]
I ActivityManager: Killing 3923:org.lineageos.updater/u0a9 (adj 904): depends on provider com.android.settings/.development.OTAProvider in dying proc com.android.settings (adj 902)
I am_kill : [0,3923,org.lineageos.updater,904,depends on provider com.android.settings/.development.OTAProvider in dying proc com.android.settings (adj 902)]
[G4 Android Development] steadfasterX:
Thanks for the logs. Unfortunately i cannot reproduce that here. Here i get the update popup like on LOS..

The only thing which happens before is your app syncthing. Could you back it up and uninstall it for a test? Maybe that consumes too much RAM and the process killer gets triggered due to that..
[G4 Android Development] girdap:
Hey, After I tried and failed to install MM version bootloader. I decided to install over v29a. Even developer explains it's not supported over v29a, it has no problem. I am trying to find a problem but failed. Great, thanks to developer. Better than v29a.
[G4 Android Development] nubla:
Odd, yet I'm not the only one having this issue.

How much memory does the updater need? The phone usually shows ~65% utilization.

I checked the logs over a few days and there are always killed apps at the update time, but not always the same ones. i.e not syncthing. They're also not large apps.
[G4 Android Development] pizza_alarm:
I tested the latest /e/ version on my H815 with the latest TWRP version, but after the phone had started the lock screen often freezes and then the phone restarts. What could be the reason for this behaviour?
[G4 Android Development] girdap:
I have switched to the opengl instead of default skaigl. I have faced many freezes and gliches that was the reason.
[G4 Android Development] girdap:
I can not use android auto with this ROM. It says USB device not recognized.
[G4 Android Development] pizza_alarm:
What is skaigl and how can I switch from skaigl to OpenGL?
[G4 Android Development] steadfasterX:
see FAQ 12.
[G4 Android Development] xDev91:
Perhaps this information will be useful to someone if, after installing the firmware, the internal storage on the device ceases to function correctly. This happens after a full clean install, specifically after formatting the internal storage ("FORMAT data"). If anyone comes across a similar one, here is the solution that the venerable steadfasterX advised me to do:

Boot to fastboot and exec:

fastboot format userdata

I also want to add that after A regular clean and Factory Reset - this problem was not found. So, if after formatting the data you have problems accessing the internal storage, you know what to do. ;)
[G4 Android Development] llarr:
I split my home wifi network between separate 2.4ghz and 5ghz networks. My phone gets good signals to both, but only about 1mbps while on the 2.4ghz connection that claims a decent 70mbps. Phone is fine on 5ghz. Other devices are fine on 2.4ghz. Just this phone with latest update on 2.4ghz only, is an issue. Don't suppose anyone can reproduce?
[G4 Android Development] AlboTourus:
@steadfasterX ota server seems dead for about a week already, cant reach it. Android logs says the same. Download of cached updates also unavailable.
[G4 Android Development] AlboTourus:
Is there a thread on xda about custom /e based on a10?
[G4 Android Development] steadfasterX:
Yes thanks OTA was down but fixed again
[G4 Android Development] 1captainjacknotsparrow1:
Is there still that problem with the e-appstore being suspicious or has it been solved already? Unfortunately your custom-eos-rom is too custom for me. I would only use it, if it had ONLY the appstore changed to aurorastore with f-droid and nothing else changed.
[G4 Android Development] steadfasterX:
If you don't like my custom builds use the official build, then disable the apps app and install aurora + fdroid.
[G4 Android Development] nubla:
Still? The issue is inherent to the design of the /e/ App store, so I don't think it can be "solved". The FAQ explains it. There isn't much else changed, (phonesky is added for paid app support but that doesn't have to be used and can be disabled), and you already mention wanting f-droid and aurora store, so I'm not sure what you find objectionable. Lawnchair?

I've mentioned it before, but your custom builds are exactly as I would like them, so thanks for making and continuing them. Spares me from the hassles of having to make the modifications myself.
[G4 Android Development] steadfasterX:
As a side note: in /e/ OS v1.0 the new app "App lounge" has been introduced which is a customized aurora store and so likely will be added in.the next build(s)