yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.

[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Well the official one is missing some things then one I posted whit h has no problems I use it
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.

[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.

edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.

Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.

does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Not recommended as this can really brick your device.

Just flash custom bootloader logo.bin to remove that screen

---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------

I'll be making new devdb posts for official G7 ocean/channel..

once threads are active please post there.

Thx
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
In stock LED only indicates charging (unless rooted and using an app such as LiteFlow) but in LOS the LED should also work for notifications, although the color cannot be changed. There is a place where you can disable with it for charging. Search settings for battery light.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] WaterMan!:
That's great, thank you! Crazy how it doesn't work on stock ROM at all.

Another question - I am reading up through the past posts about this "party mode" issue, and I do have it. What's the general consensus? How do I return the colors and so forth back to normal? Thanks for all the help!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Change the color profile to any other setting then back to what you want and then never touch the live display setting or the live display quick tile.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] WaterMan!:
Thank you, that much I gathered. The issue is that I cannot find the setting that changes color profile, what is it called?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
LOL, I'm on stock now and forget what it is but IIRC it might be adjacent to the live display setting. Also, as it was previously discussed here the full path to the setting might be described somewhere in this thread. Additionally, in Android, searching settings for "colors" might find it.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] onyxcode:
I think so, when it turned on for the first time holy crap that thing was bright. I disabled it lol
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Tod13:
Does anyone else have the problem where clicking on the Add Account to add a second account in the LineageOS Email app causes the app to crash?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] onyxcode:
I personally prefer third-party email clients like Zoho Mail. However, upon inspection, I am not having this issue in the latest version. Are you on the newest version? It came out on the 6th.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Tod13:
Thanks for the quick check. I'm running the 02-03 from MicroG. I think they'll get the 03-06 build out this weekend, so I'll test it again. I don't need much from an email app, and a lot of the third-party ones are overly complex for what I want. I'll probably test the SimpleEmail fork of FairCode if it remains an issue.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Tod13:
BTW, when I do the next phone, I'll be building and posting a install walkthrough (on Linux) and posting the APN settings for T-Mobile USA. (The ones in the ROM did not let my phone make calls.)
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] imarsh72:
are there specific variants that have this led, mine is uk 1955-4 model but I'm quite sure I don't have one
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] onyxcode:
I'm not sure, I have the XT1955-5, which is the US T-Mobile variant.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] WaterMan!:
Well, I really like it on my backup phone, so I may switch over my daily G7 to LOS17. A couple of questions:

1) Are there instructions for root with magisk? Seems weird it's not included in the ROM.

2)Can I still get updates if rooted?

Thanks in advance!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] BTK19:
Flash the ROM and TWRP installer.

Choose Reboot -> Recovery

Install GApps & Magisk.

Reboot -> Bootloader

fastboot -w

Yes you can update if you're rooted
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] joefidler:
Not sure what a "modded" Official 18.1 LineageOS build is, but here goes...

https://t.me/MotoG7PowerBuilds/435
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] WaterMan!:
Okay, so I got the devices rooted on Lineage OS 17.1 successfully, on an already installed and used ROM. I found information kind of all over the place so I will put it all together here. Anyway after you have installed LOS:

1) Download the magisk app, it is an APK. I got the apk file from Magisk itself HERE. You need to rename it to a .zip, then put the .zip on your device

2) Download the TWRP .img file. Place it in the same folder you'll be running commands from, or otherwise somewhere where it is easy to reference.I used twrp-3.5.1_10-0-ocean that I got HERE

3) Hook up your phone. ADB debugging enabled. Boot into the bootloader using the command "adb reboot bootloader". Verify your device shows up with the command "adb devices"

4) We will boot into TWRP, not flash it. The command is "fastboot boot twrp-file-name.img"

5) Keep the system read only when it prompts you. Don't know if it matters, thats how I did it. Now flash the magisk zip from step 1, and reboot. Ta-da!

I haven't got an OTA yet, but when a new one comes out, I'll see if root remains after an update.

PS: It does not pass safetynet.

EDIT: Yes, root survives updates!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] MatheusAlpha94:
guys, I put the rom on my girlfriend's phone, but the phone is muted in the calls (no one hears anyone), what solution to be taken?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] thespacemonky:
Followed install directions but when I did the command to reboot so I could install GAPPS the os came up. In the instructions say you need to flash gapps before running os out of the question now caused it booted so when I go back to recovery lineage recovery comes up cant get back to twrp so can I sideload gapps from this recovery or do I need to start over. the os runs fine.

Update: factory reset, side loaded GAPPS in lineage recovery then reboot will see if that works with no errors
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] thespacemonky:
Seems like Lineage OS killed my camera quality pictures look out of focus and lights blur really bad is this normal?

Another issue discord wont run either

half the apps wont run

I know the problem is with google play services how I do I fix?

Ok had try like half gapps listed on open gapps got one to work correctly
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
any news on bring up for lineage 18.1 as it was official as of yesterday on different XDA news threads.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] berlinerbaer:
Seems like my G7 power has graphical issues on LineageOS 18.1 (official release).

I already had those Issues on 17.1 with multiple sim cards. One sim card alone worked out fine.

Edit:

A reset solved this issue for now.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
any other issues with lineage18.1 just out of curiosity what gapps ddid you use for that flash. .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] MatheusAlpha94:
friends, i really need your help, my girlfriend's cell phone after i passed this rom, she kept the dumb calls, on the speaker and on the microphones, i've reinstalled even the rom stock, and i couldn't fix the problem, someone help me?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Stilbium:
Hi,

I'm curious if there is any progress regarding this issue?

I have g7 power 1955-5 (T-Mobile prepaid US) and have not been able to make VoLTE/VoWiFi work, neither with LOS 17.1 nor after upgrade to 18.1. IMS is not registered, carrier's instructions for BYOD do not help much...

Would appreciate any help, it looks like the phone will turn into a useless brick without VoLTE support as soon as they switch to 4G completely...
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] zendude:
I noticed that lineagesos 18.1 has been available for download since April 1st and the last 17.1 version was released on March 27th. Does this mean 17.1 is no longer maintained? I normally prefer to hold off upgrading until the newer version is time-tested and deemed stable.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
that maybe hte case.but dont know. usually when there ar newer lineage releases the older ones will usually go on a weekely or semi weekly basis.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Typically a device will not receive official builds from the previous android version if it has been added to the official build roster for the next android version. This makes sense because development by nature is forward-looking and testing in the previous android version would not inform bugs in the new android version. You would not be the only person who stays with the last official build of a previous android version while waiting to see what happens. Also sometimes developers may release on official builds of the previous version including security patches.

IIRC the way it used to work is that devices on the roster for new android version got daily builds and devices on roster for previous android version got weekly builds the lists were mutually exclusive. Interestingly, now all builds are weekly. https://github.com/LineageOS/hudson/blob/master/lineage-build-targets.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I'm now running stock on this device and testing LOS on a different device so I can't speak to this for current builds but for what it is worth:

In stock I did not have the same problem where LTE did not persist during phone calls. In my case it's unclear if I did something wrong while flashing or if there is an issue with the ROM but for T-Mobile service I suspect the latter because there has not yet been a confirmation that voice over LTE is working on T-Mobile service om LOS on this device and there has been confirmation that it works in stock on the same devices (here and in other forums).
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Yep. During what I thought would be a quick test of a build a few months ago the device was not connecting properly to cellular service. It saw the cellular service but it did not pick up any bars and could not make calls or connect to data unless forced to use WCDMA. While attempting to restore previous version and do another test something went wrong in TWRP and I was stuck so I figured that was a good time to go back to stock. In stock I found as mentioned above that VOLTE issue no longer occurred, in fact a few things were better in stock and I might as well share some details.

VOLTE: the path I took through this from first installation of LOS and since then introduced the possibility that I messed something up as SyberHexen had hypothesized, but here and in other forms I found multiple reports of issues with VOLTE in LOS on T-Mobile and no confirmations that that combination worked as it does in stock. If and when I returned to LOS on this device I'll watch this stuff closely..

Messy fade in/out when switching call between handset mode and speaker mode and occasional failure to exit speaker mode. This has never happened in stock even with the same phone recording software installed.

The rules of the ballgame have somewhat changed with the move to android 11 so I would not call these bugs but they are worth noting because some issues to travel along the android versions.

Also, it seems that the underlying issues with saving photos to external storage have been rectified and that functionality has been restored to the camera which can now properly access photos saved their. I noticed this well testing LOS 17 on a different device.

Anyhow, as this is my daily device and there was an instant gain in the return to stock I stayed there, and probably will stay a little more while testing LOS in devices that don't matter to me so much as this one with its capacious battery.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Stilbium:
Thanks a lot, I really appreciate your assistance.

The whole situation seems to me a bit weird, because of one hand there are reports like this one:

https://gitlab.com/LineageOS/issues/android/-/issues/3269 (device: river)

where someone was able to restore defunct VoLTE just by going back to stock and then reflashing LOS17.1, but then lost it again after upgrading to 18.1 (also T-Mobile).

On the other hand, there are several threads on Samsung phones running stock Android (about half a year old) that lost VoLTE/VoWiFi after an official Samsung update just like me/us on LOS. Also T-Mobile and also no fix so far.

What I'm trying to say - is it possible that T-Mobile is somehow special and this might cause problems? I heard of smaller carriers that do not allow VoLTE on the devices not bought directly from them, but it is probably not the case here...

Also, I've noticed that on my device data connection switches between LTE/H+/3G (according to the indicator) even when there are no calls. It happens in the same places (with poor signal reception I guess), so I suppose that it is T-Mobile who's responsible for that.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
With AT&T's impending 3G shutdown, I am trying to make sure that VoLTE is working on my phone. However, I can't get it working. Using the NetMonster app, I can tell that my phone is using LTE, but as soon as I make a call it drops to 3G, indicating that VoLTE is not working.

I actually just bought a disposable T-Mobile sim, thinking that it was AT&T's fault - same issue.

Setting the phone to use LTE only (rather than LTE/CDMA/HSPA/etc..) results in calls failing to go through.

Does anybody have VoLTE working on this ROM, or even on this phone? If so, did you do anything special?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
When I switched back to stock on the G7 power volte (t-mobile us prepaid) started working and still is working through at least 2 clean manually applied stock firmware updates. I've even had a chance to test it in an area where there is LTE service but no 3-g service and it performed fine.

Also, I've seen indications of my T Mobile provider bringing some older devices, IIRC Moto Z Griffin, into the volte roster but in the case of the G7 I'm fairly sure the device itself was volte capable before I switched to stock several months ago. As yet I've seen no reports at XDA or elsewhere of volte functioning properly on Moto G7 LOS17.

If there is any additional information I could provide from stock dont hesitate to ask
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
Thanks! It's good to know that VoLTE is at least supported in hardware. It seems that the IMS service is having trouble pulling config data:

05-15 21:57:36.013 2102 2102 D RadioInfo: updateImsProvisionedState isImsVolteProvisioned()=true
05-15 21:57:36.027 2102 2102 D QImsService: ImsConfigImpl : getConfigInt :: item=25
05-15 21:57:36.028 2102 2102 I QImsService: ImsSenderRxr : [0112]> REQUEST_GET_IMS_CONFIG [SUB1]
05-15 21:57:36.028 2102 2102 I QImsService: ImsSenderRxr : REQUEST_GET_IMS_CONFIG request to ImsRadio: token 112 item:25 boolValue:false intValue:0 strValue:null errorCause:0
05-15 21:57:36.030 2102 2274 I QImsService: ImsRadioResponse : Get config response received.
05-15 21:57:36.030 2102 2274 I QImsService: IFRequest : [0112]< REQUEST_GET_IMS_CONFIG error: 2
05-15 21:57:36.030 2102 2508 I QImsService: ImsConfigImplHandler : Message received: what = 1
05-15 21:57:36.030 2102 2508 I QImsService: ImsConfigImpl : Notifyall
05-15 21:57:36.031 2102 2102 D RadioInfo: isFeatureProvisioned() featureId=25 provisioned=false

Is this QImsService code online anywhere for me to take a look?

I've been experimenting by flashing various modem firmwares (T-Mobile, RETUS, RETLA, etc.) with no luck so far. In fact, the only modem firmware that I hear any audio on calls with is my original RETLA firmware.

This may be complicated by my device being a XT-1955-2 (RETLA)..

edit: Interestingly, the guys over at G7 Plus are using a Moto proprietary IMS package...

android_device_motorola_lake/proprietary-files.txt at lineage-17.1 · LineageOS/android_device_motorola_lake

Contribute to LineageOS/android_device_motorola_lake development by creating an account on GitHub.

github.com

The IMS package installed on my phone is org.codeaurora.ims, not the Moto version. Looks like I need to get my hands on the Motorola IMS package. Anybody know where I can download that?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Stilbium:
Take a look here:

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

I had exactly the same problem on my Moto G7 Power (ocean) (neither VoLTE nor VoWiFi) using LOS17.1. Going back to stock and then installing 18.1 anew recovered at least VoLTE. Have no idea why it worked, but the TS initially reported the same trick on his "river" with 17.1.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
Some good discussion over there. I have two theories:

1) VoLTE only works when the proprietary binaries are included in /system or /vendor or wherever. If you did not wipe the system partition before going from stock to LOS, this theory might hold water.

2) Installing the stock ROM modifies a different partition which is not touched by the LOS installation, such as /modem, and this is the difference.

We can rule out #1 by determining whether you wiped your system partition before the stock -> LOS flash. Do you remember?

For #2, I have already tried running the following with partition files from various stock ROMS, to no avail:

fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn

fastboot erase modemst1
fastboot erase modemst2

fastboot erase cache
fastboot erase DDR

fastboot reboot

Perhaps there is an additional partition which is critical?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Stilbium:
Yes, I wiped both system and dalvik cache.

I also tried to flash the radio/modem part (extracted from the stock) while using LOS18.1 (I'll post the link with the code later), but it did not fix anything but caused additional problems... after which I went to stock. I am not an expert and I guess I might (or even likely) have made some mistakes there.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
I think this rules out that there are any binaries we need from the system partition.

I extracted a LOS 17.1 image, and discovered that it had the following: boot, dtbo, system, and vendor.

The stock image has bootloader, modem, fsg, dsp, logo, boot, dtbo, system, and oem.

This leaves the following partitions as culprits:

bootloader, modem, fsg, dsp, logo, oem

Of these, I think that the critical partitions are modem, fsg, and oem. I doubt that the DSP partition is used for this.

I will try to flash those and will let you know when I brick my phone succeed.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
... and added to the provider's roster (as I understand it) of supported devices.

Now that the Moto G (unofficially 8) Power has received official Android 11 I may be able to switch to that one as my primary and be free to test some LOS. Meanwhile, I'm way behind you and @Stilbium regarding the technical details but delighted that anyone is hacking away at this. As before, if any information from volte functional stock Android 10 on us T-mo is needed just say so.