yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
I've never used touchcontrol from Google play market . it may be built into vanirs ROM though , I really never use touchwake or pgm
[Samsung Galaxy Nexus] Jagoflax:
I'll try it whith the SlimKat rom :rolleyes:
[Samsung Galaxy Nexus] AbhishekS:
I guess you have the pro version then.
[Samsung Galaxy Nexus] bsmitty83:
Lol I literally just found that out as you quoted me . but thanks that confirms it . I'm sick of seeing it in my logs
[Samsung Galaxy Nexus] Nephilim:
So just to reiterate, this will kill the maxed out cpu bug correct? If so I am going to post this workaround over on the G+ so that everyone can still enjoy v3 while waiting for the next build. ;)
[Samsung Galaxy Nexus] bsmitty83:
No this is the fix to keep audit from spamming the logs
[Samsung Galaxy Nexus] KJW979:
Tried deleting system/bin/auditd in root explorer and it just freezes up, does this need to be removed prior to installing?
[Samsung Galaxy Nexus] aosp:
Reverting this might fix that issue ;)

Fix cpuidle44xx.c · b2e5f85 · bsmitty83/DirtyV_tuna · GitHub - http://goo.gl/ooqI8s
[Samsung Galaxy Nexus] Nephilim:
Dammit! :(

---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------

Jesus man! why are you not building a f*cking 5.8 kernel? You are a damn freighter of knowledge!

I'll just wait for Smitty to go ahead and use that info. :p
[Samsung Galaxy Nexus] poo706:
I'd just like to add that I'm not having any issues at all with SR3 and vanir 1/20 on my toroplus. I'm on dalvik because of openpdroid and Xposed. Hyper, some undervolting. Oh, and I've been using that nexus 4 qualcomm dalvik patch that was mentioned in the vanir thread a couple of days ago.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
yup that was the first thing I reverted ;) its the cause for the lightswitch cpu , i thing the cpufreq commits I used also may be giving some problems , so for now im puling them in my public kernel ,

I dont think the graphite and linktime optimizer flags are the cause but theyll be next if I suspect them of maliciousness , im just trying to rule out stuff thats causing you guys problems
[Samsung Galaxy Nexus] Vekhez:
Idk about 4.. But it has HALO, Immersive (enable expanded desktop) and theme chooser (under cyanfox)
[Samsung Galaxy Nexus] Hetalk:
And, carbon doesn't have Halo, but has lockscreen notifs with active display.

Choice is yours [MENTION=2853378]Nephilim[/MENTION] :D
[Samsung Galaxy Nexus] Vekhez:
Yeah, idk what lock screen notifications is.. I just use Knock2+ anyway, gives me Active notifications. But better.
[Samsung Galaxy Nexus] fracama87:
Is out new beanstalk... Didn't tried this version so don't know about features.

Still resist on cm-remix ( it's almost acceptable now... I've few time to change again, so I'm waiting a stable rom to keep.)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Commencing F5 finger stance, preparing for F5.....

.....F5'ing the f*ck outta my keyboard has begun........... :p
[Samsung Galaxy Nexus] pattyboi:):
i broke the F5 key..xD
[Samsung Galaxy Nexus] bsmitty83:
SR-4 up in the OP

i fixed the cpu scaling and reverted some things to hopefully get rid of the freezes for you guys

hope it works
[Samsung Galaxy Nexus] Nephilim:
You're F5'ing the wrong webpage. ;)

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

I downloaded that sh*t before you even announced it lol, about to try it out right now with LiquidSmooth 1/20
[Samsung Galaxy Nexus] rockingwing:
can confirm, cpu scaling is definitely fixed :3 will have to see about freezes
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4608636]bsmitty83[/MENTION] ,just flashed sr4..did you intentionally remove govs this time? xD
[Samsung Galaxy Nexus] bsmitty83:
I think just hotplug and one other but yea :D
[Samsung Galaxy Nexus] büscher:
Haha, just wanted to give a reply to you guys and my phone froze, had to do a battery pull.

[MENTION=4544860]osm0sis[/MENTION]: I always delete the 3 scripts and do a immediate reboot. I just use the scripta delivered with the rom (some efs, selinux and userinit scripts) and my slightly modified nephs-settings init.d script

[MENTION=4337538]Kewyang[/MENTION]: well, I had 4 freezes today, but I accuse this storage bug I experience because these freezes always happen to me if I switch apps (sometimes these are only micro freezes from 1 to 3 seconds with a following systemui reboot)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION]

Could you add intelliplug and intelliactive to your kernel? :)

Also i think RAM reclaim does matter. I notice more available memory in daily using in compare to stock 693MB.
[Samsung Galaxy Nexus] osm0sis:
Haha okay then my suggestion is to try it with the scripts and see if it improves or worsens the score for you. ;)
[Samsung Galaxy Nexus] gohamstergo:
catch up the last few pages. overnight the thread became /r/gonemild X_X
[Samsung Galaxy Nexus] osm0sis:
Haha yeah we leave it for like 12h and it gets a little wild. :p
[Samsung Galaxy Nexus] poo706:
Since I can't upvote here, have a thanks.

[poo]
[Samsung Galaxy Nexus] gohamstergo:
haha right on.

And for those of you that don't like halo: http://xdaforums.com/showpost.php?p=50444030&postcount=2167
[Samsung Galaxy Nexus] Nephilim:
It's not dead, I've been on G+ about this for hours. They are just reinventing the app.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gohamstergo:
well, i think he meant the way Halo operates now, is dead. That it's going to change a lot, or something.
[Samsung Galaxy Nexus] metalspring:
Multiwindow will likely replace halo, similar to how immersive mode is supposed to replace expanded desktop+PIE
[Samsung Galaxy Nexus] Nephilim:
Well after testing the osm0sis 2/17 DirtyV I have noticed my benchmarks suffer severely in every section. I cannot even break 11000 for a score. I get 12800+ on the regular DirtyV 2/17.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Haha okay use regular DirtyV 2.17 with the init.d scripts and delete them one by one (reboot in between) and tell me which one(s) are f*cking it up for you please. ;)
[Samsung Galaxy Nexus] Nephilim:
I'll try that out once I let my battery charge and I get to my computer. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] büscher:
[MENTION=4544860]osm0sis[/MENTION]: The scripts interfere with some settings but they have no impact to database or storage as it seems.

[MENTION=2853378]Nephilim[/MENTION]: noop isn't the answer for my phone... the same results. either storage is "okay" and database f*cked or both results are around 500 points...

also with all this trouble I forgot to mention that I'm still not able to connect to my 5GHz wifi network (WPA2 - CCMP)

it worked with previous builds tough.
[Samsung Galaxy Nexus] Nephilim:
Now even after deleting the init.d scripts I am getting horrible (10100) results on Antutu with the regular DirtyV SR 2/17, what can I do to get it back to how it was before I flashed your version? Nothing is fixing this. Before flashing your new kernel my scores never went below 12500+ now 10100 is the highest my device reaches. Cpu integer is horrible, so is ram and I/O. all of them are about 200 to 400 points below what they should be.
[Samsung Galaxy Nexus] osm0sis:
By contrast, I get better scores with the latest DirtyV-RSR 2.17 osmod vs. DirtyV-RSR 2.17 with the bundled init.d scripts removed.

12671 vs. 12407 after fresh reboots and waiting 10 min for the device to cool reasonably and ensuring it had the same amount of free RAM before starting AnTuTu. Best scores I've ever seen on my setup even.

Virtually the same scores, but ~300 more for Storage I/O on osmod. :)

---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------

Flashing 2.17 from the OP already has it back to what it was before. Nothing I do is permanent because it's done in the ramdisk. It's all you, I'm sorry to say. :(
[Samsung Galaxy Nexus] Nephilim:
I'll try flashing your kernel once more and then just deleting the scripts, reboot and see what I get.

This time I deleted the scripts and then reflashed the regular 2/17 SR.
[Samsung Galaxy Nexus] ASHURiCAN:
Where is the init.d located ?
[Samsung Galaxy Nexus] vfmmeo:
You can find the init.d directory under /system/etc.

The /etc that appears on the root directory is a symlink.
[Samsung Galaxy Nexus] osm0sis:
Yeah only the one from the OP comes with init.d scripts, osmod has it all self-contained in the ramdisk. :good:

I updated my last post with screenshots and more details. :)
[Samsung Galaxy Nexus] ASHURiCAN:
Thx, can I delete this directory?
[Samsung Galaxy Nexus] Nephilim:
It's the damn Trickstermod app, after I wiped tricksters data and rebooted I did another benchmark. The device was super hot from all the other benchmarks and rebooting but I got a 12325, seriously annoying that I have to wipe trickster to get my settings to properly work again. I don't mind adding them in manually but I paid for the donate version so I can simply reboot and select the profile "nephilim" in all areas to save time. Every damn time I have to go to settings/app/trickstermod and wipe data I lose those profiles and have to spend 15 minutes adding them again.

Oh well, at least problem is solved. :D

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

Yep, I used Root Explorer. :)
[Samsung Galaxy Nexus] gohamstergo:
def sounds like something worth emailing the dev about..?

personally, i always disable trickster boot functions, flash new kernel, go back to trickster, select profiles, reenable boot function. and everything seems fine for me. but then, i dont do benchmarks, i just judge by usage and it still seems as smooth to me.. iono
[Samsung Galaxy Nexus] Za_RO_Maniac:
So what version are you using now? [MENTION=4544860]osm0sis[/MENTION]'s or the one from OP ?
[Samsung Galaxy Nexus] ASHURiCAN:
What I mean, will it not interfere with my installation if I delete this directory? I'm with latest DirtyV-RSR + TricksterMod.
[Samsung Galaxy Nexus] Nephilim:
Hey osm0sis, could you take a look at this init.d script and tell me if it may be the reason why target_loads were stuck on 0, the only reason I ask is because now that I am using your modified 2/17 DirtyV SR I am trying to figure out if you found the solution or if removing this script allowed me to have target_loads set to 85 again.

https://drive.google.com/file/d/0B_HqOdvKZoQhcUt6eV9FQU9uWlU/edit?usp=sharing

---------- Post added at 03:27 PM ---------- Previous post was at 03:27 PM ----------

DO NOT

delete the directory, delete the scripts inside the folder. ;)
[Samsung Galaxy Nexus] ASHURiCAN:
Thx but look all the files I have in this directory, is it safe if I delete all the files ?
[Samsung Galaxy Nexus] osm0sis:
He can delete it if ours are the only scripts in it, the ramdisk script will just recreate it on the next boot. :)

I think I fixed it. I noticed Smitty modded uevent.rc and so I added a few more there and made sure everything matched, I also added chown system:system to the governor permission fixer in the ramdisk script as well to be safe.

Trickster sounds seriously f*cked lately, guys. I'd be pissed if I paid for it. Time to look into Synapse, I think.

---------- Post added at 05:37 PM ---------- Previous post was at 05:36 PM ----------

In your case no. Some are from your ROM. 875, 925 and 950 should be deleted.
[Samsung Galaxy Nexus] Nephilim:
So you gonna drop a revised osmod 2/17 SR?

Also, did you see my post on the last page about that init.d script I removed that came with the LiquidSmooth rom?

Btw, is G+ Communities Fcked for you guys or is it just me?
[Samsung Galaxy Nexus] aaron13:
Have you ever used Gs2kernelwipe Neph?

It removes old kernel files and init scripts. It can be normally used between using other kernels.
[Samsung Galaxy Nexus] osm0sis:
The fixes are in the one that's up now. :)

I'll see if I can figure out how Synapse works if [MENTION=4608636]bsmitty83[/MENTION] doesn't get to it first.
[Samsung Galaxy Nexus] Nephilim:
I'll check that out.

Unfortunately, it seems as though the problem is that when there are any major differences between kernel updates Trickstermod tries to hold onto old settings sometimes, which in turn totally fcks up performance and sometimes even leads to the overheating issue some people have posted about.
[Samsung Galaxy Nexus] osm0sis:
Looks harmless enough! Standard SELinux relabeling script from what I can tell. :good: :)

Yeah on grouper we even found having SetCPU and franco.Kernel updater installed at the same time, even with nothing set on boot in SetCPU caused overheating. Uninstalling SetCPU fixed it. So definitely only use one at a time to be safe and never touch your ROM's built-in one if you intend to use another.

It honestly sounds like Trickster has just gotten too complicated and out of control for the devs.
[Samsung Galaxy Nexus] Nephilim:
So then it's your osmod DirtyV SR that fixed the target_loads being stuck on 0, after flashing your updated kernel it's no longer suck for me and reads 85 like it should. ;)
[Samsung Galaxy Nexus] bsmitty83:
That's more your territory since AFAIK its all ramdisk changes , I've tried but it always comes up no UCI support . I gave up on it ATM .

You can open pull req any time osm0sis ;) , my ramdisk is in my kernel tree .
[Samsung Galaxy Nexus] Nephilim:
Well I am used to how it works and I am patient and confident that they will work it out. Plus, I paid for the damn thing lol.
[Samsung Galaxy Nexus] Grarak:
did you read the wiki of Synapse?

https://github.com/AndreiLux/Synapse/wiki

If you still cannot get it to work. Send me your ramdisk I will see what I can do.
[Samsung Galaxy Nexus] osm0sis:
Haha lots of files edited this time; I'll have to clone it locally to do a single commit pull request for you since Github only let's you edit 1 file per commit online.. Would you rather I do that or do you mind extracting from my latest zip and committing yourself (probably less work over all, though it's your work :p)?

---------- Post added at 05:57 PM ---------- Previous post was at 05:55 PM ----------

Will give it a read. Thanks buddy! :D
[Samsung Galaxy Nexus] bsmitty83:
ill commit it myself , no big deal :p

i also updated the op with the missing old versions , ill add metalsprings and your versions as well
[Samsung Galaxy Nexus] Nephilim:
After letting my device cool down my Antutu score is 12875 with the osmod 2/17 ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pagratios:
I have had 2 sudden reboots until now. I have uploaded some logs but there aren't last_ksmg
[Samsung Galaxy Nexus] vfmmeo:
Argh. I've just started to look on [MENTION=4443334]Grarak[/MENTION] 's ramdisk to try to implement some Synapse support on DirtyV in order to get some kind of "unified kernel control tool" for us...

I'm ever late everywhere. The history of my life... :banghead:
[Samsung Galaxy Nexus] metalspring:
Synapse is even worse for setting on boot than trickster IMO. I tried graraks kernel with synapse and almost every boot it would say settings not applied at boot for whatever reason
[Samsung Galaxy Nexus] Nephilim:
I've researched Synapse and from what I've read and reviewed I prefer to tough it out with Trickster. That's just me personally though.

Btw, we need to get your ass an avatar. I could put a few together if you like.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION]

I added Synapse in a CM11 ramdisk as a reference for you I pulled the files from [MENTION=4443334]Grarak[/MENTION] multiboot ramdisk

https://www.dropbox.com/sh/und20twja48plcx/RW_48uMsKJ
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] The Synapse folder in /res can be placed in /data and uci can go in /xbin symlinked to /data/Synapse/uci instead for AnyKernel
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] You probably want to use [MENTION=4443334]Grarak[/MENTION] Synapse fixes

https://github.com/RomSwitchers/RomSwitcher-tuna/tree/master/boot.img-ramdisk/res/synapse
[Samsung Galaxy Nexus] osm0sis:
Awesome! Thank you, as always, sir! You're unstoppable! :D

I'll give it a shot tomorrow!
[Samsung Galaxy Nexus] Culex316:
I don't know why but SmartReflex for 1.5Ghz + 1.5Ghz max speed and 350mhz min speed plus deadline scheduler and ondemandplus governor is a winning combo for me.

Quick performance and best battery life I've had with 1.5Ghz set as max speed.
[Samsung Galaxy Nexus] garyngkt:
Somehow RSR 10/2 seems less prob for me with Neph's settings :laugh:.

Tried 15/2, 17/2 & 17/2_osmod got freeze....
[Samsung Galaxy Nexus] bsmitty83:
Got a new SmittyV build compiling . .

I think I fixed target loads finally in the code , added a new interactive tunable "sampling down factor" , seems to be butter , ran 13300 antutu for you benchmark guys on daily settings .

I'll put it up soon .
[Samsung Galaxy Nexus] pattyboi:):
hey smitty,since your kernel is forked from the vanir one,it includes all of their last updates right? cause they added a bunch of goodies yesterday or the day before (cant remember exactly)
[Samsung Galaxy Nexus] lazydognet:
Look forward to new Smitty build.... Pardon the noob question and getting a little off topic but is there an easy way to backup your launcher shortcuts (so I can easily restore my shortcuts and groups to a new ROM build).

Thanks,

LDN
[Samsung Galaxy Nexus] ASHURiCAN:
Exactly same for me! I even had a lot of data loss.
[Samsung Galaxy Nexus] bsmitty83:
No , you have to update yourself , I don't pull from their git unless its a cherry-pick .
[Samsung Galaxy Nexus] pattyboi:):
OK bud.(:
[Samsung Galaxy Nexus] metalspring:
Actually, it looks like smitty already has at least 95% of what they commited, if not all of it (maybe they checked HIS github for things to add lol)
[Samsung Galaxy Nexus] pattyboi:):
Hm,good point,I hadn't checked his git at least for a couple hours,I was mostly talking about fauxs intelliplug and intelliactive stuff lol,my bad :p & nice avatar!!
[Samsung Galaxy Nexus] cujo6801:
Yessir used titanium backup backup your launcher then when you restore it you can easily add back everything

Tibu will remember everything

sent from the DOG pound
[Samsung Galaxy Nexus] metalspring:
Some of the things they added that you dont have might be useful though

Fixing a memory leak- cfg80211: Fix memory leak

Net tcp performance boost- net: loopback: set default mtu to 64K

removing useless junk- mm, vmalloc: remove useless variable in vmap_block

memory performance enhancement- mm, vmalloc: use well-defined find_last_bit() func

more performance enhancements- readahead: make context readahead more conservative

block: Reserve only one queue tag for sync IO if only 3 tags are available

cpufreq: Optimize cpufreq_frequency_table_verify()

And an improvement for hotplugging- CPU hotplug, debug: detect imbalance between get_online_cpus() and put_online_cpus()
[Samsung Galaxy Nexus] bsmitty83:
try SmittyV out , Op updated

hope it works for everone
[Samsung Galaxy Nexus] namtombout:
Thanks.

Will anykernel format ever come back?

And does anyone know if I can disable logging or if only compilers can?
[Samsung Galaxy Nexus] bsmitty83:
Not sure , haven't thought about it to be honest lol
[Samsung Galaxy Nexus] namtombout:
All good. I'm on 4.3 and wanted to check out your latest but I'll manage
[Samsung Galaxy Nexus] Nephilim:
Guys, anyone using my settings set sampling_down_factor to 1. I'll update my thread when I get to my PC, I can't be fcked with to do it right now, busy playing Castlevania.

Smitty, so far the new SmittyV has yielded good results! Great work as usual!!! ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I got you covered , gimme 5 min :thumbup:

https://www.dropbox.com/s/xzw6u9of16blg2h/SmittyV-Anykernel-2.20.zip
[Samsung Galaxy Nexus] milojoseph:
Just about to aks u that.. what about boostplusduration
[Samsung Galaxy Nexus] Nephilim:
Just got a 13017 on antutu! Highest score I've gotten since DirtyV was rebuilt from scratch. SmittyV 2/20 is fcking amazing Smitty!!!!

I'll post my benchmark details tomorrow, they're looking really good!!

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 10:49 PM ---------- Previous post was at 10:47 PM ----------

That is already posted on my thread, 750000.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
[MENTION=4608636]bsmitty83[/MENTION], would you mind if I post a version of the new build you did of smittyv today but with all the updates vanir added, including intelliplug and intellidemand (which seems oddly similar to dyninteractive?).

It would be just to see if everyone thinks those commits are worth adding or not
[Samsung Galaxy Nexus] osm0sis:
That would make the touch boost 0.075 seconds. :confused:
[Samsung Galaxy Nexus] bsmitty83:
Never will I mind man , saves me the trouble of having to build them lol :thumbup:
[Samsung Galaxy Nexus] gohamstergo:
deleted
[Samsung Galaxy Nexus] ahmadairfan:
Intellidemand vs intelliactive (tried it on faux), which you prefer guys? Thanks :)
[Samsung Galaxy Nexus] metalspring:
Well here it is

SmittyV-RSR-2.20.14-vanir-test

Btw, their changes seem to add 2 more options in trickster under specific

Eco Mode and Intelli-plug (an in-kernel replacement for MPDecision)

I thought the gnex didnt have mpdecision?? Or maybe it acts like mpdecision for phones that dont actually have mpdecision?
[Samsung Galaxy Nexus] Nephilim:
My bad, 750000 ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Sounds like it tries to bring the lower latency kernel-side mpdecision replacements to devices that don't normally use it. That'll be interesting since the GN hates to hotplug. Haven't tried that yet, but I can safely report that intelliactive feels sluggish and choppy as hell. ;)
[Samsung Galaxy Nexus] pattyboi:):
I agree with inteeliactive being choppy,BUT,intelliplug is so far pretty decent,been running the gnex full steam with intelliplug on and I must say I'm inpressed with the fact there's been no lag or crashing yet:) I can't say much else yet lol,but IMO this is actually pretty sweet :D
[Samsung Galaxy Nexus] metalspring:
I think intelliactive and intelli-plug together creates sods, unless it was just a setting of mine? They both work with turning on/off CPU cores I believe so it would be like using multi core powersaving with a hotplug governor?
[Samsung Galaxy Nexus] osm0sis:
cho "0/1" > /sys/module/intelli_plug/parameters/intelli_plug_active
echo "0/1" > /sys/module/intelli_plug/parameters/eco_mode_active

Not sure if we'd want to use Eco mode since we are a two core device, or not for pretty much the same reason; we already are. Apparently both are already active by default on your build though!
[Samsung Galaxy Nexus] pattyboi:):
That's what I've found. As soon as I mixed them I got SOD then reboot (did it again just to check) so maybe they just conflict each other?

---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------

So using eco mode on a dual core essentially makes us a single core,right? (If I understood what I just read lol)
[Samsung Galaxy Nexus] metalspring:
The vanir commits are actually straight from faux kernel where he already has both eco mode and intelli-plug active

---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------

From what I see, one CPU core is off most of the time unless you really need it
[Samsung Galaxy Nexus] pattyboi:):
I thought it was just trickster f'ing up ,hmm that's interesting,weird part is it actually isnt that bad on performance from what I've seen
[Samsung Galaxy Nexus] büscher:
So I clearly have to change that in my init.d scripts...

Will update them today with new settings for 2/20

Sent from my Galaxy Nexus

---------- Post added at 08:38 AM ---------- Previous post was at 08:23 AM ----------

Just that someone mentioned it: latest smittyv breaks pgm

---------- Post added at 08:58 AM ---------- Previous post was at 08:38 AM ----------

sampling_down_factor is a multiplier for min_sample_time.

So setting it to 1 will do nothing imho...