yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Punkiderma:
4-12 for me is a bit laggy, and kills too many apps (I have some launcher redraws I didin't have before).

Also [MENTION=4608636]bsmitty83[/MENTION] switching from ondemandplus to interactive seems to have solved random reboots problem!

Now trying osmosis' release with suspend trim
[Samsung Galaxy Nexus] djtutis:
I can confirm that... The latest dirty v is even faster than previous version on slimkat stable 4.0...
[Samsung Galaxy Nexus] dbh369:
Two logs, long freeze here:

https://app.box.com/s/ltfu8ki3i774lj7nbdkz

Reboot here: https://app.box.com/s/e7t2l294xzl2a4z0glf3 lots on sync loss

Both on smitty 4.12, nothing too crazy going on...
[Samsung Galaxy Nexus] ashclepdia:
I am usually not the type to post things like "wow this version is FAST" and stuff, since IMHO it tends to be a placebo feeling from installing a new version and 'expecting' it to be magical when sometimes changes made really DON'T affect performance that much.

BUT... I have to admit, after running 4-12 since release(smittyV version) even WITH that -5mb ram, things are flying. I haven't had a single screen lag(well except a couple that were purely app related and not kernel issues) lockups or freezes that I had become accustomed to along with crazy lag on any keyboard.

I haven't been forced to reboot in order to fix bogged down system, I am quite pleasantly surprised with the smoothness I've experienced this far. And I was SURE that one of those MANY updates added for slub and many other commits would have borked SOMETHING. So I was EXPECTING/waiting for something to bog down and error out.(no offense meant lol) so its not a placebo/expectations thing happening IMHO. [MENTION=4608636]bsmitty83[/MENTION] I must say, you've done AMAZING job here. Love this.

Heck, I even forgot that I hadn't over clocked or changed ANY kernel settings the whole time it was running so nicely.

To those having issue with restarting apps, try these minfree; (I lower mine for better multi and I don't get bogged down at all)

And I'm also happy that you've been able to(with this kernel) in my opinion, disprove that more ram to user is NEEDED for better performance. In fact you actually took some AWAY lol and its best my device has run in a LONG time. I'm sticking with NoMem Smitty from now on, things just run properly.

I look forward to the next kernel that breaks things on by device from ya, since you dig so deep in trying to fix it and end up making it hella crazy good. Keep killing it man!!

Edit::

And I know is not a long one, but this gotta be cleanest dmesg I've seen in a long time lol

No sync error!(said in Drop Dead Fred's voice... :eek: )
[Samsung Galaxy Nexus] cujo6801:
I couldn't agree more..

SmiityV 4/12 makes my phone feel like the winner in a paraplegic beauty contest..

You know

"Sitting Pretty"

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
Lol that one made my day there . great saying . [emoji6]
[Samsung Galaxy Nexus] ashclepdia:
IMHO it could of course be beneficial to have it run after wipes.

But as mentioned above, it COULD have users flooding thread with "omgggggzzzz no boootssss!!!" Type posts lol.

Is it possible to leave it up to the user whether it will do that or not? Then have it off as default and paired with description of "prepare for potential long boot time if enabled"? Or is it something that needs be hardcoded in?
[Samsung Galaxy Nexus] spirit1002:
got a long freeze. device uptime 20h. dirtyv-r 4.12

log: https://www.dropbox.com/s/yl2eng14ca34tdg/2014-04-13_23.29.zip
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] You forgot to post a link for SmittySRAM?
[Samsung Galaxy Nexus] osm0sis:
Definitely way easier to just tie to the master switch if it is included. And doing one initial trim doesn't appear to speed up any future trims so it's not like there's any benefit except for knowing it's been done.

---------- Post added at 03:42 PM ---------- Previous post was at 03:09 PM ----------

Okay new Synapsed version up with an implementation of [MENTION=4615478]boype[/MENTION]'s suspend_trim I'm happy with.

DirtyV-SR-4.12.14-Synapsed: http://v.ht/osmod

This adds a master switch for suspend_trim, which is off by default. There is a toggle in Synapse under Misc for it, or it remembers its state so you can use these commands:

Enabled: sed -i "3s/.*/1/" /data/trimhelper

Disabled: sed -i "3s/.*/0/" /data/trimhelper

If you used the previous Synapsed version, you must remove /data/trimhelper so it can initialize again. Also the initial/wipe trim is removed so you can remove the "trimmed" files in /cache/, /data/dalvik-cache/ and /system/etc/ if you like.
[Samsung Galaxy Nexus] ashclepdia:
Woah

Definitely an issue there lol

Wish I knew more about this stuff, but to me it looks like it got stuck trying to register input from a status bar touch. I can't be sure but I think it also mentioned something about an animation. Do u happen to use any custom animation settings?

(And it looks like it said it wrote info to data/anr/traces.txt dunno if that is useful too) or maybe are you using immersive mode or expanded desktop?

I'm just trying to learn sorry if I'm way off.(it just made me think that it was having trouble with getting status bar to show or react to touch. Maybe could be a bug/issue within that part of ROM code for status bar settings if that's the case...)

I'm sure [MENTION=1143630]osmosis[/MENTION] is gonna drop in and set me straight though lol :D
[Samsung Galaxy Nexus] Punkiderma:
if I want to use Trickster I have to make a init.d script with the enable command in order to keep suspend_trim on?

thanks
[Samsung Galaxy Nexus] spirit1002:
My rom is cm11 snapshot M5.

I didn't use any custom animation setting.

I didn't use immersive mod and expanded desk.

This freeze happened when I pull down the notification bar.

Sorry for my poor English.
[Samsung Galaxy Nexus] ashclepdia:
English not poor at all buddy don't apologize :) I can fully understand you :)

I didn't see anything in dmesg that would indicate something in the kernel messed up badly. The only place I saw error was in logcat relating to inputdispatcher and the statusbar. Though I did see longer than usual times for something in dmesg(I'll have to find the lines again to figure out exactly what it was) which will probably coincide with those input errors.

Maybe something just got backed up trying to recieve touch input from status bar(like maybe a notification was coming in and got touched at same time as pulldown and something errored out)

I'm not thinking it necessarily kernel related though.

If it happens again be sure to let us know with logs again I'd like to compare with the others Posted to see if they match up and figure out what caused it :)
[Samsung Galaxy Nexus] Atento:
Guys, do you know how can I restore all default values for this kernel? I think I messed things up and I don't remember the default values.

I'm using Trickster.

Thank you.
[Samsung Galaxy Nexus] ashclepdia:
Just turn off set on boot and reboot ;)
[Samsung Galaxy Nexus] milojoseph:
That is a good question I like trickster.
[Samsung Galaxy Nexus] poo706:
There's also a flashable zip that'll wipe all of trickster's settings: http://timos.me/tm/_media/downloads/trickster_reset.zip . I use it every time I flash a new kernel.

[poo]
[Samsung Galaxy Nexus] osm0sis:
Actually it remembers its state, so once it's on it stays on until you turn it off. Just use the posted commands if you don't want to use Synapse. :)
[Samsung Galaxy Nexus] milojoseph:
downloading now XD
[Samsung Galaxy Nexus] ASHURiCAN:
Does the Synapsed version work without Synapse installed?
[Samsung Galaxy Nexus] osm0sis:
Definitely. The "normal" version is also "Synapsed", mine just have my latest updates and fixes to the ramdisk so that people can test and Smitty can add them. :)

---------- Post added at 06:08 PM ---------- Previous post was at 05:57 PM ----------

I'm still sort of figuring out when suspend_trim gets triggered. There's a timestamp and increasing counter in /data/trimhelper, then there's some calculation in the suspend_trim script involving the two which decides if it triggers a trim during suspend.

The result of the equation was a time that had to be higher than a value of 900 in the script originally, which corresponded to boype saying it took 15 minutes to trigger. I changed that to 20 minutes (1200).

The weird things are I've seen the number in /data/trimhelper climb higher than 1200 without triggering (so the equation makes a difference here?), and the count gets updated every time you turn the screen off, seemingly adding the amount of uptime.

I added a 3rd number to /data/trimhelper which is the master switch on/off Boolean. Then a 4th which resets to 0 after each reboot and counts the number of times trim was triggered so we'd actually know if/when it happened.
[Samsung Galaxy Nexus] DR3W5K1:
Guys the best way to reset trickster is to do a quick wipe of the app data.
[Samsung Galaxy Nexus] pattyboi:):
english: osm0sis is very smart.
[Samsung Galaxy Nexus] osm0sis:
Lawl :p
[Samsung Galaxy Nexus] ashclepdia:
[MENTION=1143630]osmosis[/MENTION] does the counter count ALL trim operations?

I'm wondering if it is counting the trim happening from that discard option or whatever that was talked about before(not sure if that was ever changed or not)

EDIT:::

I just re read post, I believe I misunderstood what you said lol

Don't mind ash
[Samsung Galaxy Nexus] bsmitty83:
New SmittyV , latest ramdisk by [MENTION=4544860]osm0sis[/MENTION] , modified by me with lower minfrees for the new lmk/oom from Nexus5

Hope it works .......
[Samsung Galaxy Nexus] cujo6801:
But I have a gnexus

Will this work on my phone...

Muhahahaha.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
Is that the same LMK boype ended up with? Here's the latest over there:
[Samsung Galaxy Nexus] ashclepdia:
Yea with some people still reporting kill rampage(no cached apps or very little) though I'm uncertain if it is due to the kernel ONLY

That being said, I find no issue with trying it out and IF there IS issue, I'm sure we can work thru it as usual and perfect it. Something this community has become masters at recently thanks to all this activity going down and users doing mostly proper tests and providing logs(I MUST say, most y'all users here in Gnex kernel threads have been kicking ass recently by consistently providing detailed bug reports and including logs, something that didn't happen all that often not long ago lol.)

So everyone, after giving all our awesome devs a pat on the back, go ahead, reach around and give yourselves one too, you deserve it!(said as Butters from South Park Stick of Truth lol)
[Samsung Galaxy Nexus] TheMan0790:
Can someone give me the new, default minfree values that the 4/13 build has? Been away from XDA all weekend. Is everyone using these new values over Neph's values?
[Samsung Galaxy Nexus] osm0sis:
As I understand these, it's a different LMK so Neph's should not be used, along with any other ones designed for the old LMK.

English: Smitty is smart. :D

Really though, I can't read C for sh*t. :p

[MENTION=4608636]bsmitty83[/MENTION] This means you can add the donotkill back pretty easily again, right? :)
[Samsung Galaxy Nexus] GilGameshn1:
I use

6

8

16

64

80

115

And testing for now .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Correct use the included values or generally somewhere in that ballpark
[Samsung Galaxy Nexus] bsmitty83:
Lol stare at it long enough , you'll get sick of it and you force yourself to learn lol .

HTML , CSS and any other language is like that for me . i have a rough time reading it sometimes .

And I'm not that smart , just persistent and willing to try , fail and read lol
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4544860]osm0sis[/MENTION] run the below app on latest build and post the results please https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory
[Samsung Galaxy Nexus] TheMan0790:
The rest of Neph's settings are still good to use, right?
[Samsung Galaxy Nexus] cujo6801:
I tried it a couple of times

fill up the memory and then just freeze reboot the phone

First time I tried to take a SS

Sent from the "DOG" pound
[Samsung Galaxy Nexus] aosp:
If you on VanirAOSP please run the app on the last build I posted in the thread please ?
[Samsung Galaxy Nexus] bsmitty83:
App crashed for me a 470mb used , homebuilt vanir from yesterday , latest ****tyV [emoji57]

Edit , nice auto censor on the tapatalk app . never knew that it did that .
[Samsung Galaxy Nexus] cujo6801:
PAC 4/13

Sent from the "DOG" pound

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

PS toro

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Unzitron:
Fill memory crashed at 476 MB used.
[Samsung Galaxy Nexus] Nephilim:
Is this starting with today's build because my minfrees are working amazing on SmittyV 4/12 on LiquidSmooth 4/12. The best my device has ever run so far. No lag, sods, freezes or reboots at all in about 17hrs. 4/12 is my new fallback.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ashclepdia:
Yea

Lmk has been changed on 4/13

4/12 And older still use the older lmk that your values should be golden on.

The new lmk does something different (which we all trying to figure out what exactly lol) that the regular values we are used to using cause no apps to cache and many restarting apps

And I agree, 4/12(I'm using default settings except lower minfree values and like two sysctl changes) is best I've used for long time. Backed up for future
[Samsung Galaxy Nexus] milojoseph:
So everyone talking about lmk...... minfree.. lagfix. but can we get some sysctl settings?
[Samsung Galaxy Nexus] Charmacas:
Wouldn't it possible to ask a Nexus 5 user for his minfree values and divide them by 2 because the N5 has twice as much memory? This should give a good start for the values.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] osm0sis:
There are literally over a thousand of them. I've given access to some important ones in Synapse already, what are you missing?

I was thinking something along those lines too! [MENTION=2918197]The Gingerbread Man[/MENTION], what do you say? :)
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4544860]osm0sis[/MENTION] dirtyv12/4 synapsed my new fallback...gd job
[Samsung Galaxy Nexus] marcocsh:
My phone behave strangely with dirtyv12/4 synapsed. When plugged, sometimes it charges sometimes it doesn't. Fall back to 2/4 and the issue is gone.

Any clue?
[Samsung Galaxy Nexus] milojoseph:
[MENTION=2853378]Nephilim[/MENTION] and others can you come up with tunable to smartassv2. Maybe we can change this time.
[Samsung Galaxy Nexus] erghetto:
i'm interested in trying dirtyV (the one bigmem). it has some problem of stability, or else? or is good?

and, from what i've understood it support touch control, but which module i have to download?
[Samsung Galaxy Nexus] Atento:
Does Osmosis synapsed version keep minfree default values from SmithV?
[Samsung Galaxy Nexus] poo706:
Download the DirtyV 3/16 touch control module.

[poo]
[Samsung Galaxy Nexus] erghetto:
ehm guys i've never seen so many tcp profile XD

could you suggest me TCP, scheduler and governor?
[Samsung Galaxy Nexus] Shambola:
This is a job for [MENTION=2853378]Nephilim[/MENTION]!

Neph, take off your glasses...
[Samsung Galaxy Nexus] heXacode:
[MENTION=4608636]bsmitty83[/MENTION] I have the Note 3 now. Anything you want or need from it?

Finally bought a brand new laptop Acer Aspire M Intel Core i7-4500u 1.8ghz with turbo boost to 3.0ghz.

Had everything planned out on what to do with the GNex and/or Note 3 as far as themeing and developement. Now I feel overwhelmed by just the task of where to start and what to set up! Lol.
[Samsung Galaxy Nexus] Droiderat:
SmittyV-NoMeM-4.13.14 (with cm-11-20140411-NIGHTLY-maguro) is very smooth; no freezes and so far no reboots. I'm using the default MinFree values (2, 5, 10, 15, 20, 25).

I am finding, however, that GEL (or whatever they are calling it now ... the Google launcher) is often being killed, and it often (though not always) must be restarted when I go to it (which is a lot). How can I keep the GEL from being killed?
[Samsung Galaxy Nexus] bsmitty83:
Try raising the open app minfree value , I believe that's the launcher .

Those are just base values I came up with , feel free to find a good combo .
[Samsung Galaxy Nexus] Kaemo:
I thought the launcher was part of the Secondary Server.
[Samsung Galaxy Nexus] bsmitty83:
There you go , secondary server . knew it was one of them [emoji6]
[Samsung Galaxy Nexus] pvkiniyan95:
going to try [MENTION=4615478]boype[/MENTION] 's new min free value, currently downloading ls 14/4 lets see how the combo works...
[Samsung Galaxy Nexus] büscher:
guys... I think I found the culprit of the sync_lost and why some of us have it and some not (and that's so obvious now...)

I only get sync_losts if I change "OMAP gamma contrast" to anything else than 0.

I can test it this way:

Set OMAP gamma contrast to 6 for example.

Turn off and on the screen

cat dmesg and see at least 1 new sync_lost entry.

Set OMAP gamma contrast to 0

Turn off and on the screen

No new sync_lost

change to anything else than 0 and the sync_lost will most likely be there after turning screen off and on.

Also if I do a restart with OMAP gamma contrast set to 0 I can't find a single sync_lost in my dmesg.

All the other color controls don't have an affect to sync_lost.

For now I will find out new color control values that I like and add them to my script.

If that info somehow helps to do something on the kernel, even better :good:

edit: just found out that changing from 6 to 0 my colors don't change at all... great, will use 0 from now on.
[Samsung Galaxy Nexus] michierusama:
I was gonna say the same. 0 changes nothing noticeable so Im using it at 0 and thanks for this!! It must have taken lots of your time to come to this. (Y)
[Samsung Galaxy Nexus] osm0sis:
It's the old minfree (changed in 4/13) so it's the old Franco's Dev Team minfree values we've been using since Smitty added the ramdisk. :)

It's 5 and 0 that are the same actually, because 0 is disabled and 5 is the middle of the range.

Great find by the way! Explains why not everyone had those errors. :)
[Samsung Galaxy Nexus] aosp:
If you on VanirAOSP please test the rampage jackson free edition of [MENTION=4608636]bsmitty83[/MENTION] and post feedback thanks

http://xdaforums.com/showthread.php?p=51903773
[Samsung Galaxy Nexus] büscher:
Yeah haha, that really bugged me. I hardly could provide a dmesg with other infos inside than sync_losts.

Only one thing to go for the perfection: that annoying bug where my phone forgets my wifi's. Even a back-to-stock wipe couldn't solve this...
[Samsung Galaxy Nexus] Royal King:
Check Nephilim's setting mate =)
[Samsung Galaxy Nexus] büscher:
didn't want to mess with Neph's settings. But as 5 is the same like 0 we are good here.

changed the script for Neph's settings too.
[Samsung Galaxy Nexus] aosp:
Any of you with sync lost spam have adaptive backlight enabled?
[Samsung Galaxy Nexus] büscher:
Yep that's enabled too but only since one week now. Had sync_losts with and without auto brightness.

Or did you mean CAB?
[Samsung Galaxy Nexus] frimpasi:
Why I can not run the Antutu's full test? When the last part of the test begins (3D graphics), it crashes... Somebody has the same problem?

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] aosp:
Disable CAB
[Samsung Galaxy Nexus] büscher:
Disabled CAB, set gamma to 6, turned off and on and sync_lost back there...

It's really just OMAP gamma contrast settings that causes sync_losts.
[Samsung Galaxy Nexus] GilGameshn1:
Fuuck that piece of **** software ...always stay behind of commits that added to kernel ... It is not accurate anymore in my op ... [emoji44]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] michierusama:
Just dont use benchmarks lol. Trust your inner power buajaja.
[Samsung Galaxy Nexus] osm0sis:
Happens when the voltage is a bit too low on something (MPU, GPU or even IVA), or the GPU OC isn't taking well. You doing either of those? As others said, AnTuTu is also prone to plenty of derps of its own.
[Samsung Galaxy Nexus] Kaemo:
Just bought a Red Nexus 5 out of impulse.

This is so weird. I've been with my GNex for so long, I've been installing custom ROMs and what got me into Android was the GNex, because it was the first 'Nexus' I've ever heard about.

It's gonna be so hard to see it go. But that's how things work out.

#MayTheGNexGoOn
[Samsung Galaxy Nexus] frimpasi:
I OC the GPU to 512MHz, but it happens with all of the GPU configurations... I didn't touch nothing more...

The benchmark is the least, but the games performance is bad, with lag in games like Plants vs Zombies or RR3...
[Samsung Galaxy Nexus] michierusama:
I used to have that issue so i stoped getting benchmarks and trusted my inner power buajaja. I know its over 13k xD
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] Okay figured out a couple more things about suspend_trim that aren't the way it implies.

The counter (which I set to now trigger trim at 1200 seconds, or 20 minutes) only goes up when the screen is on.

This number is only checked when the screen is first turned off, at which point if it's high enough it trims, and if not it just writes the number to file.

This means it doesn't wait at all when you turn the screen off before trimming; if it's going to trim, it does it immediately when the screen is turned off.

So in practice, if you have hit the magic number 1200 and you try to turn your screen off for a split second, it will trim all filesystems and you probably won't be able to turn your screen back on until it's done (between 30-60 seconds).

Fun right? I'm going to see if I can figure out a way to make it properly wait.
[Samsung Galaxy Nexus] bsmitty83:
Trimming shouldn't take that long at all , I used to trim all 3 partitions with lagfix and it took 2sec max .
[Samsung Galaxy Nexus] osm0sis:
Yeah, I dunno. Sometimes it's like 5 seconds, sometimes it's 40. LagFix is with screen on, so that's probably part of it, but my max screen off is 525 MHz so you'd think it would be fine.

Just another oddity about this thing I guess?
[Samsung Galaxy Nexus] bsmitty83:
Im thinking it should just be written for trim on each boot , and every 24hrs uptime
[Samsung Galaxy Nexus] Kaemo:
Remember we discussed earlier this year about how Glass could help the GNex get updated drivers?

The update has been announced. I have no idea what this means, but is it worth looking into? :fingers-crossed:

http://www.androidpolice.com/2014/0...hoto-bundles-voice-command-sorting-much-more/
[Samsung Galaxy Nexus] osm0sis:
Trimming on the first boot is the way it was originally written and extended the bootani by about 30-60 seconds, so basically we've already tried that and it wasn't good. :(

>24h uptime is when the native fstrim happens; we've put in suspend_trim to try and cater to those who never reach 24h, like crack flashers or on ROMs with Deltas.

Also complicated by the fact suspend_trim only counts screen on time for some reason. :confused:

Either way, it's off by default, and if I can make it behave better by not instantly trimming at screen off, and somehow aborting if it gets turned back on, I think we'll be okay. That last one will be the hard part, but I have a couple ideas.

Nice! We have the exact same GPU as them so that's where we might get some improvements. :)

Probably be some updated kernel stuff, but mostly it'll get fixed in the ROMs.
[Samsung Galaxy Nexus] bsmitty83:
Anyone using the new ioscheduler on last smittyV ?
[Samsung Galaxy Nexus] milojoseph:
what response are you expecting

A) Yes i Have and its buggy yada yada, battery killer

b) yes its the best scheduler hands down [MENTION=2853378]Nephilim[/MENTION] should take a look

c) no

My answer

C)
[Samsung Galaxy Nexus] osm0sis:
He was looking for

d) I'll try it now.
[Samsung Galaxy Nexus] dbt816:
Yep! Seems fine here. A few random benchmark runs and things are still on the top end of what I always get on my device.
[Samsung Galaxy Nexus] michierusama:
Is that scheduler better than others?