yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] andrescm:
Hello guys. Last time I checked, this ROM was unable to switch single SIMs on and off. Is it able to do that now?

Thanks!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
No, it's only possible in stock based roms.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
Does anybody have more detailed information as to why? Is it a proprietary thing or is it only a matter of not having been coded in by anybody yet?

---------- Post added at 07:57 AM ---------- Previous post was at 07:29 AM ----------

Just to confirm - you are talking about the bug where the screen remains off after pushing the power button? I have the base Moto G4 model without the fingerprint sensor, and i have this issue. I flashed the development version of LOS 15 for testing, and the bug is gone. It's an early version though and not suitable as a daily driver for me, and so the device sits in my drawer until further development. I'd love to return to 14 if this bug could be fixed for it. :good: As it is, the bug totally kills using the device. I was surprised it wasn't more common, but reading your post makes sense, i guess a lot more people have the Plus model? I got mine for free so didn't have a choice, really.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Yes, that's what I'm experiencing on a G4 xt1625. BTW: When I pass something over the proximity sensor before pressing power button the delay does not seem to occur. I don't see why it would be fixed in LOS 15 unofficial without also being fixed in LOS 14 but we will see. As to being under-reported, it might not occur in all usage cases and some people might not notice (even as bad as it may seem to you and me). In any event, since LOS Jira is still receiving reports for LOS14, I hope to file a bug report for this later today. I'll share the link here so you can vote for the ticket and add notes. Thanks for confirming this.

---------- Post added at 04:39 AM ---------- Previous post was at 04:38 AM ----------

Thanks! I added notes and vote.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
I'll do that, thanks! LOS 15 does have fingerprint options visible in settings too, and yet the bug definitely does not occur for me on the unofficial version, i've been testing it so much my power button is going to wear out soon. I should probably add that to the notes on Jira, sounds relevant in case someone (hopefully) takes a look at it?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ldeveraux:
Sorry for the bump, would love to install this!

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] IronTechmonkey:
All of the recent versions flash properly on my xt1625 single SIM device. I've been flashing LOS builds each week on Athene and every few weeks on Osprey and Peregrine devices (also single SIM devices, flashed with and without SIM inserted) and had no such problems, nor have others been reporting such problems.

This could be an issue with the process being followed, the installation material being used, or the history of the device, and your question might get some traction in a TWRP recovery thread.

If this is an actual ROM issue then you or someone else experiencing it would have to provide some logs and evidence that it is so, and perhaps create a jira ticket for it. Reports should include a mention of specific model # and single/dual SIM configuration (which obviously might be important to a SIM related issue). I'm not doubting your report, but those things are necessary for bug reporting and so others can act on the reports.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ldeveraux:
It was a LOS bug that began sometime in June I believe. If you're dirty flashing you wouldn't see this error, but a clean wipe and flash will. I don't recall the bugbash mentioned offhand, but I do recall reading. Is nobody else having issues clean flashing a build on the G4?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
You've been around and active long enough here to know this: Cite source or it never happened ;).

I clean flash Athene every week (sometime multiple times for additional testing) and have been clean flashing LOS builds on Athene, Osprey and Peregrine for months with no such problem.

Then it never happened. If it was an actual bugbash or regression ticket then you could search LOS jira for it and share the link here.

It seems not. That does not mean there is no bug, but it does mean that you would have to provide enough supporting material to make a viable bug ticket at Jira. Such is the nature of a possible bug which may be occurring in a narrow usage case.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ldeveraux:
I think this was it on JIRA:

https://jira.lineageos.org/browse/REGRESSION-1168

And the resolution:

https://review.lineageos.org/#/c/191099

If you're clean flashing every week, then I guess it's not a LOS issue. This should work fine on a G4 (not Plus) with the NPJ25.93-14.5 build right? The build shouldn't matter if it's being completely wiped in TWRP? Apart from the OP, is there something omitted that needs to be flashed/wiped beforehand? Seems really weird that it won't find the SIM card at setup, despite the notification bar showing full signal as well as LTE.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Thanks for the detail. That ticket seems to be a duplicate that was folded into this one (https://jira.lineageos.org/browse/REGRESSION-1138) through which the issue was tracked. I remember seeing that commit when it came out but thought it only had to do with recent apps. In any event I suppose that means it should be fixed. The previous build should not matter as long as it has not done anything unconventional to the partitions.and drives. I add few extra steps, some not necessary but I get good results: Wipe dalvik & system caches > Full wipe (factory reset).> Flash ROM, gapps, and SU in one session > Wipe dalvik and system caches > Boot to system.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Bug roundup.Oct 10 LOS 14.1

Notes about 3 reported issues:

Occasional "spontaneous" reboot.,https://jira.lineageos.org/browse/BUGBASH-1112.

[MENTION=6928666]jyoti.id[/MENTION] and others experiencing reboot, here is a jira ticket for the reboot I experienced last week (thanks again [MENTION=2881807]x86cpu[/MENTION] for reminding about dmesg). People who have experienced the reboot can add notes and votes or watch the ticket. When adding details to Jira tickets please remember that LOS Jira is a serious issue tracking system rather than a chat thread.

Data usage being logged under Android OS process, https://jira.lineageos.org/browse/BUGBASH-1097

Added notes to ticket (thank [MENTION=1360535]ldeveraux[/MENTION] for creating it):

In clean flash of Oct 10 Athene, w/Open Gapps Pico and native LOS SU the issue was immediately evident. I downloaded 2 LOS build zip files (each >300mb): The first via Naked Browser passing the file to the LOS system downloader and the second by having Naked Browser pass the file to a "Save as/copy to" feature of MiXplorer (file manger app). In both cases all of the downloaded material was being added to "Android OS". Same thing when test repeated for wifi and mobile data. Interestingly, in the statistics there were some apps that had downloaded small amounts of data. I suspect they may be doing so at startup before some condition is reached after which the stats are all filed under Android OS.

Delay between power button on and screen on:

[MENTION=7874992]ccpower[/MENTION], and others experiencing the power on screen delay: I was unable to force this to reproduce when logging, therefore no bug report, however: FWIW: When I pick up the device and wave its front across something or when it is stationary and face up and I wave my hand over it (triggering proximity sensor?) then press the power button the delay rarely occurs.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] ThePrathamesh:
Xposed is out for nougat. Will it work in this rom?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
Yes. FYI there's a discussion thread for xposed https://xdaforums.com/moto-g4-plus/how-to/xposed-framework-moto-g4-plus-t3398332
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
[EDIT] Moot, deleted.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
Thanks for the info. I was able to reliably reproduce the bug 2-3 times out of 10 when i tried waking up the device. For me enabling the gesture settings you mention made no difference; the screen would all too often remain dark whether i waved a hand over it, lifted it up or pressed the power button. I gave up hope on getting it fixed, so wiped the device and re-flashed the unofficial LOS 15 version, which is of course quite incomplete but at least it's somewhat usable. I'll just say it again; the bug doesn't exist in it. Let's hope it stays that way. :good:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Which would mean that you might be able to log it and get a Jira ticket started ;)

Well, that's an odd thing about this: I did not enable any of the gesture settings, in fact immediately after flashing ROM I intentionally enable then disable them all to make sure they are actually disabled (that's an ancient configuration panel trick), and I briefly tested with them enabled as well. The device still behaves as if proximity sensor detection wakes it up faster even with that feature disabled, but then there is the fingerprint scanner mess and the fact that some of those features also have to do with waking and sleeping the device.

Giving up hope is not typically they way things get fixed in software development, in fact such a view of things is antithetical to the purpose of dev (yeah I'm getting heavy about the purpose of development today even though I'm just another end user). I'm not at all doubting your observations (which actually gave me motivation to chase this a bit) but absent any valid description of what was fixed in LOS 15, IMO it's worth pushing through LOS Jira which is still receiving reports for LOS 14.1. Perhaps, If I have the opportunity to reproduce this by next weekend's bugbash I'll report it at Jira. If anyone else creates a ticket first I'll certainly add notes.

In any event, thanks again for at least validating that this was an actual issue!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
Well, you're right. I could reflash it and see what i can do, but i've never logged anything or submitted a bug officially. There's a first for everything of course, i'm just not convinced anybody would do anything about it, given that Oreo is the likely focus for almost everybody involved right now. And, as mentioned before, this appears to really annoy only a small handful of people, of which i have been complaining about it the most. I asked about it on the LOS subreddit some time back and there was one person reporting it as "normal" for the ROM. :eek:

I know this is irrelevant but i'm annoyed by it because my old 2nd Gen which has a gray and scratched camera lens is almost useless for taking pictures of our newborn, and i got the Moto G4 just in time and for free, and i can't make proper use of it. The official version lags so i can rarely wake up the phone in time for a good shot, and the unofficial version has no video recording. This is nobody's fault, but it's irritating the crap out of me. Glad my wife has a Moto G3, not a very good camera either but at least the lens is clear.

I'll see if i have the time for a reflash, i didn't take a TWRP backup of it because i figured i'd never go back. / edit: it just occurred to me i might try flashing the latest stock ROM just for the camera, until the unofficial LOS version works properly. Dumbass doesn't always get it, see. :silly:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
That is not true. As I've said, the LOS jira ticketing system is still receiving and working on bug reports from LOS 14.1.

Various factors could explain why a real issue may be under reported, but this is real and it is not normal.

I share your frustration as this really does hobble the natural use of the device. FWIW, Our usage cases may be different but waving my hand in front of the proximity sensor before pressing the power button really has worked for me, and now some logs provide supporting evidence:

I logged the following:

- An instance where there was a delay of several seconds.

- An instance where after a wave at proximity sensor there was no delay.

- The proximity sensor being triggered when screen on when it should not be active.

- The proximity sensor being triggered and the "wave" feature being invoked when the screen is off.

The sensor activity in the logs does not seem right, and the same proximity sensor activity does not occur on an Osprey device running LOS from some weeks ago (and I don't think the date of the build matters since this issue has persisted for a while). If it is not a problem with the settings we've been discussing then maybe it has to do with "doze" which also looks at sensor data. In any event this should be enough to create a jira ticket (this weekend).

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

Speaking of Jira tickets, some people have added good feedback to the ticket for the reboots (https://jira.lineageos.org/browse/BUGBASH-1112). In particular "Christoph Ze" (Jira username) provided to proper location of the last_Kmsg file (for which I had provided the old logfile name and location). After a crash the equivalent of last_kmsg file is now the file /sys/fs/pstore/console-ramoops.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
Okay, i registered at Jira and i'll try to pull some logs when it happens. :good:

edit: I don't get it. I plugged the device to my computer, and now the issue does not occur. I've clicked the power button 150+ times and it always turns on. I unplugged the cable, and the problem showed up immediately. How can this be related? :eek: I plugged it back in and quickly grabbed the log so i have it now, at least with some info. No idea if it's helpful.

edit 2: I can reliably reproduce the above, the phone wakes up fine as long as it's plugged in to my computer via USB. Unplug it, and the problem returns in just a few clicks.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
It does not surprise me that it behaves differently when under power, which may affect doze and related sensor activity among other things. After I create the ticket and share the link here you can post additional logs. IMO any logs that capture the delay would be great so it's nice to know that you can force reproduce this. Thanks!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] SilverDragon24:
It would be nice to be able to select LTE, 3G or 2G irrespective of sim card. I've attached images below.

I travel a lot nd 2G is extremely consistent on the road.

p.s the ability to select LTE Only and 3G Only would also be a nice addition. Just an idea.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
I use the same setting panel that is shown in one of your pictures to force 3G (and LTE should force LTE as long as LTE network is available). If you want more control you can open a hidden "testing" menu like so...

- In phone dialer paste the following *#*#4636#*#*

It may also be possible to invoke the hidden testing menu using activities that are exposed to launchers and other utilities.

- In the "testing" panel select "Phone information".

- In the "Set preferred network type" field you can force various individual and combinations of network types. The effect of various selections there will vary depending on your provider.

Nota Bene: I would advise against playing with any other settings in the phone information panel.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] SilverDragon24:
I know about that but it doesn't always stick.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Not doubting, just clarifying) here. Without some more detail "stick" is open to interpretation so: What do you mean by "stick? What actually occurs?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
I don't mind opening the ticket too, if i get to it first. I'd like to get it open as soon as possible, is the tracker open every weekend or at random? By the way, waving the hand in front of the phone before pressing the power button does indeed seem to help. Not always, i tested it briefly but it certainly seems to reduce the lag. I have my gesture settings (ambient display) turned off at the moment.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jaxx08:
Pls make it official ????
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] strongst:
https://xdaforums.com/moto-g4-plus/development/rom-lineageos-15-0-14-sep-2017-t3672940
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
IDK at which at which time it starts, or in which time zone, or if it starts the same exact time each week but the Bugbash should start some time tonight. I've got what I need to create a report but if you want to explore the process and create it, then please do go for it. How about this: If I notice when Bugash is opened tonight I'll post here so you can run with it. If you've not replied by Saturday or Sunday I'll go create a ticket. If you prefer that I do it I can do so by some time tomorrow.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] cra1g321:
Moto G4 here with latest build (9th Oct), i've noticed today that just setting location settings to "device only" as in GPS only, i'm unable to get any app to detect where i am.

Is there a solution / workaround to this issue ?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
I use device only GPS exclusively and it's been working fine for me. Not likely to be a ROM issue, and to establish that it is would require more details as well as logs.

Sometimes it takes a while to get a GPS fix. You can try an app called GPSfix from the PlayStore to see if you can get the fix moving along. Also, all this presupposes clean flash and no external system modifications.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
Sounds good. Out of curiosity... could you please check if your phone has the following services installed and running (= not disabled manually):

com.qualcomm.qti.ims

com.qualcomm.atfwd

com.qualcomm.qcrilmsgtunnel

com.qualcomm.timeservice

com.quicinc.cne.CNEService

com.qti.service.colorservice

org.codeaurora.ims

My logcat has tons of spam related to some of these, i've had them disabled for quite a while and noticed no adverse effects. After seeing lines with "Atfwd_daemon out of sleep" i enabled them, but i still get the lag.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Those are normal items and it's normal for the logs to be chatty (many thousands of lines some times), especially when logging shortly after startup and other times when the device is fairly active. I would not disable any of those services for 2 reasons: 1) No specific and targeted reason to do so, and 2) logging and reporting issues should be done from a "normal" state, and a "normal" state in this case is to leave those running. What we really want to look for is proximity sensor activity and references to "wave" in the logs. I've described this in more detail in a previous post and will add those notes to the ticket.

[EDIT] [MENTION=7874992]ccpower[/MENTION], Weekend Bugbash has begun...
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] SilverDragon24:
it just resets to LTE on its own.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
And here's the ticket. I hope i entered it correctly.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Hari Haran:
One noob question.

I haven't used this since a long time. I wanna try this rom. Can anyone give latest review and also tell me whether it supports oms and this Andorid os data consumption bug is present or not
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] jyoti.id:
Its smooth & Good. Battery backup is good.

Data Consumption Bug Is Present Since its a LineageOS Source Bug.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] :
By "data consumption bug" you mean that all data usage is logged under Android system, instead of individual apps? Mine does that, but i also have the same regarding battery stats: the power manager shows screen, wifi, system and a couple other misc items but not individual app power usage at all. Must be model-specific because none of my other LOS devices behave this way. :silly:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
Looks good. The details about when you first noticed this and that you can reproduce on demand are good to have in there. I've voted for it and in a few hours will add logs and details about the curious proximity sensor activity. Thanks for kicking off the ticket.

+1 In re battery stats not showing per app in recent LOS Athene builds (model xt1625) while battery and network stats do appear on Osprey & Peregrine builds from 2 months ago. I could see how these to things could be related. Let's see if the devs say anything about that in this Jira ticket:https://jira.lineageos.org/browse/BUGBASH-1097. Thanks [MENTION=6928666]jyoti.id[/MENTION] , et al for adding details. The ticket has already been assigned to one of our device devs... who also happens to be busy with LOS 15 unofficial (as can be told by vache's recent posts) so let's see how it goes.

[EDIT] In regards to the terminology "model-specific". The case you seem to be describing might be more appropriately called "device-specific" while the differences between Athene models, eg xt1643, xt1625, would be "model-specific".... Or are there some Athene devices on which this does not occur?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] alaindupus:
I have an strange bug. Every week I have to erase this file because it increases like 10 GB and it consumes all my memory. I don't know what is this and why is it created...

LineageOS 14.1 20171009

OpenGApps stock 20171010

Magisk 14
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] IronTechmonkey:
That is odd indeed. On both Athene from this week and Osprey from a few months ago I see no such file of that name or file of that size. At that location both devices have the following files with none of them, being over 3MB

<datestamp> - power_supply_info.csv

<datestamp> - power_supply_info.csv.gz

power_supply_info.csv

The only other reference I can find for concate-power_supply_info.csv it is this post in Osprey Q&A thread: https://xdaforums.com/showpost.php?p=72818692&postcount=102

Whether not Magisk is the cause of this, IMO the next step would be testing a clean flash without Magisk and without any other system mod other than Gapps and LOS SU (for those who use SU). If it can be reproduced in a clean flash with no mods then it's a matter of drilling down into why it is occurring in those usage cases - and logging/creating a Jira ticket for it.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] alaindupus:
Thanks, I'll test my device without installing Magisk. Also, I forgot to mention, I have /data partition encrypted, with F2FS.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] gavron:
All of a sudden the Amazon Shopping App is unable to take pictures of gift cards (use camera to read QR code).

- I have tried a clean boot with *NOTHING* other than gapps and lineage OS and would not work

Suggestions welcome.

E