yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] IT Tech:
@aleasto

Using: VS980

lineage-18.0-20201130-UNOFFICIAL-vs980

BiTGApps-arm-11.0.0-R19_signed

TWRP 3.3.1

Magisk 21.1 (21100)

Magisk Manager 8.0.3 (314)(14)

1) With Screen Lock ENABLED:

* Screen does not Auto-wake

* With the screen timeout set, the screen goes to sleep. I can double-tap the screen to wake it. Also, on the lock screen I can double-tap the status bar and it will put the screen to sleep.

2) However, once you get past the screen lock OR with Screen Lock DISABLED:

* The screen auto wakes

* double tapping the status bar does not put the screen to sleep, it opens up the drop-down notification window

* In my prior post regarding the 1126 ROM I mentioned that the only way to put the screen to sleep was to use the power button because the double- tap on the status bar does not work. Now in the 1130 ROM, I can put the screen to sleep by pressing the power button and can now wake the

screen by double tapping the screen. I do not remember being able to do this in previous ROMS. Seems you are getting closer to correcting this bug.

3) PREFERED NETWORK TYPE / PREFERED NETWORK MODE:

The 17.1 ROM's and thus far all three 18 ROM's have a default Preferred Network Type / Preferred Network Mode of: GSM/WCDM/LTE. When using MESSAGES (texting) you cannot receive text messages and would receive the error message "WAITING FOR CONNECTION". I have to change the Network Type to GLOBAL in order for this the Messages App to work and be able to send and receive texts.

Now, in the latest 1130 ROM with the default Preferred Network Mode set to GSM/WCDM/LTE the MESSAGES App will appear to send a text message, I receive the "WAITING FOR CONNECTION" message briefly then it appears to send the text but it actually does not. Again, the only correction for this and to allow the MESSAGES App to work is to set the Network Type to GLOBAL.

4) LOSING WIFI CONNECTION ON INITIAL SETUP (seems to be fixed)

I mentioned in a previous post when initially installing the ROM and after booting the phone for the first time and going through the initial google setup wizard it would see my wifi network and then disconnect and I would have to go back a step or two for it to recognize the wifi network again. This seems to be resolved in the 1130 ROM (maybe due to the lineage setup wizard instead of the google setup wizard?)

5) @aleasto is there any chance of having the new ROM releases to be installed as an update? (I remember doing that with the AOSP ROM’s) Your phone would even alert you when a new updated ROM was available and you could download it directly to the phone. Even though I never had much luck downloading the ROM directly to the phone and installing it, I was able to download the ROM via computer, transfer it to the phone and simply flash it right over the existing ROM without wiping anything.

The 1130 ROM overall is working fast and for the most part smooth. Apps are working smooth…WOW, I cannot believe it is the same phone compared to using the 17.1 ROM’s.

Awesome! (y) Great work! ;) Thank You! 👏
[G2 Original Android Development] aleasto:
I presume phone calls don't work either then?

Please try `LTE/CDMA/EvDo/GSM/WCDMA` instead of `Global`.

Not on unofficial builds, I would need to set up my own update server.
[G2 Original Android Development] IT Tech:
Correct the phone and messages app does not work when network is set to GSM/WCDM/LTE.

I could not find LTE/CDMA/EvDo/GSM/WCDMA as an option. The option that was available close to your request was LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA. Both the phone and messages work on this setting. Should I use this instead of GLOBAL?

How about a way to flash a new ROM right over the existing ROM without wiping anything within the same version of course, 18 - 18.1 or 1126 - 1130?
[G2 Original Android Development] aleasto:
There's both :)

But it doesn't matter which you choose, I was just making sure which was the issue. Will fix the default option.

Just flash it in recovery, that's all.
[G2 Original Android Development] IT Tech:
I seem to remember just flashing (been doing that for years) and not have luck / good performance when doing that with the 17's & 18's. I've done so much testing and troubleshooting that all scenario's might be running on top of each other o_O. I'll keep an eye on in the future. ;)
[G2 Original Android Development] aleasto:
New builds out

LineageOS 18.1 - Android 11 QPR1

These builds are targeting Android Go, for better memory management on a 2G phone as suggested by Google starting from Android 11
[G2 Original Android Development] aleasto:
Oh, and @IT Tech check if the default network option works now
[G2 Original Android Development] theelderstatesman:
@aleasto: In the thread, it still mentions " LineageOS 18.0 is a free, (...)", while it should be 18.1, isn't it? ...
[G2 Original Android Development] theelderstatesman:
@aleasto: In the changelog, where it mentions: "This now and Android Go phone:", I suppose, it should be "This is now an Android Go phone:"
[G2 Original Android Development] theelderstatesman:
@aleasto: So, Android (Go edition) - you must have had your reasons and, of course, you know much more than me, but - for now - I'm not too happy with it. I've got two of my major apps crashing, being one of them Outlook and the other one is Better Alarm. Most of the widgets are gone - I know ("only includes 4x4 grid") - in terms of my layout (the clock widget 3x2 and the weather widget 4x1 are gone), it's a setback. I had to go back to lineage-18.0-20201130-UNOFFICIAL-d802.zip, which was just perfect for me (without any bugs, I would have noticed) ...
[G2 Original Android Development] aleasto:
Have you tried if you have the same issues with a clean flash?
[G2 Original Android Development] theelderstatesman:
Ok, I'll try that and will tell you soon ...
[G2 Original Android Development] theelderstatesman:
With a clean flash, Android Setup is constantly crashing ...
[G2 Original Android Development] aleasto:
Ok, I've replaced the builds to only include the memory optimizations without touching apps. Let me know how that goes.
[G2 Original Android Development] theelderstatesman:
The result was like this:

1) Dirty flash (wipe everything except internal storage, install rom, install BiTGApps, install Magisk Canary and restore data backup) is working so far (no immediate crashes) ...

2) Clean flash: Android Setup keeps crashing ...
[G2 Original Android Development] agrumpyone:
@theelderstatesman :

Please, let me clarify your dirty flash precodure steps:

* wipe everything : these means you remove System, Cache and Data! - at this step you have actually the same state as doing a clean flash

* you flash BITGapps, Magisk and at least reinstall your previously wiped data back again

wiping your data and reinstall it again seems a bit redunant to me BUT it makes a difference - very surprising
[G2 Original Android Development] theelderstatesman:
Maybe, I didn't explain it too well. First (and before I start to install/flash anything), I do a backup of my data partition (in my case, 3,8GB with 35 apps installed). Then, I wipe everything except internal storage. Then, I start flashing (Rom, BiTGApps and Magisk) - that means, I got a brandnew data partition created by the installing/flashing process (as you say - like a clean install/flash). This partition is then deleted/wiped again restoring my backup data partition. To me, this makes sense, because I don't have to configure anything, i.e. if it goes well. Did you try the new rom with a dirty or clean install/flash?
[G2 Original Android Development] agrumpyone:
Unfortunately, not yet, because I use the phone every day. I would like to wait a bit until most of the problems are fixed. Or would you say it's stable enough for daily usage?
[G2 Original Android Development] theelderstatesman:
I can understand you - I also use it daily and, therefore, it's good to be cautious. As you can see by the posts between @aleasto and me, the original rom of 13.12.2020 has been replaced. In this moment, I'm not sure, if it's as stable as the one from 30.11.2020, which I'm on, because I only tried it for a very short time. It seemed to be a bit laggy ...
[G2 Original Android Development] theelderstatesman:
I just did a clean install of lineage-18.1-20201213-UNOFFICIAL-d802.zip without any problems ... In my opinion, the crash of Android Setup was caused by the setup-config.prop file of the BiTGApps-arm-11.0.0-R19_signed.zip that I placed in the root directory of the internal storage. After I deleted it (and did a new, clean install), the problem/the crashes was/were gone ...
[G2 Original Android Development] RobertoN90:
Do you notice relevant differences in RAM management? Is It laggy? Thanks in advance.
[G2 Original Android Development] theelderstatesman:
I'm sorry, I said that it seemed laggy (@agrumpyone), BUT IT'S NOT ... It's normal. For the time being (you have to see that I'm only using it for a very short time), I didn't notice any difference ...

@aleasto: Advanced restart is missing ...
[G2 Original Android Development] agrumpyone:
Thanks (y) So i will give it a try, as soon as the bitgapps site is online again.
[G2 Original Android Development] theelderstatesman:
BiTGApps has a new site it seems: BiTGApps
[G2 Original Android Development] theelderstatesman:
@aleasto: I know that this has nothing to do with you, but I just wanted to tell you that I can't install Magisk on the new rom ... @agrumpyone: Watch out, there might be a problem. On the other hand, if you suceed doing it, pls., tell me how you did it ...
[G2 Original Android Development] agrumpyone:
But it seems that the download is currently offline. Thanks anyway.
[G2 Original Android Development] theelderstatesman:
BiTGApps-arm-11.0.0-R19_signed.zip

drive.google.com
[G2 Original Android Development] theelderstatesman:
@aleasto: In fact, Magisk status says N/A (so, not applicable), which leads me to the conclusion that Android (Go Edition) is not compatible with Magisk (or any other rooting). Is it not possible to do two versions of the rom, one with and another one without Android (Go Edition) for those who need root?
[G2 Original Android Development] theelderstatesman:
@aleasto: You didn't answer, so - maybe - my conclusion was wrong and the problem Magisk has, is with Android 11 QPR1, because with the version lineage-18.0-20201130-UNOFFICIAL-d802.zip it (Magisk) works. In this case, there should be a solution sooner or later and I'll just have to wait ...
[G2 Original Android Development] IT Tech:
Currently Successfully Using:

LG G2 VS980

lineage-18.0-20201130-UNOFFICIAL-vs980

BiTGApps-arm-11.0.0-R19_signed

TWRP 3.3.1

Magisk 21.1 (21100)

Magisk Manager 8.0.3 (314)(14)

Does Not Pass Safteynet

OK @aleasto here is the scenario trying to flash the 18.1-20201213 ROM:

Trying to flash lineage-18.1-20201213-UNOFFICIAL-vs980

You and I were discussing "flashing the ROM as an update" as opposed to wiping anything or everything. As I stated, I came across problems starting with the 17 ROMs and continuing with the 18's and that is why I do not just flash a ROM on top of another in recovery because that has not worked for me for about a year or more. I would have all kinds of issues. I usually backup apps & data with Titanium Backup, wipe everything except for Internal storage and flash each new rom release, Gapps / BitGapps and Magisk.

Just thinking back to the first couple 18's and now the 18.1-20201213, I flashed them as you suggested by simply flashing it over the existing ROM. By doing so the ROM's would not boot. I would get stuck at a continuous scrolling lineage logo. Oddly enough after just flashing the new rom as an update (as you suggested) when it would get stuck I would power down, boot into recovery, flash BitGapps. Bingo! The ROMs would now boot but had many performance issues.

So with the 18.1-20201213 ROM I had the same circumstance. Once I was able to fully boot the rom it has bad performance and is pretty much unusable. GUI Freezes, apps run very poorly and crash, cannot access SETTINGS (blank screen & not responding), messages stops / crashes.

Also you wanted me to check the default network setting. I cannot check that because as I mentioned I cannot get into SETTINGS. When I first boot, Airplane mode was ON by default and NO LTE (states: Emergency Calls Only).

Since the 17's, TWRP image restore does not work. As you can imagine without being able to flash each new rom as an update it takes a ton of work to do everything from a clean install even with Titanium Backup (I currently run about 74 apps). So when the 18.1-20201213 did not work and the other ROMS do not work I have to wipe everything (except internal storage) and start from scratch.

o_O :( 🙃
[G2 Original Android Development] theelderstatesman:
Two questions:

1) Which version of lineage-18.1-20201213-UNOFFICIAL-d802.zip did you use, the first one or the second one? If you don't know which one, tell us the day / date (13/14 of December) you downloaded it ...

2) Did you use BiTGApps-arm-11.0.0-R19_signed.zip with or without setup-config.prop?
[G2 Original Android Development] rodken:
Have you successfully acquired Call, Text and Data with TWRP 3.3.1?
[G2 Original Android Development] IT Tech:
1) Not using the d802.zip, I have the VS980. Downloaded the BitGapps on 12-15 after @aleasto "replaced the builds to only include the memory optimizations without touching apps". I did have issues trying to download from GoogleDrive on 12-15 (drive limit exceeded message) so I went to another site and used a "backdoor" link. Maybe it wasn't aleasto's latest build, not sure.

2) I am currently successfully running: lineage-18.0-20201130-UNOFFICIAL-vs980 with BiTGApps-arm-11.0.0-R19_signed (downloaded 11-23 because as you know Gapps were not available) and trying to flash the 1213 ROM and @aleasto suggested to me to simply flash any new ROM in recovery as an update to the current ROM but as I mentioned in previous posts I have not had good luck doing a dirty flash even with the Gapps packages. I was not aware of the "setup-config.prop" until you mentioned it.

I was not aware of the instructions below. I have been doing clean flashes for a while so this would have not applied to me. I was even doing clean flashes using the Gapps packages with the 17 ROMs.

BitGapps mentions:

BiTGApps R19 And Before

• You have to keep BiTGApps zip and Config files in same directory.

• Need to flash BiTGApps zip after dirty flashing ROM.

• Need to flash BiTGApps Addon zip after dirty flashing ROM.
[G2 Original Android Development] theelderstatesman:
I know that you have a V980. I made a mistake. I'm sorry.

Where setup-config.prop is concerned and as I stated before, I suggest not using it, because it got me in trouble (see my earlier posts).

I'm only using BiTGApps, because there's no OpenGApps for Android R yet.

For the D802 there were two versions from the 13th and 14th of December. I don't know, if that is also true for the V980, but I suppose so. It's easy to distinguish the two versions, because the first one only accepts 4x4 widgets and the second one doesn't ...
[G2 Original Android Development] IT Tech:
Yes. And as I mentioned in a previous post for the VS980 ROM in the US the phone and messages app did not work because the ROM's default "Preferred network type" is set to GSM/WCDMA/LTE

You will receive "Waiting for Connection" when trying to send a text and LTE would appear to be working from signal strength but I could not make or receive calls. I had to switch the "Preferred network type" to GLOBAL. This was present with the Android 10 Lineage 17 & 17.1 ROMS as well.

@aleasto asked me to try setting the "Preferred network type" to LTE/CDMA/EvDo/GSM/WCDMA. I could not find that as an option. The option that was available close to what @aleasto suggested was LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA. I used this setting and the phone, data and messages work on this setting.

How to change the Preferred network type:

Settings > Network & Internet > Mobile Network (Verizon) > Preferred network type and change the default GSM/WCDMA/LTE to LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA
[G2 Original Android Development] IT Tech:
No problem. Just thought I would mention it so others would not get confused
[G2 Original Android Development] aleasto:
@IT Tech

I got lost.

Dirty flash issue was caused by bad gapps integration. Opengapps would work fine, though I understand there's no arm gapps yet (and arm64 opengapps-testing is very broken anyways)

Did my patch to the default preferred network work? Or you couldn't test because of other issues with the latest build?
[G2 Original Android Development] aleasto:
Shouldn't have to do with go... But neither with qpr1 so idk

Looks like we're going back to non-go builds anyways :confused:
[G2 Original Android Development] IT Tech:
@aleasto

1) See my post #82 above

2) My phone / call speaker (ear speaker) has very, very low volume since using the 1130 ROM. The external speaker works fine.

Older ROMs had a mixer_paths.xml that you could edit to increase speaker levels? From my research it seems as though In Android 11 or higher, the version of the audio policy engine is selected in the audio_policy_configuration.xml file ?

By the way, you mentioned you got lost. Where did you get lost ? :D

@theelderstatesman Regarding the problem with not being able to restore an image in TWRP. According to your post I assume you tried this? : Steps to restore image in TWRP by @m0han
[G2 Original Android Development] theelderstatesman:
Believe me, ever since @m0han taught me this trick, that's the only way I do it (and I already did it many, many times) and it's always successful - unless there's a problem with the rom itsself ...
[G2 Original Android Development] aleasto:
Please consider the included Seedvault for backup/restore.
[G2 Original Android Development] qwertycutie:
Do you think this will work on the lg g2 l22 variant? i kinda wanna take pre-cautions first.
[G2 Original Android Development] wally_ctba:
Hello guys, I'm very pleasent with this Rom. Actually it was the first time I root my D805. I did the clean flash, Install the 20201213 D802 version and the BitGapps R7. Thanks of these instrucions and some youtube videos I did it Right!

The first day the battery warm up and had to recharged some times, but after that returned to normal (almost 1 day long with a 6 year battery is very good).

The only thing is some apps still have bugs. Google Drive, Telecine crashs... And I miss very much the original Universe Remote Control, FM Radio, Widget Ram cleaner...
[G2 Original Android Development] RobertoN90:
Hi. What's your feeling after 10 days of use?
[G2 Original Android Development] theelderstatesman:
I'm using lineage-18.0-20201130-UNOFFICIAL-d802.zip for more than 4 weeks now and I have no problem whatsoever ...
[G2 Original Android Development] RobertoN90:
Is the Android Go release? What about performance (free RAM, lags etc.)?
[G2 Original Android Development] theelderstatesman:
No, that's the release before the go one. As far as I can tell, it has enough free RAM, no lags and the performance is good (fluent) and stable ...
[G2 Original Android Development] theelderstatesman:
In the developer options, it says that it has an average usage of 1,0GB of a total of 1,9GB RAM ...
[G2 Original Android Development] aleasto:
New builds out

Back to non-go

Updated LineageOS frameworks and apps
[G2 Original Android Development] wally_ctba:
Hello, Actually more than 2 weeks. In average felling pretty good.

But last week it seems that increase the freeze times...

As I changed to gestures instead of the 3 buttons menu, I have to wait some seconds to came back to first screem. With 3 buttons menu, the central button goes to first screem fast and gives you the option of shutdown the app that freezes/crash.

Actually the app with more freezes is Duolingo. The only diference is that it doesn't crashs, after the come back of freeze it appears the screem of Close/Wait/Report and all the times it's just click wait that the app still working.

The RAM uses it has been pretty good. Most of time with 700 to 800mb of free Ram.

I've installed the One Touch RAM Cleaner, but I almost never needs to clean.
[G2 Original Android Development] Sankeshwar:
Here is a Good Tutorial for the ROM Installation
[G2 Original Android Development] LGElectronics:
Work - on LG D802.

Problem - holy lags when using Wi-Fi and for example extensions for playing live music.

Interface sometimes down with Bitapps and work fine with Nikapps.

So recommend last. Anyway work not stable. But cool in all. Waiting for official release and fixing bugs.

:cowboy:
[G2 Original Android Development] theelderstatesman:
Maybe, you should check your hardware. I'm on the latest build and I have no problem whatsoever ...
[G2 Original Android Development] LGElectronics:
All work fine with android 9, linageos 16. d802
[G2 Original Android Development] theelderstatesman:
That's no argument. On Monday, the 4th of January (this year), my phone broke literally from one second to the other after a daily run for over seven years and first I also thought it's the rom, but it isn't - it is a hardware issue. The screen is flickering from time to time - like shaking or trembling, but it also happens in the recovery mode and the LG logo has a stripe below full of little coloured spots. I'll try to have it fixed, but this might take a long time. In the meantime, I have a second one ...
[G2 Original Android Development] BigEddyson:
At me too build 11 works unstable. Especially SystemUI. Despite the fact that I do not use GAPPS.

Also, for now, I switched to the lates ROM of Android 9 AOSP. Works good. D802.
[G2 Original Android Development] LGElectronics:
Installed Android 11 & LineageOS 18.1 - tested lags after go back to Android 9 and it's work stable as already posted in last post. Android 10 ( 17.1 ) for d802 is still in nightly builds and not stable.
[G2 Original Android Development] LGElectronics:
To wait stable release.