yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] aoleary:
In fact this is not available in any ROM, on any device.

You can download an app called "Screen Off and Lock" from Google Play that will do the trick.. Its an old app, but it still works in Pie
[G4 Android Development] jwm20:
HI steadfasterX & team,

First, a big thanks for your continued support of the LG G4! It's amazing what the community has done to keep support for this phone alive.

After ~5 years happily running rooted LP on my Verizon VS986, I finally hit a snag related to Android Auto that forced me to update. I made the jump to LineageOS (6/30 build due to recent GPS issue), and have mostly had success!

There are a few nagging issues that I was hoping to get some help with:

1. After every reboot, there is something wrong with mobile data. Either:

-SIM is "not available" - no apparent mobile data connection. At this point I just reboot.

-Phone connects to mobile data/LTE but SIM status is "Out of Service." As a workaround, the SIM seems to 'activate' if I try placing a call. (The first outgoing call will not connect, but subsequent ones will). After placing a call, the SIM says Verizon and seems normal.

Maybe this can be fixed with a baseband update? Right now I think I'm on MM vs986-2BA. (Is there a way to check? I think I tried a couple versions going from LP->MM...)

2. There is some instability. I don't see much lagginess, but sometimes the screen just locks up (a *lot* at first when reinstalling apps and getting it set up, still a couple times a day). It usually happens when the phone is 'busier' so it might be thermal, what is the temperature threshold? When it freezes, I just pull the battery, and then have to go through the SIM workarounds above after reboot.

3. Drops wifi occasionally - won't show any available networks. comes back after toggling wifi off/on

4. Video recording is not working.

Logs: (I'm not sure how useful this is, collected after a reboot.)

Log with "thermal|kill" parameter: as a new XDA member I can't post URLs, so...

paste dot omnirom dot org/view/476da2a3

Thanks!!
[G4 Android Development] 99913308:
Slimport isn't working?
[G4 Android Development] jovanv:
I recently switched to a new mobile provider, Digi mobile in Spain. The way they configure the access is through data and they require to activate data and data with roaming, I guess because they fetch configuration from somewhere outside Spain. When I run the code for configuration (*148#) it does not report an error. But my phone stays in Roaming mode. I've rebooted and it is still as if I am in roaming. I set SELinux to permissive and tried again the configuration, and no change. After reboot I am still in roaming mode. While I was trying the configuration *148# I took logcat of the radio, and I see some errors there but I don't know how to interpret them. Here is a link to the logcat.

My wife, with her stock phone does not have this problem. I.e. After she configured the phone she is no longer in roaming.

Any help on this will be greatly appreciated.
[G4 Android Development] rundumdieuhr:
First of all, just want to confirm that GPS tracking is without interruption again for me on the newest build.

Thank you both very much for the fix!

Telling from your device model, you are probably affected by a known issue: "vs986: no RIL/cell service on Verizon networks ":

https://github.com/Suicide-Squirrel/issues_pie/issues/41

Please have a look there and see if you can either obtain improvement or contribute your workaround.

On previous builds, I did observe that a couple of times as well (though I didn't share a log). However, haven't encountered it on the newest build yet. GPS has been fixed, so you might want to go ahead and have a try on 16.0-20200719-...

What about sharing some more information to your question? Is this something like a DisplayPort/Miracast implementation? Might be that the following answers your question (no Miracast support unfortunately), but can't really tell from your question. https://github.com/Suicide-Squirrel/issues_pie/issues/18
[G4 Android Development] horvalos:
[MENTION=5545101]steadfasterX[/MENTION] thanks for your continuous work with our G4 and [MENTION=5461026]kessaras[/MENTION] thank you for your comeback it was great news we have you back...Im on Los 16 by day one it published...im on January build because i cant flash and backup every now and then..Now i wanted to flash the latest build but with [MENTION=5461026]kessaras[/MENTION] return i hope for something new...So I'll make the big question to both of you,should i flash the latest build or wait some time for Android 10???

Whatever the answer thank you both for your awesome work...Greetings from Greece happy summer to everyone!!!
[G4 Android Development] OVERHEAT 50:
Hi! I have been trying this Rom on my g4 h815 for a week and everything is great so far. On my device CPU is cooler than others roms (around 50°C while using). I want to thank [MENTION=5545101]steadfasterX[/MENTION] [MENTION=4956374]aoleary[/MENTION] [MENTION=5461026]kessaras[/MENTION] and everyone involved in keeping this device alive. Soon, I want to contribute some money to all of you!

I have been using yowhatsapp and that issue doesn't happen. I tried different scenarios ( taking a picture, sending, taking another one / taking a picture, canceling, taking another one) and nothing unusual happened. If you want to try it's a good mod
[G4 Android Development] kessaras:
yeah there will be android 10 after i fix a few things.

So not yet. it will take a lot of time as i do not make use of all of my free time for this.

Update to latest 9. 10 may take a month +-
[G4 Android Development] rojanor:
Not exactly sure what you wanted me to do, but heres Logcat after running rootbeer sample: https://paste.omnirom.org/view/453d21c7

Please tell me what more I can do :)
[G4 Android Development] steadfasterX:
ah ok got it. I haven't realized it first but it refers to signing here (test-keys).

ok so here what to try:

reboot to TWRP/SHRP

backup system

exec:

adb shell
mount /system
sed -i 's/test-keys/release-keys/g' /system/build.prop
sync

reboot to Android

start the rootbeer sample app again and do that together with the specific log grabbing

share the log again and do a screenshot of the result as well (even if positive)
[G4 Android Development] Root_newvie:
Could the miracast problem be solved with android 10? Also, sometimes the screen goes dark in this ROM when I launch new apps.
[G4 Android Development] steadfasterX:
provide a log as written in the FAQ for a specific issue

.-
[G4 Android Development] horvalos:
Thank you for your reply Kessaras,im not in rush i just wanted to ask the big question about android 10!Thank you for your efforts keep up the good work..??
[G4 Android Development] jwm20:
Thanks, that does sound exactly like my issue with Verizon connectivity.

I'll try the latest build in the next day or so.
[G4 Android Development] Root_newvie:
Does this rom support fast charging? Or is it a rom-dependent feature?
[G4 Android Development] dat_benjie:
[/COLOR]

my battery is fully charged within approx. 1.5 - 2 h :good:
[G4 Android Development] hamed_forum:
magisk hide root dont work?
[G4 Android Development] jwm20:
Hi, to follow up, I did update to the 7/20 build and that went smoothly. I can't say I've noticed it any better or worse.

- video recording still does not work. Is there something I'm missing to get that working?

- I haven't been able to test more than once on the new build, but my biggest issue now is that when plugged in in my car with Android Auto, the battery will not really charge, it might even discharge while plugged in. It also gets hot and will reboot itself after ~20 minutes. Anything I can do about that, or logs to collect for more info? I don't think I'm running anything too demanding, just a podcast app.

Thanks!
[G4 Android Development] osimobile:
[MENTION=10976991]jwm20[/MENTION]

Video recording works with the camera app and other cam apps for me in the latest build, I am using an H815 though.

I assume you have checked the app permissions?

Charging works fine here too and not getting hot.

The one thing I experience since a few builds ago is randomly loosing RIL when I moove. But It might be because I have a Frankenstein (H815) and not clean flashed for a while... Thats why I guess it is my fault...

Big thanks for this awesome Rom to SteadfasterX, kessaras and all involved developers and testers!!!

You rock!!! (G4 is staying alive - staying alive!)
[G4 Android Development] kessaras:
Which variant G4 ??

About fast charge.

The lower the battery , the more mAh will go through.

The higher the temperature of the phone, the less mAh will go through.

If usb charger unknown, case 1: if mAh lower than 150 -> set to 150. Case 500 -> set to 500. Case 900 -> set to 900. If LG charger and if mAh more than 900 -> set to whatever goes through, allow them all.

Max allowed mAh to go through - > 2000mAh.

If more than that, break charge procedure, print error and stop charging.

These four are the basic rules in kernel.

In the code we only read the usb type and allow mAh to go through.

To actually get those mAh , it's hardware related. The cable and the charger (or power bank , whatever that is) quality is most important. Even a scratch on the cable could reduce the mAh from 1100 to 700 for example.

The device usb port could have dust or scratch.

The charger usb port could have dust.

And so on ;)

EDIT:

I = V/R. Anything like a scratch or dust or whatever, increases the resistance, so less mAh go through.
[G4 Android Development] steadfasterX:
video recording: you need to get a log as specified in FAQ #1 - specific issue

charging: you need to get a log as specified in FAQ #1 - specific issue

also a good idea is sharing the debug boot logs as written in FAQ #7

.-
[G4 Android Development] horvalos:
I've installed the latest build and i can say its working fine,with the older build i had issues with battery but with the latest build its like a charm.. I've didnt test Gcam so far,any suggestions will be gratefull..Keep up the good work guys..!
[G4 Android Development] jwm20:
Verizon VS986

I ordered a new battery that should arrive this week, it was pretty cheap and I figure it can't hurt...

logcat for video recording, covering opening two different camera apps: https://paste.omnirom.org/view/79515f1b

Not sure how to log the freeze in android auto because it happens when plugged into my car...

boot_lc_kernel: https://drive.google.com/file/d/10IV6hLNWHEdWEGhpN0pIa5a6LPxsMzSo/view?usp=sharing

boot_lc_full: https://drive.google.com/file/d/1RQr5qyAxushY1KF6aAQKniE87D6wvxPD/view?usp=sharing

(boot_lc_crash was empty)

Again, thanks very much for your help!!
[G4 Android Development] Root_newvie:
I experience heating up during charging. Is it normal in this rom?
[G4 Android Development] steadfasterX:
the reason for your cam issue is

subsys-pil-tz fdce0000.qcom,venus: venus: Invalid firmware metadata

That means the "venus" firmware included with the ROM does not fit the ARB.

Did you ever flashed the Video G4 lagfix mentioned in the UsU OP? That would explain it. If so just re-flash (needs to be done after every ROM flash - as written) and the problem should be gone.

the best way to solve that would be if you have a SALT backup from before UsU:

mount (in SALT -> advanced menu) the system image of your backup and navigate to etc/

copy the full folder "firmware" to a location on your system and use the unmount button in SALT to close the image again.

boot to TWRP/SHRP and mount system in the mount menu

push all the venus* files to the device, e.g:

adb push venus.mdt /system/etc/firmware/

adb push venus...... /system/etc/firmware/

etc

I am not sure if the selinux properties get set correctly so do this as well:

adb shell

restorecon /system/etc/firmware/venus*

Then boot and see if that fixes your issue. If not share just the boot_lc_full.log again.

Regarding your charging issue as described in FAQ #1 - specific issue. Actually if rooted then at step 3 you can just use a terminal app (e.g. enable the integrated one in developer options) and use the cmd "su" to get root. Then as described clear the buffer, then put the charger in, then when you see the issue happened use the next cmd in the terminal app

.-
[G4 Android Development] kessaras:
if you are not bored, there is a way.

when it freeze, unplug, pull out the battery, put battery back in and do not turn on the phone until you get home.

When you get home,

do the hardware button trick to boot directly into recovery and from there pull the logs just like you did ;)

and send them. at the end of the logs there we will see the reason for freeze.
[G4 Android Development] steadfasterX:
This will not work. I described above the way which will work.

the /cache/debug log is just used for the boot process and so stopping after Android has fully booted.

.-
[G4 Android Development] kessaras:
sry thought he froze right at the begining if it's plugged in
[G4 Android Development] jwm20:
Thank you!! I flashed the lagfix and now video recording is working.

And for the freezing thing, when it freezes (after ~15-20 minutes plugged in and doing navigation, it happened once without android auto) it's totally non-responsive - the clock won't change, power button does nothing, etc. I just pull the battery at that point. I'll give it some time with the lagfix applied and with the new battery I ordered to see if either of those help.
[G4 Android Development] steadfasterX:
when the phone gets unresponsive let it run and do not pull out the battery. so do the steps I told you and when that issue happens just leave it on. It will become responsive after some time. can take even several minutes or even an hour but then you can take the logs at least.

.-
[G4 Android Development] kessaras:
Spoiler ;)

It's almost here.

But it won't be released before it's stable enough. It will take some time..... I'm currently on vacation, and I'm officially unemployed and looking for a job !

Sucks ? anyway.

Soon. As I said initially, 1 month.
[G4 Android Development] owlery_hk:
wow. i cannot wait to try this out.

but enjoy your holiday, and dont spend it on developing g4 rom haha
[G4 Android Development] kessaras:
Enjoy it here : https://vt.tiktok.com/yDNYsW/

???

The release is after I get time which is after I find a job haha. I hope soon.
[G4 Android Development] horvalos:
Booomm!!!thank you for the teaser,and the build...:DHappy holidays!!!Hope to find a job soon(after you enjoy your vacations:silly: )
[G4 Android Development] steadfasterX:
using h815 files should be ok but depends on your ARB as well. As you didn't shared that info or the SALT log i can't say for sure though.

Regarding your flashing error:

Always read the FAQ first. In your case FAQ 13 of the UsU thread

PS: use a paste service for pasting logs always ;)
[G4 Android Development] niks412:
ARB is 0 in SALT

I modified 815 UsU ROM as instructed and now it installs ( I tried several versions of lineage OS for 815), but device is bootlooping on restart . Is there a way to install stock ROM so device can be operational ? Here is TWRP log psty.io/f?q=74d . Thank you for your help :good:
[G4 Android Development] steadfasterX:
I meant a paste service like http://paste.omnirom.org or http://paste.bin or http://del.dog

anyways I dont need a TWRP log. I said SALT log but as you say ARB is 0 you are good to go with h815. Well it is a Frankenstein so that might be the reason why it bootloops though.

you can flash your previous STOCK rom from your SALT back or any other as described in the UsU

FAQ

.. (If I rem right I said that before, didnt I?) ;) check FAQ #28 for that.

.-
[G4 Android Development] kessaras:
get navigation gestures of Android 10 at any Android 9 or older

1. Install app - https://play.google.com/store/apps/details?id=com.fb.fluid&hl=en

Launch the app and grant it permissions and enable it.

- No need root - No need adb shell pm grant command -

2. After you enable it, go to developer settings and allow adb root access

3. plug in to pc usb port and open a terminal

do the following:

setprop qemu.hw.mainkeys 1
stop
start

That's all. Enjoy.

If you like it, then you need to open build.prop and find "qemu.hw.mainkeys" and change it to 1. Then you don't have to ever do the above steps on every reboot.~

Edit:

Also you all know about the graphic glitch at the bottom when we use skiagl.

When you use the above method to disable the navigation bar , the glitch is gone. Profit.
[G4 Android Development] Arwel:
Flip flap cover, problem with the magnet sensor

First of all, thanks a lot for this great rom. I am using a LG G4 h815tr. Everything works great except I am having problems with my flip flap cover. Each time I move it, the screen gets locked. I searched this thread and did some research online but couldn't find any solution. Is there a way to disable it? If that involves disabling the magnet sensor completely, I am up for it...
[G4 Android Development] steadfasterX:
what do you mean by "move"? closing it?

.-
[G4 Android Development] Arwel:
When I close it obviously it is not a problem but when I open it and fold it towards the back of the phone, the screen gets locked as well. Also when opened, if I apply pressure to back of the phone or move it a little, it happens too. It is problematic because sometimes I write something and because of how I handle it, the screen gets locked randomly...
[G4 Android Development] steadfasterX:
sounds like you press the power button then as when you fold it to the back it will touch it right?

.-
[G4 Android Development] rundumdieuhr:
No, I can confirm that also my device is a little sensitive in conjunction with the magnetic cover. When the cover is flipped all the way back, the screen locks up without the power button being pressed. This is the same mechanism that locks the screen when you close the cover normally from the top.
[G4 Android Development] Arwel:
No, I don't or it doesn't. The cover avoids it doing that as it is quite thick. The locking happens because of the movement, I can assure you that, I have done different tests. Is there a way or a trick to disable the magnet sensor in this version of the Lineageos? I have gone through the settings and downloaded different apps, couldn't manage to do it.
[G4 Android Development] steadfasterX:
do you both have pocket detection on or off?

EDIT

ah ok got it.. the magnetic sensor detects it as closed due to the magnetic within the cover. when it is too strong android thinks it is closed as normal even when folded to the back.

-.

.-
[G4 Android Development] steadfasterX:
what you can do (quick, dirty, ugly.. but gets the job done):

adb shell
su
rm /dev/input/event2

this will disable the magnetic sensor completely - until next reboot.

I've just tested some basics afterwards - so touch and rotation is still working ;)

when that works for you the next step would be to add it in an init script (likely in /system so you can add/replace it). that way you can also start it not on every boot but when needed only (e.g. start magneticoff). anyways due to the fact that this is deep in the system you have to reboot afterwards to re-enable it (and yes I re-created that device but even when killing system_server and let zygote restart all system processes no luck to re-enable it again without a reboot)

EDIT:

and ofc another option would be to disable that behavior completely on build: https://github.com/Suicide-Squirrel...orks/base/core/res/res/values/config.xml#L311

but I dunno who might find that useful to have..

.-
[G4 Android Development] kessaras:
Obviously magnet is strong and accidentally by the case manufacturer placed at the exact spot where the magnet locks the screen on the back.

You can apply few tests with a small piece of a strong magnet. It's a small spot , how big could it be...., 10mm ???

It's ironic ?

Normally I'd advise you to get another case. If I reduce the magnet strength in kernel, we will lose geolocation accuracy.
[G4 Android Development] cris3:
hello, i don't know well english hereindi use translator, i tried the rom, i had various problems before i could install it, but i succeeded using the penultimate version then after putting the last one. from the tests made there are some anomalies, for example the miracast sees the tv, connects, but doesn't transmit screen, i have a 2017 philips. the workout and round apps, try different, before the vibration worked, now no, it only goes audio. I tried simple pro gallery app, but I use to save the photos on the external memory, but it seems that pie gives problems, once I take the photos, they do not appear immediately in the gallery, but after a while, I'll try alternative galleries and see. Excellent the presence of the accessibility package that I needed, too bad it lacks the possibility coem in nougat that announced the name of the caller instead of the sound. I have to try again the gps, for theresto is fine, maybe the connection to the wind network happens a few seconds after turning on the phone, but cmq calls work well. As camera I put edgecam 2 coem recommended, and I found myself better than the others, also for the fact that it can see the external memory, and save them. Congratulations for the work done, I tried it last year, but I had to take it away from the rom, because it gave too many problems, but now we are almost perfect, it's really incredible, I wish you to find a job soon, because its qualities are rare. If someone has had the problems reported and has solved them, could you give me the solution? Thank you. I have a G4 h815. Thank you
[G4 Android Development] Arwel:
I have tried the first method and it works well, thanks a lot steadfasterX!

I have also discovered that it had nothing to do with the power of the magnet in my case. There is a hidden magnet that was causing trouble. It is placed in the lid, close to the middle of the spine. It triggers a certain sensor on the left side of the phone. Removing it solves the problem. I really don't understand why this wasn't happening with the stock Android 6.0 but problem solved, so I guess it doesn't really matter now.
[G4 Android Development] niks412:
lineage 16.0 h815usu and F500UsU_baseband_flash worked, everything is stable and fast . I 've never used linux or flashed the phone before, but following your instructions now I have great phone. Thank you for your work and patience :) .
[G4 Android Development] kessaras:
H815 Only - NoN UsU - Lineage-16.0

adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot

Flash this kernel and tell me how fast it is, how good everything is, if your overall experience is better and if you have any random reboots.

Report to me here, it's not a secret that i'm upstreaming our kernel.

Tag me when you do. @ my nickname here.

If everything is smooth , changes will be merged to all our roms.
[G4 Android Development] breversa:
Flashing it right now ! :)
[G4 Android Development] breversa:
Okay, so… Flashing the kernel is a no-brainer, but if you're using Magisk, microG, and Signal, you're gonna have some tinkering to do (I sweated quite a lot !) !!

Here's what I did :

Flash the kernel in the /boot partition.

Flash the Magisk zip.

Boot the phone.

From my computer (or from within any phone local terminal) :

sudo adb shell

su

pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

(from https://www.reddit.com/r/MicroG/comments/h9c7w1/phonesky_installed_but_wrong_signature_as_a/)

Reboot

Not sure if needed or not, but I also did the following :

Install Push Notification Tester and run it

Open the phone app and dialed

*#*#CHECKIN#*#*

… and FINALLY, I could get my message through Signal !

Now, I haven't done any other testing beside this so far…