yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] KrisM22:
So see lots of notifications or lose your LTE functionality.

[MENTION=2148908]reee[/MENTION]jn said he had a solution back in post#3381, but I didn't see it.

So ims.apk is no help to you.

Random old ideas:

?settings apps Phone Notifications

change A importance and/or On the lock screen - don't show notifications at all.

org.codeaurora.ims - change notification settings.

Long press on this notification bar and there a option appears. Click on them and there is a option to block the notification. After blocking it will not show on your screen again.

I have not tried this one: It can be disabled.. all you need is custom recovery and xposed.. Here is a video on how to turn it off permanently without affecting the VoLTE feature.. https://www.youtube.com/watch?v=QZiOl5dhYJE

I'm sure you've tried all those and many many more. Lots of folks telling you to just shut off VoLTE. Big help!

Apparently it's google's fault. Driving many folks on the web crazy.

Best I can do for now. Keep trying!
[Moto G 2015 Original Android Development] sargam44:
Thank you being explain me above process . It's been knowledgeable and helpful to other members as well.
[Moto G 2015 Original Android Development] Subinsmani:
Hey Pixel nav bar lover,,,,

Now we will receive this animated button by default,,,

there is some work on going,,,,

https://review.lineageos.org/#/c/157953/

Dnt know when, but there is chance to be add on 7.1.2

https://review.lineageos.org/#/c/167810/
[Moto G 2015 Original Android Development] drkhalidomer:
Pixel Nav Bar commit is committed on Mar 4 2017!!! Don't why they have left this?
[Moto G 2015 Original Android Development] drkhalidomer:
Can someone please give me the link for weather provider other than Yahoo !! Can't find any other in play store.

Yahoo doesn't seem to be accurate. Showing showers and it's sunny here :crying:
[Moto G 2015 Original Android Development] KrisM22:
I use BeWeather but no idea how they are in India (uses Weather Underground)(says clear for Delhi)

---------- Post added at 09:52 AM ---------- Previous post was at 09:33 AM ----------
[Moto G 2015 Original Android Development] xfahim:
You can try Dark Sky, I use it in NY and it's accurate down to the minutes here.
[Moto G 2015 Original Android Development] KrisM22:
:D
[Moto G 2015 Original Android Development] Arch Carrier:
Videos not playing on VLC Player when opened from File Explorer or standard gallery.

I know this is not the place to report bug; but due to LineageOS' brainless bugreport system it's the only way to get it out. (read below)

When playing a video file (made with the standard camera made) from the standard gallery (or other gallery: Leafpic) in VLC, VLC will freeze the video after 1 second.* But It will play the sound of the complete video though.

When opening the same file from a File-explorer VLC won't even show the video but will show the same behaviour described in this submission: https://jira.lineageos.org/browse/BUGBASH-361

The bug is there since the build of 2017-03-23 14:04:02

The bugrapport in the link is rejected because its hasn't got a logcat.txt attached. I tried to make a Submission myself to report the error. But it's impossible to make a logcat.txt in terminal on my device (yes everything is set correctly). I can't make a logcat.txt from my PC. May be another build-bug.......But.....I also can't make a bugreport about that it's impossible to make a logcat.txt (because bug-submissions without a logcat.txt will be rejected) Catch22!

VLC player is giving errors since 2017-03-23 14:04:02. I've seen this bug on two moto g 2015 devices already. The VLC problem is still present in build 2017-04-06 16:55:44 And I can't report the bug because of some catch22 bugreport-rule on lineageos.org

[MENTION=7967832]lineageos[/MENTION] fix your communication/bugreport options Which atm prevents LineageOS from getting info about real bugs.... I'm done for today. Will look for another Mediaplayer or if nothing gets done and LineageOS isn't interested in the bug another OS.

MOTO G 2015 Osprey

lineage-14.1-20170406-nightly-osprey-signed

SuperSu
[Moto G 2015 Original Android Development] IronTechmonkey:
This is actually the right place to report a bug as well as at Jira. In fact here is where you would come to kick it around and get the bug report shape. In regards to jira.and logging, without logs developers are left guessing and there is just no time for that, especially considering that a great many reports not bugs in the ROM. You may have encountered a real bug but logs are required in order to tell for sure (and even then it may or may not be a bug in the ROM - which in turn is another reason why the logs are needed).

Have you you tried using an app like Matlog? https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en.
[Moto G 2015 Original Android Development] KrisM22:
for a simple alogcat, use CatLog https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en and go ahead and file a report. Log level default verbose is good.

The usual stuff:

assure clean flash - no non-stock kernel or theme.

clean boot, start catlog, get failure, stop catlog.

Be sure to document the exact steps you take,

Thanks!
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI Catlog is 2 years old and no longer under development. Matlog is basically the same project more recently updated by a different developer (and possibly still active though a year since last update). https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en

https://xdaforums.com/android/apps-games/app-matlog-1-0-0-beta-material-logcat-t3155566

https://github.com/plusCubed/matlog Matlog active.

https://github.com/nolanlawson/Catlog Catlog unmaintained.
[Moto G 2015 Original Android Development] Arch Carrier:
Thanks for your reply.

I understand the importance of logs but this is catch22 situation. There should be a way to report a bug when a log can't be created. I've just wasted 2 correction: 3) hours trying to make a logcat.txt (in every possible way). I think the bug is real. VLC hasn't been updated. LineagOS has. But to find out I need to make a bug-report.

I've rebooted the device and replicated the bug. Matlog creates a mad long log (163384 lines). Which part is needed? The complete thing? And is it accepted at Jira?
[Moto G 2015 Original Android Development] IronTechmonkey:
That's like telling a mechanic to fix a car without any wrenches. You just need to get real about logs. The ARE required. That being said - onward:

Logs can be quite long indeed but a large log file is better than nothing. How big is the file size? Have you tried to attached it to the jira ticket? If it's too large maybe a shorter one can be captured.

BTW as a point of encouragement, the fact that jira said they would reopen it if a log is provided is a good sign (not all tickets are accepted even with log) and it may be worth adding to that ticket or creating a new one with a link to that one. Also, you may not always need a log from boot. If you are truly on a clean flash with no system modification and can reproduce the issue regularly then you might only need to log one instance of the issue.
[Moto G 2015 Original Android Development] Arch Carrier:
Where did you get the idea I don't understand the importance off logs? You probably don't mean it bad...but come on. I already told that I've spend 3 hours following the instructions on how to make a logcat.txt and trying all kind of troubleshooting when that didn't work ( a clear indication that I understand the importance of a log ;) )

This seems their policy: All bug reports require a logcat (http://wiki.lineageos.org/logcat.html); attach one and this can be reopened. http://wiki.lineageos.org/logcat.html

If catlog is the only way to get a bugreport accepted and catlog fails you're stuck. That's called a procedural error. Or catch22 https://en.wikipedia.org/wiki/Catch-22_(logic) (for example: it makes it impossible the report that the making of a catlog isn't possible)

But enough :).... back to the the bug and how to report it.

I don't know/think a matlog log is allowed on lineagos.org looking at their reply and instructions. (one of the reasons I tried so long to make a logcat)

Matlog created a 10 MB .txt file (163385 lines) I had to save it as attachment (which is just a .zip with the txt files in it), because it crashed when saving to .txt file directly.

I installed the first 14.1 build that appeared on the official LineageOS site, on 2017-02-23 00:33:09 https://download.lineageos.org/osprey and updated when an new nightly appeared. no non-stock kernel or theme.

Done!

-Started my device

-started matlog

-opened videofile default gallery from with VLC (recreated error)

-Stopped matlog

-exported log

I will try to make a smaller one and upload it on Lineageos.org and see what happens.
[Moto G 2015 Original Android Development] iyurcic95:
Hi there! This ROM is awesome! So, I want to help a bit with my contribution.

I noticed that as I download the updates, once them are installed, there are not removed (the *.zip file update). For this reason, as the updates are downloaded, the memory is filling up and you have to remove them by your self.

Also, in apps that you can write with the keyboard, the "writing line" is not showed on the screen and you cant see what are you writing, and if you make a mistake you cant fix it until you close the keyboard and see what is writed (Instagram's DM is an example).

One last thing I have an issue, is with Bluetooth. Sometimes when I try to connect with and drive (BT Speaker), this one is removed from the list so I have to match them again.

By the moment, those three thing I have noticed.

Thanks for this ROM!
[Moto G 2015 Original Android Development] Arch Carrier:
My list of downloaded nightly's keep showing the green button 'Install" (after I've installed them...) I can't remove them (only manually) But then already installed nightly's show up again as new versions and are ready to download again.... (the first build didn't have this problem!)

But I'll focus on the VLC problem first
[Moto G 2015 Original Android Development] KrisM22:
a) yes, I've noticed that update offers you the same version you are on until a new one comes out. I ignore that and never check updates. But then I always download LinOS and Gapps to PC and copy over to phone via USB and flash from TWRP. Personal choice.

b) I've never tried matlog - just how big a file are you getting? GB? I tend to recommend CatLog as it's easy to use but a log should be a log - same size, assuming verbose. Yes, definitely grab a log and put that one to bed! Thanks!

c) sorry you wasted so much time on alogcat. I avoid terminal stuff like that for just that reason.

---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------

Hi.

a) I believe ota update puts them in /data/data/ . This means that they are probably not accumulating since /data is cleared on a flash - however, it is easy to check if you are rooted and use a browser like FX, and look in what it calls system - then in /data/data/

b) if an app 's writing line doesn't appear correctly I would assume that would be the app's problem - you might try contacting them...

c) BT - a device should remain known by the phone. If it loses that memory you might have a BUG, especially if it's dependably repeatable.
[Moto G 2015 Original Android Development] IronTechmonkey:
Well....You are in the wrong place to complain about logging. It is just not that hard to do and there are many ways to do it. As to time spent... I've been here the whole time too testing bugs, and nobody is getting paid for this ;).

The ADB logging that jira pointed you to is perhaps the most powerful because it does not depend on the Android OS for everything but using it requires a learning curve. That being said, Jira will accept the logs from matlog, catlog and other logging apps if they capture the moment of the problem.

As to Matlog and catlog: They will generate similar logs and in fact Matlog may still use the same Catlog save location because it is a newer version of the same app. I recommend Matlog because its last update is closer to the transition between Marshmallow and Nougat. Links to the source code for both are pasted into a previous post for those curious about this difference.

As to log size: 10 MB is huge for that quick series of actions as you described. How much time transpired? To try getting a smaller one:

- Log as short a window of time as is possible while catching the issue.

- Try to set Matlog's "Default log level" Debug instead of verbose.

If you updated using the LOS updater within the OS that may or may not be a truly clean flash but that does not mean the bug report is for naught. Just worth remembering:

Clean Flash

- Boot to recovery.

- Wipe Dalvik and System caches (optional).

- Full wipe, aka Factory reset.

- Install ROM, Gapps, native SU package during same TWRP session.

- Wipe Dalvik and System caches.

- Reboot to system.

- Let the phone settle for 5 or 10 minutes to indulge first-boot-post-flash scans.

- Reboot, and give phone 5 or so minutes to perform normal boot and startup scans.
[Moto G 2015 Original Android Development] Arch Carrier:
Maybe it's better you don't reply to me again. You haven't read what I've wrote and seem to behave like a blind horse (reageren als een blind peerd), by keeping to try and teach me things I already know (like the the importance of a log) If I reply with arguments in controlled manner you ignore that reply but start complaining about me complaining (ow irony....) Semi-suggesting that I complain about the DEVs of LineageOS... (in this case Alberto97) Which I haven't ever! ON the contrary. I don't demand a fix and don't bash the bugs or the development. But I do have indeed critique on the stir approach of the handling and ignoring of some bugs. Why not accept that other people have other opinions? You could ignore it?!

PS] your suggested Matlog created a 10MB and crashed

I also noticed you have the need to tell you've spend a lot of time doing stuff for nothing. I don't know what your message here is, but realise that the world is full off people who do things and spend time and not get paid. In all kinds of fields. for all kinds of reasons. And sometimes they in fact do get paid/financial support. (You could be speaking with someone who donates to open-source/free-projects and single developers.....or maybe to a cheapo using free stuff for nothing.....we don't know each-other and I don't talk about what I do for nothing and if and what I donate to)

Lets move on and ignore each other. At least that's what I'm going to do. It's not working.

To be fair I expect you to reply to me again as it seems you like to have the last word. That's fine. Just keep in mind I'm not your audience. I'll skip it.

cya

---------- Post added at 04:01 ---------- Previous post was at 03:53 ----------

[MENTION=2945516]KrisM22[/MENTION]

Thanks for your answer and advise to use the catlog app instead. It did the job and made a file of around 800kb (matlog's file was 10MB)

I've now been able to make a proper bug-report: https://jira.lineageos.org/browse/REGRESSION-314

I'm interested if it's a bug or not. (I've seen it on 2 moto G2015 Ospreys with LineageOS myself) So I hope the report gets accepeted. IF not I'll try a totally fresh install first.
[Moto G 2015 Original Android Development] KrisM22:
First, and this is just a general reminder to all in the forum, if you wish to not see an individual's posts in forum and PM, simply go to

Control Panel (gear on top of page)

XDA Control Panel

Settings and Options

Edit ignore list and do your thing.

This is not a suggestion, simply know that it is available to all.

To all: Let's keep this thread pleasant!

Shocked that matlog did such a big file and pleased that CatLog gave a much more appropriate result and you were able to file the report. I do suspect that there are many good simple alogcat-type apps in the google store - these are just two. Apps are often updated and errors can happen - just try another.

Thanks for the link to the report.. Now we'll just have to wait to see what they do with it.

Thanks!

(as most folks here know I continue to edit my posts for at least 5 minutes after posting, to correct/clarify/brevity/etc wording.)
[Moto G 2015 Original Android Development] IronTechmonkey:
That feedback is appreciated. I'm going to log future issues with both to see if there is a problem with matlog... wondering if it may be having problems with SuperSU.
[Moto G 2015 Original Android Development] KrisM22:
ref https://jira.lineageos.org/browse/REGRESSION-314

Please do a new clean flash. I am unable to replicate. Thanks.

Cancel that - easily replicated when accessed via any explorer.

I added a comment and a logcat. pita. have you tried a player besides VLC?
[Moto G 2015 Original Android Development] jjsol:
https://xdaforums.com/attachment.php?attachmentid=4104606&stc=1&d=1491589310
[Moto G 2015 Original Android Development] jjsol:
1 Enero de 1970?

Does not install last nightly
[Moto G 2015 Original Android Development] KrisM22:
I'm looking at it. I'm trying it myself. Give me 10 min. - very slow - only 110KB/s. changes now faster.

---------- Post added at 03:16 PM ---------- Previous post was at 03:10 PM ----------

unsuccessful. tap 3 dots at top "delete downloads" start over - may be server problems. working on it.

---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------

failed again - server very sporadic. I will try this later, maybe in a few hours or so.
[Moto G 2015 Original Android Development] KrisM22:
probable server problems - you got a bad one - just delete it with the 3 dots at top, and re-download.

it's in data/data/org.lineageos.updater/app_updates
[Moto G 2015 Original Android Development] xfahim:
Huh it worked for me, downloaded and installed. Currently gapps are being installed.

Try downloading now.
[Moto G 2015 Original Android Development] KrisM22:
Thanks - yeah, server probs - I had to try 3 times to test for above, finally got it. Puts it in

data/data/org.lineageos.updater/app_updates

I will not use it as I am already there.
[Moto G 2015 Original Android Development] xfahim:
Installed the new build, first thing I noticed is the new bootlogo: https://gfycat.com/OrganicYearlyAcornbarnacle

I liked the previous one better to be honest.

---------- Post added at 01:55 AM ---------- Previous post was at 01:54 AM ----------

Oh I misunderstood you, sorry about that. It's a spare device for me so I clean flash almost always.
[Moto G 2015 Original Android Development] KrisM22:
It will be gone by next release - just an april fools thing, then back to normal. Same with the brozip thing - just for the first april release.

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

Yeah - just doing it because jjsol was having a prob. I normally d/l to PC, copy to phone and then clean flash from TWRP. Just easier for me!

EDIT: I also want to test whether it accumulates them in /data/data so will ota grab the next one as well just for that test. I think that's something that [MENTION=4288665]iyurcic95[/MENTION] mentioned.(post #3922)
[Moto G 2015 Original Android Development] reeeju:
Installing latest build...
[Moto G 2015 Original Android Development] xfahim:
Right, I forgot the whole thing. There's so many april fools "pranks" these days, hard to remember.
[Moto G 2015 Original Android Development] reeeju:
:good:liked that hotspot tiles longpress tweak
[Moto G 2015 Original Android Development] KrisM22:
what's that?
[Moto G 2015 Original Android Development] reeeju:
See the changelog
[Moto G 2015 Original Android Development] IronTechmonkey:
Seems like the long-press is now taking us directly to hotpot settings now instead of higher level menu. https://review.lineageos.org/#/c/165212

Also, there has indeed been much focus on QT in the last few releases. New tiles, change of name from "Custom tiles" to "Extra Tiles, new and better long press options. Personally I'm delighted to see this since one of the main reasons I skipped Marshmallow was the disaster (IMO) that was made of QT in the early going there.
[Moto G 2015 Original Android Development] KrisM22:
I get Widgets - Settings Shortcut - Tethering & portable hotspot. Job done

I don't get "longpress" - it's just tap and it's there.
[Moto G 2015 Original Android Development] IronTechmonkey:
In Quick Tiles (as opposed to widgets), Tapping "Hotspot" should enable a configured hotspot. Long pressing "Hotspot" should now take you to the "Tethering and portable hotspot: menu where it used to take you higher up the menu tree.
[Moto G 2015 Original Android Development] reeeju:
Very happy to see regular updates and most active thread....i m usiing this rom as my daily driver...somehow dont know why in mine previous roms (like rr, aospxtended, crdroid, etc) banking apps not working well...dont know its may be due to magisk cos couple of above stated rom got magisk...

But in LOS 14.1 all my banking apps are working well...

Thats why i m mainly able to use this as my daily driver...

No bluetooth problem in case of mine phillips bt50b & g blueetooth speaker....its just connect within a pulse?

And after many apps open it doesnt lag that much....its a very big achievement of this rom regarding to me...previously coc also lags in my phn...some times it lags during a mere call receive....

Now all the problem solved...

Pretty happy

Cheers [MENTION=4480917]Alberto97[/MENTION]

---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------

Thats what im trying to say
[Moto G 2015 Original Android Development] IronTechmonkey:
I know. I had not gotten to testing Hotpot yet and did not realize it. I use hotpots for creating off-the-grid local wifi networks for motion detection nature/security cameras, and this tweak saves screen taps. Thanks for the heads up.:)
[Moto G 2015 Original Android Development] KrisM22:
Thanks!
[Moto G 2015 Original Android Development] reeeju:
Forgot to tell ..

New bootanimation looks cool...

And that bro zip has spelbound me

---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------

Looks like ur a FBI person...:silly:
[Moto G 2015 Original Android Development] KrisM22:
yeah it's fun!
[Moto G 2015 Original Android Development] IronTechmonkey:
Worse, as I'm not necessarily bound by the same protocols, but at least the birds being recorded at the bird feeder dont care. :) The humans just dont know. ;)

But seriously, it started as a remote motion capture nature camera which turned into a genuine security system and it depends on a wide range of device functions (on multiple devices) so it's a good testing drill for ROMs as well as apps, VPN, Firewalls, FTP servers and more. Also, it is projects like that which have me motivated to test and support the custom ROMs on which those things to can be done.

Apologies for the OT, getting back on topic: Although the panoramic camera FC is flagged as fixed at jira, just an FYI that there may still be issues particularly when taking a pic while moving the camera around a shorter radius. I'm still testing that one on Peregrine and in the unlikely event that time permits I'll carry the test to Osprey (which also experienced a variation of that issue).

The symptoms are: that when taking pano pic in short radius (but a radius that works in other cameras) the recording goes on until about 270 degrees of rotation. Sometimes the picture is successfully saved and other times camera may FC before complete. After FC the overlay which states pic in progress or "too fast" may be missing at next attempt to take pano pic. It is reasonable that there be some lower limit on the radius but in that case the camera should report error rather than FC.
[Moto G 2015 Original Android Development] reeeju:
And in status bar its showing my connected bluetooth device's remianing battery just along with bluetooth icon
[Moto G 2015 Original Android Development] KrisM22:
Doesn't with my PLT-M165