yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] thatJasper:
Anyone else experiencing camera image freezing and stuttering both in Moto cam and Google cam apps

Strangely enough, after a short while Moto cam starts behaving normally and then to fix any other camera app I have to open that app, then switch to Moto cam and then back and then it all works.

It started happening since I switched from LOS 19.1 to 20.0 😕
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Heeni:
Yes, I've noticed it in the Moto cam, only since upgrading to 20.0. I don't use gapps and I've not installed any other camera app; so I can't verify anything that involves switching to another app.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kquijada:
The same thing happened to me, and it also happened to me that I updated my moto g7 power to LOS 20 and the minthegapps did not connect to the google servers.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Azukegi:
Lineage will softbrick if it does not detect vibraton is working. Vibration doesn't work after replacing charging board which causes Lineage to soft brick. Stock OS WILL boot if it doesn't detect vibrator. is there a way to bypass this in lineage? i have tried 3 different charging boards and none will make vibration work except the stock original one which has a broken chaging port.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
You on telegram? Most of the 'on the fly' work has honestly migrated there as there are channels full of bootlogo, roms, notes and tutorials.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Nope, but I should probably check it out at least for a peek if not ongoing participation. TY.

Also; video recording, which uses top and bottom mics as left and right, seems to indicate.the top Mic on my G7 Power may not be broken (and I can flash stock and bootlogo for an exchange if need be) so I've flashed the latest LOS17 build using TWRP on device, Just going through initial configuration and tests before installing/restring apps. So far so good*. Thanks again.

*... except for the issue where neither LOS camera or native gallery app can see photos saved to external SD. If Google is forcing use of com.lineageos.snap/files instead of DCIM then the camera app preview and gallery app should be able to see the photos. If that is not allowed then the IMO the ability to save photos to external SD should be removed entirely because the present configuration will certainly end up with private photos lingering on SD in locations users may not know about, or even result in lost pictures due to confusion of tapping on an image preview that is supposed open image from external SD but instead opens image from internal SD even though that image does not correspond to preview. Same thing in LOS 17 Osprey but not in LOS 16 Moto Z which uses lineage.os.snap/files with proper access to images in Camera and Gallery.

[EDIT] Also, device not cetified although using same process as for Moto X4 LOS 15. I'll have to explore that.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Moto G⁷ Power | Bootlogos™

Bootlogos & Bootanimation

Bootlogo Request ➡️ [MENTION=284775]ocean[/MENTION]request_bot

English Group ➡️ [MENTION=4581254]mg7[/MENTION]Power

Brazil Group ➡️ [MENTION=10398393]motog7[/MENTION]Brasil

Spanish Group ➡️ [MENTION=10244741]motog7power[/MENTION]ES

Moto Bootlogo Maker ➡️ https://telegra.ph/Motorola-Bootlogo-Maker-06-25

Powered by [MENTION=246450]Nemesis[/MENTION]TeamNews

https://t.me/OceanBootlogos
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I'm curious about that as well but that is not really part of LOS ROM and in fact might undesirable in LOS 17 ROMs from which bug reports are being submitted.

It was already mentioned that an official thread will be created and then we can go there for LOS dev stuff (and to a Q&A thread for other stuff). Meanwhile this thread is a fill in for official. IM0 no need to complicate this one beyond bug reporting, speaking of which...I'll be reporting a possible bug in another post.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
New flash of Sept 19 build with open gapps pico and Magisk.

2 instances of a psychedelic looking washout on the screen. As if there was an overlay causing curved colored stripes along graphic elements in the wallpaper with some color replacements. As notification shade was pulled down the coloring "overlaying" (and conforming to the wallpaper mage) would ripple - a bit like the Android Pie Easter Egg.

The first time it was corrected by reboot. The second time it seemed to occur after I was adjusting display color settings and or nightlight and was rectified by toggling Settings > Advanced > Colors to different values.

I Cannot tell for sure if that is hardware of software issue. Has anyone else seen something like that? Is this a known issue?

[EDIT] I had set the phone down with display looking proper to write this post. 10 minutes later I picked it up and turned on the display and the artifacts were back. This time it was rectified by going to settings, display, advanced, colors and toggling from Natural (which I had set it to) to Saturated. Screenshot does not capture issue. This did not happen in several days on stock. It also became evident only after the nightlight had been enabled by schedule but I have to test more to be sure of that.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Scoffy:
#27

I saw that too. Thought I was tripping! But then my device went into a constant state of reboot!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Regarding the color issue, here are some questions to flush out similarities between our circumstances, and try to determine whether this is strictly a software issue or a hardware issue which occurs during some normal software states.

Regarding the state of your device when you noticed the color issue (my answers to each question are below the question)...

What were your nightlight settings?

(scheduled to be enabled 10pm-8am).

Was nightlight enabled?

(Yes, by schedule or manually)

What was the nightlight "intensity" set to?

(lowest)

What was the "colors" setting?

(natural)

Had you ever inserted SIM/SD tray pin into top microphone hole?

(Yes, curse my fuzzy eyes and Motorola's derelict documentation).

How long have you had the device?

(1 week)

Did you ever see similar screen artifacts in stock or other ROMs.

(not in stock)

LOL, I know that's a lot of questions but any information you can add might be helpful. Thanks again for reporting this.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kramttocs:
Took the update this morning and so far so good. No reported issues and what was causing a random reboot previously isn't. :svetius:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Follow up to psychedelic screen artifacts initially reported here: https://xdaforums.com/showpost.php?p=83545821&postcount=26

The issue has now occurred while night light is disabled although I had previous been testing different settings for nightlight intensity. The issue was again rectified for the time being by changing Settings > Display > Advanced > Colors from > Natural to Saturated.Note: The default value for Colors is Boosted which I change to "Natural" after flash, but only Saturated seems to fix this color issue, then you can use either boosted or normal again.

G7PowerColorIssueBad1.jpg:

Display is in bad color state upon turning on display after it had been off for a while. In addition to many things wrong with this picture; note the purple color of the typically green Magisk icon.

View attachment 5101647

G7PowerColorIssueBad2.jpg:

Same bad color state with colors having been shifted by turning display off and on again. Swiping the notification shade (and other screen interactions) cause also the colors to band or cluster (depending on nature of wall paper) and move around creating the "psychedelic effect".

View attachment 5101649

G7PowerColorIssueNormal.jpg

Changing; Settings > Display > Advanced > Colors, from Natural to Saturated resets to proper colors until next incident.

View attachment 5101651

This occurred in a "clean" flash of ROM, Gapps, and Magisk with no other modifications made or apps of any kind installed.

I am hoping against hope that this is a software issue. [MENTION=10649603]Scoffy[/MENTION] I'm even more interested than before in any details you might provide.

[MENTION=7887589]SyberHexen[/MENTION], any thoughts?

[EDIT] New flash, initial configuration complete, practically no settings changes other than toggling off wifi, bt, etc, phone set down for 20 minutes then when powered on the color issue occurred, again to be reset by settings Colors to "saturated" then back to desired setting. That eliminates just about all possible causes related to user interaction and settings leaving - genuine ROM issue or hardware issue. Got a video, working on posting it.

[EDIT] Here is a (heavily cropped and somewhat choppy) video which shows the effect. The issue is visible in the color areas but is occurring across the whole screen. Note: video is rotated 90 degrees counter clockwise and is only of a part of the display.

https://youtu.be/MWtiAiN5KJc

[EDIT] Also,where might we be able to find stock Moto G7 Power Android 10 firmware? I'd like to test this issue in stock.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] kramttocs:
That video is crazy
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Indeed.

That particular wallpaper (the default) has shading and uses colors which demonstrate the issue well. Natural landscape images that are largely dull brown and or green with no bright colors don't show the issue as much although it is still present.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Scoffy:
#33

Back to the trippy hippie!

It was daylight and fresh off the press, so no nightlight settings. Colors would have been default. I did put the sd pusher in the headphone jack once about a year ago. I bought this new roughly two years ago. It has run just about every rom out there. I have bricked it more times than I can count.

The discoloration to me looked like overheating. I don't recall if my phone felt hot at that moment, but I did notice it being warm at times.

I flashed back to stock android 10, but once I left my house and my wifi, I noticed I had no sms, no data, nadaway.....

So I have been beating this phone down for most of the night. I went on some telegram and got some pointers, and I think I am screwed. lol

I have not gotten a sim card to work, and now I can't get any roms to work. Everything installs perfectly, but once the OS boots, it wants to shut down.

I think it has to do with overheating. Not that the phone actually is, but it thinks it is. I now get a message, "your battery will continue to charge once the phone cools off"

I tried to install UNOFFICIAL 17.1 - same thing, just rebooting. Then CR DROID, Then AOSPX, then stock again, and now stock reboots.

I will probably try a couple other things yet this am.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
As much as I appreciate the details (particularly about default settings and tray pin) and want to draw a comparative connection there is too much going on with your deice to compare to a clean flash of LOS on a new device (1 week old) having no history of bricks, overheating, or FCs. For the larger issues you are outside the range of LOS dev but...

This is not to say you might not be experiencing multiple issues, one of which could be the issue I reported, but there is no way to see that tree in the forest (as it were) on your device. One simple question remains: Have you seen the trippy color banding on any other ROM than this LOS 17 ROM?

[EDIT] [MENTION=10649603]Scoffy[/MENTION], This device specific but not ROM specific Q&A thread may be a good place to kick around some of the issue you are having.

https://xdaforums.com/g7-power/help/help-thread-2019-question-noob-friendly-t3898646

That particular thread is not heavily used yet but many of the other moto Q&A threads created by sd_shadow are good for this so it might be worth a try. I've posted there about the graphic issue to see if it occurs on other ROMS.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] googleverifysux:
https://mirrors.lolinet.com/firmware/moto/ocean/official/

or for Moto direct d/l links

https://t.me/s/MotoUpdatesTracker?q=#ocean
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Mwah! Thank you. It's been so long since I've had to flash stock (Atrix HD) that I'll have to do some studying first but that is for another thread. Thanks again.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Scoffy:
#37

Never saw the discolor like that before. Not on a phone. Maybe on a tv. It is nothing like the other guys worms.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
FYI, this is actually the only version of TWRP that seems to work. Both the official twrp-installer-3.4.0-0-ocean.zip/img and the new official twrp-installer-3.4.0-1-ocean.zip/img have no touch response when booted via ADB or on device. At one time I thought I had a working installation of twrp-3.4.0-0-ocean the device but I may not be remembering properly. In any event only TWRP-ocean-3.4.0-2.img seems to work.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
I also had the trippy screen issue about a week ago. It was during the day, so as with yours, Night Light wasn't enabled. I tried toggling every setting related to screen brightness or screen color, with no results.

After several reboots the issue went away and I haven't seen it since. Very weird one. If I see it again I'll be more methodical about recording what's going on.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thanks for sharing that information. I see it several times daily. I’ve been doing a lot of testing today. Between your report and some more observations here this is looking less like a hardware issue. Here are some of the observations.

Regarding potential thermal effects, I was flashing, backing up, and restoring for several hours and although the device never overheated it was significantly warmer than when the issue occurred in the ROM. During that time the issue never occurred in any version of TWRP or in LOS recovery or in boot loader. All of those looked fine whenever I was in them. This fairly well eliminates thermal causes.

During one test the issue occurred in a clean flash from LOS recovery of just LOS 17 with no gapps. That eliminates the presence of gaps or TWRP.

*At present I am running SyberHexen’s havoc ROM ith Gapps and will run that overnight and tomorrow to see if the issue happens there.

At one point in either the native Google play store app or the Google search, there was an overlay issue: A frame or border from the sliding drawer at the left persisted over the primary app UI until app was swiped away and reopened. Although that did not involve colors moving or being replaced both things have aspects which look like two overlays not behaving together.

I did not re-install stock.

BTW, FWIW Every time the issue has occurred on my device the only setting needed to fix it each time has been Settings > Display > Advanced > Colors >Toggle to Saturated then toggle to anything else. If that does not work for you then there may be some settings combination creating the difference in our experiences but it is clearly the same issue. Thanks again.

*[EDIT] Ruh roh. the issue has occurred in Havoc ROM as well, so I've posted there with a link to here.

[EDIT2] Have you ever stuck tray pin in top Mic?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Something wrong on ur end I'm on havoc for 2 months no issues at all
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
With all due respect you have no empirical basis on which to declare that the reported issue must be an issue on my end. That is a possiblity but is yet to be determined. Also, I did not declare that it must be a Havoc problem but rather provided evidence that it might be a software problem.

There are many ways that the states of our devices could be different (even if we flashed the same files) and yield different result in testing, and someone else confirmed the same symptoms. It is common for an issue to be noticed by some people and never by others. I once submitted an official bug report from LOS 14 (maybe even earlier in CM) that was not fixed until LOS 17 because so few people experienced it, even though it could be easily reproduced.

If this is a software issue it would be with a common component in LOS17 and Havoc. If it is an issue with the process of flashing then there is something wrong with the documented workflow or a problem with one the resources. If this is a hardware issue then it must be very specific This is not to say there could be no user error but as yet the symptoms and circumstances don't indicate that is the cause...yet.

BTW, sorry if I'm a but terse here but after 12 (my word, actually16) hours testing ROMs and providing details, your post seemed like a dismissal of the report (even though that is not what you meant). I like your post in the other thread better because it has ideas to kick around. :)
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
Are u flash on the phone or are u doing it through and app on pc like rsdlight which don't play nicely with this phone .I always do from ad card .If u use cable all time it will get lose and cann get bad connection from my experience since 2012 not saying not to but try to stay away from pc install unless nessary .
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Good advice about avoiding cables whenever possible. When I use cables I'm careful not to move them. As for Windows, point taken that many people prefer Linux but Windows has been my professional and personal milieu since before there was Windows so I'm comfortable working around those glitches. If I absolutely need Linux for something I can set that up.

In this case the issue flashing stock was that RSD light does not work well through USB on Windows 10 machines or some newer PC hardware, so for the first time in a year or two I started up a Windows 7 work rig where I used to do this stuff. That computer was able to see the device and successfully flash stock. I am presently doing the initial configuration in stock and will test to see if the issue reproduces itself.

Tip for anyone flashing stock on Moto devices or trying to unbrick them. Sd_shadow, who has many Moto Q&A threads, has a fantastic thread for this kind of stuff. I'll add a link to it shortly.

https://xdaforums.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Display color banding/moving issue

Display color banding/moving issue:

The hypothesis, partly verified, moves to the next step. This is seeming less and less like an issue of failing hardware and more like an issue of communication between hardware and software, either due to issue in ROM(s), or due to the history/legacy of TWRP installations, or due to something in TWRP 3.4.0-2.

Supporting observations below, and at the end of each line is the approximate duration of observation. Each duration is longer by orders of magnitude than it takes for the issue to first present in LOS and Havoc (seconds to 1 or 2).

The issue has not occurred in any instance of stock including:

- Initial stock Pie – 1 to 2 days

- Native update to 10 (before unlocking bootloader) – for several days

- Flash (RSDLite) installation of stock 10 (successful 1st attempt with no errors) – for half a day

Bootloader unlocked

Regarding TWRP:

- I’m fairly sure the issue did not occur in initial flash of LOS 17 using official TWRP 3.4.0-0 – one day.

- First noticed it after installing TWRP 3.4.0-2 on the LOS 17 build

- After that only TWRP 3.4.0-2 would function properly. Both; official 3.4.0-0 and the very newly released official 3.4.0-1 had no touch response when run via ADB or installed to device.

- I’m wondering why 3.4.0-2 did not make it to official; just the next version in progress or an issue with it?

Possibly relevant differences between stock on LOS/Havoc

1. Colors settings (remember that changing this setting "fixes" the issue temporarily in both LOS and Havoc)

- In stock; when the "Colors" settings is changed from any value to another the change is easily noticeable in the preview image.

- In LOS and Havoc; when the "Colors" settings is changed from any value to another the change is less noticeable in the preview image.

2. Home screen icons.

- In stock; home screen icons for native apps, in this case "Settings", assume the color set in themes/styles.

- In LOS17; home screen icons for native apps, in this case "Settings", do not change regardless of color set in themes/styles. IIRC likewise for Havoc but not 100% sure.

If Havoc also does not change the color of home-screen icons according to the themes/styles color then this is an area where it seems there could be overlay or color replacement or palette issues.

Next testing steps, aka lather rinse repeat, but smaller steps.

- Install TWRP 3.4.0-1 (if possible) and run with that and stock for a while.

- Install LOS 17 without leaving TWRP on device.

- Install LOS 17 with leaving TWRP on device.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
What version of havoc again
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
That is mentioned in Havoc thread and I'm curious to know why that may matter considering the results that were described in my posts. Also, I don't take offense to the question and I'm not above user error but really... do you think someone who tests as intensively in such a methodically planned way, and reports in that kind of well organized detail would test an older build? ;) :silly:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
I been on 3.7 and 3.9 no problems with the screen color ishue trying to figure out if I'm doing something different on install that's not allowing it to pop up or I'm just lucky
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
This issue is due to LineageOS live display hal.

It does not like the g7s Adobe color profile which causes this generally temporary distortion on the lockscreen.

To fix you go to settings > display > colors

From here toggle to a mode that fixes.

You should only need to do this after restarting your device.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Thank you. The symptoms did seem to indicate such an issue and I'm quite relieved it's not a hardware problem. Also, here are some points of clarification about when this was occurring.

- It also occurs without reboots - when the display is powered on by either power button or hand wave wake gesture. Not every time, but only when display is turned on.

- For most incidents (dozens) the lock screen was disabled and wave screen-wake gesture was enabled, so the issue was occurring at home screen rather than lock screen.

The aforementioned observations may be differences caused by differences in user configurations, which I mention here so users may be better able to identify this and distinguish it from other things.

Also, one more question: Does this speak to the no touch response issue in TWRP official versions?

In any event, I don't have to return the device and I can keep playing with the firmware. Both LOS and Havoc performed well, quite well in fact for first official versions. Thanks for the reply and for the work!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Maybe we experienced this differently due to different settings but it seems as if we are both still wondering about the steps taken during installation (which in my case may relate to the TWRP no touch). Now that functional stock is on my device and the cause of the issues is known not to be hardware, later today or tomorrow I'll do another test installation of LOS using latest official TWRP. 3.4.0-1 to see what happens.