yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] palmbeach05:
Weeklies are continuing. We did not make the first round of promotions to 18.0. when lineage team says bump it, it will happen.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
thanks, that's all i needed to know.thanks will be patiently following the thread.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] imarsh72:
this is of course reliant on a developer wishing to maintain the device on 18.0 ??
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Indeed to both points. Also, this device has been receiving LOS17 official builds for only a few months and there are still things to fix. Racing ahead to the next version for the sake of it will not necessarily fix those things. Of course continued development is good and I hope for that but being able to say "I've got a bigger version number" seems less meaningful than being able to say "there are no more or (or at least there are fewer) bugs to be found."

P.S. big difference in battery life between this G7Power and the old Atrix HD which I see is still in your signature. :)
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Esin8785:
Thank you so much for your time in doing this, I have installed lineage on this phone installed magisk and the modules riru exposed framework indeed works, at first bootup it acted like it didn't want to start I held the power bottom and it turned off and I restarted it and then it went normally instead of bootlooping, this ROM is super awesome thank you so so much (bootlooping only happened after I installed riru framework and it was resolved by power the phone down and starting it back up)

---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------

You can install the ROM without a sdcard just FYI you can put it on your phone after you install twrp you do it when you put the root app and the no variety deal and gapps and the twrp install file in twrp folder as its the only one after you format data and type yes you will have the option to load the phone up with files you can flash via twrp
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] ovrwrt:
Party Mode is still occurring on latest update (21 nov). I mean, if they solve it by bumping into 18, I'm not complaining :/
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Likewise. I thought it may have been partially fixed but party mode still occurs in each build and is still easy to avoid, in my case by disabling Live Display and hiding the live display Quick Tile.

As to other potential glitches (since I was planning to follow up on these anyhow):

Spell check broken:

I've logged this in each of the last 3 builds and will actually create a ticket for it this time. Can anyone confirm if the red underline spell check functions properly and if so what language settings are in pace?

Failed toggle between headset and speakerphone mode - stays on loudspeaker mode: This might have been caused by or been exacerbated by the presence of call recording software. Disregarding for now.

Volte and possible Data-bundling issue:

It will be another week before I can get to the computer on which I can run RSD lite but meanwhile I have been doing some research and more testing. There are indications that T-mobile may indeed not provide Volte service to this particular device even though it is capable but the various bits of information about that (from Moto, T-mobile and general web) conflict. Pending restoration of stock and answers from others.

Missed notifications for text messages and phone calls when LTE is enabled but not when WCDMA/3G is forced

This may relate to Volte issue but is worth reporting separately. When LTE is enabled (even if not forced) then the phone does not always detect incoming calls. The caller never hears a ring and the call goes to voice mail with no ringing on the device and no notification of voice mail until the state of the cellular connection is changed. I have seen that same symptom set some time ago in stock Moto Atrix HD (Jellybean) where "modem fast dormancy monitor service" was not properly inducing the switch from LTE to 3G to receive a call or cellular notification. In that case the problem was between the MFDM service on the phone and the AT&T modems in the towers but considering the changes to the tech landscape over the years and cross testing in other devices and SIMS that I've done, issues in the modems in the towers does not seem a likely cause. That being said, in both cases switching to WCDMA (3G) only prevents the issue because MFDM service is not needed to make the switch.

I was able to observe and log this a few times during one instance and will create a ticket for it apart from the Volte issue.

[MENTION=9549572]Pio_CPD100[/MENTION] & [MENTION=3538171]redspeed[/MENTION], it would be informative to know what region and type of T-mobile service you have.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
no rush, as long as the device is being maintained, and continued to be developed that is all that matters.do agree its better to resolve all issues before bumping to another major android build.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] CAKyPA:
[MENTION=5119654]IronTechmonkey[/MENTION] thanks for reporting problems, I'll add my learnt things from those problems.

Party mode:

- Haven't tested latest builds, but Party mode happens after every restart, fixed by changing colors (boosted/normal to saturated then changing back to boosted/normal).

- To me, it can be triggered if you left the phone to screen locked.

Failed toggle between headset and speakerphone mode:

- Noticed this issue too, but it can't happen if you trigger the Party mode then fixing the Party mode with changing colors. If you make a call before Party mode fix, it can't be fixed later.

- So I think that Party mode is root of this issue.

Missed notifications for text messages and phone calls when LTE is enabled but not when WCDMA/3G is forced:

- This happens only when the phone is screen locked.

- Also when WCDMA/3G is forced, text messages are still delayed to show notification.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thanks. It's good to bounce around these ideas and also to have some validation for a few particular observations which multiple people have made.

If you have not tried this already and if you do not use Live Display then disable Live Display in Settings > Display >,Live Display > Display mode = Off, and remove the Live Display quick tile. In my case, after that is done then party mode does not occur even after reboots but there may be variations in our experiences.

Interesting. I've not noticed a correlation between this and party mode but will watch out for that when I install a call recording software now that live display is disabled and party mode will not occur.

An additional observation about this one; The fade in and fade out when toggling between headset and loudspeaker mode seems a bit extreme in this ROM. IIRC the fadeout exists to prevent people from being blasted with full volume immediately upon toggle but things tend to run smoother without the fade in/out. Such is the case in LOS and 15 and 16. This may not be the cause of the issue but is worth noting for diagnostic reasons.

I'm using T-Mobile US use Prepaid. What service are you using and in which region?

For this one we may be seeing different things. Although this did sometimes happen when the device was locked most of my testing and all of my logging was done when the device was not locked. In fact the display was on and I was interacting with it in order to enable the logging app while calling from another phone to observe the issue - I was looking at the unlocked and powered on display during the test. Also, if my hypothesis about (what was once called) data-bundling is accurate, then the log may contain few clues because the phone did not know a call was incoming (which is the definition of the issue) however the log includes the step where the cellular connection state was changed and the notification came through.At that last part there may be something informative about the issue. In any event it's enough to create a ticket. I have yet to witness the issue when forcing WCDMA/3G so that part of the testing continues.

Thanks again for the brain bounce.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] fastness:
This lineage 17 works well at Tello ( Sprint LTE / CDMA network, MVNO ),

Tello APN setting,

Name, internet

APN, n.mi.ispsn

Proxy, Not set

Port, Not set

Username, Not set

Password, Not set

Server, Not set

MMSC, http://mms.plspictures.com

MMS proxy, oap7.sprintpcs.com

MMS port, 80

MCC 312

MNC 530

Authentication type, Not set

APN type, default,mms

APN protocol, IPv4/IPv6

APN roaming protocol, IPv4

APN enable/disable, APN enabled

Bearer, eHRPD, LTE

MVNO type, GID

MVNO value, A00165FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

* The stock Android ROM shows MCC, 310, MNC, 000. when the 310/000 were input manually, the APN will crash/disappear by itself.

With the Lineage ROM, MCC312/MNC530 in the file can get LTE Sprint network after rebooting. After getting the LTE, App shows the true MCC 310, MNC 120.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Regarding Camera Save to SD (which is not device specific) FYI; a resolution to the camera save to SD issue, which is the removal of the capability to do so: https://gitlab.com/LineageOS/issues/android/-/issues/2114

Additionally: Another observation about spell check - it actually does get invoked in rare instances such as 2 partial words with a period in the middle but then cannot be reproduced, This is similar to something I've seen in text editors when the wrong character set is used but this problem is device wide in all keyboards that use native spell check. I'll fold it into a ticket as it does not seem to be device specific but again... if anyone could share their experience with spellcheck (not auto-correct) that would be helpful.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Johnfoo19:
Spell check always gets invoked in that circumstance, at least in spanish.

About camera issue I really can't tell 'cause I use google camera instead. The only time I use snap camera, AF seems to be totally broken

And the so called party mode is there even if you entered live display option just to check what it is

Beautiful rom must i say
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Good to know but in English it is not detecting any misspelled words apart from ones associated with the period and is not even detecting all of those. That is to say it is missing the vast majority of what is should catch.

As described in the referenced ticket and some detailed notes in this thread the issue was clear and now so will be the resolution ... when it is applied in a future build. This is the the link the the developer had just posted in the ticket to the upcoming commit where ability to save to external SD is removed. https://review.lineageos.org/c/LineageOS/android_packages_apps_Snap/+/291025

True that. Same here. Possibly likewise any time Live Display Quick Tile is added or removed.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] CAKyPA:
I'm using with GSM based Asian network that supports both 3G and 4G.

Maybe you're correct, i'm only tested with screen lock. To add, it can receive calls right after the screen lock, maybe you need to wait 10 min or more to become it can't receive calls.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] archstar1982:
Installed rom from latest nightly to XT1955-5 last night along with twrp-3.4.0-1-ocean and Gapps.

First I noticed touch screen unresponsive sometimes. But I managed to install latest rom from official LOS17. After the rom installation process G Apps are not able to install with error within TWRP. I decided to use ADB push and it went successfully. No issues since initial boot and I decided to install Magisk using TWRP but when I restart to recovery mode TWRP will not start.

I am not sure why TWRP is not booting up in recovery mode...
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] nighthawk676:
Greetings - I hope this is the correct forum to post a question in regards to trying to install this custom ROM.

Situation:

-Moto G7 Power (XT2041)

-Brand New, just unboxed

-Bootloader Unlocked

-USB Debugging Enabled

-Device Drivers installed / working

-ADB / Fastboot works fine (device is detected and commands work fine)

-Attempts at booting TWRP (or any custom recovery) result in a quick reboot of the device, the motorola logo for a few seconds, and then I'm back to the fastboot bootloader screen

I'm currrently attempting to boot into the TWRP for Ocean:

Download TWRP for ocean

Download TWRP Open Recovery for ocean

dl.twrp.me

I have the file in my 'platform-recovery' folder, and I get a success message on the terminal when I run the commands:

fastboot boot twrp-3.4.0-1-ocean.img

I have attempted the above on a Windows 10 device, MacOS, and Ubuntu Linux, with the same results each time.

I can boot the device normally, into recovery, etc...no issues...

I feel like I'm missing something pretty simple here. Wondering if anyone has experienced similar issues or maybe I'm just being dense?

Any thoughts / suggestions will be much appreciated.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] archstar1982:
You are attempting to install ocean TWRP which it applies to XT1955 only.

They are not all same. Please be caution when you do this.

First thing you have to make sure your model number supported by TWRP. At this moment I do not see their support list for your XT2041.

XT2041 code is MOTO G8 POWER

Read this thread for your model. TWRP is currently unsupported but some unofficial you might want to read everything.

https://xdaforums.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/page-3#post-83281331
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] nighthawk676:
Thanks for this info. Not sure how I mis-identified my device to start, but appreciate the assistance here and the great reference.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Johnfoo19:
Google payments auto fill service is not working on latest build. It is not invoked when filling credit card data

I switch to Gboard and it didn't work either so It doesn't seem to be related to aosp keyboard issue.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
FWIW, there have been recent reports about problems with Google pay for certain apps (MiXplorer), so to your point this may not relate to any keyboard issues.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
question for those of you who flash roms from one rom to the next.what's the best approach to avoid the encryption issues with internal storage with these android 10 based roms and encryption mess .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] ovrwrt:
I think your best bet is to make a backup of the internal storage and then use TWRP to format all partitions first and finally format data. To avoid any issue you must remove any lockscreen setup before flashing a new ROM, otherwise you'll have issues.

So far I haven't had any problems installing these ROMs (I've tested every official one and some unofficial ones).
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Johnfoo19:
Yes, this was not rom related but on some third party app side.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
that's what i have been doing with thre roms that I have tested. Every time my data partition is being encrypted. Its happened with pixel experience plus rom on andoird 10 , revenge OS 4.0 based off of android 11, and now with evolution x 5.1.2, based off of android 11 now i am a bit concerned that with my device moto g7 power xt1955-2 , thas it will encrypt even if i ws ot install lineage as this has been the cas e with the s version of he moto g7 power model numbe xt1955-2 whihc is the international version that i got off of Amazon a long time ago .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] tyarcher79:
Having a bit of an issue with an XT1965-3 I was trying to flash with LOS. Not new to flashing, but not a load of experience either:

I unlocked the bootloader, flashed the recovery and OS and as long as the phone is connected to the PC, everything is fine. I can set it up etc. However, once I pull the USB cable, it says "Shutting down", reboots twice and then the recovery greets me with a message saying that my Android may be corrupt. The phone will stay in this screen until the battery runs out. Battery charges normally.

Tried flashing again, flashing an older version, flashing Project /e/ ROM, nothing seems to help. The device always shows the same behaviour. Couldn't find any posts elsewhere stating the same issue. I am quite surprised, as the Moto G7 Plus is supposed to be one of the friendlier devices to use with LOS.

Verified with just a charger and the phone won't stay on. Plug it into the PC and it starts normally. In recovery or bootloader mode it stays on until it runs out of juice without any cables attached. So I can pretty much rule out a hardware issue.

Maybe not related, but another oddity is that both SIM Cards show as offline and are not recognized, when I use it connected to the PC. Removing and re-inserting them did not help. Also, a white LED near the front camera is on, when it is connected to the PC.

Anybody any ideas?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
That sounds like a battery or hardware issue. The same thing happens on an old phone I use as a security camera connected to charger all the time and other devices where the battery is degraded or damaged. That being said the G7 power is a bit new to have that occur. I don't know of any way those symptoms could be caused by a bad flash or something like that but to be sure you might want to go back to stock.... If the hardware lets you do that.

For what it's worth I had been using the LOS ROM for a few months and it ran well apart from a few bugs, one or two specific to the device and others universal in LOS. In my most recent flash attempt something messed up and I've gone back to stock for the moment (more reporting to the developer about that later) but none of those issues seem as severe as yours. Confirm your hardware is good before proceeding.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] tyarcher79:
It sounds like it but I can almost certainly rule out hardware or battery issues as the phone was working just fine and dandy before the flashing attempt. But going back to stock is something I haven't yet tried.

I have a Oneplus 5T with LOS that I was able to flash without any hitches whatsoever and that

has been nothing but stellar for two weeks.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
The fact that it was working before the flash does not establish a logical connection of cause and effect between the flash process and the issue. Such perceptions may reasonably guide the formulation of troubleshooting hypotheses but they don't stand alone as proof without any evidence. The fact that everything went fine on another device actually serves more strongly as an indication of hardware issue on this device than the other way.

Again, this is not to say it could not be possible but, if you can no longer charge the device or run it without a charger even outside of the ROM, let's say at the bootloader, then the hardware is most likely broken. If there is some rare circumstance where a problem flashing could corrupt the battery charging subsystem I don't see how that could be caused in the normal process of flashing but stay tuned to see if anyone else has heard of such. Also, sd_shadow's Q&A thread for this device would be another good place to mention it because that thread is not ROM specific. Don't be fooled by the word noob in the thread name My a$$ has been saved a few times by comments in those threads. In fact it was a note in that thread which informed me of something I had to do to restore stock on this device.

This all comes back to the suggestion to restore stock which would restore all the partitions including, I would assume, the battery subsystem.

[EDIT] I was curious and did some research. There have been some cases (not specific to LOS or necessarily ROM flashing) where a device would not charge and was repaired. I cannot connect the dots between what I found and your scenario but you might want to expand your research. One suggestion stood out as being easy to do so... first you can try powering off the phone completely and connecting it to a charger to see if it charges. In any event good luck.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] tyarcher79:
I probably did not make myself clear in my original post. Sorry, English is not my primary language:

It DOES stay on until the battery runs out (which takes more than a day, which is close to the normal standby time) in recovery mode or in bootloader mode WITHOUT any cables attached and then will charge normally again. I can repeat this ad infinitum. So the phone does charge normally. It also holds a charge, just like it used to.

The phone DOES stay on when booting into LOS only as long as it is connected to a PC and only a PC. A charger will not do the trick. It needs a PC on the other end to stay on. It does not matter if it is my Windows or my Linux machine. Somehow it feels like the PC is sending some sort of PING signal that keeps the phone "alive".

So in my perception, there is a very strong connection to the ROM, because problems occur ONLY when I try to boot it into LOS without a PC attached and the problems coincide exactly with me trying to flash the new ROM.

As for putting on stock ROM, it did not work yet following the instructions laid out here (thanks for the hint!): LMSA: Lenovo's Motorola Smart Assistant (PC)

The Lenovo Software is complaining that some key information cannot be read from my device, like the very last post on that LMSA thread, where it said one needs to do a blankflash through TWRP, which I am a bit hesitant to do. I feel I am soo close...

And happy new year!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] sd_shadow:
There's a few reasons LMSA may not work, often it's if baseband is missing or doesn't match software channel.

Next step would be to try fastboot.exe to flash firmware not blankflash.

https://xdaforums.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
@tyarcher79, Thanks for the additional explanation. Unfortunately all references to charging functioning properly seem to be from before the flash so it is still not clear if the issue is reversible or if it was caused by the flash attempt. In any event that does not matter at the moment because your path to an attempted fix is the same.

Also, for what this is worth, I restore stock using RSD lite on a desktop. With the requisite drivers and ADB/fastboot and a USB 2 port this can be quite easy - if the attached USB devices can be seen by RSD Lite. This was the a$$ saving help I got from @sd_shadow's QA thread for this device - some Win 10 laptops cannot handle RSDlite so I used an old desktop.

Also, although your hope may be to get LOS running, at this point you are troubleshooting the device outside the ROM so it might be better to post elsewhere. This is not to be dismissive, other places might offer better info for your circumstances.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Johnfoo19:
Icon Packs & trebuchet

Hey guys have u found any icon packs that it is fully compatible with lineageos apps?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] triggerlord:
Not being rude or impatient, is anyone working on the drm issue? Just wondering.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Jim Barr:
I've had extremely good success with LineageOS on my Moto G7 Power. Love the weekly updates!

LineageOS is based on Android 10. Is there any plans to develop an Android 11 version of LineageOS?