yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] heXacode:
Osm0sis discusses about it a few pages back. There's a temporary fix but as bsmitty said it only made it a hair faster than 3 seconds. He's aware of it and is fixing it while doing other stuff for the kernel.
[Samsung Galaxy Nexus] aosp:
No go away thanks ?
[Samsung Galaxy Nexus] GilGameshn1:
Here dear [MENTION=2838735]aosp[/MENTION] ... Sorry that I fighting with sharing a file ...lol .... https://www.dropbox.com/s/rbhdgxksetz8u64/Log_2014-03-08_23-04-21.txt
[Samsung Galaxy Nexus] dbh369:
I over ride a few other settings with trickster with no issues. Gpu, color, Illinois, high freq. Seems initd runs first, then trickster. Only issue is that trickster writes all kernel settings for me so have to turn off for a new script, then update each page again in trickster so that trickster only changes what I want changed
[Samsung Galaxy Nexus] heXacode:
If you're using a script then Trickster is pointless. I wouldn't recommend running both with different settings. What you change in Trickster will be conflicting with the script.
[Samsung Galaxy Nexus] aosp:
Thanks for the effort I need a dmesg during booting though you posted a logcat ;)
[Samsung Galaxy Nexus] GilGameshn1:
Tell me exactly which file and I will do it .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Reboot then unlock your screen then reboot again and grab him /proc/last_kmsg :good:
[Samsung Galaxy Nexus] GilGameshn1:
Acknowledged sir ... Will do . :cool:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] I got a blurry Google+freeze kmsg finally:

http://pastie.org/private/stlq5re58kpomy00s4nq1q

It happens directly after that OMAP 4470 466MHz LPDDR fix gets applied so seems reasonable to assume that's the problem. :)
[Samsung Galaxy Nexus] GilGameshn1:
https://www.dropbox.com/s/ik4ifbolj2vturc/last_kmsg hope it is the one

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
thats wierd tho,cause i use those same commits on my kernel and ive yet to hear anything about the blurry google logo :confused:
[Samsung Galaxy Nexus] aosp:
Thank you exactly what I needed appreciate it

[MENTION=4544860]osm0sis[/MENTION] Resetting all functions in Synapse enables zRam? Can't be disabled afterwards ? zRam control in Synapse should be revisited to at least a simple enable/disable works unless the apk I'm using needs to be updated?
[Samsung Galaxy Nexus] GilGameshn1:
Glad to see it helped ... :):) I did it like [MENTION=4544860]osm0sis[/MENTION] said ... Learning here ...

Sent From HellRift / No One Can Stop Death
[Samsung Galaxy Nexus] dbh369:
Running 3-7, flawless so far, thx
[Samsung Galaxy Nexus] mkuehl06:
Old build but running nephs settings. Looks good so far.
[Samsung Galaxy Nexus] Shambola:
Even more strange : Now works well. No reboot, no modifications.

Mysterious behavior :)
[Samsung Galaxy Nexus] bsmitty83:
Finishing up a new dirtyV . should be done sometime tonight ....
[Samsung Galaxy Nexus] Nephilim:
I try every new SmittyV/DirtyV but keep going back to 2/28. I get 13200 in benchmarks almost everytime and my standby time is around 18-20hrs which anyone on Toro will tell you is pretty damn good lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
anything more than 10 hours on my toro is good lol
[Samsung Galaxy Nexus] Nephilim:
I can milk about 12-15hrs with moderate to heavy use, that means from 1.5 to 3hrs of on-screen. I can squeeze 17hrs once in awhile with extended on-screen though. Our device just doesn't have the battery size to handle a lot of 4G, thats the main issue with Toro. It's also why I'm on Wifi wherever it's available. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] mkuehl06:
I run toroplus so I'm always looking for good settings. Before liquid came to toroplus I would run a modded toro version. Ever since sourcery went away, ive had a hard time finding a rom like it.
[Samsung Galaxy Nexus] pattyboi:):
you shoulda seen me when i got this phone man,first day i had it and didnt think i needed to turn 4g off during my day at school my mouth dropped to my chest when i had like 30% left after only a couple hours of not even touching it
[Samsung Galaxy Nexus] Nephilim:
Ever since I started using AK kernel I really started getting into refining settings, I build them so we dont have to turn crap off to get the battery life that I've stated above. I put a lot of effort into it and I take pride in how many of you I've been able to help. I just can't condone having to turn off pertinent features just because Galaxy Nexus' battery blows ass lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
oh yeah speakin of that,mind given my kernel a chance when you have free time? i could use some neph settings ;)
[Samsung Galaxy Nexus] Nephilim:
You made a kernel? Wow, I haven't been keeping up on here that well lately lol.
[Samsung Galaxy Nexus] pattyboi:):
yes sir :P here lets go there before the smitty throws tuna at me lol http://xdaforums.com/galaxy-nexus/development/kernel-community-remix-t2669394
[Samsung Galaxy Nexus] Nephilim:
Guys, for those that didn't see the couple small adjustments I made to Interactive Governor Control Tunables, I have updated my thread.

Thanks,

Neph
[Samsung Galaxy Nexus] Doublewise:
[MENTION=2853378]Nephilim[/MENTION] Are you getting 13000 benchmark with oc? I never exceed 11000 with with standard 1200.
[Samsung Galaxy Nexus] imam.krismanto:
Can you give link for 2/28, on archive i just see nomem version..
[Samsung Galaxy Nexus] milojoseph:
no can someone translate this changelog..... to noob friendly..... lml i need to learn this stuff.
[Samsung Galaxy Nexus] pvkiniyan95:
Flashed 8/3 Smitty V, btw is dirty v 8/3 modified 7/3 smittyV I.e stable etc...

BTW noob friendly changelog pls [MENTION=346208]smitty[/MENTION]V
[Samsung Galaxy Nexus] wisefreakz:
It means: the sh!t is fixed!!! Go get'em tiger!!!!

Lmfao
[Samsung Galaxy Nexus] milojoseph:
Yup aosb rom + kernel gave me this with [MENTION=2853378]Nephilim[/MENTION] settings with +180mhz min and +1350max :cowboy:
[Samsung Galaxy Nexus] Nemed:
Anyway i think i solved the random freeze/lag, i think it was related to the smartreflex voltages, maybe they were too low for me. I'm really happy!
[Samsung Galaxy Nexus] juju2011:
Had the freeze issue periodically what did you set smartflex to remedy freeze¿
[Samsung Galaxy Nexus] Nemed:
I'm trying with 890mV (Core, IVA and MPU) ...i can't say it's totally solved, but it's definitely more usable!
[Samsung Galaxy Nexus] juju2011:
Yah I put all to 900 and under volted mph 100 and over volt rest by 25 seems to working smooth now just my usual keyboard lagg because it can't handle my speed :) but thx for the advice helped a lot
[Samsung Galaxy Nexus] >stylz:
[MENTION=4608636]bsmitty83[/MENTION] pgm(touch control) is for waking up the phone and locking anytime you swipe the screen navbar from left to right or right to left ;) your implemented touchwake isn't a complete replacement for the power button, i guess thats what everybody wants ;)

Btw i love that kernel and it has so many options sweeeeeeet!

And i think the kernel module is called s2w vor sweep2wake or something ;) thx for this kernel bro!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] AbhishekS:
Then what is touchwake? :S

Man, this is so confusing. :P
[Samsung Galaxy Nexus] juju2011:
Tap screen and it wake up :/ I rather this than sweep2wake tbh
[Samsung Galaxy Nexus] itslels:
Been running this close to 24 hrs now. Battery life and performance seem comparable to fancy kernel, which is my favorite kernel. Good work on this and keep t up!
[Samsung Galaxy Nexus] juju2011:
Yah 890 for sure works better than my 900 freeze is down to a sec and like once every few hours just what's on screen freezes tho can still use soft keys lol will keep fiddling in trickster an see if it will go away completely :D
[Samsung Galaxy Nexus] Nemed:
I'm experiencing freezes mostly (almost only i think) when i have many conversations on whatsapp. It's a little annoying because, after the freeze, my keyboard disappears and i have to close and reopen whatsapp in order to fix this thing. :(

I'll test some new values, let me know if you find something better! :)
[Samsung Galaxy Nexus] juju2011:
For sure same with me but on Facebook and in text app I had it perfect on carbon but flashed slimkat and forgot to write down what I had set when phone charges I'll restore my backup and see if settings still there if they are I'll post a screenie :)

---------- Post added at 05:12 PM ---------- Previous post was at 04:41 PM ----------

K my setting are still there smart flex set to 850 all around . core volts and Iva are the same 1275 1175 1075 975 and mpu I undervolted by 50 had no freezes with these settings just the keyboard issue persists every now and then have GPU at 384 rab at 2048 min screen off 525mhz max same min CPU also that and max at stock use cubic, vr and interactive
[Samsung Galaxy Nexus] z1on:
I tried many 4.4 ROMs so far but all with the random reboot problem and as far as I know it's related to kernel, is this kernel affected by this bug?
[Samsung Galaxy Nexus] bsmitty83:
Not really sure , I've gotten one random reboot since building and it was a mpu watchdog reboot , but only once . I think I've gotten random reboots on every custom ROM I've used at some point .
[Samsung Galaxy Nexus] WILLI120:
I'm on metalsprings Carbon KK build for about a month now - no single random reboot. I use the kernel that came with the ROM which apperently is ASKP. Check it out, maybe you can get rid of your issues, too :)
[Samsung Galaxy Nexus] NeverSeparate:
Askp doesn't have it built in like this does. Using Askp the option isn't in trickster but it is with this.

I'm also getting the freezes. They last several seconds and sometimes the keyboard goes away.
[Samsung Galaxy Nexus] juju2011:
Check carbon thread new kk ROM out on the 14th what am using :)
[Samsung Galaxy Nexus] bsmitty83:
How frequently do these freezes happen ? I use vanirs keyboard so I haven't experienced that yet , but I have been looking into some things that may add to the overall smoothness and stability of the kernel . I also want to change the GPU freq , make 384 the lowest and add a 4something freq

Also working on a superRam version by request :p , I might make 3 versions or more and make an aroma kernel installer to pick what one you want

( really been wanting to do the installer for myself for a while just never got around to it )
[Samsung Galaxy Nexus] NeverSeparate:
Seems to happen most when I'm typing. I'm using SwiftKey. But it's happened using Tapatalk. It happened when I was typing that post. And it has happened various times today. Never rebooted. Just froze for several seconds.
[Samsung Galaxy Nexus] bsmitty83:
Sucks man , I'm not sure why , I haven't had anything like that at all . I wish I could help more . try catching a logcat while its freezing , maybe it'll show up and be fixable for you . I'll try to help as much as possible
[Samsung Galaxy Nexus] NeverSeparate:
It isn't just me reporting it. But I'm not on it now. I use my phone at work while installing cable so i had to flash a different kernel. So I can't get a log.

But to help trouble shoot, those reporting the freezing/keyboard disappearing issue, what rom are you on?

I'm on unofficial KitKat liquid which is build on sabre mod tool chain (I believe that's what it's called). Compatibility issue?

The kernel seems to run fine until it does that. Battery seemed good.

---------- Post added at 09:17 PM ---------- Previous post was at 09:17 PM ----------

I'll definitely test your builds the though. Happy to support my old dinc2 pals.
[Samsung Galaxy Nexus] aosp:
Sweet I thought you put tuna back in the ocean after you got a mako :)
[Samsung Galaxy Nexus] Nephilim:
Stefano is too much of a good guy to leave anyone behind, I'm so happy that my G+ Community helped get him back here, even if he is just giving a helping hand! Although he left Tuna for Mako I always knew I could send him a pm here or a hangout on google and he would always respond with help to the best of his knowledge. Truly one of a kind.

Smitty is turning out to be a true predecessor to that type of helpful attitude. :good:
[Samsung Galaxy Nexus] metalspring:
Btw [MENTION=1533050]bsmitty[/MENTION]84 have you considered using sabermod arm-eabi 4.8 instead of linaro 4.8? I know linaro 4.8 can cause issues with kernels but I've used the sabermod toolchain for quite awhile for the arm-eabi toolchain on my rom builds with ASKP kernel and it always works just fine

Btw, sabermod toolchain is aosp based with patches to improve optimization much the same way the codefirex toolchains are.

It may work as well as linaro 4.8 but without any reboot issues
[Samsung Galaxy Nexus] Nephilim:
AOSP! You are my 7000th thanks!!!!! Woo-Hoo! :good: :D
[Samsung Galaxy Nexus] ak:
Always tha same story on web xda:

Sorry, you are limited to 8 thanks per day

im sorry guys.
[Samsung Galaxy Nexus] Nephilim:
So you think 4.8 may be the cause of my overnight charging SOD's possibly?

Thats the reason I suggested a 4.7.3 test build as-per Stefanos recommendation.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Blackcrx:
Not to point fingers. But is anyone else having sleep of deaths besides you? Mines running like a champ
[Samsung Galaxy Nexus] poo706:
I see that you added some more settings and that they mostly match what Vekhez suggested in post #487. Curious though, you have 1800 for VUSIM and Vekhez has 1500. Did you purposely bump that up by 300 or is it a typo?

[poo]
[Samsung Galaxy Nexus] Nephilim:
[/COLOR]

I'm only encountering SOD's after having my device sitting on the charger overnight, other than that I get none. At this point I am trying to narrow it down to whether it's voltage settings, minimum cpu frequency, a bug with Linaro 4.8 or a mixture of them. :)

---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------

Not a typo, back when I was using Mpokang SuperRam I was using the settings Vekhez has for VAUX3_6030, VUSIM and VMMC but decided to bump them even before he posted his extended settings. I have VAUX3_6030 jumped up to 2700 rather than 2500 because I noticed a slight brightness glitch after setting it at 2500. (You will notice that right when you click the checkbox to initiate the settings that the screen will kind of brigthen up and lose a tiny bit of color saturation.)

Everything else I have exactly the same as Vekhez per testing and they seem to be doing great. ;)
[Samsung Galaxy Nexus] ahmadairfan:
So here it is, I found my GNex keeps it speed and stable at -90 MPU all voltages. :)

I dunno whether I UV more on the low/high frequency, either gives freeze and then random reboot begins...
[Samsung Galaxy Nexus] clnzx2:
I am getting a sod every morning when my alarm is set. Does not happen with other kernels. Could this be the same issue you are having [MENTION=2853378]Nephilim[/MENTION] ?
[Samsung Galaxy Nexus] Nephilim:
Is this the only time you get the SOD and are you usually connected to the charger overnight? It sounds just like my problem. When I wake up my notification LED is still blinking properly but the screen is black and completely unresponsive until I do a battery pull. I literally have no issues with SOD's outside of this.
[Samsung Galaxy Nexus] ak:
What are your kernel settings?
[Samsung Galaxy Nexus] metalspring:
[MENTION=2853378]Nephilim[/MENTION], I'm doing a quick build of the kernel with the cpu governors and I/O schedulers added back in, plus using sabermod 4.8 instead of linaro 4.8 (with one patch specific to linaro 4.8 reverted)

If it works I can pm you it to try if its ok with [MENTION=4608636]bsmitty83[/MENTION] (No promises though since I know very little about compiling kernels lol)
[Samsung Galaxy Nexus] Nephilim:
Sure, I'll be the guinea pig on this, got nothing else going on while we wait for Smitty's new official. This will help us to find out if it is indeed 4.8 linaro causing some of us issue as well. :good:

---------- Post added at 09:45 AM ---------- Previous post was at 09:44 AM ----------

That's a mighty fine sigpic you have there good sir......
[Samsung Galaxy Nexus] cujo6801:
If you want to you can toss it my way too..

I'll try it on Vanir 1/22...

sent from the DOG pound
[Samsung Galaxy Nexus] juju2011:
And I'll try on carbon :)
[Samsung Galaxy Nexus] schnob:
This thread really is turning into the old ak thread, swift kernel releases and even anarkia himself is present. I dig it.
[Samsung Galaxy Nexus] fracama87:
This thread like old ak thread is the reason which make me love my gnex! It's unique :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Utkarsh-ezzo:
wow already feeling abundant as I never witnessed [MENTION=3685904]ak[/MENTION] 's development environment as I joined maguro kinda late, but always heard good things in almost every thread , also seeing [MENTION=4608636]bsmitty83[/MENTION] working so hard and also b he is really kind person, and [MENTION=2853378]Nephilim[/MENTION] testing his ass out on every build to provide us best review one could get, and [MENTION=2838735]aosp[/MENTION] being an encyclopedia sharing every damn thing that too without expecting for any credit , also [MENTION=4328678]metalspring[/MENTION] giving his helping hand,

all this is awesome , you guys are great, Thank you Thank you Thank you
[Samsung Galaxy Nexus] milojoseph:
thank you for translating lmfaoo
[Samsung Galaxy Nexus] bsmitty83:
I updated the old versions , there were no other 2/28 versions , but DirtyV 3/2 is about the same , although I prefer the latest
[Samsung Galaxy Nexus] Nephilim:
Yep, I use my custom kernel settings as always. :)

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------

Thats what I'm using. Honestly, since 2/28 all I test are SmittyV. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
Quite confused about using smittyv or dirtyv... The wakelag of 1or2 sec in lock screen is still there in smittyv, anybody in dirtV experiencing it.

Btw the settling time is much quicker in 8/3 smv
[Samsung Galaxy Nexus] Nephilim:
I gotta agree, wake lag is pretty heavy on 3/8, 3/5 it was barely noticable but on the new SmittyV it's at least 3 or 4 seconds lag before the screen comes on.
[Samsung Galaxy Nexus] bsmitty83:
Idk about 3 to 4 sec ..... :sly: Maybe 1.5 tops
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=2853378]Nephilim[/MENTION] Google promised gnex to have 6h of web browsing in ICS but those days are gone, I don't even get continuous 3h on wifi, going back to 1200Mhz max and test it....as said "sitting like a dog near plug point charging my mobile always"
[Samsung Galaxy Nexus] Nephilim:
I'll let it settle a bit but on the first 3 attempts of waking from deep sleep it was around 3 or 4 seconds. I gave 3 minutes of screen-off in between to make sure the device was sleeping before clicking the power button.

Crossing my fingers.
[Samsung Galaxy Nexus] wisefreakz:
Neph.... Try to switch from interactive to ondemandplus just for testing purpose.

On my end with ondemandplus I have no wake delay...
[Samsung Galaxy Nexus] Nephilim:
**Update

Now when I hit the power button I see the screen faintly light up with a dark dark gray like it's about to wake but it doesn't, I can then tap the power button again and the screen goes off, then I hit it again and it sits on that same dark gray/black, I got it to wake after that but it took about 8 to 10 seconds, the real head scratcher is that it is not even in deep sleep because I have it plugged into my pc right now. This is not reaccuring everytime, it's hit or miss, sometimes it takes only a second to wake others it's 3 or 4 seconds and then other times it's as I stated in the beginning of my post. Going to have to go back to 2/28 I think, will give it an hour to see if it works itself out before I do though. Personally, 2/28 is giving me 20hrs of standby and 13287 for a benchmark, I don't see the point in keeping early suspend when it seems to cause this much issue for some of us. I use the exact same settings on 2/28 as I do on all the new releases of SmittyV so it's not my settings that are creating issue. On a personal note, I am not bumping my max screen-off up any higher than 525mhz, just saying that now so nobody tries telling me to. My settings have worked remarkably on all SmittyV/DirtyV variations until early suspend was added so I am not about to change them. No offense to you Smitty or anyone else, the kernel still rocks, below is my first benchmark on SmittyV 3/8/14, really hoping the wake lag calms down. :(

---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------

See that's the thing, I may sound selfish right now but I will not switch governors to fix the wake lag problem, that is more of a workaround than an actual fix. I love my settings, they give me amazing results with this awesome kernel, unless I am tweaking something because I think it'll improve my custom settings I am not going to change them, especially not when they work fine on all the other kernels prior to early suspend. ;)
[Samsung Galaxy Nexus] aosp:
What does dmesg say when you get the lag?
[Samsung Galaxy Nexus] Nephilim:
To be honest, it looks like it needed to settle once again. Now the wake lag is down to about 1 second again. I'm prayin' it stays that way but I'll post a dmesg if it doesn't. ;)

Neph puts his foot in his mouth once again. :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=2853378]Nephilim[/MENTION] the dark grey screen u mentioned has been there even earlier, I get them when play store updates something... Man I started hating playstore updates...turned off automatic updates and started updating them when I sleep
[Samsung Galaxy Nexus] aosp:
At least you not reporting battery usage already ?
[Samsung Galaxy Nexus] Nephilim:
I will now proceed to let the device settle for no less than a half hour before determining wake-lag.

This sh*t is retarded, what could possibly cause the Gnex to have major wake-lag for the first 5 to 15 minutes and then all of a sudden it vanishes?

---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------

Well the battery is amazing, I've been on this kernel for a half hour not using it and I still have 97%. :p

I really wish this supported every single version of touchwake that exists on the planet earth though, I am really pissed that it doesn't and it's all Smitty's fault. Actually it's also Stefano's fault because AK Kernel did not support every single existing form of touchwake either.
[Samsung Galaxy Nexus] lazydognet:
Just curious Nephilim's, were you talking about SmittyV NoMem 2-28 version? Do you usually only use the NoMem versions?

Again, I was just wondering.

LDN
[Samsung Galaxy Nexus] Nephilim:
I used to be a SuperRam elitist but since using the last 7 or 8 SmittyV kernels which have regular memory I've come to agree with a lot of others here that don't think extra free ram actually makes a difference. With my custom kernel settings I've not once had a point where I feel the SuperRam version has outperformed the NoMem SmittyV version, especially since I have modified minfrees. The benchmarks I posted on the last page are on stock ram. I was getting about 13287 on SmittyV 2/28 so I've been sticking to the SmittyV NoMem kernels because there is absolutely no risk of anything being broken from having it's allocated memory freed up like like there is with SuperRam. I'm a changed man lol.
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=2838735]aosp[/MENTION] we got a believer :thumbup:

As for the early suspend interactive ,

I by no means suggest switching to a different gov to resolve the issue . I want and need honesty , if it don't work it don't work . i feel that the .02 % battery saving your getting from it isn't worth the wakeup issue . I have no problem reverting it as its a simple self-contained commit , I was just giving it a fair chance

Anyways ive been working hard on mem management , I really want to do away with extra ram altogether