[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

[steadfasterX]

It's a requirement to MicroG GSM Core.
That is the collection of stubs to replace Google Services, as you probably already know.

Here are some pointers:

* https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing

* https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/195284/

ok I had reviewed this and come to the conclusion that this will not match my security feeling. It opens a door I would have better closed so no, sorry but I won't add that.

I'd also like a us991 version of the ROM, myself. I'm not asking you to make a special one. But if I flash a h811 as my gpt compatibility said. Will I lose my cell service?

And, if so, would flashing the modem.bin file work to fix it, like it did when I UsU'd in the first place?
If not, could you put me on the right path to 'porting' for us cellular cell service to work? I've built roms myself in the past, but they were already for my device. So I don't have any experience with carrier specific issues.

Sent from my LGUS991 using Tapatalk

Read the OP for UsU , topic "Making the baseband flashing obsolete" where the last sentence is for your situation.
You can also wait a bit as I am currently re-structuring all device trees for all models and will add all known g4 models there as well. I may not build for US991 but it will be super easy doing so if needed.


.-

 

[TheCappn]

Read the OP for UsU , topic "Making the baseband flashing obsolete" where the last sentence is for your situation.
You can also wait a bit as I am currently re-structuring all device trees for all models and will add all known g4 models there as well. I may not build for US991 but it will be super easy doing so if needed.


.-

Thanks for the reply! I take it to mean that I can't simply flash the h811 version of this rom and then follow it up with my own modem file from the SALT backup, as I have yet to find a us991 specific ROM, or kernel. And I'm sure that's because there was no way to unlock until your work was done.
I was eager to give it a try, but I can only find kdz files for the stock rom, and it's not safe to use them after UsU, right? So if this rom didn't work, I wouldn't be able to go back to stock.

If that's the case though, why put us991 in the title of the post if it doesn't work for the device? Just curious if I'm missing something, and I'd love to get an update for the device since the carrier has abandoned it...

Thank you for all your work unlocking the g4!

 

[steadfasterX]

Thanks for the reply! I take it to mean that I can't simply flash the h811 version of this rom and then follow it up with my own modem file from the SALT backup, as I have yet to find a us991 specific ROM, or kernel. And I'm sure that's because there was no way to unlock until your work was done.
I was eager to give it a try, but I can only find kdz files for the stock rom, and it's not safe to use them after UsU, right? So if this rom didn't work, I wouldn't be able to go back to stock.

If that's the case though, why put us991 in the title of the post if it doesn't work for the device? Just curious if I'm missing something, and I'd love to get an update for the device since the carrier has abandoned it...

Thank you for all your work unlocking the g4!

ok just once. just for you.. and just because you have luck (as everything is written, clearly, imho):

1. you CAN flash this ROM on US991, even on a LS991 or F500 or others. For none of them a special UsU version of this ROM exists but the UsU thread clearly describe this way. Even the assert line removal which needs to be done first
2. I linked you to the UsU thread to a specific topic and even to a specific sentence there: "When the ROM is neither fully UsU compatible nor there is no kernel with UsU patches you can or better must flash the baseband package." . So breaking it down: there is no UsU specific version for your model which is the first part of that sentence ("When the ROM is neither fully UsU compatible nor there is no kernel with UsU patches ...."). That means this is for your situation. The next is the solution for your situation: "....you can or better must flash the baseband package." . So flash the ROM version which is compatible with your GPT (see SALT FAQ) and flash the baseband package as stated. That's it.
3. You think about KDZ flashing after UsU'ing? OK there is absolutely NO doubt left when you read the UsU OP. But here again: in the UsU OP find the topic "LIMITATIONS / KNOWN ISSUES". Read 1), 2) and 8) there. Really no doubt left. THREE times.. I thought it would be enough.. and consider reading the whole UsU FAQ ..
4. going back to your current state? ok there is TWRP. Do a backup before flashing this ROM and read the UsU FAQ #17 what to backup. Restore if you wanna go back..
5. you can even go to another stock version of your model by simply flashing the boot and system partitions (extracted by SALT).

 

[TheCappn]

ok just once. just for you.. and just because you have luck (as everything is written, clearly, imho):

you CAN flash this ROM on US991, even on a LS991 or F500 or others. For none of them a special UsU version of this ROM exists but the UsU thread clearly describe this way. Even the assert line removal which needs to be done first
I linked you to the UsU thread to a specific topic and even to a specific sentence there: "When the ROM is neither fully UsU compatible nor there is no kernel with UsU patches you can or better must flash the baseband package." . So breaking it down: there is no UsU specific version for your model which is the first part of that sentence ("When the ROM is neither fully UsU compatible nor there is no kernel with UsU patches ...."). That means this is for your situation. The next is the solution for your situation: "....you can or better must flash the baseband package." . So flash the ROM version which is compatible with your GPT (see SALT FAQ) and flash the baseband package as stated. That's it.
You think about KDZ flashing after UsU'ing? OK there is absolutely NO doubt left when you read the UsU OP. But here again: in the UsU OP find the topic "LIMITATIONS / KNOWN ISSUES". Read 1), 2) and 8) there. Really no doubt left. THREE times.. I thought it would be enough.. and consider reading the whole UsU FAQ ..
going back to your current state? ok there is TWRP. Do a backup before flashing this ROM and read the UsU FAQ #17 what to backup. Restore if you wanna go back..
you can even go to another stock version of your model by simply flashing the boot and system partitions (extracted by SALT).

I actually understood all of the post, and read the UsU post several times before I unlocked the phone. The baseband package for the us991 made my cell service stop working. That's why I asked the question.

Since your reply to this is, "Read the post, that says you need to flash something that breaks your cell signal" I suppose I can just skip this all together.

Thanks for telling me about which backups to flash, that was the reason I asked about it. I know I can't flash kdz. And I never said I was going to. I simply needed to know how to get back to stock in case this didn't work.

Thanks anyway, for the work you did. And for referring me to a post that doesn't address the problem I have.

 

[steadfasterX]

The baseband package for the us991 made my cell service stop working. That's why I asked the question.

Aha I must have over seen that you mentioned this ?!
When that happens it is important to know your ARB version and which region code (uck,ucl,..). A logcat started before booting would be good as well.

Since your reply to this is, "Read the post, that says you need to flash something that breaks your cell signal" I suppose I can just skip this all together.

when I say you need to flash that then I'm not kidding. You can't skip that. The reason why your signal breaks here is due to an issue with not compatible baseband files for your bootloader stack . So we just need to know the above and then I can provide another baseband package for you.

Thanks anyway, [....] for referring me to a post that doesn't address the problem I have.

Wow just wow ..


Sent from my OnePlus 6T using XDA Labs

 

[steadfasterX]

We made a LOT of progress in the last days regarding performance so stay tuned.

Keep in mind that we still on opengl graphic rendering here as I preferred a stable ROM instead of having a bit faster UI but graphic bugs like when using skiagl. The bugs in skiagl are much decreased while not completely gone and @kessaras and I trying to fix the rest. He found the bug in the code which might be responsible for that so a fix is possible . Regardless of the full fix I will switch to skiagl in the next build as the glitches are really very rare now.

Other then that I'm changing a lot behind the scenes like restructuring the device trees and unifying all models, enforcing coming soon, a lot of bugs from the issues page are fixed, ril fixed,... I hope to do more this weekend like fixing TWRP decrypt on pie etc as well..




Sent from my OnePlus 6T using XDA Labs

 

[a tiny ant]

You're amazing @steadfasterX and of course @kessaras and @ThePiGuy.

 

[jjcdennis]

You're amazing @steadfasterX and of course @kessaras and @ThePiGuy.

Amazing and awesome support from these great developers. Really looking forward to the next update so that I can get 16.0 onto my ancient G4.

 

[Ximo F. Verde]

really appreciate all your work, couldn't really imagine how the UI performance could be any better, so happy days indeed :laugh:

 

[Ximo F. Verde]

btw, others might have different results, but in my case magisk seems to be working flawlessly. Have been using Adiutor for a couple of mild tweeks & Fluid NG for my gesture needs. Might have to root again after the update, but i really dont mind. The fact that the 4 year old G4 runs the way it does right now is pretty remarkable on its own..

 

[Termehansen]

Will there be a new build with 4.4 kernel to test?

Sent from my LG-H815 using Tapatalk

 

[steadfasterX]

Will there be a new build with 4.4 kernel to test?

There is no 4.4 kernel coming for our device. Kessaras had added and will add fixes and features from the 4.4 to our kernel though and those are all coming in the next build as well ofc.


Sent from my OnePlus 6T using XDA Labs

 

[calavera2k]

Good morning, I am a user from Germany. I just wanted to thank you at this point for the great work. My LG G4 works better than ever. I can not wait for the next release. You are great. Thank you very much.

 

[sbasil]

@steadfasterX

Had you pulled this off last year, no sane G4 user would have bought G6 (well, at least I wouldn't have). Awesome job, both L15 and L16 work great now! Time for me to retire the (un-)official Nougat beta.

 

[bazaleem818]

hello sfx i install rr 6.2.1 and there are too many customization but no update like your rom so
is there many cutomization in lineage 16 pie like in rr
for example i can edit the navegation bar so when i long press a button get actions and so on
or can you add those features
https://drive.google.com/open?id=17xqr3zDQ-RD3u-k_BfKQ-oGQMoDlJU3-
https://drive.google.com/open?id=1mujSTawghxY7NWXdfswmov5l7Vb1C2dB
thank you

 

[jotaincubus]

WiFi error

@steadfasterX

Someone else got WiFi problem? I try to put on WiFi but can't start and the switch it turn off automatically without show me WiFi connections

LG G4 H815p

07-08 19:37:48.315 495 495 E WifiHAL : Timed out waiting on Driver ready ...
07-08 19:37:48.315 495 495 E [email protected]: Timed out awaiting driver ready
07-08 19:37:48.315 495 495 E [email protected]: Failed to start legacy HAL: TIMED_OUT
07-08 19:37:48.316 1037 4128 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
07-08 19:37:48.317 1037 4128 E WifiVendorHal: Failed to create STA iface
07-08 19:37:48.317 1037 4128 E WifiNative: Failed to create STA iface in vendor HAL
07-08 19:37:48.317 1037 4128 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
07-08 19:37:48.317 1037 4128 D WifiStateMachinePrime: State changed from client mode. state = 4
07-08 19:37:48.317 1037 4128 D WifiClientModeManager: expected stop, not triggering callbacks: newState = 1
07-08 19:37:48.322 1037 1121 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.net.wifi.WIFI_STATE_CHANGED flg=0x4000010 (has extras) } to tv.peel.remote/com.peel.receiver.ConnectivityActionReceiver
07-08 19:37:48.324 1037 1037 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true
07-08 19:37:38.246 397 397 I snet_event_log: [121035042,-1,]
07-08 19:37:48.329 16562 16562 I sysui_count: [wifi.WifiSettings/switch_bar|false,1]
07-08 19:37:48.329 16562 16562 I sysui_multi_action: [757,803,799,wifi.WifiSettings/switch_bar|false,802,1]
07-08 19:37:48.336 1037 4128 D WifiStateMachinePrime: ClientMode failed, return to WifiDisabledState.
07-08 19:37:48.336 1037 4128 D WifiController: ClientMode unexpected failure: state unknown
07-08 19:37:48.336 1037 1127 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
07-08 19:37:48.337 1037 4128 D WifiClientModeManager: currentstate: IdleState
07-08 19:37:48.346 4791 6429 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
07-08 19:37:48.359 1037 4128 D WifiStateMachinePrime: Entering WifiDisabledState
07-08 19:37:48.360 1037 4128 D ActiveModeManager: sending scan available broadcast: false
07-08 19:37:48.361 1037 4128 D WifiStateMachinePrime: received a message in WifiDisabledState: { when=-24ms what=3 target=com.android.internal.util.StateMachine$SmHandler }
07-08 19:37:48.361 1037 4128 D WifiStateMachinePrime: Switching from WifiDisabledState to WifiDisabled
07-08 19:37:48.361 1037 4128 D WifiStateMachinePrime: Entering WifiDisabledState
07-08 19:37:48.361 1037 4128 D ActiveModeManager: sending scan available broadcast: false
07-08 19:37:48.363 1037 4131 I WifiScanningService: wifi driver unloaded
07-08 19:37:48.363 1037 4131 I WifiScanningService: wifi driver unloaded
07-08 19:37:49.033 523 627 E ThermalEngine: ==== Enter sched_bmhb_cs_gov -> vs_temp = 420 ===

 

[TheCappn]

Aha I must have over seen that you mentioned this ?!
When that happens it is important to know your ARB version and which region code (uck,ucl,..). A logcat started before booting would be good as well.

when I say you need to flash that then I'm not kidding. You can't skip that. The reason why your signal breaks here is due to an issue with not compatible baseband files for your bootloader stack . So we just need to know the above and then I can provide another baseband package for you.


Wow just wow ..

I'll get a logcat for you likely tomorrow.

My arb is 2.

How can I find the region code? I'm in north America, but I assume that doesn't mean much.

But I really do appreciate the work you've done for this project.

Edit: I don't see those codes in the device menu, so just let me know how and I'll get back to you with the info

 

[busattovini]

Is there a new build coming this month? ?

Sent from my LG-H815 using XDA Labs

 

[steadfasterX]

@steadfasterX

Someone else got WiFi problem? I try to put on WiFi but can't start and the switch it turn off automatically without show me WiFi connections

LG G4 H815p

No it works perfectly here. read the FAQ in how to do a proper logcat (turn off wifi and follow the steps) and how to share it properly.

How can I find the region code? I'm in north America, but I assume that doesn't mean much.

But I really do appreciate the work you've done for this project.

Edit: I don't see those codes in the device menu, so just let me know how and I'll get back to you with the info

well maybe on your sticker (behind the battery), very likely on the original packaging..
sometimes it is named "Buyer code". In your particular case it would be one of UCL or UCK: https://lg-firmwares.com/lg-phone-firmwares-region-description/

you can also check one of those free imei check websites ( I do not trust any of them though ) or ask your local dealer if he can check for you.
You can also send a request to LG or your provider and based on the imei they all can provide you that information.
There is also a llittle chance that it is printed on the mainboard but I guess the chance is 20% only..

nevertheless the logcat from boot is required as well

.-

 

[jotaincubus]

WiFi Error

No it works perfectly here. read the FAQ in how to do a proper logcat (turn off wifi and follow the steps) and how to share it properly.

Thanks about your reply @steadfasterX, here is the full log and I try to put on WiFi some times... but something is wrong with my smartphone
@steadfasterX Maybe is not important but my MAC address is 02:00:00:00:00:00 (that's bad)

https://paste.omnirom.org/view/de98725a