yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI the LOS SU packages have been updated (now bearing the LOS version to which they pertain in their file names) and if you use the old one bad things may happen (bad behavior in apps requiring root, including spontaneous reboots). I usually check for updated LOS SU packages when downloading ROMS but neglected to do so this week, so more fool me, however if they have changed then IMO there should have been an update about it in the LOS Blog.

It might be the case that the LOS SU packages have not actually changed but were just re-generated with the new names, as possibly implied by this note in a non-related Jira ticket: https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-15523, in which case there may be issues in the ROM (although no apparent reports of such at Jira). The device specific change-logs are down and I see no mention of a new SU package in the general change-log, which certainly does not help fill in the information gapps

[EDIT] Although change-log is not populating to previously created bookmark ("err09: Bad data or no nightlies for this device yet.") it is available from the "Show merged changes..." link, so this probably has to do with the a site redesign (in which captcha may also have recently introduced). That being said, the rollout of all of these changes could have been tidier.

[EDIT2] Another Clean flash of ROM, Gapps, new LOS SU with-nothing but one file manager installed (MiXplorer) = same problems. Also the native Files app reports errors deleting files on internal SD even though the files seem to be deleted. Either there were substantial changes made to the way the LOS SU package works or there is a serious problem. IDK if this is Osprey specific but wont have time to re-flash and test again for a few days.

[EDIT3] Correction: This issue is not related to SU, and there should be no issues with the new LOS SU package but there are issues with some apps rewriting or deleting files. This commit should fix it in next build https://review.lineageos.org/#/c/178062/, and there are some more details here https://android-review.googlesource.com/#/c/419020/ and here https://android-review.googlesource.com/#/c/421400/.
[Moto G 2015 Original Android Development] pjc123:
So, we are supposed to be matching the Lineage OS download with the su download of the same date (if a matching date becomes available that is)? Oops, I have been dirty flashing for months, and never checked this!
[Moto G 2015 Original Android Development] IronTechmonkey:
AFAIK it has only been updated once or twice so not a direct date match, but it's always a good idea to check to see if it has been updated. That being said, the reported issue flashing Osprey June 22 occurred with both the old and the new LOS Su packages.
[Moto G 2015 Original Android Development] pjc123:
I see, thanks. I will keep this mind going forward.
[Moto G 2015 Original Android Development] guest_2011:
I use aquamail. It's always active. Any other personal info gets logged that i should remove?

I started Matlog in the morning because i can't control when wifi disconnects. Can happen any moment, so it will probably be a huge log?
[Moto G 2015 Original Android Development] KrisM22:
Just do a search on the text file for your email addy and remove it.

Also search for your IMEI and remove it.

Long is okay but I assume you will stop it very shortly after it disconnects, so I can ignore anything but the past minute or 2. You could snip all but the last 5 minutes.
[Moto G 2015 Original Android Development] guest_2011:
I don't even know how long is too long. App has a setting to omit stuff like email, url. I use it in the evening, go to bed, wake up, wifi still on, i use it for a bit, put it aside, come back to use it again, no internet access. Sometimes i use it for an hour and it disconnects suddenly, sometimes half a day, sometimes longer. Very unpredictable behavior. I remember it started last builds of May.
[Moto G 2015 Original Android Development] KrisM22:
Murphy is very clear about things like this - when you're watching it closely, it won't fail. :) I'm beginning to think I will see a loss of signal. - not a rom problem at all.

EDIT - if you have a long log, just stop matlog and throw it away and start it again. Just tell me the aprox duration you threw away - 1/2 day, day, etc.
[Moto G 2015 Original Android Development] IronTechmonkey:
Pardon this bit of repetition but I wanted to flag a correction in regards to the issues that I mentioned here, https://xdaforums.com/showpost.php?p=72769335&postcount=4954

"[EDIT3] Correction: This issue is not related to SU, and there should be no issues with the new LOS SU package but there are issues with some apps writing or deleting files. This commit should fix it in next build https://review.lineageos.org/#/c/178062/, and there are some more details here https://android-review.googlesource.com/#/c/419020/ and here https://android-review.googlesource.com/#/c/421400/.

Depending on what apps you use and what you use your device for this issue may have bad consequences (as was the case for some apps that I use to manage and edit files) or not.
[Moto G 2015 Original Android Development] guest_2011:
exactly. i've been recording and restarting rec again since early am and still no wifi disconnect.

update: maybe because i spent most of the day away from the phone. it's evening, wifi still connected. nuts!
[Moto G 2015 Original Android Development] Thermalcake:
"Free up space" option in the context menu should detect that there are downloads in the Download folder. It always says "0 bytes" no matter what. See the screenshot I attached.
[Moto G 2015 Original Android Development] KrisM22:
Yes. The long delay is me trying to find an answer, in terms of what the Nougat manual says. Or doesn't. Only the below pic so far from a pre Nougat release. The manual says nothing.

However I can say that "Downloads" (with an s) may refer to downloads but not necessarily limited to the Internal Storage folder "Download" (no s). Also I note there is no Apps folder so it may just refer to any ".apk" in any folder in Internal Storage. But I can't find Nougat instructions saying so (been looking at G5). I will keep looking but if you want to delete a file I think the attached page says something about it.
[Moto G 2015 Original Android Development] KrisM22:
[MENTION=5126823]bhishmar[/MENTION] I have moved 9 posts to

https://xdaforums.com/2015-moto-g/help/questions-flashing-gapps-t3627211/post72804174#post72804174
[Moto G 2015 Original Android Development] KrisM22:
changelog is back.
[Moto G 2015 Original Android Development] braddocksp:
Is posible to repair or make to work miracast? Never user it, but the last month for work in the car of bussiness uses a radio with miracast and the gps is very util. Only stock can run, all roms i have tested none....
[Moto G 2015 Original Android Development] KrisM22:
I think that topic would be much more appropriate in the Q&A forum.
[Moto G 2015 Original Android Development] guest_2011:
i think i know what my problem was. Coincidentally as i was updating lineage, besides BT/wifi signal related bug which i haven't tested in a while, from late May until several days ago i started getting "no internet connection" in some apps while others could connect. I tried disconnecting/reconnecting to wifi. It happened regardless if i was mobile or in one place. Public hospots or home router. Sometimes none of my apps could connect. Soft or hard restart helped fix wifi connection temporarily. Sometimes it happened once a day, sometimes i restarted 2-3 times a day. A few days ago disabled Adguard. Haven't had wifi disconnects since. It also consumed 13% of the battery which i think may be too much. First disabled and then downgraded to an older version. No wifi problems since. I have yet to test if BT still disconnects in new builds.
[Moto G 2015 Original Android Development] KrisM22:
a) great!

b) why did you downgrade?
[Moto G 2015 Original Android Development] guest_2011:
i wanted something stable. in my other phone older version didn't give me any problems so i downgraded.
[Moto G 2015 Original Android Development] KrisM22:
Okay.

I use Block This! . google for it.
[Moto G 2015 Original Android Development] IronTechmonkey:
In re 3rd party issues, among other things expected in development threads:

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

The last time Alberto97 posted in this thread:

https://xdaforums.com/showpost.php?p=70740011&postcount=2548
[Moto G 2015 Original Android Development] KrisM22:
I scan reg and bug in jira regularly. I see a reg that has been closed because it's a bug(never worked). I have a suggestion for person but can't contact them because the name they use on jira is different from the one they use on xda. Consistency helps... :)

edit: found them.
[Moto G 2015 Original Android Development] Krishna00:00:
Does this Rom has OMS support?
[Moto G 2015 Original Android Development] IronTechmonkey:
If you are talking about Substratum with OMS (as opposed to Open Mobile System which is a different OS) this line from a Jira ticket in which problems with Substratum were reported may be your answer. "This looks like a substratum/OMS issue to me. We don't support OMS. Some people have supposedly gotten it to work under some circumstances but it leaves a mess in the ROM and it would be off topic for this thread.
[Moto G 2015 Original Android Development] braddocksp:
In the Q&A exist a miracast post. Querying for a rom with 7 and miracast, but my question is for LineageOS ROM, same as other problems or bugs posted here. Miracast with builp.prop line activated, and the option to enable wifi display. Try to connect but not succefull. Is a bug or problem. I supect as a general bug of al N roms, all AOSP and LineageOS tested, same problem. But I hope Alberto97 to say some light.

But I have used always cm and later lineageos, was my principal rom, and now i have return to stock for this....
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm sorry to be so direct but just saying it does not work is repeating what is already known and is useless to hear again. If you search the thread (as we are all expected to do) you will find that Miracast requires Xposed which is off topic.

If you want to do something about it and contribute to development of the ROM (the purpose of this thread) then submit a proper bug report at Jira (for which links have been provided many times in this thread).

As to reporting issues on XDA, a link was posted to a guide that tells you how you can do that just two post up from yours.

Please respect the XDA rules and expectations of development threads, which are different from Q&A and tech support threads.

[EDIT] there are 4 reports of Miracast issues at LOS Jira. One of them was filed five months ago and was fixed for one particular device at least for a while. The other three were rejected because they were filed as regressions instead of bugs. If you want to fixed (if it is even a bug) then file a bug report at jira.
[Moto G 2015 Original Android Development] n33raj18:
My phone's screen turns off the moment I receive a phone call. It doesn't come back up until the other person cuts the call. The screen can then only come back after long pressing the power button.

I also have the "Volume buttons wake up device" setting on, but hey don't turn the screen on after the call.

Is this a known bug?
[Moto G 2015 Original Android Development] IronTechmonkey:
https://xdaforums.com/wiki/Reporting_A_Problem_-_Android
[Moto G 2015 Original Android Development] KrisM22:
+1 to [MENTION=5119654]IronTechmonkey[/MENTION] 's answer.

Yes, I have heard of it. Tell me exactly all the apps, kernels, and mods you have put on your system of what ROM and what gapps, and what themes. It is an apps problem.
[Moto G 2015 Original Android Development] n33raj18:
I tried recalibrating the proximity sensor and that seemed to solve the problem. If the problem comes back, I'll report back with the log and other necessary details.

---------- Post added at 05:51 PM ---------- Previous post was at 05:45 PM ----------

I am on the 2017-06-22 nightly with nano ARM opengapps. I have the su package installed to use AdAway. I have no other modules, extensions, theme etc from outside the play store installed at all.

I apologise if I came across as entitled with my original post. I flashed it for a friend and don't have the phone on me right now.

Also, like I said in my earlier post, I recalibrated the proximity sensor and that seemed to have done the trick, at least for now.
[Moto G 2015 Original Android Development] KrisM22:
No apologies needed - it problem recurs, delete adaway for a bit and see what happens.
[Moto G 2015 Original Android Development] IronTechmonkey:
It not a matter of opinions about seeming entitled, no one criticized you for that. There are just expectation for bug reporting in development thread.
[Moto G 2015 Original Android Development] :
Downloaded and installed new Update of June 22, And Stuck at Flashing the ROM at " Patching system image unconditionally...." Please help, what to do, updated like 3 times before, never happened like this.
[Moto G 2015 Original Android Development] KrisM22:
My bet is you didn't follow the instructions in the OP.
[Moto G 2015 Original Android Development] KrisM22:
Please remember folks that you can't file a "regression" unless you have a previous OFFICIAL LineageOS build THAT WORKS. It will simply be closed. Wait until the weekend and file it as a "bug".
[Moto G 2015 Original Android Development] teensheet:
Are the bugs still bugs or have they been fixed?:fingers-crossed:
[Moto G 2015 Original Android Development] damianx5:
Anyone else missing now on tap in the build?
[Moto G 2015 Original Android Development] di__bi:
Just use cm13. I switched back to cm13 because its not stable enough for me.
[Moto G 2015 Original Android Development] Mimisf:
It never crashed on mines and I have it installed since 27 or 30 of September (can't remember). Rock solid!

Moto display just lets you peek at your notifications and tells you more information than it should IMHO. ambient display is better privacy wise...
[Moto G 2015 Original Android Development] ContractorDude:
Working for me. I have open gapps micro installed
[Moto G 2015 Original Android Development] WaxysDargle:
This ROM is a daily driver for sure. Every once and a while an app will crash the first time it runs but it's always good after that
[Moto G 2015 Original Android Development] AjayV01:
Yes
[Moto G 2015 Original Android Development] Mkfermam:
Hey guys, I need a help. I have two bigs problems:

1) Min cpu frequency is stucked in 800Mhz. I change it in Kernel Adiutor, but after a few minutes, min freq is setted automatically in 800mMhz again.

2) Cell broadcast transmission continues with annoying messages. I deactivated all in messages config, but one continue marked on.

Another minor bugs: battery icon, live display dont set night color temperature, PIN configuration crashing when click, weather widget is crashing too.

Camera is working for photos and videos normally for me.

Im appreciate some help for anyone. Sorry by bad english. Thanks.
[Moto G 2015 Original Android Development] keeithlv:
Update to Nightlies

So I've installed this. Just wanted to know, once the nightlies come can i just update it by flashing it over this or do i have to do a clean install again?
[Moto G 2015 Original Android Development] Gravemind2015:
Do a clean install for the first official nightly. Then you can just dirty flash new faily builds.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] keeithlv:
Would it be a problem though if I dirty flashed it?
[Moto G 2015 Original Android Development] Gravemind2015:
Not necessarily, but no harm in staying at the safer side :victory:

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] keeithlv:
True that. Thanks!
[Moto G 2015 Original Android Development] CypherPotato:
any fix for the bugged camera??

if I replace the cm package camera files by the stock rom, it will work? :p
[Moto G 2015 Original Android Development] Gravemind2015:
There will be a fix when the fix will be discovered. This is not like mediatek porting, so simply replacing files (that too from marshmallow to nougat) and giving permissions might not be enough.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] CypherPotato:
this means that ROM is still under development? I thought it had been abandoned :P
[Moto G 2015 Original Android Development] Gravemind2015:
It's still WIP. It's not abandoned as long as dev himself says it. Dev is working offline in his free time, just give him his time, and as always, I am pretty sure he would come with something impressive [emoji106]

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] hareshsangar:
Check This One

http://xdaforums.com/showpost.php?p=69001639
[Moto G 2015 Original Android Development] Chinfuk:
Gapps?

Hi, forgive me if this is stated somewhere but I'm a little confused about gapps. You say without the need for Google apps but also state we need to flash the gapps zip, where is it please. also how will I update this app in the future say if the camera issue gets fixed. Many thanks :)
[Moto G 2015 Original Android Development] Gravemind2015:
Flashing gapps is optional. Most of the people need play store, thus they need gapps. But it has to be done along with the rom install, flashing it later on will give force close error messages. That's why it's included in the steps to install the rom.

Multiple variants of gapps exist, say OpenGapps, Bank Gapps etc. I use OpenGapps Pico.For opengapps, its- www.opengapps.org

Dunno about some app you were talking about.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] IronTechmonkey:
+1 to that reminder. From looking at the Jira activity stream it seems that many people, perhaps new to the system, report potentially valid bugs as regressions which were then rejected. That does not mean the problem itself was reject but rather that the way it as reported was rejected. In those cases it may be well worth the minimal additional effort to refile the report as a bug. One example is Miracast. As mentioned a few pages ago, there have been several reports that were rejected because they were bugs filed as regressions. If those are refiled properly as bugs they might be fixed or at least we might learn about why they may not be fixable.
[Moto G 2015 Original Android Development] IronTechmonkey:
More issues with LiveDisplay, with possible connection to GPS-on for a certain duration. Observed on Peregrine but would probably occur on Osprey also under same conditions: Details in this comment at Jira: https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-15286.

[EDIT] These observations are from the June 15 build so it's possible there have been changes, although nothing at jira or in the change logs indicates that there has been an additional fix. Just worth keeping an eye on.
[Moto G 2015 Original Android Development] KrisM22:
What a mess... :(
[Moto G 2015 Original Android Development] IronTechmonkey:
That could be said of LiveDisplay, or the NYC traffic referenced in the Jira ticket as the reason I could not log it. :)

At least in these instances it is a matter LiveDisplay being an hour behind schedule rather being several hours off or not invoking at all. Thinking back a few weeks there was one instance when the system time was off by an hour until going on line after a TWRP session so there may be some underlying time time-keeping issue in this case.... speaking of which...

Although I see such timekeeping issues rarely in Osprey and Peregrine LOS, in Otus LOS the system time is off by several hours until web connection after every reboot. Having just flashed CM12.1 on Otus and seen no such timekeeping issues at all (in fact TWRP and OS are now even using the same time on that device), I think there may be some timekeeping issue between LOS and TWRP.
[Moto G 2015 Original Android Development] ChExMo:
Hi there...

I've not been in xda since i flashed my Defy+ almost everyday and CM10 ruled da world lol

Now I'm back with a xt1540...

I've already read great part of the thread and the LOS page... It is absolutely not clear to me what are the main and/or significative differences between an standard (for example, the aosp (taking account there is not an official Android 7.1 Update for this device)) and LOS14.1

I know there are changelogs everywhere, but it's an exhaustively long detailed source and, in the end, it does not add any relevant information to a not-expert (like me, and many other users)
[Moto G 2015 Original Android Development] KrisM22:
Have you read the OP for this thread? Start there.
[Moto G 2015 Original Android Development] ChExMo:
Obviously yes.

It sounds like I'd have to install it and prove it myself.
[Moto G 2015 Original Android Development] KrisM22:
The Q&A forum is the place for questions like that.
[Moto G 2015 Original Android Development] Arshadhack:
Guys give solution

I flashed this ROM n it's pretty good ROM

But I'm facing battery dry up when I'm I'm using net plzzz give me suggestions
[Moto G 2015 Original Android Development] IronTechmonkey:
Start with a clean flash. There have been recent reports in the Moto Peregrine thread about higher battery drain being caused by some Google services which got better after a clean flash.

Beyond that, the suggestion is to establish what is causing the power drain and if the drain is outside of normal expectation for this device. If it is caused by the ROM.(which is unlikely) then troubleshoot and submit a bug report. If it is an issue with an app (more likely) then find a forum for the app and post there. To determine what is causing the drain you can use Better Battery Stats https://xdaforums.com/showthread.php?t=1179809.
[Moto G 2015 Original Android Development] Arshadhack:
Thanks bro

---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------

Bro I have another question that I had unlocked bootloader and install twrp also

Now tell me how to root mr phone
[Moto G 2015 Original Android Development] Subinsmani:
Regards Root, bootloader, twrp doubt will clear from this thread,,,

https://xdaforums.com/2015-moto-g/general/guide-osprey-moto-g3-begin-how-to-t3599251
[Moto G 2015 Original Android Development] IronTechmonkey:
Let's clear something up first: "Bro" implies familiar, young and male... but the world, including XDA, is a bigger place than that.

As to root: LOS is natively rooted and there is an SU package that manages SU permissions. I would advise doing some research about flashing and rooting since this thread is supposed to be focused on testing the ROM.

---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------

You ninja-ed me, and with better advise too. :)
[Moto G 2015 Original Android Development] KrisM22:
cheese, to think I missed all that. :D
[Moto G 2015 Original Android Development] KrisM22:
wanted to see this in there...

https://xdaforums.com/wiki/Reporting_A_Problem_-_Android
[Moto G 2015 Original Android Development] IronTechmonkey:
I was wondering when that one would end up in there. When I was writing a FAQ focused on bug reporting (as opposed to flashing as yours does) I found that wiki page which precluded much of the FAQ I was writing.

Apologies for the OT but it will become on topic when I finish this keyboard test (typing via OTG USB keyboard ATM) and report shortly.
[Moto G 2015 Original Android Development] KrisM22:
No prob - I would have posted it earlier but restored my os at least a dozen times tracking a linux prob and lost the bookmark for it - had to go find it. All is fixed and I'm even finally on 6-29.
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for including it. No criticism implied. My post was an excuse to test keyboards, as if I did not already type enough. :)
[Moto G 2015 Original Android Development] Arshadhack:
Thanks bro