yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] aka_bigred:
Is regular calling supposed to work in the latest build (2019-06-20) of lineage 16 for VS986 on VZW network? I have mobile data, but no calling. I can browse web, and see the "LTE" icon, but when I try to call out via built-in phone app, it just says "Mobile network not available." after a bit. Seems like it tries to call, shows animated calling icons, etc, just never actually connects.

Just wondering if it's related to the "blobs not being updated" issue for VS986 from a while back, or something else.

I just did a clean flash { formatted System + Cache + Dalvik + data (exept data/SDCard)}. I was on UsU'd on stock 2BA. Before flashing LOS16, I also applied TWRP_2ba_modem.zip

I was just kicking the tires, can revert to my 2BA nandroid backup if calling isn't working yet. Otherwise I can capture a log if helpful too.
[G4 Android Development] beingmishra:
Quick questions here :

1. Did anyone tried this rom on F500?

2. [MENTION=5545101]steadfasterX[/MENTION] can u share the DT u used for f500? ... I'll modify one if needed but if u have then it will be more cool.....
[G4 Android Development] Frazercrib:
H811 clean flash on jun 20 build

When I make phone calls, I can't hear anything from the person I called

I only hear them when I place the call on speaker
[G4 Android Development] steadfasterX:
no. the progress of that particular issue is tracked here: https://github.com/Suicide-Squirrel/issues_oreo/issues/21

reg. 1 no idea but will work ;)

there is no dedicated f500 release so you simply flash the h815 UsU one on your f500 and it will work as it should.

if you like you can fork the h815 UsU DT from here: https://github.com/Suicide-Squirrel/android_device_lge_h815-Usu and replace all findings (except those going to the blobs) with f500 and rename the whole repo to f500 as well.

if you finished let me know and I will fork yours to the suicide org and can do f500 builds in the future, too.

its easy to do the above but I was too lazy yet (and it seems there are just a few - if any - f500 users)

do you talk about BT voice? or the normal handset?

if BT voice wait for the next build (arrives today)

if handset take a log (read the FAQ #1

.-
[G4 Android Development] beingmishra:
Yeah can see that ... only found 1... I will do as soon as I get my hands on my lg g4....
[G4 Android Development] steadfasterX:
Looks like the temperature is going too high. makes sense as the G4 is known to overheat and even more known to the ILAPO. So it would be possible to adjust the thermal engine with the risk of burning the device..

.-
[G4 Android Development] steadfasterX:
New builds are cooking...

In progress (in that order):

H815 UsU

VS986

H812

H810

Done:

H815

H811

Noteworthy Changes:

BT voice fix optimizations by z3DD3r

Keep in mind that even when I have done some tests it might have unknown side effects or behave not in every situation as expected as I cannot test everything ...

so always keep a recent backup of your important data !

BT WBS (wide band speech) is now disabled.

Why? If you have a device which supports WBS the BT voice fix failed. Disabling WBS is a workaround only, ofc but it is not that a big disadvantage so nothing you need to worry about - usually.

When coming from lineage-16.0-20190620 or later a "REGULAR CLEAN FLASH" is

recommended

When coming from

before

lineage-16.0-20190620 or later a "REGULAR CLEAN FLASH" is

REQUIRED

See the FAQ of this thread how to do a "regular clean flash": https://xdaforums.com/g4/development/rom-lineageos-16-0-t3929082/post79502871

If you wanna show your gratitude give those guys at least all your 8 thanks clicks (open the post I linked and click on every post you can find there from those guys):

z3DD3r (does not accept donations):

https://xdaforums.com/google-nexus-5/devs-only/bt-calling-robotic-audio-t3798105/post79747463

Sashko98 (accepts donations as well):

https://xdaforums.com/google-nexus-5/devs-only/bt-calling-robotic-audio-t3798105/post79749418

.-
[G4 Android Development] MrVoidex:
Soo there is no solving for it :/ [MENTION=5545101]steadfasterX[/MENTION] in RR Oreo rom there isn't problem like this. :(
[G4 Android Development] steadfasterX:
Correct that's because you do not have overheating protection within that ROM .

if you like you can change the thermal configuration file and then at your own risk hope that you will not burn your device
[G4 Android Development] MrVoidex:
I found that my cell is coming late so I have to wait for it. If I don't system UI has stopping and I can't do anything. I flashed H815_20p Modem. And Also I figured out that when I use different launcher again system UI locking. But in Magisk There is QuickSwitch Module so I installed it and installed compatible launcher for it. Now everything is fine. Thank you [MENTION=5545101]steadfasterX[/MENTION]
[G4 Android Development] himtan:
I went to lineage 16 from lineage 15.1. Seems very smooth.

I noticed that the maximum call volume is a little lower than lineage 15.1. Can you please increase the maximum possible volume on calls in the upcoming version of lineage 16 ?

Thanks in advance.
[G4 Android Development] Vishnuisgod:
Hello guys,

Ive been struggling with my G4 overheating when using the camera extensively. Im wondering if theres a ROM that doesnt cause as much heat in the cpu/camera area? Ive recorded (with cpuz) temps as high as 90C..... Its melted one of my phones, with unrecoverable data :( . Looking for a cooler running rom if theres such a thing.
[G4 Android Development] ANDROID2468:
No, there are no roms that don't have this issue. Even the stock rom has this issue. You can try underclocking the CPU and/or disabling 2 of the 6 CPU cores, but your phone will still get a little Warm.
[G4 Android Development] Vishnuisgod:
hmmmmm, turning off a few cores.... that sounds promising. Is there a guide for that somewhere?
[G4 Android Development] ANDROID2468:
You can use this guide by steadfasterX here.

I heard People also use kernel adiutor to do it but I haven't gotten it to work.
[G4 Android Development] zeduck:
[MENTION=5545101]steadfasterX[/MENTION] thanks for the build with bluetooth fix!

Since LOS 16 you includes microG and G-droid to your build.

Would it be possible to include signature spoofing as well?

Otherwise, would it be possible to have a pure LOS build, please?

I have quite a difficult setup to maintain as I use signature spoofing to enable GMS services and I use FakeGapps stub.

MicroG embedded is not much simplier in my case.

Thanks again for the huge work you did for our device!
[G4 Android Development] steadfasterX:
I guess you meant F-Droid ;)

If you explain what you mean with signature spoofing .. maybe.
[G4 Android Development] zeduck:
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/
[G4 Android Development] polfrank:
Hey, I think that I have found a small issue with BT.

Let's assume that we are doing a call with the BT headset and afterwards we end it. The dialer app or the data-dialing app (WhatsApp/Viber/etc) remain in the background, as expected.

If we try afterwards to play music with a music app (eg. Spotify), the music cannot be heard. But if you open the recent apps and swipe the dialing app from before to close it,the music continues automatically.

It's like the dialing app is "not giving back the sound" to other apps after the call.

I created a log by doing these steps:

1. Doing a call with Viber.

2. Ending the call.

3. Open Spotify to play music. The time of the song is starting, but cannot hear anything.

4. Open recent apps to close Viber.

5. Music from Spotify continues automatically.

https://paste.omnirom.org/view/2e5cf106

note: the same is happening when I use the default music app instead of Spotify.
[G4 Android Development] steadfasterX:
Thx for your report . Will look into it ..

looks like that is causing the issue:

06-30 21:22:19.338 16424 16469 E bt_btif : register_notification_rsp: Avrcp device is not connected, handle: 0x0
[G4 Android Development] TheCappn:
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.
[G4 Android Development] steadfasterX:
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.

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.

.-
[G4 Android Development] TheCappn:
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!
[G4 Android Development] steadfasterX:
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).
[G4 Android Development] TheCappn:
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. :svetius:
[G4 Android Development] steadfasterX:
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 .. :svetius:
[G4 Android Development] 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 [MENTION=5461026]kessaras[/MENTION] 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..
[G4 Android Development] a tiny ant:
You're amazing [MENTION=5545101]steadfasterX[/MENTION] and of course [MENTION=5461026]kessaras[/MENTION] and [MENTION=8699949]ThePiGuy[/MENTION].
[G4 Android Development] jjcdennis:
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.
[G4 Android Development] 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:
[G4 Android Development] 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..
[G4 Android Development] Termehansen:
Will there be a new build with 4.4 kernel to test?
[G4 Android Development] steadfasterX:
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.
[G4 Android Development] 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.
[G4 Android Development] sbasil:
[MENTION=5545101]steadfasterX[/MENTION]

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.
[G4 Android Development] 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
[G4 Android Development] jotaincubus:
WiFi error

[MENTION=5545101]steadfasterX[/MENTION]

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
[G4 Android Development] TheCappn:
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
[G4 Android Development] busattovini:
Is there a new build coming this month? ?
[G4 Android Development] steadfasterX:
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.

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

.-
[G4 Android Development] jotaincubus:
WiFi Error

Thanks about your reply [MENTION=5545101]steadfasterX[/MENTION], here is the full log and I try to put on WiFi some times... but something is wrong with my smartphone

[MENTION=5545101]steadfasterX[/MENTION] Maybe is not important but my MAC address is 02:00:00:00:00:00 (that's bad)

https://paste.omnirom.org/view/de98725a
[G4 Android Development] sperelli:
seems process didn t succeed for h815
[G4 Android Development] polfrank:
I think that the progress being done here deserves a post on the xda news feed at least. Good job! :)
[G4 Android Development] busattovini:
OMG, I'm so excited! Thank you so, so much aaaaaaa

YOU ARE ****ING BRILLIANT

---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------

Oh, what happened?!

---------- Post added at 11:52 PM ---------- Previous post was at 11:08 PM ----------

I can't wait! ? Now I'm kinda anxious.
[G4 Android Development] ozukoc:
Wow big update! cant wait to flash it =) Now that selinux is enforced, is there a way like this build can be official ? I'm not sure but i kinda remember that this was one of the reasons. Also ı dont know if it goes official something will change for us but just being curious :D Big Thanks !!
[G4 Android Development] grigione:
Hello,I have a LG G4 H815EU and I made an update to Ofiicial Nougat V29a (with locked bootloader) about one year ago.I would wish to move to Android 9 by Lineage OS 16,can you tell me what are steps to get and install it?Thanks
[G4 Android Development] steadfasterX:
actually that IS VERY important ;)

Pls wait for and flash the newest pie upgrade currently building. It has this (WiFI and BT MAC issues) addressed..

I created a new FAQ for that: https://xdaforums.com/showpost.php?p=79502871&postcount=2 --> FAQ #3 ;)

just a jenkins build error. I wrote that this might happen as I changed so much under the hood.. Fixed anyways and H815 is up already, H811 soon as well and the rest follows as described.

.-
[G4 Android Development] calavera2k:
I love you! Last LOS version was installed directly.
[G4 Android Development] steadfasterX:
Note:

Unfortunately I found a little bug already while the build progress is still running. It has been fixed but only for those not build yet.

If you have one of the the following devices and you want to use google play (there is F-Droid pre-installed btw ;) )

then you should read and follow: the gapps issue* workaround

H815

H811

H815 UsU

All others will have the fix included already.

Sorry for the inconvenience

.-
[G4 Android Development] sbasil:
Great work again. :) However, I installed the newest version, but can't get Wifi to work. It connects but doesn't work (IMEI and IMEI SV are both unknown). Older version works just fine. Anyone else facing the same problem with H815?
[G4 Android Development] steadfasterX:
regular clean flash done as described in the FAQ?

MAC address shown?

provide a logcat as described in the FAQ

.-
[G4 Android Development] sbasil:
regular clean flash done as described in the FAQ? - Yes

MAC address shown? - Yes

provide a logcat as described in the FAQ - Ok. Will do that when I can (asap).

I attached a couple of screenshots of the "IMEI situation."
[G4 Android Development] steadfasterX:
regarding WiFi:

do u had tried setting selinux to permissive?

and try that as well: settings -> system -> advanced -> reset options -> reset WiFi, mobile & bluetooth (will delete all those settings obviously!)

after that do a reboot and connect again.

regarding Imei:

what happens when you type "*#06#" in the dialer app? does it show your imei? do you have cell service/call etc working?

.-
[G4 Android Development] busattovini:
It seems like Google Play is still working for me. No bugs. I flashed the ROM, and it's perfect. You're such a genius. <3
[G4 Android Development] busattovini:
BTW, why don't you like Magisk? Do you think it's bad for LineageOS?
[G4 Android Development] jjcdennis:
Hate to ask, but for a flash from steadfasterX's 15.1 unofficial lineage to this 16.0 image is a full clean flash required, as per the installation instructions on page 1?
[G4 Android Development] himtan:
yes !
[G4 Android Development] steadfasterX:
Never said that I do not like it ;) Its a great piece of software and besides that it is Open Source which SuperSu never was.

I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.

Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..

.-
[G4 Android Development] busattovini:
Oh, I got it. Thank you! Please, would you tell me how to install the LOS root-addon?!
[G4 Android Development] jjcdennis:
TWRP. Link is in page 1 instructions.
[G4 Android Development] busattovini:
I appreciate it. Thanks! ??
[G4 Android Development] jjcdennis:
I don't understand the installation instructions from page 1. I have flashed the baseband package, way back when I installed 15.1 after flashing uSu - H812_20z_modem.zip.

This step is for UsU'd devices only:

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

If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.

If you have no backup:

- TWRP flashable MM modems (N will not work)

Does this mean that the baseband is flashed with this ROM?

I have TWRP backups, but don't know how to clean flash the modem partition in a twrp backup.

Would appreciate some help here. I'm confused with the instructions.
[G4 Android Development] sbasil:
This one did it for me. Internet is working again. Billion thanks! :)

"*#06#" displayed the IMEI code as it was probably supposed to do?

edit: one question: how to I make it permanent? after booting the phone, I had to do setenforce permissive all over again.

edit: logcat file attached (don't know if I got it right, cause I've never used it before)