yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] jjcdennis:
Thanks again for your timely and excellent help steadfasterX.

I installed the rom and rebooted. I am getting various Google Play errors. Google has stopped, Google Play Store keeps stopping - this happens with Play store and other apps when opened, but not all apps. Is this a gapps issue?
[G4 Android Development] steadfasterX:
My post linked by yourself mentioned that issue and the fix (reinstall those crashing)
[G4 Android Development] RealZarazas:
Now that we are on enforced, it light be worth a consideration to make it an official lineage repo, right?
[G4 Android Development] steadfasterX:
Well you can dream of it but I guess that will never come.

There are several reasons for this and mostly due to the way we fixed several things like ril and such because the lineage developers just don't "like" it.

This alone is enough from preventing going official but another big deal breaker here is that it needs an official maintainer and no one of us seems to be willing to do so. Why? Well I can speak only for me: you need to discuss every single commit and this is extremely time consuming and often enough just useless and annoying. Don't get me wrong it's ok to discuss and having rules but I saw too many of useless ones that I will not take it.
[G4 Android Development] conbak49:
Is there any chance Bluetooth will be fixed on this ROM? It's not a deal breaker for me as I don't use it for calls and other than this the ROM has worked great for me. But I do have problems with everything locking up sometimes when I use Bluetooth for playing music. I have to reboot and then everything works again. So really I'm mostly just curious.
[G4 Android Development] treechile:
Non-eu h815, cannot set lock pin

I have my non-eu h815 successfully unlocked and recovery all flashed and working. However with both this ROM and the cypheros 7.1 ROM, I cannot set a pin. The settings app crashes and the unlock mode stays on swip. Then if I try again it asks for my pin, whenever I input one, it crashes.

I have done the FAQ zzz steps for each ROM flash and then did them again for each ROM and the issue persists. What other steps can I take?

Thanks
[G4 Android Development] sdembiske:
First, this is the H812 UsU thread, not the H815 UsU thread.

Two things you can try

:

1). In TWRP, > Advanced > File Manager > data > system > scroll down & delete 'locksettings.db'

2). Do a clean flash of the latest version of the rom (again): in TWRP, wipe System, Cache & Dalvik, and importantly,

format

Data, then install the rom, gapps, reboot to recovery and install preferred root version and if required, Xposed before rebooting system.

Suspect it will be the 2nd alternative that provides the long term solution.
[G4 Android Development] treechile:
Sorry, I didn't notice I was in the wrong thread, thank you for answering anyway.

The first solution is something I have already done, as I am sure you are aware, all that does is remove the pin, no allow me to successfully set a new one.

I will try that second one, the extra reboot in between flashes is not something I have done yet.
[G4 Android Development] fates13:
Video recording not working properly on H12/VS986. Very jerky and cannot record above 1080p. Flash videos in browsers also have issues with stuttering.
[G4 Android Development] conbak49:
So it looks like there's not any more development on this ROM which is completely understandable because it is a great ROM and very stable (for me anyway). Thanks [MENTION=5545101]steadfasterX[/MENTION]!

I'm just wondering if there are other ROMS people are moving to. Are there any Pie ROMS for a USU'd H812? Are people just getting rid of their G4s? I know it's an old phone, but I'm still using mine every day and still love it.
[G4 Android Development] VmasterL:
Pie is becoming very close to ready my friend:)
[G4 Android Development] conbak49:
Most excellent!
[G4 Android Development] thekeemo:
Any info on the 5ghz wifi issue? I cant detect them.
[G4 Android Development] steadfasterX:
If you would had read the OP you would have seen the topic "Known Issues". Then you would have followed the link there which at the end would have leaded you to https://github.com/Suicide-Squirrel/issues_oreo/issues/16

.-
[G4 Android Development] thekeemo:
Sorry I phrased the question poorly.

What I meant to say what causes LineageOS on the LG G4 to have this particular issue when I haven't noticed this bug with other devices in a not too technical way since im not a developer.

Bluetooth issues make sense as this seems to be common with several devices. I just havent seen wifi issues being common.

Thanks
[G4 Android Development] steadfasterX:
That's basically not a bug more a little limitation as its clearly stated what to do in that issue to fix /workaround .

Regarding your other question:

To be able to talk with the implemented hardware (e.g the WiFi chip) you need a driver .

The driver is closed source and provided by the smartphone vendor in binary form(so without sources).

The driver must be compatible with the operating system so android . If it isn't as e.g. LG do not provide an updated android version for the next major release several techniques and ways need to be achieved by developers to let either the driver work with that new android version nevertheless or find compatible drivers from other devices. Like we have done for WiFi .

If no other device has the same hardware and no compatible driver or workaround can be found you're lost. Like we are atm regarding the Bluetooth issue. The only way to solve that is finding a workaround as non other device has that exact chip and a newer android version.

If the hardware vendor would release the source code it would be a perfect world but the most issues in the open-source world comes through missing sources by hardware vendors .
[G4 Android Development] thekeemo:
Thank you that was very informative.

Unfortunately I have wifi issues with my home router even with 2.4Ghz but the rom itself is amazing so I might just have to tolerate it.

---------- Post added at 06:44 AM ---------- Previous post was at 06:37 AM ----------

I have just needed to go back to my G4 after two years of storage because of some issues with my DD, and I am legitimately impressed with it. Camera is better than I remember, battery lasts longer than the S8 and S9 and everything is very smooth. I had to stop using it because the sim card tray doesnt work, but now im considering repairing the tray and making it the new DD.
[G4 Android Development] steadfasterX:
well you are the only user having that issue on 2.4 GHz at least so either:

your bootloader stack is outdated

or your WiFi router just act weird

For the first ensure you have flashed at least the 20x bootloader stack. I have just created TWRP flashable ones for convenience.

For the second well.. play around with the settings but I guess you had already without much success.

when you say "wifi issues even with 2.4 GHz" what does that mean exactly? Consider to provide a logcat exactly as described in my signature - but first ensure you are on a current bootloader stack,

.-
[G4 Android Development] thekeemo:
80% sure it's my network as my work network and the transit networks work

My router is set to 2.4ghz, N only, channel 1, 20mhz bandwidth only

Here's the logcat

https://pastebin.com/mN2mwb87
[G4 Android Development] steadfasterX:
so it seems that wifi connects just fine . but..

then several things happen:

02-27 19:29:47.093 D/WifiPermissionsUtil( 933): Denied: no location permission
02-27 19:29:47.093 D/WifiPermissionsUtil( 933): Denied: The current config is not for an open network.

02-27 19:29:55.270 V/b3:onWifi:changed( 8695): create components, onWifi: false, firstLoad: false <-- TunnelConfig(wifiOnly=true, firstLoad=false, powersave=false, cacheTTL=86400), Thread[tunnel-ctrl,5,main]
02-27 19:29:55.278 W/gscore-worker-2(23402): type=1400 audit(0.0:10118): avc: denied { read } for name="u:object_r:net_dns_prop:s0" dev="tmpfs" ino=13609 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:net_dns_prop:s0 tclass=file permissive=0
02-27 19:29:55.278 I/chatty (23402): uid=10105(org.blokada.origin.alarm) gscore-worker-2 identical 1 line
02-27 19:29:55.278 W/gscore-worker-2(23402): type=1400 audit(0.0:10120): avc: denied { read } for name="u:object_r:net_dns_prop:s0" dev="tmpfs" ino=13609 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:net_dns_prop:s0 tclass=file permissive=0
02-27 19:29:55.283 V/b3:onWifi:changed( 8695): loading from the persistence <-- /data/user/0/org.blokada.origin.alarm/files/io.paperdb, Thread[tunnel-ctrl,5,main]

02-27 19:29:55.284 E/libc ( 8695): Access denied finding property "net.dns1"
02-27 19:29:55.285 E/libc ( 8695): Access denied finding property "net.dns2"
02-27 19:29:55.285 E/libc ( 8695): Access denied finding property "net.dns3"
02-27 19:29:55.285 E/libc ( 8695): Access denied finding property "net.dns4"

The first one is an issue which you can find sometimes for Apps handling the WiFi connection.

The second is clearly a denial of selinux for (it seems) this app https://play.google.com/store/apps/details?id=org.blokada.alarm.dnschanger&hl=en_US which tries to change critical system settings (DNS) and is not allowed to. This together with the fact how that app works (providing a local DNS server and then force Android to use it) will cause issues with your internet.

My first try would be to set selinux to permissive and see if your issues are gone. if so then it is very likely that app.

Next step is (regardless if what the first try gives) to remove that app an/or even re-install/wipe data to be sure its 100% gone. Then try with selinux enforcing if your issue is gone

.-
[G4 Android Development] thekeemo:
The app is not the issue.

Using the app I can connect to other networks, and occasionally my home network.

And even after uninstalling I have issues with my home network.
[G4 Android Development] steadfasterX:
new build up
[G4 Android Development] Sir Daniel III:
I have a quick thought:

I know this ROM has a YouTube playback issue, but what's the reason for it?

(Just wondering)
[G4 Android Development] sdembiske:
It's primarily buffering issues (creating lags, freezes etc.), on higher resolution video play. For a workaround, refer to post # 1264 in the UsU thread.
[G4 Android Development] Sir Daniel III:
Also, is there ever going to be a fix for the camera? And by that, I mean video recording. The stock camera that comes with LOS + Camera FV-5 is perfect for photos, but videos are a buggy mess.

I'm getting crashes when trying to record video with the LOS camera, and Cinema FV-5 does work, but it's super choppy. 1080p is nowhere near useable but even 720p is pretty bad...

Will there ever be a fix for this? (And what might be causing it?)

I'm also noticing that the first second of the video is butter smooth, but then it becomes really laggy/choppy. It's actually the same result I get from HD video playback on YouTube. Is it maybe related?

Of course, I can live with these issues, but video recording is a great nice to have.
[G4 Android Development] sdembiske:
Recent New Issues

: [MENTION=5545101]steadfasterX[/MENTION], [MENTION=5461026]kessaras[/MENTION], [MENTION=8699949]ThePiGuy[/MENTION]

- Some of us have experienced of late the phone screen going black when answering a call and the dial pad not working with the phone app indicating it's closing after a number is dialed and call is connected, etc. It seems directly related to the Google Phone app version (11.0) that is installed with the rom/Open GApps. My workaround has been to download from Play Store the latest Google Phone app (do not freeze or remove the stock camera app, as originally thought). However, a couple of things may have to be done then with respect to the app permissions in Settings > Apps & notifications > Phone - scroll down and

allow

Display over other apps and Modify system settings, then scroll back up to > Permissions - click on and turn on all of them listed there.

Seems to have resolved the issue for me so far and has been confirmed by another member with the same issue - bonus for me is that the new version also has a Dark theme setting in the app.

- Lockscreen password, pin etc. not working after a period of time, rendering opening the phone impossible.

No need to re-flash the rom (initially) to be be able to disable the password lock screen. Manually boot into TWRP > Advanced > File Manager > Data > System > delete locksettings.db (the only one present in my installed rom) - some roms may have additional files present: refer to https://xdaforums.com/android/software-hacking/remove-lockscreen-recovery-t3530008 (omission of these, a possible reason why this might be occurring ... ?).

Something to try and remember is to remove your password before backing up the rom in TWRP or flashing a new rom or a new version.

Note

: A clean install (wiping Cache Dalvik cache, System and formatting data) doesn't seem to help overcome this issue in the long run, so I suspect the issue resides in the latest version of the roms as it didn't appear in earlier versions.
[G4 Android Development] thekeemo:
Has anyone been able to get the face unlock to work after the update? I've been trying to get it to work ever since the most recent version came out.
[G4 Android Development] steadfasterX:
Forgot to mention but new build up (April)

Happy flashing ..
[G4 Android Development] steadfasterX:
Hi folks

some users experienced an issue with low video playback rates.

Those interested to test a possible fix (initial version by [MENTION=8854963]Triumo[/MENTION] - thx again dude for sharing) pls read and follow this:

https://github.com/Suicide-Squirrel/issues_oreo/issues/11#issuecomment-482486471

Cheers

sfX
[G4 Android Development] Sir Daniel III:
Alright, so I flashed this zip in TWRP, and I am happy to report that both high resolution video playback (1080p 60fps) and even 4k video recording works now!!! (I used the camera built into Lineage). Thank you so much!

Edit: Even Google Camera Ports work now! I really cannot thank you enough (and Triumo, of course).
[G4 Android Development] steadfasterX:
Awesome thanks for reporting !!!
[G4 Android Development] sdembiske:
Confirmed here working as well after playing my go-to 1080p 60fps testing video (Battlefield 1ps4 on YouTube), that has always given major buffering issues, e.g., freezes, stuttering etc.

All good. Thanks for the great work, [MENTION=8854963]Triumo[/MENTION] & [MENTION=5545101]steadfasterX[/MENTION]. Much appreciated.

S.
[G4 Android Development] Sir Daniel III:
After a bit of usage, I think there might be a little bug on Instagram. When you first open the app up and watch videos it's fine. But once you tap on the video to watch with sound the video doesn't play and gets stuck trying to load. The sound icon on the bottom right also appears then disappears appears disappears repeat.

I'm not sure if this is related to the April patch or the fix as I haven't used Instagram since I flashed the ROM until now. It'd be nice if someone else can test to see if they have this issue too.
[G4 Android Development] steadfasterX:
Make a full backup of the current state.

Restore your previous before-video-patch backup to test if it's related to my video patch or wipe system and re-flash LOS dirty..
[G4 Android Development] thekeemo:
Be wary of the video patch

First reboot after installation and the camera no longer connects

Could be coincidence, could not be.
[G4 Android Development] thekeemo:
After full wipe still no camera connection... This is on the April update.

But I had the patch zip set to install automatically after lineage.

I will try the march ROM again. If not then the camera has probably been damaged at the hardware level. Strange that it would work until a restart.
[G4 Android Development] steadfasterX:
?? I said flash it *without* the patch to identify if the issue is gone .
[G4 Android Development] Sir Daniel III:
Actually, I got this problem too after trying to restore backups. YouTube videos are 144p, 360p and 720p. Camera no longer works, and gets stuck on Landscape mode when you change it to that. I'm going to clean flash the April update to see if any problems persist. Gonna do a full backup this time, and I'll try flashing the fix again.

---------- Post added at 02:41 PM ---------- Previous post was at 01:42 PM ----------

Actually, there's a really serious problem here: Something broke really hard. I wiped everything (including internal storage) and clean flashed the April patch (without the fix). The camera is still broken and you can't connect to it. This isn't good; this is my main phone, and it's crippled. Backups don't work, clean flashes don't work, I don't know what to do! (I still have my SALT backup though...)
[G4 Android Development] thekeemo:
Sorry I wasnt clear. I reflashed with the patch before you told me to do it without it.

I have now reflashed with ONLY the April update and the camera will not connect still, which is a shame because this was my main driver ever since my S8 got stolen, meaning im back to the S4 (and about 15 minutes of battery life) for the foreseeable future.
[G4 Android Development] steadfasterX:
please provide a Logcat exactly as described in my signature and do it when starting the camera

please provide a Logcat exactly as described in my signature and do it when starting the camera
[G4 Android Development] thekeemo:
The camera app no longer appears. I can download gcam and try it with that if you'd like

As far as apps seem to be concerned the phone doesn't have a camera
[G4 Android Development] steadfasterX:
This is absolutely odd so please clean flash the March version and when I say clean / I mean wipe the system partition as well before actually flashing the ROM
[G4 Android Development] sdembiske:
I just did a clean restore (wiped Cache, Dalvik cache, System and did a format Data) of my March backup (after clean restores of my April device backup and then a clean flash of the April rom update). In the March restore, the stock camera appears again but the issues remain - just force closes. My go-to-camera, FV5 Lite reports an error opening camera driver and suggesting a device re-start may be required (it doesn't help), when it too force closes.

This is a serious issue - possible broken fuse ... or ... ?

Sound is not working now as well (will re-flash my modem.bin backup to see if that helps) and phone is screwed as well - not dialing and going to black screen

Phone is now basically useless ...
[G4 Android Development] steadfasterX:
As long as no one following my advice to give a logcat ...
[G4 Android Development] Sir Daniel III:
Oh I already did that. Still the same issue. (Yes I wiped system too).

I'll do a logcat when I have the time to.
[G4 Android Development] steadfasterX:
please provide a Logcat exactly as described in my signature and do it when starting the camera
[G4 Android Development] sdembiske:
Fully intend to, after exploring and getting sound and phone operations working again.

---------- Post added at 05:09 PM ---------- Previous post was at 04:39 PM ----------

May find this of interest: In SALT ...

GPT compatability - unknown

Antirollback - ARB_unknown

---------- Post added at 05:35 PM ---------- Previous post was at 05:09 PM ----------

May find this of interest: In SALT ...

GPT compatability - unknown

Antirollback - ARB_unknown

Here is the SALT log: https://bpaste.net/show/ace2edd0b3c1
[G4 Android Development] steadfasterX:
Nope. If you use the TESTING branch of SALT you have to install all new requirements first. Iirc I list them in the OP already or use the FWUL nightly.

And come on without a logcat I can't help.
[G4 Android Development] Sir Daniel III:
Um I tried doing a logcat using ADB but I couldn't get that to work so I tried using CatLog. This was what I ended up getting from it...

Just saying, YouTube is also broken --> Video quality shows 144p, 360p and 720p for all videos. IDK if the logcat got the camera error but I hope it helps....
[G4 Android Development] steadfasterX:
Thx just a quick one: pls set selinux to permissive as I saw a few denials.

su

setenforce permissive

getenforce

This looks like an issue :

04-13 15:59:51.965 E/adsprpc (2433): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:153::error: -1: dev >= 0

04-13 15:59:51.965 E/adsprpc (2433): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:230:/dev/adsprpc-smd device initialization error: No such file or directory

04-13 15:59:51.965 E/adsprpc (2433): vendor/qcom/proprietary/adsprpc/src/adsprpcd.c:26::error: -1: 0 == remote_handle_open(ITRANSPORT_PREFIX "attachguestos", &fd)

Have to check something but still try the permissive mode
[G4 Android Development] Sir Daniel III:
How do I do that? :D
[G4 Android Development] steadfasterX:
As written in my post above ...the 3 commands.. Enable the local terminal in the developer settings and you obviously require to have the LOS root add-on or magisk installed . Then write these there ..
[G4 Android Development] sdembiske:
Here are the requested logcats. Phone for now has been rendered useless so appreciate any solutions/ideas you might have.

Camera crash: https://bpaste.net/show/ddd919edbaa1

Phone crash: https://bpaste.net/show/f6a6042f508f

Also no sound even with re-flashing modem.bin and installed ringtone indicates # 142, default notification sound # 33, default alarm sound #14 .... ???

Putting SALT to back to stable/Master brought back correct Antirollback & GPT compatability - my mistake and my apologies. A little frustrated as you might imagine.
[G4 Android Development] Sir Daniel III:
Yeah I don't really know how to access the terminal... (I don't think I did it correctly).

(It still says disabled, and my device is rooted)

(BTW another issue is the phone gets stuck on Landscape rotation)
[G4 Android Development] thekeemo:
Camera app disappeared on march build as well

Installed gcam to demonstrate the issue

Here's the logcat

https://bpaste.net/show/08320753f87e

You can also see the wifi issue there as well
[G4 Android Development] steadfasterX:
Try to set selinux to permissive .

su

setenforce permissive

getenforce

stop cameraserver

start cameraserver

Try opening cam again
[G4 Android Development] Sir Daniel III:
I still don't know how to do this. Do you use ADB or do you use a terminal on Android? And how do you know if you did it properly?
[G4 Android Development] sdembiske:
No change.
[G4 Android Development] sdembiske:
Camera logcat: https://bpaste.net/show/cd1a2f136365

Phone is very important, anything to try on that>

Thanks,

S.
[G4 Android Development] Sir Daniel III:
[MENTION=5545101]steadfasterX[/MENTION] So uh, how bad is the problem? Do you know what might have caused it?

(Phone is kinda important... A fix would be awesome. But of course, take your time).
[G4 Android Development] thekeemo:
Is there a way to force the camera app to appear Soni can give a logcat for that instead of just for gcam