yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] unqualified:
You may have already seen, but there was a patch for Falcon here: https://xdaforums.com/moto-g/general/ant-moto-g-4g-maybe-t2875420

Unfortunately the user who posted that patch, antftw, seems to have been a bit of a phantom, with only that one thread.

The MSM8916 is used on other phones that are ANT+ certified (Galaxy J5). I think Motorola just didn't want to pay for licensing and add cost to the phone. Maybe the patch was device specific and just never made it past CM?

Seems like it just needs to be told it has ANT+, by activating a few things in the build.

Not a high priority, most Android users don't have a ton of ANT+ devices like me, but would be cool if this type of patch could expand the capabilities of a whole bunch of phones.

My old Moto G falcon is still in use as a dedicated bike computer because of that feature!
[Moto G 2015 Original Android Development] IronTechmonkey:
I don't recall ever seeing it on Mote E 3g 2nd Gen (Otus), Moto G3 (Osprey) or Moto G4 (Athene), just Moto G 4g (Peregrine).

I can dig it but without much demand for it (statistically), and to one of your points, this may be a limitation of the device or its manufacturer support.

OT-

So that's what all those sensor settings in Orux Maps are for. Ride on!

- Done OT
[Moto G 2015 Original Android Development] :
I have the same problem like on AICP here, when i want to rebbot phone i have 90% freez screen :( any solution what is cousing, on clean flash ?
[Moto G 2015 Original Android Development] IronTechmonkey:
That could be the same as this: https://jira.lineageos.org/browse/BUGBASH-798. If so please do add notes and logs to the ticket. I work around it by installing squid2's Osprey kernel.
[Moto G 2015 Original Android Development] :
this is literaly exact the same problem i have on LOS and AICP - so BIG thx for replay, now i have to learn how to add notes and logs to a ticket and here we go, cheers
[Moto G 2015 Original Android Development] IronTechmonkey:
IIRC you are the 3rd person to mention it here and in each case it seems, fairly definitively, to be the same issue. You would have to create a Jira account (which is free) after which you can add notes and or logs. Even if you don't have logs the notes might help. As to logs, the trick is to learn how to get the last kernel message, and to have that information at your disposal (mentally or on "paper") when the freeze occurs, then force boot straight into TWRP, to find and copy the log files to a safe place with TWRP's native file manager.
[Moto G 2015 Original Android Development] :
this look to complicated, i just create acc and add some mp4 whith this bug for now :)

BTW this bug is on LOS and AICP for 100%
[Moto G 2015 Original Android Development] IronTechmonkey:
Well, no more complicated than holding power and vol down to boot to recovery and then copy a file, but at least the ticket has another vote. Tx.
[Moto G 2015 Original Android Development] Hedied4me:
I too can confirm that I also receive random reboots while on Los 14.1. However to the best of my memory I have not received any random reboots on Los 14.1 while using squid kernel.

Edit: sorry I did not mean random reboot but rather freezing on reboot.
[Moto G 2015 Original Android Development] :
I will test it tomorrow :)

EDIT 23.12.2107 after flashing squid KERNEL i did, just now 10 reboots and 0 freezes - normaly i will have couple of time to freez my phone on reboot ;) so i stay on SQUID ;)
[Moto G 2015 Original Android Development] squid2:
I''ve known about this bug for some time, and as you have noticed, it seems to be a bug specific to the LineageOS kernel. My custom kernel doesn't have this bug, but I don't know for sure when this bug was introduced or why it doesn't happen on my kernel. I do want to look into this when I have time, but it may be a bit of a PITA to test because the bug appears random and only happens sometimes.
[Moto G 2015 Original Android Development] squid2:
Test build with new blobs

I've been working on extensive security patching for this ROM lately, and part of this effort includes migrating to newer versions of proprietary binaries taken from the Nougat stock ROM (for lux/harpia). I've updated nearly every prebuilt binary, and have also done extensive kernel patching for both security and compatibility with new binaries. I've made a build with these changes. I'd like to have them well tested before I merge them into official LineageOS for this device family. Please test this build for all your normal usecases, and let me know if this breaks or fixes anything for you compared to regular official weekly builds. Please use the bundled kernel for testing, and not any custom kernels. If your carrier supports VoLTE, also let me know if VoLTE still works on this test build. Be aware that since this is an unofficial build, you will have to do a clean install. You can back up your official build with TWRP, do a clean install of this test build., and later restore your official build backup if you'd like.

Download link: http://www.mediafire.com/file/766jtg9fix7agaa/lineage-14.1-20171223_230804-UNOFFICIAL-osprey.zip

For those who want to see the actual changes, look at LineageOS gerrit for the device side, and here kernel and binary wise.
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for the status update. Fortunately, by definition of when it occurs this has not been a high impact issue.

Indeed, I could hardly find a commit without your name on it upon last review. Will test this build through the next few days days. Thanks!

[EDIT] [MENTION=6485916]squid2[/MENTION], In the the test build (which is running generally fine except for old issue camera killing processes) with OpenGapps Pico and LOS SU the reboot freeze occurred, after which I force rebooted into TWRP and got a dmesg log for what that is worth (attached here rather than at Jira since this is on unofficial build).
[Moto G 2015 Original Android Development] IronTechmonkey:
FIY, Although this week's update was light (seemingly for most devices) Alberto97 and squid2 have been busy bringing blobs and stuff from Addison to Osprey for next week's build; See starred commits: https://www.cmxlog.com/14.1/osprey.
[Moto G 2015 Original Android Development] sethgreen:
if i install this rom, after, i can reinstall stock rom 6.0.1 without problem?
[Moto G 2015 Original Android Development] samir.saurav:
Yes, make sure you have clean flash.
[Moto G 2015 Original Android Development] santo_007:
What are these blobs from Addison. How will they help .Can you please tell me? (I read that blobs are like drivers)
[Moto G 2015 Original Android Development] IronTechmonkey:
I don't know how they specifically will help but this may be related to what squid2 mentioned on previous page: https://xdaforums.com/showpost.php?p=74943589&postcount=5599. The context could be (I'm sort of guessing) that since Osprey never got an official Nougat/Oreo update from which to get those things they're being gotten elsewhere in the family of devices.
[Moto G 2015 Original Android Development] santo_007:
Nothing but making lineage os more stable by merging proprietary blobs from devices which already got nougat update.is it right
[Moto G 2015 Original Android Development] pratyushshopping:
OTA ruins everything.

Sim card not detected.

All zips including magisk xposed and google services stopped working.....

Clean flashed again
[Moto G 2015 Original Android Development] IronTechmonkey:
More than just stability, in fact IIRC this is sometimes the difference between being maintained in CM/LOS and not being maintained in CM/LOS.

---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------

That is what you could expect when dirty flashing a ROM containing 3rd party mods such as xposed and magisk. Those 3rd party factors, especially Xposed, have no place in ROM tests and bug reports. Most tutorials about ROM testing or bug reporting, including this XDA Wiki article, will tell you the same thing: https://xdaforums.com/wiki/Reporting_A_Problem_-_Android.
[Moto G 2015 Original Android Development] pratyushshopping:
Isn't OTA Using Updater supposed to be dirty flashed. The update get auto flashed using native updater app
[Moto G 2015 Original Android Development] unqualified:
Not to beat a dead horse, but with a little more digging on the ANT+ question, I noticed the msm8916.mk file in other <device>-msm8916-common repositories under Lineage (Asus and BQ particularly) contains the following, whereas the

motorola

version of msm8916-common does not:

# ANT+
PRODUCT_PACKAGES += \
AntHalService \
com.dsi.ant.antradio_library \
libantradio

with this added under the #PERMISSIONS section

external/ant-wireless/antradio-library/com.dsi.ant.antradio_library.xml:system/etc/permissions/com.dsi.ant.antradio_library.xml /

And in the Lineage OS 14.1 source for android_device_motorola_msm8226-common, it has those same lines in msm8226.mk. As noted earlier, my old Moto G falcon actually works flawlessly with ANT+ in Lineage OS 14.1 as well (flashed it to test).

It can't be that easy, can it? Probably not... but then again, that's pretty much what they seem to be saying here:

https://github.com/ant-wireless/ANT_in_Android

And the lines above are essentially the exact contents of this blob (with the addition of ANT Radio Service and ANT Plugins Service, which can also just be downloaded from the play store):

https://github.com/ant-wireless/Android_build/blob/master/ant-wireless.mk

I think the boardconfig would need to be BOARD_ANT_WIRELESS_DEVICE := "qualcomm-smd", which would then I assume generate the lib files from here https://github.com/LineageOS/android_external_ant-wireless_ant_native, but not 100% sure on how all this works

I may have to learn how to compile to try this out.
[Moto G 2015 Original Android Development] IronTechmonkey:
You're missing the point. This thread is for testing the ROM explicitly without third-party modifications such as Xposed and magisk. How many times does that need to be said? Get Xposed and magisk out of the equation by clean flashing without them. Then the next time you flash, see if a dirty flash works, and if the dirty flash does not work and then go to clean flash....then your ready to report possible LOS ROM bugs (which is the purpose of this thread).
[Moto G 2015 Original Android Development] pratyushshopping:
Ok man I've got the point now with the 3rd party mod I can't report a bug. Thanks for replying
[Moto G 2015 Original Android Development] IronTechmonkey:
As to Xposed, look at it this way: If you remove the chassis from a new car and replace it yourself with something unsupported by the manufacturer, then if something goes wrong after that point you could not expect the manufacturer to be prepared with proper spare parts and wrenches or expect them to be willing to work on it at all.

BTW, IMO your issues may not be caused by Xposed or Magisk and might be rectified by clean flashing with those 3rd party things....but then if there are problems you would still be outside the standard LOS ROM testing box and would have to reflash clean without Xposed to create a good bug report.
[Moto G 2015 Original Android Development] IronTechmonkey:
I don't know if that horse is dead, resting or just got left out of the stable, but after you last mentioned it, (incidentally teaching me the practical value of Ant+) I purchased a replacement new Moto G Peregrine (at an embarrassing price - more than the Moto G4s on sale at the same store - total gouging) in case I have a chance to play with Ant+ peripherals (and because Peregrine has a full compliment of sensors).

Anyhow, steering back on-topic to Osprey, you seem to have your mind well wrapped around this. Although Jira does not officially take feature requests perhaps it would still be worth creating a ticket, especially now that squid2 is working on the ROM (no knock on Alberto97, it's just good to have extra help). At worst it might be rejected, in the middle you might get an answer about why it is not in Osprey, and at best perhaps it could be added.

If you decide to cook something up I'd be glad to test it, but whatever you decide to do, it might be good to wait until after the upcoming bunch of Osprey specific (or branch specific) commits which will be in this week's build, speaking of which...

On a separate note in regards to the shutdown/reboot freeze: There is this commit (https://review.lineageos.org/#/c/200690/) announced here

https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-21332.
[Moto G 2015 Original Android Development] unqualified:
So I tried another approach, and made a flashable zip following the template of the one in the Moto G thread mentioned previously, only I replaced all of the files with the identical versions from a LineageOS 14.1 build for the BQ Aquaris E5 4G vegetalte (the one that uses "qualcomm-smd"). Low and behold, it actually worked! It picks up my HR monitor and I was able to upload a dummy run file from my Garmin to Strava using Ant2net PRO.

So I can confirm, this device has ANT+, just needs to be turned on in the ROM, and should be BOARD_ANT_WIRELESS_DEVICE := "qualcomm-smd".

I'm not sure how to use the Jira system, but I can try to mention it there if the maintainers don't see it here. Not a bug, like you said, more of a feature request.

For now, the flashable zip is posted here https://xdaforums.com/showpost.php?p=75069149&postcount=31
[Moto G 2015 Original Android Development] santo_007:
Is it possible to make a flashable zip of commit.i know it is a kernel level change . But I have a doubt whether we can change kernel files
[Moto G 2015 Original Android Development] adrianogoes:
No Audio

Hi ALL.

I have a Moto G XT1543 (osprey).

I was using 20171102 build and out-of-nothing I got no audio (media) through (bottom) speaker.

I was using UltraDevs Kernel for Osprey v7.0 and Magisk. The problem appeared after upgrading Magisk to 15.2 but was not right after the upgrade. I used the phone for almost 24 hours with some boots in between. This morning my alarm clock did not ring.

Bluetooth audio is working and I also make phone calls without problems (I can hear and I'm heard).

I've tried to clear Dalvik/ART and cache with no success.

I did a clean install of 20171229 (with Lineage SU and without UltraDevs Kernel and Magisk) but the problem persists.

Any ideas?

Is it possible to confirm that could be a hardware failure?
[Moto G 2015 Original Android Development] marchelius:
20171229 version works perfectly.

Try clean install, wipe everything and don't use custom kernels etc.

Use SuperSU v2.85 from Chainfire

Maybe no audio is a hardware problem in your Moto.
[Moto G 2015 Original Android Development] adrianogoes:
Thanks!

Out-of-nothing, after several boots and inserts/detachs of headphone (jack), the audio returned.

Weird as it is...
[Moto G 2015 Original Android Development] IronTechmonkey:
Since, squid2 has been recently active with Osprey here and at LOS Jira (and has worked with many Moto devices) you could mention him in your previous post and ask if this might be possible. If you don't get a reply, then after a few days or a week you could create a Jira ticket.

Jira is an enterprises level issue tracking system which Lineage OS uses. Some LOS development does happen outside of the LOS Jira ticketing system (and even outside of the commits listed at LOS) but Jira can be a good place to submit (viable) reports. It is also an excellent place to research potential issues.

Categorization as issue or feature request aside, what you've got there is not only viable but includes a potential solution. I hope there is not some silly proprietary obstacle to implementing it. However it goes, thanks!

BTW, do you know off hand if there is a way to test your tweak between Osprey and another Ant+ enabled Android (Peregrine)?
[Moto G 2015 Original Android Development] unqualified:
[MENTION=6485916]squid2[/MENTION] I just went ahead and set up a pull request, and gave the background in the description. It is only a few lines of code, and I figured it was more straightforward that way. A little sloppy since I've never done that before and didn't know how to delete the first version of my commit. https://github.com/LineageOS/androi...6-common/compare/cm-14.1...unqualfied:cm-14.1

[MENTION=5119654]IronTechmonkey[/MENTION] I think the peregrine is another msm8226 device like the falcon, so should be enabled already in Lineage, right? My pull request above is actually identical to the code that is already in motorola_msm8226-common.

All you should need to do on a peregrine in Lineage is download ANT Radio Service and ANT+ Plugins Service to enable, then use an ANT Tester app to check it.
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes, in Ant+ Tester, LOS 14.1 on Peregrines includes built in Ant+ and the Ant HAL Service, and the other components could be installed from PlayStore:

On Osprey I did not see any difference before or after flashing your zip but ATM this device is running custom kernel and modified minfree settings and could I should also verfy my process. Will try to do that with flash of upcoming build. Here is how it looks with all the available services installed:
[Moto G 2015 Original Android Development] sargam44:
Anyone notice after flashing latest nightly 5th jan. HD capable notification removed.
[Moto G 2015 Original Android Development] unqualified:
Huh. It definitely works with clean LOS14.1 on Osprey, and now confirmed on the other thread also on Moto G4 Play harpia and Moto E LTE surnia. This is what my Osprey shows.

Check if the AntHALService folder is in /system/app? Maybe flash didn't stick?
[Moto G 2015 Original Android Development] Rafiue_SRA:
5/01 changelog?

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

Any changes from previous build? Which security patch installed?
[Moto G 2015 Original Android Development] IronTechmonkey:
Yep, possibility of issue in my own process is the first thing to check for. I'm preparing for clean flash of Osprey later today and will check for the AntHALService folder.

[EDIT] [MENTION=5547760]unqualified[/MENTION], Testing before the clean flash: The AntHALService folder was not being created (confirmed in TWRP file manager during same session and and in OS after boot) until: In TWRP mount system then, flash zip, then confirm presence of AntHALService. Then...Groovaliciousness!

As to Jira, if you are already comfortable generating pull requests you may be ahead of Jira, but if you don't get a reply I would still suggest creating a Jira ticket just to get a definitive answer.
[Moto G 2015 Original Android Development] unqualified:
Awesome! I had to mount /system also for it to 'stick', I just added that detail to the zip file post. I'll try to keep the conversation around the zip over there as it feels slightly off-topic here.

I wouldn't say I'm 'comfortable' generating a pull request, but I did it anyway, taking comfort in the 'allow maintainers to make edits' checkbox. I'll leave them alone for a couple weeks and then look at a Jira.
[Moto G 2015 Original Android Development] mrViZhy:
Hello All,

On today build i have very silent sound on calls.

Have somebody same problem? Do you know how to fix it?
[Moto G 2015 Original Android Development] figg2blet:
Same audio bug with latest build, can't control volume while calling, sound very low with speaker on, so back to 1229 build. Everything works fine now.
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI: Today the Ant+ Tester app received an update and it no longer appears as a compatible app at PlayStore (on any of my LOS devices) and a screen-shot of the new version has an additional value which it tests for, and another Ant+ related utility (Sampler?) was pulled since yesterday. I'm hoping that the indications it gave us are are not false positives. Since the app is also now missing in Playstore for Peregrine which is natively Ant+ ready I don't put too much stock into this, but thought it was worth mentioning.
[Moto G 2015 Original Android Development] unqualified:
Sheesh, great timing. There's another ANT checker app here: github.com/ant-wireless/ANT-Android-SDKs/blob/master/ANT_Android_SDK/Tools/Android_ANTSupportChecker_1-2-0.apk

Definitely not false positives, I just used ANT+ with my heart rate monitor in the Wahoo Fitness app for an hour this morning on my osprey, simultaneously with a BLE footpod using a treadmill, with zero issues.
[Moto G 2015 Original Android Development] pratyushshopping:
I don't know if this counts as a Bug.

I younturn the torch on Using Notification Toggle You have to do Chop Chop gesture twice to turn it off instead of one
[Moto G 2015 Original Android Development] Osid:
I'm using 20180501 nightly.

VoLTE is working?

On Phone Info activity, VoLTE provisioned is on.

Under "IMS status" it says Not registered and Unavailable for all.

If you try to go to IMS settings under "Phone -> Settings -> Calling Accounts -> (SIM) -> IMS Settings" it causes com.android.phone to crash "com.android.phone has stopped".

Under logcat it says

1-06 22:33:50.453 20938 20938 I QImsService: ImsSenderRxr : [0018]> REQUEST_GET_IMS_CONFIG[SUB0]
01-06 22:33:50.453 20938 20938 I QImsService: ImsSenderRxr : Message data: [0, 0, 0, 23, 11, 13, 18, 0, 0, 0, 16, 1, 24, 45, 32, 0, 8, 58, 16, 0, 29, 0, 0, 0, 0, 40, 0][SUB0]
01-06 22:33:50.457 20938 21016 I QImsService: ImsSenderRxr : processResponse[SUB0]
01-06 22:33:50.457 20938 21016 I QImsService: ImsSenderRxr : Response data: [11, 13, 18, 0, 0, 0, 16, 2, 24, 45, 32, 2][SUB0]
01-06 22:33:50.457 20938 21016 I QImsService: ImsSenderRxr : Tag 18 2 45 2[SUB0]
01-06 22:33:50.457 20938 21016 I QImsService: IFRequest : [0018]< REQUEST_GET_IMS_CONFIG error: 2
01-06 22:33:50.458 20938 21018 I QImsService: ImsConfigImplHandler : Message received: what = 1
01-06 22:33:50.458 20938 21018 I QImsService: ImsConfigImpl : Notifyall
01-06 22:33:50.458 20938 20938 D ImsSettings: loadVideoCallQualityPrefs, vqValue = -1
01-06 22:33:50.474 20938 20938 D AndroidRuntime: Shutting down VM
01-06 22:33:50.475 20938 20938 E AndroidRuntime: FATAL EXCEPTION: main
01-06 22:33:50.475 20938 20938 E AndroidRuntime: Process: com.android.phone, PID: 20938
01-06 22:33:50.475 20938 20938 E AndroidRuntime: java.lang.NoSuchMethodError: No static method shallTransmitStaticImage(Landroid/content/Context;)Z in class Lorg/codeaurora/ims/utils/QtiImsExtUtils; or its super classes (declaration of 'org.codeaurora.ims.utils.QtiImsExtUtils' appears in /system/framework/telephony-common.jar)
01-06 22:33:50.475 20938 20938 E AndroidRuntime: at com.qualcomm.qti.ims.ImsSettings.displayStaticImageOptions(ImsSettings.java:202)
01-06 22:33:50.475 20938 20938 E AndroidRuntime: at com.qualcomm.qti.ims.ImsSettings.onResume(ImsSettings.java:87)
[Moto G 2015 Original Android Development] IronTechmonkey:
Nice catch. Reproducible on my XT1540 (with or without SIM inserted) by : Phone app > Settings > Calls > IMS Settings = com.amdroid.phone FC

Thanks for the confirmation. Yep, just fluke of timing which has since played through. Whatever becomes of this, thanks again. Meanwhile I'm playing with the unmodified ROM to test other stuff, speaking of which, from lineage-14.1-20180105-nightly-osprey-signed:

- Reboot/Shutdown freeze: seems fixed. Usually by this point (2 days into a flash) the issues has occurred a few times but it has not yet occurred.

- Minfree settings: Discalimer: The issue is not that the minfree settings alone are bad, but since modifying them mitigates the issue and I don't know what the underlying problem is, I refer to this a minfree/LMK issue. Whatever it is called it still exists. With default minfree values; using the native camera to take a single picture kills other apps/services (LMT completely, Tasker status bar bits). Setting minfree values at half of their default significantly mitigates this.