yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Well, unless you are experiencing this issue differently than other reports (including my testing on 2 devices) you've made the point that even people familiar with custom ROM testing might loose track of private photos due to this issue.

:)

When native LOS camera is set to save to external SD; images are saved to \[external SD]\android\data\org.lineageos.snap\files. You may not be finding them because as reported, neither the camera app or the native Gallery (or some other gallery apps) are able to see the contents of that location. To access them I use app MiXplorer's file manger and image viewer or an old version of Quick Pic. The folder is treated as hidden even though it has no apparent hide attributes, eg preceding dot. In LOS16 on Moto Z that location was accessible to native camera and apps but in LOS17 it is not.

This is may be a byproduct of Google forcing images to be saved to a "secure" location which is part of the camera app installation and not shared by other apps in the manner that DCIM is, but the implementation of this in LOS is faulty.

Here is the relevant discussion from the LOS 17 Osprey thread. At the link to git someone claims that this is by design but that could only apply to the intention to save pictures in that location and not to the mess that leaves them there unbeknownst to user.

https://xdaforums.com/showpost.php?p=83172083&postcount=315

https://xdaforums.com/showpost.php?p=83172523&postcount=316
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Bananicorn:
Heya, could you perhaps add known issues and known working features to the OP?

It is good to keep track of the state of the phone and helps people who are considering buying this phone to know whether it is a good choice without reading through the whole thread. :)
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
FYI, this is a development thread where the purpose is to test and report bugs in LOS17 for this device.

If you want to get into the nitty gritty of the bug reporting:

- Here is a link to reported issues at LOS official problem tracking system https://gitlab.com/groups/LineageOS/issues/-/issues

- Here is a link to recent changes https://download.lineageos.org/ocean/changes/

- You might be able to find the developer on telegram and participate there.

Discussion about the device or ROM features in general is more appropriately held in General section of forums. Here is a good general thread for Moto G7 Power https://xdaforums.com/g7-power/help/help-thread-2019-question-noob-friendly-t3898646.

[EDIT] [MENTION=9644613]Bananicorn[/MENTION], just to add:

This ROM went official only recently so there is not a lot of bug reporting history but there is some discussion in this thread about a few issues. In particular a graphics issue related to Live Display and a few issues that are not device specific, but none of them have been deal-breakers at least in my usage case. You can learn more about those by reviewing this thread.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] redspeed:
Havent ran custom roms in a very long time but was able to install this one ok. Not sure what may be the issue but its having problems installing some apps from the store like DJI Fly which I use for my drone. The install fails, not sure if its checking for a specific model and refuses to install?

Also, is there a good working GCAM port that works on this rom? The stock ones I had been using all arent working for me. Is there also a way to get back the scrolling screenshot editor from stock too? Thanks!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I'm still using the build from a few weeks ago but have had no problems like that. Could be Play Store, Play services or account issue. If not in actual clean the flash then clean flash, if in actual clean flash then factory reset. Less drastically, you could delete the account or reset the app data for a variety of Google Apps and services.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Pio_CPD100:
I was thinking about buying a moto g7 power and flashing this ROM on it. Can anyone here confirm that volte works on t-mobile? Thanks!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] roadkill42:
I believe so I'm on cc which runs on T-Mobile but T-Mobile might b different for its acutle people
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] redspeed:
I think I figured out what happened. I tried a clean flash again but I had the same issues and would get google play services errors popping up. I was trying to flash gapps right after flashing the rom which wasn't working, only the rom would install so it would boot up without gapps installed. I then did a clean install and then rebooted the recovery which let me install gapps so both were installed on the first boot

---------- Post added at 09:18 PM ---------- Previous post was at 09:13 PM ----------

I'm on a T-Mobile MVNO and there's a VoLTE toggle in network settings that it lets me enable and calls seem to work with it
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Pio_CPD100:
It seems like VoLTE may not be working for T-Mobile according to this issue filed on gitlab: https://gitlab.com/LineageOS/issues/android/-/issues/2596#notes

When you make a call does the icon next to the signal strength switch over to 3G or HSPA? If so, VoLTE isn't working. If the icon still displays LTE then it is working. You'll probably have to disable WiFi to see the icon for the mobile data connection.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] redspeed:
LTE stays in the status bar when I make calls with WiFi disabled at home. I live in an area that really only gets the extended range LTE signal which made me think VoLTE is working. I'm running the latest nightly too 10/10/20 I believe.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Pio_CPD100:
Okay, good to know. Thank you!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] arnoldpalmernold:
I have experienced the same exact issue on the latest LineageOS build (10/17) and the most recent release of CrDroid. Strangely this issue is not present on the latest release of Resurrection Remix. Thanks so much for sharing this, as I thought I was going insane.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
I've found that Party Mode (the color bug) only occurs when I have the Night Light feature enabled/scheduled. Mine is permanently off now and Party Mode is a thing of the past.

Side question: has anyone managed to test WiFi calling yet with ATT? I haven't had a scenario where I've needed it yet, so no chance to test.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
FWIW, I do use Night Light on a set schedule but as long Live Display remains disabled then party mode does not occur.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] arnoldpalmernold:
Unfortunately, I experienced party mode (under Lineage and CrDroid) even when Live Display was disabled, and when Night Light was off as well. I always disable features which I never intend on using. Resurrection Remix is the only one I've tried where the issue does not occur. As far as WiFi calling goes, AT&T is known for not allowing unlocked and rooted devices to make use of WiFi calling (and VoLTE for that matter).
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] AAccount:
Does android auto work on this rom? Tried searching this thread but didn't find an answer. Also tried searching threads for other roms but didn't find much.

I'll answer my own question: YES. It works! Plugged it into my car, went through the "do you accept" stuff and it came up on the head unit.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] RyukRuse:
Is anyone else having problems when restoring the backup of the google account? The message appears that the Android settings fail continuously ... I had this problem in Resurrection Remix too, so I am suspicious of opengapps.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
No problem here with open gapps pico in any of several tests flashes and running the device for several weeks, although I never restore the Google account, but rather login anew and reconfigure then install apps. I've heard of that kind of error with dirty flashing or bad gapps packages but there could just as well be something wrong with the (undescribed) process or material you are using. If you're not using pico give that one a try... in a clean flash without using any third-party stuff to restore the account. I'm not railing against third-party backups, in fact I use Titanium Backup quite heavily... which is why I know some limitations and one thing I never touch with it or even with Google's native backup and restore features is the account itself.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] luigi.gianizelli:
DTV is not working

I installed this rom on my Motorola G7 Power along with Gapps' TVstock package.. doesn't work. Lineage crashes and suggests to format data. I need this package because my phone has DTV. Can someone help me? :confused::confused:
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Seems as if you may be missing some prerequisites or not following all steps in the process. Carefully review the instructions and the resources you are using.

If your resources and process are all in order and you are truly clean flashing, then for diagnostic purposes it might be informative to try with opengapps Pico - if that works then you know the problem is with gaps TV.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
In Sept 24 build with OpenGapps Pico and Magisk stable I'm finally gathering some logs for a few previously mentioned general issues such as; no spell check and camera save to SD but there is one particular glitch I've only seen on this device in this ROM and it might be a significant glitch.

Missed alarms.

From the native alarm clock app or from other apps which invoke alarms, or the alarm for voicemail - the alarm will not sound until the screen is turned on.

This does not happen all the time and I've not yet figured out how to force it to occur but it has occurred in each of the last two or three builds enough times to make the alarms in the clock app undependable. I will continue to try to reproduce and log it.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] Greek2me:
Thanks for all of your in-depth diagnostics work and detailed reports, Iron.

I'm not sure if this has been reported yet, but I've found a way to reliably trigger the Party Mode bug, and a way to reliably fix it temporarily.

To trigger party mode:

Turn on "Battery Saver".

Lock the screen using the power button.

Unlock the screen.

Phone should now be in Party Mode. (color glitches)

To fix Party Mode, until it's triggered again:

Set Display-->Colors to "Saturated". Party Mode will immediately cease.

Hopefully this information is able to point someone in the right direction!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] redspeed:
The only bug Ive came across so far is copyrighted movies seem to cause it to reboot immediately when trying to play them. Tried Vudu, Youtube and Movies Anywhere and Im not able to play any movies I own. Not sure if this only affects this phone or its a Lineage issue? Im not rooted right now.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
There has been no mention of such issues in this thread (or a few other lineage OS 17 threads that I follow) nor are there any LOS tickets mentioning copyright (https://gitlab.com/groups/LineageOS/issues/). That's not to say it could not be a ROM issue but you'd have to provide details and or logs captured in a clean flash of latest build to substantiate the claim and move it along unless others have also experienced it and can speak to it.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Something similar is be occurring on my device with T-Mobile US prepaid.

- Not only does the data connection switch from LTE to H (+) when a call is made, but also when the device is set to LTE (LTE only) then data is OK but no calls can be made.

- In phone settings GSM options a SIM error is reported although there are settings in place that would only be there if there is a SIM present.

- When switched back to any mode which includes WCDMA (3G) then calls can be made and the icon switch from LTE to H returns.

- On a different device (MotoZ) running LOS 15 but with an identical type of SIM card and service, the data connection remains on LTE as it should when a call is made.

So, this seems to indicate that the problem is indeed in the ROM. Also, for what this observation is worth; I’ve been running the October 24 build in which the default mobile network setting is LTE/CDMA/EvDo/GSM/WCDMA which appears as “Global” but in the previous build the global option was (as you or someone else previously described) GSM/WCDMA/LTE (PRL). If I was not testing default settings I would use GSM/WCDMA/LTE. In a clean flash of the 10/31 build there are several more network types in that list, several of which are called “global” after being selected, but the same issue with no calls on "LTE only" occurs.

For me the issue is not just Volte but that I cannot make calls at all when using LTE only. In a few days I might have a chance to test in a place where there is only LTE service which may be diagnostically informative.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I’m not a coder or but from a legacy of PC workstation building it’s my pleasure to test (depending on how bad things are, LOL), especially since there are some things to fix.

As to Party Mode, it is quite helpful to have a way to reliably induce the issue which seems to be the tricky part in this case because different usage scenarios result in different frequencies of occurrence. Logging that would be the crux of any bug report. IIRC Syberhexen spoke to this but it may still be worth creating a bug report. Also, in the changelog there is a new commit related to Livedisplay. So since live display is part of the issue (at least in my case) this may or may not be of note (but it also might not be related): https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/290653/

Maybe after that build comes out I’ll see if I can reproduce the issue as you describe and log it.

--------------------

Meanwhile, new observations about some previously mentioned stuff.

- The aforementioned issue in previous post regarding LTE which is of high order IMO.

- Missing spell check. This is not just a problem with the native AOSP import but also impacts the spellcheck used by G board and hacker’s keyboard.

I logged some of these things but the LTE issue jumped in front and that one is worth testing immediately after flashing so I’ll see if I can log a few of these things at once in the next build.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Bug report: https://gitlab.com/LineageOS/issues/android/-/issues/2742

Logs are at the gitlab ticket.

When preferred network type set to LTE no calls can be made. When set to LTE/CDMA/EvDo/GSM/WCDMA data switches from LTE to H(+) during calls.

Expected Behavior

1) When Preferred Network Type is set to LTE (LTE only) it should be possible to make calls and when doing so data connection should persist as LTE.

2) When Preferred Network Type is set to default LTE/CDMA/EvDo/GSM/WCDMA (or GSM/WCDMA/LTE) it should be possible to make calls and when doing so data connection should persist as LTE. (Same as above but they exhibit different symptoms of the problem, described below)

Current Behavior

1) The LTE data connection persists but the call immediately fails and in this state some (but not all) SIM related settings report a general error.

2) Calls can be made and the data connection switches from LTE to H(+) for the duration of the call and back to LTE after.

- The same T-mobile US prepaid SIM and another SIM of supposedly identical configuration exhibit the expected behavior on other devices including Moto Z (Griffin) running LOS15 and Moto G(8) Power (Sofia) running Moto stock Android 10.

- Both SIMS exhibit the issue in the Moto G7 Power ocean device running LOS 17.

Steps to Reproduce

1. Confirm or set Preferred Network Type to LTE

2. Place a call

3. Observe "current behavior" #1 above, unable to make call.

4. Confirm or set Preferred Network Type to LTE/CDMA/EvDo/GSM/WCDMA or GSM/WCDMA/LTE)

5.Place a call

6. Observe "current behavior" #2 above, data switched from LTE to H for duration of call

Note: This may also be perceived as a Volte issue by people whose usage scenario would not encounter the call failure under LTE. It might even be perceived as missing reminders or alarms by some people who thought they had good service but had only a strong LTE-only data signal which was unable (due to this issue) to receive voicemail or text message notifications because it is not actually on the cell network - just data. In any event T-mobile US prepaid users should be able to reproduce this as described. If so please do add some details and logs to the ticket. https://gitlab.com/LineageOS/issues/android/-/issues/2742.

[MENTION=7887589]SyberHexen[/MENTION], This is a bit more serious than some of the other Ocean LOS 17.1 issues I've encountered and read about so I've flagged you here.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] triggerlord:
This ROM has been working fine for me.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Who's your carrier?

Can you restock and make sure you run the commands

fastboot erase modemst1

fastboot erase modemst2

fastboot erase DDR

It appears your VoLTE provision did not carry over from stock.

Make sure all is working in stock and backup EFS & persist in twrp.

Then install rom again and report back.

If still not working after initial setup restore efs / persist backups
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
T-mobile US prepaid, 2 different SIMS of same type confirmed to be capable of this on other devices.

Also, A comment in the gitlab ticket mentioned this:

"it may require that proper Volte profile is available/loaded for your carrier as is the case of my OnePlus 6T with SFR in France. For the record even on stock OOS it does work on my 6T out of the box and I have to load the proper Volte profile."

Can you confirm that this device has such a profile or if that is even significant? If it had no profile but required one it seems there would be no need to proceed, but your suggestions imply that there is a profile or that it does not matter? Either way; I'm headed towards a restoration of stock.

BTW: After I had been testing Havoc and LOS back and forth some weeks ago I restored stock via RSD before this round of testing, and someone else mentioned the same issue, so I have doubts that something did break from stock to LOS but this is why we test. Thanks for the above suggestions. Depending on what happens in stock I'll try them, although I may not have a chance to do this for a week or 2.

On a possibly related note: The presently configured device is capable of sending and receiving MSS without any data connection. I don't know if that informs the LTE issue but it is very nice.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Regarding the Tmobile LTE switching, there was an existing ticket so to increase the chances of gathering more useful information I'm folding the ticket I created into the existing one.here: https://gitlab.com/LineageOS/issues/android/-/issues/2596

OT:

I'd just like to make it clear that these bug reports are not a criticism of the ROM or the developers, in fact the opposite. I would not be putting this much time and serious testing into this if I was not glad that there is LOS dev for this particular, big-a$$ battery device.

Also, an ironic side note: My first serious dip into LOS/CM was in 2013, precipitated by a failure of AT&T to provide proper LTE service in their own branded devices (Moto Atrix HD). With the help of a Motorola technician it was determined that there was an issue in the AT&T modems in the cell towers which was known to AT&T and which in turn caused the "Modem Fastdormancy Monitor Service" on the device to hang or lose connection resulting in missed voicemail notifications and other issues. Modem Fastdormancy Monitor Service was responsible for the LTE/GSM switching we are talking about today, although I suspect the landscape of infrastructure, hardware and firmware has changed considerably since then. It's just amusing to have circled back to something so similar many years later. Anyhow back on topic

DONE OT

The next bug report will be for spell check. Has anybody seen the native AOSP red underline spell check function correctly on this device/ROM with any keyboard that uses the native spell checker. If it would be helpful to know the various language and input settings on the device and to see a screenshot of a red underlined misspelled word that has been selected so the drop-down list of possible replacements is visible, as in this screenshot from another device.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] triggerlord:
Also I've gotten it to pass safetynet!
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Cool. Does it also indicate "Certified" in Play store > Settings > Play Protect Certification?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] ovrwrt:
Is the "Party Mode" bug already fixed? I saw that the removal of the apparent cause was already merged a few days ago. I'm currently using PE+, but I think its too Google-centric to be safe to use. I hope we don't have this error anymore.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
Seems to be halfway fixed but the range of experience.with this is so variable I can't be sure.

I saw the commit you are referring to and was wondering about this as well. I usually experience the party mode bug only once or twice when turning on the display during the period of time when when I'm placing initial settings after a new flash, then and it never occurs again after I disable live display.

With the latest build (which contains that commit) a sort of halfway version of the party mode bug occurred and it corrected itself. I had flashed and was placing settings as usual but had not yet gotten to disabling live display. Then one time when I powered on the display the party mode bug was in effect on the lock screen but it reverted to normal when the device was unlocked. That is a new behavior for my device. In previous instances when the bug was invoked it would not be corrected until changing the color setting.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] triggerlord:
Yes.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] ovrwrt:
I see you're using LineageOS + MicroG. How did you install Google Play? Does this overrides the MicroG packages? I would love to have only the Play Store without the Play services and libraries and if that's possible please let me know how.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] SyberHexen:
By chance was there any change with restocking and re-provisioning the VoLTE in stock?
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] IronTechmonkey:
I'm eager to test this but won't have a chance to restore stock for a while, perhaps a week or two when I have access to a computer on which I can run RSDlite. This is not procrastination or a push-off. If this could be fixed or if cause could be determined, it would be one of the most significant improvements to my cell phone usage for some time. I'm chomping at the bit and will test stock as soon as possible. Thanks.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] mrk2815:
dont know how this works.since there is official lineage 17.1 for the device ,will then there be other official future version of lineage available for the device down the road.
[Moto G7 Power ROMs, Kernels, Recoveries, & Other D] triggerlord:
I have noticed one problem. Prime video plays fine but of I try to use Philo it just reboots when I play something.