yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
Yep, in lineage-14.1-20180119-nightly-osprey-signed with open_gapps-arm-7.1-pico-20180119 volume seems quite good. Thanks for confirming, and thanks [MENTION=4912374]rahul9999[/MENTION] for same.

As to kernel, since this thread is for developing and reporting bugs for the LOS Osprey ROM we would by definition usually be using the native LOS Osprey kernel. Discussion of alternate kernel might be best placed in the Q&A thread and here's a bit of follow up: https://xdaforums.com/showpost.php?p=75266977&postcount=315
[Moto G 2015 Original Android Development] spectkiller:
is there any way to disable or remove default lineage audio fx coz i have to install viper4android mod ??

anyone can help me
[Moto G 2015 Original Android Development] agu12333:
Home button not working after setting profile

I've been having this weird issue for a long time. I have three profiles and every time I set one of them from the quick settings, the home button stops working. I got tired of that and I added widget shortcuts on my desktop and it seems to work from there. The thing is that I bought a smartwatch and added a button to manage my profiles from the watch, and when I set them from there, my phone home button stops working again. Any idea or fix for this? Thanks! I'm running latest LineageOs 14.1 build.
[Moto G 2015 Original Android Development] rohanmane3:
Hi guy i have a problem with the memory management whenever i keep download in mobile after sometime it shutdown the browser i went to battery option and i did the optimize for battery for the browser but it didn't work still my ongoing download automatically close, please help me
[Moto G 2015 Original Android Development] pdeadm:
Latest nightly 20190119 smoothier ever. Fast and very very robust.
[Moto G 2015 Original Android Development] debojyotidey:
hello guys, i've been using CM and LOS from lp days (CM 12.1 era)....but nowhere found any mention of this particular issue (bug?) i am facing in CM13,,LOS14.1(didn't try to expt. in CM12.1) that even when you turn off the shutter sound in snap camera the shutter sound is still there.....other camera apps like the moto camera app show that option as enabled,but it isn't possible to turn off.....stays on.....would be nice if anyone could confirm it.
[Moto G 2015 Original Android Development] Sachin ET:
Use Titanium Backup and freez it....that's what i do. ?
[Moto G 2015 Original Android Development] IronTechmonkey:
That's a good answer for the question but you're talking about disabling a system component so you can make a third party mod work. That's obviously off topic here.

Don't stop trying to be helpful but please post Q&A answers in the Q&A thread. You could just cut and paste the quote into the other thread and answer it there.
[Moto G 2015 Original Android Development] maosilva:
The download servers have been offline since yesterday!
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes, something does seem to be wrong. I was just able to start a download and then a few moments later unable to do so. Maybe it was having problem since Friday and that is why [MENTION=4912374]rahul9999[/MENTION] shared an independently uploaded build here: https://xdaforums.com/showpost.php?p=75256401&postcount=5679.
[Moto G 2015 Original Android Development] maosilva:
Thanks for the link, my friend!
[Moto G 2015 Original Android Development] IronTechmonkey:
Thank [MENTION=4912374]rahul9999[/MENTION] (thanks button is good for this). As can be seen in the posts following the linked one; I (not realizing there might be a download issue) actually nagged rahul9999. not to do that, so no thanks to me. :o
[Moto G 2015 Original Android Development] pratyushshopping:
The 19Jan build is great issues for low volume during call is resolved.

Hats off to the developers who are addressing the issues and resolve it ASAP.

Really appreciate it thanks for keeping our 2015 device alive.
[Moto G 2015 Original Android Development] IronTechmonkey:
Regarding what may be called the LMK, minfree or RAM management issue, some notes brought here from Q&A after squid2 mentioned taking a look at this when there is time. (https://xdaforums.com/showpost.php?p=75271273&postcount=320). Also, an interesting test which may (or may not) inform the issue.

Clarification: Although changing the minfree values does significantly mitigate the issue in some usage scenarios, a comparison of minfree values in LOS 14.1 on 1GB RAM devices (Otus-RIP and Peregrine) may indicate it's not the primary cause, since one of those devices also had what seemed to be high minfree settings without the same symptoms.

Also, there is this chance to log something easily reproducible which might inform the issue (although it may not be practical for many people to do this test). Seems as if some buffer or cache may be running out of space. If this does not inform the "LMK issue" it might be a new one.

- Audubon Birds of North America app downloads and extracts about 350MB of image and sound files in batches.

- For each batch, shortly into each extraction step, it stops and reports "No space left on device".

- When the process is re-started it gets a bit farther (always the same increment) in that particular extraction process, then yields the same error.

- When the process is repeated enough times it finally completes.

- In LOS 14.1 Jan 19 Osprey it required about 40 (forty) passes through the process, in order to complete.

- In LOS 14.1 Jan 19 Peregrine (similarly configured device) it completed in one pass.

- In previous Peregrine builds and previous Athene builds it took 2-3 passes but no more, and certainly not 40.

Within a few days, after flashing tomorrow's Athene build I'll compare this across the devices again and log part of what occurs on Osprey.

BTW The bonus for doing this test is that you would then have off-line access to pictures, range maps and detials regarding... Ospreys :silly:
[Moto G 2015 Original Android Development] iDevilscythe:
:good:
[Moto G 2015 Original Android Development] Khaled Gargary:
New nighty available 26 Jan
[Moto G 2015 Original Android Development] IronTechmonkey:
Possible issue very early in flash/config process.

FYI: In truly clean flash of LOS Osprey Jan 26 LOS & OpenGapps Pico Jan 16 w/LOS SU; During initial configuration when attempting to connect to Wifi, the connection was not established but rather saved with no authentication error. That occurred 2 or 3, times then the device spontaneously rebooted back into the next step of initial config - successfully connected to wifi.

[EDIT]2nd flash was OK through initial config to home screen, so this is just a flag in case this has any bearing on issues which may be discovered later.

[EDIT2] Things seem fine so maybe that was just a misstep in the dance of the ROM and Gapps during initial configuration.
[Moto G 2015 Original Android Development] LinuxPanda:
Do u think dirty flash over last week build will be OK?
[Moto G 2015 Original Android Development] IronTechmonkey:
Well, I have very biased opinion about that; I always clean flash because chasing bugs is more efficient in clean flashes. Also, not knowing your circumstances (which be more than we would want to do here) I could not tell you dirty flashing in this instance will definitely be OK. If you are "on the fence" (undecided) you might be swayed toward clean flashing just because Osprey device specific dev has been active lately and there have been numerous commits that address some long standing issues. You can look through this thread for posts by squid2 to see more detail.
[Moto G 2015 Original Android Development] x389sadas2:
Proximity sensor is stopping occasional

Current version: lineage-14.1-20180126-nightly-osprey-signed

Hi *,

anyone noticed that the Proximity sensor on their Osprey is stopping to provide current data occasional (around one to two hours after the last reboot) on the 14.1 nigthlies since the beginning of December 2017?

On my device it needs a restart of the phone to get the Proximity sensor to working again and to provide data to the device. I did a short search and it seems some one else already reported something similar to the LineageOS bugtracker here:

hxxxs://jira.lineageos.org/browse/REGRESSION-1419

but failed to provide basic info. I'm currently gathering the logcat but it might get huge within an hour, is there anything i can look at to maybe see the reason why the sensor is stopping?
[Moto G 2015 Original Android Development] squid2:
Can you identify specifically which build your issue started on? There were some changes to the proximity sensor driver in late december. If you say it started in the beginning of December, I don't know what is responsible.

EDIT: The driver changes only affect harpia, not osprey, so I don't know what's behind your issue
[Moto G 2015 Original Android Development] IronTechmonkey:
[MENTION=7881052]x389sadas2[/MENTION] & [MENTION=6485916]squid2[/MENTION].

For what this may be worth by comparison: On XT1540 running Jan 26 build (with no SIM and therefore no dependency on proximity sensor for dialer), proximity sensor seems to indicate normal activity in diagnostic apps such as Aida64 and Sensors Multi Tool, and it seems to work properly for Ambient Display > Hand Wave. I'll leave the device untouched to for a few hours and see if hand-wave still works.
[Moto G 2015 Original Android Development] x389sadas2:
Hi,

and thank you very much for your response.

Unfortunately i'm not able to exactly pinpoint this to a specific build. I've noticed it the first time at 2017-12-11 but it might be possible that this started even earlier as the hxxxs://jira.lineageos.org/browse/REGRESSION-1419 was created on 2017-11-21.

Yesterday i've tried to catch a logcat via ADB but the issue didn't showed up as long as the device was charged. Luckily i was able to catch a logcat directly on the device once the issue was showing up.

I havn't found a way to upload a complete logcat output here (if required i could put it on pastebin or similar) but the most noticeable entry where those two:

2018-01-28 10:33:14,DEBUG,CMActions-FlatUpSensor,Advanced settings,Disabling

2018-01-28 10:33:14,DEBUG,CMActions-ProximitySensor,Advanced settings,Disabling

A few seconds later the Proximity Sensor stopped with a final line:

2018-01-28 10:33:19,ERROR,MotoSensors,Android System,Proximity covered 2

Could this be related to some sort of power saving changes or similar where the sensor is just stopped without bringing it back to life again? (I don't have any extra battery saving apps installed).
[Moto G 2015 Original Android Development] rahul9999:
just make a zip file of that full logcat & try to upload it here.. if not possible here then try to upload that zip to Gdrive & share a link here..
[Moto G 2015 Original Android Development] anish sk:
audio fx working only after turn off screen light. any solution?
[Moto G 2015 Original Android Development] IronTechmonkey:
You could try playing with settings for features that use the proximity sensor.

Settings > Gestures (2nd group) > Wave to Silence

Settings > Display > Ambient display > hand wave.

Others?

Also, I've seen sensors (compass/magnatometer) and other hardware become invisible to the device when being accessed by more than one app or service. If you've not already covered this, just make sure to close and swipe any app that use the sensor before testing the next one.
[Moto G 2015 Original Android Development] x389sadas2:
Hey,

this is a really great background info which i can use to start digging into this issue. Thank your very much :good:
[Moto G 2015 Original Android Development] panagiotis15:
No sim card after 26/01/18 update

Hi

I own a xt1550

Just made ota update to the last rom and after the mobile completed the procedure, its not recognising any sim card.

I have Magisk installed as well.Do i have to flash any aditional file?

Downgrade could resolve the issue?

One more issue.... microphone as well is not working and no sound coming out...
[Moto G 2015 Original Android Development] thamnees:
working well ...tnx:)
[Moto G 2015 Original Android Development] Khaled Gargary:
can anyone tell me what is this program and how to get rid of it ?

i do have this shield and app named as data protection of android shield since long time ... i've never seen it on any other phone before .. wondering if its from LOS or Google or whatever .. its annoying always showing this notification on locked screen and shield icon up in the corner
[Moto G 2015 Original Android Development] BenjyTec:
Go to Settings --> Privacy Guard (Datenschutz) --> Turn off 'Show Notifications'.

There it was in CyanogenMod, not sure if it still is located in the same place in Lineage. But the setting should be somewhere around there.
[Moto G 2015 Original Android Development] Khaled Gargary:
thanks u so much ... finally i got rid of that constant Notification .. it was really a pain in the a** for long time ...

i never thought it was so simple and easy like that ... especially as it just started to appear suddenly ..
[Moto G 2015 Original Android Development] OSantal:
Can anyone confirm that camera crashes when taking photos with hdr?

Thanks
[Moto G 2015 Original Android Development] anilpotaliya:
I am using latest LOS 14.1 on my Moto G3 but unable to use Jio VOLTE. Also tried with fresh installation. Enhanced LTE mode is already enabled. Please help how can i use JIO volte on this rom
[Moto G 2015 Original Android Development] pratyushshopping:
I'm on the latest build and Jio Volte works fine.

Try clean flash again.

First make sure Your Sim is fine try it another Volte device
[Moto G 2015 Original Android Development] anilpotaliya:
I have tried 2-3 SIM cards and also with clean flash. Same SIM is working fine in another device. But not working, is there any other solution.
[Moto G 2015 Original Android Development] stonny20:
Did you try a clean flash ?
[Moto G 2015 Original Android Development] Sachin ET:
i just tried updating to 26 jan build using updater service and now my sim card is not being detected and it takes much longer time to boot up
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI: This week's build has a particularity small number of commits, none of which seem to relate to SIM: https://www.cmxlog.com/14.1/osprey, and it does not seem as if anything outside of that stream of commits is being added (there is so little there that I'm skipping this week and continuing to test LMK stuff in previous build).

This does not mean there must be no bug (SIM issues could be region or provider specific), but it does mean that in order to establish whether or not it is a real bug and what the cause may be, logs with specific details about how to reproduce, taken in a actual clean flash would be need. Actual Clean flash for testing:

- No 3rd party mods including Magisk, Xposed, viper, no apps moved to system, etc.

- Don't use native OTA updater. Download ROM zip and flash manually from recovery.

- Boot to recovery.

- Wipe dalvik and system cache.

- Factory reset (full wipe)

- Install ROM, Gapps package and LOS SU in same recovery session.

- Wipe dalvik and system caches.

- Boot to system.

- Before installing app or modifying settings reproduce issue while logging, then report bug.

[EDIT] FWIW, at Jira there is one new report about sound issues in Osprey and one new report about SIM issue in Peregrine, although IMO there is little in each report to take it as a bug without more information. You can search Jira for those things: https://jira.lineageos.org/
[Moto G 2015 Original Android Development] rohanmane3:
[MENTION=5119654]IronTechmonkey[/MENTION] Glad to see you are working on LMK since it really hectic for me to keep any app open while screen is off the memory management need to be less aggressive hope you resolve the LMK problem very soon , and one thing what if i install squid kernel will that solve my problem?
[Moto G 2015 Original Android Development] norullzz:
[MENTION=5119654]IronTechmonkey[/MENTION] I've had a similar problem earlier this month, rolled back and hoped it would be fixed. (was on ROM+micro gapps+magisk). Had the same issue with this weeks build and did the wipe cache data system with the ROM+micro gapps+LOS SU and the issue is gone.

TLDR; you are right to recommend a clean flash.
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI, I'm not "working on" anything. I'm just another user of the ROM (who happens to test it and has another device to compare to). I share your observation and opinion about the effect of when powering off/on the screen. In my case also when viewing multiple tabs in web browser or using the LOS camera.

squid2 kernel does not seem to have an effect on this issue (and the shutdown freeze issue which the custom kernel worked around has been fixed so I'm not testing with the kernel). As to LMK settings, I'm now forcing myself to use the default settings so as to test the ROM, but the workaround LMK settings I had been using were half the "default" values - You could try those.

For the jira ticket I've got a new test that shows this is not just about how much available RAM there is, as well as a test I previously mentioned using the Audubon Birds app, for what that is worth. I'll add those details to the ticket this week but don't know if or how they would help.

---------- Post added at 05:34 AM ---------- Previous post was at 05:27 AM ----------

In your case either or both the clean flash or the switch from Magisk to LOS SU cold have been factors.
[Moto G 2015 Original Android Development] Tomail69:
Hi,

The camera don't crashes when taking photos with HDR. I test it. It's good!
[Moto G 2015 Original Android Development] shadowbone:
I updated to the latest build and I can see an 'ANT HAL service' app. Can someone explain to me what that does?
[Moto G 2015 Original Android Development] IronTechmonkey:
For reference, There is previous informative discussion about that in the thread. In short: ANT+ is a form of wireless communication used between the Android device and any number of health, cycling, or other sensors.
[Moto G 2015 Original Android Development] shadowbone:
Yeah, I had seen couple of posts regarding this, but didn't know what its purpose was.

So thanks for the short info.
[Moto G 2015 Original Android Development] IronTechmonkey:
ANT + is also quite well documented outside of XDA but think along lines of pedal cadence sensors for cyclists or heart monitors for runners (among myriad other uses).
[Moto G 2015 Original Android Development] Tomail69:
Hi, ANT SERVICE APP is a service to use various ANT / ANT+ devices like heart rate monitor, fitness equipment etc.
[Moto G 2015 Original Android Development] Subham9997:
I am having wifi drop issue...i did full wipe/clean flash and 2018 build but still having wifi drop issue on every rom i flash had h same problem...help me someone ...

Also when i back to stock 6.1 wifi seems connected ...bit having a single problem...if anyone knows how to fix that wifi problem on custom roms plz help

---------- Post added at 12:45 PM ---------- Previous post was at 11:55 AM ----------

i am having a wifi drop problem on lineageos 14.1 2018 build and every other rom as well...i did clean install still having the problem...and when i install stock 6.0.1 wifi works great ,

how to fix wifi drop problem??
[Moto G 2015 Original Android Development] IronTechmonkey:
What problem;). I've had my Osprey on Wifi all day with no disconnects, even when the device was idle for hours.

FYI "bumping" posts is against the rules (I've no standing in that regard but am just letting you know we are not to do that). Another expectation is to post in the appropriate thread and include proper details for a bug report. If you are having this problem in every ROM while hardly anyone else is reporting it here in LOS then it is not likely to be a Lineage OS ROM issue or appropriate to discus here. You can search this thread and LOS Jira https://jira.lineageos.org/secure/Dashboard.jspa?selectPageId=10502 to see if there are other similar reports. If you think it is a Lineage OS specific bug then you should reproduce the issue while logging then share the log and a description that others could follow to reproduce and test, in this thread or in a Jira ticket.
[Moto G 2015 Original Android Development] adityak1303:
Okay first, stop spamming. You've asked this same question in 2-3 other threads also.

Second, this is a development thread. Questions like this belong in the Q&A section which can be found here : https://xdaforums.com/2015-moto-g/help/rom-official-lineageos-14-1-qa-thread-t3545422/page33

Third, your question was answered here : https://xdaforums.com/2015-moto-g/development/rom-aospextended-rom-v5-0-t3681997/post75510182
[Moto G 2015 Original Android Development] pratyushshopping:
First) Spamming is when you post in same thread Asop and Lineage are handled by different people so this isn't spamming.

Second) Noted this belongs to Q&A. I will take care of that next time.

Third) Thanks but I already got a notification for that.
[Moto G 2015 Original Android Development] IronTechmonkey:
Spraying the same question into many threads is not only spam, it is a higher order of spam affecting more branches of the larger tree of threads. Repeating in the same thread would be considered a lower order of spam as well as a form of bumping.

So... perhaps the next post here will be about viable bug reports in the latest build of LOS 14.1 Osprey, and the next post not about that will be in the Q&A thread. ;)
[Moto G 2015 Original Android Development] pratyushshopping:
Sorry I'm not quite familiar with rules still exploring them by reading threads and how people reply when somebody asks non contextual question. I posted it just 2 threads this and Aosp thought it's no big deal. Thank you
[Moto G 2015 Original Android Development] LinuxPanda:
Maybe you should read the rules first before posting in threads.

There is a reason for sticking rules threads and when you argue for doing something against the rules and calling it as no big deal, the mods will step in, ban the trolls & call it no bid deal. :laugh:
[Moto G 2015 Original Android Development] gustazo:
It is known when the error in sending whatsapp videos is going to be solved, no buid of January works for me.
[Moto G 2015 Original Android Development] IronTechmonkey:
Who is to say this is actually a ROM issue? AFAIK no one has established this with a bug report here or at LOS jira.
[Moto G 2015 Original Android Development] Mama Luigi:
So what happened with this? I installed this build back in November, and it solved my bluetooth dropping bug when leaving wifi range. I haven't heard anything about this fix making it into subsequent nightly builds. Why wouldn't this happen? Are there any plans to actually solve the bluetooth bug or will I just be on this November build forever?
[Moto G 2015 Original Android Development] SANTHOSH SK:
Hi guys does the lineage 14.1 supports pixel portrait mode or camera nx?? If not can someone port this apk to this platforms??
[Moto G 2015 Original Android Development] Funky Rebel:
Hey guys,

Just noticed that ok google or hey google does not work when phone is on charging and i also don't have the option to turn that on in google app settings.

Kindly i don't this is a feature request or it should have come with the rom. Sorry if am wrong.

Thanks in advance ?.
[Moto G 2015 Original Android Development] BenjyTec:
I think the OK Google support depends on the Gapps package you are using. You need the application 'Hotword' included in your Gapps package. Make sure that the package you flashed includes it.

Not 100 percent sure with this, just a guess. What do you mean with you haven't got the option to turn it on? Not sure if I got your problem.