yashsingh1/xdaforums huggingface dataset:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] tuppb:
Glad to hear that your installation went well!

Evidently, the LineageOS wiki installation guide for the Moto G7 is causing some phones to brick.

Some Moto G7s apparently are sensitive to which slot is active during certain steps of the install. The Lineage wiki instructions do not address this active slot issue, but the guide provided by XDA user _Clon_ does direct which slots should be active during certain steps.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] jman315:
The main things I have noticed with LOS 17 are the FM tuner and night light don't work.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Yes, I noticed those two issues. Not a big deal, as the rest works great. I have been using LOS 17.1 for a week on River and I don't have any complaints.

I recommend the upgrade if you run LOS 16.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] phatzilla:
Strange issue im having:

With magisk 20.4 flashed, my phone shuts down as soon as i unplug my cable (connected to PC), when i flash the backed-up boot.img, no such problem. What could be the cause of this?

edit: fixed by reinstall stock firmware and following clons steps

https://xdaforums.com/showpost.php?p=81872703&postcount=174
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] joemcool:
wifi in LOS

I'm running into an issue with wifi in LOS (works fine in stock)...

I followed the install instructions on the LOS wiki, and was able to install successfully. I joined my wifi as part of the setup process and had both good wifi access and LTE data. However, after a reboot the phone fails to connect to the wifi. Turning on verbose wifi logging shows NETWORK_SELECTION_DISABLED_ASSOCIATION_REJECTION for my wifi network. I've tried multiple wifi access points (Ubiquiti and TP-Link, and no other wifi clients seem to be having issues. The APs don't report any failed associations when the phone tries to join.

I found a thread on the Lenovo forums (https://forums.lenovo.com/t5/moto-g...G7-Power-wifi-connectivity-issues/m-p/4394079) that shows a lot of people are having issue with wifi on the G7 phones, however I don't see this issue when I'm running the stock ROM, only in LOS (I've tried both lineage-16.0-20200325-nightly-river-signed.zip and lineage-17.1-20200423-nightly-river-signed.zip), so I'm not sure if that applies to my situation or not. I've reverted to stock for now.

Is anyone else seeing these issues? Any ideas for a path forward? I can provide additional details upon request.

Also, I saw another thread for LOS here (https://xdaforums.com/moto-g7/development/official-lineageos-17-1-t4075907). Apologies if I should have posted there instead of here.

Thanks to the developers for all their work providing this ROM! Please let me know if I need to provide more info to help with debugging...
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gabo_lope:
Can confirm as well that _Clon_'s guide has worked to install Lineage coming from Stock. Only to note, that I already had A as the active partition, and I did not have to reboot into Lineage before installing Gapps and I did not disable verity. I did do it both ways, rebooting and then installing gapps and disabling verity, but it worked for me without doing these steps.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Cheetah74:
On google hangouts and google meet microphone is not working. Tried on other apps like Camera, Google Assistant and the Google app there the mic is working perfectly fine so isn't a hardware issue for sure. Also on the stock rom the mic is working fine, only during hangouts call or video meetings in google meet the mic doesn't work at all.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] jman315:
The solution that I found to work is...

1. Install the Phone app from Google in the Play store.

2. Make the Google Phone app the default app in settings.

3. Reboot.

4. Try a test call. I used 1-866-210-2157 (press 3 then 1 to record your audio).
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Eguy:
Just got this installed on my G7 after taking forever following _Clon_'s guide. First time dealing with an a/b device. I have Magisk installed. Is there a way to use lineageOS updater? Or do I have to manually install the full linage zip, twrp zip, and Magisk patched boot img every time I want to update the build?

Thanks!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
We've Merged a voip audio fix recently. Should now work as intended.

We've Merged a voip audio fix recently. Should now work as intended.

If you update with lineage updater you will lose magisk / twrp

The best method to keep these is the manual flash / update method.

Flash lineage zip + twrp.zip

Reboot recovery

Flash magisk + gapps zip

Reboot system
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Eguy:
Gapps every time too? Do I have to flash the Magisk patched boot image from fastboot each time as well? Thanks for answering
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] shlape:
Is it normal to have a warning appear each time I reboot the phone?

The warning states my phone can't be trusted, which first appeared after I unlocked the boot loader.

After a short delay the phone boots into Lineage OS.

Is there a way to switch off this warning (and the delay it causes)?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] willcall:
Delete
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] experiment322:
Yes, it's normal and it's just a warning, you can ignore it, even if the increase in boot time is a little annoying.

I know that I wondered myself the same thing when I started with this device and unlocked it and found out some threads here on XDA on how to do that, but I can't recall if I've found instructions specifically for this device.

There are for other Motorola devices, but I can't find one right now on how to do it for every device having this thing. It's basically some tinkering with the logo.bin, but I don't know what.

I got used to living with that warning :D.

EDIT: Found this for this device - https://xdaforums.com/moto-g7/themes/custom-logo-bins-moto-g7-power-rid-root-t3967463
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] shlape:
It's an interesting link, and I'm tempted to give it a try, but at the risk of bricking my phone for 'aesthetics' I think I'll learn to live with that too. Just wanted to check I didn't do something wrong.

I may have found a bug relating to System Profiles. Basically, I wanted a mode where I didn't need to unlock the phone while at home, but switch the screen off to save the battery while not in use. Additionally, have another profile when I'm at work to lock access to my phone from other peoples' "curiosity". ;)

I created a profile called "Home", which is set to leave all other settings unchanged except the "Lock screen mode".

I set the "Lock screen mode" to "Don't ask for a PIN or password" but it still requires me to unlock with a screen pattern (this is the unlock method I use). Is this how it is meant to work, ie pattern unlock still required but PIN is not for this mode?

Setting to "Disable lock screen" doesn't appear to work correctly either. Sometimes clicking the power button will switch off the screen (which is what I want it to do), and other times the screen will light up again a second after it darkens. I have also tried the double-click the status bar to switch off the screen, but it lights up again a few seconds later.

Just now, I changed the settings while compiling this post, and it is currently working, ie toggling the power button turns the screen on/off, as required. I then changed it to "Don't ask for a PIN or password", which first asked me for my pass pattern when I first clicked the power button, but successive clicks no longer required the pattern to access the screen (I only had to swype).

The behaviour seems sporadic, ie either of these mode settings don't have a consistent behaviour, or behave opposite to their namesake.

One other thing that I'm not sure if it's related. Out of the 3 buttons at the bottom of the screen, only the 'back arrow' works, seemingly after changing the profile, ie the circle and square do not respond.

Any ideas?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] BennTech:
Bluetooth Issues

Anybody else having Bluetooth issues with LineageOS 17.1 on Moto G7?

Ever since installing, my Bluetooth occasionally drops connection to car stereo or laptop. Have to manually reconnect or sometimes restart Bluetooth or phone. Two of my Bluetooth speakers now have issue where they connect then immediately drop. Fixed that with Tasker Profile to force connection after it first sees affected speakers.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] VoreDock:
youtubeTV keeps hard crashing the os only if i use the volume or full screen
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] DrWu:
This probably is naive or ignorant (or both) but now that I'm on LOS 17.1 with LOS recovery, I can't figure out how to make a Nandroid backup or clear a cache. Is either possible with LOS recovery? I ask because I understood TWRP recovery was never going to be available for Android 10.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
A/B devices don't use a cache partition.

Also Twrp10 is in development so no worries there
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] DrWu:
Huzzah! for the TWRP team. And thank you, SyberHexen, for the reply.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] idumych:
I'm using a RETUS variant, and it has been screwed up ever since I tried that Ubuntu GSI. I'm able to get it to flash and run XT1962-1_RIVER_RETUS_9.0_PPOS29.114-134-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, which works fine, including cellular functionality. However, whenever I try to install Lineage 17, either the IMEI disappears, or the modem just refuses to power on. I have tried flashing to slot B after flashing that partition zip, and i also tried installing to slot A. Same issue either way. Any ideas?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] idumych:
I wish they worked for me. I did a clean flash from the Lenovo rescue too. Then, I followed these instructions. I get this, even after rebooting and trying again, every time.

Same result with these instructions as well. https://xdaforums.com/moto-g7/development/rom-lineageos-16-0-t4004357/page19 Why won't my phone run anything other than stock? WTH am I missing here?

---------- Post added at 07:06 PM ---------- Previous post was at 06:56 PM ----------

So later I was able to get it to at least flash by installing the LineageOS recovery via TWRP, and booting in to that. It just doesn't work in TWRP at all, confused how it's working for anyone else. But, surprise surprise, no cellular. IMEI shows up, but radio is stuck off.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
Shared in the event it helps others... the device is river, XT1962-6

I ran into a little trouble installing magisk after upgrading from 17.1, 20200614 to 17.1, 20200712. I booted the july 12 lineage before installing magisk. If I go back and try to install magisk from lineage recovery, the phone won't boot (just a black screen). I can get back into fastboot, reflash lineage recovery, and get back to the july 12 image without issues, but I'm a little unsure about what to do to install magisk at this point. I'm going to try to install magisk from twrp (temp. twrp boot). That does not work, I'll try reflashing the july 12 image and installing magisk before rebooting.

Comments or suggestions welcome.

EDIT: FWIW i first attempted to update to the july 12 17.1 ota with magisk left installed. The ota update did not complete. The update app just crashes at the install stage. Removing magisk stoped the installer crash but the update app will not install the new update:rolleyes:.

fun fun fun,

if I set the current slot to the june 14 build (in my case going from slot a with july 12 to slot b jun 14) and attempt to reboot, lineage does boot but I lose touch screen access so I can't get in. Fortunately I do have adb root access.

bah - my bad. Earlier I carelessly flashed the july 12 recovery to slot b (that has the jun 14 image). re-flashing the jun 14 recovery to slot b allows me to boot slot b and the touchscreen works again. will try again to get magisk on slot a with july 12 and report back later

Last EDIT: I got it to work. The instruction posted Syberhexen do work, but they are a little unclear to me given how I've been able to upgrade/sideload in the past and the multiple recovery versions available. So here is what I did:

Running lineageos 17.1 june 14 build on slot b:

1. reboot to lineageos recovery and from this recovery (current slot is b):

2. adb sideload lineage-17.1-20200712-nightly-river-signed.zip (installs july 12 build to slot a)

3. adb sideload twrp-installer-3.4.0-0-river.zip (installs twrp to slot b and a)

3. reboot to recovery (twrp 3.4 boots)

4. sideload magisk (I don't use gapps...)

5. reboot system

When I updated from lineage 16 to 17, I recall being able to use lineage recovery for the whole process. Now I am unable to use lineage recovery to install magisk to slot a (with the july 12 build on a) and I also could not install magisk using fastboot boot twrp from slot a (again with july 12 on a). In short, Syberhexen's instructions are the only method that worked for me.

Pleasantly, my magisk modules from the june 14 build are still present on the july 12 build and functioning normally after all this - thanks for that, and for all the work done to do the update.

HTH
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
It looks like the OTA update to lineage-17.1-20200712-nightly-river-signed.zip fails as reported by other users. I have magisk installed and every OTA update before that worked like a champ.

Is this a temporary issue? Would you recommend to wait for the next nightly update or update manually?

Thanks!

EDIT: problem solved with the 7/19 OTA update.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
17.1 attempting to tether disrupts phone data connections

Start EDIT 2:

I got it working. Googling, I found this thread with a suggestion to turn off "Tethering hardware acceleration" found in "Developer options." Other suggestions in this thread did not work including to reset wireless settings (which I did).

I still have issues with my VPN but this may be specific to the app and unrelated to the tethering issue. At least, tethering my PC through my phone now, I can VPN from my PC to my network and ping/ssh to clients in that network.

END EDIT 2

I believe I just ran into this issue in which the phone is unable provide internet to another device by tethering (USB, wifi, or bluetooth) and just making the attempt disrupts data on the phone. I can get data on the phone back if I turn off tethering and then toggle data off and on.

I first observed this behavior on the july 12 build. I am uncertain if I used tethering on the june 14 build but booting to the june 14 build now, I have the same issue.

I don't use tethering frequently, but I do rely on having the ability to do so when needed so I'd like to revert back to 16.

Is there any issue with reverting to lineage-16.0-20200325-nightly-river-signed.zip on the slot that currently has the june 14 build on it?

EDIT looks like reverting to 16 is not possible without factory reset/wiping data. Also my carrier/account allow tethering and when testing just now on an recently updated ios device tethering works just fine.

EDIT 1 another possibly related symptom is that my strongswan split tunnel vpn will connect as usual (when using my carrier LTE data), but the app that uses the vpn does not pass data. I do not lose data access for other apps in this case.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kdm6389:
Is VoLTE working is this ROM/LineageOS ?

---------- Post added at 07:36 AM ---------- Previous post was at 07:26 AM ----------

my service provider allows only VoLTE call, I can use data with speed of 16-21mbps on LTE, but can't call, currently relying on whatsapp call.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Who's provider, I've managed to get a VoLTE working on Google Fi recently
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kdm6389:
att, I am using alcatel 4060A with HD Voice / VoLTE. Would you explain how did you archived? I want to stay stock, since I use Google Pay. I have update last week to android 10.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] step_21:
With the Lineage OS build of 16 Aug 2020 for river, the French app called "Molotov TV" makes the phone crash and provoke a reboot, from the moment I start a video inside "Molotov TV".

https://gitlab.com/LineageOS/issues/android/-/issues/2492

https://gitlab.com/LineageOS/issues/android/-/issues/2241
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Zaxx32:
AWESOME NEWS!!! :victory::highfive::good::good:
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] AluminumTank:
Just wanted to drop a note here since I see a lot of people asking about whether LTE, HD calling, VoLTE, etc. are working with this ROM. I helped a buddy of mine who only had 3G on their Moto G7 with Lineage 17.1.

I believe the context is that they had originally been using it as a non-phone device. I helped them to install LineageOS 16 on their device. They directly upgraded from 16 to 17.1 when the nightlies started to come out. When they finally put a SIM card in it, it only had 3G no matter what we did to it. I helped them back up all of their data, then downloaded the latest Moto G7 (RETUS) firmware, which is Android 10. When I booted up stock Android 10, LTE and everything else was working. After installing the latest LineageOS 17.1 nightly, LTE is also working on LineageOS.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kdm6389:
Today I have installed Lineage OS 17.1 (lineage-17.1-20201004-nightly-river-signed.zip) and Jio VoLTE is not working.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Eguy:
I'm having a problem with camera focus on mine, I couldn't find anything else searching the threat. Pictures are focused until I press the shutter button and then come out blurry, especially in WhatsApp. Is that a known problem with this rom?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] thisisapoorusernamechoice:
Just wanted to say thank you so much for maintaining this device. Been using the device tree for crdroid
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] HueyT:
I also enjoy your builds on AFH
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] thisisapoorusernamechoice:
Weeklies in conjunction with lineage for as long as my river keeps chugging along and I never upload before making sure it at least boots for me first. I gotta say for the price I paid I'm really loving the performance I'm getting out of this device.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] HueyT:
Do you care if I post your AFH link to Moto G7 Telegram as many avid users there also?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] lcdial:
Thank you! I had the same issue and turning off the hardware acceleration fixed it for me as well!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] BennTech:
I finally gave up on LineageOS 17.1 and reverted back to 16.0. Tired of loosing Bluetooth connections. Tired of Bluetooth not working and having to restart it. Furthermore, as 17.1 updates progress, Tasker usability is deteriorating: can no longer mount /system as writable, can no longer turn WiFi on/off. Almost as annoying as Bluetooth issues, camera cannot save to SD card. Doesn't tell you, just never saves your photos. Why even have that option if it can't do it? Just to screw with people and lose their photos? Couple of other minor OS issues, like LineageOS updates fail and have to be re-downloaded and re-installed.

Also tried Havoc-OS, which I believe is based on LineageOS. Unfortunately, same issues. Shame. LineageOS 16.0 is missing features that I really like in LineageOS 17.1 and Havoc-OS. Admittedly, 16.0 has some annoyances itself, but at least everything works: Bluetooth doesn't randomly fail, Tasker can control WiFi, camera can save to SD.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] :
In the event you're motivated to try 17+ again in the future:

About the time of you June post about bluetooth troubles, I was having more trouble than "normal." There were a few updates that seemed relevant to bluetooth shortly after that so I updated and removed/redid all my past bluetooth connection configs. After that it has been closer to "normal." I have had at least one unexplained disconnect since then; however, I believe I just redid the connection and it hasn't occurred again. I have yet to get a logcat after one of these events to submit with a bug report.

Unfortunately for me with moto devices (not just the mg7) and lineageos, "normal" consists of redoing my bluetooth connection settings after every update. For some reason my vehicle does not like it when I update and usually refuses to connect to a saved connection config after an update. That might explain why I don't observe the issue as frequently as you have.

EDIT: I also "reset" my wireless connections (which includes bluetooth) when I was trying to figure out why tethering had stopped working. Settings, advanced, reset options, reset wi-fi, mobile & bluetooth.

Regarding the SD card, others have pointed out that AOSP/googles support of using a SD card is poor. I tried it anyways and learned that I should not trust google/android for anything important. It works well enough to get by, it can be a fun toy, but all the talent that lineageos developers have x 1000 isn't enough to fix google's turds.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] crazy4jack:
so im on stock andorid 10, is there any advatnages to go for Lineage or Pixel ROM? better battery maybe? better photos? any?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] BennTech:
Unfortunately, in the few weeks since reverting back, I have encountered twice when Bluetooth disconnected and needed to be manually connected. Dark mode, which I prefer, is barely partially functional. Most apps, particularly widgets, aren't doing dark mode at all. I have that annoying double Privacy Guard plus Android security settings, and the always-on Privacy Guard notification about apps not having access to personal data.

On the positive side for 16.1, camera photos to SD card works again (unlike 17), which is critical to my backups--I don't use my Google account for that. Tasker has access to WiFi again, whereas on 17 it has recently lost access (yes, I checked all the permissions), and SmartStay+ works again (defunct facial detection app). Both are critical to my configuration. Screen actually times out again, whereas on 17 it stayed on all the time.

So couple of annoyances going back to 16.1, but huge functionality benefits over 17 upgrade for me. YMMV.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Usernameisnotavailable:
Thank you. Your instructions helped me a lot. (I almost missed step 0) After hard bricking the phone following other instructions, I was able to install LineageOS successfully on moto G7 river (XT1962-1) I did run into some errors, but in the end everything seems to work fine. I do want to mention that it's IMPORTANT to have an active sim card installed and have the phone connected to a carrier network (and update the carrier settings in Google play store.- No need to login ) before flashing Lineage. I learned the hard way that there was NO LTE (4G) connection, no wifi calling and very poor signal after my first installation. Had to do it all again and it all works great. (including WIFI calling) I'm on Verizon btw. Hope this helps someone!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] vulkan-ops:
very good rom