yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] stevensoaj:
It's actually deadline, row, and cfq. Sio is not included because franco.kernel doesn't feature sio at all.

These are the tweaks that Osm0sis (and many others) came up with and yes, it is specific to these three because every IO Scheduler has different variables to tune, so they don't carry over to other schedulers. If you look at the script, you'll notice that there are different settings for deadline, cfq, and row. :good:
[Samsung Galaxy Nexus] splus:
I apologize in advance - I haven't been following the thread very much due to its extremely fast pace.

I'm still on older AK 734 kernel and have tried the new Diamond 099 and then saw that the GPU is now fixed at 384 Mhz in all newer kernels.

Can someone tell me what is the reason GPU can't be OC any more to 512 Mhz?

I mean, I really notice the difference in scrolling smoothness in different apps between 384 and 512 Mhz GPU, it's not placebo, it's clearly noticeable difference, so I'm just trying to understand why has GPU been downgraded in newer kernels?
[Samsung Galaxy Nexus] MBQ_:
Please, use the search button. It has been asked, and answered on more than one occasion. A simple search should suffice.
[Samsung Galaxy Nexus] Az Biker:
not knowing exactly what to search for I'm really not getting anywhere... Anyone feel like educating me on this '1013'?

Atom + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] szucsgf:
http://xdaforums.com/showthread.php?t=626210

I hope that helps!
[Samsung Galaxy Nexus] namtombout:
http://xdaforums.com/showthread.php?p=39450511

There may be more reasons...

Scent from my bud
[Samsung Galaxy Nexus] splus:
I did, and saw that there's a lot of discussion about it but no real answers.

Just some users defending the move to lock the GPU to 384 Mhz with "512 Mhz isn't really needed unless you do heavy gaming" or "512 Mhz drains too much battery".

I thought this is a well know thing - there was plenty of research on other threads about battery difference between 384 and 512 Mhz GPU, and has been established that the difference in battery drain is very small, almost negligible.

And what's wrong with having a choice??

If someone prefers 384 Mhz then just don't move the slider up to 512 Mhz and end of story.

But this way this very good kernel now has an inferior graphic performance in most apps. It's easy to compare the scrolling in most apps and see the difference...

I'm not being negative, I'm just sad and don't understand why my favorite kernel now has lower performance than before...
[Samsung Galaxy Nexus] Nephilim:
The reason is that there is a very very low volume of people that need 512, there is nothing "inferior" about this kernel, games for the most part play just as well. There is a noticeable battery drain between 384 and 512 as well unlike between 307 and 384.. The biggest problem is that most devices do not play nice with 512 oc'd gpu unless Smartreflex "CORE" is turned off, and most noobs do not know that so this thread is filled with dozens of people asking why their Gnex can't handle 512mhz gpu rather than following the rules and searching when it's been answered hundreds of times already. Even then some devices outright just do not work with 512 with CORE set to off.

384mhz is a happy medium that works great with all Gnex devices and does not have any battery difference from 307mhz.

If you feel this kernel, which is better than all others, is "inferior", I suggest you try a different one. Have you even tested games with this kernel? Or are you just making your judgement off of the lack of option to set the GPU where you want it? On the last few test betas there are actual governors being integrated for the gpu itself. I suggest you try Diamond v108 out before claiming 384mhz can't handle games.

And finally, Your favorite kernel does not have lower performance than before. If you think that the tiny difference in gpu boost between 384mhz and 512mhz is enough to give the kernel itself lower performance you really do not have much knowledge on technology or how kernels work.
[Samsung Galaxy Nexus] tuemdeluxe:
Personally I also prefer the 512 mhz GPU but every devs does his choices, that's completely fine.

Everyone has plenty of other options to choose from.

On a side note, I went back three times already from Diamond kernels to Cylon 734, which FOR ME is unbeaten so far in terms of speed and battery life, so maybe you don't do anything wrong with staying on 734. It's harder than it sounds if you see new versions almost every day though :thumbup:
[Samsung Galaxy Nexus] kr3g3r:
made a new AK boot animation

wanted the NEXUS logo to be the crossbones for anarkia;s skull logo
[Samsung Galaxy Nexus] 91franz:
Which is the app for monitoring the battery you all use?
[Samsung Galaxy Nexus] Nephilim:
Betterbatterystats off Play Store. :good:
[Samsung Galaxy Nexus] EvilDobe:
Or off of our good ole forums...

http://xdaforums.com/showthread.php?t=1179809
[Samsung Galaxy Nexus] msa1390:
Have you tried it with white skull buddy? I think that would be better...
[Samsung Galaxy Nexus] KemikalElite:
Sorry you must have not noticed the full context. I believe the patch code was first posted in March.

Certain ROMs/Kernels have merged a patch that enables Ad hoc WiFi. This is not the usual access point or router I'm trying to get working. My WiFi to my router is fine.

The public WiFi I use reaches my laptop but my Nexus. I have a second WiFi card to run a ad hoc network with Internet Connection Sharing. So my laptop acts as a range extender. It works with CM but AK won't connect fully.

It's been about a year since I've done any development but I guess I can compare the code difference for the ad hoc patch between the two kernels.
[Samsung Galaxy Nexus] kr3g3r:
yeah i might do a couple variations of it
[Samsung Galaxy Nexus] splus:
Thank you for comprehensive reply. I really appreciate it.

I've used Franco kernel in past and I know it comes with 512 Mhz GPU which works for ALL devices. It simply has disabled SR for GPU.

Bottom end - it works for all, and it's doable.

I disagree about the power consumption difference between 384 and 512 Mhz, but I really don't want to create a discussion about it.

I'd just say that giving a choice between 384 and 512 Mhz and shipping the kernel with default 384 Mhz doesn't hurt anyone.

FYI, I'm not a gamer, I don't play games AT ALL. I'm talking about graphic performance in everyday apps, scrolling smoothness being the most obvious difference where no amount of GPU governors can compete with plain hardware performance boost. Simple as that. And this difference can be checked by anyone...

Yeah, it's anarkia's kernel and he has a FULL right to do change it in any way he pleases.

And I'm very grateful for all the incredible work here, just like everyone here.

I'm just voicing my opinion, as a user. Absolutely no hard feelings towards anyone, I'd just like to understand the reason for the drop in GPU frequency and it going locked. Just like everyone else, I'd like to see this kernel getting better and better with useful options...
[Samsung Galaxy Nexus] Az Biker:
I meant to include this with my orig post but got distracted... You know... Work and all :D

Atom + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] stevensoaj:
Just out of curiousity, does anyone know where I can download Cylon 734?
[Samsung Galaxy Nexus] terminal13:
Dig through the op. If not i may have and could zip it to you.

Edit. Link to old versions on op.

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] stevensoaj:
The androidfilehost link doesn't work for me, and the devhost link only has Cylon 801, so no luck there. I had already checked these before my previous comment, I should have stated that.
[Samsung Galaxy Nexus] terminal13:
Got ya. Pm me ill make sure i have it if you want it.

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] nmlssit:
It happened again, 78% - browsing twitter, facebook and viewing a video with MX Player. Something freezed and i had to remove battery. After the reboot, suddenly, 84% :what:

Edit: Even this afternoon it happened after a freeze with battery removing.

» Tapatalk 2 on Paranoid Nexus
[Samsung Galaxy Nexus] ak:
The problem is Facebook app don't work well with ak or ak don't work well with it :thumbup:
[Samsung Galaxy Nexus] 93foxgt:
As far as i remember the Facebook app is a real memory hog. I don't use Facebook personally but it should work through the browser just as well and not interfere with ROM/kernel.
[Samsung Galaxy Nexus] kr3g3r:
AK boot thread updated with new boot animation :D
[Samsung Galaxy Nexus] terminal13:
Haven't had much trouble with that app myself. What's the issue, maybe I'm having it just not noticing

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] nrgaway:
Turn off keyboard sounds in settings and see this disappear. There was a note about it on the Wakelock Detector thread. It's has to do with audio
[Samsung Galaxy Nexus] Az Biker:
I double checked... Keyboard (SwiftKey 3) no sounds activated, neither are keypad sounds: only notifications, ringers, music, volume up/down...

Atom + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] nmlssit:
One more reason to drop FB, thanks :D

» Tapatalk 2 on Paranoid Nexus
[Samsung Galaxy Nexus] dizzy1k:
i have no issues with fb app on liquidsmooth 2.2 + ak108

Wrote with my little fingers on my shinny Galaxy Nexulicious.
[Samsung Galaxy Nexus] Piemo:
Several and frequent freeze and reboot with diamond 108 with all -100mV voltages, 180-1060mhz frequencies (cubic/sio)

With previous version was working perfectly :(

Sent from my Jellybam'd Galaxy Nexus swyping with my nose.
[Samsung Galaxy Nexus] Fenvarien:
Ak108 is running just perfectly well and stable here, thanks for this great kernel and development work! :)
[Samsung Galaxy Nexus] lioux:
I was having problems but they went away with a little voltage change.

I increased +25 all my MPU voltages. My phone hasn't frozen in the past 20 hours under heavy usage.

Previously, I froze it twice under 1 hour after installation.

Now, everything looks nice.
[Samsung Galaxy Nexus] ChazzMatt:
Undervolting is experimentation with the bits of micro current that is powering your expensive smartphone. You are betting that the manufacturer is full of crap and LESS electricity coursing through the circuitry will work just as well as what they recommend.

It's like overclocking. Some phones can do it more than others. Over in another GNex kernel thread: "I tried to overclock to 1800Mhz. It fried my phone." Yeah, so what? :) That's not the kernel's fault. That person purposely set the CPU speed 1/3 higher than stock. (Yeah, he finally recovered. His phone wasn't really fried. But it scared him so much he said he was never going to try that again.)

IF the kernel freezes at stock voltage, then yes something is wrong with the kernel. But If something freezes because you are driving with your head through the sunroof window at 100mph, then it's not the car's fault if you crash.:rolleyes: NEVER is it the car's fault. It's your undervolting. Change your undervolting back to stock -- or back closer to stock. If it still freezes, then report it. The kernel is built to work with stock voltage.

Over in

another famous kernel thread

, some people got really obsessive about trying to undervolt and then reported freezes as if it was the kernel's fault. For awhile the developer actually LOCKED OUT the ability to undervolt, because he couldn't tell if the freezes were something really wrong with the latest kernel or if was just idiots trying to undervolt too much. :) Amazingly, after locking the idiots out, the kernel was flawless! Later he put the feature back into his app, but the lesson was learned. Undervolting reports are ignored. If it works, fine. If it doesn't, tough. The manufacturer which designed and built the phone decided how much voltage was needed to properly operate the phone.

SEE? :victory: Back closer to stock recommended voltage.
[Samsung Galaxy Nexus] maverick_hunter:
Heard good things about AK, going to give it a go. What do people recommend for tweaking settings? Trickster Mod?
[Samsung Galaxy Nexus] terminal13:
Yessir!

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] cmoG530:
I'd like to know about this as well. I have the same issue.

---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------

There's always friendcaster, which is better.
[Samsung Galaxy Nexus] nrgaway:
In Settings -> Sound, I had to disable Dial pad touch tones, Touch sounds and Screen lock sound although I think disabling only Touch Sounds worked for me to reduce the wakelocks
[Samsung Galaxy Nexus] Wh1t3Rose:
You're a magician :p

Toro | Xylon | AK Diamond
[Samsung Galaxy Nexus] shriom_manerker:
A Gpu governor :eek: thats new for me :eek: and my phone is flying sky high with Vanir 4.2.2.1 stable build with ak 108 kernel ! Thanks anarkia :)
[Samsung Galaxy Nexus] galakanokis:
Just wanted to say 108 is running great for me. 12+ hours with 4+ hours ost, no hiccups, coughs or other issues. Smooth and fast.

I was running my tweaked interactive governor but will try hyper tomorrow to see how it runs. I have an S3 coming soon but I'm not sure I will give it up my Nexus as it runs so well with Anarkia's touch.

G man
[Samsung Galaxy Nexus] adio201:
I try diamond v108 and my phone is not liking it I get random reboot especially if pgm is turn on. So I'm back to v83 which that's running perfect. By the I'm using jbsourcery ROM for toro plus
[Samsung Galaxy Nexus] ak:
THIS IS NOT A PROBLEM OF KERNEL

NB:

PGM is supported

--- if you have problem report this to Developer Thread! ---
[Samsung Galaxy Nexus] MBQ_:
This kernel >
[Samsung Galaxy Nexus] nikulogical:
Use rubik
[Samsung Galaxy Nexus] JohnstonF:
Anyone using the GNex beats + xlouder patch with this kernel??

If so, does the incall volume see a drop?
[Samsung Galaxy Nexus] luisqcosta:
Runs perfectly here :) as it should. All volumes are loud and clear as hell :D
[Samsung Galaxy Nexus] j3r3myp:
Incall volume dropped for me when using kernel headphone volume boost in Trickster, thus it was really loud on music. Known bug I think :)

Envoyé depuis mon Nexus 7 avec Tapatalk
[Samsung Galaxy Nexus] L-ViZ:
tested v99 because a few people were complaining about sods on 108. for me v70 is faster, so i went back to 70 :)
[Samsung Galaxy Nexus] marhensa:
deleted
[Samsung Galaxy Nexus] ak:
Where SOD? don't post infos that create entropy please.

Sod = Pgm
[Samsung Galaxy Nexus] lesp4ul:
Let's eat, indomie anyone?
[Samsung Galaxy Nexus] ak:
new kernel

[4.2.1 - 4.2.2] DIAMOND (EXPERIMENTAL)

androidfilehost - Last Version: AK.200.SKL.zip

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

Differential Changelog: Link

Features: Link

Github: Link
[Samsung Galaxy Nexus] marhensa:
hahaha... i dont think indomie goes worldwide.. :D

wow new codename, what is SKL?

gotta try it.

thanks anarkia.. :)

---

Sent from Android Device
[Samsung Galaxy Nexus] ak:
skl = skull
[Samsung Galaxy Nexus] Soundigy:
I like new codename! :cool:

Flashing immediately :D
[Samsung Galaxy Nexus] gaich:
No changelog?:rolleyes:
[Samsung Galaxy Nexus] SuperSalvo:
Great and how can i get more than 1400 mhz?
[Samsung Galaxy Nexus] ak:
search before ... there are all info from other users .... :fingers-crossed:
[Samsung Galaxy Nexus] psxsnake:
when latest 4.2v457 with PGM? :D
[Samsung Galaxy Nexus] ak:
when i reached 22000 thanks ...... :D

its a joke .... :p

perhaps this weekend but if its possible i want to put out v459 pgm .... :) ;) before the mainline ....
[Samsung Galaxy Nexus] ak:
I want to have some feedback for the 459 exp version by the users that tested it :victory:
[Samsung Galaxy Nexus] Nicuz95:
No problem so far, it seems smoother than 457 :)

Also Xylon 011 it's faster, very good combo! :good:
[Samsung Galaxy Nexus] ak:
Fantastic i have 460 nel sacco .. Detail on git :eek:
[Samsung Galaxy Nexus] psxsnake:
sounds like famous phrase "don't tell cat, if you have'nt in the sac hahahaah
[Samsung Galaxy Nexus] schukje:
I have xylon 11 beta 3 running with your latest kernel and your settings but my battery uses 41% to Android system. Normally its about 6%. See screenshot.

grtz from holland
[Samsung Galaxy Nexus] odin13:
That's not a kernel problem...my stats are fine. Try rebooting or dirty flash your rom + ak kernel again

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] ak:
I dont have this problem ... OS not kernel related :D
[Samsung Galaxy Nexus] schukje:
I read on another thread it has to do with using trickster mod. Gonna try without it. :);)

grtz from holland
[Samsung Galaxy Nexus] Nicuz95:
I use Trickster MOD and I don't have any problem :)
[Samsung Galaxy Nexus] ak:
I can confirm that trickster works very good without problem :eek:
[Samsung Galaxy Nexus] marcoperro74:
I can confirm that ak 459 beta and xylon v11 beta 3 work very very good... I use your settings anarkia and all is very smooth and fast... For me the best kernel for gnex at the moment! Thanks anarkia continua così... Stai facendo un ottimo lavoro! Grazie ;)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] SahilC:
Hey how what happens if I mess around with these values? What do they even do? :eek:
[Samsung Galaxy Nexus] shag_on_e:
459 is super nice anarkia! Thanks fit the test release, I haven't tested all the things yet, but navigation is super slick!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] bigeyes0x0:
Trickster MOD does not run a BG service, unless you do these things:

- You're on Nexus 4 with color set to NOT: 255, 255, 255 in future versions.

- You're looking at Infos tab (the service will turns off when you go to other tabs or screen off)

- You're having adb wireless with screen on enabled

Otherwise it does not have anything running, whoever reported that is on crack... and is likely to have screwed up his config in some way.

BTW, had enough with syfses changing other sysfses (e.g. Live OC and some other crap on N4) so a GUI refresh feature will be built into the app in some future version.

@Anarkia: You still build 4.1 kernel? I love you because I really hate bugs on 4.2, both my devices are now on 4.1.2. I wish Google did a better job than this.
[Samsung Galaxy Nexus] Shadow-Nexus:
Nice work with 459 ak you're the man!!

But I have one slight problem

I have set up my colors (gamma, contrast, etc...) And they apply fine at boot and everything but after a few seconds my colors revert back to stock and since I have trickster to apply settings on boot after a few seconds they go back to normal

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

Edit: Oops forgot to say that my colors are set up on boot with an init.d script
[Samsung Galaxy Nexus] ak:
Thanks a lot for new SIG its fantastic! :D :D :D
[Samsung Galaxy Nexus] bunnahabhain:
http://xdaforums.com/showpost.php?p=31467708&postcount=4
[Samsung Galaxy Nexus] ak:
???

click on diff changelog!
[Samsung Galaxy Nexus] Soundigy:
You quoted a wrong man! :laugh:

I'm glad you like your new signature. It's look fantastic! :P
[Samsung Galaxy Nexus] krugdenis:
Why you removed discard option on data and system? (( My gnex with V3U00M chip, and you know how it works without discard...
[Samsung Galaxy Nexus] GamaX320:
nice name :good::good::good:
[Samsung Galaxy Nexus] odin13:
Yes!! Moksi meti for me tonight :)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] ak:
why discard out

I have made some test:

----- for example

minco v7 + discard opt = bootloop

I dont know if is a problem of kernel or rom but with this ext4 opt you have a bootloop.

I want to remove discard also for cache.
[Samsung Galaxy Nexus] krugdenis:
Sad to hear that :( btw, I've always used discard on different roms (except minco), and never had any bootloops, so maybe problem in rom?
[Samsung Galaxy Nexus] bunnahabhain:
Minco V7 is out? How is it running?

I won't try - I dislike the dev :(

Curious anyway :p
[Samsung Galaxy Nexus] L-ViZ:
sry, just read it a few or more posts ago, i am not rly up to date because i was in a hospital for a week, going to install skull200+latest rasbean :)
[Samsung Galaxy Nexus] Punkiderma:
Hello! First of all, thanks for this great and hard work! :) (Even better: grazie mille da Torino! ;) )

I would like to ask a question about voltages: if I have all smartreflex ON, and I want to undervolt, I need to change only min calibrated voltages or also, for example, MPU offsets? Thanks!

I also made a very simple wallpaper, taking inspiration from Soundigy's one (thanks :) ) hope you like it :)
[Samsung Galaxy Nexus] schukje:
Minco was created with Franco isnt it? Where has he put his roms nowadays?

grtz from the crazy basterd from holland. and i love maguro roms.!!.
[Samsung Galaxy Nexus] Godra:
Here
[Samsung Galaxy Nexus] lesp4ul:
Hahaha, but my friend from belgium likes mi goreng very much.. Well... Haha.
[Samsung Galaxy Nexus] TheMysteriousOne:
I think he has something to do with High Performance Sound in Trickster. Disable it and report back. :)

SKL 200, here I come.
[Samsung Galaxy Nexus] Khizar:
kanged your sig lol... does it look good? :p

Edit- and also your avatar :p
[Samsung Galaxy Nexus] ak:
Fantastic another piece of Art! :D

I miss cr88! :crying:
[Samsung Galaxy Nexus] Hetalk:
Wow. That looks awesome. Can you make 1 for me too? :p
[Samsung Galaxy Nexus] ak:
new sig

Here link to original images:

http://imageshack.us/a/img607/4192/aklogomelogo50.png

http://imageshack.us/a/img826/3387/aklogomelogo.png

http://img248.imageshack.us/img248/1858/aklogomelogo.jpg
[Samsung Galaxy Nexus] TheMysteriousOne:
I have a question:

I was on v108 recently and it was working fine.

I then reduced min calibrated of all to 700.

Kept the phone idle overnight to test idle drain.

Woke up in the morning and it was an SOD. Had to pull the battery.

Now, the phone wouldn't go past the boot screen.

So, I dirty flashed the same ROM. (didn't even flash kernel on top)

So, it was went to the optimizing apps stage and then starting apps stage.

That's where it got stuck.

It wouldn't go past starting apps.

Ultimately, I had to clean flash the ROM.

Now, I know this is not the kernel's fault.

But, I would just like to know what caused this. Have any of you experienced this in the past?

Trickster's set on boot had a 30 sec delay. So, it should have at least booted properly, right?

Very curious to know the cause.
[Samsung Galaxy Nexus] Khizar:
thank you and yup i miss Ciprian as well

nope i made 2 here you go :highfive: hope you like them :fingers-crossed:
[Samsung Galaxy Nexus] ak:
The problem is the fck discard option.

I have removed also for cache and now 0 bootloop.

New kernel into next hours.
[Samsung Galaxy Nexus] TheMysteriousOne:
How could the discard option have affected even after a dirty flash of the ROM?

Since I dirty flashed the ROM, it had the ROM's kernel.

Hmmm.
[Samsung Galaxy Nexus] Hetalk:
Thanks man !!:good:

You da man. :cowboy:
[Samsung Galaxy Nexus] GamaX320:
very nice wallpaper~tq brother!
[Samsung Galaxy Nexus] ciprianruse88:
minimalistic ak kernel skull ed signatures 500x100

DOWNLOAD PAGE 63 OR OP --> http://xdaforums.com/showthread.php?p=40460477#post40460477
[Samsung Galaxy Nexus] ak:
You call CR and BAM .... new sig.! :good:
[Samsung Galaxy Nexus] ciprianruse88:
Some big banners later on :thumbup:

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] fairct:
I actually had issues like this as well. I had to wipe my sdcard to get everything working again. My recovery started acting funny at the same time though... So I really don't know what's going on either.