yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] tullyp:
Will work on some Verizon phones, but recent problem with Caller ID

Hi All, Just wanted to encourage anyone with a Verizon VS986 to at least try this ROM and see if RIL (cell calling) works on your phone. As noted early on in this thread this ROM does not generally work with Verizon phones for cell calling (or any custom ROM). While this was a documented problem that has not been solved for all, I for one have a Verizon phone working. Worked with build Lineage-16.0-20191106, TWRP-3.3.1-..207_g4, nano gapps, and addonsu I have had service since November of last year. I just did a "dirty flash" to latest version 16.0-20200324, with TWRP 211_g4, and it still works .

I only updated to latest version because, about two weeks ago all Verizon service went down in my area, and Verizon insisted it was my phone's problem instead of their system (they were wrong). So they insisted I needed to do a factory reset and I did. After this reset my phone shows all incoming calls that are not in my contact list as "unknown" . So I updated Build hoping to fix this. Did not fix. I don't see anywhere in the ROM where caller ID is activated or blocked. Any help appreciated for this one issue.

Other than this recent problem, phone has worked flawlessly and runs much cooler and faster that stock.

tullyp
[G4 Android Development] Knowbody42:
OK, I have MicroG set up on my phone, and the Play Store works. But the phone's internal GPS doesn't seem to work.

I have location backends: DejaVu, GSM Location, Wifi Location, Nominatim Geocoder set up from F-Droid, and MicroG has ticks for everything except the last one which is "UnifiedNlp does not have Location to test Geocoder"

I have Location enabled with High Accuracy.

In SatSat, it doesn't get a fix on any satellites.

I don't know if it's the ROM, MicroG, or the phone itself.
[G4 Android Development] steadfasterX:
You installed these backends but which do you had choosen then in microG settings? I'm using dejavu here and the mentioned message in microG is normal when there is no location found. Try the mozilla one (see the back ends mentioned in FAQ 9) otherwise.
[G4 Android Development] Knowbody42:
All of them.

And I gave them the required permissions, and set up the database for GSM Location Service.

I also tried flashing a different modem bin, but that broke wifi, so I flashed it back.
[G4 Android Development] Xain_1425:
Thanks it worked. But I am facing new issue Gcam app crashes when I select Video. Did you face this issue ?
[G4 Android Development] steadfasterX:
How long did you wait outside with clear sky? first gps fix can take up to 20 min even when network location backends are used.
[G4 Android Development] Knowbody42:
I left it overnight with high accuracy enabled
[G4 Android Development] steadfasterX:
This does not work when indoors
[G4 Android Development] Knowbody42:
I left it outside on the grass for over an hour. Still nothing.
[G4 Android Development] Ponder Stibbons:
Please test your phone with one of the following apps and refresh AGPS data . They are like swiss army knifes (you know MacGyver?)

SatStat

GPS, sensor and network status.

A diagnostic tool that displays data reported by sensors in the phone.

GPS and other location providers:

Refresh AGPS data (if supported by phone) either manually, or when a new data connection is detected.

GPS Status & Toolbox

GPS Status & Toolbox is a simple program to show all the GPS and sensor data of your phone. It is designed to be simple, yet effective. It helps you to see what is happening while the GPS is trying to acquire your locations and can be used as a simple compass, as a leveling tool. It will measure the phone’s speed and acceleration, the brightness or the air pressure (if your phone has the necessary sensors.) The program also supports basic navigation functions that are useful when you are out in the wild. The app has four main screens plus it can display a system notification to show GPS data.

Keep your GPS fast: Reset or download A-GPS data regularly for faster updates.
[G4 Android Development] zxyzgt:
I have a UsU'd vs986 which is running LOS15. I want to upgrade to LOS16. In OP it is said to update bootloader stack to MM 20p and provided TWRP flashable files. How can I know the current bootloader stack version? For the TWRP flashable files, is it called "vs986_2BA_UsU_bootloader_arb2.7z"? Thank you for your help!
[G4 Android Development] steadfasterX:
Keep your bootloader as it is for the vs986.
[G4 Android Development] cking2000:
tap and hold Problems & infrared

Hello,

i use the last lineage 16 version with gapps on a h815.

When i tap and hold a link this often will be ignored and i need do redo it 3 or 4 times.

A single click on a link will make the same problems.

Change to opengl don't help to resolve the problem.

What can i do now?

And the second question: it is possible to use anyremote and infrared on the h815?
[G4 Android Development] zxyzgt:
Got it. Thanks for your reply. :good::good::good:

BTW, How can I know the bootloader stack version?

Besides, do I still flash the TWRP flashable MM modems?:confused:
[G4 Android Development] lgg4-user:
I had a camera freeze –*was able to get a logcat. From around line 435 you can see it gets stuck in the same loop over and over again. Not sure where to start with making sense of it.
[G4 Android Development] steadfasterX:
Yea thx the camera freezes are easily to reproduce so no logs needed.
[G4 Android Development] zxyzgt:
Please help.

I just flashed LOS16 (kept its bootloader stack as it is) on my vs986 (USU'd, running LOS15 without any issue) successfully. After I flashed magisk from TWRP, it entered into the OS without any problem. But once I granted the root privilege to Titanium backup, it rebooted automatically.

Now it can't go to the OS (stuck on the LG logo screen) and it can't go to TWRP using Power+volumn down comb (stuck on the recovery mode loading... screen). How can I fix it? Please help.
[G4 Android Development] chrysopra:
Your problem looks as if your phone has gone into bootloop mode. You might try two options: First place your phone (without battery) for about 10-15 minutes in a fridge. If it starts in cooled mode, your big kernels have gone.:crying: You may try to install 4-kernel versions of bootloader an ROM:

https://xdaforums.com/g4/general/guide-create-custom-x-cores-boot-image-t3718389

Second, when your phone is turned off, press volume down button. Keep button pressed, then hook your phone to your computer (via usb). The G4 should now start into adb mode, where you can reinstall the bootloader :cool:
[G4 Android Development] zxyzgt:
Thank you for your help! :good::good::good:

The first one didn't work for me. I am in the adb mode now. Could you please recommend a tutorial for how to reinstall the bootloader? Which version should I reflash? [MENTION=5545101]steadfasterX[/MENTION] made so many versions, I am confused to choose any one of them... (my G4 is vs986 BTW)
[G4 Android Development] chrysopra:
You could give the new SHRP a try, if you´re running on Pie aka Lineage 16

https://xdaforums.com/g4/development/recovery-sky-hawk-recovery-project-2-2-t4074497

The download source:

http://leech.binbash.rocks:8008/SHRP/P/

Compared to TWRP its real cool stuff. Much more intuitive.

Otherwise the classic TWRP

On steadfaster´s server you may also find the TWRP versions for several android versions (MarshMallow, Nougat, Oreo, Pie) Bootloader version should match your ROM;) From the appropriate folder, just grab the newest image.

For the installation:

Place your bootloader (twrp.img or shrp.zip) into the same folder as your adb

enter the command : fastboot flash recovery twrp.img (or shrp.zip)

next command : fastboot reboot bootloader

Now, you should have a running bootloader. :D

If yes, please go backwards to steadfasters server an consider a little donation on his Gas station section...
[G4 Android Development] zxyzgt:
Sure I will donate.

1. Tried SHRP, got error message: Failed. The image is not a boot image...

2. Flashed TWRP pie successful. But when restart bootloader from fastboot, I can't see TWRP, it went back to fastboot mode. Tried manually, still stuck on the recovery mode loading... screen

3. Tried different versions of TWRP, including N, O, P, no luck:(:(:(

But still thank you for your help
[G4 Android Development] chrysopra:
With SHRP it's my fault. You're right, it's a zip which means you can flash it out of TWRP, not with fastboot.

(You were lucky if you would get to this point, I suggest) I just read about UsU not being able to run the fastboot boot command.

(I used the offical unlock on my phone, so don't have any experience with UsU) I'm just a convinced user with limited knowledge of the whole stuff. Enough for running my phone, but far too less to bring yo any further, I regret:(

MaybeSure steadfasterX could help, but recently he seems to be busy and only occasionally visiting this board.

I hope you're lucky and he'll be soon back to help you:fingers-crossed:
[G4 Android Development] zxyzgt:
Thank you. Look forward to [MENTION=5545101]steadfasterX[/MENTION]'s help!
[G4 Android Development] steadfasterX:
This sounds not like a LOS issue but a hardware one.

first of all we should eliminate the wrong placed wordings:

the

bootloader stack

(or in short just "

bootloader

") is a

set of partitions

which are responsible to actually boot up to the state where you see the LG logo.

fastboot itself is part of that for example.

... but e.g. recovery (i.e. TWRP/SHRP) or the download mode are

NOT

part of the bootloader (stack) though which I saw mixed up in a previous user's answer.

so now that this is clear you should try to find out the root cause of your problem:

first, read the UsU FAQ , especially

#14

!

if you flash TWRP you should try the ilapo version with 2cpu then 4cpu first: http://leech.binbash.rocks:8008/TWRP/ILAPO-O/ it does not matter that it is been made for Oreo.

If TWRP does not boot with the regular TWRP image but boots with one of these (see the correct key combo in the UsU OP) then you are catched by the ILAPO.

Keep in mind that you have to boot to TWRP directly after flashing (power off after flashing, then turning on and boot directly to TWRP by the key combo).

so to sum up, ensure that:

- it does NOT boot to recovery when flashing the regular TWRP

- if it boots to recovery with the ILAPO twrp image

All details about the ILAPO and possible workarounds are described in the link of FAQ #14.

.-
[G4 Android Development] zxyzgt:
Thank you so much for your guidance. I agree with you. After flashed with LOS16, there was no problem entering into OS. It even fixed the issue for flashlight which was from LOS15 :good::good::good:. I guess there was something wrong with Magisk since it bootlooped immediately after magisk granted root to Titanium.

But I will try your way. Thanks again and fingers-crossed.:fingers-crossed:
[G4 Android Development] steadfasterX:
Yes trying without magisk is always the first option but as you mentioned in one of the previous posts that your device now just boots directly to fastboot ...
[G4 Android Development] owlery_hk:
dont think this is G4 specific, but is there a way to separate the rotation suggestion and keyboard switcher options?

i am trying to get the keyboard switcher on the right and the rotation suggestion on the left.

[IMG="screenshot"]https://i.imgur.com/AURuEzd.png[/IMG]
[G4 Android Development] Knowbody42:
I found out what the problem was: It seemed to be the antennas.

Before, SatStat was showing zero satellites found.

Then I replaced the back frame with the antennas, and now it's finding satellites and getting a location fix.
[G4 Android Development] zxyzgt:
I got updates: Good news and bad news.

Good news: ILAPO-2cpu_twrp-3.2.3-PREVIEW-144_g4_O.img works! Finally I am able to see TWRP interface. Thank you, [MENTION=5545101]steadfasterX[/MENTION]. :D:D:D

Bad news: still got stuck at LG logo when tried to enter LOS. I reflashed LOS (MM modem first of course), no luck. Just saw some errors in TWRP:

Magisk addon.d failed.

Can't find magisk binaries ....

But it continued to overwrite the ROM partition and succeed.

After I restarted, it still got stuck with LG logo.

I also tried magisk uninstaller in TWRP, it is said magisk not found...

I don't know what to do.

Is there any specific ROM to try? Or is there something wrong with the boot.img:confused:
[G4 Android Development] masemoel:
Have you tried to disable the 2 big cores in Lineage's boot.img?
[G4 Android Development] Le-Kube:
Hello, I just followed the guide to upgrade my H815 from stock to the latest lineage OS 16.

First of all, many thanks for the work (both of the guides and the OS), 'im so glad i can keep on using my G4 and give it a new life.

I am still in the process of adapting but there is 2 simple features I can't get to work :

-"turn on the flash light by long push on power button with screen off"

"smart lock" (by geolocalisation)

Are those features supposed to work ? and if yes do you have any recommendations on the how ?

I have a final question that may be dumb, but, can (and should) I use my phone with apps like my bank app and paylib ? (maybe i need to "unroot it or smth ?)

Thanks again for the work, Long Live the G4
[G4 Android Development] steadfasterX:
ok. you didn't followed my advice completely. so again. slowly.

one by one

:

1. when TWRP boots with the ILAPO version but does NOT boot when you flash the regular TWRP version your device has a hardware damage!

2. if that is the case you have to follow FAQ #14 of the UsU thread. in that FAQ you find a link to the ILAPO thread which explains everything around it.

3. start clean. that means follow FAQ #2 of this thread and do a "

full clean

flash" of LOS ! This is crucial important before doing anything else.

4. in that ILAPO thread you see several options how to workaround your hardware issue without any guarantees how long that will work. its a hardware damage which cannot be solved by software.

5. the first thing you might try from that thread is following the X cores guide which is linked there as well. that guide will help you in modifying the boot image of any ROM you like to disable CPU cores which CAN help in extending the life of your phone. so in terms of LOS you would extract the boot image from the LOS zip and follow that mentioned guide to create a 2 or 3 or 4 CPU boot image out of it.

6. if that boot image has been flashed (TWRP -> img or in fastboot flash boot ..) and LOS actually boots this is another proof that you get catched by the ILAPO but you might can work with that for while. Keep in mind that disabling cores will decrease performance obviously but better then nothing.

7. DO NOT FLASH MAGISK before EVERYTHING is working as it should!

8. DO NOT FLASH GAPPS before EVERYTHING is working as it should!

the flash light is an issue related to the camera and mentioned in the known issues linked in the OP. here the exact one: https://github.com/Suicide-Squirrel/issues_pie/issues/26

smart lock by geo is a google feature not a LOS one. if you encounter issues it might be GAPPS related. always use the same or better older version of GAPPS as the ROM date.

.-
[G4 Android Development] Le-Kube:
Ok thanks, I tried to research for "flash" and "flash light" in the thread but number of result not related to the flashlight threw me off. Guess no more quick access to flash light, no big deal.

If I want to use an older version of GAPPS, do i need to wipe the whole system again or is there a way to only wipe GAPPS ?
[G4 Android Development] zxyzgt:
Creating 2 core boot.img now. Thanks for the heads up.:good:

---------- Post added at 10:18 AM ---------- Previous post was at 10:15 AM ----------

Thank you for your help! It is a hardware related issue. I am creating 2-core boot.img now. Hopefully it works:p
[G4 Android Development] jovanv:
A quick question: will there be any problem to devices with disabled cores at boot? With your saying "if needed" I understand that there should not be serious troubles but you would know better :)
[G4 Android Development] steadfasterX:
This build actually will help all devices , ilapo or not :)
[G4 Android Development] jovanv:
Can confirm! Two days with this great ROM on my ILAPO device (after disabling the big cores in boot.img) and no problems at all. And the battery life seems very good, better than before (February version of this ROM) but need more days to have a better estimate.
[G4 Android Development] tullyp:
New 20200515 build working with RIL cell service on my Verizon VS986. You can actually watch cores go in and out of use in Kernel Auditor shortly after boot (really cool! ;) ).

Still no incoming caller ID. But caller ID comes right back if I flash back to stock (worked 3 times). I am assuming this is a Verizon issue somehow connected to VoLTE. I am on prepaid plan, and VoLTE is deactivated for Prepaid by default, but what I am wondering is if all Verizon calls go thru LTE now anyway, as CDMA is supposed to be decommissioned, and Verizon just doesn't announce it.

All happened after our local towers went down for a day (switch over to VoLTE maybe?). Verizon wants to know what update I have on my phone when I called in for customer service, and of course I can't tell them I'm on a custom ROM.

tullyp
[G4 Android Development] Thordgar:
Hi [MENTION=5545101]steadfasterX[/MENTION], finally I had time to try aoleary's custom roms and today I installed your last LOS (15/05).

On every rom (except H-ROM maybe because it's a modified stock) the phone is stuck in 3g (no 2g and no 4g).

I tried both 20p and 29a modem with the same result.

I'm using an officially unlocked H815.

Can you help me? Thanks.
[G4 Android Development] ThePsymoon:
Since this morning, I have an issue with mobile network connection on my h815. I was still running on the CALMDOWN experimental build (with was working very well), and I notice limited network connectivity (emergency calls only, no internet access). I tried to restart, shutdown and switch on and off airplane mode and it did not solve the issue. Sometimes, the network connection was working during few seconds (enough to load a web page), but stop working just after. In the status bar, the phones seems to be connected to the network, but without data.

I don't know if it can be related, but yesterday, my phone froze when I was loading a webpage, over 4G. I had to remove battery (the system was unresponsive, even power button). Afterward, it was working ok and I did not notice anything special yesterday evening.

In order to try to solve the issue, I installed the new build (20200515), with regular clean flash. The system is working properly, but mobile connection issue is not solved. Calls are not working. Should I try to perform a full clean flash?

I don't know if the issue is hardware or software... (I would guess soft as it sometimes works during few seconds...) Is there a way to get a log?

Thanks in advance for your support.

Edit: the issue is likely related to my mobile operator which seems to have some troubles in my area today. I will update this post in the coming hours/days...

Edit2 : I confirm the issue is related to my mobile operator.
[G4 Android Development] quetzaltr:
Hi. Once I asked aeolary in telegram group he directed me you to ask. My question was if we have any chance to configure boot (start up and turn off) options can we change boot order entriees in init files which we can extract boot partition via twrp for configure boot order make more passive for g4. I meant for example diable big core at system start may reduce maximum briggtness etc. For sometimes my phone cannot success start up the system so phone turn of itself but my battery’s health very bad though may you should judge this first [MENTION=5545101]steadfasterX[/MENTION]
[G4 Android Development] Thordgar:
An update:

I noticed that my phone its not locked in 3g but it's locked in the same type of network that I selected before flashing a custom rom. So I flashed stock, selected 4g and flashed LOS again to "solve" my problem.
[G4 Android Development] Feduz:
is this the best rom for now? i have nougat stock
[G4 Android Development] Not_perfect:
Yes, works well for me! The battery life is much better;)
[G4 Android Development] zwab:
Bluetooth Crashing Issues

Good evening all, hope you are well.

NOTE: I have removed the majority of this post temporarily as the Forum keeps detecting it as spam for some reason.

I'm looking to get some assistance with a bluetooth crashing error I'm getting as soon as bluetooth is enabled.

I've been using the ROM for a while without bluetooth as I think its a fantastic ROM, but I'm really feeling the urge to be able to use my Smart Watch once again, which I cannot do without functional bluetooth.

As I've been using the ROM for a while, allow me to give a full recount of actions I've taken to date to help you understand what I've done with the device.

EDIT: adding bits of this post back in so that hopefully the spam detector doesn't block my legitimate information.

Actions Taken

1.) Installed LG Up and upgraded device to latest version.

2.) USU'd my device using FWUL

2a.) Link to instructions: [LINK REDACTED due to spam detector, its steadfasterX's thread on how to USU your device.]

3.) Flashed modem from those provided in the OP.

3a.) Link to modems: [LINK REDACTED due to spam detector, its the link from the OP]

3b.) Version flashed: h815_20p_modem.zip

4.) Clean installed LoS using 23rd February build.

4a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]

At this point I had the issue with bluetooth, but was happy other things were working fine and opted to remain on the build. I was able to install various apps I like to use and root with Magisk without any other issues.

Eventually I decided to look into the issue again due to a desire to use my Smart Watch again.

5.) Searched all posts in this thread for "Bluetooth Crash"

6.) Searched github issues for related issues in both closed and open issues.

6a.) Link to github issues: [LINK REDACTED due to spam detector, its the issues page on github from the OP.]

7.) After not finding anything that seemed actionable, I noticed we now had a March build for the ROM, so I CLEAN installed the 24th March build

7a.) Link to build: [LINK REDACTED due to spam detector, its the leechbin link from the OP]

8.) Issue persisted.

9.) Fast-forward to today... Looking into the issue again.

10.) Generated a logcat following Option B in steps 2 & 3.

10a.) Link to instructions: [LINK REDACTED due to spam detector, I got it from the FAQs of the OP.]

10b.) Link to logcat: https://paste.omnirom.org/view/023b15d7

Cheers,

-zwab