yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
I should clarify that my custom dashboard is not a knock against the native settings which, as you say, have indeed gotten better over time, particularly in the management of the sensors. That dashboard just allows me to set exact values and can report the exact value in some cases when it is set by something else. Eg the lower limit for the manual brightness slider is 4% brightness (aprox 10 of 255). To the end of more accurately setting it the new slider arrangement gives us more screen space for the same range which, in turn makes it easier to pinpoint a desired setting.

I dont use Google Advisor but it would not be surprise if any of their utilities required a good bit of resources. As to RAM on 1GB devices, I'm presently testing a hypothesis that may result in a workaround for some people who often see apps getting killed on 1GB devices (if perhaps even a tweak in the ROM for those devices - I hope). This is a deep rabbit hole but I'll be out of it in a few hours or a day with a lot more about this.
[Moto G 2015 Original Android Development] KrisM22:
Nice! This seems good progress!

The "any of their utilities" pit is deep in itself and probably worthy of guidelines - I'm sure these will appear as you wander around the rabbithole. I will be looking forward hearing to what you discover. Just thinking about that was going to test the femto package but I guess it's not ready for prime time so I'll go amuse myself with pico (I usually use nano).
[Moto G 2015 Original Android Development] MrMosoani:
When I first installed LineageOS, YES clean flash.

gapps micro March 19 2017 165,533kb zip

average memory use showing under memory settings, 844mb total memory 899 (game not running)

It's very annoying when the game crashed in the middle of the Clash (action games) and you have to wait for the app to start all over again. If you're a gamer you'd understand how frustrating it is.

How can I avoid this auto-exit or auto close issue?
[Moto G 2015 Original Android Development] KrisM22:
If you read the last couple posts you can see we are working on ram/memory load. I just grabbed an apk for google services and playstore and will now go and flash 4-27 with no gapps and see what happens. Some massive experimentation going on here! Sit tight for a couple days!

EDT: unfortunately I didn't gain anything. Didn't have to add anything google other than gmail.
[Moto G 2015 Original Android Development] MrMosoani:
Thanks. Where did you get the APKs for google services and playstore? Are you suggesting I wipe dalvik/cache flash 4-27 with no gapps?
[Moto G 2015 Original Android Development] MarshalVarghese:
Goto settings>apps and tap the gear icon at top right corner. Open 'phon app' and enable pixel dialer as your default phone app. This should solve the issue:)
[Moto G 2015 Original Android Development] KrisM22:
all this stuff about not needing gapps is wrong - I was not wiping system.

Actual Ram use is 760 at the moment so I gained nothing over using nano, though I don't know what nano would have given me, if anything. I would guess that Lineage has done this to protect themselves from a ton of unnecessary "problems" arising from missing google basics.

LineageOS WIKI https://wiki.lineageos.org/gapps.html claims

yet playstore is there. yes, gmail and maps need to be added.

EDIT: so, what? LinOS "includes" opengapps arm nano? or at least Pico...

I surely hope [MENTION=5119654]IronTechmonkey[/MENTION] has vastly better success than I.
[Moto G 2015 Original Android Development] KrisM22:
To answer your question, I found them here

http://www.apkmirror.com/apk/google-inc/google-play-services/

Though, again, I never needed to use them as they are already in the LinOS ROM.

I screwed up here - I was not wiping system. when I did wipe system and flashed rom and installed those 2, it seemed unable to add my account, so I abandoned it.
[Moto G 2015 Original Android Development] BrokenBee:
When will this ROM support dual SIM mode?
[Moto G 2015 Original Android Development] Jamiéric GS:
Yes, bro!
[Moto G 2015 Original Android Development] KrisM22:
If you want it there and working correctly, the best thing for you to do would be to install LinOS, and then file jira bugs for any problems you find. That would help both development and you.
[Moto G 2015 Original Android Development] IronTechmonkey:
Although LOS has for a while included Google components which were at one time only introduced by Gapps it was my understanding that did not include the full suite of Google services required-ed to use Play-store, location and other services, but maybe this has changed. I did not realize it includes as much as you are seeing in Rom-only flash and will explore that when possible, with an eager eye towards running with no Gapps package.

I've had no problems with Open Gapps Pico on April 27 Osprey or Peregrine but then I only use Play Store and Voice Typing (and firewall the other Google stuff once done with clean testing) so, not the best comparison. As to Google Assistant, maybe this would help although it seems like a lot off hoops to jump through: http://www.lineageosdownloads.com/get-google-assistant-lineage-os/.
[Moto G 2015 Original Android Development] KrisM22:
I have been searching hard for things to chop out of LineageOS but so far have found nothing. Except maybe that assistant thing I mentioned above.
[Moto G 2015 Original Android Development] MarshalVarghese:
I got a bootloop today morning after flashing the latest build. Had substratum up and running. Was that the reason for bootloop? How can I get rid of this the next time I update the rom?

Thnkz in advance :)
[Moto G 2015 Original Android Development] KrisM22:
Do you get a bootloop on a clean flash with no mods, stock kernel, stock launcher, stock theme?
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes. Apparently substratum leaves some junk behind even when removed.

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

https://jira.lineageos.org/browse/R...issuetabpanels:comment-tabpanel#comment-13178

Considering the responses to that and other LOS Jira tickets where substratum was the cause of problems,

https://jira.lineageos.org/browse/R...issuetabpanels:comment-tabpanel#comment-13199

discussion of substratum would be more appropriately directed to a substratum forum as it is not part of the LOS ROM.
[Moto G 2015 Original Android Development] KrisM22:
I said that gapps was included in LinOS. It is not. I was not wiping system. Sorry.
[Moto G 2015 Original Android Development] IronTechmonkey:
Better that than some weird new curve-ball from Google. Thanks for the heads up.
[Moto G 2015 Original Android Development] MarshalVarghese:
No

Only when I updated
[Moto G 2015 Original Android Development] KrisM22:
AS I would expect. Theme engines, including but not limited to substratum touch just about every part of the system and often wreak havoc. . We (LinOS) could not begin to try to think about supporting them. Please follow [MENTION=5119654]IronTechmonkey[/MENTION] 's advice to look elsewhere for fixes - they usually have a forum or group. Thanks for understanding.
[Moto G 2015 Original Android Development] shravan27:
Guys I am having a problem with my custom ROM lineage os 14: I can make calls but I can't hear their voices but when they call I can hear their voices.any one knows anything about it let me lnow
[Moto G 2015 Original Android Development] KrisM22:
Excellent sleuthing! Well presented. I voted and have high hopes for this one. Good work! Nice! The Moto G1-4G is proving its worth to test beside it. The rabbithole provideth. Are you using the free Audiutor from playstore?

Folks who have thanked IronTechmonkey's post (and

ANYONE

who has a 1GB XT1540 Osprey! ), if you can vote for the jira, please do. This is such an easy fix if they buy it.
[Moto G 2015 Original Android Development] IronTechmonkey:
Kernel Adiutor (KA) from Playstore. My initial intention was merely to test squid2 Osprey kernel with lionfish governor, but then while exploring KA I noticed how disproportionately high the native (default) LMK settings were, then switched back to clean LOS 14.1 and saw the same thing. In regards to some reasonable doubts about whether or not KA is properly representing the default LMK values, I tested for that like so:

Allow the device to boot with no KA settings modifications, then set LMK to apply on boot without selecting any of the profiles or changing any parameters, then reboot, then go to KA's "On Boot” section where the command and parameters are shown. This seems to indicate that the reported settings are indeed the ones in effect. Attached images OspreyLMKdefault.png and OspreyLMKmedium.png show the raw values for the default settings and the KA medium profile respectively.

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

On a different note, the use of the camera in testing LMK somewhat clarifies a separate non device specific glitch with the camera, reproduced on Osprey and Peregrine but not yet logged:

- Panorama overlay text missing (occurs frequently but I’ve not gotten to charting the events which induce it), Once induced, restored by switching to different camera mode then back.

- If a panorama picture has been started and is canceled mid-scan or mid-render there is no way to switch to other camera mode until app restarted.
[Moto G 2015 Original Android Development] KrisM22:
Thanks

- not pretending to fully understand Kernel Audiutor (KA) my question was where are you getting the "default LMK settings"? From the "on Boot" page with it set off - from the slider values?

I initially thought my slider default values were different but they are the same, given the missing 126 value in the jira.

However, looking at KA profile on the "On Boot" page, I see for medium (rounded to MB) 14,19,24,29,34,44 , but when tapping Medium, the sliders go to 57,76,95,114,133,172 so I assume that KA is sensitive to the 1GB/2GB difference. I was hoping to simulate your 1GB settings which I guess I could do with the sliders - just wanted to make sure my thinking was right. This is not a big deal - just playing with what you've come up with!

I also think that once I tap one of those in Profile, I have to reboot to get it back to default. It does not remember what default was.

yeah, actually I've seen that... when you first started mentioning panorama a few weeks back.
[Moto G 2015 Original Android Development] shadowchaos:
minfree : 2048,4096,6144,8192,10240,12288

(8MB 16 24 32 40 48)

vmpressure_file_min :14336

(56MB)

enable_adaptive_lmk :0

You don't need aggressive lmk at all at any device which has a power enough cpu better than snapdragon 400.

And combine with low minfree ,it can hold as much cached apps as you can in the background .

When the system starts to lack free memory to open a new app ,it will kill background apps AND WHICH THE SPEED IS DEPEND ON CPU AND FLASH READING RATE .

So the "kill" move(include allocate) is not much different between current cpus .I'd say it's the same speed to kill apps when the free memory is 180MB or 0MB .

What is the limit depends on FLASH(emmc 4.5 ,emmc 5.0 ,ufs 2.0 ,ufs 2.1) than CPU than Memory (lrddr3 ,4) .

Above is my settings ,try it .It can hold much more than the default one and no speed difference between them.
[Moto G 2015 Original Android Development] KrisM22:
Where do you enter those settings?

Never mind - found it.
[Moto G 2015 Original Android Development] IronTechmonkey:
Those are essentially the same as the Kernel Auditor "very light" profile. In any event, all of these settings combinations seem to yield better performance than the default, which seem disproportionately high..
[Moto G 2015 Original Android Development] KrisM22:
Using KA to set a profile, puts that profile (not the sliders) into minfile.

In KA, set Adaptive Low Memory Killer switch to off - sets enable_adaptive_lmk to 0 (zero).
[Moto G 2015 Original Android Development] shadowchaos:
Fun with vmpressure_file_min is that if it set to lower than (largest number)/0.9 in minfree ,you can observe NEGATIVE free memory .

Once I set it to 50MB and saw -13567xxx MB free memory ,lol .Although it felt all normal .

For the enable_adaptive_lmk ,I think it matters .It acts more aggressive when it set to 1 that may ignore the minfree settings .This needs more tests . (It works what I want when it set to 0)
[Moto G 2015 Original Android Development] kiekeboeboe:
Hello, I downloaded "lineage-14.1-20170420-nightly-osprey-signed.zip" few days ago, clean install, everything works fine, really like this rom.

Yesterday I updated to :"lineage-14.1-20170427-nightly-osprey-signed.zip " using the LineageOS-updates button in Android.

The new update was download, but during install the system reboots every time into recovery twrp. Once in twrp, I was able to boot the system, but the update was not installed. I tried this 3 times.

So no i dirty flashed the latest version using twrp.,

So is it not possible to update LineageOS with the update function in Android?

thanks for your help, and keep up the good work!
[Moto G 2015 Original Android Development] KrisM22:
Some folks have had success with update, others not. I download to PC, copy via usb cable to phone and clean flash.
[Moto G 2015 Original Android Development] kiekeboeboe:
Thanks KrisM22, but it is a bit strange to do a clean install every week.

So I think I'll stay with this update, and only do a next update with a clean install when it is really necessary.
[Moto G 2015 Original Android Development] KrisM22:
Sorry - I didn't mean to imply that you had to do a clean flash - only that I do one because I do a ton of testing each week in support of folks here. You can certainly dirty flash - just don't wipe before doing rom flash.
[Moto G 2015 Original Android Development] kiekeboeboe:
Ok, I cleared Dalvik-cache and cache using twrp, before flashing the rom. Is this something I should avoid next time.
[Moto G 2015 Original Android Development] cutesammy1:
Hey, I had some problem with my phone just as with kiekeboeboe post #4425. Last week, the same scenario happened with me and I rooted my phone, updated TWRP and re-install update from Lineage OS. Today, I tried to install the newest update but the same problem happened. The system went into updating but stops at TWRP main screen. I thought I should update "root access" with supersu app. I downloaded it from the play store, selected TWRP recovery. Now, my phone is stuck in boot loop...what should I do now?

Hey, I finally got my phone out of boot loop. I figured that the supersu binaries were causing the phone to be in bootloop so I put my phone into recovery mode...copied supersu latest zip from chainfire website and then flash it using TWRP....Now everything is working fine.

Also, there are some bugs I have found in the rom...

1st - my call timer doesn't start from zero...i think it starts from the moment I touch dial instead when the call is picked up

2nd - In a conference call, if you go to home and come back to conference screen...it crashes.

3rd - my sim signals keep going low after few seconds....especially in LTE mode....It wasn't happening in earlier builds
[Moto G 2015 Original Android Development] kagowtham:
Any way to change hd notification to volte icon like stock rom?
[Moto G 2015 Original Android Development] KrisM22:
Depends on what you want to do.

For clean flash, in TWRP, I tap wipe, tap advanced, and check

Dalvik/ART cache

System

Data

and Cache

and then swipe the bar at the bottom to do it. Then flash rom, gapps, and supersu, and boot.

If you're doing an intentionally dirty flash, bypass wipe step and just do install for rom and whatever.

If it doesn't work, you could come back and wipe Dalvik and cache.

If still doesn't work, come back and wipe data.

---------- Post added at 02:29 PM ---------- Previous post was at 01:55 PM ----------

To do a LinOS update, go to settings/phone/update.

connect to wifi.

Then tap:

3 vertical dots(settings)(top right) click delete downloads.

<---------------

It may get confused if there's multiple updates sitting in there /data/data

Download the update.

"apply update" box tap update.

does stuff for a few secs and boots to TWRP special screen and automatically installs (you don't touch anything!)

after a bit it automatically reboots to LineageOS. (3 minutes or so boot - normal first boot)

Curiosity: What supersu you using? I use 2.79 . supersu was running through all of the above - makes no difference.

1) That has been mentioned here recently. I tested that and my call timer starts right when it starts dialing. I have not tested previous releases. File a bug if you wish after doing some research.

2) This would be a good one for you to start a log, get the crash, stop the log, and file a bug report - nice one!

3) have no idea - be sure you check that on a clean system before filing a bug.

Thanks
[Moto G 2015 Original Android Development] PixCrow:
Google map work in last update 4-27??

and there is any issues with Uber app?
[Moto G 2015 Original Android Development] MixMachinePL:
[MENTION=7363590]PixCrow[/MENTION] - everything works well, at least for me. No issues at all.
[Moto G 2015 Original Android Development] KrisM22:
a) google map works fine.

b) you'd have to ask at the uber app forum.
[Moto G 2015 Original Android Development] PixCrow:
sorry for asking about Uber App

One more question please. after i do a clean install should i keep bootlador unlocked? or can i locked it again?
[Moto G 2015 Original Android Development] adityak1303:
I don't think it's possible to lock the bootloader with a custom ROM installed. It'll remain unlocked. To lock the bootloader, you'll need to flash stock firmware.
[Moto G 2015 Original Android Development] KrisM22:
I am told that flashing the stock leaves the bootloader unlocked,
[Moto G 2015 Original Android Development] pjc123:
So, got tired of the Android 6.0 security update message popping up all the time and I installed Lineage. Everything went smoothly and I am almost done installing and testing all my apps, except for one thing:

The ES File Explorer app made my phone go completely crazy. Apps were opening up by themselves, various things flashing on the screen, etc. I replaced it with another file manager (Been wanting to do that anyway) and cleaned all the caches for a second time, and everything is back to normal. I did not have this problem with my Nexus 4, but that is on Lineage version dated 04-20 , if that is the reason.

What/How I installed, since this is asked every time:

1) Updated to the latest TWRP

2) Did a factory wipe. (Actually manually wiped everything except internal and sd storage).

3) Without leaving TWRP, installed:

Lineage dated 04-27-2017

Nano Gapps

Lineage version of su

4) Wiped all caches and rebooted.
[Moto G 2015 Original Android Development] KrisM22:
I tend to avoid ES file explorer - seems to want to do a bunch of weird stuff. Too many ads. That's becoming more of a thing of late. Lots of alternatives out there.
[Moto G 2015 Original Android Development] pjc123:
Yes, the ads are why I wanted to get rid of it even before the latest issue; just forcing me now. Very true that it is becoming the thing of late. They are also starting to rip features out of the free versions. Well, they have to make money somehow. One of my favorite apps for the Nexus 4 is Clean Master, but the ads are absolutely brutal. So I install it once in a while, clean the phone, and then immediately uninstall it.....and repeat when necessary. Well, off topic anyway, so back to installing apps. Rather than restoring my apps from Google or Titanium, since they were from Android 6.0, I am reinstalling them as to avoid any issues.
[Moto G 2015 Original Android Development] KrisM22:
Yep, ads are getting brutal. I'll buy a paid version if there's one available, but often there's not.

Good idea to reinstall coming from 6.0 .

I do use TBPro to restore apps after a Lineage flash but I tic the "apk only" box as I don't want to risk problems between releases because of stuff in data, especially with the security fixes. But that's a personal choice. ymmv.
[Moto G 2015 Original Android Development] justjr:
Yeah, I just ditched ES Explorer this week. Solid Explorer all the way.

Also SDMaid is so much better then Clean Master, no ads on both.
[Moto G 2015 Original Android Development] pjc123:
Even though I do Titanium backups, I have only used TWRP backups in the past if things go horribly wrong. But I could see a scenario where perhaps all new nightlies going forward will not let me update for some reason, then it would be extremely useful to have that Titanium Backup.

So under that scenario above, which type of backup would I do. There are so many. (apps, data,system, etc, or a combination of all). And then, what type of restore would I do? If I backup everything, can I restore just certain things? I guess I also should get the paid version at this point as well.
[Moto G 2015 Original Android Development] KrisM22:
Whenever I am about to change anything (test, new release, whatever) I do a nandroid (TWRP backup). I don't mess with the twrp backup settings. It's about 2GB. Then when I'm done I just restore that (via TWRP). If I'm going forward(of testing a different clean flash rom), then I would use TBPro to restore the apps as I always do a clean flash (cache, Dalvik/ART, data, system). I got the Pro version of TB a long long time ago as it makes batch restore easy, mindless. Just have to make sure you have backed up the latest stuff to TB before you change things.

So I always have a bunch of back nandroids for when I left previous releases - makes it easy to test. Too much memory? - I move them to PC.

I may be in twrp 30 times a week doing tests etc. I never use update as it creates a dirty flash (unless I'm testing some option for someone.)

OK time to start winding down this topic. Thanks. PM me for further questions.
[Moto G 2015 Original Android Development] IronTechmonkey:
Cloning another note from https://jira.lineageos.org/browse/BUGBASH-480:

In re LMK (minfree settings) I see this new general commit (https://review.lineageos.org/#/c/169885) having to do with “foreground process will be mistakenly killed when it uses content provider”. That commit might (or might not) address the app killing as I'm experiencing it (regardless of the LMK settings). That would be wonderful as it might also pertain to the few instances of such intrusive app killing that occur on Peregrine during panoramic pictures, and other devices.

That being said, even though the aforementioned commit might address some app killing, for what these details might be worth in regards to additional tweaks for Osprey XT1540, please see image LMKchart.png.

- Line graph used for visual effect and clarity between data sets but the actual values are only at the marked points.

- Default settings for Osprey XT1540 in LOS14.1, (red line in graph) seem like an outlier compared to others.

- Even the KA aggressive and very aggressive profiles (dark brown, light brown) maintain relatively low values for foreground Apps, visible apps and secondary server.

- CM12.1 on both Otus (Moto E 2nd gen 3g) and CM12.1 on Osprey XT1540 (blue lines in chart) use the exact same values as each other so they overlap in the chart and appear as only one line. When I manually place these settings in Osprey XT1540 LOS14.1 I still experience apps being killed.

- The settings profile that has worked best for me so far has been the KA Osprey medium settings profile which is light orange in the chart (tucked between the 2 lines for Peregrine default and medium). The reasons this profile works may have to do with the “Content providers” setting in particular. We’ll see if the aforementioned commit addresses that.
[Moto G 2015 Original Android Development] rodrigoalbq:
camera

How do I do when I use the camera, the music application does not stop?
[Moto G 2015 Original Android Development] Hedied4me:
Yes SD maid actually works. Apps like CleanMaster don't actually delete anything. Scan 5 mins later or shut down the app and all that stuff it says you deleted is there again. Sorry for the OT.