yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] harry9713:
I am facing call disconnect issue in lineage 05/18 build. The call won't last more than 4minutes and it gets disconnected for all contacts. Am using Google dialler (used the aroma package of gapps..is that a problem? ?) . Also using ultradevs custom kernel☺️ . Is there anything to solve this problem? Help!
[Moto G 2015 Original Android Development] KrisM22:
See if problem occurs with clean flash and stock kernel and no addons.
[Moto G 2015 Original Android Development] suhasinip:
I clean flashed this ROM and then flashed magisk, but the default camera app and any other camera app I install doesn't work. It just shows a black screen. Anyone having the same problem?
[Moto G 2015 Original Android Development] KrisM22:
which rom? which kernel?
[Moto G 2015 Original Android Development] suhasinip:
Official LOS 14.1, stock kernel
[Moto G 2015 Original Android Development] KrisM22:
my bad - what's the

date

of the LinOS rom? (settings/phone/lineageos version)
[Moto G 2015 Original Android Development] suhasinip:
Latest available. i.e 18th May.

Do you recommend a different kernel? Squid kernel looks great but hasn't been updated in a while so I was wondering if I should use it with latest build.
[Moto G 2015 Original Android Development] KrisM22:
I don't know about different kernels - can only do stock in this thread. If you use a different kernel probs would have to be done in that thread.

I asked because 5-11 had the problem where the Osprey camera preview didn't move and was very dark. There was a workaround using a couple switches in Developer Options. 5-18 fixed that problem, so this is new to me. Any mods? any theme engine?
[Moto G 2015 Original Android Development] vinardi32:
Download link for 5/18 not working. Could someone please check to reactivate it? Thanks!

EDIT: Working now!
[Moto G 2015 Original Android Development] knpk13:
No. Like I said. Fully Stock 18th may build. And magisk for root.

Edit: that's my mom's account (I posted it through that)
[Moto G 2015 Original Android Development] KrisM22:
If this has been going on over different releases, file a bug(weekends), If it worked before, file a regression. Thanks.
[Moto G 2015 Original Android Development] Paulo Siqueira:
Dear Sirs

I'm having problems on my gps when it enters the 3g network. There seems to be interference. Is there a solution to this problem? I am using lineageOS from 05/18/2017.

Can someone help me?

Hugs.
[Moto G 2015 Original Android Development] KrisM22:
a) has it ever worked? what roms and dates? stock?

b) location set to high accuracy?

c) some quick googling indicates possibly phone, possibly SIM.
[Moto G 2015 Original Android Development] Subinsmani:
hai, i have found very small bugs.. just for info...

when i presss blank side of notification bar, the touch shows on under date and time or above the wifi icon...

i upload one video...

please verfy that others have same bug or i have only...

[emoji14]

https://drive.google.com/file/d/0BzTYUeTjUxfrRHFGQm9nUElDS0U/view?usp=drivesdk
[Moto G 2015 Original Android Development] rahul9999:
Not facing such issue.
[Moto G 2015 Original Android Development] outlaw1313:
Guys, i have Moto 1541 and my situation: I had some lags on stock firmware and decided to flash crDroid, everything was fine, but the fact is when I take pictures so fast, Camera software lags, become busy and after it shutdown. I can take only 15 photos in fast mode and after it have this error. Using stock firmware i can take more 60 photos without busy and 30 without lags in camera software. I down know why it happen may be some problem with memory. Whoes know this firmware (LineageOS) have this problems? So what about battery saving in camera mode, this firmware hungry on energy?

My standard lags on stock firmware:

1) Turnings off Duration of the youtube video seconds is 4.

2) Turnings off Duration of web browser is 8.

And finally: Whoes have the highlight of the edges in the photo? By this effect, the photos are not terribly realistic.

PS Sorry for my bad english
[Moto G 2015 Original Android Development] rahul9999:
Hello mate.. my suggestion is flash latest lineage os nightly.. it will be release by today EOD.. I'm not facing such issues on Lineage OS.. performance & battery life is good.. for camera i would suggest to use this one https://xdaforums.com/2015-moto-g/themes-apps/apps-moto-camera-gallery-cm13-based-roms-t3360854
[Moto G 2015 Original Android Development] sargam44:
Hey anyone tested today's nightly? Tell us how's​ your experience.
[Moto G 2015 Original Android Development] rahul9999:
Not released yet..
[Moto G 2015 Original Android Development] Subinsmani:
waiting for mirror link... specially waiting for safetynet... :D
[Moto G 2015 Original Android Development] rahul9999:
here you go https://gensho.ftp.acc.umu.se/mirror/lineageos/full/osprey/20170525/lineage-14.1-20170525-nightly-osprey-signed.zip

---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------

Lates Official Nightly Download https://gensho.ftp.acc.umu.se/mirror/lineageos/full/osprey/20170525/lineage-14.1-20170525-nightly-osprey-signed.zip

Official Change log https://www.cmxlog.com/14.1/osprey/#
[Moto G 2015 Original Android Development] Paulo Siqueira:
Dear

In motorola G3 osprey only worked when it was in ltg. When it connects in 3g the gps stops working.

I am using the official lineageOS version of 05/18/2017. Your phone is set to high accuracy.

I already installed GPS Status PRO which shows the loss of the GPS signal when the connection is 3g.

Has anyone ever experienced this?
[Moto G 2015 Original Android Development] KrisM22:
sorry - " in ltg" means what?
[Moto G 2015 Original Android Development] Paulo Siqueira:
Dear,

Sorry for my bad english

LTE .. here in Brazil we call 4G

Hug,
[Moto G 2015 Original Android Development] KrisM22:
If it didn't work correctly on 3g in

stock,

the problem is probably with the phone or the SIM.

Assuming you made a backup of stock after you flashed TWRP, just backup where you're at, wipe, and restore stock, and test it.
[Moto G 2015 Original Android Development] Paulo Siqueira:
Dear,

The SIM I already changed. Has anyone ever complained about this problem? Here in Brazil the claim is recurrent even in other brands' cell phones.

Hug,
[Moto G 2015 Original Android Development] KrisM22:
I have not heard of it but I am only 1 person.
[Moto G 2015 Original Android Development] IronTechmonkey:
That indicates a possible regional or provider issue issue, not necessarily an LOS ROM issue. You might consider contacting your provider to confirm the correct APN settings for your service and make sure those settings are in the ROM. If they are not in the ROM or if they are correct but you still have the problem the you could file a bug report including logs. If you know other people in the region affected by the same issue you should compare with them to see what the common factors are (if no-one here has had the same experience).

---------- Post added at 09:05 PM ---------- Previous post was at 08:55 PM ----------

For what this is worth: I've flashed May 25 LOS build with OpenGapps Pico May 25 and LOS SU on both Osprey and Peregrine. With root enabled for apps: On Peregrine Playstore reports device certified but on Osprey it reports as uncertified. I dont know what the differences are between the way that commit was implemented between the 2 devices.
[Moto G 2015 Original Android Development] Subinsmani:
through that fingerprint i got my device certified

..

still apps are not opening...

on testing safetynet it pass..

but dont know now what all requirements need to pass...
[Moto G 2015 Original Android Development] KrisM22:
with the Magisk module the modules will open (at least things like Netflix)
[Moto G 2015 Original Android Development] Subinsmani:
yes only hope magisk... :D
[Moto G 2015 Original Android Development] IronTechmonkey:
It's nice to have that workaround but of more immediate importance to LOS 14.1 on Osprey is the fact that there may be something wrong with that commit... if anybody cares to test for it. ;)
[Moto G 2015 Original Android Development] KrisM22:
I'll bite - How would I test for it?
[Moto G 2015 Original Android Development] Subinsmani:
k i got some information about safety net... this has answer from google official dev...

so non official build will not get clear safetynet...

https://www.xda-developers.com/goog...-with-root-and-android-pay-in-the-xda-forums/
[Moto G 2015 Original Android Development] IronTechmonkey:
Perhaps confirm whether Playstore reports certified or uncertified in whatever you've already flashed (perhaps stating the obvious there). Beyond that I'm wondering what would happen with a clean flash of Osprey/Gapps without any SU. I should also confirm that Peregrine without root installed (or at least before enabling root for the first time) can see Netflix as it could in last week's build.

I suspect there is a better way to test the hiding of SU but I dont know what it is. To learn more in that regard I'm comparing sub components of the pertinent commit for Osprey and Peregrine (there are some small differences but I dont understand their significance) and checking the build.prop of both devices (they both have a line with similar syntax referring to fingerprint although the syntax differs from the lines being used for the safetynet fix).

---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------

Google's "logical" argument for doing this is rubbish but at least it is good to know what they are up to. Thanks. IDK if this also affects the visibility of netflix but will test for that when I have a chance (after a few days fo recovery from today 2 device flash).
[Moto G 2015 Original Android Development] KrisM22:
Yeah I'm in the middle. I have a testbed with no su. PokemonGo plays, testing playstore. Also 2 more sets of tests with LinOS su, and with SuperSU. Remember - there is a delay before playstore "works".

EDIT: 5-25-2017 LinOS rom

(this is all based on squid's TWRP which does NOT have SU.)

No SU: all work: PokGo, Netflix, uncert, integrity.

LinOS SU: nothing works whether root is ena or disa in Dev Opt.

SuperSU: nothing works whether root is ena or disa in SuperSU in app drawer.

EDIT the last 2 work fine after you remove su (addonsu-remove, or Full Unroot). So if you don't use root much this is viable.
[Moto G 2015 Original Android Development] Sachin ET:
Yes i have noticed this issue From 30-3-17 built........since it doesnt cause any problem i just ignored........
[Moto G 2015 Original Android Development] KrisM22:
yes, a second larger touch is shown but doesn't appear to do anything.
[Moto G 2015 Original Android Development] outlaw1313:
Thank for your answer. Yesterday I flashed it and got problems: camera shutdown after 5 fast taking pictures. I dont know why. I think this problem have everybody. You can try it just take some (5-20 photos) one by one in HDR mode and after it change to standard mode and take some photos again. After mod change ones again and take some photos more you can get this problem. Software that you advice me nice but i could not capture video in slowmod and autofocus work after every captured photo. Right now i back to stock. May be you can give me another advice?
[Moto G 2015 Original Android Development] scattey:
rm
[Moto G 2015 Original Android Development] KrisM22:
Run Simple System Monitor while you're doing that and post your RAM graph. I'm betting RAM problem. eg not enough. - try [MENTION=5119654]IronTechmonkey[/MENTION] 's kernel aduitor trick. - my version: settings: Low Memory Killer: tap "very light" and tap apply on boot if you want (leave more agressive).
[Moto G 2015 Original Android Development] pdeadm:
Is it just me or May 25 nightly is a bit laggier than May 18 one?
[Moto G 2015 Original Android Development] asros:
Yesterday i flashed 25 may version. With su. Then i placed back several apps with titanium Backup. Next i removed su with zip file. Restarting and cleaning cache. And voila no problems installing Netflix or Pokemon Go.
[Moto G 2015 Original Android Development] KrisM22:
See updated post 4743 above -

YES

. I just tested both supersu (Full unroot in settings, say YES to stock boot img, say NO to stock rom) and addonsu (flash addonsu-remove). No need to clean cache. Sometimes takes 10 min for playstore to behave.

So it's good for folks who don't use root much.

---------- Post added at 01:41 PM ---------- Previous post was at 12:49 PM ----------

The rom is fine for me but I have noticed today that sometimes downloads of apps from playstore are only running at 300Kbps. Probably just overloaded.
[Moto G 2015 Original Android Development] IronTechmonkey:
I've been planning some follow up on this so here it is bounced off your post.

For most of last week in May 18 build I tested without changing the LMK settings but still had apps getting "killed" and found that a VPN client (PIA) was one of them. While the killing of some apps is an inconvenience, the killing of VPN client is operationally significant so now I'm using the LMK medium profile with adaptive disabled (I haven't tried the "aggressive profiles" in few weeks).

There is most definitely a big improvement when not using the default LMK settings in the Osprey ROM but I've not been able to find explanations for why the defaults might be so high and what functions those high settings would benefit.

In Peregrine, which by default uses LMK settings resembling the medium profile, the only time apps get intrusively killed is during panoramic camera pictures. The better performance on that lower end device leaves me wondering even more about the default LMK settings in Osprey.

[MENTION=4480917]Alberto97[/MENTION] and [MENTION=6485916]squid2[/MENTION], I've searched for reasons why the LMK settings might be as high as they are on Osprey but every article I find pulls in the other direction suggesting lower settings (although admittedly for older devices, Android versions and ROMs). Could either of you shed some light on why this is so in Osprey?
[Moto G 2015 Original Android Development] Subinsmani:
for those who have miracast issue please install this magisk module....

https://xdaforums.com/apps/magisk/module-miracast-tethering-enabler-adb-t3611335

sry its not helpful no three dots is showing on cast option... :D
[Moto G 2015 Original Android Development] Orange Solution:
Dual Sim radio/modem issue

Hi folks

First of all thanks for the very active osprey community.

I'm using a Brazilian dual sim device (xt1543). Once connecting to the European network, the phone develops his own will and just bounces to several apps, changes settings and eventually will shut down or reboot. On WiFi only it just works great.

Flashing stock modem improves but doesn't solve it.

Anyone with the same behaviour. What data is required to support bugfixing?

Thanks in advance

OS
[Moto G 2015 Original Android Development] KrisM22:
to support bugfixing:
[Moto G 2015 Original Android Development] KrisM22:
[MENTION=2810725]Mama Luigi[/MENTION] and [MENTION=4750427]guest_2011[/MENTION] could you please try BT dropping with wifi in and out again. I just did a quick couple tests and didn't get any BT drop. I don't need logs at the moment. THANKS!!!

Definitely need logs - this is different!

reminder:

https://jira.lineageos.org/projects...rby=created+DESC,+priority+DESC,+updated+DESC
[Moto G 2015 Original Android Development] guest_2011:
What build are you on? I'll update to whatever is the latest and try.
[Moto G 2015 Original Android Development] KrisM22:
5-25 LineageOS, and 5-25 nano opengapps. I've seen a lot of fixes go in for wifi, though none specific, some seemed related. I also noticed that no one has complained about BT in the last month... :)
[Moto G 2015 Original Android Development] niftynick:
I have one unvoiced complaint, in that case. In the last two weeks I gave LineageOS Official, RR and Pure Nexus a run; all three had the same issue with dropouts while at the edge of WiFi range. I figured the reason is the same in all builds, so I didn't report it.
[Moto G 2015 Original Android Development] KrisM22:
If it happens on 5-25, please create a log and add it and comment to the jira with your full system details.
[Moto G 2015 Original Android Development] niftynick:
It does. Logged and commented.
[Moto G 2015 Original Android Development] KrisM22:
and re-commented - very different! Huge thanks!!! Nice log!!!
[Moto G 2015 Original Android Development] IronTechmonkey:
Here is a roundup of a few bugs and their present status as of the May 25th build:

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

Decreasing the "Low Memory Killer" setting on Osprey XT1540 1GB signifigantly improves performance.

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

Confirmed persists in May 25 build and added to the ticket a paraphrasing of the post in which I describe this a few days ago https://xdaforums.com/showpost.php?p=72441316&postcount=4752.

As to finding information about which minfree (LMK) settings should be in effect I still cant find much new information. Case in point is this rather old thread: https://xdaforums.com/showthread.php?t=622666. There are suggestions in that thread about how to tweak minfree settings from build.prop including one for making a specific app of choice persist (https://xdaforums.com/showpost.php?p=13040189&postcount=301), but IDK if those suggestions would work in LOS14.1/Nougat and have not had time to test them.

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

LiveDisplay does not apply the blue screen at night when set to automatic.

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

Possible fix from this commit: https://review.lineageos.org/#/c/174642/

I don't know if the fix (which involves the "twilight state" of the multi stage transition between day/night modes) is related to my most recent observation in the ticket of a correlation between local time zone and GMT-0. [MENTION=6073162]Komapatient[/MENTION], you may have grown weary of testing this but next week’s build might be a good one to test.

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

Increasing system fonts size pushes countdown timer backspace button off screen

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

Confirmed persists in Osprey and Peragrine May 25 build

LOL, Am I the only farsighted person who uses "Largest" font size and uses the countdown timer? IMO a native accessibility feature that is impaired by a native OS setting could merit higher priority and a previous fix for a separate but similar issue could be a guide to an easy fix, but I’ll leave the opining at that. In any event, if others can reproduce this (which should be easy as it is not device specific) it might be helpful if it had mode votes.

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

com.android.phone FC when leaving voicemail sound settings (when visual voice mail is disabled).

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

Confirmed persists in Osprey and Peragrine May 25 build

This bug does not prevent changing the voice mail ringtone even though the phone app FCs at that point so, not necessarily high priority but if anyone can reproduce and add notes/votes to the ticket, that might help determine if there is a provider specific factor.
[Moto G 2015 Original Android Development] KrisM22:
a) too bad no answer yet.

b) yeah, it doesn't work. I thought it used to. I just added "twilight" app.

c) apparently. ;)

d) I followed your procedure

but I get no error. did both cancel, and select sound.
[Moto G 2015 Original Android Development] IronTechmonkey:
The test workflow in the initial report was amended as more information was gathered. Just in case the newer notes were collapsed while you were viewing the ticket:

- Phone app

- Settings

- Calls

- Voicemail (Visual Voicemail is enabled)

- Sound

- Cancel (or select file then OK)

- No FC

- Disable Visual Voicemail

- Sound

- Cancel (or select file then OK).

- FC (Osprey and Peregrine).

If you dont see the issue in the aforementioned workflow maybe provider is a factor after all (although I was making a wild guess when I previously mentioned that) or some other setting.
[Moto G 2015 Original Android Development] KrisM22:
How do I "Disable Visual Voicemail"

EDIT: okay, this requires one add the (in my case) ATT visual voicemail app, which I did, and played around in phone, but no error, but I couldn't see in phone/settings/calls/voicemail where visual voicemail was being activated or deactivated.
[Moto G 2015 Original Android Development] IronTechmonkey:
You might be experiencing what the Peregrine maintainer experienced and described in this comment (https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-13144) where the provider did not support visual voice mail but the fix described in that comment did not fix the issue. The visual voice mail setting, if present, should be in the Voicemail settings panel.

That would inform the ticket as it is an additional indication that the issue is in the native LOS management of these settings.
[Moto G 2015 Original Android Development] KrisM22:
To me this is too user app specific. Not LinOS. ?
[Moto G 2015 Original Android Development] IronTechmonkey:
Cross posted. See previous post.

[EDIT] Link back to post containing information about the following LOS issues (to keep it fresh for at least a few minutes):

https://xdaforums.com/showpost.php?p=72480331&postcount=4763

- Decreasing the "Low Memory Killer" setting on Osprey XT1540 1GB signifigantly improves performance.

- LiveDisplay does not apply the blue screen at night when set to automatic.

- Increasing system fonts size pushes countdown timer backspace button off screen

- com.android.phone FC when leaving voicemail sound settings (when visual voice mail is disabled).
[Moto G 2015 Original Android Development] Komapatient:
I am following the JIRA log and I have tested the patch in my own build for Sony Xperia M (nicki) which had the bug also.

It seems to be fixed. The last two days night mode was enabled. :victory:
[Moto G 2015 Original Android Development] KrisM22:
[MENTION=5119654]IronTechmonkey[/MENTION] - what was the "fix" for bluelight? Tnx.
[Moto G 2015 Original Android Development] Komapatient:
https://review.lineageos.org/#/c/174642/
[Moto G 2015 Original Android Development] KrisM22:
Tnx but how did you apply I?
[Moto G 2015 Original Android Development] IronTechmonkey:
Please dont take this as playing too rough, but for someone with signature that says in big red font "Search/read back before asking" these are easy finds. ;)

Links to ticket and the commit which contains description of fix here: https://xdaforums.com/showpost.php?p=72480331&postcount=4763

From: https://xdaforums.com/showpost.php?p=72483689&postcount=4770 (also described in ticket): " tested the patch in my own build for Sony Xperia M"
[Moto G 2015 Original Android Development] KrisM22:
When I get home. ;)
[Moto G 2015 Original Android Development] IronTechmonkey:
Ahhh, so that was you in the jira ticket. Thanks. Since my devices often held onto the proper setting for 3-4 days I'll test next official build for a week or so then add a comment to in the ticket. Also, I did not want to precipitate a side debate in that ticket but, as you described there I saw no evidence those "random" factors. In fact your tests, and the correlation I noticed between local time and GMT-0, and most importantly the discovery of the missing twilight trigger pull in a much less random direction.
[Moto G 2015 Original Android Development] KrisM22:
1

2

3

4

The big red font replies!!! :)

in 1 I asked the question.

In 2 I was given commit 174642

I looked at that, as I had many times before, and saw a bit of java to be inserted in the next build. I was hoping not to have to re-cook LinOS.

So 3 I asked how to apply it.

In 4 you gave me a bunch of links which repeated the commit number 174642, but I don't see a simple test patch.

---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------

Did you re-cook the whole ROM after adding those java lines, or what simple patch/line did you apply to what module? 174642 just gives me java code to be added to next build. Thanks.

In other words, I would like to test it.