yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] vfmmeo:
Strange: builded from source last version of Dirty (big mem). Applied neph settings via [MENTION=4315955]Nemed[/MENTION] init script (first version). Result:

All settings defined correctly. Only the target_loads issue, corrected through [MENTION=1143630]osmosis[/MENTION] solution. Freqs, gov, RAB... All OK.

BUT: seven hours after, with no reboots and no use (night time here) I've found max freq set to 1200 instead of 1400, target_loads set (and sticked) to 0, and the GPU OC set manually by me at 512 reverted.

I'm on latest omniMetal, and tricksterMOD has the "set kernel features on boot" disabled (and no reboot, anyway)

I don't know to think :confused: Can't be Rom issue 'cause with stock kernel (Dirty too) doesn't happen, and trickster is "disabled"
[Samsung Galaxy Nexus] Nemed:
[MENTION=3242935]lordofazeroth[/MENTION] yes it should

[MENTION=4197544]chongns[/MENTION] i think it's normal, i have interactive and ondemandplus (which is the one i use)

[MENTION=5073162]vfmmeo[/MENTION] use the latest script i posted. Anyway i noticed that the max freq doesn't stick, i'm investigating lol, regarding the GPU i don't know what to say, in my script there's noting regarding it :confused:
[Samsung Galaxy Nexus] Charmacas:
[MENTION=1143630]osmosis[/MENTION] could your ramdisk potentially cause reboots?

I ask because I used it and got occasional reboots all the time. After reverting the custom ramdisk I get no more reboots.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] vfmmeo:
Yes, I know that GPU OC isn't defined on these script. But the point is i've set to 512 via trickster, and seven hours after, the value is reverted to stock (with Maxfreq too). I'm not telling that is a problem related with your script. For any reason, the kernel reverts some tunables by its own, no matter how was set (trickster or init script)
[Samsung Galaxy Nexus] Nemed:
I fixed the max freq issue, it was set too early at boot.

Download

[MENTION=2288033]Charmacas[/MENTION] i had random reboots too :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] vfmmeo:
Little OT and flamer, but I need to say:

I've reading last post on Mpokang thread, and I was laughing seeing people looking for new benchmarks to claim how good that kernel is.

Kids, it remembers me a lot the Ubuntu hype thing 5/6 years ago.

/trollface
[Samsung Galaxy Nexus] chainrulez:
[MENTION=2288033]Charmacas[/MENTION] learnt so much from your Trickster Settings, thanks a lot ... :good: :laugh:
[Samsung Galaxy Nexus] vfmmeo:
Downloaded and tested. Works perfectly.

Let's see in seven hours lol.
[Samsung Galaxy Nexus] LibertyMonger:
Benchmarks mean jack-crap to me, performance and stability of my phone is all that matters. That tells me how good a kernel is. All you all do is look petty and pathetic with this nonsense. No one else cares. It's just a phone.
[Samsung Galaxy Nexus] bsmitty83:
OK so as far as the tunables not sticking or sticking , I'm just as confused as you guys are , but I'm gonna try some things and see if it works .

I'm definitely liking synapse app, I think I'm gonna try to support that as well since the ramdisk is gonna be there too .

Zram might affect battery alilttle but shouldn't be huge

Gonna try to refrain from messing with my note till I get some things in dirtyV ironed out
[Samsung Galaxy Nexus] osm0sis:
That's the other thing.. We used to include a custom power hal to avoid the max, etc getting reset after a screen off. That was until Franco added his own kernel-side touch boost implementation, so now it just gets disabled altogether.

Maybe [MENTION=4608636]bsmitty83[/MENTION] could cherry pick the touch boost and I could add the power hal disabler to the ramdisk.

Really weird. Rock solid for me.. Maybe your ROM didn't like the renice script? I'll remove it so we can see.
[Samsung Galaxy Nexus] büscher:
Wow that was a marathon now... 24h not on xda and 15 pages to read.

I also have wifi issues at home on wpa2. It connects but any time it disconnects my phone forgets the wpa key...

I have two wifis set up a t home with different hardware and it is the same on both...?

[MENTION=4315955]Nemed[/MENTION]: Now the work was done twice ;)
[Samsung Galaxy Nexus] vfmmeo:
Don't misunderstand my post. That you criticize is exactly what I say THEY do. Here we talk about performance, and sometimes there are benchmarks too. But the thread is focused in the kernel development.

Yeah, and while the old hyper-distro-war lasted we only talked about computers ... ;)
[Samsung Galaxy Nexus] osm0sis:
You've got to fix your target loads line still. ;) Can't be 0.

Edit: also you guys should just fix all the files at once:

chmod 664 /sys/devices/system/cpu/cpufreq/interactive/*
[Samsung Galaxy Nexus] büscher:
Thx for mentioning, fixed.
[Samsung Galaxy Nexus] Nemed:
Is this a problem? lol
[Samsung Galaxy Nexus] büscher:
absolutely not ;)
[Samsung Galaxy Nexus] Nephilim:
Same here, been running your ramdisk version of DirtyV SR since last night and not a single hiccup. If anything it's running smoother slightly.

Also, I want to point out that I have not had an issue ever with any settings sticking via Trickster Mod outside of certain Governor Control Tunables. Cpu Frequencies and Gpu Frequencies have always stuck when set.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
The "smoother" is likely also the renice script. :p

To keep or not to keep... ;)
[Samsung Galaxy Nexus] büscher:
another Question I have:

When I plug in my phone my CPU is always at 10%:

- Surfaceflinger at 6% permanent

- and SystemUI 4% permanent

Does anyone know why?

As soon as I plug it out the load goes down to 1% (caused by top)

(No biggie here just curious)

Edit: Nevermind: Figured out it was the Circle-Battery animation
[Samsung Galaxy Nexus] Nephilim:
I've just reported that thread for a second time. I feel the fanboyism has become very unhealthy for this site. Some of these users are not only still bashing basically all other kernels, they are now claiming that because they are using a new type of benchmark to test ramspeed it simply cannot be faked. Not only that but one of the most recent posters over their spent his time bashing me and then saying something like "if I were mpokwths I would sit in the corner and laugh" in reference to him not sharing his v10 code, then he went on to say something like "only we will get this holy grail scores". This is simply uncalled for, that thread has a few awesome helpful users but mainly now it's a bunch of self-righteous fanboys bragging and bashing everyone else.

I like how here just like on the old AK thread. Such a calm, relaxing place.

Besides me, my drama and my arrogant mightier than thou attitude of course. ;)
[Samsung Galaxy Nexus] michierusama:
Report and move on. Good.
[Samsung Galaxy Nexus] TheMan0790:
Liked your comment for everything up to the last line. I have never seen you as an arrogant "mightier than thou" type person on these threads. And I think it's other users who ensure the drama we have seen (so, not being caused by you).

Break me off a piece of that KitKat ROM!
[Samsung Galaxy Nexus] Nephilim:
Yep, I will no longer post over there but each time I see something rude being posted or something that condones violating rules I will report it.

---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------

The last line was meant obviously as sarcasm since this is what I have been referred to as over on the Mpokang Thread. ;)
[Samsung Galaxy Nexus] inmanster:
I also have had issues the last week with my Max Frequency not sticking. I'd set it at 1400000 in Trickster and after waking the screen it would be at 1200000. Happened with several versions of the kernel and across 3 ROMS (Shiny ROM, Liquid Smooth and omniMetal). I thought it may have been due to have Trickster, FKU and Performance Control all installed but after deleting two and only having one app it still happened. The only thing that stopped it was to use the Frequency Lock feature in Trickster.
[Samsung Galaxy Nexus] juju2011:
Ramdisk sr won't flash for me :(
[Samsung Galaxy Nexus] vfmmeo:
So, the joy and the fun of reading that thread is about to end? Oooh :P

It's funny to see all those kids playing with a black box while here we can see how the box is made.
[Samsung Galaxy Nexus] osm0sis:
Too vague. Explain?

Download again and use the latest CWM or TWRP. I tested with both and it worked fine.
[Samsung Galaxy Nexus] juju2011:
Have latest twrp and flashed with ROM on clean install put phone down and came back and only ROM was flashed kernel errors out
[Samsung Galaxy Nexus] Nephilim:
Actually, not "about to", it's over, thread has been closed.

And I concur, I enjoy seeing a kernel grow, not just testing it on any benchmark I can just to prove it's better than others when it doesn't even have active development anymore.
[Samsung Galaxy Nexus] osm0sis:
Still too vague! Come on, man. What was the error?
[Samsung Galaxy Nexus] fracama87:
Same here :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Hey, on a different subject. I just flashed the new 2/12 LiquidSmooth build uploaded a little while ago, going to see if the fresh flash along with your ramdisk version of DirtyV 2/10 SR fixes the read-only for SmartAssV2 Tunables.

Crossin' My Fingers. :)
[Samsung Galaxy Nexus] juju2011:
Forget what it said but it flashed now re-downloaded the kernel to a diff directory and compared two and first one was a bad download my bad :)
[Samsung Galaxy Nexus] Shambola:
...and maybe also tethering/hotspot issue?
[Samsung Galaxy Nexus] juju2011:
:/ hotspots work fine for me
[Samsung Galaxy Nexus] büscher:
Hmm... yes. on the phone it seems like the hotspotis working but I cant find the SSID, neither with my Tab nor with my notebook.
[Samsung Galaxy Nexus] Shambola:
Mhh, on my Gnex doesn't start even... (and, of course, right today I have a fault on the ADSL :eek:)
[Samsung Galaxy Nexus] peterlemonjello:
Hotspot is borked on my GNex CM11 M3 with DirtyV-SR-2.10.14. It tries to start but sits there with a status of "Turning hotspot on..."
[Samsung Galaxy Nexus] osm0sis:
Alright. I just whipped something up to fix governor tunable permission woes forever:

# fix governor permissions on older underlying ramdisks
governor=reset;
while sleep 1; do
current=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor`;
if [ $governor != $current ]; then
governor=$current;
for i in /sys/devices/system/cpu/cpufreq/*; do
chmod 666 $i/*;
done;
fi;
done&

Of course if there is something weird with the source or ROM locking them down (or the app reading them) we may still have some troubles, but this at least will take the permissions being wrong out of the picture.
[Samsung Galaxy Nexus] Nephilim:
Hopefully this works. I still couldn't get SmartAssV2 Tunables to stick after a fresh install of the kernel and liquidsmooth rom. :)
[Samsung Galaxy Nexus] vfmmeo:
Hello, [MENTION=4315955]Nemed[/MENTION]

I find a little typo on your script. On "General I/O Tunables, where says:

echo 2 > /sys/block/mmcblk0/queue/tq_affinity

Must be:

echo 2 > /sys/block/mmcblk0/queue/rq_affinity

Notice the "rq_affinity" instead the original "tq_affinity"
[Samsung Galaxy Nexus] mangusZen:
Little OT and flamer, but I need to say:

This is stupid and uncalled for.

I by no means have interest in mpokang kernel, nor I am affiliated in something, but I read a lot of trash talk here and there, that had nothing to do with the purpose of the forum.

Is it so hard for you people ignore what you dont like, instead of bashing someone else work or opinions?

This is really kiddish And, for the rights you might have, this attitude puts you on the wrong side with intolerants and bigots.

I really hope some mods come to clean some ****, and people start to be more positive and tollerant ( about that topic, I mean)
[Samsung Galaxy Nexus] gohamstergo:
and yet you decided to post and not ignore it? X_X but then, so did I. but I will not post on the topic further. Hopefully *everyone* will do the same, not reply to this, and let it alllllllll gooooooo. happy happy joy joy :good:

now, back on topic:

still hoping for an explanation of what kswap0 is doing. ;)
[Samsung Galaxy Nexus] Sik-1:
This is on Franco, jus to compare with others, plz do share

If I didn't have this silly network bug I'm sure I would have atleast 10% more battery, if anyone knows how to get around this telephony bug Help!!!!!
[Samsung Galaxy Nexus] gohamstergo:
why are your screenshots all messed up? thats odd in itself... and worst case, you could turn off your mobile data while on wifi, for now.

edit: darn, i got quoted before I fixed all my spelling mistakes X_X
[Samsung Galaxy Nexus] Sik-1:
Its a problem of toroplus users, don't hate lol
[Samsung Galaxy Nexus] Nephilim:
Vfmmeo's comment may have been a little snide but I stand by all of my comments there and here, none were in the vain of being a fanboy and I certainly was not acting "arrogant" or "mightier than thou" when posting them. (both quotes directed towards me on a post in the mpokang thread). If you look at the thanks on my comments, even developers agree that the thread was going on a downward spiral. That's all I have to say. No offense meant to you good sir. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Fellow t+ user here. Does anyone know why this is just happening to us and not toro or maguro? Shouldn't all of our ROMs be the same, other than radio-related stuff?

[poo]
[Samsung Galaxy Nexus] osm0sis:
OK back on topic, people! :p

New DirtyV-SR 2.10 Ramdisk and AnyKernel are up on my Dev-Host: http://d-h.st/users/osm0sis/DirtyV/

Added sysctl.conf disabling, power.tuna.so HAL disabling (in anticipation of Smitty adding Franco's touchboost ;)) and governor permission fixer, all to try and cut down on ROM interference, and hopefully make things work more as expected/consistently for everyone.

Only things I've left out that are in f.K's ramdisk are the fstab mount options (in fstab.tuna) and some other tweaks which could go in dvbootscript.sh: lease time, entropy, randomize_va_space, queue tweaks and sysfs remounts, as follows.

# decrease fs lease time
echo 10 > /proc/sys/fs/lease-break-time;

# tweak for slightly larger kernel entropy pool
echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

# kernel tweaks
echo 0 > /proc/sys/kernel/randomize_va_space;

# general queue tweaks
for i in /sys/block/*/queue; do
echo 512 > $i/nr_requests;
echo 512 > $i/read_ahead_kb;
echo 2 > $i/rq_affinity;
echo 0 > $i/nomerges;
echo 0 > $i/add_random;
echo 0 > $i/rotational;
done;

# remount sysfs+sdcard with noatime,nodiratime since that's all they accept
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /;
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /proc;
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /sys;
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /sys/kernel/debug;
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /mnt/shell/emulated;
for i in /storage/emulated/*; do
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto $i;
$bb mount -o remount,nosuid,nodev,noatime,nodiratime -t auto $i/Android/obb;
done;

[MENTION=4608636]bsmitty83[/MENTION] can test and decide if he wants to use any of those. :)
[Samsung Galaxy Nexus] Sik-1:
I usually flash your init.d scripts on every ROM regardless of kernel lol, I'll b updating asap, thanks

---------- Post added at 01:15 PM ---------- Previous post was at 01:15 PM ----------

Bro I have no clue and its quite upsetting ??
[Samsung Galaxy Nexus] Nephilim:
I'm all over this like a fat chick on cake!
[Samsung Galaxy Nexus] osm0sis:
That's something they fixed on the ROM side for most KitKat ROMs awhile back. I guess your maintainers need to sync their repos? :p
[Samsung Galaxy Nexus] Sik-1:
Well I'm on official cm so go figure lol, no matter how many clean flashes
[Samsung Galaxy Nexus] poo706:
I would have thought so too, but an awful lot of time has passed for it to be such a simple explanation. I've always had the problem with Vanir 4.4, which is all I've run for the last couple of months. Can any toroplus users confirm that they don't have graphical glitching problems on a 4.4 ROM that's not Vanir?

[poo]
[Samsung Galaxy Nexus] Punkiderma:
I have a question about the ramdisk version, I've searched the thread but I can't find a proper answer: now I'm on standard DirtyV ;flashing your ramdisk version would make some of my apps disappear? I have to clean flash?

I remember once I flashed Fancy kernel, coming from ASKP, and some of my apps disappeared, but not uninstalled. Flashing ASKP again bringed them back.

Also, having a dedicated ramdisk means only that all values can be tweaked on every Rom you install the kernel on, or there are also other improvements?

Thank you!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
"Other improvements" are what I outlined in my post. Ramdisks don't/shouldn't touch apps, not sure what your experience with Fancy was about. :)
[Samsung Galaxy Nexus] GilGameshn1:
Don't know related or not but my Google Play disappeared after installing ramdisk version . I am on OmniMetal with your first ramdisk . did not check your last version . thanks man .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] qtoo941:
You must have done something wrong ;o Currently using latest OmniMetal with 2/10 DirtyV SR with osm0sis's ramdisk and i don't have such a issue.
[Samsung Galaxy Nexus] Punkiderma:
Thanks, now I've got only one (very stupid) question before flashing: to correctly flash your kernel with your ramdisk, I need to flash anykernel zip + ramdisk zip or the ramdisk zip has already everything inside?
[Samsung Galaxy Nexus] Nephilim:
No issues on LiquidSmooth either. Unfortunately smartassV2 tunables still won't stick. Going to hit up Sean Hoyt over in the LiquidSmooth G+ and see if he can do something to fix that. :)

At least then I'll be able to do some testing on the tunables. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Do you happen to know where Franco's touchboost is in his git? I'm looking for the color control fix now its an older commit so I gotta dig back , but hopefully this weekend I can get some real time to work on this .

Thanks again for everyone help and testing and input , its why this thread is great , I can step away for a day and see others helping others . by no means is this just "my" kernel anymore , its everyone's .

Keep up the good work guys .
[Samsung Galaxy Nexus] Nephilim:
Same attitude I have with the G+, I created it but it's evolution made it belong to the whole community. :)

Thanks for all your dedication here smitty! :D

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] GilGameshn1:
This :thumbup::thumbup::D

Sent From My Nexus Prime
[Samsung Galaxy Nexus] vfmmeo:
Same here with a build of the BigMem variant running on OmniMetal 02-09-2014 and try to setup with TricksterMOD.

Let's see what happen if i try with some nasty script...
[Samsung Galaxy Nexus] bsmitty83:
OK cool , I'm still keeping an eye on it . ....;)
[Samsung Galaxy Nexus] Vekhez:
Could you try merging [MENTION=5310723]Amperific[/MENTION]s Hotplugging System?
[Samsung Galaxy Nexus] Nephilim:
I've come to the conclusion after lots and lots of testing that hotplug governors very rarely play nice with the Gnex cpu. I still stand by my belief that the best course of action in the hotplug arena is something like AK's custom Interactive governor, which turned off cpu01 once the devices screen went off but worked pretty much like InteractiveX otherwise. It was killer for battery life but did not cause all the issues hotplug governors did by shutting down a cpu while the device was awake.
[Samsung Galaxy Nexus] bsmitty83:
I just never saw the benefit . your screen draws the most power , if its on , its better to have all available cpu cores to do work as efficiently as possible , why do you want to turn your phone into a single core while screen is on . hotplugged govs are OK with me cause its all idle time , screen off , anyways .

Plus Amps looking like he's gonna put an update out anyways .....
[Samsung Galaxy Nexus] Blackcrx:
I agree with both of you guys. Every time I try to use a hotplug governor it ends up causing lag. Now I just use the non hotplug Governors and just charge the phone as needed.

But on my note 2, hotplug Governors worked great. But them again that's quad core.
[Samsung Galaxy Nexus] Vekhez:
That's the thing... Amps hotplug was made for the GNex. Like in ASKP kernel.

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

Smitty?! What's with getting rid of all the TCP Controllers.

Never had I had so much lag with Vegas..
[Samsung Galaxy Nexus] Nephilim:
Reading is fundamental my friend, he forgot to add them to v3, they'll be back. ;)
[Samsung Galaxy Nexus] sd3993:
I've been using hotplug with OC set to 1.5GHz and MPU undervolted by 50mV. So far no problems at all!
[Samsung Galaxy Nexus] schnob:
I'm just chiming in to give some more praise. With Nephilim's settings (of course) I'm getting some pretty great battery life along with silky smooth performance.

I do get freezes with my keyboard every once in a while, but they're no biggie.
[Samsung Galaxy Nexus] Vekhez:
Read through... Must have skipped over that :P

Still getting some crazy weird freezes with the kernel. Specifically I find in Hangouts.
[Samsung Galaxy Nexus] cmoG530:
Same here. I'd get freezes with just about everything, about every 5-15min, causing many apps to FC and it didn't matter what I did to try and remedy it. Some kernels just don't vibe with certain devices.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
[MENTION=2853378]Nephilim[/MENTION] How is it going with ART on vanir and dirty V,

I am already having some minute freezes on dalvik, thats why asking you,

P.S. my settings are mostly identical to what you posted over here earlier...
[Samsung Galaxy Nexus] Nephilim:
Art is great, unfortunately Vanir really isnt lately. I've been stuck on 1/18 for a few days now because nothing after that wants to properly work. I'm not the only one either.

Instead of the keyboard freezing and recent menu lag im now just getting random freezes that last between 5 and 30 seconds. A couple times I thought I had an SOD and right when I was going to battery pull it snapped out of it and worked again. Its still in its early stages though and it keeps getting better with every new build. V3 is super fast and smooth. Really all we need is a cure for the random freezes. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] mikesh0x7:
Good job smitty. The kernel is perfect.

Anyway, I was having problems too, but then I did a clean install of the latest AOKP nightly, and then installed DirtyV SR3.

Everything works fine now
[Samsung Galaxy Nexus] Vekhez:
"The kernel was perfect. I am having these problems" lol.
[Samsung Galaxy Nexus] bsmitty83:
........:p

Maybe I'll flash a couple different ROMs and see if have issues on any other ROM.
[Samsung Galaxy Nexus] Nemed:
I'm testing sr3 and it seems to be snappier and smoother than the previous versions. I'm facing less freezes and fcs so far, i'm also using ondemandplus and it seems to solve (not totally) the wakeup delay.
[Samsung Galaxy Nexus] bsmitty83:
Do you guys have lockscreen sound lock/unlock on ? I don't ever use it so maybe that's causing issues with wake up .
[Samsung Galaxy Nexus] Nemed:
Nope :/
[Samsung Galaxy Nexus] irland2bite:
I still stuck with Vanir 1/18, use your latest SR2, adjust it with your custom sett, I got 97 Apps, ART on, got score 13083 antutu, so far (nearly 28 hours), everything is awesome, both battery life and performance. Once again, thanks Mr. Smitty :)

Note: I tested all the apps, no FC n SOD.
[Samsung Galaxy Nexus] Nemed:
Thanks mate, i just fixed it :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk