yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] Rosenrotx3:
no matter what i do, i can't install stock gapps. Every time i try to install stock gapps, i get error 70. I tried to resize my system partition, that also not worked. Any solutions? I don't want to stick with pico gapps. Stock is more suitable for me.
[G3 Android Development] Sobhan Mazaheri:
Mr HardStyl3r

Why not install Google MindTheGapps 11.0.0 arm 20210412 - lineage-18.1-20210424-nightly-d855?
[G3 Android Development] HardStyl3r:
MindTheGapps don't really work with out device. Stick to the OpenGApps.
[G3 Android Development] Alein_:
Is there ROM for D858hk g3ds? ? I am not able to find it for v17 and 18.1.
[G3 Android Development] Alein_:
Is there ROM for D858hk g3ds? I am not able to find v17 or v18?
[G3 Android Development] HardStyl3r:
Dualsim variant is no longer supported.
[G3 Android Development] Af0x:
After upgrading to lineage-18.1-20210501-nightly on an encrypted d855-device (lineage-17.1-20210410-nightly) I can´t unlock the screen although the entered password is correct. It keeps asking for the password.

Is it even possible to dirty upgrade like this? I used twrp-3.5.2_9-0.
[G3 Android Development] alliance1975:
Please appreciate the fact that I'm and idiot. I wiped all the usual suspects except data. I installed the 4/16 - 18.1 rom along with Open Gapps. It worked to perfection, except for terminal.

4/23 and 4/30 OTA updates installed via Settings, System, Advanced, Updater. Just like the old days.

I use HardStyler's TWRP 3.3.0-0
[G3 Android Development] Alein_:
Hi, thank you for this information, actually I do not understand why the best variant is not supported, but anyway, do you know which is the most valuable ROM for dual sim?
[G3 Android Development] HardStyl3r:
The answer is simple, I don't have g3ds variant and it wasn't me who brought it up in the first place. There are very few g3ds users that it's really hard to debug. It also wouldn't make it to LineageOS official.

And to answer the question, stock rom is probably the best.
[G3 Android Development] Af0x:
@HardStyl3r can you confirm this? Currently my device is bricked because of this.
[G3 Android Development] HardStyl3r:
As far as I know, due to switch from Hardware encryption to software (keystore -> gatekeeper) /data should be wiped before upgrading.
[G3 Android Development] Ph3ar.:
I would think trying to upgrade from one android version to another dirty flashing an encrypted device is like playing with fire. I wouldn't call it a bricked device if your willing to clean wipe it and install the new version the proper way. You still have twrp recovery right ?
[G3 Android Development] HardStyl3r:
In the past, encrypted OTA upgrade was fine. Now, we couldn't HW encryption and there's special flag "wipe_on_update" or something like that in lineage_wiki. I highly doubt that it has no meaning.
[G3 Android Development] Af0x:
Is there any known bug regarding WPA3? Because I can´t establish a connection with my d855 device (lineage-18.1-20210501-nightly). WPA2 is working though.

Also knock knock functionality is not working.
[G3 Android Development] HardStyl3r:
g3-common: wifi: Disable WPA2 -> WPA3 upgrade. · LineageOS/android_device_lge_g3-common@7a9328b

Our device doesn't simply support sae. Change-Id: Ibf8b9e363b4677cf2ab9590cc2ea1ba2341e29ca

github.com

You have to enable DoubleTap2Wake in Settings > Display.
[G3 Android Development] fubag:
ugh I accidently lost my twrp recovery to the lineageos recovery and lost root...can someone link me to to the twrp zip file mentioned that I could flash using the lineageos recovery?

*edit - i found the zip and i got twrp back! also figured out how to flash magisk again!!! yay!!!!!!!!!!!!!
[G3 Android Development] petergunn666:
Plugged my d851 into a monitor via a slimport adapter and the phone display started to flash like crazy then the phone hung until I removed the battery. Anyone got this working with LineageOS 18.1 ?
[G3 Android Development] macoloco:
Thank you @HardStyl3r ...

I have 2 G3 used as secondary phone...mainly to listen podcast. I've been stuck on Pie, due i was not able to make lineageOS 17.1 run on these devices.

Yesterday i decide to try with 18.1....Backup 16 rom first....Wipe data+cache+dalvik (everything)

Just flashed through TwRP latest build and beta GaPPS..Just worked great.

I just struggled a bit trying to make Viper4FX working propperly....now it does

When I finished setting up my device i have discovered that RadioFM is not working

First boot shows nothing....sometimes it shows a random dial number, but no sound

Is there any chance to get RadioFM in this rom working?

I know its an oldschool problem....but mainly i use this phone as media player on my job time.

Thanks for all effort
[G3 Android Development] Ph3ar.:
What variant

RadioFM from the playstore is working fine here on my G3 . What variant G3 are you on ?
[G3 Android Development] macoloco:
Lg G3 d855...intl variant unlocked

Radiofm in playstore?

Never heard about it
[G3 Android Development] macoloco:
I refer to radioFM not streaming through 4g...fm tuner based app
[G3 Android Development] macoloco:
search on forum...found this fix

https://xdaforums.com/t/rom-5-1-1-cancro-unofficial-resurrection-remix-lp.3056711/post-62076919

fm radio is working now....dont know what was wrong before....
[G3 Android Development] macoloco:
it was just a moment working....today fmradio apk is not working....something is broken, i am trying to guess what
[G3 Android Development] Zirila:
I have some issues with Lineageos 18.1 w/ microG, but I think it's all rather Android 11 dependend:

- My radio app ("simple radio") is always stopping after 5min idle in standby

I switched off "save battery" for this app, so it shouldn't stop but it does.

In earlier LineageOS versions <=v17 I had the option "keep Wi-Fi connected in standby" in the advanced wifi options. This setting is now completely missing. Maybe it's the wifi that stops working after 5mins in standby.

But I can't do anything to fix it.. the option has been removed, what to do now?

- is there a way for older apps that don't get any updates soon to enable external sdcard read/write access?

Android 11 forced "scoped storage" and apps have no permissions to use the storage as before. I tried magisk/edexposed modules like "exSDcard Access enabler" and the like which worked for v17.1, but they won't work for v18.1.
[G3 Android Development] macoloco:
Starting out of zero....new install.

Wipe cache+dalvik+data+system....flashing latest nightly and test gapps zip.....

First boot....radio is working but now lineageos seems a bit laggy....

i think magisk or a module maybe broke radio app .....trying to guess now
[G3 Android Development] macoloco:
Definitely Magisk breaks radio app function at some point.....

Trying older Magisk versions....

Magisk 21.4 doesnt want to install

Magisk 22.0 app and zip are installed and radio working properly ...so far

Upgrading app to 22.1.....radio still working
[G3 Android Development] macoloco:
Fault is located....

After upgrading Magisk ( zip) to 22.1 version....RadioFM app doesnt boot.....something is broken there...

Edit: Close to make FmRadio working....waiting some final test

Final result...nothing.

Radio app stop working randomly with magisk 22.1 or some combination 22.0+22.1 - 22.1+23.0

Magisk hide seemed to work with radio app and magisk 22.1 after upgrading to 23.0 stop working, trying to revert to 22.1 and sometimes freeze radio app, sometimes seemed to work....a bit mess

i will stay on 18.1 lineageOs without magisk (i need viper4FX or something like this to improve speaker to listen podcast while driving) (i cant use earphone due my job and is the only way to listen music )
[G3 Android Development] rahimali:
Just a thought... add bluetooth speakers to car or connect phone to car audio system via bluetooth...
[G3 Android Development] macoloco:
i am not driving a car...i drive a tram and its not 100% legal use headphones or speakers inside......i use my G3 at work as a media player
[G3 Android Development] macoloco:
Finally i decided to revert my G3 to latest pie version.

i will wait to see if Android 10 gets updated and its possible to use radioFm and viperFX (magisk) together
[G3 Android Development] avf32:
Hi all,

I have an LG G3 (d855), it currently has TWRP recovery installed on it and everything else has been wiped.

I've tried to install LineageOS (tried both v17 and v18) by sideloading via TWRP, but I never managed to get anything to boot -- I just get the LG logo for a while, and then it either boots into TWRP or into Fastboot.

I have no idea what else to try. I really wish I could get some error messages out of it instead of just the LG logo -- is there a way to do this? I couldn't see any log files being left behind.

Any suggestions welcome.

Thanks,

Alex
[G3 Android Development] Ph3ar.:
So when you go to twrp are you just flashing the zip file from the device or sideloading it some other way ? Have you tried just flashing the rom with no gapps to see if it will boot ? Are you flashing anything else like magisk at the same time you flash the rom ? Also what version twrp ?
[G3 Android Development] Saksham03:
Hello, can anyone tell if I can flash GSI on D855?
[G3 Android Development] avf32:
I've tried sideloading, I've tried pushing to /sdcard and installing from there, I've tried copying to an actual SD card and installing from there. The result is the same each time: it doesn't boot. Latest version of TWRP (3.5.2), flashing just the OS image, nothing else.

But I've decided to give up with this phone, I've had enough of bashing my head against it.
[G3 Android Development] rahimali:
AFAIK, there's no treble support/ROM available for the LG G3 (no idea why), so no.
[G3 Android Development] Zirila:
I'm still struggling with WiFi and standby.

With LineageOS v18.1 I'll always lose Wifi after a few minutes the screen turned off. I'll get no messenger notifications, internet radio apps stop working, whatsapp desktop loses connection to the phone after a while, and whatever needs an internet connection gets interrupted.

This used to work in LineageOS 17.1.

in 17.1 there was also the option "keep Wi-Fi on during sleep" in the advanced wifi settings. This option is now missing.

however adb shell settings get global wifi_sleep_policy is returning "2"

this means "always on". obviously this setting doesnt change anything related to the problem.

I also made sure there is no battery saving involved with the used apps.

anybody with similar experience?
[G3 Android Development] Ph3ar.:
Sorry to hear it's been giving you a frustrating time. Would you be willing to give 16 a try just to see if it would boot? 17 did have some early issue with rebooting to recovery. I use the LS990 so I can't help much but I do know v16 ran and booted like a charm. If you tried 16 and had the same problem I would think something is just stuffed up with your device . if it booted then that would offer hope. have you tried installing clean rom one time ? Sometimes erroneous factors can have a device stuffed up so to speak. Did you come straight from stock or were you running 16 in the past ?
[G3 Android Development] avf32:
Trying 16 was suggested to me before, but I couldn't find anywhere to download it.

It didn't run any custom ROMs in the past, as far as I'm aware. When I got it, it was running stock Android 4, although it was rooted. I upgraded it to Android 6 (via 5) using LG Mobile Support, but then I couldn't find a way of rooting that version or unlocking the bootloader, so I reflashed version 4 using LG Flash Tool and went from there.

I'd love to understand more about how the previous Android version might affect installing a custom ROM. From my naive x86 PC point of view, if it's not on the disk, then it doesn't matter, so I'm struggling to understand how it makes a difference. Does a later version of Android update firmware in the hardware, or something, which isn't visible by examining the partitions? Or do not all partitions get overwritten when installing a custom ROM? I did notice that I couldn't even get TWRP to work when I first got the device, and it only started working when I went through the 4->5->6->4 cycle.

Another thing that came up is partitions. It seems that newer phones have A and B partitions, system_a/system_b, recovery_a/recovery_b, etc. My phone only has system, recovery, boot, etc. Also, something about a "super" partition in Android 10 has been mentioned. Might this be the cause of my issues, and if so, do I need to run a script or something to repartition the flash before installing a custom ROM? I'm surprised that I couldn't find much information about this point out there.

Thanks!
[G3 Android Development] Ph3ar.:
Rather than go through all of that I would go back to the basics . Maybe start from a clean installation of Android L or M. Then start with 16 . I would root and install an older version of twrp like 2.8 . Then before you attempt anything else make yourself a good nandroid of your stock rom . That way if something goes wrong you can keep restoring that stock rom and have a firm base to return to without having to go through re-rooting and re-installing twrp. . Once you've got that done then maybe someone here will post a link to 16 for you. 17 and both 18 have been a bit contrary with more bugs than 16 had. I think if you can just get 16 working good then try the upgrade path from there to 17 or 18. You won't have to worry about partitions at that point. Hopefully some of the people with your variant will step up with a little advice . The path I'm pointing you on is a solid one but it gets you back to a good point of having the phone at stock , then getting a TWRP from the times on it, then rooting , getting a good nandroid established and going from there. Don't jump ahead with TWRP or the latest Magisk versions until you have to. Version 2.8 to 3.0 of Twrp were nice and stable for 16. Magisk 20.4 was nice and stable as well. From my own experience there are some bugs interacting between the latest roms , magisk and twrp. I haven't been able to determine which of the 3 or even all 3 for that matter . Once you find out if 16 works then make another good nandroid at that point. protect that step before you try anything else . That will give you another toe hold to fall back to. We'll try to help you out. Seeing the bugs and problems with the latest rom, magisk and twrp makes me think you picked a bad time to go from stock to 17 or 18. Focus on 16 for now. Someone please post the man a link to the last v16 lineage build for his variant. . Lets help this fella out.
[G3 Android Development] rahimali:
@avf32, I have a large collection of ROMs (but only for D852 and D855). If your variant is one of those, let me know what you need, I'll do my best to help out.
[G3 Android Development] LZ_:
Which TWRP you run?
[G3 Android Development] williamvds:
I've installed (microG) Lineage 18.1, built 7th of May 2021, clean upgrade from an encrypted microG 17.1. It appears to be mostly working:

- I got a decryption prompt on first start up, I assume because internal storage wasn't wiped

- Rotation works but the compass is still broken as it was in 17.1 (tested with "Compass" by Phillip Bobek from FDroid)

- GPS sometimes works, maybe takes a while to get a fix, just as in 17.1 (tested with "GPSTest" by barbeauDev from FDroid)

- Bluetooth doesn't start up

Would the compass and GPS issues be resolved by restoring the original Lollipop firmware? Should I bother going through all that process?

Digging into the logcat I can see an obvious reason for Bluetooth failing:

05-22 12:52:58.426 12712 12740 E droid.bluetoot: [0522/125258.426453:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
05-22 12:52:58.426 12712 12740 E droid.bluetoot: [0522/125258.426634:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
05-22 12:52:58.426 12712 12740 E bt_btif_config_transcode: btif_config_transcode unable to load XML file '/data/misc/bluedroid/bt_config.xml': 3
05-22 12:52:58.426 12712 12740 E bt_btif_config: init unable to transcode legacy file; creating empty config.
05-22 12:52:58.434 12712 12745 E bt_btif_storage: btif_storage_get_adapter_property: Controller not ready! Unable to return Bluetooth Address
05-22 12:52:58.434 12712 12745 E BluetoothServiceJni: adapter_properties_callback: Status 1 is incorrect
05-22 12:52:59.674 3772 3969 E BluetoothManagerService: MESSAGE_BLUETOOTH_SERVICE_DISCONNECTED(1)
05-22 12:53:01.027 12785 12807 E droid.bluetoot: [0522/125301.027485:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
05-22 12:53:01.027 12785 12807 E droid.bluetoot: [0522/125301.027717:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
05-22 12:53:01.027 12785 12807 E bt_btif_config_transcode: btif_config_transcode unable to load XML file '/data/misc/bluedroid/bt_config.xml': 3
05-22 12:53:01.028 12785 12807 E bt_btif_config: init unable to transcode legacy file; creating empty config.
05-22 12:53:01.035 12785 12812 E bt_btif_storage: btif_storage_get_adapter_property: Controller not ready! Unable to return Bluetooth Address
05-22 12:53:01.035 12785 12812 E BluetoothServiceJni: adapter_properties_callback: Status 1 is incorrect

This might just be a bad build missing the bluetooth config. Could someone send me the stock /data/misc/bluedroid/bt_config.conf? I didn't have much luck searching the LineageOS repositories.

I was having the same issue after reverting back to 17.1, indicating this was an issue with the data partition. Same problem after wiping the "internal storage" in TWRP and reinstalling. Getting the decryption prompts after wiping was suspicious, so I flashed the latest LineageOS recovery and did a clean install. Bluetooth is now working normally.
[G3 Android Development] Zirila:
Regarding the WiFi Issues:

it seems like the issue is related to an issue with Anrdoid 11 and RFC 5006 setting in FritzBox Routers. I managed to fix this issue with a workaround I found here:

https://support.google.com/pixelpho...nden-die-wlan-verbindung?hl=de&msgid=72989707

After that, I had none of the mentioned WiFi issues anymore. luckily.

But the more interesting question is: Why is this setting (RFC 5006) in the router NOW a problem with Lineage18.1/Android11 when it wasn't a problem before with LOS17.1/Android10?

Shouldn't the fix be on LineageOS / Androids side instead of disabling a router DNSv6 setting that is common in millions of devices?
[G3 Android Development] Zirila:
The default camera app "Kamera" doesn't work when trying to record a video. it says:

"Could not start media recorder. Can't start video recording"

tried wiping all data of the app, resetting all permissions, still not working. any fixes?
[G3 Android Development] fubag:
anyone having issues flashing the latest builds on LineageOS using TWRP that is resulting in super long starting animation boot, that eventually reboot the phone back into the TWRP recovery? I have a D850 for reference

I was fine on the May 14th build but trying 5/28 and 6/4 is resulting in issues now...tried wiping cache/dalvik and no beuno for reboots :'(
[G3 Android Development] fubag:
New issues with latest builds 06-11 on D850...using custom TWRP provided by HardStyl3r; cannot install MindtheGapps 11.0 build for arm...throws up mount system error 1 everytime...any luck for anyone else? I've tried wiping and starting again, no luck
[G3 Android Development] Jason_angg:
How to fix slow charging? Already tried different chargers and cables
[G3 Android Development] hellenicboy:
Hello all,

I have a d850 rooted. I am coming from android 9 and magisk installed. I installed lineage 18.1 couple months ago and everything is running smooth but phone now shows as not rooted and can't install magisk.

Any thoughts?

Thank you
[G3 Android Development] hourwatch:
EDITED

I have installed this ROM, but it doesn't recognize my SIM. In Lineage 16 worked perfectly, and I have tried another smartphone and works correctly. Any way to fix this?
[G3 Android Development] hourwatch:
It looks like is a problem for the hardware. I have solved putting a paper above the SIM
[G3 Android Development] Nexus-3:
Greetings,

first let met congratulate and thank @HardStyl3r & all the other LineageOS developers for breathing new life into such an old but venerable device!

After OpenGapps finally released packages for Android v11, I attempted to upgrade my LineageOS from v17.1 to v18.1 with little success so far.

My D855 always ends in a login loop, meaning that the arc animation finishes (with the three circles) and the SIM card unlock screen appears BUT 4 seconds later the complete arc reappears and then shows the sim unlock screen again.

Spoiler content hidden.

Comments, hints & suggestions are appreciated.
[G3 Android Development] HardStyl3r:
18.1 update must always be performed the clean way, which means /data has to be wiped. Otherwise, the "security things" won't work.
[G3 Android Development] Fractux:
EDITED POST : Trying a few more things before wasting people's time.

Sorry!
[G3 Android Development] kmambu:
Hi everyone,

First of all, thank you @HardStyl3r for the Custom ROM, it installed without any issues 😁

The phone is running OK overall but feels laggy at times, would anyone know how to improve the performance of my installation ?

I reduced the resolution through LineageOS settings and it helped a lot, bu it seems like the kernel installed by default s a little bit restrictive regarding CPU frequency 🤔
[G3 Android Development] Ph3ar.:
Pretty much running perfect on the LS990. Loses root after update but not a biggy. Magisk runs it's script after the flash but doesn't stick for some reason but easy enough to reflash magisk and then install the v.23 apk and back in business.

Thaniks @HardStyl3r for keeping us going. Great job bud.
[G3 Android Development] Ph3ar.:
Do you still need help or did you figure it out ?
[G3 Android Development] Fractux:
Haven't gotten anywhere with it, sadly.

I made a full post in the Help section, but no replies yet.

[ https://xdaforums.com/t/lg-g3-d852g...age-primary-block-device-not-present.4309545/ ]

The only thread I found was dealing with this issue on a Nexus 7 : [ https://xdaforums.com/t/update-mounting-errors-in-custom-recovery.3064562/page-7 ] and mentioned TWRP issues that were resolved in 3.0.0 in that thread.

But the errors I get are using TWRP 3.3.1, from here [ https://xdaforums.com/t/recovery-3-3-1-abandoned-twrp-for-lg-g3.3813552/ ]. And every other build I've tried so far. And lineage recovery.

I'm not sure what to do next.

Thanks for inquiring, any help would be more than welcome.

Cheers!
[G3 Android Development] HardStyl3r:
@Fractux you've probably lost your data anyway, so recreate the partitions in TWRP. Also, the TWRP I've built is not supported anymore.

To recreate the partitions, enter the partition settings and reformat it. I've done it by formatting /data to f2fs and then back to ext4 but it's very newbie way to do it. I don't really remember the exact steps and I am in France for vacation, so no screenshots.
[G3 Android Development] Fractux:
@HardStyl3r,

Thanks for the reply, especially on your vacation.

I have already tried that you mentioned, with several installs and several versions of TWRP, but all had the same issue.

It cannot even see the block device, so it can't mount it to run a format.

All the data is still there. I can boot back into the stock ROM and everything is as is, it's literally just TWRP that can't see the storage device.

In every video I saw, when Present was YES, the formatting worked. No version I've tried so far has allowed me to get that NO to switch to YES.

Any other suggestions that you have? I'm stuck scratching my head.

Thanks again for replying on your vacation, much appreciated!
[G3 Android Development] HardStyl3r:
Have you tried the original 2.8 TWRP that comes with AutoRec? I doubt it will help but it's worth a try.