yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] llarr:
Hmmm, yes I did a full clean flash. I also flashed h815_20p_bootloader_20p_modem_TWRP-flashable.zip from your leech server using twrp 3.5.2_9_prev275 for both, with reboot to twrp between. I thought that I was already on that bootloader but I figured it couldn't hurt to make sure.

It seems I can get bars/connection data if I change mobile network > preferred network type > from 4G (recommended) to 3G but it doesn't stick when reverting back.
[G4 Android Development] steadfasterX:
Yea that's exactly the same behavior then from before the fix. Will look into that again but might be hard as i cannot reproduce that here anymore.
[G4 Android Development] ismystore:
I hope this will e fixed soon
[G4 Android Development] steadfasterX:
latest build has auto rotate and 4G signal icon fixed. it seems it was a h815 (official unlocked) issue only so there is no other release then for that one
[G4 Android Development] llarr:
I didn't have an issue with rotate before, still works.

The 4g signal doesn't seem quite right. First part is irrelevant, but using Better Battery Stats I can see that the phone doesn't believe it has any signal while in deep sleep. Obviously that isn't really important because you can't look at the signal bars when the phone is 'off'.

But when display is turned on/awake, it's still a mixture of no/unknown signal and only poor signal. Perhaps 2/3rd unknown signal.

Thanks for all the efforts on this and the roms in general.
[G4 Android Development] theartanis:
nice rom for my h815_usu but your roms have a bit laggy ui. i think my g4 cpu have problem. reducing screen resolution helps a lot for smooth
[G4 Android Development] Emo19:
I have a H815TR unlocked. I didn't get what should i do before flashing the rom. Can someone tell me?
[G4 Android Development] theartanis:
sorry
[G4 Android Development] Emo19:
I flashed the baseband before it.
[G4 Android Development] Emo19:
@theartanis
[G4 Android Development] steadfasterX:
This forum is english only !

This forum is english only !
[G4 Android Development] thedery01:
you are amazing bro thank you, for you hard work
[G4 Android Development] berkantkz:
flash twrp and the rom accordingly usu and then you must good to go.

twrp yükleyin, sonrasındaysa usu'ya göre olan romu kurun, çalışmalı
[G4 Android Development] Emo19:
Sorry for the mess. Thanks for the great job for G4 community.
[G4 Android Development] 1captainjacknotsparrow1:
Hi @steadfasterX,

first of all thanks for keeping our old g4's up to date. There are many silent users among us who are just too lazy to register here and write you a thanks.

But now to my questions:

1) How do I find out, which bootloader version I have on my H815?

2) Does a newer bootloader version have any benefits except not bricking my phone when installing LineageOS? Btw I have LineageOS 16 installed on my H815 right now.

3) Do I need to use your "latest TWRP - PREVIEW build: click" or can I just use the TWRP Version from the official website, which is at the moment "twrp-3.6.2_9-0-g4.img" from "2022-06-01", because your version seems to be older.

4) And what do I need to download at your download server, if I want to upgrade my bootloader for H815 because there is "20p", "29a" and "mixed".....I'm confused on the whole bootloader topic...

5) Since I have LineageOS 16 and TWRP installed, I guess my phone is unlocked? Lol because I don't even remember if I unlocked it, but when my phone boots there is a "bootloader unlocked" on the screen, so I guess I unlocked it some time ago? It is my phone, I just really forgot about it, if I ever unlocked it.

thanks in advance
[G4 Android Development] steadfasterX:
Re 1) There's no easy way to find out your bootloader stack. Simplest thing is flashing the recommended bootloader stack by yhe provided TWRP packages.

Re 2) the 2 major benefits are supporting newer kernel builds and fixing issues in how the hardware is addressed.

Re 3) always use yhe latest PREVIEW build of TWRP or SHRP. The official TWRP is ideal for oreo ROMs only. That's bc all newer ROMs can't be decrypted in TWRP/SHRP.

Re 4) if you have an officially unlocked h815 (i.e you have no idea what UsU is ;) ) then simply flash pure 20p . Ppl usually think latest is best but 20p is the latest stable and works well while 29a is an unofficial and never released beta.

Re 5) yes if you've TWRP and LOS installed your phone is unlocked ;) otherwise this wouldn't be possible at all. I assume officially unlocked as you (usually) would remember about UsU and if you've just 1 line "bootloader unlocked" that means officially too. If you want to be 100% sure before flashing the bootloader stack (for this its crucial important) you can start mAid and use SALT to determine the unlock method used.
[G4 Android Development] 1captainjacknotsparrow1:
Especially the SELinux point is important to me.

Or more precisely: My understanding is that SELinux plays a big role in the security of my phone and without it it's basically junk if considered for use with private information on it.

So a more detailed answer regarding the SELinux point would be appreciated. Why is it deactivated if it is important for the security of the phone?

thanks in advance
[G4 Android Development] w.m.:
MAC-Randomization

First, I am glad that you still continue to support the LG-G4. I love that phone.

The new lineage-18.1-20220523-UNOFFICIAL-h815 installed rather smooth and most things I tried so far work as expected. Thank you very much.

But the newly introduced MAC randomization, which I couldn't find a way to switch it off, makes trouble to connect to my WLAN.

After any short interruption of the connection, the phone tries to reconnect with a different MAC-address which is treated on the router as a new device and the router refuses to continue the previously established connection.

After a short while when the router has finished setting up a new device with a new ip-address it re-connects again.

But for this to work, it demands for opening security precautions in the router.

To connect to a WLAN by a FRITZ!Box router with all security features active, you must not have MAC-Randomization on. The router identifies a device by its MAC-address and this behavior cannot be changed (and will not in future, answer from the FRITZ-hotline).

Unfortunately your ROM has (or I found) no option to disable MAC-Randomization as other LineageOS ROMs have (e.g. OnePlus 7 Pro lineage-18.1-20220602-microG-guacamole).

So my questions are:

Is it possible for you to add a network settings option to switch off MAC-randomization and use the hardware MAC-address?

Or is there a way to switch off permanently MAC-randomization by an ADB command? (Tried to find an answer, but couldn't get a working one.)

Thanks a lot in advance for considering that.

Best regards

w.m.
[G4 Android Development] steadfasterX:
Re2: i assume you speak about RAM not storage ? If so you've yo know that free RAM is useless. That's why Linux (and so android) is caching as much as possible in RAM for speeding up things.

Re3: you can't toggle selinux on / off there. Selinux is very deep inside the system and is nothing which goes easy when porting a ROM. That's why you usually get a new ROM port without selinux first until all is working.

Re 7+8: sounds like your battery might be older then 2 years and might need s replacement.

Not sure if that fixes all of your issues but would be a first try.

Re 9: well you've the choice: no mobile service or accept the delay on reboot. We tried everything in pie and also here and found no real fix for cell service which does bot come up. The workaround is that i wrote a watchdog which monitors the ril process and fixes it when needed. That's a delay you see and can't be avoided if you want cell service.

Re all the rest well no idea all of these need log log log log (see FAQ) and time investigating these.

I would never use a phone without fully working selinux but this takes a lot of time implementing it (correctly). Selinux is one barrier in the chain of protecting your phone. It can prevent access on a deeper level then file or app permissions can do and so can prevent zero day attacks and exploits.

The q is how high is the risk? That depends on your personal behavior. Do you install any app you find? Do you open any link or attachment of your mails? If you think before acting then a disabled selinux is .. not ideal but one can live with it. Not me but im paranoid and live for security but for others that might be different.

As mentioned above I provide builds without selinux first anyways until all known issues are fixed. Then selinux policies needs to be written , tested and implemented. If I'll find the time soon is very unlikely. If you want having it use an older LOS version like 16 which fully supports it.
[G4 Android Development] steadfasterX:
MAC randomization is default enabled in a10 and later and usually you should have a "privacy" option when you click on saved networks and open your wifi network. If that's missing pls check developer options if there's a toggle for wifi mac randomization.

Let me know if one of these work as i can't check it atm on my own.

The inplementation can be disabled completely

Implement MAC randomization | Android Open Source Project

source.android.com

when building the ROM which i would use a last resort only. So best is we get the privacy option to show up if its missing.

Here these 2 options i refer to:

https://xdaforums.com/t/solved-mac-addres-privacy-settings-in-lineage-18-1.4347891/
[G4 Android Development] w.m.:
MAC randomization

thanks for you answer.

I previously had already checked all items you mentioned without success.

I have attached some screenshots from my G4 and my OP7Pro to show the difference in the settings options (relevant items marked yellow).

So, if it is possible, it would be nice to get the missing Privacy option in Network Settings.

Thanks in advance and

best regards

w.m.
[G4 Android Development] 1captainjacknotsparrow1:
Thanks for you answer, you're an angel :)

So:

- Point 2: No I was not talking about ram storage. It was normal storage. 8,7Gb of 32 Gb.

- SELinux point: "I would never use a phone without fully working selinux but this takes a lot of time implementing it (correctly)." - So why are you then not writing a note in the start post of the thread about the SELinux problem? People should know that this rom is not very secure, but only okay-ish regarding the security point and only okay-ish if you are always very aware about what you doing on your phone, which not many are all the time.

And also: Do you think you can get SELinux working this year or you don't have enough time for that?

But still big thanks for all the effort so far.
[G4 Android Development] steadfasterX:
99% of ppl don't care about their privacy (i know what I'm talking about). 90% don't even read about this and the impacts.

It would not make any diff to write about such things here. I do that for years and still nobody cares.

And again selinux is just one barrier in fighting against the bad. Encryption, locking the bootloader, and think before act are other barriers and all of them are important but ppl installing custom ROMs care more about features then about things like security or privacy.

Custom ROMs had selinux on permissive over years and nobody cared. Even worse there were twrp zips which disables encryption and selinux which were the first thing ppl did when google started to enforce selinux. ROM devs recommended (not me) doing that over years. Should tell you everything.

Just to be clear the OP has a clear hint about the known issues - ofc including selinux = permissive!

Other then that LOS is not that privacy friendly. That's why I build eOS as LOS contains still a lot of google spyware and the reason why i would never install gapps or even LOS on my personal phone. I build eOS for my DD (oneplus 7tpro) as I am paranoid, ofc selinux enabled and even bootloader LOCKED - which is as important as selinux btw. (Only a few devices allow locking the bootloader and one of the reasons why i had bought onrplus).

The plan is doing eOS next , then encryption, then selinux. I have no idea about when. Maybe in the next months maybe not. That depends a lot of my RL which consumes a lot of time atm (since several months though).
[G4 Android Development] k24a1:
vs986 running the latest ROM (20220524) with pico gapps (if that helps)... runs pretty slowly under load and heats up quickly. a lot of lag going on which i don't see on other devices that I put custom ROMs on too, unfortunately. hopefully this helps, followed the steps you wrote to report lag/overheating.

cheers,

katheryn
[G4 Android Development] steadfasterX:
The main prob here is your device gets (too) hot. This activates the thermal engine throttling to cool down the cpu and that means lagging.

There are high chances you have a device affected by the ilapo. Check the first 3 digits of your serial (usually on a sticker behind the battery) if it's lower then 603 you might need to find a new phone soon.
[G4 Android Development] theartanis:
dear @steadfasterX can you do 4 cores boot img for this rom? thanks in advance
[G4 Android Development] steadfasterX:
the reason why https://xdaforums.com/t/guide-any-u...tom-x-cores-boot-image-ilapo-tempfix.3718389/ exists is that I do not have time for things like that ;)
[G4 Android Development] steadfasterX:
ok finally had the time looking into this.

1. our wifi driver does not support the "new" mac randomization method by Android - that's why you do not see the Privacy menu in the WiFi setting (we cannot do anything about that)

2. yes the wifi mac (and likely bluetooth mac) changes on every boot nevertheless

background:

we had issues in the past where the mac cant be read from the MISC partition and so we added a service to fix that - if that' happens.

when it could be read from the MISC partition it was simply written as it is to a file in /data.

when MISC is corrupt a new one was generated and written to that file in /data.

the problem:

the service which is responsible to write to /data was started too early and so was never able to write the MAC into /data (as that was simply not accessible at service starting time).

Android itself had implemented some time back a function to handle corrupt/empty MAC addresses - it seems. thats why you always see a new random MAC on every boot.

the solution:

will come in the next build(s) for 16.0, 17.1., 18.1 and eOS pie (R will include that fix already)
[G4 Android Development] w.m.:
Good news, thank you very much.
[G4 Android Development] theartanis:
latest updates overheat
[G4 Android Development] steadfasterX:
Anyone still havin issues with auto rotation on my latest build? If so pls report back your device model and if you have a h815: UsU'd or not.
[G4 Android Development] aoleary:
Hi guys,

I have been investigating the auto-rotation bug and I think I may have found the root cause.

I have uploaded two builds here (h815 and h815_usu). One user has reported that auto-rotation works now for him, without issues.

These are test builds, based on initial release device and kernel trees, so some things added later in the lifecycle might not be there yet. The goal is to go through a number of test builds together to be sure that I have once and for all and finally fixed this annoying bug..

PM me if you can help with testing. I cant do this without you guys, as I dont have any auto-rotation issues on my device. It just affects certain devices..

Here is the link where the LOS18 test builds are located: https://mega.nz/folder/RQckCZjK#6x7bYWPULaECOeXXoc4Yvg
[G4 Android Development] leslietsuk:
Hi all,

I was wondering if anyone had a copy of the UsU modem for the H815 / H81x that works in the UK?

The rom itself works fantastic, but no matter what sim card I use it either says, sim not connected t or emergency calls only.

Many thanks in advance for any help given

ls
[G4 Android Development] berkantkz:
did you flash arbv0> modem partition on your device?
[G4 Android Development] leslietsuk:
I've got it to recognise the sim card and no longer show emergency calls, but can't get it to access data/voice/sms.

But I'll work on it :)
[G4 Android Development] Zandreas:
I do. H815 UsU'd.

Although I took the one from the h815 folder, as opposed to the h815_usu folder. Would that be a factor?
[G4 Android Development] steadfasterX:
You have to use the UsU one. That's mandatory!

If you still having issues try the build by @aoleary : https://xdaforums.com/t/rom-unoffic...91-vs986-lineageos-18-1.4444261/post-87587731
[G4 Android Development] Zandreas:
Unfortunately the test builds still have auto rotation problems for me :(

@steadfasterX I also commented in your /e/OS Android 11 build of auto rotation problems there too.​
[G4 Android Development] steadfasterX:
@aoleary ^^
[G4 Android Development] aoleary:
For UsU devices, or at least the h815, the auto-rotation issue can be quite sporadic. A guy testing for me said that on clean flashing the same build, sometimes it worked, and sometimes not..

PM me if you are interested in helping to test, as the other tester went back to stock, so now I have no one to test..
[G4 Android Development] aoleary:
So @steadfasterX, it seems that the auto-rotation issues started in A10.

So I'm going to have to strip back the A10 kernel branch to find just the commits required to boot A10..

That was kessaras's work, and entails going through 250 commits or so to find the commits necessary to boot A10.

Gonna be a lot of fun, but it could be good for the Unified kernel as we will start from a fresh base of Pie plus only the commits required to boot each version and rebuild the kernel from there..

The only wrinkle will be finding testers for each android version, as all 4 versions will need to be tested at the same time..
[G4 Android Development] mvn77:
Tell me please, I have H810 and H986, both after the firmware, all sensors, NFC, proximity, compass, pressure and others do not work. WI-FI bluetooth and cellular network work. I flash 16 everything works. Maybe I missed something?
[G4 Android Development] aoleary:
It seems the sensors issue started with A10, so I am going back over the last 2 years in the kernel with testers to find out where the problem originated..
[G4 Android Development] mvn77:
Thank you! I thought my poor knowledge interfered with my work. In general, the firmware is excellent, fast operation, low heating, advanced call blocking function! Thank you for your hard work. If necessary, there are 986 for tests.
[G4 Android Development] aoleary:
Send me a PM please. As the more testers the better. Are you on Telegram, cos if so, you can contact me at : @aoleary

I'm also on Discord too.

It would be much easier to coordinate via Telegram/Discord than via XDA..
[G4 Android Development] aoleary:
I've also done a lot of optimisation on A12 to get it running as smoothly as possible on the G4, much of which can be backported to A10/A11, so once I finish the kernel testing, I will do the backporting..
[G4 Android Development] steadfasterX:
H986 is not a supported LG device
[G4 Android Development] aoleary:
Oops. Thought it was a VS986. Unfortunately we don't support the H986. Is that a G4?
[G4 Android Development] mvn77:
Yes VS986! ))))
[G4 Android Development] aoleary:
OK. PM me. I have a VS986 build of LOS17 from today for you to test, if you are willing 🙂
[G4 Android Development] mvn77:
Yes with pleasure! Tell me how to contact you via telegram?
[G4 Android Development] steadfasterX:
see the OP -> Support
[G4 Android Development] aoleary:
If you have telegram, you can add me : @aoleary
[G4 Android Development] pizza_alarm:
I have also the auto rotate problem on my H815 USU with e-OS A11 USU installed. However, on my 2nd non-USU official unlock H815 with e-OS A9 auto rotate works fine.
[G4 Android Development] aoleary:
It's a really, really weird bug. With the kind help from some willing testers, I have been able to remove the worst of it. I'll be uploading the kernel for SFX in a weeks time, maybe, and then it's up to his workload when he can release new builds with the updated kernel..
[G4 Android Development] pizza_alarm:
Would it make sense to test Corvus 4.1 usu, crDroid 12.1 usu and Havoc OS 4.19 usu or is it certain that auto rotate will not work on those OSs either?
[G4 Android Development] aoleary:
Well, the kernel that now works for A10 is mostly the same in A12.

It seems to be a bit more pronounced in A12..

I'll have to build those roms again with the updated kernel
[G4 Android Development] pizza_alarm:
I tested all before mentioned ROMs on my G4 H815 EU, but all ROMs with Android version > 9 were buggy.
[G4 Android Development] aoleary:
In what way?
[G4 Android Development] pizza_alarm:
Auto-rotate didn't work on all mentioned ROMs.
[G4 Android Development] aoleary:
Your device is UsU or not?
[G4 Android Development] pizza_alarm:
It is an USU device.
[G4 Android Development] aoleary:
Do you mind joining this telegram group?

https://t.me/+ZM_ZwrUTA1JjZmFk

It is for testing the kernel related to auto brightness and rotation.

I have builds there that are working for other UsU devices. Would be cool if you could test some of the builds also..

The link to download the test builds are in the pinned post in the group
[G4 Android Development] pizza_alarm:
Yes, I can do that. Another problem is that Whatsapp backup via Google Drive doesn't work flawlessly due to MicroG. I don't use Whatsapp, but for Whatsapp users I recommend Pixel Experience.
[G4 Android Development] mcgoxel:
hi thank you for your efforts.
[G4 Android Development] hyogga:
Hi. I see there is an update via Lineage updater, the first one since August. Is it safe to install it? I wouldn't like to reflash manually. (LG-H815 with UsU)
[G4 Android Development] hteles:
Hi.

Go ahead. No problems whatsoever.
[G4 Android Development] hyogga:
I confirm that I've tried and it has worked! Thanks!
[G4 Android Development] cris3:
hello, and for a while that I do not use Android 11 on L H815 official slocco, or tried to install the ROM of March, but at first it seems to go, then after the first restart of the device, disappears the mogile network, you can not even change anything of the mobile network, remains unclickable option, I reinstalled 2 times, but same problem, The August version instead works, any ideas? I don't know if doing as an update maybe can fix it. Thank you
[G4 Android Development] lightdown:
Hi,

I have been testing this great rom in my H810. Is smooth, fast and all seems to be OK, but the only problem that I have is when I try to secure my lock screen. When I choose PIN or password or pattern the app fails and restart and let me choose again the secure method.

I have the same results in all Lineage from 14 to 18.

Any solution?

Thanks
[G4 Android Development] steadfasterX:
FAQ 1