yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
The fact that they occur overnight and not when you're using the phone may be significant, and this offers you a path to further testing. When you find that it has rebooted overnight you can check the uptime to see when the reboot occurred. Then, a log taken over a different night when the device does not crash may reveal what the device is doing at about that time.

As to the sources of similar reports; When you claim such other sources then it is up to you to cite them.

A search page is not a source, an image of a search page is unhelpful, and the scant details in the image that you did provide offer nothing pertinent to establishing cause, reporting, or addressing this possible issue.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
The reboot happens. But its really hard to assume/know when it will happen again! It appears suddenly. The phone gets hang for almost 10seconds, & then restarts. Sometimes it even doesn't restart. Sometimes it doesn't even restart, stays hangs & have to force restart by pressing power button. Sometimes it just restart the SystemUI with the wallpaper changed to default! Its really confusing. Last night i was in a call, & at the moment i tried to cut the call pressing the end call button it got freezed & restarted after a few seconds! ?

Iv reported this before, but as I can't catch any log & very few had faced it, it is neglected then!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
If you already doing this then you are already on the way to getting the log file (last_kmsg) with which a bug report could be created at LOS Jira. That last_kmsg file will be erased after the next reboot so here is how to get it:

After forcing the restart by using the power button, then force boot directly into bootloader by pressing Power & Vol down. The timing of this may be tricky. That button combination must be pressed after the screen goes blank from the first forced restart but before the LOS boot logo starts, and there is some oddity about this device (possibly related to the power on screen lag) that makes the timing of this trickier. From bootloader go into TWRP. Use the TWRP file manager to copy the file /proc/last_kmsg to external storage or some other location from which it can be accessed later for the bug report.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Ok. Thanks. Actually i didn't know that the file last_kmsg gets automatically deleted after the reboot. Tried to grab the file before but thats after reboot. Now will definately grab that whenever that restart arrive. :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] maciocho:
Hi

I've checked this TWRP file manager to get myself ready and can only see /proc/ksmg, there is no last_ksmg file- I've forced restart with the button combination.

Also there is Copy Log option in the file manager

Regards
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kamilopl:
Hi guys.

Have you noticed that minimum ring loudness on LOS is much higher than Stock ROM? It is too loud for me. Do you have any solutions for this problem?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Lucasfontoura7:
Fingerprint is not working 100%
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] anuraganasane:
Edit the mixer path file in system.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Marv42:
Is it possible to add more volumesteps for ringer, notification and alarm? I tried to edit buil.prop like this http://disq.us/p/1lpcrup but it didn't work.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
There are lines to edit for more volume steps:

ro.config.vc_call_vol_steps=14

ro.config.media_vol_steps=30
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Marv42:
Thanks I know, but I want to change ringer, notificiation and the alarm steps
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Perhaps it was not generated or there had been enough of the next boot to erase it. Maybe next time.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
FYI A commit for this was filed 2 days ago and it should be fixed in the next build. https://review.lineageos.org/#/c/190622/. In the commit there is a description of what was occurring. Thanks again for flagging this.

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

Also a general note:This fix for this issue, which was made quite quickly, shows the benefits of staying on-topic here (XDA dev thread) and providing proper details with the bug reports at Jira (or here). Perhaps the same can be done with the reboot issues and the power-up lag.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Wow, thats so fast! I'm thinking to comment few more issues one by one, if you can help me making jira tickets because im not much good in elaborating issues with so much technical way as you did in the last ticket.

& I was just reading you comments & the reboot came up! But same thing like the previous guy said, there is no last_kmsg file. Only kmsg.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
As long as we are dealing with viable bug reports I'd be glad to help people form them here so they can create them at Jira. They don't always move as quickly as this one. This one was easy to reproduce and log, and the dev to which it was assigned through Jira seems to have found a direct connection to something in the ROM.

As to the reboot, my knowledge about how to log issues after reboots is limited. Perhaps there are other log files which could be gathered - anything that is enough to get a Jira ticket started. Until a method for forcing the reboot is established that seems to be what we have to work with.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] x86cpu:
To add with this, this regression looked like it affected most all devices, not just athene. Also, if you do file a Jira ticket just make sure it was working and not just a bug that was always there. It's not always easy either a LOS device tree that supports multiple devices, while a developer might only have a single variant to test with.

For helping to catch a reboot log... I use matlog.. it has the ability to log to a file.... now that might be large.. so you might have to stop/start it periodically. There is also logcat extreme, which can do similar but catch dmesg as well, which a system crash might have details in there and not logcat.

Good luck.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] fredbadboy:
Audio and Calls Bugs on Moto G4 Plus

*Bug*

Lineage 14.1 is deleting my audio files on my moto g4 plus.

Audio not working on:

*Speakers

*Headset

*Bluetooth

*Calls

*Earpiece

Error message: "AudioFx failed try again"

*2nd bug*

Shows missed call symbol for outgoing calls.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] odavans:
Can't clean install latest nightly, setup wizard has stopped
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] QuinsZouls26:
can I use the fingerprint sensor to turn off the screen?:confused:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] x86cpu:
sim card inserted? Or pico gapps used?

---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------

This might help do it: https://play.google.com/store/apps/details?id=com.ztc1997.fingerprint2sleep
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] odavans:
Sim card inserted, and Pico gapos used
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] QuinsZouls26:
Tanks!

Its working
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] x86cpu:
I have a couple devices so I follow a couple threads. The v20 might have an issue without the sim card inserted. While on a g5 thread someone mentioned that pico gapps causes it to crash. Try nano instead: https://xdaforums.com/galaxy-s5/uni...-14-0-galaxy-s5-android-t3476433/post73901536
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Blueman1990:
LOS 14.1 support hike app ? :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] lCrD512:
No.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
No such issue for me on XT1625, nor similar issues reported by anyone else. Also, please don't declare a bug without providing the information expected for bug reporting, since they may let people think that there is a bug when there is not one. An actual bug would have to be much more clearly established than this to be addressed.

- Test and report from clean flash with no hacks or mods (eg Xposed, viper, etc).

- Provide step by step description about how to reproduce the error.

- Share a log taken while the issue was reproduced.

- Include details of the device: Model #, Root method.

Then wrap that all up in a jira ticket as described in the past few pages.

https://xdaforums.com/wiki/Reporting_A_Problem_-_Android

Well, that's just it; I've been lucky enough to have had no reboots this week. Will give some of those suggestions a try if it happens again. Thanks
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] FelipeCadal:
Is GPS working?

Yes, it is. I've tested myself.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
A possible bug people could check for.

There is a setting named "Haptic feedback" in a category named "Touchscreen gestures" which can be found by searching settings for "Haptic" or "Touchscreen" but for which there seem impossible to navigate to through menus. Maybe I've missed it, but can anybody find where this is in Settings?

Another settings issue is that on XT1625 with no Fingerprint sensor there are fingerprint sensor settings. The facts that this device has those unnecessary settings and that the fingerprint scanner (on devices that have one) can be used to wake up device could be related to the delay to screen on after power button press (up to 10 seconds - a total usage killer) and all these things may tie together. I'll be filling a bug for the power button lag next weekend (Jira bug reports received only on weekend).
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
As I was preparing to flash Sept 25 build there was a spontaneous reboot or freeze requiring force reboot (hard to tell which) in Sept 18 build for which I finally got a log. Thanks [MENTION=2881807]x86cpu[/MENTION] for reminding about the dmesg file, which I got from TWRP. Sept 25 build has since been flashed on device but the log from the previous build should still be good enough to start a Jira ticket this weekend (when they accept reports for bugs as opposed to only regressions during the week). The incident occurred after a scan for radio stations in the FM Radio app and while changing the volume, while perhaps also interacting with the UI.

[EDIT] Fixed incorrect mention.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
So you are going to make a jira ticket for the random reboot/freezing? I can flag it, in fact many users can help in that issue if they want!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Vulnerability:
Did the 25th September build get pulled? Can't seem to download it
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
It's downloading fine for me via mobile data and WiFi.

---------- Post added at 07:52 PM ---------- Previous post was at 07:44 PM ----------

Yes, I'll use the dmesg file to start the ticket and then, as you suggest, others can watch the ticket or if they've experience the issue they can vote for it and add logs and notes.

One thing to keep in mind is that it's possible not all of our freeze/reboots are caused by the same issue, or even if it's a ROM rather than 3rd party issue. In other words this could very well be multiple ROM bugs or no ROM bugs. With that in mind, the more logs that can be captured after such incidents - the better. I'll post link to ticket here when it is created.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] alaindupus:
Hello, everybody. Is there any chance to fix the battery drain in official Lineage OS 14.1? How can I fix it in my Moto G4 Plus? Without use, I lose about 20% after a complete charge in 1 and a half hour. I read about a problem in custom ROMs when you have mobile data activated, is it the problem?

Magisk v. 14 installed

Opengapps arm stock installed.

/data encrypted

Thanks in advance, greetings.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Even the extra power consumption used by the data encryption should not be that extreme. Probably not a ROM issue, unless it is one that occurs only in a narrow usage case.

In any event you can use the app Better Battery Stats (BBS) to determine cause of drain. Also, the BBS XDA thread is a good place to post about this (at least until it is established as a ROM issue). There are some folks in that thread who really know how to drill down into power consumption issues. It would not surprise me if you google services, particularly location services, are involved.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] alaindupus:
Thanks for your reply and your information, [MENTION=5119654]IronTechmonkey[/MENTION]

I'll take a look to the app and the thread in order to know how to deal with the battery drain. Good point, maybe location services are draining my battery.

Very thanks, greetings.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] sbooob:
I want to can't connect to a Bixi (a small BLE device that allows me to control my phone hands-free) which advertises itself to the phone as a HID.

Steps to reproduce the issue:

go to the bluetooth preference pane

enable bluetooth

click the device name

What happens:

the device name gets grayed out

a spinner is displayed

it stays in this state for some time (30 seconds to 1 minute)

and then goes back to the idle state (device name displayed normally, no spinner)

What I tried:

I have disabled bluetooth and WiFi scanning in the Location preference pane (someone said it helped in this thread)

rebooting

clearing caches

Phone info:

LineageOS version: lineage-14.1-20170925-nightly-athene

Gapps version: open_gapps-arm-7.1-nano-20170920

What I did

Wipe data: yes (happened on a clean install)

Upgrade from a previous LineageOS build: yes, I originally installed lineage-14.1-20170918-nightly-athene, the bug was already present. I then upgraded to lineage-14.1-20170925-nightly-athene which didn't fix the issue

Restore with Titanium Backup: no

I captured a logcat (form right before turning bluetooth on to right after the connection has failed):
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Rabidelmo4:
If I update to lineage 14.1 from aosp extended will I have to do a clean install to get lineage 15 once it's stable enough for a daily driver?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Vulnerability:
Yes
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Rabidelmo4:
OK ty I'll wait till 15 is good to be a daily then
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] maciocho:
Hi All,

On my XT1642 with the latest nightly there is no option to change the volume during the call on loudspeaker (volume is always the same). Can you please see if it works on yours?

Cheers
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] x86cpu:
Not usually... if you are on lineage official 14.1 going to 15 should be supported. All other versions were.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Slav1k.west:
Hello! This rom is excellent. I would like to know if you can enable the screen lock option by the fingerprint

Turn off and lock the screen...like in the stock ROM.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] GokulChandran:
You can use now

Fingerprint as home then long press home as turn off screen

Its not so great compared to stock can u can use like this

I dont think they will add a seperate option becz most prefer fingerprint as home instead of locking the screen
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Slav1k.west:
Sps
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Anyone Can Help Me With This? I Hardly Used The Internet Today, Just Used Whatsapp/FB Lite & Didn't Download Any Large Files. I Can Remember Someone Already Posted This Issue Before, So If Its Already Discussed/Solved Please Post The Link To That Comment. & If Not Anyone Can Help Me?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
------------

OT

That's a bit off topic for a ROM development thread. The apps you are using all have a variety of features that could use data, and there could be other causes but your exporation should start with them and not the ROM. Cause must be established, which you can do by monitoring internet bandwidth (Internet Speed Monitor Light or other app) to see at which moments this occurs, and by monitory battery consumption (Better Battery Stats) to look for the extra battery consumption that would be associated with background activity.

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

Back to bugs.

Restarts:

I'll try to get that bug report for the restarts into Jira today. Tick-tock, tick-tock, only 8 hours to go.

Power on Screen lag:

The more I explore this glitch the more it seems like some sensor or gesture detection mitigates the screen on lag even when those settings are disabled; ie, if the phone is moved and proximity sensor is triggered before pressing power button then the delay to screen on is not as long. This should be easy to reproduce and log. 2 prospective hypotheses for this test:

- The setting to check proximity sensor before powering on screen (which I have disabled) might be broken.

- Settings to use fingerprint sensor to power on/off screen (which should not be present on this xt1625 device, and which I have disbaled) could be causing problems.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
No I'm not talking about any app, as you can see in the screenshot, the AndroidOS is consuming the data lot & that's also in the background, & i can't restrict the background data of Android OS anyway. & is happening from the last build. & About the battery, the AndroidOS Also Consumes The most! As it's not a normal app & a system app so this could be arom issue ( i thought)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ____Mdd:
Happened with me on RR, and it was Chrome browser, are you using Chrome? All data usage for Chrome was counted for Android OS and Chrome data usage was 0.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Yes i use Google Chrome. But hardly browse something. Most of the time do fb (lite) or Whatsapp.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
As always:You should make a clean installation without any problems third party apps. Then see if the problem happens again. If not, install your third party apps one by one and test them one by one.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] x86cpu:
Anything that uses that much data might be fairly chatty in logs. Logcat for soneone to look at?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Spikeyvic:
I did post about this but it hasn't been picked up by anyone. I'm sure it's a regression bug but I only noticed it early September and I don't know which nightly introduced it. In addition because of the lack of people noticing it I'm wondering if it's limited to certain models I am on XT1622.

Just a quick summary for anyone not sure what's being described here: The process Android OS under data usage is reporting data used by other apps as it's own. This gives the false impression of Android OS burning though data when in fact it's legitimate usage from another app. Also those apps don't have any data usage reported anywhere, either it's app setting page or under the other apps included in usage section of Android OS so there isn't any way of finding out how much data is actually being used by them.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Log it and create a Jira ticket (at this point under the Weekend BugBash rather than as regression because of the amount of time that has passed since it was noticed).

On a XT1625 I'm also seeing all data usage for mobile networks and Wifi under the Android OS and not the individual apps. You've convinced me, but these things don't get fixed without viable bug reports, which for this ROM are best done at Jira (as implied by some statements in the OP of this thread). If you create a jira ticket for this I'll certainly add screenshots and statistics supporting your case and perhaps others will as well. With two other bug reports that I intended to file but to file this weekend I'm not volunteering for another but this one should be easy to log and report properly at Jira.

[EDIT] FWIW: On a Moto Osprey device running LOS from August 17 the data usage stats are properly reported. I suppose it might also be worth a searching existing Jira tickets and the LOS change logs to see if this has been a reported and or addressed.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Spikeyvic:
I'll report it this weekend. Thanks for the feedback.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
If and when you do, share the link here and I'll add some notes to the ticket. Thanks! Now...off to flash and today's build.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Post the link Whenever you do, i will also add the screenshot
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Spikeyvic:
No probs, I'll post the link here.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Issues with Screen-on delay, and Gestures

Although I didn't get the restart or the screen-on delay issues into Jira tickets this past weekend, this has allowed for the gathering of more information - particularly in regards to the delay to wake screen, and some gesture issues.

While searching Jira, this ticket was found describing similar issues, or at least issues that all bring focus to one particular settings panel (https://jira.lineageos.org/browse/BUGBASH-484). From my last note in the ticket (lightly edited for posting here):

"The issue reported in this ticket and several issues in Athene are all apparently centered around this particular settings panel:

- The issues with "chop chop" and "double twist" gestures initially reported in this ticket.

- Inverted state of "Wave to silence" and "Pick up to stop ringing" on my Athene device.

- Phantom "Fingerprint as home" and "Fingerprint as wake-up" on Athene device with no fingerprint sensor.

- No items in this settings panel are found when searching Settings.

- The delay to screen on after power button for Athene behaves as if the same sensors and gestures require input in order to wake screen properly even when those settings are disabled - and even if they are enabled this should not occur (still drilling down into this last one)."
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ldeveraux:
Hi All,

Trying to flash a fresh Version of LOS on my Moto G4. I can't get through the LOS setup due to it not detecting the SIM card properly, saying "Insert SIM Card." I know this is a recent error, but I can't seem to fix it. I tried the earliest build I could download, the 7-31 build, but same issue. What is the latest version that will flash properly, and can anyone upload it?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] maciocho:
I must say this 02.10 build is great with battery life!

No restart yet ?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] gavron:
Bug with fake MWI showing 2 messages after loss of network is FIXED. It is fixed in the current release (20171002) and it was fixed first in the previous release (20170925). I am unable to locate which of the commits addresses this so it's likely a byproduct of a different fix.

E

(recap: at the point of losing CDMA/GSM network connectivity the MWI showed 2 messages. Connecting to voicemail showed none. Only workaround is to create a new message, delete it. This annoying thing happened every time I went through a tunnel... across a mountain with no coverage, etc. All gone now :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Spikeyvic:
Heres the link to the BUGBASH report:

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

EDIT: This is for the data usage under Android OS bug.