yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] büscher:
vm&zram wont give you much, I think by changing the settings in "Advanced" you could feel a difference. but nothing you could measure with antutu or whatever benchmark tool.
[Samsung Galaxy Nexus] pvkiniyan95:
According to me benchmark apps are free tools to boil egg with ur phone in case of emergency, getting advanced settings done now

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

No significant improvements actually, may be the phone is too good already to be noted

---------- Post added at 09:17 AM ---------- Previous post was at 08:59 AM ----------

is there a way to keep gpu between 384 and 512 rather than 153 coz enable hw rendering might be fluent with this setting right ???

no idea, just a hunch...i know it might cause battery drain but why not a choice for high performance
[Samsung Galaxy Nexus] büscher:
yeah maybe we already got everything out of our phone... on my borked device I can feel a slight boost in multitasking (or maybe just a damn good placebo)

also I may just overtweaked my phone now, just had a SOD :silly:

for the gpu: I have no idea haha

Edit: OOM Kill Allocation Task is not a good idea [emoji28]
[Samsung Galaxy Nexus] pattyboi:):
you talk too low about yourself bro
[Samsung Galaxy Nexus] pvkiniyan95:
+1 to [MENTION=5380162]pattyboi:)[/MENTION] , [MENTION=4244313]MBQ_[/MENTION] as a college student u r perfectly alright, trust me...

being an indian engineering student is never an easy task yet we guys live in crores and come out as crap 4 years later, i m in my 2nd year
[Samsung Galaxy Nexus] pvkiniyan95:
hyper is pretty good too....gr8 in stock settings
[Samsung Galaxy Nexus] büscher:
yep, tested hyper in HybridMix, really a good governor. also have experimental tunables for this one somewhere...

if nightmare is present you could also test this one, had good results with it.
[Samsung Galaxy Nexus] osm0sis:
No idea! They're literally just backups of the Synapse app's settings databases. Not really sure if there's device specific stuff in there or not. I'll look into it at some point.

Edit: Lightbulb! The file ownership would be incorrect if transferred! I'll write a fix tonight or tomorrow. ;)
[Samsung Galaxy Nexus] ashclepdia:
I've been using kill allocation task randomly, haven't encountered problem yet, but still testing it out anyways.

something I read though made me set the oom dump tasks to 0 though(apparently if I read correctly this can become quite a task to do if there is constantly a lot of processes getting hit by oom and it is dumping the info related to it? I'm not certain though.

edit:: here is what I read(granted this isn't a LARGE system..but still)

https://www.kernel.org/doc/Documentation/sysctl/vm.txt

If this is set to zero, this information is suppressed. On very large systems with thousands of tasks it may not be feasible to dump the memory state information for each one. Such systems should not be forced to incur a performance penalty in OOM conditions when the information may not be desired.
[Samsung Galaxy Nexus] büscher:
Had two SOD's with kill allocation task set. I think as the task that generates OOM is systemui (or something related if I press the power button) and so gets killed, my phone wont wake up again (notification LED still blinking). Just an assumption because something is not right with lmk or maybe the ROM I'm using (read something about a memory leak in PA PIE)

Will also try setting OOM dump tasks to 0 and play around with my device.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3317173]büscher[/MENTION] Got this fixed locally, and will commit it to GitHub later on today. Good catch. :)

I'll look into adding sched features like Gentle Fair Sleepers, since I noticed [MENTION=3685904]ak[/MENTION]/[MENTION=5658634]apb_axel[/MENTION] have that, but at the time I assumed it was a N4-only feature. Learn something new every day. ;)

They've got some build.prop tweak options too I can try to find a place for. I can dig up my old vm heap script and add them and see if there are any others we might want too. :cowboy:
[Samsung Galaxy Nexus] Punkiderma:
trying metalspring's V2 with nephilim settings (PegasusQ): very very smooth! Battery life seems the same (or maybe better) as with interactive
[Samsung Galaxy Nexus] Nephilim:
I tried to create a happy medium between aggressive and battery friendly. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
Guys do me a favour, I was playing with hyper and pegasusq and arrived at a setting which surprisingly feels nice, test them if u wish and tell me how it performs....

SmittyVmetal ver 2

Gov pegasusq

CPU min 190 max 1500

GPU 512

I/O bfq RAB 4096 (gr8 results if u use flash drives)

Min free values Neph

KSM DynFsync Enabled

Undervolted mpu by 50(optional)

Others pretty much stock or neph's settings
[Samsung Galaxy Nexus] pvkiniyan95:
Try em
[Samsung Galaxy Nexus] @jmorosky:
Where do I find this version? Sorry if this has been linked before. I've been out of the loop for a bit.
[Samsung Galaxy Nexus] poo706:
http://xdaforums.com/showpost.php?p=52641495&postcount=9253

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Metalspring's SmittyV is working amazing with Omni ROM, everything is so smooth...

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] metalspring:
Btw, anyone here with an m8 yet besides rkpeterson? I'm compiling a customized vanir build for m8 if any are interested lol
[Samsung Galaxy Nexus] poo706:
Rk got an m8? Is he still going to be the gnex dev for liquid smooth?

[poo]
[Samsung Galaxy Nexus] metalspring:
http://xdaforums.com/showpost.php?p=52687735&postcount=9320

And considering liquid already has devs for the m8, I'm sure he would keep being the gnex dev for liquid but you'll have to ask him
[Samsung Galaxy Nexus] Nephilim:
I converse with him on hangouts, I'm going to do the beta testing for him on toro when he builds since he can't anymore. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] PicoDeGiao:
If RK needs more testers, I'm still rockin' the Gnex.

Also, sorry Smitty for the WAY off topic post. I'll take it to the LS area.

Also #2, Smitty NoMem 5/3 is awesome. Super smooth.
[Samsung Galaxy Nexus] Nephilim:
I don't know if he has testers for Maguro or Toro+ yet.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Maguro doesn't really need any extra testers, in general it behaves exactly the same as toro (I.e. if toro has some issue beside connectivity then so will maguro) Toro+ is the only one that is different (it requires 2 extra commits outside of kernel and device repos) and does behave very slightly differently.

Gsm radio bands are far far better supported than cdma, Verizon cdma is much better supported than Sprint cdma.
[Samsung Galaxy Nexus] rkpeterson:
I'm still the official maintainer for LiquidSmooth gnex. I'll still be building and posting. I got 2 gnex's to test all the background stuff and anything I can do on WiFi, so anyone willing to test is great.

Sorry about the OT.
[Samsung Galaxy Nexus] bsmitty83:
Sorry for not updating the kernel guys , [MENTION=2838735]aosp[/MENTION] and myself are working on f2fs . made some progress . finally got twrp to use the f2fs tools now its a matter of putting everything together , it still isn't working correctly ATM , so while we're testing and working on this , my nexus is a brick with no os on it lol , so its hard to test kernel builds . but I have done a little experimenting with -O3 , added about 20 new flags .

So basically the next kernel will probably be with a new recovery and a badass Vanir f2fs build for the brave . [emoji6][emoji123]

I'll say it again since its been a while . I have no problems with off topic posts , especially if they are about the gnex like a ROM or kernel or whatever.

The more knowledge spread is better for all .
[Samsung Galaxy Nexus] ashclepdia:
[MENTION=4608636]bsmitty83[/MENTION]

I think we all know that if we haven't seen updates from you for a bit, that it just means something bigger is being worked on, so the wait is actually STILL fun

lmao

every time I see your post and scan through for mention of f2fs progress I get so excited when I see those letters(and number)

I will.NOT stand by and let you APOLOGIZE for trying to do something AWESOME though! (especially since I've been very curious about f2fs and gnex every since I read about moto using it when it was first found out and it's potential for io performance)

so personally, I THANK you for not worrying yourself with tweaking such an awesome kernel while trying to do this. especially since we've got people like@osm0sis and [MENTION=4328678]metalspring[/MENTION] dropping info and tweaked builds to play with! along.with the rest of community chiming in with plenty of settings to try out and play around with.

keep killing it!

---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ----------

ahhh I can see how fatty could definitely be an issue when systemUI is the one being killed. on my setup the system UI never gets killed, and apparently no other crucial system process. I haven't noticed any crazy change in performance or anything though either. but I just like trying all kinds of different combinations anyways for fun.

another That I always set(and have seen some roms do it stock) is vm.drop_caches=3

if you look on my previous post that I linked to info about some of these settings it explains what the different settings are for that. don't know if it's placebo or not, but I feel I get better multi tasking when this is set to 3(I haven't tried 1 or 2 yet though). almost as if it's managing some memory/caches better or something.
[Samsung Galaxy Nexus] michierusama:
We know youre making the blue substance. we gonna fly. XD i cant be more excited.
[Samsung Galaxy Nexus] osm0sis:
Drop caches isn't a setting, it's actually a command, and the "value" will go back to being 0 every time it's run. [MENTION=3685904]ak[/MENTION] used to have it so it ran every time the screen got turned off I believe, but later he reverted it. Maybe he can tell us what he remembers about the reasoning there. :)

I've also seen it done at boot but that would be pointless since there aren't any caches to drop at that point yet. :good:

---------- Post added at 01:17 AM ---------- Previous post was at 01:11 AM ----------

Can a bunch of people try tethering out? I just noticed it's not working for me on the latest Carbon nightly and I'd like to know if it's a ROM thing or not. :confused:
[Samsung Galaxy Nexus] demlv:
Running the last DV-rsr-osmod and it tethered fine for me earlier today. But I'm running the latest stable Slimkat, too.
[Samsung Galaxy Nexus] bsmitty83:
F2FS recovery works perfect now , now I'm working on the ROM , for some reason the update binary keeps failing . but the kernel and most important recovery works.
[Samsung Galaxy Nexus] michierusama:
Is this happening? I must be dreaming. :D

So the new format should only help I/O performance or other stuff too?
[Samsung Galaxy Nexus] milojoseph:
[MENTION=2853378]Nephilim[/MENTION] i really do miss ur setting because the s3 kernel im using has sooooooooooooooo much settings its crazy.... Im using the app ktweaker and it so complicated. i wish u had an s3 to help me

and i still have my nexus no one want to buy it so im going to be testing as well... so i say v2 of [MENTION=4328678]metalspring[/MENTION] version is working and of course [MENTION=2853378]Nephilim[/MENTION] settings work....... My galaxy nexus has less battery life of my s3 but it can beat it when it comes to deep sleep..... all that touch wiz process in the background

so im here like a leech until someone takes my baby. :) GALAXAY FOREVER
[Samsung Galaxy Nexus] Grarak:
Because the s3 had alot of big kernel devs

AndreiLux, Gokhanmoral etc.
[Samsung Galaxy Nexus] milojoseph:
you are right. like how we have the best kernel dev here as well ? i wanna tag them but the list is to long especially the newcomers [MENTION=5380162]pattyboi:)[/MENTION]

and [MENTION=297826]jhonny[/MENTION]
[Samsung Galaxy Nexus] ashclepdia:
I think I just creamed
[Samsung Galaxy Nexus] cujo6801:
Did somebody say off topic

Now thats a subject I can get behind... :eek::D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] ashclepdia:
yup...now I definitely did.. :eek:
[Samsung Galaxy Nexus] luckana:
somehow i am not impressed and satisfied with metalspring's v2 battery life.. I don't like it
[Samsung Galaxy Nexus] jhonnyx:
did anyone mention cream?

/driftingawayonfriday

---------- Post added at 02:18 AM ---------- Previous post was at 02:18 AM ----------

/creamaway
[Samsung Galaxy Nexus] metalspring:
Hey, how'd you get a pic of my girlfriend? lmao
[Samsung Galaxy Nexus] ASHURiCAN:
Same here, on latest CM nightly.
[Samsung Galaxy Nexus] cujo6801:
The same as everybody else did

I just ask.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] Okay.. Carbon stock kernel works fine. I ruled out ramdisk by using theirs with our zImage and it didn't work. I tried their hostapd and ours with their ramdisk and our zImage and it still didn't work..

So there is some incompatibility with the 3.4 Wi-Fi drivers and CM device tree based ROMs. Maybe a patch or two we need? That or we need an updated hostapd binary again. Where did you find the last one Smitty?

[/ONTOPIC] :p
[Samsung Galaxy Nexus] bsmitty83:
possibly , but personally the way I feel about CM is that THEY shoud stay current with ME , not the other way around .....:p

I honestly never look at Cyanogen's Gerrit or git . i never use it . Carbon with the full DirtyV zip wifiAP dosen't work ? not sure what they did if thats the case
[Samsung Galaxy Nexus] Sik-1:
Wasn't it that back in AK days the 3.4 WiFi drivers are the ones that broke the WiFi ap if I'm correct.
[Samsung Galaxy Nexus] luckana:
Is it normal for the battery to decrease from 78 to 46% in 3 hours with 2g always on? (With metalspring's v2) 10 min gaming, a little facebook and snapchat and that's it ? I think thats not good i had better battery life with the regular 5/3
[Samsung Galaxy Nexus] alfiemenace:
Wonder if I can work on that "hardware" she's holding.
[Samsung Galaxy Nexus] DR3W5K1:
Oh wow you're right.. She is holding something. Didn't notice until you said something.
[Samsung Galaxy Nexus] alfiemenace:
I meant the one she's holding with her right hand. ;)
[Samsung Galaxy Nexus] Pseudonym:
That one's a software. :D
[Samsung Galaxy Nexus] Nuginuk:
sorry for my stupid question

i wanted to ask which version of dirty kernel support pgm/tc..my power button is sorta jammed, so kinda need the slide/knock thing

i'm currently on CM11 nightly if that helps

thanks guys
[Samsung Galaxy Nexus] bsmitty83:
All 3 versions should work with touch control [emoji106]
[Samsung Galaxy Nexus] Royal King:
I'm getting a lot of ideal drain with metal modded v2 with Nephlim's setting on Vanir
[Samsung Galaxy Nexus] osm0sis:
Definitely broken with just Dirty. That's what got me started on this to find the cause. :p

It's either the kernel drivers or the custom hostapd binary or both. Where did the binary come from? Maybe I/we can hunt down a newer one that works.

You are correct, but the fix for that was to replace the ROM's hostapd binary with one that works with the 3.4 drivers. Worked up until recently, anyway. ;)
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=2838735]aosp[/MENTION] found the binary , dunno where it came from , but there wouldn't be any harm in trying one from a 3.4 kernel . itll only break WiFi .
[Samsung Galaxy Nexus] luckana:
How can i do that
[Samsung Galaxy Nexus] osm0sis:
Tried hostapd from stock N7 '13 with no luck. Going to try the hostapd from a current N5 Carbon nightly now. One thing I notice is on CM there's now a new hostapd_cli binary. We possibly need to replace that too.

[MENTION=2838735]aosp[/MENTION] where'd you grab the previous 3.4-based hostapd binary? I think we need an updated one from there, and possibly hostapd_cli as well.

Edit: No luck with the N5 binaries either. :(
[Samsung Galaxy Nexus] crazyeats:
Indeed! Tested and working here.
[Samsung Galaxy Nexus] juju2011:
Yeah buddy [MENTION=4608636]bsmitty83[/MENTION] you da shizznitt
[Samsung Galaxy Nexus] scarcry:
not DirtyV2-SR-Linaro.zip at least (uploaded 01/25) and has same md5 as the one I'm running since yesterday.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] garyngkt:
This is the one I just flashed and it says #19 correct? This is not the latest?

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

So far so good trying out this kernel on CM11
[Samsung Galaxy Nexus] bsmitty83:
All the links in the op are for new kernels . flash any of them and they are current . my old kernels are in my devhost link in my SIG
[Samsung Galaxy Nexus] Shambola:
OT

I'm not a developer, plus my English is not so good (and maybe I'm too old to excite me for the technology), but I KNOW that something amazing is happening here and now.

And I wanted to be here too!

Thanks guys
[Samsung Galaxy Nexus] hepi_hape:
Report :

Dirty V2 - SaberMOD

Sometime get freeze for a few second
[Samsung Galaxy Nexus] aamadorj:
My GN had the same issue with the lockscreen while using newest DirtyV2-SR-Linaro but it disappeared when I changed the governor from interactive to any other. It wasn't necessary to change minimum frequency. Currently I'm using ondemandplus and there are no issues at all.

Great work [MENTION=4608636]bsmitty83[/MENTION], by the way. :highfive:
[Samsung Galaxy Nexus] @jmorosky:
Thanks for all the new kernels to flash [MENTION=4608636]bsmitty83[/MENTION] Forgive me if this has been answered but What's the difference between the "personal builds" and "DirtyV-SuperRAM"?
[Samsung Galaxy Nexus] eternal70:
[MENTION=4608636]bsmitty83[/MENTION] is the conservative governor include the early suspend feature ?
[Samsung Galaxy Nexus] dereaper:
just for ****s and giggles I installed the sm sr build on 4.2.2 atom ROM and it booted and us running with no problems at all this is one beastly kernel
[Samsung Galaxy Nexus] Shambola:
Same issue....

:(

Solved using ondemandplus too
[Samsung Galaxy Nexus] Firewalker1980:
I'm using the DirtyV2-SR-Linaro build on AOSPA beta 3 right now with Nephilim's test settings (http://xdaforums.com/showpost.php?p=49710056&postcount=484&nocache=1&z=7953776166837996)

It's awesome :) No issues so far and definately the fastest Kernel besides Mpokang :)

Cheers guys!! This is truly awesome!
[Samsung Galaxy Nexus] rtfpessoa:
After a lot of fighting with my GN but after all i was able to get it running latest version. And what i can say is that it runs pretty well. Good battery and awesome performance compared to stock CM kernel.

Good work you've done here :D
[Samsung Galaxy Nexus] pattyboi:):
smittyv still killing it. havent charged since 6 last night with phone on allllll night,been 15 hours,down to 30% best ive ever had with my gnex since i bought it,thank you so much [MENTION=4608636]bsmitty83[/MENTION] for all the hard work and all the time youve spent doing this,i really cant even extend my thanks enough man,i know this is a hobby for you,and all thsi is just stuff for a phone,but honest to god man your one of the best workers ive ever met,really sticking to what you do and really doing what you say,thats very rare (atleast in charleroi lol) and i really cannot thank you enough for your work bro,from the very bottom of my heart man,we ever meet,beers on me. :thumbup:
[Samsung Galaxy Nexus] cmoG530:
Confirmed. Seems to suffer the issues of the 4.8 linaro builds.
[Samsung Galaxy Nexus] pattyboi:):
what rom guys? i get noooo freezes on any saber build.
[Samsung Galaxy Nexus] djtutis:
Same issue here with ondemandplus and interactive... Now using and testing nephilim's settings...
[Samsung Galaxy Nexus] metalspring:
Btw, can anyone test the kernel builds made with sabermod 4.8 with this rom?

http://xdaforums.com/showthread.php?t=2426408

I remembered the one weird issue with the kernel being built with sabermod 4.8 is when its built inline with a rom built with sabermod 4.8 also it bootloops for some odd reason (Odd since it has no issues with any other toolchains)

Maybe its not an issue if the kernel is compiled separately from the rom though and the sabermod arm-eabi toolchain has been updated since I last tried?
[Samsung Galaxy Nexus] cmoG530:
Vanir 1-23. Just switched back to the test 4.7 Linaro kernel.
[Samsung Galaxy Nexus] pattyboi:):
im using latest vanir with latest dirtyv saber and i have no freezes at all. vanir hasnt really played well with any of the dirtyv kernels.
[Samsung Galaxy Nexus] L-ViZ:
damn, this kernel is fast xD using it partly with nephilim´s settings and got to say, great work :) the only thing that i recognized that it´s getting warmer(i really can feel it) than other kernels, in my case i was on fancy before. i´m getting a peak of 56°C very fast, but with no usage it drops very fast again. so it´s not a big deal for me. under the same cirumstances i had about 45°C with fancy. i´ll observe it a bit, but if the batterylife will be fine i´ll stick to that kernel :)
[Samsung Galaxy Nexus] bsmitty83:
Try lowering the thermal throttle temp down from 80 to 70
[Samsung Galaxy Nexus] Nephilim:
Yep, I have mine set to 70 using my settings including the new pegasusq tunables and my phone only warms up if I'm sitting on it nonstop for like an hour, even then it never gets overly hot.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] qu4nd:
[MENTION=1143630]osmosis[/MENTION]

Would you mind posting your colour settings? Used them for a while but lost them on latest clean flash ;)
[Samsung Galaxy Nexus] michierusama:
For osmosis I have this.

Gamma disabled but I think 5 was default.
[Samsung Galaxy Nexus] osm0sis:
0 is the same as 5 (default) but with no glitch when set, so I leave it disabled. :)
[Samsung Galaxy Nexus] pvkiniyan95:
guys messed the usb port....cannot be mounted as a mtp device, charge only, airdroid is the only hope here after :(
[Samsung Galaxy Nexus] metalspring:
Probably more like cm f*cked things up...once AGAIN... I'd look into what the issue might be right now but considering I cant even walk atm I doubt I could figure anything out (weekend with nothing to do + bottle of bacardi 151= inability to do anything besides party lol).

I'm sure [MENTION=4544860]osm0sis[/MENTION] or [MENTION=4608636]bsmitty83[/MENTION] or even [MENTION=2838735]aosp[/MENTION] can look into it
[Samsung Galaxy Nexus] büscher:
that's what happened to me and soon after I couldn't even charge it anymore.

the solution was to scratch the dust out of the port with a needle... there was plenty of heavy compressed dust inside. additionally I bent the small metal thingie in the port a little, now my cable once again sits rock solid.
[Samsung Galaxy Nexus] pvkiniyan95:
Hardware issue, due to some rough handling the second pin in the port bent back very hard to touch it
[Samsung Galaxy Nexus] luckana:
i personaly reverted to dirtyv 5.3 - i have so much performance there than this v2 kernel... don't know why..
[Samsung Galaxy Nexus] Atento:
I'm sorry to say that but I think you are the only one who had to revert because of performance. Something is screwed up there.
[Samsung Galaxy Nexus] pianistaPL:
Guys, i have a shy request to you, could you vote for polish language on Fleksy website? http://fleksy.com/languages/ In Poland we're still waiting for polish language :crying: Please select "Polski (PL)" on the website. Thanks!

Btw sorry for a little OT but where i could put a request if this is the best GNex thread :angel:
[Samsung Galaxy Nexus] pvkiniyan95:
did it bro;)
[Samsung Galaxy Nexus] cujo6801:
They want my email..

Sorry bro...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Atento:
Guys, what did you do to fix the boot loop when you try to reboot the phone? It's quite annoying.
[Samsung Galaxy Nexus] pattyboi:):
use this:

tuchenz@jew.com

(this isnt meant to be offensive to anyone jewish,its from a joke my friend did along time ago,it works tho)