yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aosp:
Does showing a iPhone user a GNeX running dated omap software on [MENTION=4608636]bsmitty83[/MENTION] awesome then forcing them to smash the iCrap against the pavement count as lmk rampage? If so please no fix ?
[Samsung Galaxy Nexus] pattyboi:):
a buddy of mine did that just the other day when my gnex ran circles around his 5c
[Samsung Galaxy Nexus] michierusama:
icrap lmao.
[Samsung Galaxy Nexus] demlv:
Do the 'synapsed' versions still have the interfaces needed for TricksterMod to work?
[Samsung Galaxy Nexus] DR3W5K1:
Everything works with trickster
[Samsung Galaxy Nexus] windfrenzy:
Same here. Since Omnimetal switched to Dirty, I've been chasing battery drain, SODs, reboots, and boot up loops. I've learned so much from everyone here about flashing kernels, trickster settings, wake locks, undervolting, and... electronic music?! But with the performance of Smitty 4/6 and the latest Omnimetal, my learnin' might be done. I'll work on how to share logs next, I guess. Thanks all.
[Samsung Galaxy Nexus] Culex316:
Is it possible to add a sysfs interface to overclock the RAM or at least mess around with timings and stuff like that or does that have to be hard coded?
[Samsung Galaxy Nexus] Grarak:
No they are not hardcoded

It's possible but I don't know how the phone would handle this
[Samsung Galaxy Nexus] aeroxr1:
[MENTION=4608636]bsmitty83[/MENTION] you are a genius !

Because my English is so bad i don't know the Meaning of rampage.. :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Ah thanks for the heads up. Yeah, we've got what boype put in r48 (12, 16, 20, 24, 28, 48), which are good, but he's thinking they might need to be a bit lower still.

These seem like the reasonable contenders so far:

Feel free to get in on the testing, using Synapse or Trickster, everyone. Thoughts [MENTION=4793042]pkgnex[/MENTION]? You always had the best handle on these.

---------- Post added at 06:46 AM ---------- Previous post was at 06:12 AM ----------

Here's what I'm wondering using the Franco's Dev Team values which showed the Empty App (last number) should always be high; I'm wondering if that still holds true:

6144,8192,12288,16384,24576,40960

÷ 256 pages =

24,32,48,64,96,160 (Trickster numbers)

÷ 2 =

12,16,24,32,48,80 (~boype LMK equivalent)

- 4 =

8,12,20,28,44,76

For reference:

12,16,20,24,28,48 ([MENTION=4615478]boype[/MENTION] r48)

8,12,16,20,24,40 ([MENTION=2288033]Charmacas[/MENTION] test)

Dividing [MENTION=2853378]Nephilim[/MENTION]'s by 2 would be:

5,10,50,60,48,98 which still seems too high for sure but might be interesting to try.

[MENTION=4608636]bsmitty83[/MENTION] we are using the newer LMK right? I didn't go off on this tangent for no reason? :p

I just assumed since the rampage bug seemed to be fixed.
[Samsung Galaxy Nexus] bsmitty83:
Lol I was waiting for someone to ask if I was even using the same as boype , I'm not sure what he used , I didn't look at his source , but I believe we got the same thing going . I'll have to double check , but I took my lmk from an omap zoom source ( archos g9 )

Edit it looks like he took his from hammerhead , I didn't look through it all but it looks different

I'm using an "enhanced" lmk routine

https://github.com/bsmitty83/DirtyV_tuna/commit/81ff90c3858c1f610a96810eb88bc39eb498d97d

Boypes

https://github.com/boype/kernel_tuna_kk44/commit/16697686bf436106ca4af25a83be537d793bdbe1

Hack the freaking tuna
[Samsung Galaxy Nexus] pkgnex:
I'll try to take a look at the commits Boype and bsmitty83 used this evening to see if I can glean anything. Something has to be radically different with the new code - after a reboot with an ASRAM kernel, I have ~ 400MB free RAM, so having an empty-apps number of 48 and getting LMK running amok killing things after a few hours makes no sense. There must be some sort of new multiplier in these updated lmk drivers, or the numbers are no longer in "pages", or something similar.
[Samsung Galaxy Nexus] DR3W5K1:
These are working great for me.

---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------

I'm running 4-3 with zero issues.

---------- Post added at 08:37 AM ---------- Previous post was at 08:30 AM ----------
[Samsung Galaxy Nexus] osm0sis:
Bahaha. Damnit. Okay, well I'm not sure what's better or if we'd need reduced values like boype's to keep it good. Maybe the lower values would have helped on all the old builds where we had rampage issues. :p
[Samsung Galaxy Nexus] DR3W5K1:
I was thinking the same thing. When did he change lmk? I'm not having rampages. Refer to post above yours.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Rampage must be a good thing right?
[Samsung Galaxy Nexus] DR3W5K1:
I'm gonna start calling them killing sprees
[Samsung Galaxy Nexus] TheMan0790:
m-m-m-m-m-m-monster kill!
[Samsung Galaxy Nexus] bsmitty83:
For those born pre-1990's [emoji6]
[Samsung Galaxy Nexus] DR3W5K1:
I bet I spent $150 in quarters on that game when I was a kid.
[Samsung Galaxy Nexus] chainrulez:
Hi everyone. I just want to know you all that I had so much wonderful time here where I learned so much about my Nexus and all that things which I should know according to my little level :p. Here I would like to say goodbye to this thread because I switched to HTC One & along with this I would like to thank [MENTION=4608636]bsmitty83[/MENTION], [MENTION=4328678]metalspring[/MENTION], [MENTION=2853378]Nephilim[/MENTION], [MENTION=3317173]büscher[/MENTION] and ofcourse [MENTION=4244313]MBQ_[/MENTION] for his epic music. Wish you all good luck. Have fun ... :) :good: :D
[Samsung Galaxy Nexus] Culex316:
I would be willing to try out a build with that enabled. It shouldn't be any worse than changing RAM settings on a PC. The worst that could happen is just a reboot, right?
[Samsung Galaxy Nexus] Grarak:
Sometimes it's not just a reboot

But I don't have much time right now, although it's not more than some lines of code

Will do it when I have some free time
[Samsung Galaxy Nexus] büscher:
About these new lmk values: on 4/5 I can feel a difference with the new values but in a negative way. My phone begins to lag, switching apps, opening keyboard in an app etc. All becomes very slow and sluggish. I reverted to wavedashhogs settings and things got better. Switched to 4/6 now and trying the new values. Can't say much atm, no issues yet.

Edit: 4/6-osmod works bad on my phone. Music stutter and serious battery drain. Also heats up my phone. Never had that much sync_lost in my dmesg (and I always have a lot) multiple tousands in one second.

Trying 4/6 regular now.

Edit2: also om 4/6 regular after a short usage. Tousands of sync lost (nothing else in dmesg) unlocked screen, freeze for some seconds, also music froze, systemui got killed. Stutter while playing music...

Back to 4/5...
[Samsung Galaxy Nexus] Atento:
Best definition ever hahahaha.
[Samsung Galaxy Nexus] Nephilim:
Got a random reboot overnight off the charger on 4/6, besides that still smooth sailing, no other issues to report.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] How much ram is used before the rampage occurs? https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory
[Samsung Galaxy Nexus] osm0sis:
4/6 and osmod the main difference is the boype values; 4/5 and 4/6 have the same LMK settings from since Smitty started using a ramdisk.

So maybe we should try the hammerhead LMK boype ended up with? Right now I'll just get rid of the custom values and let LMK run default to see what happens.
[Samsung Galaxy Nexus] Atento:
4/6-osmod working great here. Just one soft reboot while I was watching a video on YouTube. Not a deal breaker though.
[Samsung Galaxy Nexus] pattyboi:):
last time i read from the fancy kernel thread the stock values were rampaging
[Samsung Galaxy Nexus] osm0sis:
KitKat defaults were rampaging with the new LMK from hammerhead that Fancy's using, not necessarily so on the different, also-new omapzoom one SmittyV is using.

They're actually different defaults in the SmittyV one:

12006,15022,18037,21081,24097,30100

(or 46, 58, 70, 82, 94, 117 in Trickster). :)
[Samsung Galaxy Nexus] pattyboi:):
woops,didnt read up enough in ze thread before i posted that :P my bad :silly:
[Samsung Galaxy Nexus] ashclepdia:
something just popped in my head(I don't have a steady connection right now so I'm just gonna post it here while I'm connected lol even though might be better in [MENTION=4615478]boype[/MENTION] thread)

I wonder if there is some specifics that need to be modified for the hammerhead lmk stuff to work better on the Gnex, mainly since the hammerhead has more RAM than Tuna? maybe there is something to do with ratio of available ram vs total RAM, and that explains why defaults for hammerhead make lmk go killing off everything trying to get things to be in line with what should be available for a 2GB RAM device.

not sure if this makes a lot of sense how I worded it but hopefully yas get my drift. it could also explain why such WAY LOW values(vs what we USED to use) need to be set to "trick" lmk into doing what we "expect".

I'm not versed in many specifics of the code behind how lmk works and is triggered, I'll have to look at it and see if any of it makes any sense to me lol. figured I'd put this idea into the discussion to see what yall think once I can get connected again.

(and side note, I had stumbled across a commit recently that has to do with calling lmk in place of kswapd and it being faster due to kswapd compaction using too much cpu, it didn't make a TON of sense to ME but I'll link it soon in case it is helpful if I can find it again, though from what I saw I THOUGHT it might be part of android already)
[Samsung Galaxy Nexus] metalspring:
;)

Cloning into 'DirtyV_tuna'...

remote: Counting objects: 2126931, done.

remote: Compressing objects: 100% (330992/330992), done.

Receiving objects:

Rather than try to read the few hundred pages I probably missed, anything interesting new things or changes to the kernel?
[Samsung Galaxy Nexus] aosp:
Don't think so only kernel.org updates amirite [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] pattyboi:):
HES RISEN FROM THE DEAD :highfive: glad to see your back ;)
[Samsung Galaxy Nexus] heXacode:
While you guys are waiting for a new update from bsmitty I'll leave this link here to show how iCrap is catching up to us Android users!

8 iPhone Tricks You Need To See: http://youtu.be/MKEKhiybAdM
[Samsung Galaxy Nexus] bsmitty83:
A lot , lol .

I'm sure from the commits you can see

I'm on exp2 branch now .

I don't even know where you left off so to speak
[Samsung Galaxy Nexus] pattyboi:):
is it bad i think of [MENTION=4608636]bsmitty83[/MENTION] & [MENTION=4328678]metalspring[/MENTION] as the guys from boondock saints..
[Samsung Galaxy Nexus] bsmitty83:
Lol I'm way more gansta than Norman Reedus [emoji6]

But its a classic .

Im not sure when I'm gonna get to update my kernel , maybe this weekend .

Working on a side project ATM , plus been hammered at work , I do prototype car stuff so when there's work , its 50+,hrs a week
[Samsung Galaxy Nexus] pkgnex:
I remember that $hit. I used to work in automotive (engineering for an OEM), so I feel your pain.

Now I work on gun stuff. It's actually a lot more fun. ;)
[Samsung Galaxy Nexus] pattyboi:):
lucky bastard. i shovel horse sh*t and fix tractors.
[Samsung Galaxy Nexus] michierusama:
I study medicine and attend our family minimarket lol
[Samsung Galaxy Nexus] aosp:
I'm sort of a real life Magic Mike ?
[Samsung Galaxy Nexus] bsmitty83:
I picture you as Android : the Dude
[Samsung Galaxy Nexus] aosp:
Hobbies ?
[Samsung Galaxy Nexus] namtombout:
Ron Jeremy before he couldn't git it up
[Samsung Galaxy Nexus] heXacode:
I'm a field manager for an insulation company. My 2nd job is parenting 3 kids (8 month old boy, 2 year old boy, and 6 year old girl).

I got my work cut out for me for sure.
[Samsung Galaxy Nexus] Atento:
Guys, I'm getting a black screen for 4 or 5 seconds on callings before everything appears. Do you think it's kernel related?
[Samsung Galaxy Nexus] DR3W5K1:
When this has happened to me before it was dialer related
[Samsung Galaxy Nexus] pattyboi:):
never laughed so hard in my entire life
[Samsung Galaxy Nexus] thagringo:
in case anyone is interested and referring to the kernel patches i linked in this thread, there is an interesting discussion about the benefits of lto at a kernel level :

http://lkml.iu.edu/hypermail/linux/kernel/1404.1/00275.html

cheers
[Samsung Galaxy Nexus] TheMan0790:
Was "git" an intentional misspelling of "get" or was it accidental? It works so perfectly for this thread.
[Samsung Galaxy Nexus] Unzitron:
Just had a freeze/anr on 4/6.

https://drive.google.com/file/d/0B9OBw0gxtTWdbVJEQzhERGZUZ0k/edit?usp=docslist_api
[Samsung Galaxy Nexus] dbh369:
Git. On purpose.lmao

Also just had 40 sec freeze on 4.6

https://app.box.com/s/ydbh4xtl4bdliw1zmuqr
[Samsung Galaxy Nexus] Grarak:
http://en.wikipedia.org/wiki/Git_(software)
[Samsung Galaxy Nexus] dbh369:
Ps. I had min free set low as discussed by [MENTION=1143630]osmosis[/MENTION], using boype r48 settings had been working well...
[Samsung Galaxy Nexus] Unzitron:
Testing Charmacas minfree... See how it goes.
[Samsung Galaxy Nexus] b4u2:
I tried settings in pic and phone really didn't like it. What are other values I can test?
[Samsung Galaxy Nexus] b4u2:
I tried 24,32,48,64,96,160 with very good results.
[Samsung Galaxy Nexus] osm0sis:
Right, so the current DirtyV/SmittyV defaults. Good to know! :good:
[Samsung Galaxy Nexus] pvkiniyan95:
Altering lmk values work good for few hours and later gets worse and annoying so better leave it alone for now
[Samsung Galaxy Nexus] Punkiderma:
I also think default dirtyV defaults are the best values I've ever tried: apps open fast and persistent ones (like Lux and gravity screen off) don't get killed. Better than with V6 supercharger for me!
[Samsung Galaxy Nexus] pkgnex:
Still working after all this time!... :highfive:

.

.

.

/system/etc/init.d/925vmsettings:

#!/system/bin/sh

# chmod -R 755 /system/etc/init.d

# 26-Jun-2013 by Franco's Dev Team

# malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres

.

.

.

# lmk tweaks

minfree=6144,8192,12288,16384,24576,40960;

lmk=/sys/module/lowmemorykiller/parameters/minfree;

.

.

.
[Samsung Galaxy Nexus] dbh369:
Quick question, using@buscher's script to set min free. Section stats with

chmod 664 /sys/module/lowmemorykiller/parameters/minfree then loads values. Should there be a chmod 444 /sys/module/lowmemorykiller/parameters/minfree after you load values? Or some other permissions?

Second, my values had not actually changed, any reason anyone can suggest? Thanks
[Samsung Galaxy Nexus] DR3W5K1:
Chirp chirp
[Samsung Galaxy Nexus] cujo6801:
Bacaa bacaa

Sent from the "DOG" pound
[Samsung Galaxy Nexus] büscher:
I think as we have a ramdisk in smittyV we actually don't need to chmod anything. I use it on my tablet and there I have to, just copied the script I created there.

I will change the values in my script as soon as I'm sitting at my laptop. I also have a very good experience with these minfree values.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] I just had a 40 second freeze on 4.6.14 which ended with Launcher FCing.. Not sure what caused it.

dmesg: http://pastebin.com/Z9MN6HMc
[Samsung Galaxy Nexus] bsmitty83:
Too much porn ?? [emoji6]Lol I'll take a look in a few

Not sure what happened , nothing unusual in your dmsg
[Samsung Galaxy Nexus] cartman333:
same thing happens to me at least twice a day:(
[Samsung Galaxy Nexus] osm0sis:
Haha I was just switching conversations in Hangouts. Nothing spectacular. Yeah I thought the dmesg looked pretty clean, disappointingly.

I've got 190-1350, 230 Screen On Min, MC Power Saving 2, KSM on, 384 GPU, Swappiness 0.
[Samsung Galaxy Nexus] Punkiderma:
Just to know, I'm the only one still having random reboots on 4/6? Sorry if is a stupid questions but last posts doesn't seem to talk about that anymore

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] b4u2:
I get random reboots. Mainly overnight when on charger.

I am a little surprised that even with fast charge on the phone cannot charge faster than I use it. I am on wifi as well. Is this normal?
[Samsung Galaxy Nexus] bsmitty83:
I'd say its possibly mc=2 that could be causing it ?? I don't use that so its the only thing that stands out
[Samsung Galaxy Nexus] bsmitty83:
I haven't had one issues on my end with the new build , but on the whole it seems like many of the issues people had are gone

Its not a stupid question . I just really don't have a answer for you .
[Samsung Galaxy Nexus] brymaster5000:
Yes...it is good...on the hole.
[Samsung Galaxy Nexus] ashclepdia:
does that option even REALLY work?

I was under the impression that MCpowersaving setting was mainly for ondemandplus governor(I'm not sure WHY I thought this, except that the only time I see that setting defaulted ON is with a kernel that sets ODP as default governor)

and I've always disabled that also. I don't know much about how it works, but it seems like I see more reported issues with it turned on then with it off. and I'm always looking for ways to make my device faster, so I try to disable all "power saving" tweaks.

(I just wish I knew exactly what ALL the "battery saving" tweaks devs put into their roms/kernels, such as vm&sysctl tweaks meant to save battery, as I'd like to revert those since usually to save battery it's a sacrifice partially of performance....)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Stock Smitty + VanirAOSP = 99 problems but my hacked up tuna Kernel and ROM ain't one ;)
[Samsung Galaxy Nexus] osm0sis:
It is a kernel setting that groups tasks to one CPU so the other can stay at a lower frequency. Shouldn't cause problems; Fancy sets it to 2 by default even. :confused:
[Samsung Galaxy Nexus] namtombout:
Don't you remember Franco saying it (mcps) was borked? I think that was his reasoning behind not adding it to his kernel

Edit: found it

http://xdaforums.com/showthread.php?p=43395874
[Samsung Galaxy Nexus] dbh369:
Conversations, is that what they are calling it these days...;)

---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------

I have mc=2, no issues now that I put min free back
[Samsung Galaxy Nexus] TheMan0790:
http://www.youtube.com/watch?v=mi5kXcc-TJ8
[Samsung Galaxy Nexus] pkgnex:
I remembered that, too! Also, he mentioned hotplug governors (hotplug, interactive-x, others) are a placebo on Tuna as the device does that automatically. I believe him on both counts - every time I set MCPS to anything other than 0 I get WORSE battery life. Hotplug governors at least haven't hurt my battery life, but they have caused random reboots and worsened the overall device experience (lack of responsiveness, etc.).
[Samsung Galaxy Nexus] ashclepdia:
The only kernels I have seen set it on as default are fancy and faux, and I believe both of those also set ODP gov as default also, that is why I was under that impression. And also as mentioned above, I thought I had remembered seeing before somewhere that it doesn't work correctly on tuna(and I'm guessing it was Franco thread where I read that) though I am not sure if issues had been worked out after that or not. But I always stay away from turning it on just because as I mentioned before I have 3 batteries and know I'm never gonna get amazing life on the Gnex so I push more for performance and stay away from battery savings things. :)
[Samsung Galaxy Nexus] clnzx2:
Turned off MCP def seems better off
[Samsung Galaxy Nexus] osm0sis:
Yeah I'm going to turn it off now and see if it resolves any issues. :)

Totally didn't remember that info from the f.K thread. Thanks fellas!
[Samsung Galaxy Nexus] Atento:
After 2 or 3 days without rebooting or shut down, my phone started to lag everywhere. After a reboot everything goes normally.
[Samsung Galaxy Nexus] ashclepdia:
Isn't it recommended to all android users that you reboot once a day??

2-3days uptime just seems long to me...

Maybe that's just me
[Samsung Galaxy Nexus] pattyboi:):
thats what i do,reboot before i go to bed,let it settle through the night,fine for another day ,rinse and repeat
[Samsung Galaxy Nexus] osm0sis:
They supposedly fixed the uptime issue with fstrim running after every 24h.
[Samsung Galaxy Nexus] infectedorganism:
I'm quoting this post because it brought about a question I've had for awhile now: what does it mean to let a kernel "settle"?

I understand what people are suggesting when they say that, but I've always been curious to know if there is actually something happening in the background or if it's just one of those things that stuck over time.

Excuse my ignorance.

Thanks in advance.
[Samsung Galaxy Nexus] DR3W5K1:
One thing is to let your phone rebuild the caches.

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

Or cache rather. I suppose dalvik is rebuilt on boot.
[Samsung Galaxy Nexus] Punkiderma:
There's a kind of log that could be useful to you? I'm using ondemandplus, could be that? Thanks in every case

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Ziyan:
Does mpu/iva/core voltage monitoring have been removed from the last few SmittyV versions? I remember Trickster showing them below the temperatues, it was pretty cool :confused:
[Samsung Galaxy Nexus] pattyboi:):
like the other guy said is that you could clear caches and let them rebuild,but to me its a lil more simple,your literally just letting your phone sit there for a awhile while all services/apps etc start up and reactivate, also,dependent if your rom could have a memory leak this may help alot :d
[Samsung Galaxy Nexus] dbh369:
All ready to report that stock min free solved my reboots, but this am, running with music and runkeeper

https://app.box.com/s/g18o5if7uwag7byadcmy
[Samsung Galaxy Nexus] bsmitty83:
Dmsg is empty .
[Samsung Galaxy Nexus] ashclepdia:
I don't think fstrim running would have such an impact as a reboot does. And that's IF fstrim runs, if you aren't plugged in for over 8hrs and idle, or whatever criteria is, you might not get fstrim run for a while.

A good ol reboot once a day never hurt performance is all im saying, and I believe in user manuals(what's THAT I know right lol) it usually has that as a recommendation for keeping performance up. IMHO it's just a good habit for ANY kind of device, be it smartphone, tablet, laptop, desktop PC, console gaming system...anything with a cpu . it's just a habit I have and whether it helps or not it's not hurting :)
[Samsung Galaxy Nexus] aosp:
Rebooting should not be required to maintain performance vogue ram munchers can be killed check running processes and clean house cause it's all about that uptime on Linux fellas ? [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Shambola:
(Part of) my everyday work is to manage >100 Linux servers.

I have some servers with more than 800 days of uptime without any side effect. But i had to schedule a restart of the application servers (JBoss) every night.

So, you are right, it's not the SO that degrades performance and in a "fairy tales world" our smartphones could live happy without daily restart.

But there would be tons of external factors to be monitored, and a reboot takes only a few minutes to be done...
[Samsung Galaxy Nexus] osm0sis:
Rebooting daily will prevent fstrim from running though, so you will see speed impacts over time if you don't ever achieve 24h uptime. The other requirements are easy (>30% on charger or >80% off, idle for 1hr); the uptime is difficult, especially for nightly crack flashers.

So I don't disagree, it's good to reboot once in awhile, but it's also good to just let things run for a couple days without rebooting once in awhile. :good: :)
[Samsung Galaxy Nexus] Atento:
Completely agree. What a shame have to reboot to maintain the performance. It doesn't make any sense.
[Samsung Galaxy Nexus] pvkiniyan95:
i've had uptime like 2 days + without any issues with lagfix fstrim running daily...