yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] IronTechmonkey:
Yes that may be another factor. I stayed with SuperSU until recently to keep a few apps happy. In the process of switching to a native LOS SU I would do my flashes under native SU until I hit a wall, some app that requires SuperSU. A few months ago the last of the app I use caught up with native SU. That all being said, bug reports should come from a ROM with Native SU if possible.
[Moto G 4G Android Development] IronTechmonkey:
Camera (and more) FC when attempting to take panoramic picture

Jira ticket: https://jira.lineageos.org/browse/BUGBASH-326. Please vote on it if you can reproduce this:

Camera (and more) FC when attempting to take panoramic picture. Tested in clean flash of March 23 Peregrine with native SU, no gapps, no apps except matlog, attached log (at jira) spans:

Open camera (obliging first time permissions prompt)

Switch to panorama mode

Start picture.

Motion on screen stutters as camera pans and the it feels as if the rotation sensor is being unpredictable and or off scale.

Camera crashes near after nearly 360 degrees of rotation, seemingly bringing down other things in the UI (status bar icons may disappear after this crash).

Open camera.

Start another panorama picture

The overlay which states that a panorama picture is in progress and warns about speed is missing.

During second attempt at panorama picture camera crashed after about 180 degrees of rotation.

Has also been reproduced in clean flash of Osprey where the pattern of symptoms is similar but seems more severe. It might be worth noting that Peregrine has a gyro sensor which Osprey lacks, just where this may involve a sensors issue as common cause with result rendered variable by different hardware.
[Moto G 4G Android Development] mrLoma:
It used to be in the second gestures menu. Than it was moved to buttons. Now the options looks gone and always on, strange.

I have the same FC on panoramic pictures.

Btw.

I found a jira that states the gyro doesn't work on another device as wel

https://jira.lineageos.org/browse/REGRESSION-221

It looks very similar to the issue I see with the gyro.

I added a comment, is that ok or should I have made a new jira ticket for peregrine?
[Moto G 4G Android Development] IronTechmonkey:
I did see that ticket when researching but I'm not experiencing the same issue, just the possibly app related calibration issue.

I'm not convinced that this is a sensor problem. The values in Aida64 and Sensors Multi-tool look good, and every app that needs to use the sensor is able to do so including Google Maps with a fairly precise cone of calibration. Even in the app Here WeGo the sensor works fine in spite of the fact that the calibration routine seems broken.

This begs the question, what app are these of failing calibration routines part of (within app, or an OS component)?

Another significant bit of evidence (which I believe I mentioned before) is that the same calibration routine fails on the Osprey device which does not even have a gyro sensor. On my devices this is playing out as a Here WeGo app issue so far but I'll keep looking.

You're usage case may be flushing out another issue or helping with the existing one. Let's see what becomes of that jira ticket.
[Moto G 4G Android Development] mrLoma:
In your case the sensor value might look ok. The issue I seem to have just shows - in Multitool, so we probably have a different issue.

The jira ticket says it he happens minutes after boot, for me it takes way longer though. Rebooted yesterday, sensors still work. Maybe it's a specific usage that triggers it?
[Moto G 4G Android Development] IronTechmonkey:
Just to clarify, I'm not saying that these are not separate issues (or different symptoms of the same issue) as you mention, just that it is still not fully proven if and exactly at what point either of these issues may be purely ROM related Past history as case in point:

I've seen orientation/accel/gyro sensor disappear in CM12.1 when being used by 2 apps at once but I forget whether that was on Osprey or Peregrine, and the hardware difference matters between those 2 devices. I've also seen instances where competition for camera hardware caused simar issues, in some cases requiring emergency reboot (CM11).

So.... we test and keep watching. Thanks for digging into this one and posting at jira. I'll keep an eye out for opportunities to test, and on the tickets.

BTW, Speaking of jira, it looks like they've accepted and assigned the newly created tickets that we (and perhaps a person or 2 from Osprey) voted on. It is rare (perhaps never before) that we are allowed to submit bug reports (as opposed to regressions) on nightlys/weeklys and it's nice to see them moving along. Thanks!

[MENTION=7785396]mrLoma[/MENTION] FYI: A new gyro sensor specific ticket https://jira.lineageos.org/browse/BUGBASH-348. This might be a ROM issue after all and might benefit from some testing (although I still cannot reproduce this one). I learned of this in the panoramic picture ticket (https://jira.lineageos.org/browse/BUGBASH-326) for what that is worth.
[Moto G 4G Android Development] FrozenDroid90:
Hey there. I did a clean install of the lineage-14.1-20170302-nightly-peregrine-signed.zip and I have been having some issues with speed on the app ever since, even with the phone on performance> battery life. Particularly chrome has been slow, but pokemon go has been VERY slow and the phone itself has been slow to bring up apps. I did a dirty flash of the latest nightly, and it has still been slow. I hate reinstalling apps from scratch, and am sketipical that another clean install will help. Anyone have any clue why its been going so slow? I have greenify installed as well. Still did not help.....

Thanks!!!
[Moto G 4G Android Development] mrLoma:
Hey, could you give us a bit more info.

How much free memory do you have. Do you have apps like an antivirus installed? Do you have a lot of apps running in the background?

The slow apps are they installed on the internal or on an SD?

What exactly is slow about the apps? Is it the loading or the responsiveness once the app is open?
[Moto G 4G Android Development] FrozenDroid90:
How much free memory do you have.

Total memory: 869 MB

Average used:55%

Free: 393 MB

Do you have apps like an antivirus installed?

No antivirus

Do you have a lot of apps running in the background?

Rarely have any apps running in the background ... I just use my phone for facebook, pokemon go, gmail, and a few "food" apps like mcdonalds. I exit out of the apps and use greenify, so this should not be related.

The slow apps are they installed on the internal or on an SD?

The apps are installed on an SD- remember though: this issue started after I swapped ROM's . I was running SHOstock/

What exactly is slow about the apps? Is it the loading or the responsiveness once the app is open?

The loading of apps is slow, and the responsiveness is slow as well. Chrome can take up to 30 seconds to navigate to the next page, or 10-15 seconds to scroll down.
[Moto G 4G Android Development] IronTechmonkey:
Those results from a nearly 4 week old build and from a dirty flash on top of that build dont indicate any problem with the ROM itself. Whether you want to solve this in the interest of ROM development (which is the purpose of this thread) or in your own interest, you would clean flash then test incrementally as you configure the device and install your apps until you can reproduce the issue then log it.

Greenify can actually cause greater demand for R/W accesses and processor and should be removed as a possible a factor (as should a other things in your situation, most likely).

Using external SD as internal storage? If not then how are apps going on external SD in Nougat?

In any event, if you want to troubleshoot this in a meaningful way you should clean flash and bug test as described here: https://xdaforums.com/showpost.php?p=71514770&postcount=737. Also, you might consider using a a backup utility such as TiBU so you dont have to "reinstall apps from scratch". As a testament to how useful TiBU can be (if used properly): I've not had to reinstall all apps from scratch on any of 4 devices over 3 years and many dozens of clean flashes in that time.
[Moto G 4G Android Development] FrozenDroid90:
Are you saying the 4 week old build should have been as slow as it was? I have not seen anyone complain about that build. I updated to the latest version in frustration of the slowness. I expected to see some improvement, even with a dirty flash, but alas, none...

Regarding greenify and removing it- it appears that the consensus is that it is a positive force, not a negative one. Can you explain why it would harm my phone specifically? I am a pretty average user and don't understand why my experience would vary so far from the consensus.

I don't recall being asked how I wanted to configure my sd card, but some of my apps are listed as being in external storage. I'm not sure if I somehow configured it to be internal storage, but that would have been accidental.

Regarding titanium backup. Isn't that only for root? I didn't even want to enable it and install SU for fear that Pokemon Go would detect it and not function. Is there a non-root alternative? My biggest miff with doing clean installs is that I lose all app passwords and logins, which is a pain. If there was some alternative, that would help immensely.

After typing the above, I followed your instructions and did a clean install . I ended up needing to update recovery from 3.0.X to the latest version( 3.1 I think).After doing a clean install using the pico google apps, I left off the privacy guard, and installed pokemon go. Its extremely fast. Chrome (beta) is fast and responsive as well. I noticed that after I did a full wipe and install, it never asked me how to handle apps, but they are automatically going to my 32gb external sd card. No clue why. My suspicion is that privacy guard or the micro gapps I previously installed caused some issue. I say this because the older ROM version I installed was just as laggy as the dirty flash, and I did everything supposedly right when I installed the older version initially. I dunno though
[Moto G 4G Android Development] IronTechmonkey:
To my point, and to the evidence you describe; these are not likely to be ROM issues.

There is no reason to expect improvement when dirty flashing on top of an existing mess.

Among fans of the app perhaps, but not in general. In fact, many knowledgeable techs and devs for whom these things are a specific focus would say so more strongly than I have.

If that happens without your direct interaction then there is something very wrong with your setup there which you would have to clean up before being able to provide any viable bug testing results for LOS.

If that is something that you did but dont remember then you are being careless and cannot expect others to fill the gaps. That also casts doubt on every claim you make about the device's condition and what process you followed. The veracity of those claims is critical to issue reporting, and since previously provided information cannot be taken at face value as accurate, I recommend doing research about clean/dirty flashing and ROM bug reporting then start with an actual clean flash and controlled incremental testing. Good luck.
[Moto G 4G Android Development] mrLoma:
Good to hear your issue is solved.

About greenify, I used it in the past with the stock ROM because it never had free memory so it helped a great deal. Ever since I flashed cm or lineage os I never bothered cause I had better battery life and memory usage than on stock ROM with greenify.

What greenify does is shutting down apps, stop them from running and removing it from memory.

The newer android os actually does that very well by itself.

What's negative about greenify on a newer os is that the os can't optimize the app usage itself. If you have to open an app from scratch every time, your phone had to load the whole app to memory etc time and time again instead of leaving it in memory, which takes more resources (battery and lodging time)

I would suggest leaving greenify uninstalled for now, start using the back arrow to close apps you don't use often instead of minimising the them with the circle.

Or remove the apps you won't need frequently from the recent app list.

If you still feel like you need greenify after a week or so, when your clean build had time to optimise your app usage, you can install it again.

Removing the FB app from my phone was a big optimisation too ?, I don't use it often so the mobile site is enough for me.
[Moto G 4G Android Development] IronTechmonkey:
Not just newer OS and not just Android. In any system, if we disable the native functions that keep things in memory or cashed there will be a resource cost to wake them up each time they are needed.

Good advice. Greenify can do no good for ROM testing and should be removed as a factor at least until an issue is resolved or abandoned. I back button out of everything and also have a Tasker task that simulates screen input to clear recent with one tap. This is also supposedly not ideal for optimal performance but it works for me and I can get nearly 2 days on a charge, and most importantly - it does not interfere with or invalidate testing results.
[Moto G 4G Android Development] FrozenDroid90:
Wow, you did not read my post all the way through. Perhaps you should read all I have to say before resorting to being condescending. In my last paragraph I relented and did what you said, no need to be insulting.

I'll emphasize again: when I originally installed the 1 month old version, I did a fresh clean install from shostock. I wiped everything. My TWRP was the latest version I could find at the time as well. You have not given a reason why what I did was a " mess" and why I had slow speeds. I have no clue what I did wrong, if anything. My only guess was given in my last post.

Regarding the sd card, you have missed where I said I followed your instructions to a T with my installation last night, and the apps have still installed themselves on my sd card without any prompting from me.

I would have remembered being prompted, and I never have. Please be respectful when replying, so that I can likewise take your post seriously. I did the right thing in following your instructions and resolved my issues, don't then patronize me.
[Moto G 4G Android Development] IronTechmonkey:
Apologies for being curt. To your point I did miss the last part but not the preceding and details which I reviewed thoroughly. Thank you for clean flashing.

I did not question that but rather indicated (or meant to indicate) that later after things slowed down on the device, dirty flashing unlikely to fix.

You may be the only person who can answer that until something can be established as a reproducible ROM issue (which is seems unlikely in this case). If this seemed like a ROM issue and if I could have reproduced this I would help test. Whatever was going on was outside of the box of normal expectation whether caused by you or incidental to something else. Unfortunately that leaves it up to you to follow a clean process and try to figure out what it going on. Also, logs logs logs (more about that below)

This is the strange part and perhaps the crux of the matter. Even though that is possible to do by accident (see below) it should not happen automatically unless...If you were by any chance using an SD card with some legacy of old OS on it (such as having been used as internal storage)? If it occurs again try a clean freshly formatted SD. As well as a clean flash. Also, logcats would be in order.

That isn't how it was presented in the previous reports and you could not blame someone reading them for wondering if no-one was looking at the screen at the time. Thanks for clarifying. Getting to the nitty gritty, the "SD as internal" prompt may appear automatically in some case but not others. With the prompt popping up at first boot (Google trick to get us to use SD internal storage) to your point it is fairy easy to do it by accident however, if the prompt doesn't appear at first boot (which has been my experience) it would take more steps and be very unlikely to occur by accident. That being said the no prompt installation seems off (and I'm going to research it later). If it occurs again I recommend the bug testing steps from the previously posted link. Logs can answer most of these questions.

- Testing is done in a clean flash of most recent nightly/weekly with no mods or hacks and is done under LOS native SU package (if any SU package).

- Provide Details of the device (model #?* Single dual SIM? Anything that distinguishes your device from others running the same ROM).

- Name the specific nightly/weekly being tested (and Gapps package too).

- Provide a description of the exact steps taken to reproduce the error (so others who would try to reproduce or fix the issue might be able to test it).

- Share a logcat taken while the issue was being reproduced as described in previous step.
[Moto G 4G Android Development] FrozenDroid90:
I see now. Thanks for clarifying

I appreciate it. :good:

Everything is working fine on the latest ROM, so I suppose its irrelevant to try and troubleshoot whatever went wrong on the older version . Admittedly the opening of the apps has started to slow a bit, but its not a large enough issue to pursue , IMO, and could be related to the SD card issue....

I was using it as internal storage on SHOstock, but I did an advanced wipe on the latest version of lineage I installed last night, and most definitely checked the box that wipes the SD card.

To be fair, in the post where I said I may have accidentally made it internal storage for lineage, I later clarified that when I did a clean install, I was not prompted to use the SD card as internal storage. Either way I plan on moving the apps over, wiping the sd card again, ejecting it, putting it back in, and seeing what kind of message I get.

I will do this in the future. I didn't know if there was some obvious thing I was doing to make it malfunction ( Like privacy guard) that would make this an easy fix and avoid posting a log such as that. It vexed me that my mileage was so much different than everyone else's, and I was convinced there was an easy solution. As it turned out, doing a clean install and only adding on the bare bones essentials appears to have solved the issue. If I encounter this issue again, I'll report back using the critera you gave.

Thanks for helping out, I appreciate your effort.
[Moto G 4G Android Development] IronTechmonkey:
Thanks for the reply. I've really mangled the thread here with some bad manual quote management while mobile (apart from being a harda$$ earlier). Will clean up and reply later when I'm at a desk.
[Moto G 4G Android Development] FrozenDroid90:
Not a big deal.

I moved all apps over to internal storage, formatted the SD card using the storage settings, ejected, and now after mounting it again, I can use it as internal storage or portable. Utilizing the latest TWRP to wipe the SD card did not revert it to portable storage( which is what I did earlier), and is what caused it to install my apps into the sd card. Now I'm wondering if its ill advised to format the sd card as internal...
[Moto G 4G Android Development] IronTechmonkey:
Glad you posted this as I was preparing to jump down that rabbit hole. If I'm understanding correctly the SD card was previously formatted as Internal. Ironically the preservation of apps on SD as internal seems to be a blessing for those having no issues and who use SD as internal across ROM flash (seems to preserve apps), and is a curse for those in your situation having to switch between the adopted and portable (reformat required).

As to formatting the SD card as internal (adoptable) storage there are significant downsides depending on usage case, one of which you seem to have experienced. There is a good description here: https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/. More details (and my opinion) here:https://xdaforums.com/showpost.php?p=64135969&postcount=36

Recommendations for flashing workflows should account for this. It may have done you no good this time, but in future recommendations I'll include some warning about adorable storage. LOL mis-spelled adoptable was just spell-checked as adorable which it certainly is not. Even spell check doesn't like it. I'm actually thinking of making a FAQ for all this but have to see what else is out there first. Thanks for the mental bounce back.
[Moto G 4G Android Development] _that:
Meta comment: Awesome debugging and testing work on the last few pages - that is how development threads are supposed to be. And congratulations to [MENTION=5119654]IronTechmonkey[/MENTION] for becoming a RC, you deserve it!
[Moto G 4G Android Development] mrLoma:
Congrats [MENTION=5119654]IronTechmonkey[/MENTION] .

I had the sensor issue again.

I have a logcat but I want to remove my personal info.

I tried to upload but I keep getting network errors on the app

... ow on pc it says this

"Your file of 779.8 KB bytes exceeds the forum's limit of 512.0 KB for this filetype."

ok I split the logcat in 2 :/
[Moto G 4G Android Development] IronTechmonkey:
Thanks, and thanks for logging. 779.8KB may not seem like much in this multimedia age but for a densely packed text file (which AFAIK cannot be compressed as effectively as others) that is large.

I'll check it out later albeit without understanding much of it. Did you get any closer to being able to intentionally induce the issue? If not, what apps/activities were you using/doing. If there is no fix in next build I can introduce those factors to my testing.

---------- Post added at 05:26 PM ---------- Previous post was at 05:21 PM ----------

Thank you for the ROM and tech playpen which, along with LOS jira's window of willingness to receive bug (as opposed to regression) reports for nightlys/weeklies, makes the bug reporting more gratifying.
[Moto G 4G Android Development] mrLoma:
Well it is a log of like 2 days. No repro yet. It only happened with the phone on longer than a day. Never had it really fast. I'll keep an eye on it and open Aida from time to time
[Moto G 4G Android Development] IronTechmonkey:
Wow, that's dedication, and does add some clarity: That being that the problem may not be flushed with quick tests, and that sustained testing might be required. Thanks!
[Moto G 4G Android Development] aha360:
I don't know where to post this, but congratulations on being promoted to Recognised Contributor [MENTION=5119654]IronTechmonkey[/MENTION].
[Moto G 4G Android Development] IronTechmonkey:
Thank you. It means I'll have to be somewhat less of a grump but I hope to be up to the challenge. :)

BTW, this ROM, this thread, and the fact that (for the time being) jira is accepting bug reports for weekly builds have stirred up my enthusiasm.
[Moto G 4G Android Development] aha360:
Yes - that's the main challenge with being a forum member with staff-level rights - patience, especially when you have to deal with idiots, and I have had some personal experience in that regard.

That said, I wish you all the best for this and thank you for the contributions.
[Moto G 4G Android Development] LuK1337:
That error has nothing to do with you not being able to boot the system.

Try wiping your data using `fastboot -w`.