yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Starting with the simplest thing even though it does not necessarily seem to be a suspect; make sure this setting is disabled:

Settings > LiveDisplay > Automatic outdoor mode = disabled.

FYI That log was inaccessible (removed?) and you've provided no details about device/ROM (model #/build date) but FWIW: in LOS April 10 Athene (and LOS April 21 Peregrine and LOS March 31 Osprey) autobrightness (adaptive brightness) is working properly for me via any available toggle: Eg: In Settings > Display, or via QT/Status Bar, or my own Tasker utility (which incidentally shows actual numeric brightness value and or autobrightness status as confirmation). In all cases, not only does autobrightness function correctly but whatever state it has been changed to via one method is then reflected in the other methods as expected.

That all being said, someone did mention something similar today in the Osprey LOS thread: https://xdaforums.com/showpost.php?p=76334057&postcount=5841. Perhaps there is some combination of settings or narrow usage case in which this occurs or perhaps is is due to 3rd party factors such as dirty flash, presence of non LOS system modes, or past history of Substratum on device.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] theredbaron1834:
Display mode is set to "disable all adjustments".

Rom is this one, not sure what release. Model is a moto G4 none plus (Moto G4 XT1625).

Since it is pretty uncommon it seems, will try a clean flash this weekend, see if i can get past it I guess.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
OK, that eliminates "Outdoor mode" as possible factor.

"This one" does not identify which build you are using. ;)

Yep. FWIW I've never seen this on any of 3 devices so, good odds for clean flash (but of course no promises).
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] theredbaron1834:
I don't have access to the phone atm, so cant look :). I know it is post the april fools release, but not sure what one.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] TLastPrism:
Sometimes after pressing the power off/on button the phone take 5 seconds to wake up the screen... This delay is annoying af... And sometimes the device just freezes and reboot from nowhere... Why this happens? Has a fix? Using 10/04 build though it happens in all other builds...
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Yes, that lag to screen on is incredibly annoying. There is a Jira ticket for it here: https://jira.lineageos.org/browse/BUGBASH-1115. You can review the notes in that ticket and add to them. Logs in particular are helpful.

There may be a Jira ticket(s) for this as well. You can search this thread or search Jira to find it (them).
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Slayer5934:
I'm getting random reboots on this rom, any advice would be good. I'd be glad to upload a "crash report" to help the devs if I'm instructed on where to find them.

Device is XT1625, no custom kernel.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Unfamiliarity with capturing logs excepted, following the trail indicated in last line of the post immediately preceding yours will connect you to other reports of similar issue as well as advise about how to capture logs. In particular you should try to find the related Jira ticket to which there is a link somewhere in this thread and which could be found by searching Jira). Optimally, you'd be looking to capture the last kernel message after noticing the spontaneous reboot in progress and forcing boot to recovery from where you can get the log files.

Also "no custom kernel" does not a clean flash make so just as a reminder: Be sure you are testing and reporting from a clean flash with no 3rd party mods whatsoever (no Xposed, no substratum, no Magisk modules). EG Fullwipe/factory reset > flash ROM, Gapp, SU > test > log > report.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Ragarianok:
Kind of looks like our maintainer has put all of his efforts into his unofficial builds for Moto Z2.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] CMKdaGreatest:
We need a new maintainer then
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
That's a fairly common progression; Devs may move to focus on new device while still maintaining the older one less actively. Even though the level of focus on Athene LOS 14.1 is light (and has been for all of the months that I've been using it) we should be glad that we have any maintainer at all or else we might have no ROM at all.

We can still report bugs at LOS Jira: https://jira.lineageos.org, and the more people that add notes to those tickets the better. This exposes the issues, especially general ones (not device specific) to other devs who might help. Speaking of which here are 3 bugs I've tested and reported from Athene device.

- Lag between power button press and display on (Athene specific).

https://jira.lineageos.org/browse/BUGBASH-1115

- Spontaneous reboot (Athene specific with other factors such as telecom or gapps services)

Somewhere in this thread there is a link to this Jira ticket but I cannot find it.

- Only 3 seconds to enter BT keyboard connection PIN (all devices)

https://jira.lineageos.org/browse/REGRESSION-1725
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] patel jignesh:
with this new update(lineage-14.1-20180509-nightly-athene-signed.zip sha256) i cannot access my phone.

also full wipe my phone and again install (lineage-14.1-20180425-nightly-athene-signed.zip ) but not boot up my phone

i can access twrp but not booting up

please help

---------- Post added at 05:29 PM ---------- Previous post was at 04:47 PM ----------

while wiping error show (unable to mount storage) but after some time error gone

then i install lineage-14.1 but again not booting up

then finally booting up by installing RR rom ......
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] j0nas_:
Tried to flash 20180509 build earlier today and only got a black screen with nothing happening so I restored my backup of 20180418 and now my fingerprint sensor doesn't work.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Dhanush-raj:
Try a clean flash then!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] j0nas_:
Okay I fixed it by reflashing the old build. Don't know if a clean flash would help anyway since this is a clean install from about a year ago.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] miteshpc:
Clean flash works

Have been on this rom since several months and had started suffering 3 major issues that I was living with:

1. Shutdown + Start forgets SIM cards, specifically if you have 2nd SIM installed

2. Random reboots (6-8 times a day)

3. Do not disturb doesn't stop. Just keeps the do not disturb mode on.

I have been reluctant to do a FDR as I didn't want to re-install all apps and reconfigure them.

I went ahead and did that today and all the issues have been resolved.

I recommend clean flash as many other posts have done, but specifically wanted to share the issues I faced that were resolved.

I wished there was a way to clean only specific items so that the pain of re-installing doesn't come after clean flashing.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] miteshpc:
Said too soon. The No SIM Card issue re-appears after few reboots.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Don't take this personally but many people claim clean flash when such has not been done and there has been a lot of that in this thread lately, so regarding clean flash (and making no assumptions about what you have done in the past):

- A clean flash now of latest build. Having clean flashed an older build at some point in the past is not viable for bug reporting.

- No previous history of fiddling with non standard modem, radio or other partitions outside of flashing compatible ROMs.

- Any previous history of Substratum manually cleaned up.

- No custom kernel, Xposed, Viper audio, or any other third party modifications.

- Even though SuperSU and Magisk may be viable SU methods, leave them out of it for testing.

In same TWRP session:

- Wipe dalvik and system caches (maybe not necessary but I do this step anyhow).

- Full wipe, aka factory reset.

- Flash ROM, Gapps and, if needed, LOS SU.

- Wipe dalvik and system caches.

- Reboot to system and complete initial configuration.

- Wait 10 or more minutes then reboot again.

- Test before installing your apps.

- Test incrementally as you install your apps.

The frequency of "random" reboots you experience and the infrequency of similar reports, as well as the fact that the problem is not immediately evident after flashing could be indicators of 3rd party software or hardware factors. If you are convinced that this is an actual LOS bug then prepare a bug report at LOS Jira (https://jira.lineageos.org/), and here as described in the OPs of this thread with a link to the jira ticket.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] annoyingduck:
Anyone know how to use the fingerprint button as a home button (like a Samsung's hard home button) here on Lineage? I don't care about the security, I just want to be able to turn on the screen with the fingerprint button without registering fingerprints.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Settings > Gestures (second Gestures item in settings) > Fingerprint as home. For some reason this is not found by searching settings for "fingerprint" (which is effectively a bug).

Also On my xt1625 with no fingerprint sensor it should not be possible to toggle or even see these settings but that can be done (another bug). So, this feature already seems buggy, or at least messily implemented, and your experience may inform that situation and connect 2 different issues.*

- Which weekly build of Athene LOS 14.1 are you reporting from?

- Can you find that setting by searching Settings for "fingerprint"?

- Can you manually navigate to that setting on your device?

- Does that setting work properly?

If that setting does not work for you, or if it does work but you can't find "fingerprint" in by searching in Settings, then I think we should tag-team and create a Jira ticket for it, which I could get started.

* Possibly related to this is another issue regarding an inordinately long lag between power button press and display on (at times over 7 seconds) which involves anomalous activity of proximity sensor while display is off as well as odd behaviour of other settings in Settings > Gestures (second "Gestures" in settings). https://jira.lineageos.org/browse/BUGBASH-1115
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] annoyingduck:
Nice, I don't know how I didn't see that before. I missed it due to it being in another "block", scrolling down further and there it is. I clean flashed the latest official nightly on my wife's xt1644. Option is now enabled and working properly. Thanks.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
- Can you find that setting by searching Settings for "fingerprint"?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] annoyingduck:
Thats a negative, it does not appear by searching for fingerprint.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Thanks. That's not as tight a tie-in to the other issues as I had hoped for but it is a minor bug on its own. I'm still on April10 build so will try to update this week, then file a Jira ticket during next weekend's bugbash window and share the link to the ticket. In the ticket I'll refer to your confirmation that the setting cannot be found by search even on devices that do have the fingerprint sensor (and or you could add that note to the ticket). Thanks again.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] gutosilva:
I'm using the "lineage-14.1-20180523-nightly" + Open GApps Pico Package, and the Dialer (stock) crash in all attempts to clear the call log. I've tried force close app, clear data and cache app, but the issue persist.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
On XT1625 in a clean flash of May 23 build with May 22 OpenGapps Pico I am able to clear call log and frequent calls. Try clean flashing with no 3rd party mods (Xposed, Magisk, custom kernel, Viber Audio, custom dialer) and test immediately after flashing, before installing your apps.

Clean flash process review: https://xdaforums.com/showpost.php?p=76567856&postcount=2797

If you can reproduce it in that situation then file a bug report at LOS Jira https://jira.lineageos.org.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] gutosilva:
It's working now, probably some Google app was causing the issue.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] miteshpc:
1. Maybe it's just me but the SIM isn't detected at times when booting up (hardware issue!) it was working before I installed lineageos updates of April onwards.

2. After booting and install gapps, Google Play Services crash, therefore I cannot restore from cloud.

3. At times it gets stuck at Checking for updates (if I use Start Fresh)

Trying out RR 5.8.5 to see if it gives same issues.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Hardware issues are a possibility in which case you could delicately clean the SIM contacts with a soft pencil erasor (making sure nothing gets into the SIM slot) and carefully inspect the SIM contacts on the device with a magnifying lens and flashlight. The little SIM slot spacers (with the center cut out rather than filled in) which Moto uses in new devices can damage the contacts (and actually destroyed SIM contacts on one of my devices). Apart from that it seems like you may not be clean flashing and that you may be introducing 3rd party factors. If so and you end up wanting to report this as a bug then remove those factors.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Thanks again [MENTION=4795150]annoyingduck[/MENTION] for verifying the failure of search to find fingerprint settings (an incidentally any other text unique to that page of settings). Here is a Jira ticket regarding that:

https://jira.lineageos.org/browse/BUGBASH-1749

On device with no fingerprint scanner remove or make inert "Fingerprint as home" and "Fingerprint wake-up", check for conflict with other Gestures settings.

That may not seem significant, but may relate to a different issue (power-button press lag to display-on) reported in this ticket:

https://jira.lineageos.org/browse/BUGBASH-1115;

Screen doesn't always wake up from sleep

The reasons for the hypothesized association are in ticket notes.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] runswithascript:
Can you please confirm the instruction to install the most recent GApps 8.1 in the original post is a typo. I am asking as although this ROM is 7.x, ubeknownst to me, there may actually be some good reason to use GApps 8.1. Android started locking randomly on me recently, while say recording a Whatsapp voice message or using Google Maps in the car etc. and I have not been able to fix this by wiping the cache, so I am going to do a clean install of the ROM now, with GApps 7.1, but if we really are supposed to 8.1, is there away to easily upgrade this, or should I do a clean install all over?

Also, I am aware we are not supposed to install anything like SuperSU so I do not, and root always works for me with LineageOS, but I also usually end up losing SU access somehow - is this something you have encountered, and is there something I can do to prevent this from happening?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
There is no reference to gapps 8.1 in the OPs of this thread, just a link to the opengapps web page. That web page remembers the last item clicked on in your browser which is in no way a recommendation of what to use. Use the appropriate gapps for Android 7.1.x. Where there may be references to "most recent" it is implied that means most recent compatible version.

SuperSU or Magisk are often used for SU (with no modules and no other third-party factors) without problems. I've never spontaneously or otherwise lost SU while using LOS SU (or when testing Magisk). It seems like you've got 3rd party factors or may not be clean flashing, or may not be properly removing previous SU before testing new alternate SU, or maybe you've installed mismatched components, (somewhat implied by the confusion about gaps). Whatever it is this does not sound like an issue with LOS ROM.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] miteshpc:
Thank you.

1. I have done clean flash multiple times after the post. All times the result is the same.

2. The sim doesn't look damaged, is used jewellers magnifying lens to check.

3. I am seeing a trend that if I keep any one of the sim in sim1 slot then it works after reboot, but putting both sims in whatever position triggers SIM not found (sometimes only). Single sim always works, even if its in 2nd position.

4. There are no 3rd party apps affecting. Even basic android causes same issue.

I am willing to collect logs to figure out what's hapenning. Would like to know what to log and when to log.

This happens to RR 5 as well, so its not ROM related, but looks like its dual sim detection issue.

Do note that do not disturb not turning on sound is an issue in RR. It didn't happen in latest 14.1 after clean flash.

The google play services crashes and doesn't allow me to log in to cloud to download backup on setupwizard when using the latest gapps with lineages, but same gapps works on RR.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Hari Haran:
Data usage consumed by Android is is still bugged?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
IIRC, unless RR has changed in the past few years (which is quite possible) it is based on LOS and may inherit problems from LOS (or in other bases might fix them). In any event the range of problems you've reported, even if not caused by hardware, still don't seem to be a ROM issue. You might find more helpful information, perhaps similar reports, in the Moto G General thread which would include feedback from more different ROMs and flash scenarios: https://xdaforums.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] miteshpc:
So I am back on stock ROM Latest Build NPJS25.93-14-18 with 1 April 2018 security patch on my XT1643. All seems to be working well, none of the problems faced in the trials of the past few months, SIM card is detected well after many reboots. Will revert back soon if something goes wrong. I used procedure as described on https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Meanwhile, I will search for a debug method that I can use and will use it in the event the stock ROM works well so that issues can be reported on Jira appropriately for others to benefit.

Will prepare list of issues faced that were recurrent and common with RR as well. The stock ROM is resilient to abrupt power shutdown whereas the lineage OS requires a clean shutdown or else I have seen both RR and 14.1 weekly going into loops at animation stage due to abrupt shutdown / reboots.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Display-on lag, more evidence towards fingerprint settings. Search failure separate.

A page of mostly OT after a potential connection between 2 actual bugs was reported = bump (not to nag developer but to put testers' eyes on actual LOS bugs). Also, there is some more information for this report. Starting from here: https://xdaforums.com/showpost.php?p=76624077&postcount=2809

New Jira ticket regarding the failure of search to find fingerprint settings (and any other text unique to that page of settings)* :

https://jira.lineageos.org/browse/BUGBASH-1749

On device with no fingerprint scanner remove or make inert "Fingerprint as home" and "Fingerprint wake-up", check for conflict with other Gestures settings.

That may not seem significant, but may relate to a different issue (power-button press lag to display-on) reported in this ticket:

https://jira.lineageos.org/browse/BUGBASH-1115;

Screen doesn't always wake up from sleep

The reasons for the hypothesized association are in ticket notes. Additionally: a test of LOS 14.1 May 26 Osprey may give some direction:

- On Osprey May 26 LOS Athene build the search in settings also does not find any items in the second group gesture settings.

- Osprey does not have fingerprint scanner, nor does it have the display-on lag and anomalous proximity sensor activity that Athene has when display is off.

So, the failure of search to find anything in that Gestures section seems to be its own non-device-specific issue, and there still could be a connection on Athene between the Fingerprint settings and screen-on lag.

It would be helpful to know from the people who experience this issue if it occurs in the following scenarios:

- In stock? (no reports that I know of yet)

- On devices with fingerprint scanners? (there may have been reports but seeking confirmation)

- In LOS 15.x? (reported once as no occuring, but seeking confirmation)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Data Usage reported to Android OS for some apps.

Busy day for bug revelations:

Regarding: Data usage being logged under Android OS process

https://jira.lineageos.org/browse/BUGBASH-1097

This seems like it could be a simple as that Athene is not properly recognizing some installed apps as available options for their file types, and there is a parallel between that and the apps for which Data usage stats are being folded into Android OS. From most recent note in ticket:

Confirming from Athene LOS 14.1 May 23 build that issue persists at least for some apps:

Also, and perhaps more importantly: The same apps for which data usage being is folded into Android OS are missing from available download options in when a file is selected for download.

On an Athene XGT1625 device running May 23 build with the following browser options installed: LOS stock browser, Bromite (Bromite is effectively Chromium), Naked Browser Pro, MiXplorer Save-as/Copy-to (intercepts download so user can select save location)

- Data usage for LOS stock browser and Bromite is folded into Android OS

- Neither LOS stock browser and Bromite appear in list of available download options when link is tapped.

- MiXplorer Save-as/Copy-to is available in list of download options and does have its own entry for data usage.

- Naked Broswer pro is available in list of download options and can be set to use the system downloader, or its own. When using system downloaded Naked Browser data usage stats are reported ti its own item but when internal downloader is used the stats are folded into Android OS.

It may be tempting to blame the 3rd party browsers but then I would suggest focusing on native LOS browser which can also be used to demonstrate this issue, and also the following...

On a Peregrine device running the same week's build (May 26), flashed by the same processes, and with same browsers installed; when selecting a file to download all of the installed browsers are available for use and all of them seem to properly report data usage to their own entry rather than into Android OS (as it should be).

Could this be as simple as Athene is not properly recognizing the installed apps?

[MENTION=5852120]Hari Haran[/MENTION], if this is the issue you were referring to above then by all means add any constructive input you have here and at Jira, but still let's keep the "is it fixed" questions in general. If its fixed there will almost certainly be posts about that here or at Jira which you could find, and you can follow the jira ticket.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Hari Haran:
Yes this is what I asked. Due to this mobile radio is consuming too much of battery