yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ciprianruse88:
Yes,with intellidemand it works flawlessly.it is one of my favorite governor
[Samsung Galaxy Nexus] ak:
new ak

New online news on twitter ... ak power next release is near .... perhaps arrive in partnership with xylon new release. :D
[Samsung Galaxy Nexus] Nicuz95:
It'd awesome! :D
[Samsung Galaxy Nexus] schukje:
I was always trinity fan but tomorrow i am going to switch to ak! What i read everywhere this is the best kernel for 4.2 at the moment and my daily rom is xylon. Gonna test if this is the best combo!!! :);)

grtz from holland
[Samsung Galaxy Nexus] emic2:
Good news. I came back to 448 because in 455 I had problem with interactive and it sucks my battery.

448 is really great. It works perfectly without any bug. Great job!

Thanks very much. I hope that you succeeded to fix the interactive bug. Good luck. ;)

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Droid-21:
How kind.

Thank you.
[Samsung Galaxy Nexus] ak:
type Kernel

views 7195

downloads 4141

cylon v801

http://d-h.st/LxO
[Samsung Galaxy Nexus] ak:
The same for now no new kernel ... but i have found also idle drain problem!
[Samsung Galaxy Nexus] AutomaticFailure27:
It is a good feeling :highfive:

I just do it because I like watching the Optimizing prompt before it boots.

Makes me feel like the phone is telling me "Hey man, I got this shizz. No worries."
[Samsung Galaxy Nexus] irminsul:
It's like wiping your butt after taking a leak, only when updating ROM it could be useful.

But people still think it helps making the kernel run better, that story should vanish.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] MBQ_:
In the end bro, its user preference. And typically, you can't change that. It isn't affecting you at all, and the it doesn't really negatively affect the user. And what you're saying it solely an opinion. I say we just drop it, or chat with whoever via PM. Otherwise, we're just cluttering the thread.

And yes, I know I'm not one to talk for cluttering this thread. ;p

Edit: "That story should vanish" is an opinion. That's what I meant
[Samsung Galaxy Nexus] branedamig:
I'm sticking with 063 for now for 2 reasons: 1) Stefano releases new kernels so fast it's useless to go back, and 2) recallobrating my battery seems to have greatly helped idle battery drain. Idle drain was rough yesterday (4% loss/hour) but I let it die last night and then charged to 100% overnight and all is decent today. Maybe 1% loss/hour on idle which is night and day difference over yesterday.

Sent from my ATOMic Gnex with AK Kernel on Tap2
[Samsung Galaxy Nexus] rasa92re:
Here's another tip that might address idle drain: try the deadline scheduler. Sio and Fiops were giving me about 5.2 percent idle drain. I'm down to 1.1 percent. I'm going to try some UV and see if I can get it lower even though anarkia is dropping the new kernel soon.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AutomaticFailure27:
Something else that might help with the drain.

I still use interactive/deadline, never really switched to anything else (unless Smartass v2 was available :o ) and I have been using osm0sis' interactive tweaks over in the franco thread:

Interactive

above_hispeed_delay: 15000

boost: 0

go_hispeed_load: 95

hispeed_freq: 729 (I change mine to 525)

min_sample_time: 45000

timer_rate: 30000

target_loads: 85

timer_slack: 80000

boostpulse_duration: 80000 / 10000

Changing interactive to these settings, has made the phone use a less frequency while still keeping the speed. Also, scales down quicker and uses the higher frequencies for less time.

I also tried doing the deadline tweaks, but I felt since franco and AK use different methods of building their kernels, It wasn't exactly necessary. I haven't really noticed to much of a difference, but possibly these tweaks on AK

might

have slowed it down ever so slightly. Again, no idea actually.

Deadline

read_expire: 351

write_expire: 3500

writes_starved: 6

front_merges: 1

fifo_batch: 1

Osm0sis and his team are still doing some tweaking on their end, so final results probably will change.
[Samsung Galaxy Nexus] Blackcrx:
I have also been using Osmosis deadline tweaks. I have found his newest tunables to be pretty good. I noticed that the ones you listed are of his old tweaks

new settings are as follows

read:350

write:3500

starve: 4

front:1

fifo:2
[Samsung Galaxy Nexus] jcmm11:
On Franco I prefer row but since that's not available I'm also using deadline with the tweaks. You should also mention the general portion of the tweaks since that impacts all schedulers.

echo 512 > /sys/block/mmcblk0/queue/nr_requests;

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;

echo 2 > /sys/block/mmcblk0/queue/rq_affinity;

echo 0 > /sys/block/mmcblk0/queue/nomerges;

echo 0 > /sys/block/mmcblk0/queue/rotational;

echo 0 > /sys/block/mmcblk0/queue/add_random

echo 0 > /sys/block/mmcblk0/queue/iostats;
[Samsung Galaxy Nexus] AutomaticFailure27:
Ahh yes. Thanks much.
[Samsung Galaxy Nexus] Blackcrx:
I must say... I love the team work of this thread. Not just the developer or the testing team but everything that has contributed in general
[Samsung Galaxy Nexus] frenchy714:
Same here...It's 2nd to none.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Az Biker:
Trying Greenify on v63, not getting deep sleep... Troubleshoot greenify?

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] MBQ_:
Get a GPS lock, and your phone will enter deep sleep
[Samsung Galaxy Nexus] Az Biker:
Is this because I hibernated maps? Cause I had gps lock prior to greenify?

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] akellar:
If you're toro on atom it's because they are using maguro binaries. They just merged the right one's.
[Samsung Galaxy Nexus] Az Biker:
My question is whether or not this is related to greenify? I've been on this version of Atom since it's release and never had a deep sleep issue, so I'm curious if the binary issue is sole culprit. If it is greenify, will I need to get gps lock after every boot, or only once after greenifying maps?

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] Castro27:
I'm not sure if this is kernel related but here we go. I'm on v63, stock settings, and my phone randomly started to lag. This is a piece of the log file:

04-08 18:43:20.368 E/Sensors (752): inv_update_data error (code 255)

04-08 18:43:21.366 E/ (752): hardware/invensense/mlsdk/./mllite/accel.c|inv_get_accel_data|154 returning 255

04-08 18:43:21.366 E/ (752): hardware/invensense/mlsdk/./mllite/mlFIFO.c|inv_read_and_process_fifo|635 returning 255

04-08 18:43:21.366 E/ (752): hardware/invensense/mlsdk/./mllite/ml.c|inv_update_data|558 returning 255

04-08 18:43:21.366 E/Sensors (752): inv_update_data error (code 255)

04-08 18:43:22.371 E/ (752): hardware/invensense/mlsdk/./mllite/accel.c|inv_get_accel_data|154 returning 255

04-08 18:43:22.371 E/ (752): hardware/invensense/mlsdk/./mllite/mlFIFO.c|inv_read_and_process_fifo|635 returning 255

04-08 18:43:22.371 E/ (752): hardware/invensense/mlsdk/./mllite/ml.c|inv_update_data|558 returning 255

It kept this pattern and only stopped after a hard reset (the phone frooze in the "sutting down" screen). Any ideas?
[Samsung Galaxy Nexus] Blackcrx:
make sure you give greenify root access too.

I know I had a weird problem before when greenify didn't have root access.

I would select a bunch of apps to hibernate but every once in a while my screen would turn on randomly. Thought it was greenify but later realized that I did not give it root access.

Once I gave it root permissions everything was gravy
[Samsung Galaxy Nexus] Mohawk3:
I'm using Greenify and AK63. My phone gets deep sleep. I'm using the latest nightly of chameleon OS and mostly Neph's kernel settings.
[Samsung Galaxy Nexus] Az Biker:
Greenify has root access, after reboot had to get gps lock again. If it's not a greenify vs ak kernel issue, I'll do more research once I get home and keep the kernel thread clean :D

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] Blackcrx:
I doubt it is a greenify and AK issue. I have ran greenify with cylon and diamond series with no issues

What does your battery stats show? anything noticeable that is keeping the device awake?
[Samsung Galaxy Nexus] Az Biker:
That's the problem, no wakelocks... And I never had the issue prior to trying Greenify. I will d/l updated Atom v11 and retest this at home. Not wanting to plug up kernel thread..

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] gummie:
Seriously?! 2048 at 1GHz you still get smooth experience? Man, Cylon v801 is quite a Kernel eh. I don't really use cfq way of handling queue. Anyway here's my setup on same Kernel as yours.

Min CPU - 350MHz

Max CPU - 1.2GHz

Max Screen Off - 525MHz

Gov - Interactive

I/O - row

FSYNC - Off

rhead - 1024

Cylon v801 running on AOSPA 3.15 Mar 28

I find this setup quite responsive. Also been trying out I/O values and I quite like my current settings.
[Samsung Galaxy Nexus] Blackcrx:
I don't want to be "that guy" but there has been a lot of reports of 63 and battery drain issues. Might want to go back to your last known good kernel like 43/44.

I'm currently toying with Rubik r3 for fun.

MBQ has also mentioned that he's gone as far back as cylon 801
[Samsung Galaxy Nexus] Asmodicus:
I started having problems right around version 50. I kept installing each new release, but 63 was probably the worst for me. I tried adjusting my settings on Trickster and nothing helped. Went back to Cylon 801 because for me, that release was perfect. I keep a copy on my sd card all the time just in case.
[Samsung Galaxy Nexus] MrVJTod:
Went back to 33. Wasn't happy with 63, 44 or 43.
[Samsung Galaxy Nexus] Blackcrx:
How is the battery on cylon 801 compared to the recent diamond series?

I recall there was one or two kernels that was amazing for battery and performance but I don't recall which series or release it was.
[Samsung Galaxy Nexus] kaluoshi:
Advice

To @all: if you have problems with latest Diamond and wanna switch back, use Rubik r3 (it's a AK DIAMOND 044 based one) and it's quite stable, don't just go far away to Cylon :) tracking problems and also benefits with a newer version helps @anarkia to discover issues quickly (going to compare a cylon would be harder if a newer one such AK 044 or Rubik r3 is working well :D). anyway just a thought :fingers-crossed:

All of us are verifing/testing/comparing tests builds in the meanwhile to reach the best experience ;) so stay always tuned!

P.S. in case pay attention to the wifi drivers restore needed by Rubik :good:
[Samsung Galaxy Nexus] frenchy714:
@Anarkia

Shot you a PM :D
[Samsung Galaxy Nexus] gummie:
Thanks but I think there are already enough number of concerns that points out the problems present on the new release. Reverting to previous builds is just a good choice for the meantime when you can't start day with those problems ocurring. Been lurking on AK Git and testing release by release and I conclude that Cylon was One or maybe the best there is on AK History. Yeah saw that codes are now cleaner on Diamond, newest Linux patches coupled with the best and stable picks from various projects but I can't seem to think of any reason why AK dropped that project and start again from scratch when there is already a stable experimental.

No disrespect, just saying opinions on the past AK's.

Also now that were into it, can you guys just stop posting oh man thanks this new Kernel was faster than the last, seriously how can you back that up that conclusion without some data. I know user based exp is good to see but man 30 posts of thanks was just mental. If you want to help, get to OP and start reporting based on how it should really be. Show some good data.
[Samsung Galaxy Nexus] Blackcrx:
Currently running r3 right now and everything is good.
[Samsung Galaxy Nexus] Asmodicus:
The battery performance was really good on that release.
[Samsung Galaxy Nexus] SahilC:
V19 is amazing for me. But, I haven't tried anything in between, so basically I'm only comparing it to 63. :P

Sent from my Nexus Prime powered by AK goodness!
[Samsung Galaxy Nexus] jpg3927:
Can you give source of AK-tuna-3.4?

Although i can't contribute for that work.

just i want to build this, and use this..

thanks
[Samsung Galaxy Nexus] kaluoshi:
No problem :good: What a good avatar :)
[Samsung Galaxy Nexus] MBQ_:
Its on his github if I'm not mistaken
[Samsung Galaxy Nexus] jpg3927:
I can't find that..:confused:

Can you give me github link?

Sorry.. :(
[Samsung Galaxy Nexus] DoesntPostAThing:
Hey guys, I posted the stuff I did to fix the lag on my device in the AOSPA thread -> http://xdaforums.com/showpost.php?p=40088358&postcount=30694

Take a look, any suggestions? If it's good, should I post it to Galaxy Nexus General? Thanks :)
[Samsung Galaxy Nexus] ak:
I have removed all source Because nobody contribute to implementation and fixing ... alone was impossible .... :cowboy:
[Samsung Galaxy Nexus] jpg3927:
umm..sorry..
[Samsung Galaxy Nexus] kompressorgpl:
Hello! I'm om V63 and my batery goes like this: 83%; 8h7m43s - time and only 11m43 sec of sreen. AK original settings...
[Samsung Galaxy Nexus] sajty:
Try to read previous few pages.v063 has problem with battery drain.Flash 044 or rubik.
[Samsung Galaxy Nexus] kompressorgpl:
Thanks. I now that. Just report to help Anarkia1976...
[Samsung Galaxy Nexus] lesp4ul:
Stefano, i saw you have released your kernel for N4, any recommended setting for battery?
[Samsung Galaxy Nexus] ak:
4.2.2 DIAMOND ED. (EXPERIMENTAL)

androidfilehost - Last Version:

dev-host - Last Version: AK.070.DIAMOND.zip

Differential Changelog: Link

Features: Link

Github: Link
[Samsung Galaxy Nexus] ak:
No kernel for n4 ... where did you see this?
[Samsung Galaxy Nexus] lesp4ul:
Wth, i read it from my local n4 android forum. Wait don't say AK = Air Kernel... Lolz i'll ask the one who mention AK, i was really excited. -___-"
[Samsung Galaxy Nexus] Blackcrx:
Diamond 70 is back to AK smoothness.

Thanks for the awesome work
[Samsung Galaxy Nexus] sajty:
It will be probably Air Kernel.Before i found AK,i also thought,that AK = Air Kernel.
[Samsung Galaxy Nexus] zandander:
Downloaded this from the Chicago page around an hour ago and so far the drain has been where it should be. Thanks for your work anarkia, it's much appreciated from everyone that uses/loves your kernels :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lesp4ul:
Yeaaa confirmed that's right, not anarkia but air.. :p
[Samsung Galaxy Nexus] kompressorgpl:
Go Stefano go!!! Big thanks!!!
[Samsung Galaxy Nexus] Rimher:
Awesome!

Going to test it today ;)
[Samsung Galaxy Nexus] klaidliadon:
Trickster mod message

I have a problem after switching from v066 to v070.

When I open trickster mod app a warning message comes out "warning: modified root app might contain dangerous virus/malware"

Is it a false positive?
[Samsung Galaxy Nexus] irminsul:
I'm still having those nasty WiFi re-connection drops at home, while at the office all is good.

For as good as I can follow this thread, I'm not the only one; it would be wonderful if we can fix this.

Apparently it's on my router, because at work nothing is wrong. Just suddenly the problems started occurring, mostly I blame 4.2 for this, but drain on WiFi is to high to leave it. At the office my phone has a normal minimal drain on WiFi, at home my phone easily drains 30 to 40 % on a 7 / 8 hour night sleep. I never changed any settings on my router, and in the 4.1 era I just had heavy drain at my girlfriends place, not at my home.

I'm really not into router settings, but what would be a good start? I read something about DTIM interval, but that does not fix the issue. While behaving well at work, the phone software works kinda, but something in the router triggers it to drain...
[Samsung Galaxy Nexus] kizakiyuria:
http://xdaforums.com/showthread.php?p=39986672

edit

this is why don't use pirated softwere,carefull out there,this is a wild world

:D
[Samsung Galaxy Nexus] ak:
I dont have this problem at work (wpa2 mschap net) and at home (wpa2 router).

Clear cache and data of trick and reboot
[Samsung Galaxy Nexus] ak:
new kernel

Updated androidfilehost:

4.2.2 DIAMOND ED. (EXPERIMENTAL)

androidfilehost - Last Version: AK.070.DIAMOND.zip

dev-host - Last Version: AK.070.DIAMOND.zip

Differential Changelog: Link

Features: Link

Github: Link
[Samsung Galaxy Nexus] irminsul:
No, but I'm not the only one having that problem. It's not on the kernel side, but on the router's side as I stated. At office WiFi all is good, at home WiFi it doesn't.

So some router settings are causing those problems and if we know what setting, many people are helped here :)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] ak:
Have you try to enable wifi high perf and disable wifi opt?
[Samsung Galaxy Nexus] irminsul:
No, gonna try that at home. Good option!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] pagratios:
Is there a way for clean install ?
[Samsung Galaxy Nexus] Hetalk:
Clean install of AK kernel? You just flash it using TWRP recovery. :good:
[Samsung Galaxy Nexus] buggerthis:
Try using a static ip address. That really helped my WiFi drop issue
[Samsung Galaxy Nexus] timothyung:
I have the WiFi drop issue too, but only when I turn on WiFi after the device is booted. It never happens when I turn on WiFi, then reboot.

Hope that it helps.

By the way, I believe ak70 so solves the drainage issue?
[Samsung Galaxy Nexus] MBQ_:
Yes it does.
[Samsung Galaxy Nexus] frenchy714:
Thanks for this!!

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ak:
Does the new kernel work with your phone? :D
[Samsung Galaxy Nexus] sajty:
Battery drain in 070 is definitely fixed.
[Samsung Galaxy Nexus] ak:
:D:D:D

Uff every day this error:

Sorry, you are limited to 8 thanks per day
[Samsung Galaxy Nexus] logi43:
Definitely the 0.70 kernel sleeps like a baby I left a few hours on my desk.

Good job guys, greetings and thanks
[Samsung Galaxy Nexus] timothyung:
Just curious... what was the reason leading to the drain? And how was it fixed?
[Samsung Galaxy Nexus] frenchy714:
YES! It's working great right out the box! Thanks for adding the SR min. calibrated voltage control setting! Is this a permanent addition that will be in all your releases moving forward :D??

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] 00negative:
On Rubik edition tethering doesn't seen to work for me. Anyone else? Seems to work fine on diamond edition and cyanogen stock kernel.
[Samsung Galaxy Nexus] ppog:
I'll just join the chorus and confirm that idle drain is fixed in v70. Great stuff anarkia, thanks
[Samsung Galaxy Nexus] musashihatred:
Good Idle Drain

V70 had good drain.

Even Clocked at 1350, doesnt cosume much battery.

mobile ON since this morning and just charging now.
[Samsung Galaxy Nexus] cubsfan187:
Nice way to wake up in the morning! Nice work AK! Thank you for all that you continue to do for the GNex and our little community that uses your kernel. :)
[Samsung Galaxy Nexus] relax24:
Drain definitely fixed. However, when I turn the screen on the wifi icon flicks from grey to blue :(

Worse even, I dropped loads of water on my phone today. Took the battery out and put the phone in rice straight away. Phone works, however it doesn't charge. Just cleaned the connection with a pin and it works every 10 attempts lol. Although it says Charging (USB). When it's not connected in Battery Settings it says "x% Not Charging". Looks like I may have to replace the usb charging port flex cable.

Anarkia I hope your kernel will make my battery last till it arrives :laugh:
[Samsung Galaxy Nexus] boki2911:
flying
[Samsung Galaxy Nexus] AutomaticFailure27:
Awesome v70! :highfive::victory::good:

Charging up before work and we'll see how it is. Great way to start the morning.

Was getting around 1.2% - 2.4%/hr per Battery Monitor Widget on v63. :p
[Samsung Galaxy Nexus] don_kamil:
My Nexus never works so fast :)

Wysyłane z mojego Galaxy Nexus za pomocą Tapatalk 2
[Samsung Galaxy Nexus] siealex:
Does this kernel support swapping? Not only zram, but swapping to the flash memory. If not, are there any tuna kernels that support it?
[Samsung Galaxy Nexus] binlalo:
Can anybody explain me what frandom is? I've googled it but I can only find some technical stuff I don't understand, I need a "this does that and is good/bad explanation". Thanks and sorry for the noob question.
[Samsung Galaxy Nexus] szucsgf:
I found this source:

http://www.billauer.co.il/frandom.html

It's half technical and half non-technical.
[Samsung Galaxy Nexus] binlalo:
Thanks, that was what I read but didn't get much of an idea. I think I've read a couple months ago that this makes the phone to be at higher CPU speeds so it reduces lag but at the cost of battery life. Is that right or not? Do you recommend me to use it?
[Samsung Galaxy Nexus] siealex:
Set your gov'r to performance and you'll get the same. These programs are junk processes that only add lags.
[Samsung Galaxy Nexus] Khizar:
thats cuz you never used AK before... like they say once you go AK you never go back :laugh:

who are you talking to? quote their post so they know you are replying to them...lol :p
[Samsung Galaxy Nexus] galakanokis:
Awesome, new Atom v12 and AKv70 to play with this morning. What a way to wake up.

I was still getting 12 or 13 hours with 3hours on screen with 63 si I can't what to see what thus does!

G man
[Samsung Galaxy Nexus] Butter Smooth:
edit: thanks dp917!
[Samsung Galaxy Nexus] dp917:
Did you try Nephilim's tweak for green screens at the bottom of his post? http://xdaforums.com/showpost.php?p=38030897&postcount=13473
[Samsung Galaxy Nexus] buggerthis:
Here's a before and after screenshot of drain on 063 and 070 :)

The thin black line in the middle is me flashing 070. Drain is definitely fixed. Thanks, Stefano!
[Samsung Galaxy Nexus] PatimusXPrime:
ok dudes, what I/O schedulers you using here and what are your tunables? i'm gonna do some more testing then post mine!
[Samsung Galaxy Nexus] mixtapes08:
Start from here

http://xdaforums.com/showthread.php?p=33999592

-3StarsAndaSun
[Samsung Galaxy Nexus] relax24:
One thing I noticed is that I've set the min cpu to 180mhz, but the 180mhz step never gets used. Lowest it goes down to is 230mhz
[Samsung Galaxy Nexus] szucsgf:
Is your Min Screen On frequency set to 230?
[Samsung Galaxy Nexus] stevensoaj:
I JUST updated my settings post. I'm trying to get more people to try them out, but everyone likes Neph's settings too much (that's not mean't to be offensive, it just means that he has worked out some pretty great settings :p). Anyway, if you'd like to give them a try, here's the link. ---> My AK Kernel Settings

As far as AK Diamond v70 goes, I'm absolutely loving it, and here's why..

1. Idle drain issue from v63 is definitely gone. Thanks for the quick fix Stefano!

2. I'm loving the Min Calibrated voltages. I lowered my min to 780mV, and SR calibrated frequencies 180, 230, 350, and 525 down to 790mV! That's pretty sweet. You just made undervolting a lot easier and more flexible for me. Thanks. :highfive:

3. Fiops seems more stable on v70 than it did on v63. So I'm giving it a shot again, because it had been my favorite when I first switched to AK because I don't know any other kernel that has it and I like to be different. :D

4. Been rocking Ondemandplus since you added it. Seems perfectly stable and very battery friendly.

5. Also loving Dynamic Fsync since you added it! I get the performance boost when I'm using my phone, and the safety when I'm not. Perfect solution to that little debate!

6. Best Dev/Team/General Forum support you can get. Thanks guys! :highfive:
[Samsung Galaxy Nexus] PatimusXPrime:
i seem to be getting slightly better r/w numbers using SIO than FIOPS but FIOPS is acting a tad snappier. could just be a placebo?
[Samsung Galaxy Nexus] stevensoaj:
As of right now, I feel exactly the same way. Sio did better in benchmarks, but Fiops seems ever so slightly snappier in terms of user experience.