yashsingh1/xdaforums huggingface dataset:
[L Speed] Paget96:
I found that too, but i wasn't sure about it. All the time it was not-zero. I'll do a change now, so we can proceed :)

Thanks for heads up.

Here:

https://www.kernel.org/doc/Documentation/laptops/laptop-mode.txt

Now, Dynamic virtual memory have more sense, checking atm, and yeah laptop_mode made a problem all the time, now device holds dirty memory as much as defined. :)
[L Speed] Paget96:
Yes, they will be separately configured.
[L Speed] DB126:
While the effects of DVM may have been influenced by laptop_mode the core arguments presented here and in several prior posts remain largely unchanged. Static VM values (battery/balance/performance/etc) make more sense as different devices and workflows benefit from different settings.

DVM can't anticipate these factors in real time. The persistent foreground task is unwarranted as I don't believe there are significant (measurable) gains by changing VM parameters based on screen on/off state and possibly other factors. L Speed has much to offer to mainstream users - really want to avoid the appearance of 'snake oil' which diminishes reputation.
[L Speed] Paget96:
I'm currently highly testing it, and will see after few battery cycles what to do with it, but as i can see after changing laptop_mode to 0 it seems drainage is a bit increased due to bigger flushes. We'll see ;)
[L Speed] DB126:
Yes - that's a possibility with some devices & workflows. My daily driver saw a whopping 10-15% drop in hourly drain with laptop_mode = 0. Impact is more muted on my mobile (phone). Need more testing to weed out day-to-day variations. Also evaluating with some secondary devices that don't see much use.

If laptop_mode does have advantages due to smaller, more frequent flushes it may be better to manage size and cycles using dirty/dirty_background ratios and expire/writeback timings which can operate more intelligently. Or, return laptop_mode to a dedicated setting to give users a choice. I suspect some individuals would prefer a fixed dirty flush every xx seconds vs relying on mysterious VM tuning parameters that don't always reveal their secrets.
[L Speed] Paget96:
Yeah true that. I also found that keeping dirty_background_ratio to 15, dirty_ratio to 10 and increasing centisecs give better responsibilities, since data stay a bit longer in device and device can't fill them up to 15% to block I/O, i need to do more tests and track vm. We'll see (again). :)
[L Speed] DB126:
Similar findings. I have settled on 5/20 for dirty_ratio/dirty_background_ratio and 500/1500 for expire/writeback centisecs on a 2GB device. That insures dirty data won't age past 19.99 sec (worst case) with average retention being much less. Increasing dirty_ratio to 10 would probably result in a bit less I/O and may be better for device with <2GB RAM. I would not increase background_ratio beyond 20 as that could result is a sustained synchronous write lockout if/when the threshold is met.
[L Speed] Paget96:
Exactly, also i have one more finding.

https://serverfault.com/a/131376 - check this one.

Again it's for his usage, but let see this, we are using Android device which cannot make that much cache to flush, I'll also do some tests on this. If you have a time, increase the lifetime of caches to 2-3mins, and track VM, I think it shouldn't go over 5mb.
[L Speed] DB126:
Hmm - thoughts:

- storage hardware in linked example was likely rotational and thus relatively slow once write buffer fills

- flushing to a HW buffer (HDD write-cache) is much less expensive than eMMC

- example workflows were highly transactional (active database) which is atypical of Android workflows

- android users are highly sensitive to 'lag' which can occur on large write-backs

- retaining cached anonymous (ie: app) data in cache for 2-3 min is dangerous on a mobile device

I see where you are going with this and it may indeed yield nice benchmark results. But I don't think it's a good config for real world use. Just my view of course.
[L Speed] phoberus:
Sorry can't take longer logs. Set the log max entries up to the maximum of 100'000 but I only see L speed service logs in the last 2 hours

Catlog and matlog
[L Speed] Paget96:
Ok, it's enough :) (i think)
[L Speed] Paget96:
I'm planing to merge light doze optimizations with aggressive doze, what do you think about that?

Reason is better control over doze (wakeups and time to go back)
[L Speed] HubrisRev5:
I am very impressed with L-Speed. It has been working great on my Nexus 4.

However, I have two issues.

1. Ok Google hotword detection stops after a while and does not return unless i reboot.

2. The nav bar turns dark orange after a while, and stays like that until a reboot (not the same as when battery saver is on).

Can someone let me know which settings may be causing these two issues?
[L Speed] XDAMaxe:
I'd appreciate this because of exact those reasons - to make a good app even better :)
[L Speed] rogxd:
I don't know, because I don't like aggressive doze. I always use light doze optimization...

Inviato dal mio SM-G900F utilizzando Tapatalk
[L Speed] Paget96:
For first one i need logs, second one is "System battery saver" enabled :) Disable it in L Speed, and you should be done :)

Thanks :)

I have great idea for it. :)
[L Speed] Paget96:
Light doze optimization removed, exactly it's merged with aggressive doze.

Now, toggling aggressive doze will enable set of parameters for more efficient dozing, disabling aggressive doze will return to device defaults.

Things which i have to do:

- After all maybe I'll not use standard command to go into doze (aggressively) I'll tweak those parameters so device will have normal doze behavior with just shorter timing, so it's how to say aggressive :)

If anyone have suggestions, write them here, or telegram, or facebook page, facebook group or Google+

Thanks for support. :)
[L Speed] DB126:
I lean in favor of this. While I do not use either of these modifications (my devices generally don't suffer from insomnia using vanilla doze) I believe the additional granularity offered with two controls is probably more confusing than helpful. A single control titled "doze optimization" is probably better.

On a related topic, I do wish L Speed would not automatically add itself to the doze whitelist even if related features are not being utilized. Have to disable that everytime L Speed is updated. User should be prompted for permission the first time a feature that depends on a L Speed background service or "wakeup" is enabled.

---------- Post added at 05:29 PM ---------- Previous post was at 05:11 PM ----------

Excellent IMHO as it differentiates L Speed from other apps that simply enable/disable aggressive doze with default parameters. This sometimes has consequences associated with being 'too aggressive'. Don't forget to allow a few maintenance windows; keeping devices in a comma for extended periods is just asking for nasty lag and high battery consumption when they are finally awoken. Also see here.
[L Speed] Paget96:
I'll do some changes related to permissions.

And idea for how to handle doze parameters and doze state will be how to say, let it be "hidden" for now. :D

I'll do it tomorrow after job, and probably we'll have beta tomorrow night. :)

I have done one preset for now, and will test it till tomorrow, if it shows good or close to good, l'll pass it to users :) my dear people ^^

Thanks for support ;)
[L Speed] raptorddd:
i have 2 questions

1. all settings have expanation of what it does. some say battery friendly others it drians battery. but if battery isnt mentioned means doesnt affect battery?

2. i/o stats says off performance so on means battery drains less.?

i/o boost says performance. it changes in KA the RQ afinnity to 2 says higer more agresive. so its drains battery? i selected battery profile and it was on. i dont know if those i/o bost and i/o stats off drain more battery.

thanks waiting for next release. :good:
[L Speed] DanGLES3:
Disabling i/o stats improves battery and performance as the system doesn't have to keep track of any log caused by i/o thus reducing cpu usage,i/o boost it says improve performance without draining the battery
[L Speed] h30_u10:
hi [MENTION=5514152]Paget96[/MENTION]

Maybe my question is stupid or basic but i want to know either this app is supposed to improve performance/battery by default also, like greenify/doze etc. or the user have to modify the things manually?
[L Speed] DanGLES3:
You will have to either choose any of the preset profiles (battery,balanced,performance) or manually adjust settings to your liking
[L Speed] h30_u10:
if you dont mind can you let me know where to select the above mentioned profiles as i am unable to fine in the menu.

following are enlisted

dashboard

CPu tuner

Lnet optimizer

IO tweaks

and so on.
[L Speed] nreuge:
I've had idle battery drain with v1.4.31-beta1 with Dynamic VM on.

No such issue with latest stable.
[L Speed] DB126:
Profiles - first item in menu - above Dashboard.
[L Speed] raptorddd:
thank you very welll explained :good:
[L Speed] h30_u10:
I dont have anything above the dashboard in menu. You can see the screenshot i pasted. Did i install a wrong apk or some other issue?

Edit: i re-installed the app from play store. Maybe there is some issue with the app on android file host. And i got the profiles. Thanks.
[L Speed] martyfender:
In the upper left of the dashboard you will see a 3 bar drop down menu where you would choose profiles. See my posted screenshots.

I'm not seeing your posted screenshot?
[L Speed] Paget96:
Well, i havent a time to write for them all, but it depends on the device :)

You have to change them :)

Will be fixed :)
[L Speed] Paget96:
I'm still working on new Aggressive doze. Alpha will be probably pushed later tonight :)

How it's supposed to work(you'll test it based on this):

- When device isn't connected to charger device will go in doze with normal behavior, timing will be just aggressive.

- When device is connected to charger and if "Disable on charging" is disabled device will be forced to doze like it was before.

if (Build.VERSION.SDK_INT > Build.VERSION_CODES.M) {
utils.runCommand("dumpsys deviceidle force-idle deep", false, su);
} else {
utils.runCommand("dumpsys deviceidle force-idle", false, su);
}

- When device is connected to charger and if "Disable on charging" is enabled, device should do nothing since it skips doze like normal behavior.

Now let's talking about changes on charger connected/disconnected(everything happens on screen off):

- If "Disable on charging" is disabled when you connect your charger device will immediately go into force doze.

if (Build.VERSION.SDK_INT > Build.VERSION_CODES.M) {
utils.runCommand("dumpsys deviceidle force-idle deep", false, su);
} else {
utils.runCommand("dumpsys deviceidle force-idle", false, su);
}

- If "Disable on charging" is enabled when you connect your charger device will immediately go out from doze.

Toggling service on it'll apply new parameters for aggressive doze, disabling it you'll get device defaults.

If you have any preset or a suggestion for it, tell me.

IF YOU WANT TO USE DISABLE SENSORS AND DISABLE ON CHARGING, FOR EVERY CHANGE ON IT YOU HAVE TO UNINSTALL AND INSTALL L SPEED, OR TRY DISABLING/ ENABLING DOZE SERVICE OR FORCE CLOSE L SPEED, THEN OPEN IT AGAIN. It's broken for now. I'll inform you about fixes in future.

I think this is all, if you have to add more or discuss about anything, just say. :)

Thanks for support.

EDIT:

Download:

https://xdaforums.com/showpost.php?p=75237614&postcount=24
[L Speed] Paget96:
#android #LSpeed

New alpha version!!!

v1.4.31-alpha17012017

Changelog:

- Virtual memory tweaks updated (disabled laptop_mode)

- Dynamic virtual memory updated (disabled laptop_mode)

- Updated ram manager profiles (improved calculation of min_free_kbytes)

- Improved aggressive doze

HOW TO TEST:

https://xdaforums.com/showpost.php?p=75236862&postcount=28970

Download:

https://xdaforums.com/showpost.php?p=75237614&postcount=24

Play Store:

https://play.google.com/store/apps/details?id=com.paget96.lspeed&hl=en

Join beta channel on Play Store:

https://play.google.com/apps/testing/com.paget96.lspeed

Follow L Speed on Google+:

https://plus.google.com/communities/114615858954464149084

Follow L Speed on Facebook:

https://www.facebook.com/LSpeedAndroidOptimizer

Join L Speed discussion group on facebook:

https://www.facebook.com/groups/169281933668021/?source_id=1503157226676471

Follow L Speed on xda-developers:

https://xdaforums.com/apps/l-speed

Join L Speed discussion on Telegram:

https://t.me/LSpeed

If you want, you can also donate me using this link:

http://paypal.me/Paget96

or simply disable adblocker and support me over ads inside the app :D

Play Store:

https://play.google.com/store/apps/details?id=com.paget96.lspeed&hl=en

Thanks for the support :D
[L Speed] gh0stzk:
Testing right now
[L Speed] h30_u10:
Thanks for your reply. But i sorted out the issue. The issue was in the app i downloaded from XDA. Now i downloaded app from play store and found the profiles option and all is well. :D

Thanks.
[L Speed] martyfender:
On the last beta and the current alpha, system battery saver keeps getting enabled on a reboot sometimes, on one of my 2, Nextbook ares 8a's older tablets, rooted with Magisk 15.3.

I have disabled it in the settings. On reboot, I see that it is in the orange, battery saving mode.

What was the last version, before the dynamic virtual memory was added? I want to install that again, as it was the better version. battery life was much better on the older versions, in performance, govtuner, mode. And by the way, I keep dynamic VM disabled.

Thanks
[L Speed] Paget96:
I can't remember, and yeah read description of system battery saver. It should be enabled after boot.
[L Speed] HubrisRev5:
I will send logs if necessary.

But i checked and all my battery saving features in L are off, including System battery saver :/
[L Speed] raptorddd:
so you think that before DVM was introduced was better? ill try search for it. ill let you know i might want to give that a try myself.

here is 1.4.2.8 if you read 1.4.2.9 it adds DMV https://xdaforums.com/showpost.php?p=74838297&postcount=22
[L Speed] vleutmans:
Governor execution interval

Hi all,

Maybe not needed to mention, but the governor execution interval at 3 minutes causes a new shell process in memory every 3 minutes. Workaround: disable governor execution interval with cpu menu.

You can verify with osmonitor app.

Br

Michel
[L Speed] Paget96:
Try enable/disable it :D

Yep, i can set it open all the time, but i think it's not needed. Better to "wipe all the mess" after making it ;)
[L Speed] Paget96:
How aggressive doze works on your devices guys?

I'm not so impressed at all, and I'll update it on this weekend :)
[L Speed] gh0stzk:
Certainly at the moment i am agree with you, i feel no differencies with new doze.
[L Speed] Chinaboy5216:
Feels better on my note 3, might be a feeling but I get nice flat lines when not using the phone. I'm running on a synergy kernel test version and RRN vidwhal latest version.
[L Speed] ADM.GL:
I'm not sure about that, but the ram manager profile is so much better now.

*****

Addendum: The present doze, is a bit worse, on my four devices. Virtual memory is almost great now.

I never had drain problems with Ls after doze wake up/scree-on. Only with greenify.

--------------------
[L Speed] raptorddd:
its not needed on nougat right. this is for MM and previous versions.

i mean i use integrated dozed.
[L Speed] Paget96:
Nope, M+ devices. I'm using it on Oreo.
[L Speed] DanGLES3:
How does cache allocation improves performance/battery?,its not explained properly in the app
[L Speed] Paget96:
It's how much cache (in percent) can be stored in ram. More caches == possibility of OOM. :)
[L Speed] DanGLES3:
Thx for the explanation,you should probably update the description as it makes some people uneasy about using it.
[L Speed] Paget96:
I'll do, but that also means no other translations than english :)
[L Speed] DanGLES3:
Most lspeed translations tho are pretty bad (its not your fault) as some translators just flat out seen to use google translate on some words and it looks ridiculous,an example is the (now removed) runtime optimizations, in the brazilian translation it said it improved music XD because of the word tune as it also means music. I feel you could atleast basically check their translations with google translate to give you an rough idea if their translations are ok before implementing them blindly into your app.
[L Speed] DB126:
I tend to agree.

While aggressive doze is technically available/tunable on Android 7/8 I find the stock configuration is effective on most devices/ROMs when looking at what really happens during screen off operations *and* immediately after waking. If it ain't broke don't fix it.

But people like to turn knobs 'n dials and there are probably some situations where it helps.
[L Speed] audiomarko:
Hello, short information ... Trim task does not end :( N915FY samsung galaxy note edge 6.0.1
[L Speed] Paget96:
Run it again, and send me a logcat :)
[L Speed] audiomarko:
logcat .... short instructions for creation. [emoji15]
[L Speed] Paget96:
Start fstrim

Wait for 1 min to do something, then close L Speed.

Open it again, go to debugging section, save logcat.

Open internal memory (or sd, depends) amd upload logcat here :)
[L Speed] Paget96:
Disable motion sensors seems also useless, since it's default doze behavior.
[L Speed] raptorddd:
is there a way to disable all logging in android already counting logd and log.

i mean 0 logs.

are these needed? se pic
[L Speed] DB126:
True on on Android 7/8; false on Android 6.
[L Speed] Paget96:
It's possible, but devs wont get logs, so it's a pointless.

Yep
[L Speed] DB126:
At one time I sampled the impact of significantly reduced logging on Android. There was no measurable difference in battery consumption nor perceptible change in responsiveness. I concluded the benefit, if any, did not warrant the effort involved.
[L Speed] raptorddd:
is the gov tuner 4.2 in latest l speed.?

https://xdaforums.com/showpost.php?p=74377717&postcount=4452
[L Speed] Paget96:
Yes, it is ;)
[L Speed] Paget96:
L Speed will get a bit bigger update, doing some changes under the hood. ;)

If you want you can support me over ads ;)

Stay tuned :D
[L Speed] raptorddd:
nxiuosly wwaiting been coming here everyday and 3 -4 times a day checking thread. :good:
[L Speed] Paget96:
It can be done tonight, but due to my free time, i can't say ETA.
[L Speed] DB126:
Wow - better than china white (and apparently just as addicting)! :rolleyes:
[L Speed] raptorddd:
well to be honest i have tried in the past... and didnt see any change in performance or battery this been about a year ago. but i tried 1.4.29 and i love it. a, getting over 30mins on old battery. so am interested on whats new and how it can be even better then what it is right now.

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

i know thats disrespectful to devs. itll be done when it needs to be.. dont worry. good luck:good:
[L Speed] DB126:
Cool. It would be interesting and informative to narrow down which feature(s) are contributing to the improvement in battery life.
[L Speed] raptorddd:
i mean SOT am getting 30mins more..

using data connection,fb app,messenger app whats app. yeah i know FB app and messenger drain alot of batttery but my 10gb i get i have to use fb app. if i use browser i only get 450mb. so battery is old and before i had my main cores at 1.6ghz changed this time to 1.8 ghz and had about 30 minutes more of SOT.

i have to say i have rom debloated and dont have many services running also running microG.

main tweaks

fsync on

kernel sleepers opt. on

flag tuner on

ompeove scrolling on

animations to .75%

battery

battery improvement on

LNET

buffers small

ril tweaks on

NET TCP on

google DNS on

i/o tweaks

scheduler tuner on

sd tweak on

i/o boost on

partition remount on

virtual memory

balanced

cache reclaimng moderate

swappines disabled

heap optimization on

OOM dump tasks on

ram manager

balanced

debugging all to on
[L Speed] DB126:
Yep - race to idle (high burst CPU freqs) is a proven battery saver on most devices. Probably accounts for 90% of the reported SOT improvement. Artificially capping the upper/lower limits are usually counterproductive. But people keep doing it ...
[L Speed] phantom146:
This is true. Probably if you know how to tweak your cpu freqs yourself by your daily usage the world would be a better place lol.

If you use an interactive governor NEVER EVER limit max freq. Just go and tweak it and turn on align_windows if you think theres still not enough sh** going on.
[L Speed] Radnanum:
For better perfomance and battery life, should i turn on FStrim on boot and schedule it? Thanks before
[L Speed] Paget96:
enable it
[L Speed] Radnanum:
Your advice for schedule sir? Thanks :)
[L Speed] ahmed dzico:
Smartass
[L Speed] insigma28:
Flashed man will give let it rest no problems in test 1 either thumbs up mate.

Sent from android 5.1 powered by Nash and L speed

---------- Post added at 11:34 PM ---------- Previous post was at 11:32 PM ----------

A few I have man that you could add

Impulse

Blu_active

Alucard

These in the options of my kernel I'm on don't know if possible to add to mod :?

Sent from android 5.1 powered by Nash and L speed
[L Speed] psycho4us4:
Interactive please
[L Speed] kchaisu:
It is working fine on Saga; however, it is getting more complicated, please guide me for what should I turn on and off for my Saga. Thanks for your hard work with dying phone making it harder.
[L Speed] kakho55:
So far everything smoothly .

But is testing battery usage.

Let you noe how the results. :)

---------- Post added at 09:48 AM ---------- Previous post was at 09:37 AM ----------

apply governor tweak , need to select which mod to activate it?

Example , pegasus , etc
[L Speed] flarestar123:
Hybrid please
[L Speed] Paget96:
more information:

Governot tweak is script which change governor values inside your kernel. this mod feature doesn't add more governors to your kernel FALSE.

I don't need to tweak every governor :) because most of custom governors are good by it self :)

updated governor tweak will be in maybe test 5 or 6, need time to look at every gov, need enormus research on google, xda and other forums. :)

I addrd two new features for test3, I'm testing it right now ;)

featutes:

battery calibration

mount system as rw, this option hah :D you already know what is it :)

all of you have problem sometime with "system read-only" while applying features fom L Speed, and always you need to open any file explorer to gain root, bla bla.

now :D just select option mount system as RW from L wizard and that's it ;)

today I will upload it ;)
[L Speed] insigma28:
Wow man that's awesome mate take your time I'm even searching around governors and other things that could be added to L SPEED.
[L Speed] Jkay7:
I don't know whether it's possible, but it would be cool, if there was an auto update option that simply pulls the latest version and installs it. Just a suggestion, since even insigma28 is running out of ideas :D
[L Speed] insigma28:
That's a good idea mate I hope this could be possible [MENTION=5514152]Paget96[/MENTION] and lol man the only thing I could think of Is a few more governor tweaks and audio mod. As we know audio won't be added as it could brick another members phone but would be cool if we could have it in the mod. I'm also reading up on something will link paget to it.
[L Speed] Jkay7:
And what about universal commands? Sometimes you press enter, 5,2 or type back to go to the previous menu. It would be better to unify this.

Last but not least: enable/disable all option in Build.prop tweaks ?