yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kosi27:
Observations with new release

Installed 20200515-build and did three long hikes (13h/8h/11h) with navigation, tracking and many pictures (87/56/86) - so i dare to say something about stability of this release and the difference to previous versions.

Overall result is:

1) stability is much better, but the reason for freezing/sluggish camera doesn't seem to be eliminated (albeit reboot isn't necessarily required)

2) battery consumption is clearly better

3) system UI gets slower after intensive usage of device

During the hikes flight mode active for most of the time. I use OpenCamera with DRO enabled. In former releases (including TEST2-Kernel) camera became nearly unresponsive after ~30-40 photos and I had to reboot.

ad 1)

During the first hike (13h/87 pics) absolutely no problem - dreamlike behaviour. But suddenly when taking the last 2 pics it took very much longer and music player was interrupted.

Decided to *not* reboot - force stopped OpenCamera app and started the hike next day (8h/56 pics). Every ~8 photos camera very slow, sound interupted and messages about not responsive background apps (I've activated background-ANRs in developer options). Force stop of OpenCamera necessary. So in the evening I decided to reboot, because (for me) it seemed that some kind of kernel structure was exhausted and not freed.

No problems on the third hike. But afterward, when using other apps, I noticed that starting of apps or switching apps took more time. Everything worked, but it felt much slower.

ad 2)

I use a 6000 mAh battery - with navigation and tracking I've always had a battery consumption of ~ca 12-15% in 2 hours. Now (on all three hikes, also the "problematic" second) there was ~8-10% in 2 hours. Much better!

Maybe these observatins are useful. Greets!
[G4 Android Development] Feduz:
works good, but in games is very slow.. with nougat was faster
[G4 Android Development] steadfasterX:
Your issue is:

"No Bluetooth Address"

Share the log from FAQ #7 and we get that fixed when I'm back from my vacation .

If u can't wait share these logs in ANY case and add your BT addr in /data/misc/bluetooth/bdaddr manually .

But ofc it would be better to wait so that can be fixed for others which going through that rare situation ..
[G4 Android Development] zwab:
Hi Steadfaster,

Thanks for taking the time out to look into this, especially while you're on holiday.

The log files can be found: (square brackers inserted in the URLs to prevent the Forum anti-spammer from blocking my post)

boot_lc_kernel.txt - https[://]del.dog/motinaduki

boot_lc_full.txt - https[://]del.dog/ettingerin

boot_lc_crash.txt - Not uploaded as the file was 0KB, empty.

As for the workaround you suggested, if I create the file /data/misc/bluetooth/bdaddr which simply contains a single line with any bullsh*t Bluetooth MAC address (e.g: E0-E8-16-93-72-61) do you believe that would get things working again? Does the file expect the MAC address to be formatted with dashes like my example, or with colons? (e.g: E0:E8:16:93:72:61)

If the workaround is not as simple as I make it out to be, I'm more than happy to wait for the full fix when you return from holiday.

Cheers,

-zwab
[G4 Android Development] Hotdogint:
H810 (recovered h812 frankenstein G4) checking in. Updated the G4 back in March and had similar perfomance problems. Been lurking on the forums for a new build and updated to May 15 build a few days ago. Just to let everyone know, everything is in working order. Phone is much more responsive and battery life is back to where it once was (got a ~6000maH battery so we packing). Did everything in order as listed expect for the checksum step, is it the terminal on the phone where you run adb command? If so it couldn't find adb command.

Nevertheless it installed properly. Big thanks to [MENTION=5545101]steadfasterX[/MENTION] and other community members that bring life to old phones.
[G4 Android Development] Leg0V0geL:
I'm on the latest build but I have this issue for a while now. It appeared from nowhere while I was adjusting the call volume. Now it feels like max volume is like 10% of the original max volume and I barely understand the other person even though my phone should be screaming at me. How could I investigate/fix this?
[G4 Android Development] akomakomakom:
No calls or text on VS986

Anyone else have this issue? Everything works on stock ROM but not with Pie. Data works, but no calls or text. Tried flashing MM modem, zero-ing out modem partitions, etc.

I followed instructions in this thread including full clean. Installed lineage-16.0-20200515-UNOFFICIAL-vs986_usu.zip and vs986_2BA_modem.zip

Additional info: It takes several minutes after reboot for mobile network to start working ("No SIM card" for the first few minutes). Calls fail with "Mobile network not available" after about a 30 second timeout.

Update: I also tried this:

I followed these instructions for completely re-installing stock partitions and wiping everything: https://xdaforums.com/verizon-g4/guide-how-to-update-firmware-usu-how-to-t3855522

Booted stock ROM and confirmed it makes calls.

I then I did a factory reset in TWRP and flashed lineage, addonsu and gapps (as per this thread)

Still no calls or text

Update: I found a post by steadfasterX here that says that this is a known issue, I am guessing it's referring to this, which implies that calls simply don't work at the moment.
[G4 Android Development] hteles:
Hi, the format should be

cur_etheraddr=00:00:00:00:00:00

In my case with a usu unlocked :

cur_etheraddr=00:00:00:00:00:00h815_usu

Anyway, on my notes I found:

How to find real address https://github.com/Suicide-Squirrel/issues_oreo/issues/2#issuecomment-405913133 adb shell grep macaddr= /system/etc/wifi/bcmdhd.cal | sed 's/macaddr=/cur_etheraddr=/g' > /data/misc/wifi/config Verify (while still in that adb shell): cat /data/misc/wifi/config

Regards.
[G4 Android Development] tullyp:
akomakomakom,

Well documented problem. Search forum for details. Some vs986's do have RIL (cell service) with this ROM, and now Android2468's Potato ROM is available. At least 2 phones documented to work, mine and Android2468 has one, but don't know why most don't work. See Steadfasterx Github issue #41 for ongoing developments and maybe you can help us work on it..

tullyp
[G4 Android Development] dat_benjie:
Hi, sorry for a possible stupid question.

I used your ROM previously, which was working great, but I wanted to do a reset without Gapps, as to free myself (at least in parts) from Google. In order to this, I did a full clean install, without any errors occurring.

However I encountered one problem pushing the Services Core file to my device:

While in Android, I installed the file, according to FAQ 9 and then, as I don't have root, tried to push the file to the priv-app folder. However, I get the following error:

cannot stat 'tmp/com.google.....apk': no such file or directory. I copied the codes directly from the FAQ, so I don't have a clue, what went wrong. Can somebody give a hint? Because I'd really like to be able to use my GPS.

Cheers!
[G4 Android Development] breversa:
Hallo !

Please bear in mind that you only have to do one of the three options in FAQ #9, point 3.

Personnally, I do the following :

Have you tried it yet ? Does it work ? If it does, no need to go further.
[G4 Android Development] Vetal_ca:
I installed latest lineage-16.0-20200515-UNOFFICIAL-h815 with full wipe etc

open_gapps-arm64-9.0-mini-20200530.zip

Magisk-v20.4.zip

Now, restored GroundWire (Acrobits VoIP). My Push notification don't work

I googled a bit, something vague about GCM and MicroG. Can someone point me to the right direction, where I can enable Push Notification or Google cloud messages

Thank you

[/COLOR]
[G4 Android Development] steadfasterX:
You have to either install gapps or follow FAQ 9
[G4 Android Development] Vetal_ca:
Thank you,

as I mentioned, I've installed open_gapps-arm64-9.0-mini-20200530.zip

Is this one qualify ? Or I have to update with "real" Gapps somehow ?

Obviously, got through every setting to see if there is a missing permission etc. Notification allowed, (Show over apps etc), all required permissions are granted, but no push. Neither with "Test push notifications" nor with real calls
[G4 Android Development] Vetal_ca:
Tried to whitelist my device, as it described here: https://www.phonearena.com/news/Reg...d-services-Android-certified-support_id104243.

P.S. Tested with https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en_CA, notifications forked fine

I will target the Ground Wire now. Sorry for the confusion

Not sure if it was blacklisted, but I've got confirmation

Didn't work

Every setting in application is verified, so I did in Android settings

Two questions:

1. If I installed (at the very beginning) open_gapps-arm64-9.0-mini-20200530.zip , do I need to do (or refrain of doing) from FAQ 9?

2. Is there an application to test, verify, log etc push notification in Pie? To see where problem is

Update:

Tested with Push Notification Tester, https://play.google.com/store/apps/details?id=com.firstrowria.pushnotificationtester&hl=en_CA. This one worked just fine

I'll contact Acrobits (Groundwire) than

Sorry for the confusion
[G4 Android Development] Vetal_ca:
Installed GroundWire beta, notifications are working now
[G4 Android Development] rundumdieuhr:
IMHO GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.9.apk from https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
[G4 Android Development] LukeSlovian:
Hello, I'm currently using LineageOS 15.1 and I have a problem because I can not run the flashlight from the top bar.

I am asking you with a very cordial request for your advice, what should I do?

Does LineageOS 16, Android Pie, have fewer bugs than Android LineageOS 15.1 Oreo 8.1?

I am asking you with a very sincere request for work for users, and for the Author who creates the Development LineageOS system.
[G4 Android Development] steadfasterX:
they really unbanned your account again? sigh..
[G4 Android Development] steadfasterX:
You are the only one requesting it. so no sorry. read on:

https://xdaforums.com/showpost.php?p=75817533&postcount=2

--> FAQ #12

https://xdaforums.com/showpost.php?p=74811095&postcount=2

--> FAQ #15

.-
[G4 Android Development] val1950:
I installed dirty on 8.1, (by mistake) but everything works fine. I reloaded to TWRP and installed Magisk 19.2, I got root (H815) Thanks for excellent ROM.
[G4 Android Development] nesnesnes:
Thanks for the reply! I'm going to see what I get with SALT
[G4 Android Development] LukeSlovian:
Hello Friend. Can you help me ?

I agree I have a temporary problem with my first Google account.

And with the first account on the xda forum.

So I do not log in to my first Google account.

Please help me, because I currently have a serious problem, with my LineageOS 15.1 Oreo 8.1.

I currently have in my LG G4 H815 LineageOS 15.1.

Send me information or no problems, will I go with Lineage 15.1 on Lineage 16?
[G4 Android Development] rundumdieuhr:
Flashlight works once you add the fixed tile steadfasterX has introduced in the May build. Read earlier May posts.

See, compare and decide for yourself on GitHub. IMHO basically, Oreo and Pie bugs are similar.
[G4 Android Development] LukeSlovian:
Does the Flashlight in LineageOS 16 work correctly?

How to solve the problem at this time, with the system restore option stopping, to factory settings on the TWRP Menu Recovery?
[G4 Android Development] steadfasterX:
View attachment 4767146

;)

he has a long story here in the forums.. always coming back after some ban time (while he switched his nick in the meantime)..

.-
[G4 Android Development] LukeSlovian:
Hello, Dear SteadFasterX, I am asking you with a very cordial request for your support. How did you sign the MarshMallow modem on> https://androidfilehost.com/?w=files&flid=239970 I am asking for information because I wanted to download the version under LG G4 H815.
[G4 Android Development] quetzaltr:
ı can't finish android setup in h815tr. 1. I'd clean flash the rom. 2.I'd flash google after open the system to use. for a while

Yeah, we never used pie rom in G4 but ı did choose data copy out via cloud may because of habit.

Now I'm stuck on the screeen of setup,cause ı taking 'android setup has stopping always' respond and my device name changed to ASUS_...

I never met this issue before, so ı'm saying may there is something need to repair in the rom.

May you excuese my english.

....
[G4 Android Development] fi5z.x9:
Flash gapps immediately after flashing rom in twrp. There's an option that says "add another zip" after selecting the rom zip file. You don't have to flash the rom first then boot and flash gapps after.
[G4 Android Development] steadfasterX:
Clean flash the ROM (see faq how)

Choose the correct gapps (arm64, android 9.0) and flash them after LOS .

Do not restore any backup just boot and let the wizard finish.

Backup if all is working. If not do the steps again without gapps and finish the wizard. Reboot to TWRP and flash the gapps .

Also use the latest LOS build. Exactly that issue has been solved in all newer builds . When you report issues you should always tell which LOS build you're running.

Restoring data from a previous major ROM release (i.e restoring a LOS 15.1 backup in 16.0) is failing in 7 of 10 times so don't do it unless you have taken a TWRP backup before.
[G4 Android Development] LukeSlovian:
I am asking you with a very cordial request, for your answer, do I necessarily need to do a modem downgrade for Android Nugat / Oreo - LineageOS 14.1 / 15.1 - to the modem for Android MarshMallow LineageOS 13? Currently, I now have Lineage OS 15.1, before LineageOS 15.1, I had Android Nugat LineageOS 14, then a clean upgrade to LineageOS 15.1. And now I want to upgrade to LineageOS 16. I am asking you for your support. Which specifically to choose the modem version to download - you wrote to use the modem for MarshMallow. Is my LG G4 h815, if I unlocked the bootloader through the official LG website, I also have to do a modem downgrade from what I have now, namely LineageOS 15.1, to a modem from LineageOS 13 - Android MarshMallow?
[G4 Android Development] Korin67:
I have been using LOS16.0 more than a week. I found a strange phenomena. LOS16.0 works perfect, but after some ideling (in the morning when I first use the phone that day) apps do not start. More specifically, when I activate an app by touching its icon, the app seems to start. But, the screen is all white (Music, Gmail, etc.) or all dark (Gallery, Settings, etc) and halt. Android itself seems not stack because I can touch the 'Square' and swipe out that app to finish. Then, I try to start another app, the situation is the same. Is this launcher problem or System are sleeping too deep? Your LOS16.0

works smooth everyday?
[G4 Android Development] Gigio755:
I really love the 25/05 build! thank you sooo much for this great job :cool:
[G4 Android Development] steadfasterX:
its not my daily driver but as you are the only one reporting that I guess its a personal thing (likely an app issue doing stupid things like greenify and such).

if you like do a report as the FAQ is telling when that happens.

.-
[G4 Android Development] Korin67:
Thank you for the feedback. I was thinking what causes the personal problem that does not happen to other users. Now I came across to one possibility. I am using gapps (pico) of 25th May version. This might be newer than other users. The reason I use this new version is that I tested magisk, root-adon, and adb root. Every time I test, clean install with the newest gapps. Now I am trying the gapps of 1st of May version. If the problem gone, the source is the conflict of LOS16.0 and the new gapps. I am testing now. If I find something new, I will report here.
[G4 Android Development] LukeSlovian:
Hello, what is the baseband package ?

The author of this post, Dear Steadfast X.

He gave the name in the instructions baseband package.

I am asking you with a very heartfelt request for support.
[G4 Android Development] steadfasterX:
thx [MENTION=10823473]zwab[/MENTION] for the logs. As it is hard to re-produce the issue here (tried everything which came in my mind) I would prefer to test with your phone.

I have also created an issue for that here: https://github.com/Suicide-Squirrel/issues_pie/issues/49

Could you pls do a backup in TWRP of just the "Bootloader" (just tick that one and backup). You will find the backup in the TWRP folder of the storage you selected. Pls upload that somewhere safe (as it contains your IMEI) and share the link to me by PM.

thx

sfX

.-
[G4 Android Development] verbage:
Hi all, I am running the 20200223 version of this ROM on an H811, and when I make or receive a call, the screen goes black, and there is no way to access it till the other person hangs up, or I plug something into the 3.5mm audio jack (which will turn the screen on instantly). Calls work fine using Bluetooth, and the screen does not go black. For sure, this is an issue related to the proximity sensor, and indeed, after installing a few sensor reading apps like AndroSense and Sensor Box, I can see my proximity sensor seems to be dead even though it was working with other LOS16 versions from before the 20200223 release. I have been living with this hiccup since late February when I first installed the 20200223 release, but since nobody else has mentioned it, and I am partly able to avoid it by using Bluetooth, well, I have not pursued a fix.

Well, fast-forward to today, and I just had an identical problem with an LG G5 H830. In that case, I was able to identify the problem quite easily by luck--a new tempered glass screen protector I had installed on that phone was blocking the proximity sensor, and by simply removing the screen protector, that fixed the problem. However, in the case of my LG G4 H811, this is certainly not the problem as it does not have a screen protector at all.

If you do a search on something like "screen goes black during calls", you will see lots of results from lots of different phones and ROMs. In sum, it is not a problem limited to the LG G4 on LOS16. Many of the fixes that are suggested involve recalibrating the proximity sensor, and that is usually done by punching in a USSD code that will pop up a hidden testing menu. But those codes apparently only work on stock firmwares--they do not necessarily work on LOS16. There are also some apps in the Google Play Store that can supposedly be used to reset/recalibrate the proximity sensor, but I have tried several to no avail.

So I am turning to you all to see if there is a more direct way of recalibrating a G4 proximity sensor. For example, perhaps the current proximity sensor calibration data is kept as a simple text file that I could either manipulate directly with a text editor, or simply delete, and have it recreated on-the-fly during the next boot or similar? Maybe this is just wishful thinking on my part?

Another thought--though I do not necessarily think my H811's proximity sensor is defective because it was working with earlier versions of LOS16, for sure, that remains a possibility. But I already know it is not working at the level of the GUI so trying to test it at that level is not helpful. This leads me to wonder if there is anything that runs at a lower that I could be used to diagnose the proximity sensor? For example, maybe I could fastboot a tools or diagnostic partition and do the analysis there (much like one would fastboot a recovery partition to install it permanantly)? Does anybody know about something like this, i.e. a way to test sensors a level that is lower than the GUI?

Thanks in advance for any guidance you can provide!
[G4 Android Development] steadfasterX:
sounds like a hardware defect. flash a previous LOS version or 15.1 to see if its gone then but I really believe its your hardware. proximity issues are mainly happening due to protection glasses (even when right now there is none but if there were any some of the glue might reached the sensor). if that is not the case its 90% a hardware issue. ofc there is always a chance (10%) that a ROM causes this so your best way to check is flashing STOCK again and not a custom ROM.

.-
[G4 Android Development] dat_benjie:
Hi,

Please excuse the very late answer. I did it first with this step, but it didn't work. So I thought that I had to do these other steps as well. However, as I didn't need the GPS working these past days, I had the opportunity to use this ROM without Gapps and I came to the conclusion that I wanted just the tiniest Google Footprint, as for comfort. :eek:

So I did a reflash and installed nano gapps.

Long story short, thank you for your help (even though belated).

Cheers
[G4 Android Development] verbage:
Ok, thanks for the suggestion--I suspected this would mean going all the way back to stock to verify whether this is a hardware defect or not. I was just trying to avoid that for all the time it will involve :D:D But I will use it as an opportunity to upgrade to your new 20200515 version on the way back.

It would sure be cool to have something like a diagnostics/testing partition image (similar to a recovery partition image) that one could fastboot for basic, bare-metal testing of hardware. Even it was just raw reads of output values from a sensor, at least one could use this to assess whether a particular sensor is still functional or not. I wonder if from recovery, one could open up a shell, and just raw read a /dev node corresponding to a sensor? I really have no idea about how sensors are set up and polled under Android so don't laugh too much as my suggestion!!! But let's take it even a level lower--imagine doing the same thing, but from download mode--that's about as bare-metal as you can get!

Thanks again, [MENTION=5545101]steadfasterX[/MENTION], for keeping the LG G4 alive for many of us!
[G4 Android Development] breversa:
I understand, that's what I did in the past too, until 1- MicroG became easier to install and 2- I realised that even Nano GApps was getting too bloated with Google features I wanted to NOT have.
[G4 Android Development] steadfasterX:
There is such a thing : the LG mini OS. It sits in a specific partition and can be booted from stock from the hidden menu . There are other ways to boot the miniOS but that's complicated so stock will help here as well.
[G4 Android Development] verbage:
A-ha, thanks for the hint. If I cannot figure it out, I will make the long slog back to stock and go from there.
[G4 Android Development] Daniel071:
Constant freezing and lagging

I'm on the LG G4 (h811, build 20200515), and I experience constant lagging and freezing. This happens usually on apps like Youtube Vanced and reddit. The screen would become unresponsive for about 15 to 30 seconds and the System UI would freeze. I set SELinux to permissive and I'm experiencing less lagging however, it still occurs occasionally. I've done some searching on this thread and found that some people had a similar issue.

Here is a logcat for when my phone was freezing:

https://gist.github.com/daniel071/cb0f9a1ff093c8ce7f7e9c65c1a3d458
[G4 Android Development] bel57:
Yes me too, phone becomes slow or start to freeze and takes some time to get back to normal - usually a reboot does the trick. Seems like a common issue on Pie roms, says that the UI/interface or current app is not responding.

Anyhoo I'm on the previous version so I'll take time soon to wipe, flash and test the latest build.

Thanks for your work.
[G4 Android Development] Feduz:
I had a similar issue, app were very slow. Than I discovered something useful on battery settings, this function "reduce" the power of app for maintain battery. I have disabled it and now the LG works better
[G4 Android Development] bel57:
Which function? The battery saving/optimizer setting?

Well on or off it doesn't make such a difference, AFAIK that's a random behavior happening here.

Edit: even on charge (not even low battery) sometimes the phone becomes slow.