• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Siyah Gingerbread kernel (v2.x)

Cool. I will give 2.4 a go - had only just installed 2.3.

Here [REF] Quasar kernel governors and I/O schedulers manual - xda-developers
it says:
"NOOP scheduler is best used with solid state devices such as flash memory or in general with devices that do not depend on mechanical movement to access data (meaning typical "hard disk" drive technology consisting of seek time primarily, plus rotational latency). Such non-mechanical devices do not require re-ordering of multiple I/O requests, a technique that groups together I/O requests that are physically close together on the disk, thereby reducing average seek time and the variability of I/O service time."



Surely all phones use flash therefore noop will always be best (which would be consistent with http://androidforums.com/3457389-post1.html)? Am I missing something?
 
Cool. I will give 2.4 a go - had only just installed 2.3.

Here [REF] Quasar kernel governors and I/O schedulers manual - xda-developers
it says:
"NOOP scheduler is best used with solid state devices such as flash memory or in general with devices that do not depend on mechanical movement to access data (meaning typical "hard disk" drive technology consisting of seek time primarily, plus rotational latency). Such non-mechanical devices do not require re-ordering of multiple I/O requests, a technique that groups together I/O requests that are physically close together on the disk, thereby reducing average seek time and the variability of I/O service time."



Surely all phones use flash therefore noop will always be best (which would be consistent with http://androidforums.com/3457389-post1.html)? Am I missing something?

Ah.... the nuances of the English language.

"NOOP scheduler is best used with solid state devices", indicates this works at its best with solid state devices as opposed to any other type.

Alternatively...

"NOOP scheduler is the best for solid state devices", would indicate that this was the best scheduler to use on your phone.

Whilst I have used NOOP in the past it is not one of my favourites. You really do have to try them all and see which works best for you. :D
 
How about the later line?

"Such non-mechanical devices do not require re-ordering of multiple I/O requests"

This would imply that io scheduling will give no benefit so doing nothing is best?
 
How about the later line?

"Such non-mechanical devices do not require re-ordering of multiple I/O requests"

This would imply that io scheduling will give no benefit so doing nothing is best?

Each of the I/O schedulers have their own particular attributes when it comes to handling requests and in the way that they interact with the various governors.

If the above quote were an absolute, then there would be no need for I/O scheduling whatsoever and all kernels would come with NOOP set.

However, as I have found, the different I/O schedulers do produce differing results which is why developers include them.

You will just have to try them and see which works best for you.
 
Well, Siyah 2.4 has certainly lasted 24 hours for me, which was one of my main criteria.

Using lulzactive and vr, I have encountered no problems and it is running very smoothly with Launcher Pro.

According to CPU Spy, loads of Deep Sleep. BetterBatteryStats not reporting any nasty wakelocks.

:D
 
Well.. Siyah 2.4 definitely works better for me compared to 2.3. Kinda amazing in a sense, haha. Yay to long lasting battery life! =D
 
On v2.4 I lost 4% overnight (9 hours), plenty of deep sleep, no insidious wakelocks.

Now checking to see if my over zealous NetworkLocationPassiveCollector wakelock has calmed down a bit after updating Google Maps from 6.0.0 to 6.0.1.
 
On v2.4 I lost 4% overnight (9 hours), plenty of deep sleep, no insidious wakelocks.

Now checking to see if my over zealous NetworkLocationPassiveCollector wakelock has calmed down a bit after updating Google Maps from 6.0.0 to 6.0.1.

That is bl**dy good old boy!

Do you shut virtually everything down at bedtime?

I'm a lazy s*d and have everything on, including Wi-Fi, GPS, weather, news, tasks, email, Whatsapp, PowerAMP, No Lock, Lookout, etc; and am happy with a 15-20% drain if not charging.
 
No butty, I keep everything on. Wifi will be on sleep due to my policy but not off altogether, data on. I do have the odd few wakelocks that do not coincide with screen on time, but I think that may be to the Maps 6.0 bug, so waiting to check how 6.0.1 copes tonight. I've noticed it hasn't increased it's count in the last 2 hours so I'll just have to wait and see.

the only thing I have done for overnight is to configure my weather widget to stop refreshing between midnight and 6am.
As I'm not a heavy email user on the device, I have refresh frequency set to 4 hours.
 
the only thing I have done for overnight is to configure my weather widget to stop refreshing between midnight and 6am.
As I'm not a heavy email user on the device, I have refresh frequency set to 4 hours.

Have ditched Lookout, I wasn't using it as an anti-virus antway, in favour of Android Lost as Lookout was active, obviously, 24/7.

Have also set my emails to once an hour instead of every 20 min's (see if I can live with that) and unfortunately, my weather widget does not allow selective turn off (Beautiful Widgets + Add on set to refresh every hour now instead of every 30 min's).

Not too concerned if these tweaks don't make a great deal of difference as I am getting the 24 hours on battery that I want... but, every little bit helps. :D

Work on 2.4.1 has begun

OMG! Will we never be free of this curse?

(OK... histrionics over now)
 
Have ditched Lookout, I wasn't using it as an anti-virus antway, in favour of Android Lost as Lookout was active, obviously, 24/7.

Have also set my emails to once an hour instead of every 20 min's (see if I can live with that) and unfortunately, my weather widget does not allow selective turn off (Beautiful Widgets + Add on set to refresh every hour now instead of every 30 min's).

I use AVG, and it seems to work very well. It only kicks in as a download completes. I very rarely see it on the process list at all, and I dont recall ever seeing an AVG wakelock. You just have to tell it to ignore checking su, and to ignore the "Unknown sources" option (if ticked) and job done.

I use Android Lost too, and its free features far, far outweigh that of Lookout paid-up version.

As for your weather widget, it may be worth you looking at Fancy Widgets, as this gives you the ability to switch off refreshing between a set time range.
 
he often releases the changelog before the file, the tease....

often the file just takes a while to upload to the site.
 
v2.4.1 is here folks.

fixed GPU voltage & clock control
changed mali drivers with the one in galaxy-note
some usb driver fixes…

I cant say I've noticed any obvious gaffs yet, and for me, this one is the smoothest yet on Go Launcher. TW4.5 is still as silky smooth as ever.

Roll on v2.4.2! :)
 
Yeah go launcher is nice and smooth. The internet loads nice and quick as well. So I guess its wait and see how it performs on battery.
 
OMG. Smoothest siyah since beta6 for me. gonna keep this one on for a bit and see how the battery goes. smooth, good benchmarking, and all round happy days so far:D:D:D

(ironass must have a hospital appointment today, he's being rather quiet

and where's slug these days????)
 
where's slug these days????)

Boo!!! :eek:

I'm lurking around, but haven't had much time to enjoy the company here thanks to the call of duty elsewhere on the site. :(

A quick-and-dirty AnTuTu run shows v2.4.1 on par with 2.3i at my own stock settings (200/1200MHz, lulzactive + sio). Here's hoping battery stamina is similarly unaffected - v2.4 was looking good in the short time I was able to test it.
 
i've had spotify streaming some music for 20minutes or so whilst I hide in my office, normally i'd loose 1-2% doing this, but battery gone done 10%:eek::eek::eek:

will give it a day or 2 to settle in and check wake locks etc but that's a bit concerning........
 
I use AVG...You just have to tell it to ignore checking su

At the moment AVG tells me the ChainsDD Superuser package is a virus every time I try to update it in Android market.

Do you mean by your earlier post that I should tell AVG not to check the ChainsDD Superuser package?
 
i've had spotify streaming some music for 20minutes or so whilst I hide in my office, normally i'd loose 1-2% doing this, but battery gone done 10%:eek::eek::eek:

will give it a day or 2 to settle in and check wake locks etc but that's a bit concerning........

I'm not too sure on the battery life either. But there might be a fix soon.

gokhanmoral said:
I will post v2.4.1i later this night (I hope) it will have SCHED_MC enabled and there will be no other difference. let's see if it really helps with the battery life. I will download and compare the scheduler part with linux-linaro-3.1 kernel to make sure there is no missing parts again.
 
Back
Top Bottom