yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] 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!
[G4 Android Development] 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)
[G4 Android Development] f_4Strings:
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!
[G4 Android Development] steadfasterX:
well then there is not much we can do here. You are on the correct firmware and flashed the right ROM build. so I fear this is nothing we can solve. I wonder why that happens to you only.

There are still things you can try:

1. set selinux to permissive (do not reboot, then test)

2. use a later Android release like LOS 18.1 (just for testing - if it does not occur here it might be a kernel and/or android thing)

3. there's also something new coming - while there is no ETA (https://axp.binbash.rocks) and ofc it might not fit your requirements
[G4 Android Development] f_4Strings:
The chances increase that it could be a problem of age, sim adapters, old plastic or contacts that are no longer perfect on my G4. I repeat that this does not occur with normal use of the smartphone held in the hand or resting on a table (fully working and connected to the internet by wireless or mobile data). Anyway, I realize how rather peculiar and bizarre this is.

Anyway, I'll try and hope to do some tests as soon as I can such as:

- checking the /persist files after a crash/reset

- factory reset

- reverting back to stock rom

- trying LineageOS 18.1 eventually, as well.

Thank you again for everything! 🙏🙂
[G4 Android Development] steadfasterX:
just for clarifying: the boot debug files in /persist are only to debug the boot process and will not show any runtime errors. the only valid logs after such a crash can be taken from pstore.
[G4 Android Development] lookatlgg4:
great rom, everything works ad It should and It made the phone usable again 🙂
[G4 Android Development] jcornell:
Following up on this post (I was on the wrong thread)...I'm not completely confident my bootloader stack is the version required for this ROM, so which should I flash for H812 UsU? I see these options: 20x and 20z.
[G4 Android Development] steadfasterX:
you need at least 20x. 20z is the latest. In any case I would strongly recommend to make a "basic" backup with SALT before doing anything though. just for the case. if you miss this step and you find out that your device is a frankenstein it is better to have these..
[G4 Android Development] jcornell:
Okay great, flashed 20z. I took a full SALT backup first thing so I have that.

Now in installation step 1 you recommend flashing the modem partition from backup if there's a chance UsU baseband was flashed. I was going to do this just to be safe, but I'm confused because you say to flash it "from your back up in TWRP". My assumption was this would be done by booting into fastboot mode and running:

fastboot flash modem ${salt_backup_dir}/modem.bin

But there are also modemst1 and modemst2 partitions. I'm not sure how TWRP is involved so I think I'm missing something.
[G4 Android Development] steadfasterX:
if you flashed the bootloader stack you can skip that step as it contains the modem partition already (which contains the "firmware" and so is misleading named by LG).

modemstX partitions contain e.g. your network unlock state and you should not touch them usually

for the record: you could also flash the modem image from your SALT backup.
[G4 Android Development] jcornell:
Okay so I got this installed and set up and it's great! Except that I can't make or receive calls. SMS, MMS, visual voicemail, and mobile data all work but I don't seem to get any incoming calls (no missed call notification or call history entry either) and for an outgoing call the app says "Calling..." for like 20 seconds in silence and then gives up.

I checked that this still happens with SELinux in permissive mode, but I can't consult your instructions on how to get a logcat dump. It looks like your link shortener for https://bit.do/logcat has gone dead.

I had installed Magisk for root access, but I uninstalled it via the app UI and the problem persists.

I found this info in a similar GitHub issue. Main difference is I'm on an H812. My device is UsU unlocked and I flashed the 20z bootloader package before the ROM. Can you help me fix this? Let me know what I should do next.

Edit: never mind, found logcat instructions here. I'll be sending a log dump.
[G4 Android Development] steadfasterX:
hm weird. also try this: https://github.com/Suicide-Squirrel/issues_pie/issues/59#issuecomment-1009472705
[G4 Android Development] steadfasterX:
and pls also provide the boot logs (see FAQ)
[G4 Android Development] jcornell:
Awesome, poking the network preference seems to have fixed this for me too! Incoming and outgoing calls work, even after rebooting. Let me know if you still want that boot log dump.
[G4 Android Development] steadfasterX:
magic stuff... :D no logs needed as long as all is working
[G4 Android Development] jcornell:
Oops, just discovered another issue. I can take pictures, but the camera (built-in app) won't record video. I can switch from photo to video mode and the viewfinder works, but when I tap record it shows an error message "Serious camera error", and the camera doesn't work at all until reboot.

I'm attaching a logcat dump that captures the crash starting right before I hit record in the app. I found logs indicating a null pointer dereference in native system code (search for "null pointer dereference"). Got any more magic?

https://privatebin.at/?3a6d6716dba06a0b#H2qE8BTHpU3iXfhybssiLVb42ZrA4FEm3ReaLbCJMKBk
[G4 Android Development] sdembiske:
Did you remember to flash the Video-Lag Fix after flashing the rom? If you did, then clear the cache & data in your camera app and see if that fixes it. I have experienced the exact same issue & steadfasterX had to remind me about re-flashing the video-lag fix after every rom install - I then discovered if I cleared the camera data and cache, the problem was resolved.
[G4 Android Development] jcornell:
I haven't ever flashed anything related to the video lag issue, so maybe this is something else?
[G4 Android Development] jcornell:
@steadfasterX Have you had a chance to look into this? Is it possible that the video lag patch would fix this camera issue? I'm a little hesitant to flash it because of the qfuse stuff but if it gets me video recording it'll be worth it.
[G4 Android Development] steadfasterX:
if you never flashed that video lag fix there is no need doing so. it is meant for video playback not recording anyways. i just took a quick look and it might be kernel related. I will need to build and test the latest merge by @aoleary and will let you know when you can test smth

Sent from HD1911 using ReLabs
[G4 Android Development] PH_Android:
I currently have the [R/A11] /e/ OS ROM in my VS986. I'm curious as to what advantages this ROM ([TODAYS-SEC-PATCH-LEVEL], which is based on 9.x Pie) has over the R/A11 one.
[G4 Android Development] steadfasterX:
See https://github.com/LGgFour/android_issues/issues?q=is:issue+is:open+label:android_11 for the A11 one. Also I do not provide new builds for the A11 one anymore. so if you do not care about encryption, selinux and sec patches stay with A11. otherwise I can only recommend the pie build atm, any of the recent @aoleary builds (not all are enforcing or encryption tested though) or AXP.OS when released.
[G4 Android Development] jcornell:
@steadfasterX Any updates yet on the camera issue?
[G4 Android Development] steadfasterX:
not yet. I will need to do test builds first as I have to replace the kernel for that
[G4 Android Development] PH_Android:
From https://xdaforums.com/t/improve-mobile-sim-signal-on-g4-vs986.4652550/, reposting here because this is my current ROM.
[G4 Android Development] PH_Android:
Is there a way to connect Viber and Google Drive in this ROM?
[G4 Android Development] Busterftw:
Hi all,

I got my LG G4 out again that had your LOS 16.1 (I think) flashed but looking into newer versions as that version ran a big sluggish. I'm thinking to use it only for navigation in the car.

I saw it on /e/OS website the G4 was put into Legacy, but you are a maintainer.

Do I understand correctly, that even the Custom builds in the first post are based on Pie and not newer version of Android?

Thanks!
[G4 Android Development] jcornell:
@Busterftw Yes, the custom builds linked are for Android 9. If you look around on the download server you can also find Android 11 builds for the G4. Not sure whether there are separate forum posts for those.
[G4 Android Development] jcornell:
@steadfasterX Any progress yet testing the new kernel for the camera issue? Let me know if there's anything I can do to help.
[G4 Android Development] PH_Android:
Separate forum for /e/ A11 is https://xdaforums.com/t/rom-unoffic...-vs986-e-os-bye-google-hello-privacy.4478815/

But note:
[G4 Android Development] steadfasterX:
Is your SIM a verizon one? If so pls see here:

vs986: no RIL/cell service on Verizon networks · Issue #41 · Suicide-Squirrel/issues_pie

original report: https://forum.xda-developers.com/showpost.php?p=79380937&postcount=176 I am not able to test vs986 ROMs due to the fuses it blows on booting my h815 so this cannot be solved withou...

github.com

Whats the issue?

Sorry not yet. The current titan kernel does not compile on pie and my main priority is bringing up AXP.OS for this device (which turns out to become very tricky)
[G4 Android Development] PH_Android:
Here's a video of failing to link Viber and Google Drive.
[G4 Android Development] PH_Android:
Not a Verizon SIM. I cannot find any info on the use of CDMA by my SIM provider.
[G4 Android Development] PH_Android:
Turns out this is a SIM card issue. Newer SIM card from same provider seems to have consistent three-bar signal.

Maybe because the MicroG version used in the ROM (0.2.24) does not support Google Drive API. Please see https://github.com/microg/GmsCore/issues/1988 and https://github.com/microg/GmsCore/issues/1824
[G4 Android Development] steadfasterX:
how do you have installed viber and google drive? if you do not use the play store it will fail. pls see: https://github.com/AXP-OS/build/wik...o-gcm-available--google-play-service-required
[G4 Android Development] PH_Android:
Installed through Play Store, backup still failed.
[G4 Android Development] steadfasterX:
maybe that is not supported that way but give this one a try: https://github.com/microg/GmsCore/issues/1988#issuecomment-1910083365
[G4 Android Development] PH_Android:
Thank you, backup worked at 50% and then error. No explanation for the error.
[G4 Android Development] PH_Android:
May I ask your help tracing where Viber stores the backup before uploading it to Google Drive? Would this Reddit post be of help?
[G4 Android Development] steadfasterX:
that reddit post has the path where it gets stored so what help is needed? If you wanna know why it stops working at 50% follow the logcat guide but ensure you select a long expiration then (bc i dunno when I can look into it). also start the guide first when you are at 49% or so so it will be not become useless big.
[G4 Android Development] PH_Android:
Thank you very much. The location stated in the Reddit post does not contain the backup, only a .nomedia file with 0 KB. Will keep looking and give updates.

The logcat is available here. Personal info is redacted. I started at 49%, but choose account and back up process looped three times before backup error appeared, resulting in a long log. Model VS986, UsU.
[G4 Android Development] steadfasterX:
from a quick review: could u pls check if battery optimization is disabled for viber?

other then that I do not see any obvious. I mean there are several errors like:

"GmsAuthManager: token present, but expired"

which occurs after(!)

"GmsAuthManagerSvc: getToken: account:[REDACT 1]@gmail.com scope:oauth2: [...]"

which is a bit weird as I would assume that getToken should refresh a token but no idea how microG works internally when it comes to this..

of in line 7720 "GmsAuthAskPermission: Failed to find package null" might be more interesting but again no idea how to fix that..

well and the selinux denials are not related (imho) but you can ofc try the whole thing with selinux disabled again

if magisk:

adb shell

su

if not:

adb root (must be enabled in developer settings)

adb shell

for both, then:

setenforce permissive
[G4 Android Development] PH_Android:
Thank you very much. After disabling battery optimization, backup stopped after 50%, then prompted me to choose an account again, and then tried again up to 50%, then failed. I disabled selinux and same happened. The log file after disabling battery optimization and selinux is at: https://privatebin.at/?fc997efe02e54af7#B8RhBr9RDfPJjPH2vUfx3ukNSoeA2L3oszn9GCd6BTnV
[G4 Android Development] steadfasterX:
ok so not selinux related (was a tiny chance only). so did I get it right that the popup to choose an account is new since you disabled battery optimization?
[G4 Android Development] PH_Android:
I got the popup even with battery optimization enabled. Thank you very much.
[G4 Android Development] steadfasterX:
hm ok. so from what I can see it means:

1. viber requests a token at Google

2. backup starts

3. in regular intervals the token expiry gets checked and at (least at) 50% it is expired so a refresh happens

4. the response contains a hint about "own config permission":

> GmsHttpFormClient: ScopeConsentDetails=%0AThis+app+wants+permission+to+see+and+change+its+own+configuration+data+in+your+Google+Drive%2C+including%3A%0A%3Cli%3EBackground+colors+and+theme%0A%3Cli%3EYour+language+setting+for+this+app%0A

> GmsHttpFormClient: Permission=See%2C+create%2C+and+delete+its+own+configuration+data+in+your+Google+Drive

Which MIGHT be an error reg missing permissions.. or.. is just an info.

Did you ever got something similar to this during the setup (asking for drive / viber / microg obviously)?

Knowledge Base | Duo Security

help.duo.com

Is that app or microg linked in your account correctly?

See https://support.google.com/accounts...ty-apps-have-access-to-my-google-account-data

other then that I am running out of ideas..
[G4 Android Development] PH_Android:
No, I did not get the screen requesting permission to "view and manage its own configuration data in your Google Drive".

Neither MicroG nor Viber appear here as well:
[G4 Android Development] steadfasterX:
hm ok. and when you open the google drive app? can you browse there?

I might asked that before but both are enabled here ?

https://user-images.githubusercontent.com/42837531/207107085-14236392-70f9-453b-8364-62ecb5039fed.png

other then that this is nothing I can help with further. you might wanna check the issues on micog and/or request support from there: https://github.com/microg/GmsCore/issues?q=google+drive
[G4 Android Development] PH_Android:
Yes, I can browse through the Google Drive app.

Thank you very much for the work and patience.
[G4 Android Development] PH_Android:
Hello. This is the reply at Github:
[G4 Android Development] steadfasterX:
Well yea.. thats part of eOS and as that one does not get any updates anymore .. u might wanna try upgrading microg manually but dunno if that causes any issues with the eOS base. So do a full backup before doing anything..
[G4 Android Development] PH_Android:
Tried upgrading MicroG manually, see steps (quoted from my posts on the Github thread)
[G4 Android Development] steadfasterX:
have u checked the microg version after that? do not rename it to GmsCore_orig.apk as this will let Android still load it. rename it to GmsCore_orig.apk.disabled or so instead. atm its not clear which microg version is actually in place due to that
[G4 Android Development] PH_Android:
Thank you. Signature spoofing worked.

1. Cleared dalvik-cache and cache again

2. Removed account from MicroG

3. Cleared data of MicroG Core

4. Cleared data of Google Drive app

5. Opened Google Drive app

6. Signed in to Google account

7. Enabled from Settings > Accounts > Google MicroG the option to "Allow apps to find accounts"

8. Closed Google Drive and Settings apps

9. Opened Viber > Settings > Accounts > Viber Backup

10. Tapped settings hyperlink

11. Account selector showed up

12. Selected Google account

13. Backed up to 50%

14. Cleared log

15. Error backing up from Google Drive showed up

16. Tapped violet back up now button again

17. Account selector showed up, or backing up to 50 percent (did not get exact sequence)

18. Error backing up from Google Drive showed up

19. Opened Google Drive app

20. After a long time loading, Google Drive opened normally

21. Without closing Google Drive app, moved back to Viber

22. Opened Viber > Settings > Accounts > Viber Backup

23. Tapped settings hyperlink

24. Account selector showed up

25. Selected Google account

26. Tapped violet back up now button

27. Nothing happened

28. Tapped violet back up now button again

29. Back up now button disappeared

30. Generated log: https://privatebin.at/?33ba30935ce1375a#DgurscgD1JwkHga4EuzuVwYYc2vLXR7kxTvRTw7z1XR

31. I then checked Play Integrity API Checker: Failed MEETS_DEVICE_INTEGRITY, Passed MEETS_BASIC_INTEGRITY

Battery drained from 17% to 9% during the process, but was plugged in via USB debugging the whole time. Battery optimization for Viber still disabled. MicroG version 0.2.27.223616-1 (4ec0d9f)
[G4 Android Development] steadfasterX:
I hope the microG devs now can help u with that
[G4 Android Development] PH_Android:
Thank you. No reply on GitHub yet..
[G4 Android Development] jcornell:
@steadfasterX Are you still planning to look into the camera issue? Or any recommendations for other custom ROMs?
[G4 Android Development] steadfasterX:
planned.. yes. the thing is I am extreme busy. Besides that I was trying to port the G4 to AXP.OS but the cam does not work anymore at all when enabling selinux on A11 or later. so the whole thing is stuck atm while I'm ramping up AXP.OS for other devices as well..

I may have more time in 2 weeks or so and can hopefully look into that one here again
[G4 Android Development] PH_Android:
Hello @steadfasterX . Thank you again for your help. I have given up on this.
[G4 Android Development] phoohb:
Hi (Im recently installed this ROM).

I keep getting these notification: "Update Google Services. Google Play Store won't run unless you update Google Play services" (but the update don't work, and there is something about "microG" in the settings)

Another question, are there any good replacements for LGs IR-remote-control, FM-player, and better Camera (than /e/ "Opencamera")?
[G4 Android Development] AlboTourus:
Hey @steadfasterX. It seems what OTG server dead again and also internet connection checkpoint
[G4 Android Development] steadfasterX:
you can check these lists for any alternatives:

https://github.com/tycrek/degoogle

https://github.com/pluja/awesome-privacy

I guess u meant OTA and no it is running just fine. check if the ports 8010 (ota) 8008 (web) are blocked on your site. no idea what "internect connection checkpoint" means.
[G4 Android Development] breversa:
The OTA update did not work the first time I used it : the download and install went fine (I'm testing SHRP for the first time), but it did not reboot without action, and got stuck on the LG logo with the LED on.

I reflashed the previous /e/ version, then re-started the OTA update, and this time, I wiped cache/Dalvik cache before rebooting, and all went fine. I'm not sure if it's a mere coincidence or not, but I'm leaving it here just in case.

And again : THANK YOU*@steadfasterX for your work !!!
[G4 Android Development] steadfasterX:
when you say OTA update you meant downloading and flashing it in SHRP manually right? OTA means over the air and is the updater function within the android settings. As noted this function won't work when updating from the prev build so I guess you meant the regular dirty flash.

Sounds like a bug then .. I have tested that here on a h815 (upgrading in TWRP from the 20200802 build) and it worked perfectly fine without any manual cache delete..

Anyways next time grab the recovery log after such a flashing issue occured ;)

Thx

sfX
[G4 Android Development] xDev91:
Downloaded OTA

Perhaps this information will be useful to someone during the OTA update ;)

The folder where the update was downloaded must be searched for by this path:

TWRP has opened and you are in the main menu > click on “flash” , then click on “(Up A Level)” > “data” > “lineageos_updates”.
[G4 Android Development] breversa:
No, when I say OTA, I do mean the updater in Android settings, as I was eager to try it for /e/ (and I actually didn't read that I had to do a clean flash. My bad) ! :)

What I meant is that SHRP did not reboot by itself after installing the update. I had to tap "Reboot".
[G4 Android Development] hamed_forum:
ota doenload and go to recovery but dont install automaticity

i use main menu > click on “flash” , then click on “(Up A Level)” > “data” > “lineageos_updates”. and install regular clean install .phone up but all time error google play service keep stopping

in app info google play service disable and force stop and cant remove it
[G4 Android Development] zeduck:
What about apps that registered to GMS?

Will they still receive push notifications without reinstall them after regular clean flash?
[G4 Android Development] breversa:
Make a backup of your apps using Titanium Backup.

Make a TWRP/SHRP backup of all your device.

Flash the new version.

Test.

If everything's fine, you're good !

If not :

- Deinstall the problematic app(s).

- Reinstall the app from Titanium Backup WITHOUT data.

- Start the app (to make it register with GMS).

- Restore the app's data from Titanium Backup.

If it still doesn't work, you can alway restore the TWRP/SHRP backup you made. :)

EDIT :

Also make sure that you're using MicroG 0.2.11 (https://microg.org/download.html), as previous versions are no longer in sync with Google's recent FCM changes (IIRC).