yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
32-02-2017? Assuming the build you are referring to is March 23 2017 Osprey: I'm configuring it now but AFAIK there were no real media scanning problems in the previous build, just that people were not giving the device a few minutes and an additional reboot after first flash (as has been recommended for years). I've already passed that step and media scanning seems fine (64 GB ext SD, 65% full, including about 20GB video and MP3s).

It is also possible that the various apps have not yet caught up with Nougat, in which case this is not a ROM issue. The best way to know for sure is to produce a vaiable bug report, which we dont have yet for this issue. If I'm missing something , then would you please share a link back to a valid report about the media scanning issue, so I can test it.

Of course, considering that each usage case is different (and that this is a development forum rather than a review board - how many times does this need to be said?) You should test it then if you find problems submit a bug report.
[Moto G 2015 Original Android Development] tazlooney89:
I present the same problem with scan media, in the most recent build 03/23, I performed some tests with another Moto G3 dual SIM 16GB version, without using microsd, build 03/27 without installing the gapps, and also presents problems with the scan media, I doubt that the "problem" is of the users, and there is something in the ROM that causes this bug.
[Moto G 2015 Original Android Development] GoelPlz:
Clean flashed the new build and I can assure the media scan issue is still there. And yes, this is a bug from the ROM cause I'm currently on AICP and there's no such issue (And I find that weird because AICP is based on Lineage)
[Moto G 2015 Original Android Development] wbsx:
Does Panorama work for you guys? When I try to do a panorama pic the camara crashes everytime.
[Moto G 2015 Original Android Development] IronTechmonkey:
If that is the case then someone who is witnessing it needs to submit a actual bug report which establishes this as a ROM problem, As yet no reports (including yours) have provided technical or behavioral evidence that this is a ROM problem. I'm not saying it cannot be a ROM problem but this has not been demonstrated. Opinions not backed by technical information are not bug reports (even if those opinions may later turn out to be correct).

A bug report would include the following:

- Tested in clean flash, no hacks or mods of any kind, no superSU, no custom kernels (nothing but ROM, GAPPS, LOS SU package)

- Device description including:: Model #, type/format of SD or storage, list of actual files flashed.

- Description of the exact steps a person would take in order to reproduce and test the issue.

- A logcat captured while the issue was reproduces ass described in previous step.

Expanding a standard bug report to include your tests yields the following additional questions:

- What were your tests? Describe them so others can reproduce them.

- What were the symptoms that indicated a problem other than first post-flash scan, and how are those symptoms different from what you consider normal?

- Are there other differences beside the scanning behavior between the your tests of the normal usage case and this one?

- Do you experience this after waiting 5-10 minutes after flash then rebooting?

BTW, [MENTION=4335062]tazlooney89[/MENTION], No one said the problem "is of the users" (meaning caused by the users) just that it hasn't been demonstrated and proven effectively.

It may be an ACTUAL bug but without an ACTUAL bug report it may be difficult to pin down especially because it seems to be situation specific. Someone who is experience this needs to submit a useful bug report to determine range and cause of problem. I would do so myself but am not experiencing the problem. I've not seen it in several flashes and I'm actually doing my second flash of the March 23 build right now for another test.

---------- Post added at 05:15 PM ---------- Previous post was at 04:45 PM ----------

Yep. I'm not seeing an FC message but Camera app closes part of the way through while taking panorama picture. Also, before camera closes the on screen movement stutters more than it should and it seems as if the sensors are not properly reading the rotation of the camera as it is turned to take the picture. Problem is also occurring in Peregrine, and may not be occurring in other cameras (still testing).
[Moto G 2015 Original Android Development] wbsx:
I tried Google Camera, but I couldn't find panorama. Then I installed Moto Camera. Panorama does work with Moto Cam. So I guess that works for me. I don't get why CM/Linage OS Camera Panorma doesn't work... but ok, as long as I can take panoramas...
[Moto G 2015 Original Android Development] KrisM22:
I did a 180 panorama and had no prob. 3-23, camera built in to LinOS. nano gapps.
[Moto G 2015 Original Android Development] IronTechmonkey:
I've reproduced this in 2 clean flashes of Osprey (1 straight up clean and another clean with installed apps) and 1 clean flash of Peregrine, with the save location being an External SD card (different size and type in each device) and internal SD.

Also, after the FC occurs, the overlay indicating that a panoramic picture is in progress (and if it is moving to fast) no longer appears in subsequent attempts to take pano pic until after phone reboots. The reboot does not fix the actual issue, just restores the overlay.

In any event, this one is easy to reproduce and here so I'll try to do that and log it in time for the LOS jira bugbash this weekend.

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

Thinking of possible factors that could explain the difference in your case (which I would try to reproduce).

- Some combinations of otherwise normal settings and states of the device?

- Gapps package? (really unlikely but I'm using Open Gapps Pico March 23).

As you were rotating the camera for the picture did the scan jump forward in pronounced hops or was the motion relatively smooth?

---------- Post added at 07:12 PM ---------- Previous post was at 07:02 PM ----------

That is consistent with what I've seen, including the good pano pic result in the manually installed Moto Camera (I used Moto camera 5.1.13.12 for this test). BTW Don't be surprised to see bugs. This is a new variant (LOS) of a new Android version (7.x) in a state of early and continuous development. It would be more surprising if there were no bugs (and the purpose here is to test bugs). To your point, at least we have a workaround... which allows us to continue using this build to test for even more bugs.
[Moto G 2015 Original Android Development] KrisM22:
a) if you have a reproducible bug, go for it and post the bug number so we can vote on it.

b) definitely try nano. I mean it.

c) smooth. I had never done one before so didn't know what to expect. When it finished the progress bar overlay appeared and might have taken 15-30 secs. saved correctly to stock gallery where I was able to view it.

d) I'm sure there are tons of bugs in it as AZ_Biker suggested(I think) but I do relatively little on mine so wouldn't tend to find them, so it's great when folks find stuff - if only they would also file bugs...
[Moto G 2015 Original Android Development] IronTechmonkey:
Will do. AFAIK you are the only exception as yet so there should be other people who could log this or at least confirm so I'll wait a bit. Also, the method of reporting it (regression=any day or bugbash=weekends only) will depend on whether any of the people who now experience it can confirm that they did not on previous build. I'm also curious about the ratio of people who experience it to those who dont, as that will inform the bug report and maybe even determine a workaround.

Thanks. That sounds normal. The stutter would have been quite noticeable (still frames once or twice a second) and the calibration of the rotation would have been similarly off.

Good points.
[Moto G 2015 Original Android Development] KrisM22:
b may fix the prob. I saw one a few pages back where that happened.
[Moto G 2015 Original Android Development] IronTechmonkey:
I have my doubts because pico is leaner than nano but it is certainly worth trying any different package. You just so happened to have caught me about to test in a super clean ROM only w/no gapps flash so I'll add a pass with nano depending on what that turns up.

[EDIT] Reproduced in ROM only clean flash, and with Open gapps nano. Will have to see what other reports roll in.
[Moto G 2015 Original Android Development] KrisM22:
pico is too lean.

---------- Post added at 09:28 PM ---------- Previous post was at 09:17 PM ----------

it was 3482ff - Trusted Face didn't work/appear under pico, worked under nano.
[Moto G 2015 Original Android Development] IronTechmonkey:
... for some people. I'd go leaner if I could.

3482ff? color code?. Good to know in general but I dont use trusted face, hence pico. To each their own, and not likely to be a factor in the camera issue.

Apart from that I've found no issues in Osprey other than a few that have been previously mentioned, though not testing Mobile data or BT yet.
[Moto G 2015 Original Android Development] KrisM22:
post #3482 and following for that issue.
[Moto G 2015 Original Android Development] RijuSarkar:
How to disable the portrait icon on the status bar...I am on newest build..23.3.2017
[Moto G 2015 Original Android Development] IronTechmonkey:
Normally disabled by default. Can be changed in Settings - Status bar - System icons.
[Moto G 2015 Original Android Development] RijuSarkar:
No..In the latest build it is enabled by default...No system icon to disable this..
[Moto G 2015 Original Android Development] IronTechmonkey:
Ahhhh. I missed that. Tx. Still, were you able to disable it?
[Moto G 2015 Original Android Development] RijuSarkar:
When I make this in autorotate mode

...This icon gone
[Moto G 2015 Original Android Development] IronTechmonkey:
Did you try the setting I suggested?

[EDIT] OK, I think we are talking about different things. Are you by any chance referring to the top row of mini-quick tiles (which is different from status bar)?

If so then those icons are just the first six quick tiles and you can arrange them as you wish. The actual status bar (the thin one at the top) icon is controlled as I described before and is indeed disable by default.
[Moto G 2015 Original Android Development] KrisM22:
custom kernel? nite.
[Moto G 2015 Original Android Development] IronTechmonkey:
In addition to the aforementioned panoramic picture FC, even when just taking a regular picture or viewing them from the gallery button in the camera app causes parts of the UI to crash (status bar icons lost and services terminated). Sometimes the camera does not respond to the back button. This symptom is occurring on Osprey but not Peregrine (both on March 23 build).

If it's a ROM bug it may be device specific and boot scan specific. I just tested one Osprey device and one Peregrine device (both running the March 23 build), with 32GB and 64GB SD cards each full of mp3s and videos. I monitored processor usage through a few dozen boot scans and the scans that occur when SD cards are swapped:

- The scans that occur when SD cards are swapped or when I force the media scan (using MiXplorer) seem normal, putting about 40-50% load on processor cores 1 and 2 and no load on cores 3 and 4 for the duration of the scan. This is the same as I've seen in previous ROMs including CM12.1 on both of these devices.

- The start up scan on the Peregrine device shows the same type of processor usage described above but on Osprey the start up scan pegs one processor after the other at 100% in turns for the duration of the scan and the scan takers much longer.

I was unable to reproduce the one or 2 other symptoms reported about this nor could I find any references to media scanning issues at jira. This is definitely worth filing a proper bug report. I noticed that almost every previous post about this issue merely asks if it has been fixed or states it is broken. Perhaps one of those posters could submit a bug report for it. Then it would stand a better chance of being fixed.
[Moto G 2015 Original Android Development] MrMosoani:
Some Issues Found

Gaming

Problem connecting with Google Play

and can't play the Mario Run new game, it just won't start

can't sometimes take a screenshot during the game (error saying android system...)

-sometimes happens sometimes not

USB configuration is fixed to Charging, therefore I can't transfer the latest lineage nightly file from PC to the phone sd card- reboot didn't fix it

Sometimes Wifi is not available even after you hit forget network then entering the password again. Reboot fixed it
[Moto G 2015 Original Android Development] dvdgva:
If you have root I read that it could be the problem, same as Pokémon Go
[Moto G 2015 Original Android Development] MrMosoani:
what's interesting is, by default LineageOS when installed to your device, it's unrooted. You have to flash the addonsu zip to root the lineageOS. I flashed lineageOS but didn't flash the addonsu.

I love the lineageOS but hopefully gaming for all type of games would work in the future as this is also part of the basic functionality of all phones.

Installing the latest nightly and fingers crossed game hopefully would work this time and connection to google play
[Moto G 2015 Original Android Development] dvdgva:
I'm actually using latest nightly, I can't even open it in the play store. Maybe all custom ROMs are sort of "locked"
[Moto G 2015 Original Android Development] Subinsmani:
I have also didn't root my phone but it break seaftynet...

Cant open sbi pay app becuase it show ur device has been modified or rooted.....
[Moto G 2015 Original Android Development] IronTechmonkey:
Assuming clean flash and no mods:

Various Open gapps packages are working fine. No reason to think these are issues with ROM. If they are ROM related then they would be captured in a log.

Nothing to fix. It's been this way since Marshmallow. Had you bothered to do the smallest bit of research (an expectation here) you'd have been able to copy your file just fine. http://www.androidcentral.com/inside-marshmallow-usb-connection-options

[EDIT] [MENTION=7868666]Subins Mani(Tintumonn)[/MENTION] , [MENTION=5180670]dvdgva[/MENTION] and [MENTION=4307806]MrMosoani[/MENTION]; It may be the case that even without the SU package the ROM may appear rooted for some things. There was actually a time when root was more separate from SU (CM11 where there was in fact no native SU) and this could be a legacy of that. In any event it does not sound like ROM issue.
[Moto G 2015 Original Android Development] KrisM22:
This depends on the twrp you are using. I am using twrp from twrp (twrp-3.1.0-1-osprey.img) and when I flash I get a rooted rom without having to flash the root module.

twrp from squid gives you an unrooted rom. EDIT: you still have to turn it on in Developer Options.

---------- Post added at 09:56 AM ---------- Previous post was at 09:46 AM ----------

what level of gapps are you using. Try one level higher.

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

read the above.(1st one)(if you want unrooted, grab squid's twrp and flash it.)
[Moto G 2015 Original Android Development] Subinsmani:
Aroma :)....
[Moto G 2015 Original Android Development] KrisM22:
Okay, forget I said anything! :) (I was imagining pico! LOL)
[Moto G 2015 Original Android Development] WaxysDargle:
some of these issues are coming from the latest updates in google apps. i found that gapps was causing issues with substratum on some roms, and FCing on others. reverting to earlier versions might help
[Moto G 2015 Original Android Development] KrisM22:
An excellent reason to always keep a few previous versions of gapps around!
[Moto G 2015 Original Android Development] GoelPlz:
So I clean flashed again to see if I could make a bug report, but now media scan seems to be fine. No need to reboot to see downloaded images in gallery, neither from Facebook or Chrome or WhatsApp
[Moto G 2015 Original Android Development] KrisM22:
Thanks for reporting!
[Moto G 2015 Original Android Development] IronTechmonkey:
How quickly it can be forgotten (but not by you two) that and older gapps package can save the day. Thanks for the reminder.
[Moto G 2015 Original Android Development] SayantanRC:
Auto updates in Play Store needs to be turned off.
[Moto G 2015 Original Android Development] KrisM22:
That would be a personal preference thing. I leave it set to wifi only.
[Moto G 2015 Original Android Development] IronTechmonkey:
AFAIK That setting will not stop the google services or PlayStore app from being updated. Also, I was referring to the fact that using an older gapps package may also help even if you allow the Google services to update later. That being said, with very few clearly described exceptions I usually use the newest gapps package.
[Moto G 2015 Original Android Development] KrisM22:
you would have to be in root, with a special app that allows freezing system apps, and freeze/disable Google Play Services before it has a chance to update. This would be done on flash when you're using wifi, but you'd have to be very quick. I've done it years ago.

BUT this is very OT since there is no such gapps problem.
[Moto G 2015 Original Android Development] IronTechmonkey:
A question for you [MENTION=7751407]GoelPlz[/MENTION]. Are you referring to a media scan manually invoked after OS is running or the boot media scan?

I've seen differences between those 2 different scans on Osprey that I dont see on other devices. The boot scan for Osprey shows very jumpy processor core management compared to the others, described in more detail here: https://xdaforums.com/showpost.php?p=71564819&postcount=3638.

If you are not seeing that jumpy processor usage on boot scan then this issue is even more mystifying. Also it sure would help to be able to dynamically monitor individual app and service processor consumption but I've found no practical way to do so.
[Moto G 2015 Original Android Development] RijuSarkar:
Any ideas how to turn off the device is hd capable message under quick settings..
[Moto G 2015 Original Android Development] IronTechmonkey:
Can you post a screenshot of this message?
[Moto G 2015 Original Android Development] IronTechmonkey:
I've never seen that. Is that a part of the ROM or part of some app?
[Moto G 2015 Original Android Development] RijuSarkar:
Previously I had a problem with portrait icon on the status bar...It was beacause I have replaced systemui.apk...(tintumonn made this) ..To get pixel navbar animation...Now I ve replaced it with the old one with no navbar animation...Now the portrait icon is gone from.status bar
[Moto G 2015 Original Android Development] KrisM22:
http://www.gthisgthat.com/android/jio-remove-device-hd-capable-notification-android/

will tell you about it but you probably don't want to do it.

What have you added to give you voLTE?
[Moto G 2015 Original Android Development] RijuSarkar:
My carrier supports on Volte...thus every rom shows this message that device is hd capable..
[Moto G 2015 Original Android Development] IronTechmonkey:
ROTFL. I found that exact same link. It was first result i.when searching "device is hd capable".
[Moto G 2015 Original Android Development] RijuSarkar:
This is a bad solution...from lockscreen it is very easy to remove that message..

I have even got a flashable "notification remover "zip which erases this message under the quick settings panel.

That zip works perfectly with all other custom ROM..But not with lineage os...If I flash it the message is gone along with Volte feature...
[Moto G 2015 Original Android Development] KrisM22:
yeah, I see a lot of people complaining about it but no (good) solution.

How about disable volte and use Skype.
[Moto G 2015 Original Android Development] IronTechmonkey:
If you think this is an actual ROM issue (as it very well may may be) then please file a bug report at jira. They'll ask you for logs even though it is a visual thing to us, but those official bug reports and logs really do push these things along and leverage the strength of the whole Lineage bug tracking system instead of just putting it on our device maintainer through this thread. Lineage Jira bug reporting is here https://jira.lineageos.org/secure/Dashboard.jspa, and they are taking non-regression reports like this right now (in what they call bugbash which is a weekend only thing).
[Moto G 2015 Original Android Development] RijuSarkar:
Also I found the incall volume is too low in all lineage based ROMs...Any fix?

---------- Post added at 03:21 AM ---------- Previous post was at 03:19 AM ----------

In India..Here internet speed is not that fast..
[Moto G 2015 Original Android Development] KrisM22:
Is that using the phone's ear speaker, or BT?
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes, submit a proper bug report as described above. Did you not read the previous post or are you being sarcastic (rhetorical!). Now you know what is required if this is an actual ROM issue. In any event there is no benefit to repeatedly stating it is broken without providing any of the requisite information that would help fix it.
[Moto G 2015 Original Android Development] RijuSarkar:
Read it...and clicked the link k..but it is saying to login..

---------- Post added at 03:31 AM ---------- Previous post was at 03:30 AM ----------

Ear speaker
[Moto G 2015 Original Android Development] KrisM22:
a) you have to register before you can log in - it's simple.

b) check settings / sound / media volume.
[Moto G 2015 Original Android Development] RijuSarkar:
Ha ha ha...All full
[Moto G 2015 Original Android Development] KrisM22:
?? all full ?? what does that mean? "Not a member? Sign up for an account. "
[Moto G 2015 Original Android Development] IronTechmonkey:
So create an account and log in. That's how it works, and that wont be the only bit of process along the way. At jira they dont indulge reports without complete information or logs, but the process will guide you. If you create a report you can share a link to it so other with the same problem can vote on it and add details.

[EDIT] [MENTION=2945516]KrisM22[/MENTION], since you were enthusiastic enough to answer that it was a matter of creating an account, in spite of the fact that it was obvious that someone else would have been responding at that moment, I assume that you already have a Lineage jira account. :)
[Moto G 2015 Original Android Development] RijuSarkar:
Aren't...The sound is in its extreme level

---------- Post added at 03:39 AM ---------- Previous post was at 03:38 AM ----------

Ok..Thanks...
[Moto G 2015 Original Android Development] KrisM22:
a) click on "Not a member? Sign up for an account. "

b) ok, no ideas on vol - you're the first to mention it.
[Moto G 2015 Original Android Development] IronTechmonkey:
Panorama picture camera FC

FYI Panorama picture camera FC issue has been reported to jira from Peregrine device but occurs in Osprey as well so if you can reproduce it please feel free to vote on this ticket and add a note stating that you've seen it on Osprey (easier than creating new ticket for Osprey). https://jira.lineageos.org/browse/BUGBASH-326.
[Moto G 2015 Original Android Development] Subinsmani:
Done one vote from me. :)
[Moto G 2015 Original Android Development] abhi8939:
Long press home button is not working i.e., not able to open to now on tap or search assistant by long press home button

how can i enable it.

gapp intalled Open Gapp pico.... I think bcz of gapp im not able to ????????

Guide me Guyzz how can i enable the now on tap or search assistant on the latest build:rolleyes::rolleyes::rolleyes::rolleyes::rolleyes::rolleyes:
[Moto G 2015 Original Android Development] RijuSarkar:
Yup..Chng the gapp..Use nano or micro..

Pico lacks ok Google hotword enrollment..

Check this out..Package comparison of all gapps....

https://github.com/opengapps/opengapps/wiki/Package-Comparison

Hope this helps..