yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] modmail:
- Dirty flash. I use the Lineage updater with TWRP. (Maybe this matters: before the latest update I had to erase my phone remotely, then sync it with my google account to redownload all the apps--and didn't re-flash gapps because everything seemed to be already there. Unfortunately I don't know whether I had the dialer problem before that, people mostly just text these days).

- Stock variant of gapps

- Never tested 3rd party dialers, although used Mr. Number, a call blocker. It doesn't replace the dialer but shows a small overlay when someone calls. Cannot tell for sure, but I don't recall seeing the usual overlay window from Mr. Number while I was having trouble with the phone app. So maybe there's the conflict. I deleted it shortly before posting here though, which didn't solve anything.

I know it's a mess :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Thanks for those details. The dirty flash could cause things like that.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] anoopgkris:
Installed the 25 Dec version, with TWRP 3.1 on my Dual sim XT1621.

Working nice so far. Both Sims detected and work well. :D

Some minor things..

Moto camera app does not work.

CM Snap camera does not have slow motion video recording.

Thanks for the ROM! Nice work!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ____Mdd:
Are you referring to video recording?

Then, Moto camera app works fine if you install it in system partition, find flashable/modded camera zips in apps section, and flash it.

For slow motion on snap, you will have to ask lineage team to add feature.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] rijukrishnan:
how to enable FP in this ROM.. i cant find a solution
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ____Mdd:
FP is enabled by default when you add security lock screen, then you can register fingerprints.

Tell us more about your phone setup,

Have you flashed/updated your phone to stock N before ?

What is baseband of your phone ?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ferzmedina:
I have an unlocked bootlader on a XT1625 Amazon Prime G4. Is it possible to flash Lineage OS on that phone. I was lucky to unlock bootloader within the first days of release.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
Yes, it's working on every variant of g4 plus and non plus
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] VPawankumar369:
How to solve ghost touch and screen burn.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Luis Infante:
Calibrate red,Green and blue 80% in live display

Work fine for me
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] VPawankumar369:
For screen burn?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Luis Infante:
Yes
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ajab_sharma:
It fixes the screen burn to a great extent too, but it's only a fix not a solution! Set R,G,B to 80 as explained.:)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] VPawankumar369:
For me it's not fixed. And what about touch
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ajab_sharma:
Please refer to the help thread then, so that this thread remains clean for ROM development issues only.:)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ajw85:
Is there any reason editing of APNs is disabled?

Can Total Wireless be added to the LineageOS list of APNs?

My G4 shows TRACFONE.VZWENTP as the APN which is great but MMSC isn't configured correctly.

APN: tracfone.vzwentp MMSC: http://MMS.vtext.com/servers/MMS MCC: 311 MNC: 480 APN Type: default,dun,supl APN Protocol: IPv4/IPv6 APN Roaming Protocol: IPv4/IPv6 Bearer: GPRS, eHRPD, HSUPA, HSPAP, , HSDPA, HSPA, LTE, UMTS, EDGE
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
AFAIK native APNs cannot be edited but you can created new ones (and IIRC this has been the case for some time with few exceptions). I had to do the same thing once to change a value in a T-Mobile APN.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] iainfm:
Dialer issues 20180101-Nightly-athene

Hi,

I flashed my phone (XT1622) from stock, including a full wipe, and install of OpenGapps stock (20171230).

Since then, I can't hangup a call and the proximity sensor doesn't seem to work to lock out the screen when it's against my ear.

Any suggestions welcome, please!

Iain
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] iainfm:
I think I've fixed it. After trying and uninstalling a couple of 3rd-party phone apps I noticed that the google dialler wasn't set as the default phone app. I enable that, and it seems to be working properly (including the proxy sensor).

I'm now getting a blue screen when the call is connected with speaker/keypad/mute buttons etc, and the all-important hang-up button :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] sahib32:
I am not able to add fingerprint

I am not able to add fingerprint. First it says locate the fingerprint sensor on the back of your phone but it's on the front but anyway I tried to register my fingerprint. It shows an error that fingerprint enrollment didn't work. Plz... help me
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ____Mdd:
What is baseband of your phone ?

It should be latest than M8952_70025

If it's lower than 70025, get latest firmware and flash it (see link) (flashing firmware will wipe internal storage)

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jqm_:
Did you installed 7.0 stock firmware before migrate to 7.x custom roms? If no, this is the problem.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] SebaS-DG:
Hi, I'm using LOS for my G4 plus and I want to cahnge and fake my phone name and model, I alredy do this on a LG G3, now it appears for google and others programs to be a xiaomi redmi note 4. I do this editing build prop and change model and brand (it helps me a lot with some games and others), but when I do this on my Moto g4 plus with LOS (im using LOS in both cellphones) it changes nothing...

I edited build prop, but nothing changes I dont know why, in settings it keeps appearing "moto g4 plus, morola"

What can I do?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
This thread is for testing the ROM itself, by definition without such 3rd party factors and modifications. Nothing against such modifications but this isn't the thread in which to discuss them.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Dalja:
Sometimes I got troubles when I try send a Screenshot for Messenger, and it's no my conection.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
Please don't post your problem only once(xda rules), be more detailed and if you're facing this issue with multiple roms(like your double post offers) use the help thread please https://xdaforums.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
You are better than I am at letting things like that blow over without making them worse :)

Getting back on topic at least somewhat:

In regards to the lag between power button and screen on, when the device is in the problem condition the lag is consistently 3-4 seconds and occasionally as much as 7-8 seconds. I'm certain that the proximity sensor is a factor and suspect this relates to the Ambient Display hand wave setting since the severity of the issue does seem to change depending on how those settings are handled after flash. I'm still trying to turn this into a constructive note for the jira ticket. [MENTION=7874992]ccpower[/MENTION], have you experienced this anymore?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Az Biker:
* * * Thread Cleaned * * *

Let's all remember that development threads are for the purpose of development, NOT complaining, NOT arguing, and NOT posting rude or disrespectful comments.

If there is a process implemented to report broken features, bugs, etc. FOLLOW that process, if you don't understand that process, politely ask for help.

In the event users have forgotten what IS allowed and what is NOT allowed to be posted in Xda, here you go:

Forum Rules

Bottom line; if a user is violating the rules or being disruptive, simply REPORT them. Don't engage, argue or punish them, especially in the thread.

Please, let's get back to development talk and forget about the trash talk.

Thank you.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] VPawankumar369:
01-12 10:43:26.419 E/libEGL (27434): validate_display:99 error 3008 (EGL_BAD_DISPLAY)

Error I got after ghost touch checked every thing base band and everything is correct.

And I know I will send total log cat. This is just to say ghost touch is happening. I will upload complete log by evening
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
There are 2 dedicated ghost touch threads https://xdaforums.com/moto-g4-plus/how-to/ghost-touch-revealed-t3496755 and https://xdaforums.com/moto-g4-plus/how-to/ghost-touch-solution-empirical-method-t3679962 since ghost touch is not rom related as you can read there.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] VPawankumar369:
Hmm those treads are regarding charger but in my case it happens even my device is unplugged.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
[MENTION=5253673]rahulsnair[/MENTION], Would it be possible to change the unused review thread here (https://xdaforums.com/devdb/project/?id=18418#reviews) into a LOS 14.1 Athene Q&A thread (which is what some other LOS threads do)? If that could be done then all the off topic about hardware issues, 3rd party issues and bad process issues can be kept away from actual bug testing. In any event, thanks for maintaining Athene and for having some nice bug reporting instructions in the OPs.

[EDIT] [MENTION=5253673]rahulsnair[/MENTION], Please disregard (except for the thanks for the ROM). There is already a thread for Q&A.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
please read both threads completely. You'll see that's not only when plugged to a charger.

---------- Post added at 08:33 AM ---------- Previous post was at 08:27 AM ----------

There's a newbie help thread for all discussion https://xdaforums.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and a dedicated help thread for custom roms. Imo a 3rd thread would not be more helpful...
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
That error indicates bad hardware, or missing proprietary vendor files, custom DPI tweaks, or other firmware modification done to the device in the past (and possible bad flashing procedure). You can research that yourself as easy as I just did. Your charging reports (in the absence of any similar reports by anybody else) indicate the same thing. That is all off topic for LOS Athene ROM dev and now thanks to [MENTION=613506]strongst[/MENTION], we know where to post about ghost touch (which is not a LOS ROM issue so not discussed here) and other Q&A.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] st0nedpenguin:
I haven't been paying much attention since before the holidays but has the random reboot issue been fixed yet?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] odavans:
Random reboot? What you are talking about?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] tyratron:
Device reguraly reboots with no apparent reason. I have this issue too, but it's not so annoying
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
That's what search button (here and at Jira) and previously shared links to the Jira ticket are for. ;)

Apologies (in general), I should have mentioned this here, but swimming up the stream of reports with no supporting details is a bit of a drag.

As mentioned in the Jira ticket I've not had a reboot for at least 2 months, and it seems as if vache has closed the ticket, IMO reasonably so. (https://jira.lineageos.org/browse/BUGBASH-1112)

Also, even when this problem existed it was nowhere near that bad, and considering the frequency of reboots your device is almost certainly experiencing issues related to dirty flashing or other problems with the process or 3rd party factors. It is likely that a significant percentage of the "spontaneous" reboot issues were caused by such 3rd party factors, perhaps even factors not related to clean vs drity flashing. Such is the nature of those issues, especially when the cause has not been isolated - and cause can be difficult to isolate for such issues.

You should review your process and test in a clean flash with absolutely no 3rd party mods (especially Xposed) and no past history of substratum (unless you've manually cleaned it up). Then test for and try to reproduce the issue before loading the device with apps, and continue to do so as you add things and configure the device. If the issue occurs, then immediately grab the last kernel message and or dmesg files before rebooting into system. There are descriptions about how to do that in this thread and perhaps the Jira ticket, and the Q&A thread may also be helpful for this. If you get to the point where you can demonstrate a ROM issue, or at least have solid logs and reporting details, then try creating another bug report.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jimmyrs1:
Anyone have a link where i can find that rom like a AndroidFilehost or sourceforge?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] theredbaron1834:
Also s/he could look at magisk. I am pretty sure it is my issue, a reboot every other day or so. I am willing to deal, as I "need" my modules. However, if you use magisk try removing it, or disabling modules you don't "need".
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Good point. As root method Magisk seems relatively inert, but as with Xposed, modules can introduce issues.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jimmyrs1:
https://androidfilehost.com/?fid=962157660013071245 this link or rom its safe?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Who knows? That is an unofficial build. You would have to check with the people who made it or people who use it. Where did you get the link?

FYI, This thread is typically for the official builds and there is a link to them in the OPs.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] st0nedpenguin:
I've tried everything short of clean flashing and not installing any apps to see if the phone still reboots, unfortunately this phone is actually used as a phone so I can't leave it lying around in an unusable state for an extended period with no apps. And the reboots are killing me since it nukes logs in AndChat every time it dies.

I did just clean install everything from scratch with the latest build though, so maybe I'll get lucky and it'll turn out the last build I tried was before some kind of fix was implemented.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Snikeer:
I've been having trouble getting GPS fixes for over a month now, no build seem to fix it. GPS Status finds satellites, however it takes several minutes (5-10) for any of them to get a fix. To get a correct position takes even longer. I'm on the latest build right now, did a clean install. Haven't used Magisk, or Xposed, so no risk of interference. Does anyone have any advice?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Not occurring on my XT1655 on most recent build or previous builds. As to advise, if you think this is an actual ROM issue then submit a proper bug report here as described in the original posts of this thread, and at Jira according to their process. Before you do that you could try the apps GPSfix or GPS Status Toolbox to force a quicker fix.

Some non dev thread follow up about process here: https://xdaforums.com/showpost.php?p=75260842&postcount=1241

---------- Post added at 01:54 PM ---------- Previous post was at 01:44 PM ----------

Logistical difficulties of testing on a production device excepted, it is still easy to grab the logs if you catch the device while rebooting. Also, as previously suggested by [MENTION=6859775]theredbaron1834[/MENTION] here: https://xdaforums.com/showpost.php?p=75240004&postcount=2574, remove Magisk from the equation (if you are using it) and when the issue occurs again, create a viable bug report with whatever details you can gather.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] sahib32:
I have enabled root access on my moto using develper options>root access... Any idea how to unroot my device??
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Since that's a bit more Q&A than bug testing, an answer (though not necessarily a great one) here; https://xdaforums.com/showpost.php?p=75267037&postcount=1245.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Making sure the Jira ticket for the screen on lag stays alive: https://jira.lineageos.org/browse/BUGBASH-1115

Confirming still occurring as of Jan 8 2018 Athene build.

From more testing it is clear that when the device is stationary and face up with screen off and the proximity sensor is not indulged just before the power button is pressed, then the delay will occur. If that is not done then delays of 3-4 seconds are the norm, which while comparing to other devices (Osprey, Peregrine, Otus) obviously is not normal.

Even worse, when carrying the device in hand while walking, indulging the proximity sensor does not always serve as a workaround. In these cases the delay may be as much as 7 seconds, at exactly the times when a reasonable response time for screen on is needed. Although technically the device is "performing", these delays are a significant general usage killer for a hand-held mobile device. (eg back to Peregrine as daily device).

It should be noted that, through these tests ambient display and all gestures were disabled, which makes the results even more anomalous, especial in conjunction with the seemingly odd sensor activity shown in the logs.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] st0nedpenguin:
I wonder if the reboot issue was/is also related to the screen on/sensor issue? That was about the only time I ever actually noticed the reboots happen while I was watching, the phone would freak out while trying to unlock and end up rebooting.

On a related note I'm up to 59 hours without a reboot now, maybe there was a fix implemented recently that finally updating brought.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Pissa:
Sorry guys noob question.

From OP I don't understand if, upgrading from weekly to weekly, should I reflash every time GApps of it they are persistent.

Thanks!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Blackstard:
You dont have to reflash gapps

Enviado desde mi Moto G4 mediante Tapatalk
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
I've had no spontaneous reboot in the 2 weeks that I've been running LOS Athene Jan 8 build or in the preceding 2-3 months on any build. I don't recall seeing anything that indicated it was specifically fixed (not that I would know all that stuff) so it might have been and incidental fix, or it could have been related to Gapps, or something else.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] mankokoma:
i have had these reboots with ANY build but only if running excessive ram using apps like firefox or while watching netflix or so. Best to prevent that is to kill apps with long pressing back button, which is possible to set in development options.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Screen on lag even with ROM & Gapps only.

While clean flashing LOS 14.1 Athene Jan 22 build with Open gapps Pico Jan 22: During first pass through putting desired settings in place and before installing any apps whatsoever, the delays were > 5 seconds every time I powered on the screen. When I connected the device to computer to log via ADB the issue did not occur. This may be consistent with what John C. mentioned in ticket about forcing CPU states as a workaround. Details in ticket: https://jira.lineageos.org/browse/BUGBASH-1115. If anyone else can reproduce this please do vote for the ticket. I'll attempt to log with an app, and would be interested in knowing any ways to capture more useful logs.

[EDIT]

That is not enough information to establish that it is a ROM issue, and few people making these claims are verifying the details of their clean flash process. This does not mean it could not be a ROM issue but it does mean that little could be done with the reports. That being said, perhaps Athene devices with different specifications are being affected differently. On a 2GB Athene XT1625 I dont epereince the issue. By any chance are you using a 1GB device?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] derlotse:
I'm experiencing random reboots, too.

G4 Plus 64GB/4GB RAM

twice, while typing in WhatsApp, several times happened while phone was not being used while in pocket or lying on table.

I started with lineage this year on January 6th with the latest nightly available at that time (Jan. 1st build?), updated on January 8th and now on 22nd as soon as builds were out. reboots on both of the latter, on first i can't tell, was running too short before update came. No root.

any suggestions how to get some meaningful logs? would I need to root for logcat/kernel log after crash?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] mankokoma:
Got a XT-1622 (is the one without "Plus" and no finger print sensor) and it has 2 GB of RAM. The reboots are rarely and randomly. The upgrades I do dirty over shrep's TWRP 3.1.1 and I have installed the pico gapps (with now many updates in the data-partition). I'm afraid the more and more growing google stuff is responsible...

If I should get a chance to have a copy of logcat in case of a reboot, I'm gonna post it here for sure!

Sometimes I try "provoking" the reboot with extensive use of an app and before do in adb shell or terminal emulator

logcat >/storage/emulated/0/logcat.txt

but of course like Murphy knows, there is no reboot, whatever you do :(

To make it easier to clean up RAM, i wrote a script which I put as widget (smanager) on the homescreen:

#!/system/bin/sh
for proc in firefox fennec fblite xda.labs
do
Z=$(pgrep $proc)
if test $Z
then
kill -9 $Z
else echo "$proc not running";
fi
done

After using e.g firefox it will free up a little
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] NexxP963:
Just to share my experience with LOS.

I've been using LineageOS since november 2017 and there was just 1 unplanned reboot. I did all updates (I guess I made 5 updates)as dirty update incl. flash of pico gapps. Everything is running fine.

Device: Moto G4 Plus XT1642

Gesendet von meinem Moto G4 Plus mit Tapatalk
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Pissa:
I have a bug with latest build, don't know if it's a problem of my phone of of the rom.

I dirty flashed it and sometimes, when receiving calls/messages/notifications, the phone shutted down (don't know if it was really shutted down or just hanged, anyway screen totally black and I had to press power button to power on).

I think it was for the dirty flash, so I performed a full wipe and reinstalled everything.

Same behaviour.

Until I discover that the cause is when the volume is 100%.

In fact, when I'm at work and the phone is silent, never have a problem.

When at home, it happens frequently.

It happens also when, in settings -> audio, I push the slide at 100%.

With older builds never had this bug.

I'm the only one facing this problem?