yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
I saw that a while ago and I would prefer the value of 9 as well there.

I think we should change that in g4 common and remove the duplicates in the device trees
[G4 Android Development] baconbacon:
I have one of those frankenstein g4s that came back from a repair. At first i thought it was an H812 as that's what salt reported it as, I unlocked it using H812's files which worked, installed LOS, etc. One thing that I could not get to work was the modem. The SIM would always be locked and pop up "SIM network unlock PIN" over and over. Although I have the unlock code it would never take.

Anyway I took the phone apart and sure enough it's a H810. Just to be safe I re-unlocked it using the H810 files and redid everything from scratch but I'm still having the exact same problems. I put on G4_29a_N_modem_UsU.zip followed by H810_UsU_baseband_flash-in-twrp.zip before LOS. I could try putting back on the original modem from my backup but I wanted to know if this is a known bug/issue first.
[G4 Android Development] grantdb:
I had the network locked issue as well but all I needed was a new unlock code from the retail store. I had the mainboard replaced so the old unlock code no longer worked.

Cheers!
[G4 Android Development] adam_s_459_:
Hi I'm settling into this ROM right now and I was wondering, what would be the best kernel auditor settings to get a buttery smooth experience? I'm not really sure what all of the governors do.
[G4 Android Development] steadfasterX:
[MENTION=5461026]kessaras[/MENTION] spent hours on finding the best balance between battery life and performance and included the result.

If you still wanna change something search the official aoscp thread by kessaras. some guys wrote there their settings.
[G4 Android Development] n01z:
I ran into a few green screens and when I rebooted my phone, the Magisk app kept crashing. After dismissing the app crash a bunch of weird stuff started happening. Like, no recents screen, the quick settings icons reset (and I lost the edit pencil icon beside the tiny settings shortcut icon- which stopped working as well), lost my brightness slider and most of my settings went haywire.. Had to go straight to reformat and start fresh, this is why I don't have any logs to share.. Sorry about that.

So, I decided to give the LOS root addon a try.. It's about time that a ROM can handle root, even if it's with an addon.

Everything seems fine, so far.

ANYWAYS, I have one quick question about the Status Bar root icon (looks like a hashtag). How do we hide this icon?? I don't see any option under SYSTEM > STATUS BAR > SYSTEM ICONS

My firewall app triggers the root icon, so it's permanent for me.

It's purely cosmetic, I mean, that vendor error popup was worse (by the way- completely gone, now THANKS!! So it was probably for sure a problem on the Magisk side)

The only thing I noticed was under SECURITY & PRIVACY > TRUST > ANDROID SECURITY PATCHES

It shows:

Platform: up to date

Vendor: out of date

I'm not sure if that has anything to do with the vendor mismatch error, but I figure to report that, anyways.
[G4 Android Development] ThePiGuy:
No the vendor out of date thing is based on the last update to blobs etc.

For the G4 this was 2017-07-01 (I think - basically the date of the beta) and therefore lineage considers the blobs to be "outdated"
[G4 Android Development] n01z:
Interesting.. Thanks for the clarification!!
[G4 Android Development] steadfasterX:
I saw many magisk bugs in the past that's why I preferred still supersu for a long time. Then since LOS 15 I just use the LOS add-on without any issues..

When you see the hash it means an app which is using root perms is running. Close the app and it will go away.

So if you have apps running with root permanently you can remove the icon completely like this (I recommend to do a TWRP backup before):

Open a terminal on the phone (or "adb shell")

type:

su
settings put secure icon_blacklist su

That's it.

The icon should disappear immediately.
[G4 Android Development] Bloodyrek:
I did an internal storage backup with the LG App before USU and this LOS 15.1 rom ...Am i able to restore the backup after USU and LOS?
[G4 Android Development] n01z:
Awesome, I used the Terminal and that did the trick!! THANKS AGAIN!!
[G4 Android Development] kessaras:
This is different on every rom. *#*#4636#*#* and count from 1 ++ all network options available.

Otherwise how do you know 12 is unknown ?
[G4 Android Development] grantdb:
Basically the list from here https://www.internauta37.altervista.org/en/patch-fully-enable-gsm-cdma-global-phones-android shows up in a bunch of sites and I assume that it's correct. I can't find an official source.
[G4 Android Development] Bloodyrek:
Does anyone experience touch lag or sometimes have to press multiple times to open a app?
[G4 Android Development] baconbacon:
So far I have unlocked it with both H810_UsU_unlock.zip and H812_UsU_unlock.zip. I have tried both lineage-15.1-20180720-UNOFFICIAL-h810_usu.zip and lineage-15.1-20180720-UNOFFICIAL-h812_usu.zip. And I have tried both kernels h812_usu_los_boot_build-4-oreo.zip and h810_usu_los_boot_build-5-oreo.zip.

Then I decided to try an N rom and gave aoscp_h810_usu-4.2-20180421-unofficial.zip a try, also putting in h810_usu_aoscp_boot_build-55-nougat.zip.

Tried the original modem.bin from my backup (no go whatsoever), tried just G4_29a_N_modem_UsU.zip (no go) and needed to flash H812_UsU_baseband_flash-in-twrp.zip or H810_UsU_baseband_flash-in-twrp.zip each time to make it work.

Interesting to note with both O roms when it would pop up the "sim network unlock pin" and I would enter the unlock code I got from LG it would always fail, and fail instantly with "network unlock request unsuccessful". When I installed the N rom it would pop up, I would enter the code, it would try to unlock and come back with "network unlock request successful" and stop asking. However I don't think it actually did anything as it would never attach to my sim card's network (Virgin). Also on both roms I tried 2945#*XXX# where XXX is 810/812/8xx and it would come back with "cellular network not available" every time, it would never go to the menu.

# adb shell getprop | grep -i "gsm\."
[gsm.current.phone-type]: [1]
[gsm.network.type]: [Unknown]
[gsm.operator.alpha]: []
[gsm.operator.iso-country]: []
[gsm.operator.isroaming]: [false]
[gsm.operator.numeric]: []
[gsm.sim.operator.alpha]: []
[gsm.sim.operator.iso-country]: []
[gsm.sim.operator.numeric]: []
[gsm.sim.state]: [NETWORK_LOCKED]
[gsm.version.baseband]: [3-00070-M8992FAAAANAZM-1.19025.1]
[gsm.version.ril-impl]: [Qualcomm RIL 1.0]

For good measure I took the phone up to a Virgin dealer and let them look at it. They only thing they could confirm was the sim works properly. Was hoping they had some secret sauce tool which might have helped, nope.

This is also a repair/frankenphone, H810 hardware with H812 reported back in SALT https://imgur.com/a/OXyM71w . I'm leaning towards this being a refurb that is borked which is what the people working at the booth also thought.

Anything else I can try?
[G4 Android Development] n01z:
Have you tried using the TWRP flashable MM modem provided in the OP??

"If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP. If you have no backup:

- TWRP flashable MM modems (N will not work)"

The original post has the download link.

If your modem backup was a no go, maybe this will help??
[G4 Android Development] steadfasterX:
So your mainboard front says h810??

What model and firmware version is your bootloader stack then? All issues arrive from here. If you flashed the wrong ones it will not work.

Btw Oreo can take at sometimes up to .2 minutes before you can unlock the sim. You get an unsuccessful message sometimes just try another time a couple of seconds later.
[G4 Android Development] sdembiske:
If you have only removed the back cover on your phone and seen H810 on the plastic part where the battery,sim & SD card are inserted, you cannot assume that your phone is a frankenphone because of that. Many of us that have the H812 have H810 stenciled in that location. It has no relation at all to the internal components or firmware that should be installed. It appears that LG uses what ever is on hand at the time of the model's production run - it is common to see this across different models from what I understand. The ONLY determining factor is what is stamped on your motherboard - and the only way to ascertain that is to open the phone up, remove the plastic part where the battery,sim & SD card are inserted and check what is actually stamped on the motherboard itself.

The determining factor factor, if the above applies in your case, is what is shown in GPT compatibility in SALT.
[G4 Android Development] baconbacon:
I tried h810_21y_modem.zip in an O rom but not the N. Just flashed it on and it seems to detect stuff all the same (IMEI shows, show carriers) but same issues.

This image shows what was originally on it when I got it back from repair. And with Oreo I tried repeatedly to unlock minutes apart, always unsuccessful.

Here is what SALT says is on there now https://imgur.com/a/RQDljUT

Look at the image I posted.
[G4 Android Development] steadfasterX:
The Image quality is crap. Attach it to your post.

Listen: i asked you what your mainboard is showing on the front. You need to disassemble it to get the front. Ifixit website has a guide.

playing around may fix your issue too but imho it's better to make facts.
[G4 Android Development] baconbacon:
Here you go.
[G4 Android Development] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

Colour me impressed. In the space of 17 minutes, you managed to find the Ifixit site, read through it thoroughly, disassemble your phone completely, take the motherboard out completely, take a picture and reply to steadfasterX's post with the picture attached ... Hmm ... or did you ...
[G4 Android Development] n01z:
Yeah, I'm impressed. It would take me 17 minutes just to find a screwdriver that fits.. and another 17 just to muster the courage to open it up..
[G4 Android Development] steadfasterX:
I didn't noticed that your first pic above show the SALT screen

plus

a

part

of the mainboard.. better to split pics like that in the future ;)

ok to sum it up:

you have a H810 (mainboard)

an ARB of 0 (SALT)

last stock firmware was h812 20x (SALT)

gsm.sim.state: NETWORK_LOCKED (getprop)

unfortunately it is still not 100% clear what they actually do when they refurb such frankensteins which makes it hard to suggest something for these devices.

Usually you would flash on h810 devices h810 firmware thats it.

So they either modified the bootloader stack to make it run a bootloader of a h812 (would had likely required a PBL modification - nothing you can do/see)

or it still runs a h810 bootloader stack but h812 Android (would had required a change in aboot to make it load)

or the h810 was always able to boot the h812 bootloader stack (like the h811 ones).

So

a) if you would flash the bootloader stack (!) of a h812 it may hard brick (can be recovered by the sdcard unbrick and using h810 bootloader files)

b) if you would flash a higher bootloader stack of a h810 and it succeeded it will for sure increase your ARB or it hard bricks (ARB cant be reverted!). If it bricks here you may can unbrick by sdcard unbrick again - as long as it was not able to increase the ARB...

c) in any case you need a valid network unlock key which you only get by your network carrier. The NETWORK_LOCKED prop is clear about that: you need to enter a NCK key provided by your carrier or of one of these dangerous unlock websites (I cant recommend a serious one). For the unlock itself I would try a stock ROM first as thats the best option for that. Take out the SIM card and try to boot without the SIM then use the network unlock code by open the network unlock (try those dialer codes from here: https://www.unlockunit.com/blog/lg-does-not-ask-for-the-unlock-code/ - i just refer to the dialer codes I do not trust any of these unlock generator sites)

My personal choice would be b) by using files with an ARB not higher then 0 so you can unbrick with h812 files if needed.

The problem is: the only known firmwares for the H810 with an ARB of 0 are 10A and 10B. And those are not available anywhere.

--> Do not mix that up with H810PR !! the h810pr10a has an ARB of 1 !

So maybe you can find a h810 10e/10f which have an ARB of 1 or you can take the risk to flash a bootloader stack of a h810 10o which has an ARB of 2.

As said it can hard-hard brick so you have been warned (no way other then repair center! really? YES: I AM SERIOUS.)

If you wanna know how your actual bootloader stack is use SALT to do a basic backup. Then check the md5sum of sbl1 and tz partitions with those extracted from the h812 20x kdz.

If they match we know at least that your current bootloader stack is h812. Would be interesting to know as that would help to understand frankensteins a bit better.

.
[G4 Android Development] baconbacon:
Luckily I did a full backup before unlocking it. The md5 for sbl1 is fec6de714224ffb5f7176636fbf98b2d , I checked that against the H81220x_00_0712.kdz I had and they match. tz is 86592707542cc7b7b5863786ec445ce0 and that also matches. So I guess it's an H812?

Also thanks for your help with this. From my searching there aren't many other frankensteins out there so I don't have much to go off.

edit: I also tried all the unlock codes from the site you gave me, all of them return "cellular network not available" rather then taking me to the menu. It does this with both the sim inserted and not.
[G4 Android Development] steadfasterX:
Ok great.

No that does not mean you have a h812. It means you have a h810 with a bootloader stack of a h812.

Which so far means you can flash h812 stuff on your device without bricking it.

You try this on stock h812 android? If not do so. Many hidden codes does not work on custom ROMs.

.... and I would say open a new thread as this goes completely off topic now.
[G4 Android Development] baconbacon:
ok one final question, should I flash from my original backup and try that first (although I don't know that it would work either but I assume it does) and which partitions would I flash back?

Also suggestions for a new thread title? Perhaps something like "UsU on a H810 HW/H812 FW LG-repaired abomination"
[G4 Android Development] steadfasterX:
you can flash from your backup or from the KDZ doesnt matter. You want to flash: boot, system, modem, UsU baseband package

topic suggestion for the Help forum: "[UsU]how-to handle a Frankenstein h810 device?" :p

All other questions in your new thread pls. just mention me (@ + nickname) there so I get an email notifiy.

.
[G4 Android Development] jotaincubus:
Hello... someone have problem with Auto Brightness option...?
[G4 Android Development] grantdb:
Ya sometimes I can't see the screen because so dim after wake up with power button. Never did figure it out.
[G4 Android Development] steadfasterX:
It's a known G4 issue. Happens even on stock..

This workaround fixed it for me and others:

https://xdaforums.com/showpost.php?p=77219900&postcount=789
[G4 Android Development] timn_13:
just wanted to say that this rom is the knees of bees! i switched over from the latest AOSCP 6.0 and have been really pleased running this - its performance is most excellent, battery life is killer and the overall reinstallation went super smoothly (it's actually a little creepy how much app data/settings google backs up these days)! privacy guard is super welcome - i forgot how useful it is and how ridiculous some of the permissions apps expect are, and i'm really happy with the overall performance of the rom.

thanks for the h812 variant of this, it's also really handy not having to strip out the assert lines from the zip! thank you for building and maintaining and keeping our G4 rocking!! i feel rather smug at the moment, having such a solid phone :) cheers!!
[G4 Android Development] sdembiske:
Any chance we might see the rom updated with the August security patches? I understand it has been prime holiday time and developers have other projects, work and lives to lead but I'm getting concerned that as soon as a new Android OS version is out, attention and development shifts immediately to getting that new one operational in the hope that Bluetooth, Torch, Encryption, etc. (or any other bug that befalls the particular rom for that matter) can be solved and the holy grail of Official status can be achieved. There have been no security patch updates for AOSCP N, for example, and are we now facing the same development stall with the shift to Pie with respect to Lineage O?
[G4 Android Development] ThePiGuy:
I'm sure we can get one out.

I understand that it's frustrating having the last build about a month and a half ago. Unfortunately all three of us, as you said, have been extremely busy and therefore very little has been achieved (even on Pie).

Rest assured though, I don't plan on abandoning Oreo just yet ;)
[G4 Android Development] sdembiske:
Thank you, it would be appreciated.

I think until such time as a working build can be uploaded where both encryption and bluetooth can both be deemed to be working in that rom, the developers I believe should give some serious consideration to at least keeping the security patches up-to-date in both AOSCP N and Lineage O so that users can choose what is more important to them, i.e., bluetooth in AOSCP N or encryption in Lineage O and thereby provide the user the ability switch back and forth with their TWRP backups depending on their particular needs at any given time.
[G4 Android Development] timn_13:
this is probably a ridiculous problem of my own making (possibly flashing the wrong modem baseband package after my SALT backup/bootloader crack), but i haven't been able to get data tethering working since i switched from vanilla marshmallow.. i didn't realize it because i didn't try it until the other day, but although i can create a wifi hotspot and connect to it with another device - it won't pass through/says there's no internet to the other device...

anyone else having this problem? i'm going to dig up my SALT backup and restore it and test, then go through and see at what point i break it or if i can just flash a different modem file and stop having problems - but thought i'd ask in case this is something that's been mentioned and i just can't search right? thanks! an i'm very much looking forward to an updated version of this with a more current security patch, cheers!
[G4 Android Development] sdembiske:
You do not need to flash the H812 baseband package (it's only required if flashing the N modem on the stock N rom), if that is what you did on any of the custom N & O roms from the Download section on the UsU thread, just the MM modem alone from your SALT backup. Re-flash the MM modem only first before trying anything else.
[G4 Android Development] kong790:
no sound

i rooted and everything fine. installed lineage OS and everything works perfectly except i have no sound. ive gone trhough all the sound settings and everythings turned on
[G4 Android Development] adam_s_459_:
Flash the marshmallow modem from your salt backup and it should fix that
[G4 Android Development] kong790:
uh oh...i didnt make a backup with salt. how do i get a mm modem
[G4 Android Development] sdembiske:
Download the MM kdz (latest H81220 version, not lower than X) for your carrier from here: https://lg-firmwares.com/lg-h812-firmwares/firmwares/ and extract in SALT.
[G4 Android Development] kong790:
my carrier is WIND canada and its not on the list. which one do i choose? can you give me a quick run through on this as well =] what do i do exactly in salt?
[G4 Android Development] sdembiske:
Wind is now Freedom - I would use Roger's kdz but Telus or Bell should work as well as they all have the same basic bandwidth support and Freedom can roam on any of the three networks.

Suggest you google "extract" or "extract kdz" in the SALT thread. There are a number of posts addressing it.
[G4 Android Development] timn_13:
yeah, i ended up flashing the modem.bin from my SALT backup and found out that i'd already done that at some point when i switched to AOSCP from stock after going the UsU route. it made no actual change in tethering, so i tried all of the modem files i could find and had no luck. (although i finally got to see both the blue and green demigod screens!)

ultimately i rolled back to my SALT backup/marshmallow and my data just works. in exchange, i lost 2 years of security patches and having root, but pokemon go & ingress don't like that anyway and i decided that it was a trade i was willing to make.. i mean, i *really* miss having kernel control and adaway and a bunch of other great things - battery life on stock even with the extended powerbear one is baaaad - but eh, until i replace this device i chose the easier solution to make this work for me. no clue why i couldn't pass-through tether, it didn't seem to be the modem at all but i guess i took the easier way out because ultimately i just wanted to play those games with my girlfriend ;b great glob the stock lg marshmallow is baaaad lol, downgrading came at a cost hahah - lineage is sooooo much better in every metric! cheers
[G4 Android Development] sdembiske:
It seems that a couple of other members have run into the same issue. Refer to post # 627 in the LineageOS O H811/H815 thread, read the related posts and check with the members that had the issue to see if they got it resolved. Try referencing the developers using @, steadfasterX, ThePiguy and Kessaras in your post to see if they can be of assistance and/or consider going into IRC for some direct help in solving.
[G4 Android Development] davidobe:
H.264 playback?

Hi,

Maybe I missed something in the installation steps and I hope someone can help me out here.

I managed to unlock my LG G4 H812 and installed this rom (I tried another ROM too based on Nougat). However, after I installed this ROm, I can no longer play video files without any lags or artefact in them.

My main goal was to use it for Daydream, but it didn't work well and when I tried playing some video files, it didn't work as good as before I unlocked my phone.

So I decided to again re install the ROM and did not configure it for Daydream as I was thinking it was maybe the reason why the videos didn't play well and I still get issues with videos.

I just tried installing Moonlight for my PC and when I tried to launch a game, I got the following message:

"This device or ROM doesn't support hardware accelerated H.264 playback".

So this must be why my videos are not playing well.

So, are the custom ROMs for LG-G4 supposed to play H.264 correctly or it is a known issue? If it is a known issue, what is the workaround?

Thanks!
[G4 Android Development] davidobe:
Nevermind. I tried a different ROM (H815??) by removing the Assert line and following some steps by steps on the forum (can't find the page again as I closed it) and it worked. Moonlight worked without any error and when I tried playing the same video that was causing issues, it was no longer a problem :)
[G4 Android Development] Bloodyrek:
I would really appreciate it if you could find which page you were following the step by steps as i too have issues with the camera in apps, youtube ect ..there's lag with the H812 camera and it seems it's the only G4 variant with that issue.

Which H815 rom did you use and what Assert line are you talking about? How do i achieve that please and thank you in advance
[G4 Android Development] sdembiske:
Note

: You are ignoring your GPT compatability when you consider flashing an H815 rom and running the risk of bricking your device.

Don't even go there

... whatever rom was installed at best it was probably for an H811 which is the GPT compatability for the H812.
[G4 Android Development] Bloodyrek:
I tried using a H811 rom at first but it never worked (unless i was doing something wrong) only a H812 rom was successful
[G4 Android Development] sdembiske:
If the H812 rom worked then what's the problem?

Did you remove the Assert line in the H811 rom?

If not, refer to post # 947 in the UsU thread.