yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] trouble.:
Whaaaaaaat! The G2 have custom rom of Android 10 and we v30 users don't?:(
[G2 Original Android Development] jimmygua:
Lineage os for ls980,great job!!!
[G2 Original Android Development] JustIceForSake:
Get out of here! Are you frying kidding me?! Android 10 on the LG G2.?!!! This is preposterous!!! Lg G2 is immortal! Hail to the devs!
[G2 Original Android Development] aleasto:
New builds out

* Fixed video playback in default gallery (and all players using the same sw coded)

* Updated lineage upstream
[G2 Original Android Development] lucavice85:
Is it possible to have a gApps package? In the usual site are not available ... thanks!
[G2 Original Android Development] crsNNN:
[MENTION=4742143]YoDevil[/MENTION]: New builds can be downloaded through Updater?
[MENTION=7342333]lucavice85[/MENTION]: Check this out: https://xdaforums.com/showpost.php?p=80244345&postcount=6206
[G2 Original Android Development] aleasto:
No
[G2 Original Android Development] m.morcielago:
Give some screen shots
[G2 Original Android Development] eKFreak:
does anyone get magisk installed?
[G2 Original Android Development] popxunga:
Thanks for the clarification.
[G2 Original Android Development] aleasto:
In TWRP, mount system and

adb shell rm /system/system/etc/gps_debug.conf

Then reboot and try again
[G2 Original Android Development] chanh2018:
....someone got high temper ....or just being rude
[G2 Original Android Development] theelderstatesman:
Neither is true, it's supposed to be a joke that you obviously didn't like,

because you expected a serious answer to your question.

If you'll check it, you'll see that I supported your question ...
[G2 Original Android Development] popxunga:
Come on guys... let's finish this story.

It is clear now that's just a silly defect.

Cheers!
[G2 Original Android Development] rootarded:
Thanks for your suggestion. I did that, but even with the file removed my phone still can't locate via mobile network. Additionally my GPS fix is now taking forever.

My suspicion is that something between ROM, fused location services and the network location provider is not working out. In other threads I also read about problems regarding microG and other projects not being able to implement UnifiedNLP because of some permissions issue. Looks like Google changed the way ROMs and Google Play Services interact.

So should I take some logcats for further investigation?
[G2 Original Android Development] aleasto:
Nah i doubt logs alone can be helpful. Will try to reproduce on my device.
[G2 Original Android Development] theelderstatesman:
I don't know, if I should continue to report this, but the new build (12.04.2020) has the same old problems for me: the updater doesn't work and it doesn't connect to my main wifi.

Like so many others, I'm most grateful for your work and really appreciate your support ...
[G2 Original Android Development] aleasto:
Try

adb root
adb remount
adb shell "sed -i s/pmf=1/pmf=0/ /system/vendor/etc/wifi/wpa_supplicant.conf"
adb shell "rm /data/vendor/wifi/wpa/wpa_supplicant.conf"

Then reboot and try to connect again
[G2 Original Android Development] theelderstatesman:
I did the steps successfully until adb remount. Then, I get the remount failed error (see jpg) ....
[G2 Original Android Development] aleasto:
Ah, you're using magisk.

In that case, replace `adb remount` with

adb shell "mount -o rw,remount /"
[G2 Original Android Development] theelderstatesman:
You are my hero ... It worked ... Mille Grazie ...

Now, do I have to repeat the steps in the future?
[G2 Original Android Development] aleasto:
Until a proper fix gets merged, yes. Or just don't update until then.

Let me look into that
[G2 Original Android Development] theelderstatesman:
You can't imagine, how happy I am ... Again, mille grazie ...

---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------

[MENTION=4742143]aleasto[/MENTION] found a temporary solution. Pls., check the latest posts ...
[G2 Original Android Development] aleasto:
[MENTION=6321840]theelderstatesman[/MENTION]

So this build should work, right? https://drive.google.com/open?id=11RmKdkPTQGjS6esSevbETCLbT3xjjvpi

Clean flash mandatory
[G2 Original Android Development] piep91:
I've checked, perfect, thanks a lot for the support!! Both you for providing the log and [MENTION=4742143]aleasto[/MENTION] for his temporary solution. At least now i can keep a 17.1 build and decide to repeat the process with every update or just wait for the update that will have the definitive fix
[G2 Original Android Development] theelderstatesman:
YES, it does. I'm so happy ... Thanks again ...
[G2 Original Android Development] raymccoy007:
Hello, i have installed the latest lineage-16.0-20200325-nightly-d802-signed.zip. Can you please tell the steps to upgrade to lineage-17.1-20200412-nightly-d802-signed.zip? Can i use my existing recovery to install? Do i need to update TWRP and then the answer is yes where can i get it? Which gapps must i download?

The last times i only have to download the nightlys and it boots automaticly into to recovery and flashing. Can you please tell the steps i should make?

Greatings from Germany
[G2 Original Android Development] popxunga:
Read post #319.
[G2 Original Android Development] aleasto:
[MENTION=6321840]theelderstatesman[/MENTION]

And what about this one?

https://drive.google.com/open?id=1662_9NGALfAnrqqPvm41UOysIk2UaVt7
[G2 Original Android Development] theelderstatesman:
[MENTION=4240321]popxunga[/MENTION] correctly referred to the post #319, based on post #318 by [MENTION=4742143]aleasto[/MENTION], but I did it in a different way, if I remember well.

I advanced wiped Dalvik, System, Data and Cache. Then, I rebooted to recovery and flashed the rom and the GApps.

One more reboot to recovery to flash Magisk and then reboot to system.

The newest version of TWRP can be found here:

https://www.gregtwallace.com/lg-g2/g2-twrp/#download-section

My GApps version is BiTGApps-arm-10.0.0-v0.5-SW_signed.zip, but officially it doesn't exist anymore, so that you can use the one from the guide, [MENTION=4742143]aleasto[/MENTION] referred to (use the arm architecture):

https://opengapps.org/?api=10&variant=nano

---------- Post added at 03:25 PM ---------- Previous post was at 03:20 PM ----------

I'll try it ...

---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------

It's a new one, isn't it? I'll try it now and will tell you soon ...

---------- Post added at 03:31 PM ---------- Previous post was at 03:28 PM ----------

Sorry for the confusion, I'll try it ...

---------- Post added at 03:44 PM ---------- Previous post was at 03:31 PM ----------

lineage-17.1-20200412-UNOFFICIAL-d802_no_pmf.zip WORKS.

Mille Grazie for your work and forgive me my stupidity ...
[G2 Original Android Development] aleasto:
I'm sorry, did you download from the link in the post, or from the link in your email notification? I edited the link after I initially posted the wrong link (with the same file name...).

To be sure, sha1sum of the correct build i wanted you to test is 83aed246edca9f5d59d9fb1e5a602bfc81c944ba
[G2 Original Android Development] theelderstatesman:
I downloaded it from the post and the sha1sum I get is (see jpg):

83aed246edca9f5d59d9fb1e5a602bfc81c944ba

It seems the same. Shall I upload the file I downloaded to my GDrive?
[G2 Original Android Development] aleasto:
Ok if sha1 matches we good.

Will be in tomorrow's official
[G2 Original Android Development] theelderstatesman:
I don't know, how to thank you - mille grazie dalla Svizzera ...

---------- Post added at 04:53 PM ---------- Previous post was at 04:50 PM ----------

And if you ever need somebody again to try out something, feel free to count on me ...
[G2 Original Android Development] theelderstatesman:
To make things easier for you, here's the BiTGApps-arm-10.0.0-v0.5-SW_signed.zip on my GDrive:

https://drive.google.com/open?id=1oI-fARNMDHPjjP0UVjSsAXFltspu81OZ

P.S.: You have to use this version, because the setup wizard doesn't work with newer versions ...
[G2 Original Android Development] aleasto:
The new official build will also fix LiveDisplay, apparently nobody noticed it was broken.
[G2 Original Android Development] theelderstatesman:
As you might have expected, lineage-17.1-20200413-nightly-d802-signed.zip works ... Thanks again so much ...
[G2 Original Android Development] rootarded:
It was noticed. But we knew you'd fix it. :angel:

---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------

Is there any advantage in this package over open Gapps?
[G2 Original Android Development] theelderstatesman:
In my opinion, no ... But, when I first used it, there was no version of Open GApps for Android 10 yet ...
[G2 Original Android Development] vbfather:
Hi,

I have the same problem here

https://support.google.com/android/thread/12185672?hl=en

Any idea?
[G2 Original Android Development] agrumpyone:
Backup/restore with LOS recovery?

IMHO it seems that the LOS Team is pushing it's own recovery. If i correctly understand the latest commits, the installation of LOS recovery is (or maybe will in future) also be an part of the LOS Updater. As i haven't much info about the LOS recovery. Is it possible to do backups and restoring them? At the moment i'm doing my backups with TWRP but will switch to LOS recovery if they provide backup/restore partition functionality.

Thanks for any infos
[G2 Original Android Development] aleasto:
You'll find a toggle in Developer Settings to enable auto updating recovery with every OTA.

No we don't do backups
[G2 Original Android Development] rootarded:
Hi [MENTION=4742143]aleasto[/MENTION], have you been able to reproduce said behaviour?
[G2 Original Android Development] cgrig1981:
i try to flash lineage 17.1 on my D802 an i get error 7, i have 3.3.1-0 twrp . what do i have to do??
[G2 Original Android Development] aleasto:
You read the error
[G2 Original Android Development] cgrig1981:
It says wrong aboot please update
[G2 Original Android Development] aleasto:
Follow the instructions at https://wiki.lineageos.org/devices/d802/install#downgrading-bootloader to install a supported bootloader.
[G2 Original Android Development] cgrig1981:
Thank you
[G2 Original Android Development] Holgott:
Hi.first oft all thank you for this great Rom. I was getting a New display for my phone just because i saw that there are still good Roms for it. At the Moment everything is working except dt2w. I activated it in settings alrdy but it doesnt work. Does anyone got a clue in how to fix it/am i the only one with this issue?
[G2 Original Android Development] theelderstatesman:
I'm not a specialist with this function that I never use, but (after I tried it) I would say, it works for me ... I'm on the latest build: lineage-17.1-20200418-nightly-d802-signed.zip ...
[G2 Original Android Development] rootarded:
Sometimes this function is a bit quirky and doesn't work reliably, I had this happen with some earlier nightlies too. First, make sure to update to the latest nightly. If it's still not working try a clean flash with no restoring /data. If it still fails, you can try going back to stock (flashing via recovery should suffice) and try again. If it still doesn't work open up the secret menu via the dialer (3845#*802#) and select "update touch firmware" and reboot.
[G2 Original Android Development] Holgott:
Hey, thank you for your hints. It was a faulty connection of the nearby Sensor while assembling the new display. I connected it again and now it is working ;)
[G2 Original Android Development] raymccoy007:
Hello, now i have LeneageOS 17.1 installed. Today i got informed about new Lineage-17.1-20200418-nightly-d802-signed.zip so i downloaded it and click on install but then the lg 2 starts and and i can't see if the latest the nighty is installed. Can anyone tell there storage path of the Lineage-17.1-20200418-nightly-d802-signed.zip then dowloaded from the notifation updates. Maybe i have to install it manually in the twrp recovery environment. But i can't find the downloaded file So can anyone help me?
[G2 Original Android Development] aleasto:
https://github.com/LineageOS/android_frameworks_base/commit/aa080f96763a9d38f21fb33de93216cd207a5930

Location modes are not a thing in Android 10

The quicksettings tile has been removed

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/271797
[G2 Original Android Development] rootarded:
Thank you! That clarifies a lot!

One thing is still odd though - that mobile network location doesn't work at all when disabling WiFi and WiFi scanning. I will test this with the next build including those commits.

---------- Post added at 11:47 AM ---------- Previous post was at 11:37 AM ----------

Hi, make sure you have installed the latest version of TWRP (3.3.1-0). If everything works correctly your phone should reboot into recovery and start updating when selecting "install" within Lineage Updater - you should be able to see it doing that. Also check the installed Lineage version inside the updater app, here you can see clearly if it installed the new version or not.

---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------

Glad to hear it worked! :victory:
[G2 Original Android Development] neerajverma04:
Which recovery used for Verizon version?
[G2 Original Android Development] theelderstatesman:
Sorry to say that I'm using the latest build lineage-17.1-20200418-nightly-d802-signed.zip, but the Lineage Updater still doesn't work for me ... Of course, I consider that a minor problem ...

---------- Post added at 01:23 PM ---------- Previous post was at 12:34 PM ----------

The recoveries are here: https://www.gregtwallace.com/lg-g2/g2-twrp/#download-section
[G2 Original Android Development] neerajverma04:
Thanks.. it installed fine on Verizon after updating twrp
[G2 Original Android Development] rootarded:
Hi and welcome to the XDA forum! :highfive:

I am sorry to tell you that all those camera functions depend on proprietary LG binaries which can't just be ported to Android 10. So no, except for the splitscreen function, which is supported by Android 10 natively you can't use those stock based functions.
[G2 Original Android Development] vbfather:
[MENTION=4742143]aleasto[/MENTION]

i posted my problem here and got no answer

could you please help me?
[G2 Original Android Development] popxunga:
Hi

I just upgraded from LOS 16 to 17 by doing a dirty flash from TWRP recovery followed by a davlik and cache wipe. I found no significant issues so far. Congratulations Dev Team !

However I noticed that unlock the phone using a numeric pin after restart takes a significant amount of time. Anyone experienced this ?

Thanks.
[G2 Original Android Development] rootarded:
Does it still happen after a couple of reboots?

---------- Post added at 12:11 PM ---------- Previous post was at 12:05 PM ----------

[MENTION=4742143]aleasto[/MENTION]: Unfortunately mobile network location still doesn't work at all.

As soon as I disable any WiFi scanning no coarse location is detected and GPS fix is taking very very long. The same happens when I am out of range of any WiFi networks.

Do you need logs?
[G2 Original Android Development] popxunga:
Yes it does. It is a persistent behavior upon each restart. However, the time needed on the 2nd and 3rd restart was shorter than the 1st one.

I can't do it anytime soon, but I'll try a clean flash.
[G2 Original Android Development] theelderstatesman:
Yes, do that. Sometimes, a clean flash works miracles ...
[G2 Original Android Development] juanlc18:
I entered the develoment telegram group and some idiot reported me thinking I was a bot. Now my account is blocked you idiot
[G2 Original Android Development] theelderstatesman:
I'm on the latest build lineage-17.1-20200424-nightly-d802-signed.zip, but the Lineage Updater is still not working for me ... I consider that a minor problem, but I'm just curious, if anybody else is experiencing the same?
[G2 Original Android Development] crsNNN:
I think it's just you. It works perfectly for me from the first day since the official build was launched.
[G2 Original Android Development] montechristos1:
With which recovery?
[G2 Original Android Development] theelderstatesman:
You're right. I should have mentioned that. Sorry. I'm on twrp-3.3.1-0-d802-bump-blastagator-signed.zip ...
[G2 Original Android Development] rootarded:
Did you allow TWRP to modify your /system partition?
[G2 Original Android Development] popxunga:
Nope... just tried it for the 1st time after the upgrade from 16 to 17, and it worked fine.
[G2 Original Android Development] theelderstatesman:
Yes ...

---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------

Are you also using twrp-3.3.1-0-d802-bump-blastagator-signed.zip?
[G2 Original Android Development] popxunga:
Yes I'm using TWRP 3.3.1.0.
[G2 Original Android Development] rootarded:
Another idea: did you use Autorec2 to install TWRP on stock? Or do you use boot stacks?
[G2 Original Android Development] theelderstatesman:
I used AutoRec, but that was many years ago in 2014 ...
[G2 Original Android Development] aleasto:
What am i supposed to get from a "Updater is not working" report. Any information??
[G2 Original Android Development] theelderstatesman:
Sorry, you're right. The Lineage Updater works fine, until it reboots to system, then it takes a long time, where it's like stuck with the lineage logo, suddenly interrupts and boots back to recovery ...
[G2 Original Android Development] rootarded:
So you installed TWRP from within Kitkat or Jelly Bean? If second you might have the wrong boot loader. That's why it's recommended to first install the latest stock ROM via KDZ or TOT and then install LOS. Also installing boot stacks (to avoid having to flash stock) could cause problems.

EDIT: Am I really the only one with no mobile network location? Did anybody else test this outside of their home?
[G2 Original Android Development] theelderstatesman:
Thanks for your help, but I don't recall anymore, how I did it, it was too long ago. While on LOS 16 (and before I guess), I never had any trouble with the Lineage Updater and I was always dirty flashing from one build to the next without any problems ...

---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------

Can you tell me, how to get a log file or any other information that is useful to you?

---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------

I would like to help you with your problem. Pls., tell me exactly what to do and I will do it?
[G2 Original Android Development] nickname9:
if you need the right bootloader follow the steps in this link: https://wiki.lineageos.org/devices/d802/install#downgrading-bootloader
[G2 Original Android Development] rootarded:
Using those instructions I bricked my device and had to restore partitions via Linux manually, no fun. Even though I followed that guide exactly. My advice is always flashing Lolipop via TOT and after rooting installation of TWRP via Autorec2.

---------- Post added at 02:18 AM ---------- Previous post was at 02:08 AM ----------

Thanks! :)

You just have to disable WiFi, Bluetooth and all "WiFi scanning" and "Bluetooth scanning" options within the location menu. After that enable location using the pull down menu and start Google Maps. When it asks you to enable things, decline. If everything works as expected it should then show your rough coarse location, indicated by a rather big blue circle.

Or the same happens to you as I experience: it wont give you any location until eventually it's able to get a GPS fix after some (long) time, if ever.
[G2 Original Android Development] theelderstatesman:
Ok, I'll try that tonight ...

---------- Post added at 08:19 AM ---------- Previous post was at 07:47 AM ----------

Just out of curiosity, is there a way to find out, which bootloader is installed?
[G2 Original Android Development] theelderstatesman:
As you might have guessed, it's the same, as you are experiencing ...

I waited for about 15 to 20 minutes, but nothing happened. I admit, I was at home, but tomorrow I'll try it outside and then I will tell you about the result ...
[G2 Original Android Development] IT Tech:
I posted this earlier regarding the VS980:

I am in the United States. When trying to make a call I received the error "Mobile network not available". The phone did say I was connected to VERIZON but the Default network setting was GSM/WCDMA/LTE. I had to change this setting to "GLOBAL" which allowed me to make and receive calls.
[G2 Original Android Development] rootarded:
Thank you! It shouldn't matter if inside or outside, as network location should work regardless. :)

Unfortunately I don't have this setting (using the *#*#4636#*#* menu).

Interestingly if I install apps for checking the cell ID and location, those are able to track me as they use their own system. So it looks like the ROM isn't properly forwarding the network cell information. Just a guess. ;)
[G2 Original Android Development] theelderstatesman:
Just like you, I'm always willing to help. So, I'll try tomorrow outside with the sunshine, maybe it helps :)
[G2 Original Android Development] aleasto:
What recovery are you using?

Are you encrypted?

Boot back into recovery after you get stuck and run

adb shell mount /cache
adb pull /cache/recovery/last_log

And share last_log
[G2 Original Android Development] theelderstatesman:
Mille grazie. The recovery is twrp-3.3.1-0-d802-bump-blastagator-signed.zip. I'm not encrypted. I will run the commands as soon as the new build is out, tell you about the result and add the log file ...
[G2 Original Android Development] IT Tech:
Settings > Network > Mobile Network > Preferred Network Type

You can not change it from here?
[G2 Original Android Development] rootarded:
There's no GLOBAL option, just 4G, 3G and 2G. Also telephony and anything else besides network location is working without issues.
[G2 Original Android Development] theelderstatesman:
So, yesterday I forgot to do it, but I already did it today and the result is the same ...

Did you see this question in post #457? = Just out of curiosity, is there a way to find out, which bootloader is installed?

Do you have an answer?
[G2 Original Android Development] rootarded:
Unfortunately I can't help you as I really don't know.

My advice is to make a backup of /system and /data, flash stock LP via TOT and root + install TWRP via autorec2 afterwards, then restore your backup and done. The whole process shouldn't take more than one hour.

I'm sorry I don't have a better answer.
[G2 Original Android Development] theelderstatesman:
Thanks so much anyway ...
[G2 Original Android Development] theelderstatesman:
Thanks once more for your answer. I googled it and that's what I got from two of the sources:

1) adb shell getprop ro.bootloader

https://xdaforums.com/showpost.php?p=76445867&postcount=12

Result: Returned "Unknown" ...

2) Kernel Adiutor (app), “Device” tab

Result: Needs root, then returned "Unknown" ...

3) Use cpuz for android under "system" tab!

https://xdaforums.com/showpost.php?p=80175152&postcount=14

Result: Returned "Unknown" ...

Source:

https://xdaforums.com/showthread.php?t=1030062

According to this source, it must be the jb (jellybean) bootloader,

since I used AutoRec and didn't change the

bootloader since then

(at least, as far as I remember) ...

Source:

https://www.reddit.com/r/lgg2/comments/268czj/trying_to_find_bootloader_version/
[G2 Original Android Development] theelderstatesman:
After executing: adb shell mount /cache, I get this error:

mount: mounting /dev/block/mmcblk0p31 on /cache failed: Device or resource busy (see also the annexed jpg) ...
[G2 Original Android Development] aleasto:
Then probably it's already mounted (i'm not too familiar with twrp). Skip to the second command
[G2 Original Android Development] theelderstatesman:
After the second command, I get this:

adb: error: remote object '/cache/recovery/last_log' does not exist

(see also jpg) ...
[G2 Original Android Development] aleasto:
Did you wipe cache?

What's the output of

adb shell ls /cache
adb shell ls /cache/recovery