yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] lioux:
Galaxy Nexus stock ROM 4.2.2 with AK Diamond v207 inside. :)

My previous report was incorrect. The problem was not with hyper but rather a problem when resuming from suspend. The LCD does not recover.

The screen is off then I click on power button. The result:

----

<6>[35727.772399] request_suspend_state: wakeup (3->0) at 35730546289666 (2013-04-22 23:20:55.868085605 UTC)
<6>[35728.082794] DSSCOMP: dsscomp_late_resume
<7>[35728.082855] Powered on touchscreen
<3>[35728.083526] omapdss DISPC error: SYNC_LOST, disabling LCD
<3>[35728.083709] omapdss DISPC error: First SYNC_LOST.. ignoring

----

I click a second time. Result:

----

<6>[35729.043304] request_suspend_state: sleep (0->3) at 35731817194336 (2013-04-22 23:20:57.138990275 UTC)
<7>[35729.047637] Powered off touchscreen
<6>[35729.060394] DSSCOMP: dsscomp_early_suspend
<6>[35729.066772] DSSCOMP: blanked screen

----

If I keep clicking the power button, the logs loop between the "Powered on touchscreen" and the "Powered off touchscreen" logs.

The only relevant message I could find was http://lists.linux-foundation.org/pipermail/linux-pm/2011-April/031029.html with the following proposed "fix":

---------

- CONFIG_FB_OMAP2_FORCE_AUTO_UPDATE=y

- the following patch

diff --git a/drivers/video/omap2/dss/dispc.c
b/drivers/video/omap2/dss/dispc.c
index 8b3ac80..a188732 100644
--- a/drivers/video/omap2/dss/dispc.c
+++ b/drivers/video/omap2/dss/dispc.c
@@ -2784,7 +2784,6 @@ static void dispc_error_worker(struct work_struct
*work)
bool enable = false;

DSSERR("SYNC_LOST, disabling LCD\n");

for (i = 0; i < omap_dss_get_num_overlay_managers(); ++i) {
struct omap_overlay_manager *mgr;
mgr = omap_dss_get_overlay_manager(i);
@@ -2815,6 +2814,9 @@ static void dispc_error_worker(struct work_struct
*work)
if (enable)
manager->device->enable(manager->device);
}
+
+ dispc_enable_lcd_out(false);
+ dispc_enable_lcd_out(true);

---------

I also found another "issue" on logcat

E/Tuna PowerHAL(1238): Error opening /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq: Permission denied
E/Tuna PowerHAL(1238): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device

which is referenced at https://github.com/edoko/AirKernel_GN_JB/issues/1 with the following commits as possible fixes:

https://github.com/edoko/AirKernel_GN_JB/commit/591f90ee64224287f360205f6ec14057b88a7701

https://github.com/edoko/AirKernel_GN_JB/commit/be6ee99fe4380b6b1a50e15c4bdb3cdd719620fc

https://github.com/edoko/AirKernel_GN_JB/commit/a94e7cf81096fab2a8625e1ffaae0853a80e77b2

https://github.com/edoko/AirKernel_GN_JB/commit/1085a87765acabfdf55577e4c844a6d4609a6eb2

though I fail to see the relevance of those commits against the cpufreq problems. Well, we can always ask the fellow AirKernel developers about it. I know I will. :fingers-crossed:

Relevant Air Kernel post: http://xdaforums.com/showpost.php?p=40598815&postcount=1172

Relevant MiNCO post: http://xdaforums.com/showpost.php?p=40599367&postcount=4254
[Samsung Galaxy Nexus] galakanokis:
Do you have to log in to see this DT Droid X ROM? I cannot find it on the site.

No Complaints with 207. 207 with Slim 4.2 is golden.
[Samsung Galaxy Nexus] Sveke:
Nah.. Its under droid theory development section.
[Samsung Galaxy Nexus] galakanokis:
D'oh!
[Samsung Galaxy Nexus] zandander:
Just flashed Codex and the test kernel. So far so good!

:D:thumbup::cool:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mikey:
Don't do that again please

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] MBQ_:
Yes sir.

Post has been edited! :good:
[Samsung Galaxy Nexus] lordofazeroth:
because it was suggested to avoid lag - it should be the workaround.

Although I have none.

I got a no boot-past-skull today with the v200 which was working before :(

Android Revolution HD + Quicksettings Mod + V200

There was a statement we do not need lagfix anymore:

http://xdaforums.com/showthread.php?p=39727260&highlight=lagfix#post39727260

I did a trim before and then rebootet with the script above.

Could this be the error?

What happened to my phone?

Its not working with v200 anymore and I didnt use lagfix or the script...

Installing via sideload is the same as copying the zip to sd and install via choose zi, right?
[Samsung Galaxy Nexus] samersh72:
Amazing battery life on v207 PA. All stock settings! I got 0.1% per hour drain over night :cool:
[Samsung Galaxy Nexus] DoesntPostAThing:
Which version of PA? How smooth is it? Also SysUI RAM usage?
[Samsung Galaxy Nexus] yodanutz01:
where is CodeX rom ? :D
[Samsung Galaxy Nexus] schnob:
Go to the Droid Hive forums and search for Codex. It shouldn't be too hard to find.
[Samsung Galaxy Nexus] shanp7780:
just look under DT don't look under g-nex

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] samersh72:
PA 3.16 very smooth :thumbup:
[Samsung Galaxy Nexus] :
v207 is smooth and battery friendly I'm on 71% for 9hrs now. Sorry can't post any screenshots since I'm at the office. :highfive:
[Samsung Galaxy Nexus] lordofazeroth:
Help anybody?
[Samsung Galaxy Nexus] MBQ_:
Not bad so far. ;)

Pretty heavy usage too.
[Samsung Galaxy Nexus] TnK8iD:
Thanks for all your amazing kernel, my Gnex with purity rom + AK kernel is so smooth e reactive, Anarkia you are great
[Samsung Galaxy Nexus] ciprianruse88:
on v460 just got a long freeze followed by a long waited reboot :).maybe because i've oc cpu to 1.5 mhz with mpu at 110 but i am using it this way since last night or maybe not.either way i've attached kmsg.zip because the .txt file has around 1.5 mb :good:
[Samsung Galaxy Nexus] ciprianruse88:
i'm eager for your report :good:
[Samsung Galaxy Nexus] Nicuz95:
I don't know if I will discharge all the battery because I'm studying, for be sure I'll attach screenshot at 50% ;)
[Samsung Galaxy Nexus] Nicuz95:
Very good results! :D
[Samsung Galaxy Nexus] ciprianruse88:
Indeed:good:
[Samsung Galaxy Nexus] ak:
Mmm ... I dont see real problem into log.

Do you have last_kmsg from /proc dir? :D

Thanks a lot For your great support :thumbup:
[Samsung Galaxy Nexus] ciprianruse88:
Yes.it is from proc dir:good:
[Samsung Galaxy Nexus] Ashtrix:
The good news is AK has the best scores in Metal @ Vellamo - 455 (forgot the settings) , while AIR was at 380 , Lean - 400 :victory: :good:

but the 460 version had my CM10.1 Kang (Jellybro) frozen / looped at the starting apps , i had tried wiping init.d and re--flashing the rom , wiping apps ...still didn't get it booted , for now i'll stay on 460.42 version !! :rolleyes:
[Samsung Galaxy Nexus] sk8oldschool74:
Which version is this 4.1 or 4.2??? Are people having problems w/ 4.1 v460???
[Samsung Galaxy Nexus] TheMorpheus:
Me too... I tried with PA, same result!
[Samsung Galaxy Nexus] Nicuz95:
It is Android 4.2.1
[Samsung Galaxy Nexus] Ashtrix:
I think the users with AOSP based source code likes of Xylon , Xenon are not having problems , maybe due to the RAMDISK :rolleyes:,

& with francoAIR kangerade @ 1.8xxGhz , 1.3Ghz i got 549 ,430 scores in Vellamo Metal !!
[Samsung Galaxy Nexus] ak:
I have wrote into previous post with cm10.1 And PA dont work well AK + these roms.

10.1 For now not official And not so stable.

What are the problems For 4.1.2 kernel?
[Samsung Galaxy Nexus] ak:
PA is aosp like xylon dont have ramdisk Of cyano. I dont know what is the problem.
[Samsung Galaxy Nexus] sk8oldschool74:
Color and reboots... that is the only reason I recommended trinity color...;):)

I'm on fnv 4.1.1 v008 which is an asop ROM...
[Samsung Galaxy Nexus] ak:
Reboot?
[Samsung Galaxy Nexus] ciprianruse88:
If you have reboots post last_kmsg file via root explorer from proc/last_kmsg or via adb and as for trinity color you can chose it via trickster app from market
[Samsung Galaxy Nexus] ak:
... I don't know what is the problem ... :eek:
[Samsung Galaxy Nexus] ciprianruse88:
V460 is the smoothest release by now and very stable.:good:
[Samsung Galaxy Nexus] sk8oldschool74:
Me either I was getting them on fugumod which is upsetting as I'm trying to run either ak or fugumod... :(:(:(
[Samsung Galaxy Nexus] L-ViZ:
+1

running it for a few days, new daily driver :) everything running perfectly :)
[Samsung Galaxy Nexus] payas0:
hi guys .. just after flashing, im having problems ..

upon fresh boot of my nexus, everything seemed normal ..

cores plays at 350 when not doing anything ..

but once i set up my Trickster ..

i set min. 230, max 1200, max off 700, min on 230.

governor: Hyper.

then once i save the settings, the problem starts ..

my cores are stuck at 1200Mhz even when im not doing anything ! been watching it for minutes now, i already did cache and dalvik wipes but it still stuck at 1200Mhz ..

why ?
[Samsung Galaxy Nexus] ciprianruse88:
Switched to ondemand governor plus gpu powersave and BAM!!!...Perfection! Super idle drain ;)

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] ak:
rom?

previous kernel?

others app for control?

unistall trickster ... recovery clear dalvik cache ... reboot ... install trickster.
[Samsung Galaxy Nexus] ak:
you have flat line .... this is normal? :D
[Samsung Galaxy Nexus] ciprianruse88:
Alien technology :D

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] payas0:
PA3.16.

from AK200.

just Trickster ..

ill try your suggestion and report immidiately ..

for the record, i just had a really clean reflash yesterday,

reflashed 4.2.2 Stock Image, flashed PA3.16 then flashed AK200. everything was great.

until i flashed 207 today ..
[Samsung Galaxy Nexus] Rimher:
Probably battery's dead after feeling too much awesome
[Samsung Galaxy Nexus] payas0:
everything went back to normal after doing what you said ..

thank you ..

is that a Trickster issue ?
[Samsung Galaxy Nexus] ak:
you dont have to search where is the problem ... it can happen. :angel:
[Samsung Galaxy Nexus] slAsh_wInd:
Connect to a wifi network or turn on your data connection, connect to a connection will fix it.

The other option is set on boot in Trickster mod > 25s, I set 30s and leave the phone idle in this 30s, it working, not recommend use your phone in this time. Use your phone in this delay seconds will make your phone have problem again.

I have this problem with all ak kernel, all rom, problem maybe because ramdisk:

https://plus.google.com/116709542966452959662/posts/QqtE3VkanPd

With lastest Trickster mod, set on boot delay 0s fix it, try many times before and now it work :(
[Samsung Galaxy Nexus] hurte1:
Is it normal for Hyper Governer to not use the the, 525 and 700 frequencies?
[Samsung Galaxy Nexus] ak:
This is franco ramdisk, ak dont have sleep setted.
[Samsung Galaxy Nexus] ak:
Yes you have to do a fine tuning! :fingers-crossed:
[Samsung Galaxy Nexus] hurte1:
Okey thanks for the quick answer. :D
[Samsung Galaxy Nexus] payas0:
i don't do "set on boot" .. i never do that .. :)

i feel safer setting it up on every boot .. :)
[Samsung Galaxy Nexus] dominatore22:
With 207 battery life is AMAZING!!
[Samsung Galaxy Nexus] slvrarrow:
Hi AK, have you a link to latest test from G+? I cant see it on your G+ page? Thanks
[Samsung Galaxy Nexus] a5pe4:
You feel safer? Why...?
[Samsung Galaxy Nexus] terminal13:
+sv ak 212 crash and burn logs up on +

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] slvrarrow:
have you got a link to 212?
[Samsung Galaxy Nexus] Sik-1:
No you may not ask, if you aren't in the group you have to wait for public release
[Samsung Galaxy Nexus] cimdrap:
what's the difference between rubik16 and ak207? are they similar?
[Samsung Galaxy Nexus] cubsfan187:
207 is experimental and has "more" features. Rubik is the stable version.
[Samsung Galaxy Nexus] cimdrap:
yes i know that, i would like to know the main differences. Anyway i saw rubik is based on ak108
[Samsung Galaxy Nexus] musashihatred:
Nothing really. If you want a stable one get rubik. If you want to test something up to date go for ak's. If it is released stabled, rubiks is going to get compiled. :)
[Samsung Galaxy Nexus] cimdrap:
ok i'll go for rubik then....changing often the kernel and checking for the new pgm compatibility is driving me crazy. I'd like to see rubik in goo.im just to be always updated
[Samsung Galaxy Nexus] lesp4ul:
Eh, i tried to full & complete wipe and reinstall PA again + AK v207 (28 mar) after 1 minute idle, look
[Samsung Galaxy Nexus] Doomhamma:
Why is everyone so opsessed with RAM?! I really don't care how much free/used RAM I got, as long as my phone is working as it should! Anarkia, thx to your awesome kernel - my phone works like a charm! Thank you on that! And the rest of the crew that's making a fuss about free RAM, go do it somewhere else!
[Samsung Galaxy Nexus] billouetaudrey:
I want add, EXP is stable too if you use stable features ;) ( Stable Governor )

Envoyé depuis mon Transformer avec Tapatalk
[Samsung Galaxy Nexus] sajty:
systemUI in Xylon 2.5.0 took more than 100MB for me.I dont care about free RAM,but more than 100MB only for systemUI is really too much.Now i am running XenonHD and systemUI takes 50MB...
[Samsung Galaxy Nexus] Doomhamma:
Was your phone lagging when systemUI took 100 MB of RAM?
[Samsung Galaxy Nexus] sajty:
Yes,at certain points.Battery usage was also too high.systemUI took 10% of battery.
[Samsung Galaxy Nexus] pagratios:
Which is governor more battery friendly, hyper or interactive?
[Samsung Galaxy Nexus] Az Biker:
No diff than folks trying to squeeze as much as possible out of a charge: it's the challenge of fine tuning our phones. How many folks REALLY need 18 hrs unplugged and 4 hrs sot? It's the golden chalice because 99% of people who root want to get the most out of their phones. More efficient use of Ram is just another benchmark people use to evaluate how fine tuned their phone is... Just because it's not interesting or important to you doesn't mean it isn't to a large percentage of those here...

Atom/Carbon ROM + AK Diamond Series = Gyrannosaurus Nex!
[Samsung Galaxy Nexus] Doomhamma:
I never had those issues on any ROM that I've tried ... and I did try lots of them ... are you sure that a certain app was not interfering with something? And also, if you'r not using your phone a lot, if it's mostly in standby ... Then systemUI might appear ... For instance, I didn't use my phone a lot today at work, and it showed that Wi - Fi took 8 % of my battery - it just showed that it was running for 9h, CPU total 0s ...

---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------

The point was to transport the chit - chat somewhere else, Anarkia explicitly asked that the talks about everything else besides the kernel were discussed somewhere else ...
[Samsung Galaxy Nexus] ciprianruse88:
Interactive but i recomend to put gpu gov powersave ;) .now I am testing ondemand and gpu powersave and it's a very good balance between battery and smoothness

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Khizar:
the reason they are obsessed is cuz 99% of android users just dont understand that linux isnt like windows, in linux free ram = wasted ram

Edit- lol and if anyone doesnt know android is linux

interactive
[Samsung Galaxy Nexus] bluewhite79:
Looking for some help with making the system UI smooth. I continue to get lag when I press the home button. Basically, the wallpaper shows up and then the icons and widgets load. This happens quite often and I'm simply looking for suggests on how to make that lag go away. I also get lag when loading keyboard and in Google Now.

I have TCP congestion on highspeed.

Read ahead buffer at 512, scheduler on sio.

Governor was on Interactive, just now changed to ondemand (so I'm testing ondemand). Overclocked to 1.35ghz
[Samsung Galaxy Nexus] PatimusXPrime:
android is linux? i thought it was a lesser spin-off of iOS? i mean apple is the BEST THING EVER OMG OMG...

i seriously hate apple and everything with an "i" in front of it.. except maybe iRobot, that vaccuum is pretty cool :P

sorry off-topic.. anyways,

yes they are right, having little RAM left is OK. apps are stored in memory and linux has a lot of processes in storage but they arent all running at the same time.

as far as gov battery goes, hyper is really awesome. it was the best for me with v99 and now has gotten more smooth with less battery but if you change the powersave_bias to 125 or 250 you'll get some better life out of it with no side-effects with 125 and some slow down at 250. try it out!

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

hmm.. so like when you hit home it takes a long time to load the icons? what launcher are you using? it happens to me SOMETIMES on nova pro. even though i set it to aggressive home so it stays in memory lol.. try changing i/o to CFQ to test. CFQ literally takes one request at a time and finishes it in the order they are entered. sucks for downloading things and browsing the phone but i like to use it to see whats going wrong lol..

try hyper too, its like ondemand onsteroids lol.. that should be a governor name!
[Samsung Galaxy Nexus] mikeblock:
Then shouldn't this be talked about elsewhere?
[Samsung Galaxy Nexus] szucsgf:
I had this experience when System UI Ram usage went beyond about 60mb, or after about 18 hours without rebooting. Try restarting sys ui (or just rebooting your phone). If problem goes away and reappears after several hours of usage this may be your issue.

Anyway this isn't a kernel problem. You can use this thread for more info:

http://xdaforums.com/showthread.php?t=2178962
[Samsung Galaxy Nexus] mikeblock:
Then shouldn't this be talked about elsewhere? Gets tiring reading about something I can't flash...
[Samsung Galaxy Nexus] bluewhite79:
Thanks, I'll try that. It just did it again though. I was browsing through Google+ and hit the home button.

It took like 2-3 seconds to leave G+ and load the WP and then another 2-3 seconds to load icons and widgets. That was with the ONdemand governor.

I'll try CFQ here for a while.

I'm using CM10.1 launcher. Tribuchet?)
[Samsung Galaxy Nexus] lesp4ul:
Hey you don't understand about 4.2.2 memory leak problem. less free ram if it optimised for cache so it will not be a problem. If you happy with your phone then GOOD! Not all people have the same behavior and normal memory usage as yours. Did you saw i complained AK works?? NO! I tried to install same PA rom and apps on both Nexus 7 3G and Galaxy Nexus, Nexus 7 PA doesn't has the prob. Mine has! And it started to lag after some usage, this did not happen on 4.1.2 and this is my discussion with ickboblikecheese, he knows that so don't be like an ass.
[Samsung Galaxy Nexus] PatimusXPrime:
dude don't even go there. just leave it alone. trust me lol

i have never used Treb, even when i ran CM on my Dinc2 lol so im not sure. if you have no avail with CFQ then try downloading Nova, you can import your settings right into there and give that a shot! there's an option under the "Advanced" tab to keep the launcher in memory. that works well for me. good luck my dude!
[Samsung Galaxy Nexus] szucsgf:
To clarify:

1. private betas are normally discussed on the private G+ page, but they are sometimes mentioned here because many of users of this forum are using beta kernels. It's only natural.

2. Anyone who'd like to be a beta tester can apply. See MBQ's signature for details.
[Samsung Galaxy Nexus] PatimusXPrime:
to anyone who's using atom v13, what do you think about the battery with v200 or v207? i feel like ive gotten better life on v99 and atom v12. also i asked htis a while back but what makes the battery drain super fast from 100-90 then normally from then on? it has always happened to me but with atom v12 and ak v99 it didnt for a while lol it was awesome...
[Samsung Galaxy Nexus] bluewhite79:
If it's not a kernel problem, then how does one fix this? wait for a another stable release of CM?
[Samsung Galaxy Nexus] Doomhamma:
Look dude, I'm not gonna argue here and go waaay off topic ...

I'm using Carbon - which has the memory leak fix, if you think PA doesn't have and you want it - switch to another ROM

The whole point of my post was, that this thread is not ABOUT PA, or RAM, or memory leak problems ... NONE of that is related to AK kernel, so talk about those things somewhere else, and keep this thread clean!
[Samsung Galaxy Nexus] happymonk:
75MB of free RAM and I'm good because I have ak.kernel v207 with purity 5.3.1.
[Samsung Galaxy Nexus] terminal13:
Sorry for causing the beta test fiasco up above. Ill leave it on g+. And btw generating crash logs for beta kernels that don't provide info is something that gets frustrating for dev and testers. ;)

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] safendi:
skl 207 is super... thank's anarkia... is your best kernel..... è il tuo kernel migliore, mai visto un kernel così
[Samsung Galaxy Nexus] Az Biker:
You live and learn :D The irony is: one off topic comment is made, then a dozen 'keep the thread clean' responses are posted... (further clogging up the thread) If the intention is to keep the thread clean then say "ram is OT, take it to chit chat thread" and drop it.

... and 207 is best kernel on my phone in a while! Both Carbon and Atom love it :D

Atom/Carbon ROM + AK Diamond Series = Gyrannosaurus Nex!
[Samsung Galaxy Nexus] lesp4ul:
That's what i mean bro, okay sorry for OT , i just posted a systemui low ram usage sshot for ickboblikecheese and else started to judging but even don't know what i posted for. Now back to kernel topic.
[Samsung Galaxy Nexus] terminal13:
Amen brother.:thumbup:

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] SahilC:
Would setting GPU governor to powersave put more load on the cpu? And would that in turn reduce battery life?

Sent from my Nexus Prime powered by AK goodness!
[Samsung Galaxy Nexus] madhavs:
If it's reduces battery life then whats the point in naming that governor Powersave :highfive:
[Samsung Galaxy Nexus] SahilC:
AHA. Me idiot. :S

Thanks bro!

Sent from my Nexus Prime powered by AK goodness!
[Samsung Galaxy Nexus] paarthdesai:
i don't know the regular battery life on nexus as i have this phone from the past two days

i am using ak kernel diamond and carbon roms

i got about 5hrs of battery life with 2hrs screen time

so is it normal or i am getting less battery backup? :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrissurra:
Same here with 200 or 207 I had fast drain on Atom v13 right around 1.7 -2.3% an hour in sleep. I went back to 99 and Im back to .07-.10% per hour. Everything syncing, gps on and a bad signal here.
[Samsung Galaxy Nexus] szucsgf:
The faster discharge at about 100%-90% and from about 20%-0%, and about constant discharge from about 90%-20%, is a characteristic of lithium ion batteries. Google "Lithium ion discharge curve" and you will see many graphs that begin with a steep slope, flatten out, and end in a steep slope again.

I don't know the reason for this pattern, but thought I'd share.
[Samsung Galaxy Nexus] cubsfan187:
I'll say this, if Cylon 801 had half the options (gov and schedulers and such) as the newer ones, I would have never left that kernel behind. That (for me and my phone) was by far the best one made. Not saying anything bad about the newer kernels at all. Just a personal observation.
[Samsung Galaxy Nexus] sarkar1990:
That actually depends on what your phone has been up to in those 2 hours. ;)

I get like anywhere between 7 to 13 hours on time with around 3 hours OST.

And I use my phone quite heavily with 3g on always, sync on, gps on and using Lux.

No over clocking, underclocking or undervolting
[Samsung Galaxy Nexus] tuemdeluxe:
I thought the same about Cylon 734, one version before 801 which didn't work well with my phone. Actually I was using 734 until yesterday, but skl 207 is the first kernel I ever used that actually feels even faster than 734. I thought it's not possible but for me this one beats everything that has been made before!
[Samsung Galaxy Nexus] Kewyang:
I just flashed this rom, the color setting is bad, very dark.. The default setting in trickster already best for battery saving?
[Samsung Galaxy Nexus] sam45:
Change it in trickster, not every phone has the same AMOLED screen.

(I use the franco setting)