yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
Some follow up to previously reported issues including another anomaly in the camera:

- App killing and minfree (LMK): No change in behavior or status but, [MENTION=7901927]Ouiloui[/MENTION] shared the values for Kernel Adiutor profiles on an Osprey 2GB device where they are much higher and the same problems don't occur. This stands to reason since most of that extra 1GB RAM is free to use for apps with the core system and other stuff loaded into the 1st 1GB. I know the 2GBs are not distinct from each other but there is a logic to this (or so I think).

Very light 19 38 57 76 95 114

Light 38 57 76 95 114 133

Medium 57 76 95 114 133 172

Aggressive 38 57 114 191 267 287

Very aggressive 57 76 95 210 287 306

Thanks [MENTION=7901927]Ouiloui[/MENTION] for those details.

- Another camera oddity (in addition to previously mentioned missing scene modes): In the main camera menu the "Red eye reduction" is missing. As with the missing scene modes this seems device specific to Osprey. AFAIK there are no reason why Osprey could not handle those things while Peregrine can. Many of us, myself included, may be using alternate cameras by now which leaves the native LOS camera out in the cold as far as testing. It's not easy to stay motivated to test this since I'm using Moto camera with Tasker context sensitive shell command to copy pictures to external SD when closing the Moto camera, but I'm trying to find the time to make a viable bug report for native LOS camera.

- Livedisplay night mode: The correlation between the local-time/GMT-0 difference and the issue seems to be gone, which is a good sign, although there are still inconsistencies during first session after flash and before next reboot, described to some extent in the Jira ticket here:

https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-14934. As indicated there, so far so good but in my usage scenario I'll have to see it work OK for at least 3 consecutive days to be convinced.

- com.android.phone FC when leaving voicemail sound settings https://jira.lineageos.org/browse/BUGBASH-315: [MENTION=2945516]KrisM22[/MENTION], in the Jira ticket for this I've quoted your feedback about how the issue did not occur in your test because the settings combination under which it occurs is not available with your AT&T service and their independent utility. This does seem provider, plan and SIM card specific. Perhaps others using US T-Mobile (monthly and or prepaid) could test it like so:

- Open phone app.

- Settings

- Calls

- Voicemail

- Sound

- Cancel (No FC. Note: Visual Voicemail is still enabled)

- Disable Visual Voicemail

- Sound

- Cancel = FC com.android.phone

---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------

Ha! That sounds about right compared to my favorite high consumption game, Rortos Air Fighters (abaondoned because they went subscription). Those games might as well be called Poke-Battery and Rortos Battery Fighters. LOL now I'm envisioning a game that does nothing but rev the CPU and GPU while we watch colorful animated battery indicators drop. :)
[Moto G 2015 Original Android Development] ajaysingh23:
White Bar On Dialer

Hi, is this just me or anyone else too see this white space/bar on the stock dialer on call log area.
[Moto G 2015 Original Android Development] IronTechmonkey:
Nice catch. Yes, I see it in the "Call history" panel on Osprey (and other devices), and would describe it as an additional thin gray border line creating the semblance of a white bar which behaves like an auto-hiding toolbar. A few more observations:

- When there is nothing in the call history it is static. When panel is swiped up/down nothing in it moves.

- When there are a few items in the call history but not enough to require that the page scroll to see them all; the white band above the thin gray line scrolls with the up/down swipe (eg the thin gray bar moves up/down) but the main part of the panel does not move.

- When there are enough items in the panel to require scrolling to see them all; after the panel is swiped up, then when it is swiped down that space scrolls down regardless of the position of the main panel - much like an auto-hiding toolbar, eg XDA Labs app's individual thread view header, or NakedBrowser's URL bar.

IMO this is worth a proper bug report.. I would suggest creating a Jira ticket for it (https://jira.lineageos.org/) including screenshots and a log taken as you swipe the panel up and down, then sharing the link to the jira ticket here. I would gladly vote for it and add notes and screenshots.
[Moto G 2015 Original Android Development] ajaysingh23:
Created jira ticket, https://jira.lineageos.org/browse/REGRESSION-618

And I have copy pasted your line as the ticket header ;)
[Moto G 2015 Original Android Development] IronTechmonkey:
Groovy, voted and noted. Thanks for creating the ticket.
[Moto G 2015 Original Android Development] Ray Krebs:
I do not know, maybe I messed up with the versions. I only know the mentioned videos ran hardware accelerated on my device.

First there was a nightly as the screen remained black while tipping onto landscape the next nightly worked.

I have just tested these videos with the MX Player 1.8.21, they are played but only with software acceleration!

A testvideo of tears of steel in the resolution 1980x800 24fps HEVC in the mp4 container works. Also with the Lineage integrated player.

Maybe it depends on the mkv container.

Edit: Short question what is: "Yep, you're right 6-1 LinOS rom"
[Moto G 2015 Original Android Development] Subinsmani:
m using google dialer and google contact, so m not come across this prblem .. but i voted, support for bug free... :D
[Moto G 2015 Original Android Development] ajaysingh23:
Thanks. Can you confirm if you see the same behaviour but a transparent one on the contacts panel in Google dialer. Just swipe up you will see. If not do let me know about it.
[Moto G 2015 Original Android Development] Subinsmani:
i think google dialler has bugless..

so m usinng google apps frome day one like dialar, contacts, camera, browser etc exept gallery.. :D
[Moto G 2015 Original Android Development] ajaysingh23:
Not the call log, contacts tab in the Google dialer
[Moto G 2015 Original Android Development] Subinsmani:
ohhh actually there is big difference on google contacts and aosp contacts...

there is no tab..
[Moto G 2015 Original Android Development] ajaysingh23:
Edit: By Contacts tab I meant the 3rd tab on the Google Dialer app, NOT the Google Contacts.

I've seen this issue only in los dialer in call log, Google dialer in contact tab but no issues on any aosp dialer yet.

Which dialer are you using Google or AOSP ??
[Moto G 2015 Original Android Development] Subinsmani:
google dialer..
[Moto G 2015 Original Android Development] ajaysingh23:
By Contacts tab I meant the 3rd tab on the Google Dialer app, NOT the Google Contacts. Check if you can see the same thing as mine screenshot
[Moto G 2015 Original Android Development] KrisM22:
:D

---------- Post added at 10:21 AM ---------- Previous post was at 10:14 AM ----------

I suggest you put a bit more detail in a comment or they will have no idea what you are talking about. Just a thought... I had to look at this quite a bit to realize what you were talking about. :)

Also show a pic of a previous LinOS where it is correct.

---------- Post added at 10:33 AM ---------- Previous post was at 10:21 AM ----------

As [MENTION=3784616]shadowchaos[/MENTION] correctly pointed out, MXPlayer works fine.

My full quote in response to [MENTION=3784616]shadowchaos[/MENTION] "Thanks! Yep, you're right! 6-1 LinOS rom, 1.8.21 MXPlayer." meaning on the June 1 build of the LineageOS ROM, MXPlayer version 1.8.21 (from Google PlayStore) played those just fine.

So for you it would be a "player problem". I went back and edited my edited response to you.
[Moto G 2015 Original Android Development] IronTechmonkey:
Subins Mani(Tintumonn) is using the 3rd party Google Dialer app that is not native to the ROM instead of the native Dialer app in which you found the problem. It doesn't matter what that Google Dialer app is doing so don't worry about it, you've already got a good ticket there.

I've added more detail and will add additional screenshots later. It would help if someone who is still on a previous LOS build could check this out in the native LOS dialer to confirm that it is a regression rather than a bug.

---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------

The support for the ticket on faith is appreciated but things might be clearer if we just did not introduce those third-party factors. :)
[Moto G 2015 Original Android Development] KrisM22:
I'll go do that.

EDIT: I see the same band in 5-25. I am proceeding back to 5-18.

EDIT2: I see the same thing in 5-18: please note 2 pics attached. first one shows small 2mm bar. Then I tapped the 3 dots top right and chose "call history" - second pic. The 2mm bar is now the heading bar for the call list. So the problem is not that the 2mm bar is there, but that it is not expanded to it's full grandeur as shown in the second pic. Functionality is the same.

EDIT3: appearance and functionality is the same on 6-1

EDIT4: pic 3 added is pic1 with arrows referring to place in question.
[Moto G 2015 Original Android Development] ajaysingh23:
Thanks a lot, and will keep that mind for next time. Just saw your comment on jira. :good::good::fingers-crossed:
[Moto G 2015 Original Android Development] KrisM22:
Please note I have edited post 4839 (2 posts back) ref this. Pics added.
[Moto G 2015 Original Android Development] IronTechmonkey:
No worries, but there is something else. To [MENTION=2945516]KrisM22[/MENTION]'s point about providing screen-shot from previous build; Jira may trust us when we say something is a regression even without a screenshot but we have to be accurate and in this case the ticket is mis-filed.

I restored last weeks build and find the problem exists there as well. This means that the issue is a bug rather than a regression so a new ticket will have to be filed in the correct category. Can you create a new ticket as a bug? In the "Project" field at the top of a new ticket select "Weekly/nightly bug reporting...". Yes, that is more work but at least we are still in the weekend "bugbash" window and you already have logs and screen shots. Once you create the new ticket, then put comment in the other one letting LOS Jira know that a new one was created under the proper category with a link to teh new one. I'm sure they will appreciate that rather than having to reject it themselves and ask us to recreate it. After you create the new one, sjare the link were and we can re-add our notes and votes.
[Moto G 2015 Original Android Development] ajaysingh23:
Can you check if this issue was present on the 1st build. I started using stock after last two build only before that I was using google dialer.

---------- Post added at 09:42 PM ---------- Previous post was at 09:40 PM ----------

Sure will do that. :good:
[Moto G 2015 Original Android Development] IronTechmonkey:
(Cross posted and cross tested)

...Or, the dropdown is not intended to show at all in one place and it is intended to show in the other. In any event it is a bug rather than a regression and once a new ticket is created we can backfill all these notes.
[Moto G 2015 Original Android Development] KrisM22:
No, I don't keep those around. Wouldn't really matter to the jira folks if it was, I don't think. They're only looking for a recent change so they can grab it and undo it. Just my opinion, though.

Just refile as bug and pretend it never worked. Please put text description in description, not pics - then add pics as attachments with meaningful labels. Then you're golden! You're welcome to use my pics and comments w/o credit! Let us know number and we'll all add votes.
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes, along these lines, it's about prioritizing on a large scale (much larger than we see in a few device forums). Well, any scale really but more important in bigger operations. Regressions might be up-prioritized for a few reasons:

- Avoid a cascading effect of worsening problems as well as the regression itself.

- Statistically, the old bugs, for the fact that they have not yet been noticed or they have been noticed and intentionally down-prioritized, are less likely to very bad. Of course that is not always the case but on average it is.

- CYA (cover your a$$), perhaps more relevant to business environments, just making sure that there is no backwards progress being noticed in a broad view of the operation.
[Moto G 2015 Original Android Development] Ray Krebs:
May be i am wrong, but i think it is not a player problem, because in the past the videos (HEVC mkv) were played with hardware acceleration [MENTION=7825661]60fps[/MENTION], also with the bulid in Lineage player.

Now, the build in player shows only a black screen.

MX Player works for me, but only with software acceleration (showing SW)! and this ist not very fast.
[Moto G 2015 Original Android Development] KrisM22:
I don't think you have a bug, but if you think you do, then take logs to prove it and file a bug or regression depending on whether you can find an older version of LineageOS official that worked as you want it. I personally doubt that the jira folks will give much priority to playing very HD stuff on this phone especially when MXPlayer works. You cannot file a bug just because some 3rd party app doesn't do what you want. Well, you can, but psychoi3oy will reject it. Just my opinion.
[Moto G 2015 Original Android Development] ajaysingh23:
Rported under bug. https://jira.lineageos.org/browse/BUGBASH-651

Just one question how will I close that regression which I filed earlier
[Moto G 2015 Original Android Development] KrisM22:
Just add a comment to it saying "opened as bug 651, close this one."

voted.
[Moto G 2015 Original Android Development] ajaysingh23:
Posted the bug report, forgot to add your pics and comment.

---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------

Thanks a lot. Done. :good:
[Moto G 2015 Original Android Development] KrisM22:
just add whatever you want as comments and/or attachments. The more you can clarify it the better! :) Look at my bug 444 for BT - I just keep adding comments to it hoping they will understand...

I guess it's a bit like a competition - the more they can understand it the more likely they are to bump it in priority and the sooner they fix it.
[Moto G 2015 Original Android Development] IronTechmonkey:
Your signature among other things makes it apparent that you see it this way but please dont lay that on Jira or the people at Jira who have to filter out the bad reports, or me. For those entities this is about bug reporting and prioritization, not competition.

Thanks for helping get this on track with some good testing following my lazy work that preceded it. I was waiting for you to post the screenshots from your tests but did not see any in the new ticket so I added some, crediting you for the observations about the difference between the Call History as accessed by the main panel and as accessed by the menu.

Thanks [MENTION=6302410]ajaysingh23[/MENTION] for going through the ticket creation drill twice, and apologies for not being more attentive earlier (not checking about regression v. bug). Reasons but no excuse, I probably should not reply to forum posts or jira tickets between sleep and first cup of coffee. :o
[Moto G 2015 Original Android Development] ajaysingh23:
Hahahahaha not an issue, for me it's quite educative about how to report bugs or a regression. By doing this I'm not just gonna help myself but other as well. Custom Rom community gave my device and to myself a second chance to sail the sea of new adventures. :laugh::D
[Moto G 2015 Original Android Development] KrisM22:
I had told him above that he could use that stuff if he wanted. I chose not to walk all over his new report.
[Moto G 2015 Original Android Development] IronTechmonkey:
Nor did I. It's a team sport, not an individual competition ;).
[Moto G 2015 Original Android Development] guest_2011:
6/1 build dropped BT while low wifi signal or out of range. Not only that, but as of 6/1 and the previous build, 5/28 or so, random wifi disconnects. I restart the phone, it seems to connect and work for a while and then disconnects. I'm still connected to wifi except email app, browser, audio/radio streaming, other apps say "no connection to internet" or "check your internet connection". Disabling/enabling wifi doesn't seem to help.
[Moto G 2015 Original Android Development] KrisM22:
Not sure what to say - I just ran wifi for a couple hours and it was fine(I wold test it occasionally with Opera), but I didn't go in/out of range. So sounds like things are different for you last couple of builds, but pinning it down and getting a log sound difficult.

"random wifi disconnects" - sitting next to your router? If you have time, keep playing with it and see if you can come up with a "x causes y" situation... Also airplane on/off might reset it. Thanks for studying it this far - I appreciate the info!
[Moto G 2015 Original Android Development] guest_2011:
i was on 6/1 so definitely noticed something was not right with wifi because the signal is 100% home or outside hotspots. WiFi manager app shows connected, but i couldn't access email, browser, radio app, some other apps. Play store worked for some reason. Was able to download lineage. Another online radio app worked. Other apps would say check internet connection. I restarted and wifi worked for a while. Got tired of it and just updated to 6/2. So far wifi is good. Still need to test BT when low signal or out of wifi range.
[Moto G 2015 Original Android Development] KrisM22:
when you are moving are you switching between wifi and cell, or do you have airplane turned on so only wifi would be used?

Where did you get 6-2? you build it. I am repo sync 'ing at the moment...

I trust the obvious - stock kernel.

Amazing if 6-2 fixed it...
[Moto G 2015 Original Android Development] KrisM22:
https://review.lineageos.org/#/c/168816

for voicemail issue?
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes. Ironically as you were testing with AT&T (thanks again) and I was comparing those notes to T-Mobile a fix was in works. Described with a few different details here: https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-14946.
[Moto G 2015 Original Android Development] Subinsmani:
dnt know bro....

i have connected 6 wifi routers daily and it switched automatically when i move one department to other in my office... there is no any disconntion till now(VNC server is connected always via my phone)... dnt know have u installed rom and see whether this issue is there or not....
[Moto G 2015 Original Android Development] lystrade:
Bluetooth Issue

Clean install of 5-25, gapps, and su. Connected to my car's bluetooth, listening to audio. After I finish an incoming call I can't hang up and the phone reboots on it's own. This happened on earlier versions, but it went away for a while. I haven't tested yet, but I have a couple of different bluetooth devices to check.

Any ideas?
[Moto G 2015 Original Android Development] KrisM22:
search jira, both bugs and regressions - I believe I saw one out there.
[Moto G 2015 Original Android Development] adityak1303:
Deleted
[Moto G 2015 Original Android Development] braddocksp:
Some patch to work miracast? Not working since 7, and now with lineage the same.
[Moto G 2015 Original Android Development] KrisM22:
yeah probably good that you deleted that :) but even if it did happen I would stick with LinOS for the security patches, and, "it just works" - at least for me.
[Moto G 2015 Original Android Development] Mama Luigi:
Sorry but I'm back on CM13 snapshot. Bugs were getting to be too much, combined with worse battery life and I'm done with experimental software. It's also nice having Xposed. CM13 is rock stable, zero bugs at all, and does everything I want.
[Moto G 2015 Original Android Development] KrisM22:
Thanks for your response! I fully understand! Glad you have something that works well for you!!!!! :D
[Moto G 2015 Original Android Development] guest_2011:
not moving anywhere, one place, one router or one hotspot. doesn't matter. wifi doesn't disconnect. only some apps can't connect to internet. some can. restarting the phone helps for a while. updating lineage helps for a while and then suddenly happens randomly. Play store works, can download lineage update, aqua mail doesn't connect. one audio streaming app works, spb tv doesn't. so far restarted only one time around noon today since 6/2 update yesterday. still works. wifi is always on and connected. i'll just keep updating lineage until the problem resolves or will go back to CM. i don't know... very tired.
[Moto G 2015 Original Android Development] KrisM22:
I hear you. Thanks for the info. Problem is no one else that I know of is reporting that and I see nothing in commits so far that addresses that issue. Good that 6-2 works better. Let me know if problem resolves. Sleep!
[Moto G 2015 Original Android Development] guest_2011:
i didn't notice any glitches other than BT/wifi signal strength prior to 5/29?-6/1. then suddenly this. very strange behavior. wifi never disconnects. flawless tomato router at home, xfinity hotspot outside. good connection. some apps, not all, suddenly lose connection. the only thing that changed is lineage. started in the last may update, continues in june.
[Moto G 2015 Original Android Development] IronTechmonkey:
What model Osprey? Is it 1GB model? If so, perhaps apps or services are being killed and loosing connection. If not a 1GB device, then disregard this notion.

I would add that when diagnosing possible issues, knowing such details may be critical and save much time. There are some big differences between models. The model # should be on a sticker on rear of the chassis under the rear cover, or it can be confirmed from bootloader in "Show barcodes".
[Moto G 2015 Original Android Development] kiekeboeboe:
Hello folks,

Already couple of weeks on "lineage-14.1-20170518-nightly-osprey", without any problem.

I'll stay with this ROM. Works perfect for me.

XT1541 16GB/2GB.
[Moto G 2015 Original Android Development] dddufte:
Just in case anyone is experiencing similar problems:

I finally solved my issues by replacing the stock Lineage 7.x kernel with squid kernel (r19).

since changing to this kernel everything works fine for me on my osprey device

Before i had issues (as in soft-reboots and crashing apps) for month with all 7.x builds.
[Moto G 2015 Original Android Development] Sachin ET:
Hours ago i flashed 1-6-17 built, wifi got connected once, after an hour or so it got automatically disconnected and i cant get it connected again........i can see the SSID and when i select "connect" option from the wifi settings it says "Connecting" and after 4 to 5 seconds it shows "Saved".
[Moto G 2015 Original Android Development] KrisM22:
saved means it tried but wasn't able to connect - due to password or other reason. You might try "forgetting" it and then re-connecting to it and type in your pasword again.
[Moto G 2015 Original Android Development] Sachin ET:
yeah i tried it morethan 5 times no use........i found this isue on the previous built too(found it yesterday thats the reason why i thought about shifting to latest built)........tried rebooting router etc........no use........i think I'm the person in this thread with lot of issues :crying:

Thanks
[Moto G 2015 Original Android Development] KrisM22:
Yeah I was next going to blame the router. :) but do check that the power level is set to high in the router settings, if it's a distance thing. I suppose the router could be broken, but doubtful - get someone else to try your router, and go outside to some place that has wifi and test your phone there. Guest-2011 was also having wifi problems but last I heard it was fixed on 6-2 (his own build) and ITM reminds me mentally to ask - is this a 1GB phone perhaps?