yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] guest_2011:
yes it works. i'm able to move video to pc.
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI the symptoms you described somewhat resemble impending failure/bad spots on SD card. If you have reproduced this problem on a different SD card then this is moot, however if you have not tested on another SD card that might be worth doing if this happens again, and I would suggest an empty freshly formatted SD card being used as external storage (not adoptable/internal).
[Moto G 2015 Original Android Development] guest_2011:
interesting. is there an app to test sd cards? i don't think i've ever cards anything on pc or in android.
[Moto G 2015 Original Android Development] KrisM22:
What did you change to get it to work?
[Moto G 2015 Original Android Development] guest_2011:
nothing. didn't enable [use storage access]. i had it enabled before.
[Moto G 2015 Original Android Development] KrisM22:
something must have changed, yes?
[Moto G 2015 Original Android Development] guest_2011:
uninstalled reinstalled again. no changes other than storage access disabled and i had it enabled before. i save to sd. first thing i do after installing is select storage folder. i've noticed with other such apps that can write to external storage they don't play well with N. what used to write maps or any media to external in MM without going through storage selection screen now some apps don't write to external anymore even when the option is there, but sd folder is greyed out. i think it started as of CM14, now lineage, and possibly stock N. i'll still test my card for errors in pc just in case.
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm sure there are diagnostic apps which do that and there is the native Windows PC utility command line "chkdsk <driveletter> /f /r", although that one would be slow and ironically could just put more of a read/write hurt on the drive, and might not find any problems. Also, the fact that you were able to reformat might preclude the benefits of a scan. SD cards can get wonky in ways that wont appear in such scans - for instance the 64GB SD that I'm presently using had issues when I let my TitaniumBackup directory grow large (5GB), until I cleaned it up, after which performance of the drive was better overall. IDK if the removal of a corrupted file or the removal of data from part of the drive that is about to fail was the fix but suspect one of those 2 things.

If it were a desktop/laptop hard drive I'd say go with the scans but just testing on another SD (if you have access to one) might be the best way to go for a thing like this.

I should also disclaim that I'm not suggesting this counter to KrisM22's advice but I am suggesting that you do a "control test" to remove bad SD card as a possibility (or perhaps flag it as a likelihood).
[Moto G 2015 Original Android Development] KrisM22:
why not just swap in a new one (not sandisk)
[Moto G 2015 Original Android Development] Andresmoraj:
Well I can see latest builds of Lineage are consuming more RAM (I got 2GB model) with an average of 1.2 of 1.9GB of RAM; in previous builds was 0.9GB like stock rom
[Moto G 2015 Original Android Development] KrisM22:
I am 0.97 of 1.9GB

EDIT does seem to be a couple hundred MB bigger than stock.(790MB)
[Moto G 2015 Original Android Development] smiffyma:
1GB osprey

I have an old 1GB xt1541.

Would moving to LineageOS 14.1 be a bad move from a performance perspective? Is it still beta?

I've just updated it to the last CM13 and thatruns ok, should I stop there (from a preformance & stability perspective)

I know memory stats can be misleading but on CM13 it typically runs with less than 150MB free memory (3hr avg)... (instant free about 230MB and swap is 200MB+ used out of 500MB).

thanks
[Moto G 2015 Original Android Development] guest_2011:
i don't have any other 64gb card.

---------- Post added at 09:13 AM ---------- Previous post was at 09:03 AM ----------

i think checkdisk is integrated in windows drive tools. i don't know if i should run it. only for hdd in the past. my 64gb card is samsung evo+, one of the more reliable brands. a little over a year. sometimes reaches 40+gb no problems in the past. don't have anything else to swap it with.
[Moto G 2015 Original Android Development] IronTechmonkey:
Although using a different 64GB card could flush out issues related to SD in general or issues specifically related to 64GB cards, a test with ad SD card of any size less than 64GB might still help establish whether or not the former (SD in general) is a problem.Of course.. if you have an SD that you can reformat for the test.
[Moto G 2015 Original Android Development] guest_2011:
I'll clone the card to a smaller size card and use it next time i update lineage. will see how it goes.
[Moto G 2015 Original Android Development] KrisM22:
Taking that word literally, If you are updating, remember that you are dirty flashing, not clean flashing.
[Moto G 2015 Original Android Development] IronTechmonkey:
That would somewhat defeat the purpose of the test I suggested. I'm not trying to force the test but I am trying to make it clear so...Not cloned, as that could transfer problems related to possibly corrupt files.or overall volume of data. The whole point of the test is to remove those factors by testing a freshly formatted (FAT32) SD card being used as external storage with only enough data on it for you to conform whether the issue is with all SD cards.
[Moto G 2015 Original Android Development] Sachin ET:
OFF TOPIC

Can anyone get me the old Gallery app........?

Thanks
[Moto G 2015 Original Android Development] guest_2011:
i know. exactly what i want to do.
[Moto G 2015 Original Android Development] KrisM22:
I saw this before but didn't know where to get it from. Any ideas?

I went back to 3-9 and grabbed one but it's 1.1.40030 which is the same as what I have now on 4-20
[Moto G 2015 Original Android Development] KrisM22:
http://www.apkmonk.com/app/com.motorola.MotGallery2/

---------- Post added at 04:21 PM ---------- Previous post was at 04:01 PM ----------

I also have gallery from stock v530032 23MB
[Moto G 2015 Original Android Development] KrisM22:
Interestingly when I did some more stuff on this rom it went down to 889MB of 1.9GB. Who knows!
[Moto G 2015 Original Android Development] Komapatient:
Thanks for the information.

After my struggle with 20170413 and going one build back I dirty flashed 20170420. The bug is still present but at least the workaround works again.
[Moto G 2015 Original Android Development] BrokenBee:
I just moved from OPX to here. Is LOS stable for osprey? Any major bugs? Thanks!
[Moto G 2015 Original Android Development] KrisM22:
which model/country/carrier?

Have you read back a few weeks on this thread?
[Moto G 2015 Original Android Development] BrokenBee:
Indian model XT1550 i think.

There are way too many pages to make sense. Thats why I asked. Thanks!
[Moto G 2015 Original Android Development] ApocalypsjeNL:
When I get a call I don't get a popup that says I get a call. Only get a message about I missed a call. Also I noticed that when I'm calling someone I don't get a popup where I can enter numbers or see who I'm calling with.

Using Pixel dealer from google and latest build

Is there a fix for this?
[Moto G 2015 Original Android Development] Subinsmani:
reboot the device...

if not fixed then clear catch and delwik catch it will fix...
[Moto G 2015 Original Android Development] KrisM22:
dual sim? see post #4265 Thanks [MENTION=7868666]Subins Mani(Tintumonn)[/MENTION]
[Moto G 2015 Original Android Development] :
Little bug with notification panel

When I drop down the notification panel sometimes I get this little glitch: http://i.imgur.com/mv7KBEm.png; up in the screen appears the "lockscreen version" status bar (which is not the full fledged status bar, you know what I mean).

I don't know exactly what triggers this, I've tried many things but so far it looks 100% random.

PS: I'm running March-30 nightly on XT1541, 8GB/1GB

PPS: does anybody know if Alberto still reads this thread? is there a more appropriate place to post little bugs like this?
[Moto G 2015 Original Android Development] KrisM22:
a) I believe [MENTION=4480917]Alberto97[/MENTION] (wave) reads this thread but never (afaik) replies here.

b) for Osprey curiosities use the Q&A thread.

For Osprey bugs, talk them out in THIS thread before opening a bug or regression at jira :

https://jira.lineageos.org/login.jsp register, and log in -

For things that used to work, Monday-Friday open regression.

For new things or don't know if it ever worked, Saturday-Sunday open bug.

c) I see a white bar at the top of the screenshot of your desktop. I do not see lockscreen version - you may have to use camera to capture that.

d) are you using a theming engine - if so delete that and see if problem persists.

sorry for all the edits:

e) what launcher are you using - it might be an artifact of that.

f) always assure that you have a new clean flash with no mods/enhancements other than gapps and root before reporting a bug. Thanks.
[Moto G 2015 Original Android Development] :
The white bar is the notification panel, that's normal. The issue is that while I'm dragging that thing down, I have the lock-screen status bar (which you can see right underneath the white bar; it is different than the normal status bar because of the increased margin from the top, and because there's the carrier name displayed instead of the notifications' icons) appearing just under it. It's not the normal behavior, it just occurs sometimes.
[Moto G 2015 Original Android Development] KrisM22:
I edited the above post, please read...

Sorry, I am seeing a desktop statusbar under the white bar, not a lockscreen statusbar. What am I missing?

What launcher and theme engine are you using?
[Moto G 2015 Original Android Development] Subinsmani:
are u using any overlay theme or any launcher??
[Moto G 2015 Original Android Development] :
Have a glance at this http://imgur.com/a/S1B9k. Sometimes, when I drag/drop down the notification panel, I have that 2nd thing appearing UNDERNEATH the panel. I don't know how to be more clear than this....

---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------

Nova Launcher 5.1-beta6
[Moto G 2015 Original Android Development] KrisM22:
What theme are you using. delete it please for test.

please remove the beta launcher for test.
[Moto G 2015 Original Android Development] IronTechmonkey:
I cant speak for Alberto97 but it is not common for developers to respond directly to reports in CM/LOS ROM threads like this. IMO this is because few of the reports are actually from a clean flashed ROM without 3rd party hacks or modifications, and fewer include the logs that would be required to determine the cause of a problem. We (universally in this thread and others) would get better responses if we stayed on topic and provided complete bug reports from clean flashes without 3rd party factors.
[Moto G 2015 Original Android Development] KrisM22:
Just so you know, I appreciate your presence here. I feel it takes many minds!
[Moto G 2015 Original Android Development] IronTechmonkey:
Getting back to bug testing clean LOS14.1; Coincidentally, at the very moment I read this post I was doing a comparative test of Osprey XT1540 and Peregrine XT1045 (both 1GB devices) with identical set of installed apps and configuration (as much as is possible), and under the same load of user activity (Naked Browser and XDA Labs Apps); during which Osprey almost immediately maxed out memory and killed apps on a large scale (some irrecoverably so), while Peregrine never had less than 75MB-100MB available through the same test and the few apps/services that were killed bounced back. Even though 2GB devices may not max out memory and therefor not kill apps as much, those RAM usage spikes may inform a larger issue.

The more I dig into the hardware specifications for both Osprey and Peregrine 1GB devices the more baffling this is. Apart from a larger screen size of Osprey (but same resolution and even lower DPI) I cant find any obvious cause for the resource diversion in Osprey so, as mentioned in this report (https://xdaforums.com/showpost.php?p=72014331&postcount=4314) I've been collecting logs immediately after flashing, before installing apps, in an attempt to form this into cogent bug or performance issue report.
[Moto G 2015 Original Android Development] KrisM22:
I think the problem is simply one of what it is saying vs what IS. It gives an "average" which is abnormally high right after flash and initial install/setup. As you use it, it goes down. So that number Memory average, is basically useless. You need, always, what IS, at the moment.
[Moto G 2015 Original Android Development] IronTechmonkey:
https://xdaforums.com/showpost.php?p=71918616&postcount=4176 !
[Moto G 2015 Original Android Development] KrisM22:
so apply that.
[Moto G 2015 Original Android Development] IronTechmonkey:
Although the averages are not good indications of memory available at the moment, please dont assume that I'm using averages, especially considering previously linked post. I reported memory in use and meant just that. Also, even if you are reporting averages, in that case a RAM spike may be even more significant. The problem with the averages is that they would tend not to catch spikes, which means that when a spike is detected in a 3 hour average it might be more significant.

I would be interested in learning what others running 1GB Opsrey devices who also may have experienced this see in logs.
[Moto G 2015 Original Android Development] KrisM22:
Seems to me that what you need is a 3rd party app that will show you memory/RAM use over time - Then you can run your tests and make sense of them. As comparing 2 phones. OK, I'm gone.
[Moto G 2015 Original Android Development] IronTechmonkey:
I do monitor storage (and have plenty to spare - over 2GB after clean flash and over 1.75GB with apps installed) but as previously and repeatedly described, this is not a storage issue (and you stand to misinform people by stating it as such). It's a RAM and performance issue.

[EDIT] To clarify the RAM monitoring that was done: Ironically one of the byproducts of this issue is that both of the apps I would use for monitoring RAM usage also get killed as part of the memory saturation (or whatever it is) when I use their background monitoring features, so I pop in and out of the active app's graphs and grab screenshots to gauge RAM usage throughout the test. It was in that most recent side by side test that I first caught Osprey maxing memory and Peregrine not doing so in the graphs. Looking for cleaner ways to test.
[Moto G 2015 Original Android Development] KrisM22:
I used wrong word - changed.
[Moto G 2015 Original Android Development] Subinsmani:
K its looks wired,

Do backup ur data and rom, and clean flash ur rom, then dont install any gapps, theme, mod and any type of custom kernal. then check ur problem persist?

This is the best troubleshoot to know whether this problem is from rom or not. :)
[Moto G 2015 Original Android Development] IronTechmonkey:
That question would be best asked in the thread you linked to, or a thread for the "older synaptics firmware" mentioned in the linked post, or perhaps the Osprey TWRP thread, or a thread for Marshmallow stock.

To you points: That was CM13. You are on Marshmallow Stock. This is LOS 14.1/Nougat... and the LOS 14.1 Weekly Osprey build has just been released.
[Moto G 2015 Original Android Development] KrisM22:
you saved me the trouble.
[Moto G 2015 Original Android Development] tobymacfreak:
Does anyone know how to remove the Auto Brightness button from the latest update? (See photo attached)
[Moto G 2015 Original Android Development] WaxysDargle:
i think this is related to wifi. i noticed when i have wifi on for an extended period of time the cell/data radio wont come back on properly without rebooting
[Moto G 2015 Original Android Development] dazeone:
Having that issue here. Usually airplane mode would fix it, but not anymore. Need to reboot.
[Moto G 2015 Original Android Development] Marília de Oliveira:
I will install the application by play store. in relation to the xposed already have some that run on cm 14.
[Moto G 2015 Original Android Development] nsekar560808:
Hello!! Can I dirty flash this? CM13 nightly latest.
[Moto G 2015 Original Android Development] sagar27691:
No... Clean flash only
[Moto G 2015 Original Android Development] batboy29011:
Is bluetooth working. like bluetooth streaming to headphones, speaker etc ? or is it still not working.
[Moto G 2015 Original Android Development] dazeone:
Working. I use it for Bluetooth speakers
[Moto G 2015 Original Android Development] eemgee:
Anyone else having disappearing shortcuts on Google now launcher?
[Moto G 2015 Original Android Development] dazeone:
Shortcuts or icons.
[Moto G 2015 Original Android Development] eemgee:
Sorry, icons (some of them) i think I've worked it out by deleting the cm launcher. I've rebooted a few times and they seem to be staying now.
[Moto G 2015 Original Android Development] dazeone:
I had to move those apps that icons were on home screen to internal storage instead of external. I'll try removing cm launcher though to see if it'll fix it for me.
[Moto G 2015 Original Android Development] Pacer_456:
[MENTION=4480917]Alberto97[/MENTION] Could you please share how you got bluetooth working? Building AICP based on cm14 and I have no idea on how to get it to work. Thanks, and thank you for porting Nougat!
[Moto G 2015 Original Android Development] :
Is this build support VoLTE Feature,,,,
[Moto G 2015 Original Android Development] hareshsangar:
There are too many posts in this thread saying that this ROM don't support volte:silly:
[Moto G 2015 Original Android Development] :
meanse relaince jio not suppprt this rom??
[Moto G 2015 Original Android Development] Gravemind2015:
Data only. Forget voice calls :)

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] banerjeeayan1996:
Ok so I have this qiestion is there any way we can use jio join app rather than our stock dialer in custom roms. I mean nonvolte phones use this method. So there should be something that we can do so that jiojoin treat us as a nonvolte device
[Moto G 2015 Original Android Development] Gravemind2015:
Have you tried it? I don't have the sim so unfortunately I can't test.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] banerjeeayan1996:
Well ya when u call from jio join app it just redirects u to stock dialer . Sincce volte not implemented u can hear anything . This means jiojoin app is still treating our device as volte one. Anyway to remove it
[Moto G 2015 Original Android Development] Gravemind2015:
Maybe its broken on both sides then, this explains why call at least go thorugh the device although with no sound. I don't have any idea how we could disable it. Maybe disable/freeze stock dialer and see what happens?

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] drkhalidomer:
You already have a custom tile of auto brightness !! Better to remove that and keep the inbuilt one ! Cheers

Thanks to developers for this added feature !!
[Moto G 2015 Original Android Development] IronTechmonkey:
I hope not. I'm delighted to see that this is the result of a related commit previously flagged by [MENTION=6341989]drkhalidomer[/MENTION] and discussed here https://xdaforums.com/showpost.php?p=71951473&postcount=4224. To each their own tastes but IMO, it never made sense not have that button with the brightness slider, and it does make sense to have the auto-brightness setting or anywhere there are brightness settings.
[Moto G 2015 Original Android Development] KrisM22:
on 4-27 install, installing assistant (ok google) error. filed. regression 400

https://jira.lineageos.org/projects/REGRESSION/issues/REGRESSION-400?filter=allissues

Installs fine later manually.

This will be rejected as a gapps error.

Noted on open gapps forum thread.
[Moto G 2015 Original Android Development] KrisM22:
can't

---------- Post added at 12:17 PM ---------- Previous post was at 12:17 PM ----------

It's there.
[Moto G 2015 Original Android Development] SayantanRC:
Can anyone please confirm if they are experiencing a similar issue?

Call duration includes the time during which the phone is ringing. [MENTION=5119654]IronTechmonkey[/MENTION] can you reproduce it?
[Moto G 2015 Original Android Development] drkhalidomer:
Yes ! I have this issue but this was with 20 April build as well. Don't know whether it is network issue or ROM issue ?

Tested on VoLTE only !!!
[Moto G 2015 Original Android Development] IronTechmonkey:
I dont have a SIM in my Osprey (XT1540) ATM, but on Peregrine April 20 it does look like the live call counter not only starts before the ringing, but also seem to add a few seconds that did not exist (metaphysical phone calls?), and then in call history the details look more accurate, although I dont know how perfect.

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

Thanks, I got to exploring it... and should disclaim that this (brightness settings) is something that has always particularly geeked me out, and I even have a home-made Tasker scene with an alternate slider which returns the presently set values... hence these copious details :)

In addition to the new Auto-bright button, there is noticeably different behavior of the slider itself. Previously it would reach its lowest possible value before the slider reached the left-most edge. It seems to have been re-calibrated so the lowest brightness setting now occurs when the slider is all the way at the left edge. Likewise some adjustments seem to have been made on the right side of the slider. This actually makes more sense but it does take some getting used to. Another note: Osprey devices and this ROM have always allowed the auto brightness slider to set a lower brightness value than than manual brightness slider does, and that difference seems greater now. I can see why some folks may not like this change at first, but IMO this is how the slider should have worked all along.
[Moto G 2015 Original Android Development] KrisM22:
I have always felt that the brightness of the LineageOS was tops. I always leave it on the default "auto" and in almost all situations it has worked great for me, so very glad that folks have been working on this and improving it! Since folks have been having a problem with the "redshift" at night, I have been noticing how much I appreciate it and sure hope they can get hold of just what is causing the problem. Just 2 of the many reasons I give LinOS 5 stars and feel thankful for the literally hundreds of people giving of their time to support it.

---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------

We had mentioned the memory in settings and I took note that it was only in the 600's after this install - maybe less because google advisor failed for me but interesting none the less. It's only an average and is up to 1GB at the moment so I must have done something weird in the meantime. Gee, I am wondering if google advisor is causing a big RAM load... I'll see what happens if I remove it. EDIT: yes, actual ram was at 710 without it, add it and it went up to 780, remove voice model and it drops to 740. A reboot plus 1 min to settle down and it drops to 703. Expensive feature.

I had noticed this past week that google advisor caused the install to go completely bust when I was flashing I forget what rom but I think 3-23 nano gapps. In the future I guess I will simply say "no thanks" when it offers it during install and install it manually later (settings/google/search/voice ) EDIT - actually because of the load (edit above) I will just not use it since all I have to do is tap the microphone in the search box at top of screen (default Trebuchet)