yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI, While searching various things at LOS Jira I saw your ticket (https://jira.lineageos.org/browse/BUGBASH-1352) which was rejected because Xposed was present and not mentioned. That report deserved to be rejected, but this does seem to be a valid issue (verified on my actually clean flashed Osprey). Perhaps because squid2 has seen this it will be addressed but if not then you might want to recreate your Jira ticket from an actual clean flash (in which case I'd be glad to vote for it).

BTW: https://xdaforums.com/showpost.php?p=75054960&postcount=5613

;)
[Moto G 2015 Original Android Development] diego aleson:
High RAM usage by system in this ROM (osprey 1gb RAM)

Please, fix it, Please
[Moto G 2015 Original Android Development] Osid:
Do you have a MNO and/or your SIM VoLTE enabled? Could be useful to understand if it's a bug or a regression. I don't know if VoLTE ever worked on official LineageOS 14.1 for osprey.

I've already contacted LineageOS BugMonkey. When I've spare time, I'll disable magisk and Xposed and replicate bug and recreate issue on Jira.

I would try to cherry picking previous IMS shims/blobs (from LinegeOS git repo or from https://github.com/moto8916/proprietary_vendor_motorola) and barely copy on system partition, in order to simulate a "downgrade" only for IMS. What do you think [MENTION=6485916]squid2[/MENTION] ?

I'm a software developer and I've a discrete experience with Android app development and AOSP internals code review/knowledge but little experience of AOSP build and/or low level development. With some indications I can try to configure a VM build enviroment and making some changes in .mk files, blobs, etc.
[Moto G 2015 Original Android Development] IronTechmonkey:
https://xdaforums.com/wiki/Reporting_A_Problem_-_Android

https://xdaforums.com/announcement.php?a=81

https://jira.lineageos.org/
[Moto G 2015 Original Android Development] IronTechmonkey:
I don't use Volte and was just testing the ROM generally on an Osprey with no SIM when I saw your note and was able to reproduce the issue as described. Your general questions about the history of Volte on Osprey may be answered by searching this thread (and LOS Jira) where there has been much previous discussion.

In regards to Xposed - Not disable. Flash without. This can make a big difference. Just ask anyone who had to do a manual cleanup of substratum after using it. Better not to take the risk and not to undermine the veracity of your reports.

You understand more of the raw development side than me and it seems as if squid2 has already noticed your report, but one note about process which you as a software developer can surely appreciate: Failing to mention the presence of a significant 3rd party hack (Xposed) expressly not supported by LOS will not encourage people to believe your reports. You're lucky squid2 saw it here.

That being said I do believe it because I could reproduce it, and you might be able to follow any progress by occasionally checking the Osprey changelog: https://www.cmxlog.com/14.1/osprey or by keeping an eye on squid2's git (follow references in XDA user profile).
[Moto G 2015 Original Android Development] ShapeDePraiaBR:
Bugs

My calls and cam recorder or audio recorde are slower after latest update.

---------- Post added at 11:57 PM ---------- Previous post was at 11:53 PM ----------

Microphone in calls, cam recorder and audio recorder is slwoer.
[Moto G 2015 Original Android Development] IronTechmonkey:
This is a development forum, not a review board, so please post in Q&A. Also, bugs reported with no logs, details or confirmation of clean flash might as well have never happened.

There have been some substantial changes in latest build and there might be actual bugs. You both can (and should - it's an actual XDA rule) search thread for references. As to reporting issues so they can be clearly established as actual issues and then addressed:

Advise about reporting bugs: https://xdaforums.com/wiki/Reporting_A_Problem_-_Android.

XDA Rules: https://xdaforums.com/announcement.php?a=81

Lineage OS Jira (issue tracking system): https://jira.lineageos.org/
[Moto G 2015 Original Android Development] squid2:
I'm guessing your issue is that https://github.com/LineageOS/android_vendor_codeaurora_telephony is outdated and needs this commit: https://source.codeaurora.org/quic/...9&id=70965487759b0b87bf3e4dac83ff92667e98ef7c

I have no way to test VoLTE myself. When I posted the new blobs test build earlier, multiple users said VoLTE was fine and I heard no complaints at the time, so I merged in the blob updates. I'll make and post a test build with updated CodeAurora telephony bits and [MENTION=5547760]unqualified[/MENTION]'s ANT+ support later tonight.
[Moto G 2015 Original Android Development] squid2:
Test build with ANT+ and VoLTE fixes

I've made a test build with the ANT+ support patch by [MENTION=5547760]unqualified[/MENTION] and updates to open source IMS code in an attempt to fix the VoLTE issues encountered by [MENTION=1635184]Osid[/MENTION]. Let me know if VoLTE and ANT+ work. Since it is an unofficial build, you will need to do a clean install if coming from an official build. You can back up your official build before testing using TWRP, and restore it afterwards when you want to return to official builds.

Download link: http://www.mediafire.com/file/g1mds0tkll10tpa/lineage-14.1-20180111-UNOFFICIAL-osprey.zip
[Moto G 2015 Original Android Development] Bastlwastl2010:
To switch between offical and unoffical version i found this in the wiki:

https://wiki.lineageos.org/signing_builds.html#using-a-script
[Moto G 2015 Original Android Development] IronTechmonkey:
Running test build with Open Gapps Ppico and LOS SU. Ant+ Hal service seemed to be on device out of the box, reflected in Ant+ tester.

After installing other components from Play Store all required components seem present.
[Moto G 2015 Original Android Development] SANTHOSH SK:
Error while flashing!

Mod Edit: There is no reason to quote the entire OP.

1) hide it as I did above

2) quote only the first line as I did below

Dear Developer i'm not able to flash this file through twrp recovery,

It says No diskfile and skips the installation Why?

Should i have to do something to zip file to install? Please help

Or Please help me to flash this Rom Via Fastboot through commmands
[Moto G 2015 Original Android Development] SANTHOSH SK:
GAPPS link REQUIRED

Please share gapps link for this rom
[Moto G 2015 Original Android Development] squid2:
OpenGApps should work. For future non development related questions, please use 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] ouch01:
Hi there. I came to report something weird. When I try to send via WhatsApp a video recorded with the main Camera app, I get an error message telling me that I should reboot the phone. Of course, it doesn't solve the problem. It seems to be an unimplemented thing with the video codecs.

This is what I found in logcat. The errors starts with this:

01-11 16:24:47.007 E/OMX-VDEC-1080P(328): Extension: OMX.google.android.index.storeANWBufferInMetadata not implemented
01-11 16:24:47.007 E/OMX-VDEC-1080P(328): Extension: OMX.google.android.index.configureVideoTunnelMode not implemented
01-11 16:24:47.007 E/OMX-VDEC-1080P(328): Extension: OMX.google.android.index.useAndroidNativeBuffer is supported
01-11 16:24:47.012 I/FFMPEGSoftCodec(332): Thumbnail mode enabled.
01-11 16:24:47.014 E/OMXNodeInstance(328): getParameter(14808dd:qcom.decoder.avc, ??(0x7f000044)) ERROR: UnsupportedSetting(0x80001019)
01-11 16:24:47.014 E/OMXNodeInstance(328): getParameter(14808dd:qcom.decoder.avc, ??(0x7f000044)) ERROR: UnsupportedSetting(0x80001019)
01-11 16:24:47.017 D/ACodec (332): Setting [OMX.qcom.video.decoder.avc] input port buffer number: 1
01-11 16:24:47.018 E/OMX-VDEC-1080P(328): ERROR: IP Requirements(#4: 1585152) Requested(#1: 1585152)
01-11 16:24:47.018 E/OMX-VDEC-1080P(328): set_parameter: Error: 0x80001005, setting param 0x2000001
01-11 16:24:47.018 E/OMXNodeInstance(328): setParameter(14808dd:qcom.decoder.avc, ParamPortDefinition(0x2000001)) ERROR: BadParameter(0x80001005)
01-11 16:24:47.018 W/ACodec (332): Fail to set [OMX.qcom.video.decoder.avc] input port buffer number: 1
01-11 16:24:47.018 D/ACodec (332): Setting [OMX.qcom.video.decoder.avc] output port buffer number: 1
01-11 16:24:47.023 E/C2DColorConvert(328): unknown format passed for luma alignment number
01-11 16:24:47.023 E/C2DColorConvert(328): unknown format passed for luma alignment number
01-11 16:24:47.023 E/C2DColorConvert(328): unknown format passed for luma alignment number
01-11 16:24:47.039 E/C2DColorConvert(328): unknown format passed for luma alignment number
01-11 16:24:47.064 E/C2DColorConvert(328): unknown format passed for luma alignment number
01-11 16:24:47.083 E/C2DColorConvert(328): unknown format passed for luma alignment number

...

...and keeps going. My complete logcat is attached.

In fact, it also happens with screen records (videos generated by org.lineageos.recorder app), so maybe it's a general problem with (at least) mp4 videos. However, when I make a record into WhatsApp with its camera, just works fine.

I'm using the latest nightly (20180105) with mini gapps.
[Moto G 2015 Original Android Development] Osid:
"imssettings.apk regression" (https://jira.lineageos.org/browse/REGRESSION-1572) resolved.

Unfortunately VoLTE still doesn't work on my osprey. Seems to be unable to IMS register but I don't know if it's MNO (someone says that VoLTE provisioning of my MNO is only for certain branded devices) or build related. Could be interesting if [MENTION=4480917]Alberto97[/MENTION] (italian like myself) has ever tested, with an italian MNO, VoLTE on osprey XT1541.

Could be useful a logcat of system and radio buffers of a successful IMS registration to compare. I've found, on GitHub, some proprietary qcom repository (leaked?) but I don't find low-level documentation in order to trace reason of errors.

I confirm: incall and speaker. Workarounded using tinymix command and raising RX1 Digital Volume from 84 (default) to 90+. Maybe some commit in msm8916-common has introduced this "low volume" issue=
[Moto G 2015 Original Android Development] IronTechmonkey:
FWIW, coincidentally just now I was using screen record on Osprey 1540 in squid2's latest test build and it had no problems (and I have a video of Audubon Birds of North America app issue decompressing images to prove it :))

I'm not saying this is either a ROM bug or an app bug, however a determining factor could be the presence of WhatsApp. I wonder if the same thing would occur immediately after a clean flash before apps are installed.
[Moto G 2015 Original Android Development] squid2:
Try the official December 29th build. This was prior to the major proprietary binary switchover. IMS is known to work for sure there, at least for Indian users. If it doens't work for you on that build, the issue is carrier specific. VoLTE and CDMA are the bane of my existence.
[Moto G 2015 Original Android Development] squid2:
As with IronTechmonkey, screen recording is working fine for me on harpia. I don't have my osprey any more (gave it to a cousin last year), but harpia has almost the same hardware.
[Moto G 2015 Original Android Development] Osid:
Tested, it doesn't work for me. Maybe is carrier specific.
[Moto G 2015 Original Android Development] pratyushshopping:
The bug that [MENTION=6485916]squid2[/MENTION] just brought to notice about Whatsapp Video error is happening with me as well I'm using Osprey also this is consistent issue for all the builds i have used.

But Screen Record just work fine

EDIT: With latest build of January 5 the issue is not there but it was there in December build.
[Moto G 2015 Original Android Development] IronTechmonkey:
In the interest of clarity: It was [MENTION=5969852]ouch01[/MENTION] who reported this: https://xdaforums.com/showpost.php?p=75165329&postcount=5651. It seems that squid2 was unable to reproduce it, nor was I in the newer build, so to your point maybe that build fixed it.
[Moto G 2015 Original Android Development] pratyushshopping:
Ok Thanks for confirming! [MENTION=5969852]ouch01[/MENTION] should move to latest build and check again
[Moto G 2015 Original Android Development] Dark Scorpian:
Low Call Voice

The update of 10/01/2018 it makes the call volume so LOW(it also low at Loudspeaker and it's too hard to hear someone's voice in the public area) please Replace the old one Thank you
[Moto G 2015 Original Android Development] IronTechmonkey:
IIRC you are at least the second person to mention that. FWIW, although I don't use Osprey for calls I do use it to monitor a security camera and the volume of the media stream does seem lower than in previous builds.
[Moto G 2015 Original Android Development] rafaelbarreto22:
Low volume in call and multimedia in 05/01 build compared to 29/12 build

PD: Dirty flash from clean rom (nano gapps and no mods)
[Moto G 2015 Original Android Development] IronTechmonkey:
If this is an actual ROM issue your best chance of fixing it is to provide a viable bug report with details and logs captured in a clean flash here and at LOS Jira (FYI: This is all expected SOP in development threads). I would try to do this but am not using Osprey for phone and cannot be sure about what I'm seeing in media stream (mentioned a few posts ago).
[Moto G 2015 Original Android Development] fersnake:
i think the version 14.1 2018-01-05 broke the phonel app, i cant see the UI making or receiving a call. i recently reinstalled it because the update gave me a boot loop error so i think im going back to an old version :S

edit:

i reinstalled the gapps insted and it worked again so sorry about the post xD

btw i dont know if it is me but i think the volume on calls is really low.
[Moto G 2015 Original Android Development] IronTechmonkey:
Please see post immediately preceding yours: https://xdaforums.com/2015-moto-g/o...official-cyanogenmod-14-t3466246/post75176961

These "it doesn't work" reports without even the most basic bug reporting details really do belong in Q&A thread.

For those not in position to provide viable bug reports, merely respecting that rule helps keep focus on actual issues.

We are getting some Dev love ATM. Please don't waste it.
[Moto G 2015 Original Android Development] gpvecchi:
Is it just me or incall volume is really low?
[Moto G 2015 Original Android Development] IronTechmonkey:
This Week's Build

FYI: I'm not sure what time the builds usually are released but it seems as if a day or 2 of builds from from klimtwifi to r7sf (including Osprey) are completed but in some stalled state in the build queue and not available for download even though later builds (eg Surnia) are available. We (and a bunch of other devices) might be skipped this week.

Also, when the builds do get going again: Ant+ is official, thanks [MENTION=5547760]unqualified[/MENTION] and [MENTION=6485916]squid2[/MENTION]: https://review.lineageos.org/#/c/202042/
[Moto G 2015 Original Android Development] squid2:
I’ve been getting similar low call volume reports on harpia. My suspicion is that something in the new blobs (different ACDB loader maybe) is responsible. I will look into it.

UPDATE: my testing confirmed that missing kernel patches are causing the new ACDB loader to fail to initialize properly. I will have this fixed for the next weekly build.
[Moto G 2015 Original Android Development] Khaled Gargary:
Looks like this week no nighty ... Anyone has an idea about our device with LOS 15.1 ... ? Looks like we will keep getting nighties of 14.1 and Oreo official build is far from being imagined though ..
[Moto G 2015 Original Android Development] OSantal:
Checkout this thread for a AOSP build for our device.

https://xdaforums.com/2015-moto-g/orig-development/rom-android-source-project-8-0-t3709129/page29

It's maintened by the same guy that maintains LOS14.1
[Moto G 2015 Original Android Development] Khaled Gargary:
thanks for your reply .. i would wait the LOS 15.1 official because all Alpha and Beta ROMs till now looks not really ready enough to be daily driver ...

i wonder really when an official Build would show up ...
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI, It's bad form to advertise one ROM in another ROM thread (you could use PM for that) and to discuss the next Android version in the thread for the previous one.

Also, the post immediately preceding yours (and other recent posts) indicate that one of the 2 contributers listed in the OPs of this thread has been actively working on it (we've even had a few test build between weeklys) so it's not like LOS 14.1 is getting left out ;)
[Moto G 2015 Original Android Development] Osid:
The build job is "blocked" on Jenkins

See https://jenkins.lineageos.org/job/android/9215/

Also, it seems that there's no space left on device of some Jenkins node.
[Moto G 2015 Original Android Development] IronTechmonkey:
This has been known since 2 days ago, posted just on previous page: https://xdaforums.com/showpost.php?p=75176961&postcount=5661. The number of questions and repeat answers by people who did not even read the previous few posts or search the thread will soon become thread spam and there are big and new changes to test.
[Moto G 2015 Original Android Development] diordna75:
Echo problem during calls when using headset-mic or speaker

Hi,

first of all: thanks for all the hard work of bringing Lineage to the osprey...

I get complaints from people I call that they hear an echo of themselves talking on the call. This happens only when I use a wired headset or talk via speaker. When I remove the headset during the call the echo goes away. I am running los14.1-20180105-NIGHTLY-osprey.

In other devices (for example shamu), this behaviour was caused by a misconfigured "mixer_paths.xml". For osprey, the section "headset-mic" does only contain entries that seem to raise the value for ADC2. On other devices, the "headset-mic" entry sets the value for the other ADCs to zero (0).

I am no expert for the mixer_paths.xml - so my question is: Is there a possibility that the echo is caused my the (maybe incorrectly set) Analog/Digital Converters for the "other" microphones are not set to 0 during headset mode?

Since I am not allowed to post urls:

github.com/LineageOS/android_device_motorola_osprey/blob/f46152c86e917c70c6f362e0437307960b9766d8/audio/mixer_paths.xml

github.com/LineageOS/android_device_moto_shamu/blob/3112ad5dd67bf805ab67ae1164fd761e38a656d5/mixer_paths.xml

Looking forward to hearing from you,

Sebastian
[Moto G 2015 Original Android Development] squid2:
The ACDB (audio calibration database) loader is broken on the build you are using. It will be fixed in the next build. In the mean time, install my Squid Kernel r22b, and let me know if that fixes your echo.
[Moto G 2015 Original Android Development] panagiotis15:
Originally Posted by Dark Scorpian View Post

The update of 10/01/2018 it makes the call volume so LOW(it also low at Loudspeaker and it's too hard to hear someone's voice in the public area) please Replace the old one Thank you

I have exactly the same issue!
[Moto G 2015 Original Android Development] IronTechmonkey:
R-E-A-D

T-H-E

T-H-R-E-A-D

This question was answered in the post immediately preceding yous as well as repeatedly in the past few pages. Volume is obviously a work in progress which should be fixed in the next build.
[Moto G 2015 Original Android Development] yeissondevany:
Wifi works at half the download speed.

thank you for development on our motog 2015.

Mi question is: I had installed a rom 8.1 on my xt1543 and my wifi speed not working correctly, i did several test and they all worked at half download speed. I have decide install lineage os 14.1 (lineage-14.1-20171229-nightly-osprey-signed.zip) and the cell phone worked well at full dowload speed until the last update (lineage-14.1-20180105-nightly-osprey-signed.zip).

What could I do to solve it?, I would appreciate collaboration in this regard.
[Moto G 2015 Original Android Development] spectkiller:
is there any update for the 20180119 build ? i am eagerly waiting ,,, Is it uploading today or tomorrow or this week will also skipped ? [MENTION=5119654]IronTechmonkey[/MENTION] or anyone can give their precious time for answering me!!!
[Moto G 2015 Original Android Development] rahul9999:
Here is the latest 19.01.2018 build :) https://saimei.ftp.acc.umu.se/mirro...neage-14.1-20180119-nightly-osprey-signed.zip

Changelog -

https://www.cmxlog.com/14.1/osprey/#
[Moto G 2015 Original Android Development] IronTechmonkey:
LOL, just because I have a big mouth does not make my time any more precious than yours, nor do I have any special insight. Much of this can be learned by reviewing the lineage OS Jenkins build queue although that does take some getting used to): https://jenkins.lineageos.org/view/all/builds. Whatever problem there was with the build queue continued into early this week but seems to have been fixed, and official Opsrey build has been released.

---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------

Why re-post a separate link to an official build that is available on the official site? Being familiar with your user-name and knowing that you are always helpful in regards to sharing such information I would probably trust the link, but I don't see the need for it today. There is often a short bit of time when a build may be listed as complete but the link may not function. IMO in that case it is better to let people go to the official site when the link is live, or to inform them about that lag, rather than reposting the build elsewhere. If download servers became unavailable after some people got the official build it would be a different story.

In any event, Yay! we got a new build, and it is full of 2 weeks worth of commits as well as a bunch of device specific kernel stuff.
[Moto G 2015 Original Android Development] guest_2011:
I haven't updated in many months. Everything i need seems to work ok except for BT/wifi range issue which is not really a big. Based on what i read it's not a good idea to update because recent updates are buggy? Why does it happen? Why create new builds if old isn't broken? May be a stupid question i shouldn't ask. I don't know....
[Moto G 2015 Original Android Development] coolguy_16:
Just an FYI, the latest official build(20180119) may still have IMS settings crashing as this commit wasn't merged in this build.

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

Should be ready in the next build.
[Moto G 2015 Original Android Development] squid2:
Today's build should be good.

Migrating to newer proprietary binaries fixes security issues and brings improvements to things like the location stack. Changes to proprietary binaries require changes to other parts of the system as well, and sometimes things are missed, and these bugs are not caught before the changes are merged in. They get fixed in time, and once they are fixed, it makes the ROM better than before.
[Moto G 2015 Original Android Development] Psicovirus:
Hello! I'm still having the whatsapp's videos error with the last build!

Thanks!
[Moto G 2015 Original Android Development] rahul9999:
I have clean flashed latest nightly 19.01.2018 just now.. (Not rooted yet)

VoLTE is working fine

No issues with WhatsApp videos playback till now (In WhatsApp status videos also)

No IMS settings crash here for me yet

Incall & General Volume is pretty loud for me.

Great Work [MENTION=6485916]squid2[/MENTION]

I suggest clean flash to avoid any errors.. :)
[Moto G 2015 Original Android Development] Khaled Gargary:
finally sound Volume is repaired in new build ... i have faced no problem with this new build till now

do all of u use the stock Kernel or there is better one for Battery ? i used to use Optimus but i guess its build is old and i have some issues with

wifi with it ..