yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] milojoseph:
Interactive

Interactive is the opposite of Conservative; it quickly ramps up to the maximum allowed frequency, then slowly drops the frequency once no longer under load.

: Faster to ramp up and down than Conservative means a snappier response from the device.: CPU will run quickly for a few moments after it is no longer needed to do so, resulting in longer periods of higher power consumption and heat generation.

Yup maybe its the cause of my phone being hot
[Samsung Galaxy Nexus] Ashtrix:
That's Dynamic Fsync, Asychronous when screen on (i.e Fsync off ) and Synchronous when off (i.e Fysnc on). Only issue with this version of Fsync is, when ur phone crashes while screen on you maylose your data (System/ROM partition gets corrupted, Happened to me while my nexus was using Dynamic Fsync with OC.) More info on Fsync.
[Samsung Galaxy Nexus] redj12:
Seems be crazy but I am back on CNA 3.6 based on android 4.1.1. So my crazy question is : Can I flash Dirty kernel ?

Envoyé depuis mon Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
DirtyV is what now my gnex wants....
[Samsung Galaxy Nexus] garyngkt:
Every build had ramdisk now? Sorry if I missed earlier discussions
[Samsung Galaxy Nexus] schuessm:
Hello,

guys what ROM you are using with what version of DirtyV-kernel. Can we make a survey on this thread? And what are your battery time with your combination and what OST do yoiu have

Thank you for answers!
[Samsung Galaxy Nexus] tFrost:
Just flashed 2/15 Dirty Vanir (my interpretation of Vanir + Dirty V)

And IT IS FLYING.. seriously, how do I catch it again :P
[Samsung Galaxy Nexus] juju2011:
I'm on carbon unofficial 01/14
[Samsung Galaxy Nexus] aosp:
Check my last post
[Samsung Galaxy Nexus] bsmitty83:
I've used googles snappy compression / decompression for a long time I never added it back to this kernel , but I might .... I might try lzo too
[Samsung Galaxy Nexus] Nephilim:
Hey Smitty, great advice on logcat extreme, I love how I can just send the log to my Drive account.

Now onto the log, My three issues are

1. Still get SOD's during overnight charge, I rebooted, took the phone off the charger and it sat no problem for 5+ hours with no SOD, only when on the charger for extended periods of time.

2. Still get occasional freezing, none in recents menu or keyboard anymore but I get it randomly while using my device

3. MOST IMPORTANT, My device is running nonstop at 100% cpu, if I reboot it goes back to normal but then within 20 minutes it's stuck at 100% cpu again, I've tried 4 different cpu monitoring apps and none really help, I've come to the conclusion it's

system

and

android system

that seem to be the culprit but nothing I try besides a reboot fixes the problem, and that is only temporary.

Anyway, here's the logcat:

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

"11382 11382 E auditd : Failed on audit_set_pid with error: Protocol not supported" seems to be the most frequent occurance.
[Samsung Galaxy Nexus] aosp:
This ain't compression dude check the site and the below repo lol

https://github.com/robustUTEP
[Samsung Galaxy Nexus] bsmitty83:
Um not sure why CPU is pegged [MENTION=1412615]100%[/MENTION] , but I'll look into it , the audit in logs is spam ,I've been trying to get it out but it seems to be a kk thing

I looked at it and am trying to figure out what I'm looking at , the build instructions are how to build cm . im at work so I'm looking on my phone , but when I get home I'll look harder
[Samsung Galaxy Nexus] aosp:
[MENTION=2853378]Nephilim[/MENTION] [MENTION=2581599]FuZZ__[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4328678]metalspring[/MENTION] [MENTION=2999829]PlayfulGod[/MENTION] [MENTION=1922147]burstlam[/MENTION] [MENTION=2765426]styr[/MENTION] [MENTION=4790322]kufikugel[/MENTION] [MENTION=2601134]kejar31[/MENTION] [MENTION=4112553]dhacker29[/MENTION]

What you guys think about?

Summary

Baseline policies

Limit Heap Growth

Baseline heuristics are conservative based upon preset constantsAlways execute garbage collection (GC) upon heap exhaustion, even if GC has recently completed.

Causes frequent heap exhaustion and*frequent low-yield GC that consume energy and can cause interface pauses

Background GC scheduling

Baseline heuristic to trigger background GC is a fixed threshold

Threshold does not take into account fragmentation or program behavior

Our experiments indicate that this constant threshold is too low for many high-value apps.Snappy Android's "adaptive" policies

What they do

Limit GC frequency*

Adaptively compute low-memory threshold that triggers background GC*

Trust our policies and grow the heap upon allocation failure without delaying for an additional GC*

What they achieve

Few or no pauses due to garbage collection

Acceptable heap sizes

Lower energy consumption

"Snappy" version of Android with Adaptive GC Policies - Robust Autonomic Systems - http://goo.gl/pyaqJq

Building Snappy Android for Galaxy Nexus - Robust Autonomic Systems - http://goo.gl/fWneQp
[Samsung Galaxy Nexus] Nephilim:
Thanks man, I'm going to try a fresh install of Vanir 1/20 with DirtyV v3 and if everything boots nice I'll get another log for you to compare with this one. Maybe that will help. :)
[Samsung Galaxy Nexus] FuZZ__:
actually 'not stutter at all' to me but yeah, maybe?? :eek:
[Samsung Galaxy Nexus] Nephilim:
Okay so super strange thing. I plugged my device into my PC and the cpu usage dropped back to normal. WTF? Very odd.
[Samsung Galaxy Nexus] Blackcrx:
Does the sod only occur on the charger? Maybe it's time to try a different or new charger.

So far for me v3 is flawless (except for the interactive screen wake up lag)

Currently on dyninteractive with custom settings. No sod on charger (charged twice since flashing v3). Got a couple of lags but ppl have been reporting it in the slim thread while using different kernels also. So the lag might be ROM related and not kernel related.
[Samsung Galaxy Nexus] rockingwing:
So, after my clean install of VANIR 01/20 and SRv3 I have had way less freezes, no SOD, recents lag is gone, keyboard lag is gone as well. Just some random freezes at random times. Caused to crash Falcon Pro and Talon earlier today but else it's going really fine. Running stock settings, flashed it and haven't changed any kernel settings yet =) No Delay on screen-on either :)
[Samsung Galaxy Nexus] Blackcrx:
Interactive governor?

Let the phone deep sleep a bit and try it again.

I've noticed that whenever you flash a new kernel or ROM and CPU stays active for a whole
[Samsung Galaxy Nexus] rockingwing:
im on interactive governer, yes.

I also have the lockscreen notifications in Vanir enabled, maybe that helps as well.

//edit: [MENTION=2853378]Nephilim[/MENTION]: sent a request to join your G+ group ;)
[Samsung Galaxy Nexus] pattyboi:):
well since i haz no school today (thank god for mother natures dandruff falling lol) ill try clean installs on every rom i can, (CM,FML-omni,liquid,etc,etc) and post some logs up,if anyone needs anything specific tested just holla at a brotha lol
[Samsung Galaxy Nexus] klobkelosh:
The good old days of kernel dev are back on gnex. Thank you smitty!

Just reporting in, dirty v sr 3 running on official cm11 nightly, stock settings except fsync off, dyninteractive, and gpu set to 384. Not a single lag, freeze, hiccup, sod. Nothing.
[Samsung Galaxy Nexus] Nephilim:
It's not the charger, I get no SOD's using Mpokang SuperRam. This is not a big deal though because I am in the process of setting everything up after a clean install of Vanir 1/20 along with DirtyV v3, everything seems to be running perfect and I've had no lag yet. I'm hoping I just had some residual crap leftover from dirty flashing between different kernels and rom updates that was causing this. I did a full factory restore wipe (cache/dalvik/data) as well as I wiped (system). I have a good feeling my SOD's will be gone now. Gonna post an update of my findings once I'm done putting everything back to how I like it. :)
[Samsung Galaxy Nexus] cujo6801:
DHO posted 1/22 nightly but no toro yet.

I tried 1/20 clean like you but phone just would not settle down... Stay warm to hot temp.

sent from the DOG pound
[Samsung Galaxy Nexus] bsmitty83:
And I thought I was the only one ........:D
[Samsung Galaxy Nexus] juju2011:
Going try this on slimkat 2.4 will post back after my flashing
[Samsung Galaxy Nexus] memaro_maro:
please.. dont!!
[Samsung Galaxy Nexus] abhishek93:
read the OP....'R' stands for ramdisk..

Sent from my Galaxy Nexus

---------- Post added at 05:35 PM ---------- Previous post was at 04:48 PM ----------

facing problems with dirty v-sr...

YouTube crashes and I can't open camera app it says cannot connect to camera..

clean install with vanir..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xzilem:
Flash normal dirtyV, clear camera data, change camera setting to 720p, then flash again sr version.
[Samsung Galaxy Nexus] Kustaa:
Thanks, I know that, but my question was referred to smitty's post: "asynchronous fsync"...like for default, so that means new build has Fsync: off? No more Dynamic nor an option to manually set it?

Thanks!
[Samsung Galaxy Nexus] schuessm:
And what settings you are using with dirtyV?
[Samsung Galaxy Nexus] tFrost:
Nephilim's of course :P should have been called: Nephilim's Dirty Vanir :)
[Samsung Galaxy Nexus] Nephilim:
I have no issues with device overheating on Interactive. Do you play alot of games?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Za_RO_Maniac:
Launchers

Sorry for the OT (again xD) but I would really love to know if you guys, faithful Dirty V users, use other launchers besides the stock one to further enhance your Nexus's snappiness (if that is even possible after Dirty V + Nephi's touch :P )

Really enjoying my phone now with Dirty - V RSR + SlimKat RC3 + [MENTION=2853378]Nephilim[/MENTION] kernel settings ^.^

Really really good job guys ! :good: And TYVM
[Samsung Galaxy Nexus] Nephilim:
I prefer to stick with GNL, it's better than any third party launcher as far as speed and I love the hotword integration and Google Now being just a swipe away.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] scarcry:
I'm using launcher 3 where now is also just a swipe away,just a different direction lol

Sent from my LiquidSmooth KitKat maguro
[Samsung Galaxy Nexus] LibertyMonger:
I had issues with overheating on the versions before 2-14 with Neph's settings but not since 2-14. It would start heating up just from having the screen on. I have been running completely stable, the best my phone has ever ran. It's awesome cause I usually couldn't run these kinds of kernels with overclock and undervolt til now. No more freezes or reboots or overheating.
[Samsung Galaxy Nexus] swarlesbarkely:
That's the Google experience launcher not launcher 3
[Samsung Galaxy Nexus] Nephilim:
Now Google is calling it GNL (Google Now Launcher) instead of GEL (Google Experience Launcher). ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] cdfreak:
I thougt that you where using Nova Launcher Pro?
[Samsung Galaxy Nexus] aosp:
Try this repo

https://github.com/ASdev/android_img_repack_tools
[Samsung Galaxy Nexus] lazydognet:
This might be a noob question and a little off topic, but it seems like after a recent Google update about a week ago the grid size of the Google Launcher is much more compressed (being 5x5 now versus 4x4 before).

Anyone notice that or maybe its just my imagination?

LDN
[Samsung Galaxy Nexus] AbhishekS:
I'm jumping to KitKat again. Which ROM is the most stable and smoothest and works like a beast with this kernel?
[Samsung Galaxy Nexus] osm0sis:
Too many kernel source changes between 4.1 and 4.3 for that. 4.3 and 4.4 should be okay with an AnyKernel since the only real changes are in the ramdisk.

I've had that happen before. Totally random and scary. The only thing that brought it back was to completely power off, then remove battery. That seemed to allow the camera to reset properly and start again.

That builds for Linux. I'm kinda partial to my own updated versions too. :p

I'll just have to get my sh*t together and learn to cross-compile with the NDK.
[Samsung Galaxy Nexus] @jmorosky:
I'm running [MENTION=4328678]metalspring[/MENTION] OmniMetal and I don't think I'll ever switch to another ROM.

Sent from my OmniMetal and DirtyV
[Samsung Galaxy Nexus] AbhishekS:
Any other? I was using that ROM before going back to Jellybean. I didn't like the QuickTiles on OmniMetal. :)
[Samsung Galaxy Nexus] Rjev07:
Cyanfox....stable&smooth with this kernel...give it a try....
[Samsung Galaxy Nexus] michierusama:
I'm using PA 5.0 BETA. Liquid Smooth is good too. And Vanir.
[Samsung Galaxy Nexus] juju2011:
Carbon ROM ftw.....uhm does the reverse lookup in dialer work in Canada? I tried it and it works but all the numbers are american :/ and that does me nothing. Sorry for o.t
[Samsung Galaxy Nexus] mrgnex:
Well I think you know there is no best rom. So just try ?
[Samsung Galaxy Nexus] neopbm:
Yeah for me to. Dont know how to change that.
[Samsung Galaxy Nexus] aaron13:
Today I flashed the DirtyV Ramdisk version on Cm11 and benchmarked 10422. Before this I used tbe fancy r45-2 kernel which set a score of 11221. I appreciate the hard work but why is fancy r45 more flying?
[Samsung Galaxy Nexus] Kustaa:
I got the same values...with Nephilim's settings it goes up to 11.600...11.800
[Samsung Galaxy Nexus] osm0sis:
Xposed. There's a GEL Settings module I saw on Android Police a few days back, or Gravity Box also has an option to change the grid.

If you use the default DPI it's still 4x4 though, so you could also just learn to deal with the normal DPI. :p
[Samsung Galaxy Nexus] scarcry:
no it is launcher3,not GEL or GNL as Google seems to call it now. I'm running LiquidSmooth with PA modular micro gapps and both launchers are installed and I have set it to use launcher3 where a swipe up gets me into Google now.

Sent from my LiquidSmooth KitKat maguro
[Samsung Galaxy Nexus] GilGameshn1:
I use Nova Launcher Prime ... Very good indeed the not so prime version is good also . snappier that GNL .

Sent From My GNex
[Samsung Galaxy Nexus] pattyboi:):
"more flying" -_- lol,just messing with ya,but i haz question,do you have any lag on your device at all?
[Samsung Galaxy Nexus] GilGameshn1:
Try AOKP ... I pretty OK with this ROM .

Sent From My GNex
[Samsung Galaxy Nexus] neopbm:
280 dpi is better to me. So i will search for the apps you mention.

Sorry for my poor English...
[Samsung Galaxy Nexus] GilGameshn1:
Oh my god ... Not again ... Please don't judge from ANTUTU numbers . that is not MATTER at all . sorry for my tone but the antutu not a source to decide kernels or Roms .

Sent From My GNex
[Samsung Galaxy Nexus] Nephilim:
Nope, GNL, I was using Apex before 4.4 released.

If you set the DPI to anything besides stock 320 GNL changes the gridsize to 5x5, quite annoying I must say.

I've heard nothing but good things about OmniMetal but if you are not content with the quicktiles I would recommend LiquidSmooth.

It's not the kernel, it's CM11, I've seen tons of people using CM11 and all of them seem to get quite low scores. Also, are you using stock settings? With my settings on LiquidSmooth I get this:

That's right after flashing the newest DirtyV RSR 1/15 build before even letting my device properly cool down. I could probably get 13000+ if I had some patience and let my device sit for a few hours before running the test.

I see the confusion, when I said it was a swipe away, I meant you can just swipe to the right and it's built into the homescreen pages. The swipe up has been there since the first Jelly Bean. ;)
[Samsung Galaxy Nexus] scarcry:
I'm not confused at all mate. I'm fully aware of how now is accessible on GEL/GNL and other launchers like launcher3.

Sent from my LiquidSmooth KitKat maguro
[Samsung Galaxy Nexus] Nephilim:
I never meant you were confused. :p

I was more referring to the responses you got. ;)
[Samsung Galaxy Nexus] LibertyMonger:
I was getting 12,300 scores on Antutu but since flashing VirtyV SRS 2-15 my scores are back down to around 10,200 with Neph's latest settings.

I think the max 1400 isn't sticking on SlimKat for some reason. I thought I finally got it to stick but the scores were still showing 10,200

I was using SlimKat before with the 12,300 scores and max 1400 was sticking but I tried dirty flashing the same build over top SlimKat to see if I could fix some app install issues and since then max isn't sticking anymore so I either need to reflash everything clean I guess or just wait for the SlimKat stable build due to release.

So I think anyone showing low benchmarks it may be due to the max setting not sticking.
[Samsung Galaxy Nexus] Nephilim:
Try selecting frequency lock for the time being. ;)
[Samsung Galaxy Nexus] lazydognet:
Glad to see I wasn't imagining the new 5x5 grid. Yes, it's quite annoying to me too.

I'm testing LiguidSmooth now.... So far, it's very good.

I didn't know you could swipe up to get to Google Now.... I seem to learn something new everyday.

Thanks,

LDN
[Samsung Galaxy Nexus] aaron13:
Yes I did on DirtyV R, it bothered me so now I'm back on fancy r45-2

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

What it is then? Besides Antutu DirtyV R was lagging
[Samsung Galaxy Nexus] pattyboi:):
try reflashing your rom then flashing dirtyv.
[Samsung Galaxy Nexus] GilGameshn1:
I think your lag is ROM sided or many dirty flashes . I believe clearing trickster app cache and data may help . believe me I am AOKP and durtyv and no lag so far .
[Samsung Galaxy Nexus] Nephilim:
I noticed you completely ignored my response to you. I don't know if this is because you are upset because of my posting on the Mpokang thread or what but I plainly explained it is not the kernel it is CM11, then I asked you politely if you were using stock settings.

I even went as far as to show you my benchmark with a score far higher than what you got on fancy. My score of 12800+ was taken from a hot device that had not even had time to settle or cool down, that means that on a test after the device has had time to cool down I would easily reach scores over 13000+. Every person that has shown a benchmark on CM11 has had low scores on AnTuTu, even with my settings so it certainly is not the kernel causing your issue. I can tell you this because 11000 for a benchmark on fancy is super low as well.

I suggest trying out a different rom just for testing purposes, maybe OmniMetal or Vanir, I bet you that you will get a score above 12000 without a problem.
[Samsung Galaxy Nexus] milojoseph:
Guys.... why am i scoring 8921 on latest kernel with neph settings.. I did say i didnt care..... but now im starting to worry cause everyone is in the +1000.
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4608636]bsmitty83[/MENTION] ,graraks latest commits have a bunch of omap stuff,again excuse my ignorance if they are useless to you

https://github.com/Grarak/grakernel-tuna/commit/1c0b6d7fce652ea7baa4dabdc0fec4e653585215

https://github.com/Grarak/grakernel-tuna/commit/35883524873c13f743e66fbb5340084435602b6f

https://github.com/Grarak/grakernel-tuna/commit/dca59ad8e041a42d1f22d65a55b7e948b69ccc74

https://github.com/Grarak/grakernel-tuna/commit/55877da1892279e38a8c6c13e6d4c4c244b59ecc

https://github.com/Grarak/grakernel-tuna/commit/54b9e0755d8b858c9b5594ec129f6238fcaa277d

https://github.com/Grarak/grakernel-tuna/commit/575885b549b5e38ae73ba59907069f55e800aa73

ok i got lazy lol,if those are useful just check towards the bottom of his commit log lol,im not knowledgable with kernels so sorry if this is stupid :P
[Samsung Galaxy Nexus] GilGameshn1:
Happen to me sometimes . I had this experience then I see something running in memory and conflicting with antutu process . could be this . otherwise this is in opinion ,ROM related . cause I flash over 5 Roms 2 or 3 times this week . :D:p:beer::banghead:
[Samsung Galaxy Nexus] Nephilim:
You need to be a bit more descriptive. What rom, what version of the kernel etc.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] milojoseph:
Bam rom 2/15/14 versions . i will take screenshot. :(

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

I really dont care. because i always say i play MC4 and dead trigger 2.. However i wanna be with the big boys :(
[Samsung Galaxy Nexus] aaron13:
I didn't ignore you, I just reacted in order of the post and saw your post later.

The scores in antutu are not the most important for me, it's more the feeling and lag of DirtyV R. I want to try your settings and see if it works.

Do you have a link?
[Samsung Galaxy Nexus] GilGameshn1:
OK . I am on AOKP right now and have a very good experience so far with DirtyV . my rating are between 11500 to 12000 . sometimes upper . and very good gaming experience . take a side heating phone on high process . this kernel is flying . :)

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

Neph settings . http://xdaforums.com/showthread.php?t=2401653
[Samsung Galaxy Nexus] milojoseph:
Team dirty v..... Just want to at least break 11000,, and i pray [MENTION=1533050]bsmitty[/MENTION] finds a way to help with the heating problem. It gets out of hand sometimes.
[Samsung Galaxy Nexus] Grarak:
They are useless for him

My kernel was missing those commits.
[Samsung Galaxy Nexus] pattyboi:):
i dont think its dirtyv that causes the heating problem,i think its vanirs kernel that causes it cause even on stock vanir with the original kernel i got maddddd heat..could just be me tho

---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------

my apologies,like i said i am not smart when it comes to kernels,sorry :(
[Samsung Galaxy Nexus] GilGameshn1:
You are not alone . I had this so I changed my ROM for now :(
[Samsung Galaxy Nexus] swarlesbarkely:
Oh sorry I didn't know you could do that now with launcher 3
[Samsung Galaxy Nexus] osm0sis:
Had that issue with f.K for a number of people. My commit here seems to have fixed it:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/a34e27fb95326fb07269ef2825ea96efdcffb7d1
[Samsung Galaxy Nexus] pattyboi:):
isnt that already implemented considering we have the thermal framework and user set temp limits? (please excuse my ignorance:) )
[Samsung Galaxy Nexus] osm0sis:
I'm not totally up on that, but I just checked Smitty's source and it still defaults to 75.

https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV2/drivers/misc/omap_temp_sensor.c
[Samsung Galaxy Nexus] milojoseph:
what should we change it to?
[Samsung Galaxy Nexus] Grarak:
this won't heat up your device

it's just a limit, nothing more

I set the maximum to 75 too and never had any issues
[Samsung Galaxy Nexus] milojoseph:
Ok let me describe this...... It get hot on the top right corner of the back of the phone near the camera........... on my Bam rom rc2 rom running latest 2/15/14. Now it get weird. after it get really hot when i use it alot, the screen turns bright green and it glitch and it shuts off and reboots. I switched to other governors only smartassv2 helped but it was removed...
[Samsung Galaxy Nexus] bsmitty83:
Change it to whatever you want in trickster , its just the temperature at which the thermal throttle kicks it and will start pulling back freq untill the soc cools down , I push mine to 80 and don't have any issues
[Samsung Galaxy Nexus] osm0sis:
We had people in hot/humid counties with big temp issues until I lowered that throttle limit back to 70.
[Samsung Galaxy Nexus] milojoseph:
didnt know that im from brooklyn.... USA
[Samsung Galaxy Nexus] osm0sis:
Haha well not sure what is up for you then. :p
[Samsung Galaxy Nexus] hemantv:
So that's for testing score purpose only, correct? I hope that you don't mean CM doesn't offer good performance.