yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] Gravemind2015:
In mid-2017, my osprey started restarting when the battery was below 50% (sometimes below 30%, sometimes even on 40-45%). My battery was acting up, it even started restarting when I launched camera. Actually any resource intensive work that requires more power was causing a reboot. Replacing the battery fixed it.

But, as you're experiencing this after updating, I'd recommend you to take a full nandroid backup using TWRP, then clean flash the build you're having the problem on. Charge up to 100% and use it till you reach 59% and see if it reboots.

If it does, then clean flash (i.e wipe again) the last build you remember that worked properly and again check if it persists.

If it persists in both of them, then your battery is likely aged. If it gets fixed in older build however, you can file a regression report in JIRA, citing the builds where the problem occurs and the build up to which it worked fine.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] angel6700:
Thank you for your detailed answer.

I hope i still have a not so old version around... In lineage downloads there are only three last four..

Will try your ideas.

Regards.
[Moto G 2015 Original Android Development] rtrock:
More often than not , it will turn out to be a battery ageing issue coz a sudden drop in the battery level and then turning the phone into shut-down mode has been the old-school issue of "battery ageing" .

U can still try what the other members are cropping .

:)
[Moto G 2015 Original Android Development] angel6700:
So now, the problem could be outside this forum thread, as it seems nobody is experiencing the same behavior with the battery in last LOS 14.1 version.

BTW, I also noticed that charging while the phone is on, is extremelly slow (charging at <50 mA instead of 500 -900 mA, with the same charger)..

I will ask about batteries in a new topic in a different place.

Thanks.
[Moto G 2015 Original Android Development] anjanikmr39:
Wipe everything and install stock moto g3 ROM from XDA and then check if it is software problem or your battery problem. And if it is software wait for next update and if battery then change it. Actually after 2 yr of moto g3 battery drainage occur.
[Moto G 2015 Original Android Development] Porgos:
When will those changes be committed to the official nightly builds? Thank you for all your work.
[Moto G 2015 Original Android Development] x389sadas2:
Probably valid here as well:
[Moto G 2015 Original Android Development] LineageUser:
I installed Lineage OS a first time (actual: 14.1-20181006-NIGHTLY-osprey)

My Situation: DSL-Router (Fritzbox7590) with Internet Speed of up/down 50/10 Mbits/s.

Speedtest shows in normal condition on LineageOS normally around 38/10mbit, that is good because of the strength and traffic of my 2.4GHz network (i used different speedtests)

BUT:

When I switch on my Roku 802.11b Internet Radio device the up/down ratio drops to values lower than 2/1 mbits/s. It is clear that 802.11b devices can slow down WiFi but neither a MotoG5, Samsung J3 and A5 is affected so much neither did the Moto G3 with Stock Rom performed so poor when my Roku was on same Wifi-Network.

When i remove my Roku from Wifi-Nework, Wifi throughput is good again. I think this is a bug. LineageOS is affected to much from slow Roku 802.11b device
[Moto G 2015 Original Android Development] IronTechmonkey:
That might indeed be an LOS 14.1 bug/limitation but you may be in a narrow usage case (i.e. not many other people experiencing this). If you can reproduce this in a clean flash of latest ROM build with no 3rd party modifications/factors then you should consider providing a complete bug report at LOS Jira (official problem tracking system for LOS https://jira.lineageos.org) as well as here. You've already got some good details but your report should also include specific step-by-step description about how you reproduce the issue as well as a log taken while you reproduced it.
[Moto G 2015 Original Android Development] :
tell me what im doing wrong another clean flash new Lineage, and my camera still not working prioperly, after some pictures camera just close by it self, in every lineage build i have the same problem
[Moto G 2015 Original Android Development] IronTechmonkey:
Nothing has changed in the ROM to affect this (or unfortunately in your approach to the issue) since here: https://xdaforums.com/showpost.php?p=77559591&postcount=5930. If you think it is a real bug (which seems unlikely at this point) then please create a proper bug report. If you don’t want to do that then please use the Q&A thread.
[Moto G 2015 Original Android Development] Porgos:
I'm ready to install this on my wife's phone. Should I go with the latest LOS build or the Wi-Fi test build posted on page #592?

Thank you in advance!
[Moto G 2015 Original Android Development] IronTechmonkey:
IMO, go with latest LOS build. IIRC the commits from the test build have made it into the general distribution, and those which did not would have been omitted for a reason. Additionally the ROM will have received other universal non-device-specific patches since the test build (although none in the past few weeks).
[Moto G 2015 Original Android Development] Porgos:
Thank you, will install it tonight along with pico gapps and the Squid kernel. Indeed, there haven't been any changes logged for 3 weeks for this device, any idea why?
[Moto G 2015 Original Android Development] IronTechmonkey:
Same for my other similar devices (Moto G Peregrine & Moto G4 Athene). LOS 14.x is relatively mature and dev focus may be turning towards LOS 15.x. It's not uncommon to see lulls such as that.
[Moto G 2015 Original Android Development] :
i wanna raport bug, is there any way to do this?
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes there is; As described in replies to 2 previous posts of yours, you can report bugs at LOS Jira (Lineage OS' official problem tracking system) and in this thread by including detailed descriptions and logs.

[EDIT] This XDA wiki article gives a good general description of bug reporting expectations. https://xdaforums.com/wiki/Reporting_A_Problem_-_Android.

For Jira, there are descriptions at the website and descriptions as you go through the process.

If you would like more detail than was previously provided about bug reporting or would like help walking through the bug reporting process, it would be more appropriate to do that in the Q&A thread, then bring the resultant bug report to this thread and Jira.
[Moto G 2015 Original Android Development] IronTechmonkey:
Superfluous post, text deleted.
[Moto G 2015 Original Android Development] jeferson1979:
lineage-14.1-20181103-nightly-osprey-signed.zip last build bootloop
[Moto G 2015 Original Android Development] contructor0:
First boot seems to bootloop for me for a few minutes. Restarted and managed to get to set up screen.
[Moto G 2015 Original Android Development] positivetourettes:
me to, 1st bootloop after its ok
[Moto G 2015 Original Android Development] IronTechmonkey:
Interesting. [MENTION=8863813]jeferson1979[/MENTION], [MENTION=9540784]contructor0[/MENTION] and [MENTION=9531940]h4x10r[/MENTION]; did any of you by any chance dirty flash or restore any system components (as opposed to just apps) from backup (TiBU)?

I don't ask this in order to nag about the virtues of clean vs. dirty flashing (although that is something I would do in a different context :silly:). The reason I ask is because there is definitely something different in this build (across multiples devices) which might explain why there could have been problems dirty flashing this build even though there were no problem dirty flashing previous builds.

I cannot figure out exactly what changed but here is how I experienced it: After flashing the same build on Moto G4 Athene, the Titanium backup settings were not transferred to the newly flashed build as they usually are. Typically that only occurs when I flash a different version of LOS or when storage volumes are changed. After seeing your posts I clean flashed Osprey which yielded the same result (and I’ve since walked back both devices to previous build).

The changelog of commits (many this week, after some quiet weeks) for both devices is the same https://www.cmxlog.com/14.1/osprey. Although I see no obvious culprits, I'm wondering about the tzdata commits. Perhaps there is some causal commonality between our experience.
[Moto G 2015 Original Android Development] contructor0:
I must say that before this time the last time I flashed phones were Xiaomi's 5 or 6 years ago. So I definitely stumbled across things when I tried to do this past weekend and may have ended up in a dirty state. Here is what I recall:

Follow Moto unlock bootloader procedure (first time failed because did not enable unlock bootloader in Developer)

Rebooted phone and set up, access developer options and enable debugging

Installed TWRP recovery, wipe phone (default TWRP wipe, did not use advanced)

Flash Lineage, press wipe button after TWRP flash

Flashed OpenGApps, but used the wrong ARM64 version, did again using ARM (this may be where it went wrong?), press wipe button after TWRP flash

Restart, got stuck for a few minutes, force shutdown, wanted to restart into recovery but accidentally restarted to OS and booted fine
[Moto G 2015 Original Android Development] IronTechmonkey:
Clarification about dirty and clean flash:

Dirty Flash = Install ROM and gapps updates on top of same Android version - only wipe davik/system caches. Dirty flashing is not bad, in fact it is an intended update path for LOS but once potential ROM bugs are identified a clean flash might be required for comparison.

Clean Flash: Install ROM "clean" on device which has been "factory reset" or "full wipe(d)" before flashing. At the cost of extra time, clean flashing typically yields more stable results, and once potential ROM bugs are identified a clean flashed build is a good bug reporting starting point.

It sounds as if you were dirty flashing which is consistent with my hypothesis: That something in the ROM has changed; and the thing that changed was a dependency for dirty flashing and for Titanium backup to properly migrate settings. I suppose it also must be considered that maybe your device was not given enough time to boot and that it would have booted fine if given more time. In any event, IMO, what you experienced might not have occurred with clean flash, and if you made it through I'd suggest running with it unless problems arise. I'm going to see if more can be learned about what has changed before committing to manually rebuilding TiBU settings on 3 devices.
[Moto G 2015 Original Android Development] jeferson1979:
Bootloop dirty and clean flash, back to earlier build, untill fix, cannot do a logcat at the moment
[Moto G 2015 Original Android Development] Komapatient:
No bootloop on my device.

Dirty flashed as usual, no Titanium Backup or Magisk installed. Only LOS SU.
[Moto G 2015 Original Android Development] positivetourettes:
I do clean flash like always, i have to many power wakeclocks and do deep sleep state
[Moto G 2015 Original Android Development] IronTechmonkey:
[EDIT] See answer in Q&A. https://xdaforums.com/showpost.php?p=78092762&postcount=474
[Moto G 2015 Original Android Development] jeferson1979:
Flashing with magisk 17.2 it works
[Moto G 2015 Original Android Development] IronTechmonkey:
What were you using before? SuperSU? LOS SU?
[Moto G 2015 Original Android Development] jeferson1979:
Magisk 17.1. Didn't take log, my bad, i was out of time. For you knowledge, my device: Osprey 1gb Ram 8gb ROM XT1543 :cowboy:
[Moto G 2015 Original Android Development] isaacnoroncaasi:
AudioFX is still not functional (at least, not in stereo). I've tried V4A, but I don't feel comfortable with the idea of setting SELinux to permissive. Is there any fix? In case there's not, can anybody recommend another audio mod for this device that doesn't require to change SELinux settings?
[Moto G 2015 Original Android Development] Zenzfum000:
Is anyone facing problems with proximity sensor?
[Moto G 2015 Original Android Development] x389sadas2:
Hi,

i had posted the issue below which persists up to now but i wasn't able to pinpoint the issue yet. There is another user reporting some proximity issue which i have quoted below as well.

Both posts can be easily found when doing a search in this topic: https://xdaforums.com/search/thread/3466246?query=proximity
[Moto G 2015 Original Android Development] IronTechmonkey:
Don’t forget this though; A few posts later there was this confirmation from same person that the issue did not persist in that case: https://xdaforums.com/showpost.php?p=77560861&postcount=5931.

Not to doubt that this could be an actual LOS bug but there has not been any real evidence presented to convince people that is so or to help developers fix it in the case that is is an LOS bug.

For those who think this is a bug and can reproduce it (in a clean flash with no 3rd party modifications) the way to address it would be to create bug reports at LOS Jira (https://jira.lineageos.org) and here, containing step by step description of how to reproduce it the issue (list every action taken) and a log captured while it was being reproduced. That's all just SOP for bug reporting.
[Moto G 2015 Original Android Development] mentat:
Greetings,

I just noticed another build today...

lineage-14.1-20181121-nightly-osprey-signed.zip

with no apparent (recent) changes from the previous day...

lineage-14.1-20181120-nightly-osprey-signed.zip

Does anyone know the reason for this (should it be flashed)?

Thanks.
[Moto G 2015 Original Android Development] IronTechmonkey:
In short - there's just not much going on. In more detail, this has to do with the general and device-specific progression of development. In general: The LOS 14.1 ROM is fairly mature so there are not as many updates as in the past. For instance, except for one big batch of non-specific commits last week we've not had updates for many weeks. This is the case for many devices, including my Peregrine, Osprey and Athene. If there are no new commits and you are not chasing any bugs there may not be much point in updating. That being said, there are occasional instances where the maintainer(s) of a device may add some commits that don't appear in the LOS change-log but at this late point in LOS 14.x development if that were occurring we'd likely hear about it from squid2. BTW, if you review squid2's recent posts you may learn more.
[Moto G 2015 Original Android Development] mauriciognr:
Hey guys, heres i little video i made. Antutu benchmark running on a Xt1540 with LOS 14.1

Video: https://www.youtube.com/watch?v=Vt9As3WDgI8

[YOUTUBE]Vt9As3WDgI8[/YOUTUBE]

---------- Post added at 05:59 PM ---------- Previous post was at 05:59 PM ----------

Hey guys, heres i little video i made. Antutu benchmark running on a Xt1540 with LOS 14.1

Video: https://www.youtube.com/watch?v=Vt9As3WDgI8

[YOUTUBE]Vt9As3WDgI8[/YOUTUBE]
[Moto G 2015 Original Android Development] TheForce:
[MENTION=6485916]squid2[/MENTION]

Thanks that you found some time to update this rom.

It is a great rom.

Have a nice time with Xmas ? and new year ??

And of course for everyone of the community ☺️
[Moto G 2015 Original Android Development] alienhead13:
I updated my osprey from 20180526 via the LOS updater.

Now the sim card is not recognized anymore (baseband "unknown") :( what should I do to fix this?

I reflashed 20180526, but the problem persists :crying:

edit: I just found this: https://xdaforums.com/2015-moto-g/help/unknown-baseband-flashing-nightlies-t3714477

but after

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

the problem still persists

edit2:

I did a factory reset reinstalled 20180526 and updated to current version via LOS updater. Now everything works....:good:
[Moto G 2015 Original Android Development] positivetourettes:
im f@#$% tired of linerage and 0 response for problem, i have weakelock on every build ALARM wakelocks non stop , i just flash lastetst build 2 days ago and never even topuch alarm clock and today i had 15h wakelock ALARM system lineage, i send jira and develepers dont want to repair this, ffs this system is no usable with this ****
[Moto G 2015 Original Android Development] htw1:
After 1 year of working on my phone I can say, this rom is perfect.
[Moto G 2015 Original Android Development] guest_2011:
i haven't touched my phone in a long time. are older builds available for download? can you go back to older before problem started? i don't have any noticeable issues with older, october november builds.
[Moto G 2015 Original Android Development] positivetourettes:
lol i have this problem on 2 ospreys phone about 3-4 months in every build, EVERY
[Moto G 2015 Original Android Development] guest_2011:
strange. i'll try to update soon and will report if any problems.
[Moto G 2015 Original Android Development] IronTechmonkey:
Perhaps you have discovered a bug the exists only in narrow and specific usage cases or perhaps you are having the same non rom related issue on both devices. The information that you've provided here does not establish either so you are in no position to insist that it must be a ROM issue.

If you want to establish this as a ROM issue and gain support for the issue* then:, In addition to reproducing and logging the issue in clean flash of the ROM making sure not to introduce any 3rd party factors (eg no dirty flash, no Xposed, no superSU, no Magisk, no vyper audio, etc) which is assumed you did if there is a J/ira ticket, then please also share the jira ticket here so others may add notes and or vote on it.

* A bit of advise: Without good bug reporting information, others wont be able to or wont bother to try reproducing the issue. Also, if you are an arse to the developers (who's work you get to use for free and who do this work in their own time around real lives) you undermine your own cause. We are lucky that we have a maintainer at all, and even luckier to have squid2 who's work supports a whole tree of Moto device models.
[Moto G 2015 Original Android Development] positivetourettes:
This is on clean flash rom on both phones, i send the jira
[Moto G 2015 Original Android Development] immich:
I like more the Aosp, but I'm very happy than someone made a version from 7.0 to dual sims devices, thanks Alberto I'll flash it at afternoon
[Moto G 2015 Original Android Development] Mimisf:
I am soooo gonna try this!!

WELL DONE ALBERTO!! Thanks!!
[Moto G 2015 Original Android Development] Śūnyatā:
Amazingly stable for the first release!

Only thing I noticed is on latest Google camera, the preview on video is crazy upside down and stretched.

Edit: after a few camera launches the graphical glitch has gone.
[Moto G 2015 Original Android Development] amansingh63:
Your zip file is corrupted.. try testing your zip file with win rar.. there must be error in file.. i installed perfectly on xt 1550 with llatest recovery.
[Moto G 2015 Original Android Development] Mimisf:
Redownload the zip. The file is probably corrupted
[Moto G 2015 Original Android Development] Majid2000:
Installed google camera.. But when I try to use camcorder.. It says can't connect to camera. Any solution?
[Moto G 2015 Original Android Development] Śūnyatā:
Did you set to 720p? It will only work in that resolution at this time.
[Moto G 2015 Original Android Development] Majid2000:
Just did it. Problem solved. Thanks!
[Moto G 2015 Original Android Development] robot_head:
Strange, couldn't get these quick setting tiles to do anything
[Moto G 2015 Original Android Development] samir.saurav:
Thanks. It work after re-download.
[Moto G 2015 Original Android Development] valkaizer2594:
your phone gets doomed
[Moto G 2015 Original Android Development] samir.saurav:
I wanted to install google camera but didn't find it in play store. Where did you get it from?
[Moto G 2015 Original Android Development] Majid2000:
http://www.apkmirror.com/apk/google-inc/camera/ You're welcome ;)

---------- Post added at 02:23 PM ---------- Previous post was at 02:23 PM ----------

How to get rid of the yellowish tint?
[Moto G 2015 Original Android Development] gp_sousa:
Working perfectly!

I started using this ROM now, and so far has behaved very well. All resources (at least the ones I use) and are in full working order. Congratulations to the developer. Very fluid and stable. If I have a problem later post here in the forum.

OBS .: Forgive me for the English, but as I have no command of the language had to use Google Translator, so there may be some flaws in the translation.
[Moto G 2015 Original Android Development] samir.saurav:
Disable Live Display option in display..
[Moto G 2015 Original Android Development] panagiotis15:
The Rom is working without any issues at all.I installed all the apps that i had to my 6.0.1 and till now everything works ok.
[Moto G 2015 Original Android Development] baggino:
There is missing FM radio - is a gaaps problem?
[Moto G 2015 Original Android Development] WaxysDargle:
has anyone tested bluetooth audio streaming yet?
[Moto G 2015 Original Android Development] samucastro:
where can i download Gapps for XT 1550?
[Moto G 2015 Original Android Development] dazeone:
Have you tried open Gapps micro
[Moto G 2015 Original Android Development] hossman:
I've been running this since released, with minimal issues BTW. This rom has everything I need.

Haven't tried anything else other than the initial AOSP ROM.
[Moto G 2015 Original Android Development] Tron_Legacy1680:
I just found an issue. I cannot receive calls from people. I can make calls and SMS but when someone calls me , the screen to accept or decline a call never comes up and the ringtone doesn't play either. I tried clearing data but it didn't work. So I tried clean flashing cm14 again but still didn't work. I then flashed stock and it works again now. Please fix this!

Thank you!

EDIT : Also sometimes when I open the Phone app it shows me a screen with 3 options return to call add a new call or use touch tone keypad
[Moto G 2015 Original Android Development] pave_07:
That's weird, didn't have any issue, did you try another phone app?
[Moto G 2015 Original Android Development] Tron_Legacy1680:
I tried to change it to truecaller but there wasn't any change in the interface of the call. Should there be any? Also after rebooting when I called someone and ended the call, it didn't end the call the call screen disappeared but the audio was still coming through the earpiece

---------- Post added at 05:29 PM ---------- Previous post was at 05:21 PM ----------

I downloaded the google phone app from the play store and now when I end call it is stuck on 'hanging up' and won't hang up. This is weird as I had been using the ROM for 2 weeks without a problem abs suddenly today this issus has come up
[Moto G 2015 Original Android Development] Flash_Aholic:
What APN info do you use? I have a zip I can flash for it but I always get a lot of drops on data
[Moto G 2015 Original Android Development] Hedied4me:
Yea a zip would be nice.
[Moto G 2015 Original Android Development] Flash_Aholic:
I have a zip but sometimes the data drops every now an then lol
[Moto G 2015 Original Android Development] robot_head:
If you use JRummys ZipMe app and go to this location on your phone and make a zip with any APN. XML file you see from marshmallow. Then try and Flash that on nougat.

Good luck. I would help but I don't have the same carrier
[Moto G 2015 Original Android Development] hossman:
I did not flash an APN zip, all I did was select LTE in preferred networks.

Everything has been good, other than a couple times switching from WiFi to LTE I had no data... Reboot and good. That has not happened in at least a week though.
[Moto G 2015 Original Android Development] Flash_Aholic:
See that's what's happens here lol and if I'm at work an don't have service ill sometimes completely lose data an have to reboot a couple times, but hmm I'll have to try that one an see how that works for me haha