yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PatimusXPrime:
Ohhh dude that is a great question. I am by no means an expert on this stuff, I basically just read some articles and also some examples of IOPS (not FIOPS, fair IOPS) for SSD in the linux kernel and this is what I've come up with. That would be something to look into though.. I know there is something on the computer (i dont know exactly what) to measure throughput within the I/O device so perhaps there is something in android as well? AnTuTu may have something useful?

---------- Post added at 11:33 PM ---------- Previous post was at 11:26 PM ----------

http://static.usenix.org/events/fast/tech/full_papers/Park.pdf

here we go! a real resource! i have the feeling that the numbers are like you said, relative to each other. so 1 to 2 may be the same as 100 to 200. i'm going to try and read this document and see what i come up with... here we go...
[Samsung Galaxy Nexus] terminal13:
wow. thats some heavy stuff bro.
[Samsung Galaxy Nexus] PatimusXPrime:
so then by this logic, the default settings are perfectly fine? AnTuTu wouldn't be the best thing to gauge the performance then because it processes reads and writes separately and wouldn't have the best display of multitasking I/O... now i'm thinking out loud lol

does anyone else have ideas? i feel kind of dumb now for changing the settings when it basically did the same thing :P

seems to make sense no?
[Samsung Galaxy Nexus] chikimonke:
Good luck man, much appreciated if you can decipher something useful out of that. :fingers-crossed: That reading is well above my pay grade :D

---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------

What WERE the stock setting? :)
[Samsung Galaxy Nexus] PatimusXPrime:
i just loled in class, i think it was 3 1 2 2 so i'm going to try 4 1 2 2 and see what the results are.. i have a headache now by the way.. okay so let me read more, test more, ramble more, then post my new findings :D ill shut up now
[Samsung Galaxy Nexus] chikimonke:
I believe they were actually 5 1 2 2. Just changed scheduler, applied, and then changed back to fiops and that is what they were set to.
[Samsung Galaxy Nexus] PatimusXPrime:
OK! so this is the last thing i'm going to say about this! I believe what i said earlier about what each tunable means is correct. So that being said, you want synchronous I/O priority if you want the task to be done quicker with more priority and asynch if you want a lower individual task priority and want to do other things requiring I/O overhead. So 3 for async and 2 for sync (default) is perfectly fine because itll prioritize async 50% more than sync. If you want better multitasking (worse AnTuTu bench score) set async to 4 and sync to 2. Thatll prioritize async 100% more than sync. Marginal speed decrease but I noticed a slight multitask improvement..

leave write at 2 and read at 1. I don't think raising write higher will do anything good, i believe itll give too little priority over read and it wont work to your advantage.

BOOM, i'm done learning for a year. good luck dudes and feel FREE to call me a dumbass and correct anything and everything i have just said! :D
[Samsung Galaxy Nexus] branedamig:
Once I flash slim (you guys convinced me to try another one as I've been on carbon and atom), can I dirty flash updates without any issues? I ask because I hate starting over and gravitate to ROMs that dirty flash well.

Thanks everyone! Love this thread.

Sent from my ATOMic Gnex with AK Kernel on Tap2
[Samsung Galaxy Nexus] KemikalElite:
I have no idea why but 207 and possibly even 200 lags so bad that apps are unusable. It kept locking up on me. I tried wiping the cache and disabling all my background apps.

I tried resetting all the kernel settings back to Trickster Mod's default.

I flashed back to stock Xylon (MBQ's 04/22) and its back at full responsiveness.

With AK it feels like the governor scaling is lagging. As if the CPU is at 350mhz and it doesn't seem to want to pick up speed right away when I try to scroll.

Been using Anarkia kernels since January and haven't seen any severe lag like this.
[Samsung Galaxy Nexus] galakanokis:
Basically WEP secured routers are not supported with the new 3.4 drivers that are in the new lineup of kernels. It has been this way for some time and all the info you need is in the OP. If it works great but if not either change your router encryption or go to the Purity line of kernels.

Now on to the good stuff... Need to read up on those tuneables.

G man
[Samsung Galaxy Nexus] PatimusXPrime:
thats crazy dude, umm tried different governors and i/o schedulers? do you have any other mods installed? weird apps? battery savers? ect?
[Samsung Galaxy Nexus] Blackcrx:
yup, you can also dirty flash linaro slim and vice versa, but I always make a back up just incase.

my typical routine is to always make a backup before flashing anything. never had to revert back but it is a good security.

I know linaro slim was just released too, currently on official slim 4.2, havent had a chance to dirty flash linaro slim yet
[Samsung Galaxy Nexus] Az Biker:
See OP to properly report bug or issue in thread... There are a ton of people who want to help, but need specific info to make helpful suggestions :thumbup: :D

Atom/Carbon ROM + AK Diamond Series = Gyrannosaurus Nex!
[Samsung Galaxy Nexus] butikofer08:
Flash away....just know its never recommended and if you have problems don't bother reporting it or asking for help until you clean flash. :beer:
[Samsung Galaxy Nexus] schnob:
Is there anyone making a toro version of linaro slim? I could only find maguro.

Edit: I answered my own question. I found an older toro on Des-franco's server, not sure if he plans on updating.
[Samsung Galaxy Nexus] KemikalElite:
Thanks for your responses. I usually don't get replies in this thread often.

I actually think the issue is being caused by a memory leak in the systemui. I had recently switched to Xylon and it might be bugged from the systemui or something.

With Xylon I was noticing at least 150-200 MB less free RAM compared to standard AOKP. Also the status bar would disappear during web browsing randomly.

I thought it was the AK kernel because Xylon also is with AK by default.

From my experience I've used debug logs and logcat when I used to port ROMs to other phones but does lag even show up with logcat?

I always thought logcat only showed events and errors. I don't think it shows anything like memory levels or CPU load which would reveal lag issues.

EDIT:

Actual Issue Here: https://code.google.com/p/android/issues/detail?id=40961

Not sure if anyone in this thread had discussed it yet but its something about Google AOSP increasing the heap size.

Official CM and AOKP have already resolved this, other ROMs may not have yet.
[Samsung Galaxy Nexus] terminal13:
:D:D:D:D:D

Damn if you guys knew why I'm laughing. :thumbup::thumbup:

Edit: oh ya, this is a freshy rom install and complete restore from google....

AK/Codexed Beast
[Samsung Galaxy Nexus] wisefreakz:
Really a beast... I know...lol
[Samsung Galaxy Nexus] Kewyang:
Rubik or diamond, which one is better? :D
[Samsung Galaxy Nexus] Khizar:
every device is different so try them both yourself and see which is better for you :good:

Edit- just re-read your post why are flashing diamond? flash either SKL or Rubik, they are the latest, diamond is old...
[Samsung Galaxy Nexus] DoesntPostAThing:
I can proudly say my GNex is faster than a S4 :D Saw some of the reviews, and stutters everywhere. Meanwhile on the GNex, AOSPA + AK 207 + dalvik vm heap fixes = buttery smooth performance. No greenifying, stock AK 207 settings except lower temp. limit to 80 instead of 90. Absolutely flying right now. I also tried a few other kernels these recent days just for comparison. I found them to be all the same, even OC'd to 1.5GHz. That said, I enjoy some of the features AK offers, and the constant updates. Also, AK performs slightly better. But in general, the GNex is a great device, and is still one of the fastest Androids out there.
[Samsung Galaxy Nexus] joqsan:
What are you talking about when you said dalvik vm heap? And where can I find such a helpful feature
[Samsung Galaxy Nexus] musashihatred:
This :

https://code.google.com/p/android/issues/detail?id=40961

where in the previous versions of android, GNex have

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=384m

now it has 96m and 256m :) im testing this out currently.
[Samsung Galaxy Nexus] DoesntPostAThing:
Basically, someone posted on Reddit about something that could potentially fix the lag we've all been experiencing since 4.2. This one is more serious than the SysUI bug, which could explain why ROMs with the SysUI fix still get stutters everywhere. Anyways, this guy compared the dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize lines in build.prop with ones from the Nexus 7 and from 4.1. He noticed that heapgrowthlimit was 64m on the Nexus 7 and on 4.1, but 96m on 4.2. He, me, and many other Redditors, changed it to 64m, and also changed heapsize from 256m to 384m, and instant boost in performance. No lags anywhere, and back to 4.1 smoothness. Even better, because AK kernel obviously runs faster than stock kernel.

To fix it, it's simple. Just go into /system/build.prop and find the two lines. Edit the values. Or, download a build.prop editor and it will organize the fields to fill in for you. You'll have to do it every time you flash a new ROM, but hey, it works, and your device is now smoother than 99% of Androids out there, and it's running on 1.5 year old hardware.

EDIT: musashihatred beat me to it.

---------- Post added at 10:37 PM ---------- Previous post was at 10:09 PM ----------

No, previous versions actually had 64 and 256. 384 was on the N7, but it works well for the GNex too. I think it works on my S2 as well.
[Samsung Galaxy Nexus] musashihatred:
im using 384. rotation is damn smooth O_O
[Samsung Galaxy Nexus] Charmacas:
Yes, that's right. 64 and 256 are the right values for our GNex. It's because we are having less memory to actually use than the Nexus 7. GNex has about 690 MB from it's 1 GB and the Nexus 7 around 900 MB. Someone on another thread pointed out the theory that it's because the Nexus 7 has no front camera.

I've been running this 'fix' since yesterday and it is working better now. I also had one slowdown but this may come from another problem.

Waiting for the new kernel. I'm just curious what AK secretly does. ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Godra:
So, which values at the end are better? 64 and 256?
[Samsung Galaxy Nexus] Charmacas:
As I said: If you have GNex than go with 64 and 256. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] cmoG530:
Comment Removed.
[Samsung Galaxy Nexus] slayr76:
Rubik, diamond just messes up my gnex with lag, freeze an screen blackouts on rotation, these guys in here will say its rom related issue or i have messed up the kernel settings, its all bs i run default ak kernel settings an no other kernel makes my rom act retarded like diamond does, rubik works like a charm for me.
[Samsung Galaxy Nexus] cmoG530:
Lol. Rephrase your comment and everyone's device differs, in case you didn't know. ;)
[Samsung Galaxy Nexus] spacemanr:
Hey guys I'm still reading this thread but had nothing to report :), so I've been silence :). Today i had my first SOD after long time. Tried to get the last kmsg but there is no such file Info appears so it means that it's not the kernel issue. Trickster sets are:

with interactive governor, all the other sets default. Now I've just raised the min screen freq and will see. I'm on AK207 with purity 5.3.1.
[Samsung Galaxy Nexus] ak:
Perfect analysis :thumbup:
[Samsung Galaxy Nexus] Khizar:
i tried that but i dont notice any difference, maybe it could be cuz i didnt have lag in the first place

talk about ungrateful/rude users... every post that i ahev seen of yours you are bashing 1 dev or another, and JFYI countless user flash AK daily and dont have a single issue... i think your issue is either due to user error or your phone just doesnt work well with AK..

PS- next time try being a little poliet, stefano is doing this free, you arent paying him :rolleyes:

lol man i have seen that kid in other threads as well.. bashing the dev smh
[Samsung Galaxy Nexus] chikimonke:
What do you mean you didn't notice a difference? What is this blasphemy that you are spewing? Don't you know once somebody posts it on the internet it is forever the truth? :sarcasm off:

That said, I do THINK I am seeing a small increase in the overall fluidity of my phone, but that placebo effect is a ***** to see around. :D
[Samsung Galaxy Nexus] lordofazeroth:
Regarding using of mcp equals one or two:

Is there any improvement in performance or battery useage if >no< hotplug governor is used?

I can imagine there is improvement if there is high load on one core that is clocked up and the other core is nearly idle - but this is using hotplug gov.
[Samsung Galaxy Nexus] Khizar:
thanked you cuz this part made me LOL...and its been a while since i have laughed after reading a post on xda, the last time i laughed was when the mini-bath dude made his thread in the 989 section, haha that thread was a riot..anyway enough OT
[Samsung Galaxy Nexus] ak:
I have see lags with new dalvik settings.

Codex rom + ak v.224
[Samsung Galaxy Nexus] Nicuz95:
But for example I don't use mobile data, only at school
[Samsung Galaxy Nexus] odin13:
I reverted back to 457 kernel already :o

Rom is PA 2.99b7 in both cases...on 457 kernel i get 0.2% drain overnight :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] avyonix:
Nice, but I am sure you meant to say 2% overnight. If you did get 0.2%, I would like to know your kernel control settings, thx.
[Samsung Galaxy Nexus] Ashtrix:
which rom , baseband are you using ?

i need to recharge my phone after 14-16hrs of 3g (average data usage) & gaming btw ....
[Samsung Galaxy Nexus] Nicuz95:
3h on screen, not 3h of uptime :)
[Samsung Galaxy Nexus] pcphobic:
I 100% agree. Love the buttery feel of it.

But...I noticed the idle drain...a bit more than usual. Anybody noticed this? I am on Xylon build 010.
[Samsung Galaxy Nexus] odin13:
No i meant 0.2% per hour...sorry

I use adaptivex governor

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] ak:
Yes battery drain is little over the best previous release! :D

Confirmed if you use xylon 010 the last stable for me.

I have to verify.
[Samsung Galaxy Nexus] ciprianruse88:
i don't know about you guys but i don't really care about battery life.i charge my phone every night when i still have 30-20% and i've tested most of the kernels and with everyone of them i have to charge the battery every night but this kernel gives me the smoothest experience.it is the best :good:

---------- Post added at 11:16 AM ---------- Previous post was at 11:09 AM ----------

For better battery life unistall unnecessary apps,switch off gps and acount sync,use 2g network when you are not connected to mobile data,switch off wifi and nfc and then test your battery life.
[Samsung Galaxy Nexus] Ashtrix:
Same here :p !
[Samsung Galaxy Nexus] gwindlord:
Dunno if this helps, but 460 on 4.1.2 also has more battery drain, than the previous ones were, almost 1% per hour, and I could not find any wakelocks, eating processes or anything else. Going to try some maginc with wipes and check again.
[Samsung Galaxy Nexus] ak:
Its true battery drain is inside v460 .... :D
[Samsung Galaxy Nexus] ak:
I have a question:

Is there batt drain with v458? :thumbup:
[Samsung Galaxy Nexus] ciprianruse88:
Looking at ak kernels that i've downloaded i don't any 458...only 459 and 457 that are closer to 460:):confused:
[Samsung Galaxy Nexus] ak:
:D 457 :D
[Samsung Galaxy Nexus] mohaimed:
is anyone experiencing terrible battery drain in v460?? i am xenon RC3 and battery is horrible!!
[Samsung Galaxy Nexus] ciprianruse88:
Yes.in 457 the battery was a slight better but nevertheless the 448 was the best in battery/performance.i like more performance so i love 460:D
[Samsung Galaxy Nexus] odin13:
Standby drain on 457.42 kernel is excellent!! :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] ciprianruse88:
I will post tonight my battery drain with v460
[Samsung Galaxy Nexus] pcphobic:
Anarkia, previously I had amazingly good idle battery life on Xylon maguro 007 paired with AK kernel 448.42

I was getting an overnight battery drain of 2% over 6 hours 29 minutes of idle (during my sleep).

Bluetooth: Off

Wi-Fi: Off

Data connection: 3G

Data sync: On
[Samsung Galaxy Nexus] zandander:
:banghead::banghead:

:what:

:rolleyes:

:thumbdown:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chikimonke:
I'm on a roll today, 2 people on xda have admitted to actually lol'ing after reading a comment of mine. Maybe I should quit while I'm ahead...
[Samsung Galaxy Nexus] ciprianruse88:
216 idle drain.First cycle. :)

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] bunnahabhain:
LOL, are u using Purity? Airplane Mode? Wfifi and Data off?
[Samsung Galaxy Nexus] ciprianruse88:
Yes.5.3.1 ... again clean flashed it last night with 216:)

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] KemikalElite:
You haven't seen the flames of hell until you've

>used the OLD Facebook app

>on an HTC G1 with 2.3 Gingerbread

>525 MHz Single Core ARMv6

>over 2G EDGE

Lag isn't an extra 200ms it takes to open the app drawer. Lag is sitting there waiting half a minute for the Phone app to load so you can answer a call.

Haven't seen any instability until Google changed the stupid heap size. Ever.

AK still gives an extra 8-10 hours of battery time over stock CM.
[Samsung Galaxy Nexus] bunnahabhain:
Ok thanks, thought you'd be on jellybro ;)

I got very good battery life on Purity too. Hope to see the new AK Kernel soon. #207 changed everything for me
[Samsung Galaxy Nexus] ciprianruse88:
I tested Jellybro too...it is a very good rom :thumbup:

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] Doomhamma:
I'm on Codex aswell, but using SKL v207 ... After changing the dalvik settings, the phone feels much better ... It's still not on the 4.1 level, but closer ;)
[Samsung Galaxy Nexus] Charmacas:
+1 on that because I am experiencing the same here. Everything's a bit smoother now and slowdown become more rare. So I think it definitely an improvement!

SKL v207 runs nice btw. Impatiently waiting for the next update. I am curious what surprise is going to come with the next. ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] KemikalElite:
Same here rolled back to the old heap values and running great.

BTW v214 is out with new Xylon Nightly.
[Samsung Galaxy Nexus] Doomhamma:
Lol? How come if it's not public? :eek:
[Samsung Galaxy Nexus] okanb3:
I have some lags on new dalvik values. But i forgot stock values... Can anyone say these?
[Samsung Galaxy Nexus] KemikalElite:
Beta test version apparently.

heapgrowthlimit is 64mb

maxheapsize is 256mb
[Samsung Galaxy Nexus] Charmacas:
96 / 256

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Doomhamma:
Exactly! It's beta, so it shouldn't be out in the open ... Are you sure it's the v214 ?
[Samsung Galaxy Nexus] okanb3:
Which one? I don't get it.
[Samsung Galaxy Nexus] Charmacas:
Soo...

The actual stock ones which came with 4.2 where 96 / 256. Someone now found out that it was 64 / 256 in 4.1 and there were not lags.

So short:

Stock: 96 / 256

Optimised: 64 / 256

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] B1nny:
Could it be that he compiled the kernel himself? If you do that, I believe you can always get beta access. (correct me if I'm wrong please)
[Samsung Galaxy Nexus] ak:
Git is open and everyone can compile ak from source
[Samsung Galaxy Nexus] jeffkhlam:
i was using rasbean and with ak 207, i have constant wifi drop. wifi disconnect and reconnect when i wake up my phone; i now roll back to ak 200, wifi drop can be fixed by using static ip.
[Samsung Galaxy Nexus] SahilC:
Anarkia... Listen to me.. You are GOD!

I STILL HAVE 40 PERCENT LEFT! THIS IS AMAZING!

I'm Underclocked and FLYING! 207 is great.

Sorry for the caps :3

Sent from my Nexus Prime powered by AK goodness!
[Samsung Galaxy Nexus] ak:
With codex no problem of WiFi drops.
[Samsung Galaxy Nexus] jeffkhlam:
i will try, codex means codename?

---------- Post added at 11:39 AM ---------- Previous post was at 11:38 AM ----------

rom?
[Samsung Galaxy Nexus] Doomhamma:
Codex is a ROM that can be found on Droid Hive ... Use search, it's been discussed a few pages back, and even a link was provided ...
[Samsung Galaxy Nexus] ak:
v225

My error ... v225 public into 1 hour!
[Samsung Galaxy Nexus] matteventu:
Any preview of the changelog? :D
[Samsung Galaxy Nexus] ak:
https://github.com/anarkia1976/AK-tuna/commits/ak-4.2.2-exp31
[Samsung Galaxy Nexus] ak:
Originally Posted by jeffkhlam

i was using rasbean and with ak 207, i have constant wifi drop. wifi disconnect and reconnect when i wake up my phone; i now roll back to ak 200, wifi drop can be fixed by using static ip.

DO you use alternative launcher?
[Samsung Galaxy Nexus] ak:
new kernel

[4.2.1 - 4.2.2] DIAMOND (EXPERIMENTAL)

androidfilehost - Last Version:

dev-host - Last Version: AK.225.SKL.zip

Differential Changelog: Link

Features: Link

Github: Link
[Samsung Galaxy Nexus] matteventu:
Great! In download :D

From the changelog "Dmitry Shmidt - net: wireless: bcmdhd: Fix WEP-104 authentication" this mean that it support WEP encryption without restoring anything?
[Samsung Galaxy Nexus] adambala:
ak skl225 is loaded....lets see.....
[Samsung Galaxy Nexus] terminal13:
225 looks great so far sv.:thumbup:

AK/Codexed Beast
[Samsung Galaxy Nexus] c3v1t:
Flashed with last MBQ_ Xylon Nighlies, started OK!!!
[Samsung Galaxy Nexus] nitsua98:
Might wanna fix formatting in op :/
[Samsung Galaxy Nexus] schukje:
Best combo at this moment is Codex+AK or purity+AK

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] CommanderDuplex:
why still no 512mhz GPU :crying: ?
[Samsung Galaxy Nexus] peikojose:
Artifacts in the lock screen with 225 and today's cm nightly.

Flashed 207 and everything went back to normal.

BTW with 207 I got these results:

At the end I got 4:30 sot
[Samsung Galaxy Nexus] Hetalk:
I do see 512Mhz Option under GPU OC ..
[Samsung Galaxy Nexus] kaluoshi:
need to update gnex sign bro :) now it's a gnex with diamond's bones :D
[Samsung Galaxy Nexus] Butter Smooth:
There is. Just take a look at your Trickster settings
[Samsung Galaxy Nexus] kaluoshi:
if you are on rubik gpu steps are 192/307/384 :thumbup:
[Samsung Galaxy Nexus] mrchambo:
I would certainly cast a vote for Slim Bean 4.2 and AK v225!

MrC
[Samsung Galaxy Nexus] CommanderDuplex:
ok now i found it ^^

set it to 512mhz but i made still only 28fps in Nenamark 2 o.O ?
[Samsung Galaxy Nexus] SertaGE:
Hi

How to enable touch wake? What can i do?
[Samsung Galaxy Nexus] LauraSakura:
It's feeling somewhat better for me too. I'll have to wait a few days to see if it's just a placebo effect.

GNex // Toro // RootBox // AK exp // Hue