yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] szucsgf:
This didn't work. I remember when I first tried ondemandplus (odp) I noticed it liked to spend a lot of time at Max CPU. It's no different with the above setup. After some use it had spent 15 minutes at 1640 and 5 minutes at each of 1350 and 810. With Interactive I usually have about equal time spent at hispeed_freq and Max CPU. Perhaps some tweaking of odp can make it work like intended, but I'm going back to interactive.
[Samsung Galaxy Nexus] B@je:
No you didn't as you will see in trickster different governors have different options and those are the options you get for all three of the hotplug governors
[Samsung Galaxy Nexus] AutomaticFailure27:
For people who want a cleaner thread, there is this lil trick by clicking on the user's name
[Samsung Galaxy Nexus] antonio8297:
I haved two sod with vanir(last nightlies):

On v225

On v233

Kernel related problem???or ROM problem???

Thanks anarkia...:)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] angourakis:
anarkia1976, on the previous version I remember you said the GPU frequencies would change according to the load (valid for ondemand) or with the governor I choose for GPU. I tought this idea fantastic (specially because I rarely play any game on my phone) but now, on version 233 you removed it and fixed in 384 Mhz. What happened? Just want to understand =)

Best Regards
[Samsung Galaxy Nexus] szucsgf:
A bit more info if you could. Please tell us all your kernel settings and use the bugreport script instructions found in the first post.
[Samsung Galaxy Nexus] ak:
This is an excellent question for a fortune teller? :confused:
[Samsung Galaxy Nexus] natezire71:
[MENTION=3685904]anarkia1976[/MENTION]

It would appear the issue I was having with Wifi came back with v233. It worked fine on v225.

EDIT: Browsed through Github. Nothing that sticks out to me. Odd.
[Samsung Galaxy Nexus] Az Biker:
^^^bawahaha :rolleyes:

Slim + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] payas0:
Any idea what this means ?
[Samsung Galaxy Nexus] ak:
Normal.
[Samsung Galaxy Nexus] ak:
Azz .. at this point ... i dont know where is the problem.
[Samsung Galaxy Nexus] chikimonke:
I liked your original idea, so I'm trying it out myself. Using this page I've tweaked the settings to what I think will make it jump to 1640 only when absolutely necessary.

Min - 180000

Max - 1640000

Max Screen Off - 525000

Min Screen On - 180000

down_differential - 40 (Default was 54, making this number lower causes down scaling to happen faster. Down scaling happens when load is lower than up_theshold - down_differential, in this case 90-40=50)

inter_hifreq - 1350000

inter_lofreq - 810000

inter_staycycles - 5 (The higher this number, the more cycles the CPU (cycle length set by timer_rate) needs to be above up_threshold to finally be allowed to hit Max frequency. By increasing from 2 to 5 we're forcing it to do more work in the 810000 and 1350000 levels before jumping up)

staycycles_resetfreq - 800000 (has to be lower than inter_lofreq, if the freq drops below this number, the inter_staycycles counter is reset)

timer_rate - 30000 (equal to 0.03 seconds, how often it checks the CPU load. I upped it from 20000 to also try and keep it from jumping to 1640000 so quickly. this will probably need to be played with)

up_threshold - 90 (percent load that the CPU needs to be above to index the inter_staycycles counter by 1)

Let's see what happens :D
[Samsung Galaxy Nexus] payas0:
just curious, what does that mean ?
[Samsung Galaxy Nexus] antonio8297:
My bug report...

http://db.tt/QYqRfVZM

Rom vanir latest nightly

Kernel AK 233

My CPU freq

No undervolt

Problem: sod

With this i think you know...:D

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] szucsgf:
I played with only inter_staycylces and timer_rate but you've put a lot more thought into it then me. I'm going to run with your settings to see if this tames odp. Thanks!
[Samsung Galaxy Nexus] natezire71:
Could you send me an earlier version?
[Samsung Galaxy Nexus] ak:
sod = no last kmsg = i can do anything ... im sorry

This is the right way:

Step1:

Download script manager (Direct Link)

Step2:

Run as root /data/ak/create_bugreport.sh

Step3:

Open /sdcard/bugreport_YYYYMMDD_HHh_MMm_SSs.tar.bz2 and verify the presence of dump

Step4:

Collect these infos:

kernel version

rom version

governor

scheduler

freq cpu

freq gpu

undervolt

ecc ... ecc ...

short description of the problemStep5:

Submit On thread for the analysis

My CPU freq = where are?
[Samsung Galaxy Nexus] ak:
All the old versions are on the host server.
[Samsung Galaxy Nexus] ak:
boost interface = powerhal log
[Samsung Galaxy Nexus] antonio8297:
The freq CPU are this

La prima non l ho capita!! O.o

I don t know the first...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ak:
Please report problem only with stock settings (interactive and freqs).

Some phones didn't work well with 180 slot, you can try to use 350 and verify if the problem persist.
[Samsung Galaxy Nexus] OMFGNuts:
Why do you use sucha big Read Ahead Buffer?
[Samsung Galaxy Nexus] natezire71:
Er, could you send me a version between v225 and v233?
[Samsung Galaxy Nexus] nmlssit:
Yep thanks! But sadly my phone acts strange with sakuractive, don't know why.

» Tapatalk 2 on Cyanogen Nexus
[Samsung Galaxy Nexus] ak:
If you revert to 225 wifi work?

The only change is this:

Revert "board-tuna-wifi.c: add Imoseyon's random MAC ID bug that plagues some users. Also decrease startup_delay of the wifi interface from 70ms to 25ms (testing)."
[Samsung Galaxy Nexus] Khizar:
those were test kernels, not for public release :good:
[Samsung Galaxy Nexus] MBQ_:
Yep.

:good:
[Samsung Galaxy Nexus] omniatic:
Soft reboot just now...first one.

CM 10.1 nightly 05/02

233 kernel, all settings stock.

Interactive, row

Westwood

350min/700 max off/1200 max

Anything look unusual?

Thanks,

http://db.tt/nEGEWIWn
[Samsung Galaxy Nexus] DoesntPostAThing:
Hotplugging governors still aren't recommended in case of freeze right?
[Samsung Galaxy Nexus] MBQ_:
Basically.

A lot of users have reported freezes when using hotplugging governors. Which isn't anarkias fault of course, but to avoid freezes and stuff.. I'd stay away from hotplugging governors

I did have some good luck with both Sakuractive and Intellidemand though
[Samsung Galaxy Nexus] ak:
I have see a lot of this:

Line 2745: [ 717.042510] CPU1 is up

Line 2768: [ 721.588348] CPU1 is up

Line 2794: [ 722.788665] CPU1 is up

Line 2822: [ 723.619842] CPU1 is up

Line 2856: [ 727.546661] CPU1 is up

Line 2891: [ 729.791290] CPU1 is up

Line 2917: [ 730.996826] CPU1 is up

Do you use an app for control kernel?

Have you used another kernel before?
[Samsung Galaxy Nexus] antonio8297:
because i'm trying much value...
[Samsung Galaxy Nexus] MBQ_:
How? I know its a hotplugging governor, but it is pretty aggressive at the same time.
[Samsung Galaxy Nexus] omniatic:
Trickster for kernel control. However, I haven't done any tweaking to it yet.

Only using your kernels from AK70 to SKL233.
[Samsung Galaxy Nexus] frenchy714:
You can always go back to 225 if that was working good for you.
[Samsung Galaxy Nexus] Charmacas:
So far I get the following with OnDemandPlus:

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] ak:
Please, you can try to remove trick, reboot wipe cache and dalvik, reinstall. :D
[Samsung Galaxy Nexus] Invicta:
any other programs recommended besides trickster?
[Samsung Galaxy Nexus] LauraSakura:
Seconding this. My phone gives tons of SoDs if I use 180

GNex // Toro // CodeX // AK exp // Hue
[Samsung Galaxy Nexus] MBQ_:
Honestly, no.
[Samsung Galaxy Nexus] ak:
Free and cool ... no!
[Samsung Galaxy Nexus] natezire71:
Yes. On v225 it works.
[Samsung Galaxy Nexus] ak:
You have PM my friend.
[Samsung Galaxy Nexus] L-ViZ:
same here. raised it up because of having sods. now works perfectly.
[Samsung Galaxy Nexus] nmlssit:
Lags and freezes! I reflashed stock settings after the second time I had to remove battery cause freezing.

» Tapatalk 2 on Cyanogen Nexus
[Samsung Galaxy Nexus] samersh72:
great performance, very smooth, stock setting, carbon 1.5.2013 rom

great work AK :good:
[Samsung Galaxy Nexus] MaLiXs:
Why people keep post kernel setiing each business.. Why not write it on a Google doc and links it here... It a good way to keep it near too..

Send from my Pure Ak GNex
[Samsung Galaxy Nexus] natezire71:
You should make one for AK kernel. :P

Autocorrected from my GNexus

---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------

And you have a reply my friend. :p

It works.

Autocorrected from my GNexus
[Samsung Galaxy Nexus] SPyxOff:
Feedback

I'm back to leave a little feedback about AK kernel. It's funny how I can see huge differences between individual kernel builts.

I can tell 233SKL is the best of the 200 series. It shows in a phone performance mostly and I had a little bit of heat issues with 225.

Now is everything back again and it's running absolutely amazing. This kernel is saving my money, cuz I don't need to change :D

How happy I am to be part of your magic :good:
[Samsung Galaxy Nexus] X1111:
every thing works "fine + super smooth + too fast" => AK := the best kernel for GN ;

:)
[Samsung Galaxy Nexus] MaLiXs:
Each person should do it for himself

Send from my Pure Ak GNex
[Samsung Galaxy Nexus] Fenvarien:
Everything is running super smooth and stable here with SKL v233 :) :good:

Min 180/230, Max 1420. Interactive / CFQ. ROM: Rasbeanjelly.

Thank you for this great kernel! :thumbup:
[Samsung Galaxy Nexus] lesp4ul:
That was occured to me too on v225, but only one time. Stock setting only underclock to 180/1060.
[Samsung Galaxy Nexus] chikimonke:
So I've been doing a little more thinking about OD+ tweaks, I'm thinking we want MCP set to 0. My thought process is, by forcing more processes to run on a single core, you are driving up the load on that core, thereby causing the frequency to increase. If you leave MCP at 0, both cores can be used, and in theory, keep their loads lower, thereby keeping the frequencies lower. However, this is all just theory, and maybe two cores running at 810 for 2 seconds (random made up example) still uses more battery than 1 core at 1640 for 1 second (again, random) Also, I could be misunderstanding exactly how the MCP works as well.
[Samsung Galaxy Nexus] Invicta:
excuse me for the offtopic guys, but when the dev says flash kernel and fic permissions, whould i so it right away in the recovery or after the rom has loaded and then reboot and fix permissions in recovery?

i appreciate your help!
[Samsung Galaxy Nexus] schukje:
Im now testing newest purity ROM. And now gonna flash AK over it! Lets see how smooth this combo is!!!:);)

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] renuk11:
Hey I have never got good battery backup with ak. Don't know why. :( how many days will it take for a kernel to settle down? Should I wait for a while? I always test it just for a day.
[Samsung Galaxy Nexus] natezire71:
No, I mean: make a publicly accessible spreadsheet for AK kernel. Have it so you can post your username, settings, and any additional comments. So instead of putting them in this thread, it's all on one spreadsheet.
[Samsung Galaxy Nexus] omniatic:
Removed Trickster, wiped, reinstalled, will see if it happens again.

Thanks,
[Samsung Galaxy Nexus] samersh72:
usually i wait for the second full charge cycle.

but with AK releases......it is hard to wait ;)
[Samsung Galaxy Nexus] musashihatred:
I like 230 for battery.

I like 233 for more.cpu freq slots. And!!!!!! Smooth rotation.

It doesnt flicker even with pie :)
[Samsung Galaxy Nexus] PatimusXPrime:
This... Words escape me
[Samsung Galaxy Nexus] BlackJou:
So does anyone here have any ideas on how to tweak the hyper governor? Any tips are gladly appreciated

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] Sik-1:
Smh how about you read a couple post b4 and I'm sure you'll find what your looking for ....

Nothing against you personally but its crazy by the amount of the same questions that gets asked and the answers are literally a couple post b4 smh

Rather annoying
[Samsung Galaxy Nexus] zuko1989:
hotplug and swap problem

this mod don't work for me, and for SWAP i can't find any - zram_imoseyon.sh - in data/ak/backup

can someone help me?
[Samsung Galaxy Nexus] ak:
With new version zram work well without script.

You can enable with trickster.
[Samsung Galaxy Nexus] zuko1989:
OK, and for hotplug governor?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Sik-1:
Set both minimums and then turn on multicore=1
[Samsung Galaxy Nexus] dizzy1k:
Today after few hours after installed 233 kernel i had first rebot since i bought my phone ...idk if its from kernel or not ...it happened while i was entering in whatsapp app
[Samsung Galaxy Nexus] jeffcavicchi:
Got a hot reboot today on 233 too - not doing anything special, no changes except to the kernel. Only parameters changed in Trickster were FFC on and Anarkia color profile.

Hasn't happened since.
[Samsung Galaxy Nexus] schukje:
Purity with AK is awesome. All running smooth. Now moving back to codex for customisations. Smoothness is the same.

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] dizzy1k:
i`m downloading codex right now cuz i heard so much good things about it ... i`m on slimbean and i like it but.. that "Codex" seems to be great.
[Samsung Galaxy Nexus] ak:
I can't do nothing ... Follow the rules and make a post with all the infos.

This is a price you have to pay if you want over clock = you can have a little instability.
[Samsung Galaxy Nexus] Invicta:
latest purity and 233 is the most flawless combo for me until now, battery smooth and no reboots whatsoever and i had freezes with previous versions. Will see how it goes the nest days
[Samsung Galaxy Nexus] Wh1t3Rose:
Like Anarkia said he can't do anything if u don't provide logs.

Toro | Carbon | AK SKL
[Samsung Galaxy Nexus] ak:
You can use guide into op
[Samsung Galaxy Nexus] jeffcavicchi:
I know, I know - been on the road all day until now.

Log attached.
[Samsung Galaxy Nexus] nmlssit:
Link for Codex ROM?

» Tapatalk 2 on Cyanogen Nexus
[Samsung Galaxy Nexus] Wh1t3Rose:
Google is your friend

Toro | Carbon | AK SKL
[Samsung Galaxy Nexus] siealex:
CPU overclocking is cool, but where is the GPU one? I can't find it in trickster mod.
[Samsung Galaxy Nexus] sarkar1990:
Hardcoded at 384mhz!
[Samsung Galaxy Nexus] chikimonke:
I can be your friend too, but you really should just give a simple search first. :)
[Samsung Galaxy Nexus] Sik-1:
It has been reverted, too much complaints and really didn't do much for the phone, 384mhz is exactly where it should b :D
[Samsung Galaxy Nexus] sarkar1990:
Its on droid-hive. You can search for "droidth3ory codex maguro" on google. That should give you what you need.

However, don't forget to sign up there and thank droidth3ory even if you find the direct download link on google ;) :D
[Samsung Galaxy Nexus] ak:
???

Do you want cpu hotplug? :confused:
[Samsung Galaxy Nexus] xeonyxorich:
It's just that I find hotplug to be sluggish with frequency scaling and interactive with the ability to switch between frequencies faster. I think it would be nice if there was a mix between the two
[Samsung Galaxy Nexus] HereticSins:
Any recommended settings for core oc?

Finally got it to oc without it rebooting with 461!
[Samsung Galaxy Nexus] ak:
AK Interactive have cpu hotplug.

For verify:

connect usb cable

cmd windows

adb shell while true;do dmesg -c;sleep 1;done :cyclops:
[Samsung Galaxy Nexus] ak:
With my phone my max is +110, after this it reboot.

Do not stick this values at boot. :angel:
[Samsung Galaxy Nexus] ak:
<4>[ 4382.521514] CPU1: Booted secondary processor

<4>[ 4382.522674] Interactive - Screen ON Hot-plug!

<6>[ 4384.806243] request_suspend_state: sleep (0->3) at

12 08:42:06.675249956 UTC)

<6>[ 4384.806304] disable touch controls

<7>[ 4384.806304] Powered off touchscreen

<6>[ 4384.819519] cpufreq_gov_suspend : cpufreq_gov_lcd_

<4>[ 4384.819580] dhd_set_suspend: PM_MAX, proximity_val

<6>[ 4384.819854] DSSCOMP: dsscomp_early_suspend

<6>[ 4384.822601] DSSCOMP: blanked screen

<5>[ 4385.078277] CPU1: shutdown

<4>[ 4385.081787] Interactive - Screen OFF Hot-unplug!
[Samsung Galaxy Nexus] xeonyxorich:
Oh wow. Didn't know that. Thanks
[Samsung Galaxy Nexus] ak:
First page changelog:

* Governor loaded by defualt:
​

Interactive from 3.4.X Kernel (Default)

Ondemand 2.0, Sakuractive, Intellidemand 3.0, Conservative 2.0, Wheatley, Lazy, Hotplug, IntellidemandX, SavagedZen, InteractiveX, Adaptive, AdaptiveX, OndemandX, Userspace, Powersave, Performance

+ Add Early Suspend for:

Ondemand 2.0

Interactive 3.4.x

Intellidemand 3.0

+ Add Hotplug for all X Governor:

InteractiveX

AdaptiveX

OndemandX

IntellidemandX
​
[Samsung Galaxy Nexus] Abaddon:
thanks man. where's the new build/s? :S
[Samsung Galaxy Nexus] albsat:
I am enjoying the 461 new frequency. Let see how it gets with the battery life.
[Samsung Galaxy Nexus] ciprianruse88:
i've attached my settings with v461 latest test and my battery drain from over the night with sync off,wifi off,gps off,bluetooth off,3g network and i've got the same result as in previous 461 test...10% battery drain in 7 h off sleep.fwy last night i've charged my phone too 100% then used it untill 99% and then left it for test.maybe it needs another cycle so that the kernel settle up...i don't know...
[Samsung Galaxy Nexus] SahilC:
Hey, just came back from school. There is some noticeable battery drain. 5 hours, airplane mode, and no use, I got around 7-9 percent battery drain. I'll try 466 and let's see.
[Samsung Galaxy Nexus] ak:
new online

Last Exp Version: ak.466.42.berserk

Differential Changelog: Link

Github: Link
[Samsung Galaxy Nexus] SahilC:
Damn. This is really bad. On 461.

56 percent battery life and only 1 hour screen on time.

Trust me, I'm a very minimal user. No data, gps, etc. And I was on airplane mode for 5 hours during school as well.

I'll try 466 tomorrow and report.
[Samsung Galaxy Nexus] GCbard:
Benchmarks on 4.2 v466
[Samsung Galaxy Nexus] ak:
What configuration? :D
[Samsung Galaxy Nexus] ak:
461 deprecated ... switch to 466 please :fingers-crossed:
[Samsung Galaxy Nexus] ciprianruse88:
i am curious too :D
[Samsung Galaxy Nexus] GCbard:
my configurations are as follows:

Rom - JB Sourcery 4.0 pre-release 5

kernel: V466

GPU: 512

max freq: 1420

min freq: 172

Governer: Interactive with (above_hispeed_delay = 20000, go_hispeed_load = 50, min_sample_time = 80000, timer_rate = 20000, hispeed_freq = 1305600)

scheduler: deadline with 2048 read ahead buffer size

tcp congestion: westwood

wifi perm = on

content adaptive brightness = off

high perf. sound = 3

fsync = off

zram = off

color profile = franco

think that is every setting I can think off beyond what is needed for benchmarking.
[Samsung Galaxy Nexus] ciprianruse88:
i've attached antutu score with cpu at 1.4 mhz and gpu 512 mhz plus fsync off,zram off but after i've tested i wanted to change back to 384 mhz gpu and got a freeze followed by a reboot and the fu..ing fsync was off too :mad:.i've attached also last_kmsg...@anarkia,please if you can see kmsg file and tell me what was the problem i will be forever in you gratitude :).Thanks!
[Samsung Galaxy Nexus] chikimonke:
For those of you that are interested, SteveSpear just posted a new video on his G+ page showing off a new feature of the AOKP Ribbon that he's been working on. Looks pretty slick
[Samsung Galaxy Nexus] nmlssit:
I did, and it was not the same you just linked me, thanks!

» Tapatalk 2 on Cyanogen Nexus
[Samsung Galaxy Nexus] terminal13:
Hi deleted:thumbup:
[Samsung Galaxy Nexus] jeffcavicchi:
Last_kmsg posted 4 or 5 posts back.
[Samsung Galaxy Nexus] terminal13:
sorry bro late to the party:eek:
[Samsung Galaxy Nexus] jeffcavicchi:
No worries!

:good:
[Samsung Galaxy Nexus] bsmitty83:
I've also had alot of random reboots on any ak kernel I've ever used , all stock settings , atom ROM , seems to happen alot when on tapatalk or fb app , but also at random as well . had one while typing this too . i drop boxed the kmsg file. Even with all the reboots I'm still using these kernels ak ftw :thumbup:

http://db.tt/FiviATNM

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] szucsgf:
That looks like an mpu Watchdog reset. Assuming you're using default voltages, Try:

1. Increasing all mpu voltages by 25 or 50,

And if that doesn't work:

2. Increasing mpu min cal by 10 or 20
[Samsung Galaxy Nexus] jeffcavicchi:
Did you take a look at the one I posted a page or so back?
[Samsung Galaxy Nexus] bsmitty83:
Thanks for the look , i bumped mpu up +50 will see what happens , the only time i ever messed with voltages was when I'd oc , so I'm curious to see what happens on stock ak settings with your suggestion :beer:

Edit 1: got same reboot , but i still had sr on for mpu , gonna try it without

Edit 2 : seems like disabling SR for mpu and bumping volts up did the trick , thanks again for having me love this kernel all over again

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] szucsgf:
I did but I didn't know how to interpret it. Sorry.
[Samsung Galaxy Nexus] jeffcavicchi:
No worries - I have no idea what it means. Hopefully it is of some use to Anarkia.
[Samsung Galaxy Nexus] szucsgf:
My apologies, I was confused. Yours said mpu Watchdog reset as well. Try the same thing I told the other user a few posts back.
[Samsung Galaxy Nexus] adambala:
ak rulez......
[Samsung Galaxy Nexus] jeffcavicchi:
Thanks!
[Samsung Galaxy Nexus] matteventu:
With the Hyper governor, what is the best value for Multicore Power Saving (speaking about battery)?

0, 1 or 2?
[Samsung Galaxy Nexus] chikimonke:
In theory 2 is best for battery, as it tries to group as many processes onto one core as possible. That said, I'm working on something to see if forcing it to use 1 core at what will definitely be a higher frequency actually saves battery over the two cores potentially working at a lower frequency to accomplish the same tasks.
[Samsung Galaxy Nexus] matteventu:
The "for battery is better two cores in a lower frequency or one core at an higher frequency?" question is exactly what i was asking myself :D
[Samsung Galaxy Nexus] KemikalElite:
More Cores working less gives the same output with less battery consumption is better for Android.
[Samsung Galaxy Nexus] matteventu:
...so? xD

Better "0", "1" or "2" ?
[Samsung Galaxy Nexus] chikimonke:
Again, in theory, setting it to 2, meaning the most aggressive grouping of tasks onto one core, would save battery, as the 2nd core would able to be idle. But, as I said before, 1 core running at a higher frequency isn't necessarily saving you any battery when compared to the 2 cores running at a lower frequency. Sorry there really isn't a clear cut answer, but like most settings, give it a try yourself, if you like your results with one setting, then use that setting, if not, try a different one.
[Samsung Galaxy Nexus] cuzzinz:
Do you guys always flash cache and dalvik cache?

Sent by click....click....click....click.....click.......telekinesis
[Samsung Galaxy Nexus] chikimonke:
Clear it? No, no need.
[Samsung Galaxy Nexus] cuzzinz:
Wipe was the word I was looking for. Lol...I dunno why I said flash...

I had some lag after about a day of use on 233 so I reflashed the kernel and wiped both caches and things seem better.

Sent by click....click....click....click.....click.......telekinesis
[Samsung Galaxy Nexus] chikimonke:
More than likely you would have seen the same improvement with just a reboot to start with a clean slate of RAM.
[Samsung Galaxy Nexus] alohaitsdonovan:
Is ak 200 the most stable yet fastest version or should I try 225 ?
[Samsung Galaxy Nexus] B@je:
This is what I'm getting with the sakuractive governor
[Samsung Galaxy Nexus] Sik-1:
Should try v233
[Samsung Galaxy Nexus] 93foxgt:
Oldie but goodie.
[Samsung Galaxy Nexus] alohaitsdonovan:
Aight ,gonna download it but does it have OK battery stats?
[Samsung Galaxy Nexus] Sik-1:
Battery is all about your own personal usage and customizations