yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI: In next build: Big batch of device specific commits related to camera, security, battery and other things: https://www.cmxlog.com/14.1/osprey.

Regarding the issues that were mitigated by modifying LMK (minfree) settings: I've been running the Jan 29 build as a phablet (no SIM) without those tweaks and having less problems as long as the LOS camera is not being used (that camera is just terrible on all devices). Also, the one other app that I was using to log those issue experienced an upgrade that renders it useless for those tests. Will regroup and retest after flashing next build.
[Moto G 2015 Original Android Development] IronTechmonkey:
If you think it is an actual bug in the ROM then create a proper bug report at LOS Jira (official problem tracking system): https://jira.lineageos.org/

If you are just looking for a quick fix or if this relates to 3rd party factors then try posting in the Q&A thread: https://xdaforums.com/2015-moto-g/help/rom-official-lineageos-14-1-qa-thread-t3545422
[Moto G 2015 Original Android Development] LenAsh:
Thread cleaned - please ask questions in the dedicated Q and A thread for this ROM HERE
[Moto G 2015 Original Android Development] puma1363:
hi.new update linage14.1 not dawnload .

OTA not work..ota and conectvpn or not dawnlod

sit linage and dawnload and not dwnload...link dawnload problem.(31/3/2018) plz fix link and file update osprey
[Moto G 2015 Original Android Development] Subinsmani:
What u want to say...

If u r asking about latest update...

Go and check Q&A thread, there [MENTION=5119654]IronTechmonkey[/MENTION] expalin the issue realated jenkin....

Man u do some research before posting ur confusing english...

Don't ask that where is Q&A thread, u r old member so u should know how to find the any thread and all...
[Moto G 2015 Original Android Development] puma1363:
Your new update is having problems. I encountered error 404 not found. Solve it. Instead of teaching English to me
[Moto G 2015 Original Android Development] Subinsmani:
Who are u to say to fix the link and all...

Who are u to order such thing???

Atleast u have show some respect to dev instead of demanding shuch thing here..

If there is no build then no build... Do whatever u want...
[Moto G 2015 Original Android Development] puma1363:
I'm waiting for the link problem to be resolved. My advice is with the creators of ROM rather than you. You can not help but waste time and fill out the user's page. I am asking the creators of Ram to fix the link. I do not need your help.

Copy me txt. I understand what you mean by Kanle. Nothing is mother tongue.
[Moto G 2015 Original Android Development] Subinsmani:
Sory u r in wrong thread or page my friend...

The creator of RAM is Samsung not alberto..

U need to ask Sumsung for ur Ram fix..
[Moto G 2015 Original Android Development] IronTechmonkey:
I guess people get irritable when they have to wait for the ROM. JK! :silly:

But seriously chill out., and let's take this to Q@A and try not to get modded again so soon: https://xdaforums.com/showpost.php?p=76088710&postcount=374
[Moto G 2015 Original Android Development] shadowbone:
3 different things I'd like to inform the dev's and others as well.

1. Firstly, thanks. Because disabling shutter sound for camera now, actually mutes it.

2. An occasional bug. That is I've put the display size to small. But every now and then, when I reboot, it reverts back to large size display. And then I have to manually adjust it again.

3. Has some enhancements been done as a theme or something. I'm asking this because certain apps like newsblur and resplash earlier used to have only dark or light themes choice. Now its giving me a 3rd one - black theme. (Doesn't seem to be an implementation by those apps AFAIK).
[Moto G 2015 Original Android Development] IronTechmonkey:
It seems more appropriate to answer this in Q&A so...: https://xdaforums.com/showpost.php?p=76134375&postcount=380
[Moto G 2015 Original Android Development] IronTechmonkey:
[MENTION=6485916]squid2[/MENTION]: Possible regression in March 31st build on 1GB RAM XT1540:

> Camera, Picture mode, flash mode greyed out (showing on, but not in effect and cannot be changed). Flash does not light when picture taken.

> In Video mode the flash works properly, as it also does in other camera apps (older version of Moto Camera).

> Also greyed out in Picture mode menu are: Exposure and white balance

> Athene running March 28 build does not have same issue.

I don't see any camera related commits since the Mach 31st build so will create a Jira ticket for this.... unless I find something wrong with my flash/restore routine (seems unlikely but worth checking with a re-flash if it's not a known issue).

[EDIT]

D'oh. This was a particularly bad face-plant on my part: I had accidentally enabled HDR mode from the top bar, which in turn disables those other options. No bug at all regarding camera, other than it being generally mismatched for 1GB devices and worse on Osprey but that is old news. Apologies for the false alarm.

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

I might as well follow up with this one while I' m here.

Unable to pair with BT keyboard. Fails with time-out at PIN entry regardless of keyboard interaction.

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

This is supposedly an old issue, although it only became apparent in the last 2 months of LOS 14.1 builds. For those who have BT keyboards which require PIN entry at the keyboard for pairing, look out for this: PIN must be entered within 2-3 seconds instead of 30-35 seconds which is the normal timeout. For the past 1-2 months it has occurred in every LOS 14.1 build on 3 different device with Logitech K480 keyboard More details in ticket.

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

Also, as to LMK stuff. The App I was using to test was fixed and can no longer be used as a test anymore, so it's back to the LOS camera or multi tabbed web browsing to force these symptoms.
[Moto G 2015 Original Android Development] adbhitman:
Anyone else have problems with gps? Somehow my phone can't find any satellites (device only) but I get location only throught network (high accuracy).
[Moto G 2015 Original Android Development] IronTechmonkey:
Working fine here in March 31st build. If you think it's a genuine ROM bug then clean flash, avoiding any 3rd party mods, reproduce issue while logging and report the bug at LOS Jira (https://jira.lineageos.org/) and here.
[Moto G 2015 Original Android Development] adbhitman:
Thanks for confirm it works. I think it is then probably just my problem. I have used about month builds from LOS14.1 that I have compiled from source. Everything else is working fine. I need to investigate or just go back to offical builds with clean install from LOS webpage.
[Moto G 2015 Original Android Development] Vvk380:
[MENTION=5119654]IronTechmonkey[/MENTION]Whatsapp video sharing working now on latest build ??
[Moto G 2015 Original Android Development] IronTechmonkey:
Q&A, answered here: https://xdaforums.com/showpost.php?p=76229251&postcount=397
[Moto G 2015 Original Android Development] visakhmv:
Still not working on April 21st build.

log attached from WhatsApp
[Moto G 2015 Original Android Development] abhimangalms:
Bug on Lineage 14.1 Moto G3

Lineage os 14.1 for moto g3 has a bug.

Automatic brightness is always on even after turning it of. Any fix or tips to get rid of that ?

---------- Post added at 07:21 AM ---------- Previous post was at 07:09 AM ----------

How to replace stock camera or any other app in lineage os with another app. ? is there any possibility ?
[Moto G 2015 Original Android Development] BenjyTec:
What do you mean by 'replace'? You simply can install another camera app from Play Store. Then you can set it as default app.
[Moto G 2015 Original Android Development] IronTechmonkey:
1) I'm not the developer so there is no need to notify me about this, in fact please stop doing that.

2) As has been mentioned before, if you think this is an actual bug then submit a proper bug report at LOS Jira:

https://wiki.lineageos.org/#report-bugs-1,

https://jira.lineageos.org
[Moto G 2015 Original Android Development] IronTechmonkey:
No similar issues here on Osprey (or Peregrine or Athene)

Q&A questions can go here: https://xdaforums.com/2015-moto-g/help/rom-official-lineageos-14-1-qa-thread-t3545422
[Moto G 2015 Original Android Development] theredbaron1834:
Seems we are about the only ones effected by this, though I am on athene. Pointed to you when I asked in an athene thread. Since it is so rare a bug, it would be hard to nail down a cause, so I plan on trying a fresh flash this weekend in hopes of fixing.

However, I also come with a mitigation. The app "Lux lite" can take over that option, actually disabling it. And the paid one lets you set a max brightness (aka, not over 75% for me), and still have auto on. It isnt perfect, as it completely controls brightness. No more mx player brightness controls, etc.

But it does work, dealt with this issue for a few weeks, till a few days ago when I found Lux, everything is fine now (except for a new lux notification).
[Moto G 2015 Original Android Development] abhimangalms:
I'm really sorry to say that, This will be okay after turning the "Live display" off :) which is seen right under the adaptive brightness.

It is my mistake that wasted your time.

Thank you for your patience and time. I'm appreciated.

And let me tell you sorry again.

---------- Post added at 06:44 AM ---------- Previous post was at 06:40 AM ----------

Im sorry that, I would like to replace the stock camera of lineage with pixel cam. Because it is (Lineage os) much more slow than the previous stock rom cam of moto g3. So is there any possibility to do that ?
[Moto G 2015 Original Android Development] theredbaron1834:
1st, then it is just me :), o well.

2nd, as for pixel cam,just install it, and it should just work.
[Moto G 2015 Original Android Development] pantxus:
Today I've got a zygote ask for root access.

Just informing
[Moto G 2015 Original Android Development] anisgvr:
What's zygote

---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------

No bug here
[Moto G 2015 Original Android Development] Gravemind2015:
Moved to the Q/A thread here.

[MENTION=5849836]pantxus[/MENTION]: Are you using Xposed or similar memory based mods? The reason I am asking is that I found folks having similar problems, for example hete and here.

The reply to the first link has a way to determine if a fake zygote is asking for the root access. You'll have to run :

ps | grep zygote

in a terminal emulator or:

adb shell ps | grep zygote

in an ADB prompt in a PC.
[Moto G 2015 Original Android Development] r26332735:
Is Any bugs there . Please tell
[Moto G 2015 Original Android Development] IronTechmonkey:
That's a Q&A question, followed up here: https://xdaforums.com/showpost.php?p=76449160&postcount=419
[Moto G 2015 Original Android Development] anisgvr:
Working fine no issues here
[Moto G 2015 Original Android Development] r26332735:
How to get root access
[Moto G 2015 Original Android Development] stonny20:
Use magisk for root access. Flash the rom,gapps then magisk zip file.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Moto G 2015 Original Android Development] IronTechmonkey:
Unless there is a specific need for Magisk (such as modules) LOS native SU might be a better choice, especially for bug testing LOS (which is the purpose of this thread). LOS SU is available in the Extras section of the LOS main downloads page. https://download.lineageos.org/extras

As to Magisk's other features, such as SU hide and modules: Although those features may be useful they might be the first thing people suggest removing if there are perceived problems with the ROM.
[Moto G 2015 Original Android Development] squid2:
Apologies for my absence

Sorry for seeming to fall off the face of the earth for the past few months. My time for Android diminished as my father grew increasingly ill in March, and I lost the mood to work on it after he passed away at the end of March. Since then, I've gradually returned to my normal life, but I've been a combination of swamped with other work and feeling lazy. Anyway, enough excuses and apologies for the lack of recent progress in my projects. I don't want to abandon any of my projects, and I feel bad for my neglect of them for the past few months.

I'm still around, and still hope to get back to working on my Android related projects. I just need to find the time and rebuild desire to work on them.
[Moto G 2015 Original Android Development] santo_007:
Since Alberto retired as maintainer who is the official maintainer
[Moto G 2015 Original Android Development] IronTechmonkey:
No apology needed here under any conditions, especially those. Condolences for your loss, a near one at that. You've left us on good ground. If and when you decide to jump back in, I promise to try to break your stuff. :)
[Moto G 2015 Original Android Development] LinuxPanda:
Apology is a strong word since its not like we're paying you for your services.

Please take your time. No need to feel bad about anything.

And my deepest condolences for you loss. :crying:
[Moto G 2015 Original Android Development] santo_007:
My deepest condolences for your loss and may your father R.I.P.

Hope you will return to good condition.
[Moto G 2015 Original Android Development] JuanG:
Don't worry. We will be here when you are ready to go back. You have done a very good work for us and for the community.
[Moto G 2015 Original Android Development] fleischbanane:
Please take the time you need and don't start again until you really feel like it! First overcome your painful loss. We thank you all for your hard work here.
[Moto G 2015 Original Android Development] Orjakone:
Although here is not the thread of my device, I come here to pay my respects for your father, and thank for all the support by the devices that you do maintenance.

And come back when you're ready. :Boa:

A great developer!
[Moto G 2015 Original Android Development] Gravemind2015:
Very sorry to hear that. May he rest in peace, I'll pray.

And for the projects, there's no need to be sorry. You deserve a break. After all, we're humans and we have a heart that needs time to heal. Phones are just machines, a tool for our assistance and entertainment. So, I think you should join us when you feel like it, you've already carried the development to a rock solid status.

Have a peaceful and warm day.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] IronTechmonkey:
This note is copied from the Q&A thread.

All of the linked LOS Jira bug tickets below relate to Whatsapp. IDK if they all speak to your issues mentioned here thsoe are actual bug reporting and are worth reviewing. I cannot speak to them as I don’t use whatsapp but:

- One ticket indicates that a similar bug was fixed last year (perhaps for a different device).

- Another ticket indicates that some people using our Moto G Osprey device still experience it. (may or may not be same issue).

- Some tickets were rejected for failing to include required logs or for being incorrectly filed as regressions but even those tickets may contain informative notes.

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

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

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

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

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

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

If anyone thinks some of those tickets regard the same issue it might help to add notes into the most appropriate ticket (as you see it) and to cross link to other tickets which may also involve the same issue and link then relevant tickets back to the LOS 14.1 Osprey dev thread.

[EDIT]Just to clarify that this post is not intended to push anything on developers who may have moved to LOS 15.x or other devices, or those who are deciding what to do next in a larger way. It was pleasantly surprising to find those jira tickets. There is still possibility that is not purely device specific or that something from LOS15 might be cherry picked at some point, so it is worth having a broad view of available information.
[Moto G 2015 Original Android Development] nahuelt1:
Hi, i installed this rom about 2 weeks ago. Since then (update after update this still the same) i have noticed that the signal gets lost when the screen is off, and gets back when the device is awake. I know this is a "nightly" rom so it´s very buggy but i really need to solve this problem, because i don´t receive any kind of message or call when the screen is off. If this can´t to be solved please tell me wich is the more stable rom for this device, because i really need some stability here. Thanks.
[Moto G 2015 Original Android Development] IronTechmonkey:
In spite of a few issues this ROM is actually quite mature and stable. Additionally there seem to have been few if any similar reports in this thread or at LOS Jira (official problem ticket system for LOS; https://jira.lineageos.org). With that in mind, you should search threads here and search LOS Jira to see if others have reported anything similar.

The problems you are experiencing may not be ROM bugs but rather may be issues with the resources or processes being used when flashing it, or with 3rd party factors, or with the past history of the device. The fact that you are updating frequently is less important than to be doing so properly; clean flashing and testing without any 3rd party factors. If you think this is an actual ROM bug you can create a proper bug report with details and logs at LOS Jira (https://jira.lineageos.org) and share the details here.

Until you can get a good bug report together or can otherwise establish this as a ROM issue it would be more appropriate to post in the Q&A thread here: https://xdaforums.com/2015-moto-g/help/rom-official-lineageos-14-1-qa-thread-t3545422. This is not all to say that what you've noticed could not be a Lineage OS Osprey ROM bug but you've provided no supporting evidence that such is the case, and there are expectations for bug reporting (which is the point of this particular thread and LOS Jira). So, in short, take it to the Q&A thread > confirm your flashing resources and process > decide whether it seems to be an actual LOS bug > create a bug report containing requisite details and logs.
[Moto G 2015 Original Android Development] nishant6577:
lineage OS download link is experiencing technical difficulties in download speeds .... does some body have the official lineage OS of June or July and can give the link ... i need it desperately ...
[Moto G 2015 Original Android Development] IronTechmonkey:
The download link to official builds is in the OPs of this thread and is working fine.
[Moto G 2015 Original Android Development] Carolina r:
With new update, sound quality down.
[Moto G 2015 Original Android Development] IronTechmonkey:
That is unlikely to be a ROM issue since there have been very few changes in the past month and those changes don't seem to involve the sound system. If you do think this is an actual ROM issue then please provide a useful big report in this thread or at LOS Jira (the official problem ticket for LOS).

If you are not interested in the development of the ROM (which is the purpose of this thread) beyond announcing that something is broken without providing helpful supporting information then please use the Q&A thread.
[Moto G 2015 Original Android Development] scattey:
Use a VPN to download it
[Moto G 2015 Original Android Development] taiyoko:
Every time I go to update to the latest nightly (trying to do it now, last time was in April), I always seem to lose my IMEI and APNs. And given how long I go between updates, I can never remember how I got the APN menu to let me re-add the Virgin Mobile APN.

Is this something related to doing a dirty flash, or is there something else going on? Restoring from backup works fine, that's what I've done for now because I got frustrated with trying to figure it out yet again.
[Moto G 2015 Original Android Development] IronTechmonkey:
Wahoo, it seems as if squid2 is still slinging code for LOS 14.1 Osprey; A bunch of new device or branch specific kernel commits to be in next build: https://www.cmxlog.com/14.1/osprey, including one commit that seems to address recently reported what's app issues: https://review.lineageos.org/#/c/LineageOS/android_kernel_motorola_msm8916/+/220544/.
[Moto G 2015 Original Android Development] squid2:
While I don't use Whatsapp myself, the commit you linked should fix the video upload issues some users were reporting. Once the next build comes out, I'd appreciate confirmation from Whatsapp users that this resolves their issues.

I also did a big security patch roundup on the kernel. Some of the security commits (WiFi driver ones) I pushed through gerrit so they are visible on CMXLog, and for many others I bypassed gerrit and pushed directly since they were too numerous. Anyway, the upcoming build's kernel will be fully patched as of the July 2018 ASB (and I included a few other patches too).

My current plan of action (in order but with no hard timeline) is:

Security patch the msm8610 family LOS 14.1 kernel

Update my MSM8916 family "Squid Kernel" with the same patches that I applied to the MSM8916 LOS 14.1 kernel

Update TWRP for all devices I support

Prepare a kernel for LOS 15.1 official Oreo on MSM8916. There are several suitable kernels in use, but I might do another CAF rebase if necessary.

Clean up and combine the LOS 15.1 device trees of various community members on the MSM8916 family.

Once "official" device and kernel code for LOS 15.1 is ready, I will make a few unofficial test builds with the official code.

Once people are happy with the stability of the unofficial builds made with official device and kernel code, I will make LOS 15.1 official for the MSM8916 family

Prepare LOS 15.1 for the MSM8610 family in a similar manner

Once all my official LOS 15.1 devices (MSM8916 and MSM89610) are on LOS 15.1, I will evaluate what to do on the MSM8937/8953 families. There has been extensive development by others on various devices in this family, and my main contribution has been on MSM8917 devices (perry/owens). I've been wanting to commonize these, but this would require cooperation with maintainers of other devices. I'll cross the bridge when I get to it.
[Moto G 2015 Original Android Development] sargam44:
After long time i heard this great news . Take bow mr. squid2 and best of luck for this
[Moto G 2015 Original Android Development] Leon Nardella:
So... I just would like to report that as of build 20180721 the video upload issue in Whatspp, Instagram, Facebook etc is fixed. Highly appreciated. Thanks!
[Moto G 2015 Original Android Development] juanpm77:
the videos have some 'lag' in instagram, whatsapp, face, etc !
[Moto G 2015 Original Android Development] Ellahi:
Your phone is problem...
[Moto G 2015 Original Android Development] marito292:
error camara

alguien sigue con problemas de camara? se sale...
[Moto G 2015 Original Android Development] Ellahi:
Only English language.
[Moto G 2015 Original Android Development] strugart:
Since this changes were merged my moto g suffer randoms reboots. A downgrade to last build fixes the issue. This is affecting what is a stable ROM, testing should have been more extensive. Please rollback the changes until is possible to point out the culprit.

Welcome to provide a logcat.

Thanks.
[Moto G 2015 Original Android Development] IronTechmonkey:
Absolutely no problems with clean flash here. As to "rolling back the changes until the culprit is found"; that's not how it works. It's up to us to prove that any problems are actual bugs. In this case you've provided no information to support the hypothesis that those problems are caused by the new commits.
[Moto G 2015 Original Android Development] strugart:
Thanks, i will consider the option, even if not usually required for these weekly/monthly updates.