yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Java shin on xda has got a fix for it now using and commands and push I have the file and instructions for it if u interested
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Much appreciated. I'm tempted but will play it safe and continue to test the latest official builds. Thanks for offering and sharing the info about it. :good:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] zapjb:
I had the no-touch TWRP dealy bob. Ended up using PBRP instead.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I have cause to believe that if I stay with the latest TWRP (not installing others after it) this may not occur, but if it does occur again I may follow your lead in that regard. Thanks for the info.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Yea the pbrp is nice no touch ishue
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Does touch not work for you on twrp 3.4.0-1 official?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
In first flash (LOS17) TWRP official 3.4.0-0 was used and worked fine.

This was before release of official TWRP 3.4.0-1

On next flash (LOS17) unofficial TWRP 3.4.0-2 was used and worked fine.

This was also before release of official TWRP 3.4.0-1

On next flash (LOS17) TWRP official 3.4.0-1 had been release so it was used but there was no touch response.

After that; any installation of TWRP official 3.4.0-1 or 3.4.0-0 resulted in no-touch response in TWRP (via ADB or on device) and only TWRP unofficial 3.4.0-2 functioned properly.

Since TWRP official 3.4.0-0 seemed OK on first flash (before 3.4.0-2 was installed) and now the device is back on stock, I will flash LOS17 using 3.4.0-1 to see what happens unless you recommend otherwise.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Would the twrp with the karrot one from tellagtam work for him .I foud out certion roms will not work right with twrp but the one with karrot always worked in tellagtam group
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
FYI, [Repeating from my report, again ;)]

- There was no issue with official TWRP until after the unofficial one was installed and then official was installed again.

- This is not to blame the unofficial one but this indicates that the issue is not likely with official TWRP,

- The 2 most likely remaining culprits are: 1) the unofficial TWRP or 2) The order of events.

I'll make a note that another TWRP version exists (thank you) but installing yet another unofficial version in order to fix something that might not be broken in a situation where installing multiple versions might have caused the problem does not seem advisable ATM.

Let's find out what's broken or if it is even still broken first. Now that stock is on the device, whatever was jamming TWRP might have been cleared so the next test is to install LOS17 with latest official from copy partitions through the entire recommended process.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
It is a driver ishue that is causing twrp to freeze on touch even on zto k pie it would freeze had to reboot in to recovery several times then it would work or boot in to fastboot several times then it would work .I only saying on what my experience was on this phone for the past six months .And from the test I have done some roms don't play right with twrp .From what I have been reading this piculiar phone twrp is strange and some kernals that java shen makes will fix the touch .You right about software it's in the kernel driver .That is what I have learned and tested now the color glitch I never experienced it
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
This kernel I used fixed the touch also could many affect the color ishue I'm just trying to figure it out to this is what I did have shen has a channel here in xda to but can't remember any more then that .I know at the tellagram group they one who came up with the soultion moto g7 power deccussion group stop in and ask away can't hurt
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
TWRP 3.4.0-1-ocean.img is working fine now, although while testing I may have formatted or wiped something I should not have, and am now experiencing the "no system installed" issue after ROM flash when rebooting back to recovery. This must be operator error on my part. I worked through it once before but forgot what I did.

[EDIT]

Here is how I worked thought the no-system installed issue (most likely an issue with my process, not the resources).

one or 2 things I don't recall

install LOS via sideload

reboot to LOS recovery

reboot to bootloader

fastboot flash boot

fastboot boot

flash ROM and TWRP

reboot to recovery

flash gapps and Magisk

reboot to functional LOS

Lastly, now that we know that the visual effects are not a hardware or serious software issue, IMO it looks much better than the Android 10 Easter egg.

+1 for a Trippy Hippy Easter egg
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
I found it best to flash ROM first don't mater slot cause it installs on inactive slot then reboot ignore no op in stalled cause u on slot that u started the install on .After reboot turn on USB debug then fastboot twrp flash gaps and magisk if u want reboot then fastboit twrp flash twrp but before magisk me bad but that's how I do it no problems
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
This is where there was operator error on my part. In my flashing work folder there is an older version of TWRP, and I remember reading somewhere that older versions may have touch issue. I don’t remember installing it but that must have been the reason for the no touch issues. AFter going stock via RSD and now back to LOS No problems now on official 3.4.0-1.

The process I used got me back to LOS OK but yours may be more efficient so if things get scrambled again I may try it. As long as I stay within LOS this seems not to be an issue so just did a new flash like so:

TWRP Official 3.4.0.1 is already installed on device.

- Boot to recovery on device

- Install LOS17 and TWRP Official 3.4.0.1

- Reboot to recovery

- Install Gapps and Magisk.

To your point about the different experience; before flashing just now I had run a clean install for eight or 12 hours with one or two hours of use and did not experience the graphics issue. Then immediately after a reboot it occurred and not long thereafter occurred again when I opened the dialer. I’m going to play with trying to find a way to save some steps when changing the colors setting, perhaps with Tasker or an activity exposed by Nova launcher so that wen it occurs there is a one-tap fix.

Also, I may have found a bug with phone speaker/headset but will describe that in a separate post shortly.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Handset mode vs. Loudpeaker mode

Handset mode vs. Loudpeaker mode. Loudspeaker wins

For all incoming and of outgoing calls the audio goes to the loudspeaker but the speaker icon is un-highlighted indicating handset mode.

.

When speaker button is tapped and becomes highlighted indicating loudspeaker mode the call audio goes to handset mode for two or three seconds and then fades back to loudspeaker mode.

When speaker button is tapped again and becomes un-highlighted indicating handset mode the audio goes to loudspeaker mode immediately.

When headset is attached the toggle between headset mod and loudspeaker mode functions as expect.

So the only time a call is ever in handset mode is for those few seconds when loudspeaker mode has been disabled. I hope Not to be missing some new setting hat I should have noticed or something like that.

[MENTION=7887589]SyberHexen[/MENTION], et al; is this a known issue? If not I can log it but FWIW now: this is in a clean flash with no apps installed using T-mobile US Prepaid service and occurs under all combinations of settings I’ve tried in the phone app.

[EDIT] My speaker issue bears some resemblance to this issue reported from a different device at gitlab, the commonality being; the sound is coming out of the wrong place (but other aspect of the issues differ). Not a great match but the best I can find.

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

[EDIT2] Initially occurred in clean flash immediately after initial configuration but then seemingly fixed by reboot, which is another similarity to that ticket.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] imarsh72:
G7 power only has one speaker, it just reduces the volume on voice calls, however you probably still have an issue as indicated by the speaker button being highlighted or not here are the specs

https://support.motorola.com/us/en/...oto-g-family/moto-g7-power/documents/MS137728
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
:rolleyes: Soooooo... another person doubting that an issue could be real just because they have not witnessed it. Well, OK I can remain good-natured while explaining it... one more time, Same story, different words, I hope more obvious:

I never mentioned 2 speakers. I referred to 2 different "modes", and I am familiar with the hardware and the expected behavior of the speaker and volume management during a phone call in LOS17 and stock on this device (and other Motos with one speaker). What I observed was not the expected behavior. This is not a matter of subtle effect or errant observation. The problem was obvious immediately upon toggling the mode back and forth - there was no back and forth - it was the same - either way the volume was in loudspeaker mode which is too loud to be put near the ear, In fact when it caught me by surprise it was painful - that is how I noticed it. This is not something that manipulating the volume sliders can compensate for. It was a unique behavior which occurred in a clean flash of LOS17 shortly after initial config but had not occurred in previous flash of same build,Clearly there was something wrong but I missed my chance to log it as a reboot rectified it.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] dacoolboi:
slot_b missing then slot_a

I encountered an error when I flashed twrp-3.4.0-1-ocean.img

Basically it said that slot_b was missing and when it was writing to it, the bootloader had an error like the image was not signed or corrupt.

Lineage OS did install properly though.

I decided to redo the setup and the second time through, it was slot_a that was missing and the same bootloader message of the image not signed or was corrupt.

Lineage OS, again, installed properly.

I was wondering if this is intentional?

I mean the OS installed properly and everything except for the weird color glitch which was fixed by turning LiveDisplay off.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Did I flash the copy part there is a zip u can flash to get rid of the color glich
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I'm now running the Sept 26 build (for a few hours) and have not yet seen the color glitch. If it occurs, where can the fix zip be obtained?. Thanks
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] dacoolboi:
If you're talking about flashing the copy-partitions, I did that right after flash booting TWRP. It did not fix the color-issue, turning off LiveDisplay did.

I basically just followed the LineageOS guide in chronological order, am I not supposed to do that? Sorry I'm new to this lol.

I was just wondering what the slot_b error during the TWRP flash boot process was when it said that the image (twrp-3.4.0-1-ocean.img) was not signed/corrupted. In my previous post, during my second clean install, the same error occurred for slot_a.

---------- Post added at 05:25 AM ---------- Previous post was at 05:22 AM ----------

I'm actually running the Sept 26 build as well, the color glitch definitely happened for me, but it fixed itself if you turn off LiveDisplay. I think the zip roadkill is referring to is the copy-partition zip.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
It has not happened in this build for me yet but it does seem to occur less when the lock-screen is being used (which is implied by developer's description a few pages back). Will see about tomorrow.

Could be but as minimal as the wording was the words did say..."there is a zip u can flash to get rid of the color glich"
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
I have the color glitch zip if interested let me know
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
The issue has not occurred overnight so I may now be using a happy combination of settings in which the issue does not occur, although the last time I said something like that in a previous flash the issue occurred the next time I picked up the device. LOL. Indeed I'd like to have that zip just in case [and I would not redistribute]. Do you know if that fix is in the pipe to be added to the ROM?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Don't know all it dose is disabled the live display so if u turn it off it should not happen
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
In that case; offer appreciated but I would rather do that manually. Also perhaps more importantly, in my case disabling live display does not to prevent the glitch as I had Live display disabled through most of my previous testing and the issue still occurred. Rather hilariously just after I implied I might jinx myself, the glitch has now occurred for the first time in this flash, once when turning display. once and again while changing lock screen settings. And another test just now: After resetting the colors with Settings > Display > Advanced > Colors, I disabled everything in the Display. The glitch occurred a few moments later when the display was powered on.

Aha, There is something odd about the interaction between quick tiles and display settings. The last thing I did before this morning's color glitch issues was to configure and test quick tiles for first time since flash yesterday and as I test quick tiles for the purpose of this writing the glitch is occurring almost every time the display is powered on,

- Long press of ambient display does go to display settings but not the ambient display settings leaving user to expand advanced and scroll to ambient [which normal] but there is no Ambient display toggle, only the toggles for wave and touch to wake. Ambient can however be toggled from the Quick Tile which in turn greys out the 2 gesture settings.

- Long press of Live Display Quick Tile does nothing (except return to whatever was on display). It should at least go to display settings and at best go into live display section.

The Ambient Display Quick tile long press behavior inefficient but familiar or expected..

The Live display is definitely not expected.

So I'll be testing to see if interaction with Live Display quick tile (or ambient display quick tile) is factor, perhaps not a root cause of the issue but a factor in making the issue present.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] dacoolboi:
TWRP question

I have a question, when you flash boot TWRP, it doesn't actually install TWRP, does it?

Does it maybe instead just boot into the TWRP image located on the host machine?

If that is true, then the only way to boot back into TWRP would be to actually run the fastboot command and select the TWRP image again from the host machine right?

Unless, is TWRP deleted after sideloading the ROM?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
To temp boot to twrp u need the img in ur adb folder phone in fastboot then in terminal u type fastboot boot twrp.img or whatever it named that is is only temp now u can get the zip have it on ur ext card and flash the zip will in fastboot booted twrp then it's perm also side load it or push and another way I forgot
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] dacoolboi:
Thank you for explanation.

Do you happen to know the command to flash TWRP after temp booting it?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
If you are coming from stock or anything except lineage OS 17 on this device I strongly recommend following the official instructions which are linked in the original post of this thread. The commands are described there as well and I'll leave it up to you to find them. I do that out of concern because your questions seem to indicate following only part of the process or following it in the wrong order. If I am mistaken please take no offense, this is just an excess of caution. Also this is not a criticism of the advice you've received which is accurate but focused on one part of the process.

Once you have LOS running properly on the device you can flash more freely and without having to connect to a computer but as Bane said in The Dark Knight Rises, "Now is not the time for fear. That comes later."

:)
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] dacoolboi:
Lol thanks for that, I actually already managed to get Lineage OS working on the G7 Power, just had a really weird error when flashing TWRP but everything after was fine.

The error has really been bugging me and was something along the lines of: unable to write to slot_b (another time it was slot_a) image not signed or corrupt.

This error has been bugging me though so I was thinking maybe to boot into TWRP through the image then flash TWRP, but I don't happen to know how to flash TWRP after booting into TWRP.

I know it's a bit strange, but I figured I'd ask now so maybe in the future I would be able to avoid the error.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thanks for that advice. Since I posted yesterday I have not changed live display settings via tile or in Settings > Display, and the graphics glitch has not occurred once. It's nice to know it can be avoided and I don't use live display anyhow. Fortunately the color change component of the old Live Display (Display Mode = Day/Night) was separated into ""Night Light" which functions properly without causing the glitch. Thanks again.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] KHSebastian:
This is working very well, except when I am on a phone call, my mic is just barely picking up audio. Nobody can hear me. I tried leaving myself a voicemail on my Google Voice number, and I could not hear myself.

If I make a call from Hangouts, that works fine, so it seems to be specific to phone calls. Has anybody had this problem / does anybody have any suggestions? Any help is appreciated. Thank you!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I've noticed that speakerphone calls are sometimes muffled or garbled, (my voice at other end) particularly after toggling back and forth. between loudspeaker mode and handset mode". Additionally I experienced this one time-glitch which might or might not be related lthough it did not occur after reboot.https://xdaforums.com/showpost.php?p=83578849&postcount=66.

At first I thought I had damaged the top microphone by mistakenly inserting the SD/SIM tray eject pin but FWIW, you can use video recording as a crude test of both microphones by recording in landscape while alternately covering left/top mic and right/bottom mic then listening to the playback on headphones. In my case there could be some minor damage to some part of the top mic but the video test sounds OK so perhaps there is a software issue here.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] KHSebastian:
Hm. I tried this, and both mics seem to be working, so I think it must be something software / configuration related.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
My thoughts as well. I'll always have a small doubt regarding the mic hardware on my devices but potential damage there is rendered not (primary) factor because the behavior seems to change when toggling speaker mode. As to software, in my scenario I see 2 testing points to work through:

1.Call recording apps can impact speaker phone performance.

Prior to the occurrence of the previously reported loudspeaker mode glitch (not the one we shared moment) I had been testing the a call recorder app from Play Store (unchained version available at XDA labs). That particular glitch occurred after the app was uninstalled but did not occur after reboot or re-flash or restore of previous installation.

While this speakerphone glitch (the one which we both experienced) occurred, the device was running skvalex's call recorder app which seemed to be working fine.

I do somewhat suspect ACallrecorder in the first glitch but don't suspect skvalex's call recorder in the second glitch. This should be easy to test for during the next flash by making a few speakerphone calls immediately after initial configuration but before installing other stuff.

2. Stock versus LOS:

If the issue is reproduced in a clean flash of LOS17 as described above then I'd be curious about what happens in stock. This is a more ambitious and therefore less likely to occur test as it requires dragging out a computer that can run RSDlite.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
There were only a few general commits and one kernel specific commit in the recent October 3rd build so I'm skipping it but, lined up for the next build are a whole bunch of kernel and or device specific commits. Hexen has been a busy bee. Meanwhile, here are 3 non device-specific issues which have been around for a while, which I've seen variations of in LOS17 Osprey, and for which I'm preparing reports for the LOS gitlab

1. Ambient Display setting in wrong place in settings tree and is called by different name than its corresponding quick tile.

Settings > Display > Advanced > Lock screen display > (When to show) new Notifications.

This is an improvement over an earlier version of LOS17 Osprey which had no such a setting at all, but this leaves a mismatch between name of Quick Tile (Ambient Display) and the name of setting (New notifications) which do the same thing.

Additionally the setting is a top level toggle for hand wave and pick up to wake gestures which also applies when device is not locked so why have them in lock screen settings?

2. No spell check.

Autocorrect functions okay but there is no spell check (red underline).

3. Camera & gallery

Neither the native LOS camera preview or gallery is able to see the location to which the camera saves photos on external SD. Also, when there are any photos in the internal SD card save location then when user taps on preview (which seems to be photo saved to external SD card) instead of opening that photo the latest photo on internal SD will be opened. This is problematic because the user may never know that private photos are lingering on the external SD card.One of two things should be done.

- Grant LOS proper access to that location. I know that was done in LOS 16. I hope that still can be done.

or

- If the native apps cannot access that location then remove the capability of camera to save saving photos there.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
That camera bug is even worse than you write actually. When the camera app is set to use the SD card, photos are never even saved in the first place.

Also, out of curiosity, has anyone tried making an emergency call yet using this ROM? I had to make one using Electimon's unofficial version several months ago, and the operator could barely hear me because of some extreme echo.