Database Info

Google Assistant Voice Match

Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.

I have thé same trouble sincères thé Google voice match was updated

Same issue for me, in Italian language.

With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?

Homestar1217 said:
Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
Click to expand...
Click to collapse
It's currently the same on all roms, it's working if you use a gsi

Flatric said:
It's currently the same on all roms, it's working if you use a gsi
Click to expand...
Click to collapse
Good to know I'm not alone!

You are not alone! This happened to me a few weeks back. All my searching leads to gapps verification, or shall I say use of gapps instead of built into system. This feature does work once again using gsi with Google apps pre-installed as well as pixel exp ROM, as they are verified there.
Sent from my Mi MIX 2S using Tapatalk

Hi,
Same problem here in french language.
Voice Match used to work last week. Activation by pressing home is not working too.
I have to launch the app by clicking it

I have solved with last update MIUI Global 10.0.9.0

duraaraa said:
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Click to expand...
Click to collapse
I am still having this problem.

Same here, it stopped working about a week ago. Tried everything: retraining model, changing language from “English (Ireland)” to “English (United Kingdom)”… nothing works. I have to press the button to activate the assistant. I'm using the Pixel Experience ROM by Psy_Man – amazing ROM BTW, super stable.

Which version of the Google app do you use? I installed the 8.65.6.21.arm64, and Voice Match works on it.

I am experiencing the same issue ever since I flashed AEX. Pixel Experience was working fine and no issue with assistant but after the problem appeared all ROMs stopped working. I am currently on MIUI global because it's so far the only ROM that has it working, but it still requires faceunlock/fingerprint to unlock the phone though it does wake up by saying OK Google.
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.

jamesyuli said:
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
Click to expand...
Click to collapse
I tried out OctopusOS ROM GSI. Very stable, could be a daily. I used it for a few days. But I prefer to be able to use a true dark theme. Didn't have issues with Google hot words at all. A few tweaks and some magisk modules help it out.
https://forum.xda-developers.com/pr...led-device-development/9-0-octopusos-t3859233

I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havok.

Voice Match is working again in latest AOSIP

Flatric said:
Voice Match is working again in latest AOSIP
Click to expand...
Click to collapse
There's also a changelog entry for PE that hotword enrollment was fixed! More stuff to try!

Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk

noobtoob said:
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
almost 24 hours so far on the 12/30 build of Pixel Experience with no issues. The rom just runs flawlessly, and I love the pixel live wallpapers. OK Google still working with none of the voice options greyed out. Android wear device working too (Explorist 4). Auto bright, and lock/unlock good too. Battery seems good so far. These points aren't relevant, but everything else seems to work good.
I know Pixel experience is not very dense on details for install so here's my process.
Use MiFlash to flash fastboot version of latest developer rom
Re-flash TWRP, enter wipe menu and wipe (Not format, NOT the one you have to type y-e-s) the first four options, Dalvik, Cache, System, and Data.
Flash your rom
Boot! (Regardless of whether or not it makes a difference, I like to let it sit on the first screen for a little, and then after 2-5 mins, I'll restart, before setting it up)
Oh! And I've had less issues since I installed MIUI, went into settings, and Signed out of my Mi Account. Not sure if it makes a difference, but I no longer have to "authenticate" and unlock after I install MIUI. This confused me because I read that unlocking BL automatically disables find my phone, but evidently not.
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Gopena said:
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havoc.
Click to expand...
Click to collapse
1/3 Didn't post this yesterday, I tried Havoc as well and it behaved like miui, no OK Google to wake & Unlock, but ok google from lockscreen brought up the pin pad, and unlocking with pin or FP would allow google assistant to activate. Havoc also had no bluetooth audio.

Microphone not working...

My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??

i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse

LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.

since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.

I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.

toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...

I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.

Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem

LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?

I installed lineageos 16 without gapps and is working good for hours until installed gapps.

ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??

Netflix playback not working on Lineage OS

Hey all,
since I upgraded my tablet to Lineage OS, now 13 Netlfix is just not working.
I can find the app in the Play store and install it etc - that's not the issue ( the device is NOT rooted by the way)
The app will open and the video menus are available, but the issue is with actual video playback.
At best I can maybe get one whole episode of a series to play, but then (at the latest) by the next episode it will get a few minutes in and then it will slowly fade to black and cut back out to the Netflix home menus. Of course, I've tried closing the app, logging out and bag in, dumping app cache and even data, and restarting device but this makes no difference unfortunately.
Issue repeats and repeats no matter what I do.
I think this is an issue with Lineage and Netflix, or at least an issue with custom roms and Netflix.
By the way, even though the device was not rooted at time of having the issue, I tried to use Magisk and Magisk Manager to see if this could solve the problem, but it didn't work.
This is really annoying because tbh Netflix is probably the main thing I use my tablet for!
Anybody got any ideas? Would appreciate any advice!

i think there's some bugs in the rom. i'm using lineage os 17.1 rooted with magisk and my Netflix app works absolutely fine. and when i was using lineage os 16 it was working good no issue at all

ranjodhricky said:
i think there's some bugs in the rom. i'm using lineage os 17.1 rooted with magisk and my Netflix app works absolutely fine. and when i was using lineage os 16 it was working good no issue at all
Click to expand...
Click to collapse
Ah ok, good to know thanks. Unfortunately only Lineage 14 and not higher is available for my device
My tablet is a Samsung Galaxy Tab 2 10.1 (GT-P5110) - I know super old, but that was the reason for using a custom rom in the first place.
I deliberately didn't mention my device before because I still think the issue is more to do with Lineage, and not directly to do with my device.

LineageOS questions

Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?

Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!

nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.

Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.

shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers

AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.

is there a working build of lineage 18 for moto g8 plus?

hi, I have a moto g8 plus and I want to use Lineage but my devices isn't under the supported devices list. is there a working unoffical lineage build that is opensource for the moto g8 plus?
and if there is no build, how much work is it to port lineage to a new device and what knowledge is needed?
thx for your answers beforehand

I used @waltermobile's guide for 17.1 https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83094247
plus @AndyYan's 18.1 build: https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105

stormarrest said:
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105
Click to expand...
Click to collapse
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue? I'm thinking of installing it; i'm tired of waiting for a custom ROM. thanks.

gfrank227 said:
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue?
Click to expand...
Click to collapse
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.

stormarrest said:
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.
Click to expand...
Click to collapse
OK thanks for the info.
I attempted to install Lineage 19.2 on my moto g8 plus but it got stuck on the curved line and circle screen. i'm not even sure if I flashed it correctly; this is literally my first time trying to flash a whole GSI/Rom on any phone. Any advice or instructions would be appreciated (I used TWRP; after it was done flashing and I tried to restart it gave a warning that there was no OS; not sure how that's possible, and I still got that curved line screen). In short, I am not sure if it's the .img file I used or the flashing method, or perhaps even both.