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

Siyah Gingerbread kernel (v2.x)

My findings so far on 2.6.8 v 1.3.2 is that siyah very slightly has the edge in terms of smoothness, but only slightly I emphasise.
Neak gives me 0.5% per hour overnight drain whereas siyah is eating 1% per. Too early to say categorically however.
see how 2.6.9 performs now....
 
Would you mind posting your init.d script(s)?

#!/system/bin/sh
##################################################
## Voltage Control boot script by xan and nitr8 ##
##################################################
LOG_FILE=/data/volt_scheduler.log
rm -Rf $LOG_FILE

echo "Starting Insanity Volt Scheduler $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

echo "Set MIN Scaling Frequency" | tee -a $LOG_FILE;
echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo ""
echo "---------------"

echo "Set MAX Scaling Frequency" | tee -a $LOG_FILE;
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo ""
echo "---------------"

echo "Set Scheduler for stl, bml and mmc" | tee -a $LOG_FILE;

for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk* ; do
echo "deadline" > $i/queue/scheduler;
echo "$i/queue/scheduler";
done;
echo "---------------";
echo "Set governor" | tee -a $LOG_FILE;
echo "lulzactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ""
echo "---------------"

#UV_BEGIN#

echo "Set UV" | tee -a $LOG_FILE;
echo "1400 1300 1175 1050 950 850 850 850 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo ""
echo "---------------"

#UV_END#


#GPU_BEGIN#

echo "GPU clocks " | tee -a $LOG_FILE;
echo "160 267 " > /sys/devices/virtual/misc/gpu_clock_control/gpu_control
echo ""
echo "---------------"


echo "GPU voltages " | tee -a $LOG_FILE;
echo "950000 1000000 " > /sys/devices/virtual/misc/gpu_voltage_control/gpu_control
echo ""
echo "---------------"


echo "Charging current " | tee -a $LOG_FILE;
echo "650 550 450" > /sys/devices/virtual/misc/charge_current/charge_current
echo ""
echo "---------------"

#GPU_END#

echo "Insanity Volt Scheduler finished at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

There you go. Its been made using voltage control.
 
Yes! I got 7595 with the same config. I win! I can load pages 0.00000001 seconds faster!! :D

Quite smooth indeed.

well done m8, you are really fast! :D i`ll check 2.6.9 tonight and will see results :p

ps. btw, i cant do screenshots (home+power). any ideas where to turn it on? or there is some zip to install from kitchen? i use jkay 13.3.8 as newest one doesnt work too good with my theme...

Help pls :o
 
So far seems good

Cheers Syd! :rolleyes:

The KoD, (Kiss of Death), lives on.

Have spent about 8 hours on v2.6.9 and I'm afraid it's not for me, my phone and my usage.

Very smooth I must say but I managed to break it almost immediately.

It certainly doesn't like anywhere near the sort of u/v'ing that, say, v2.6.7 endured at my hands.

I tried the full range of schedulers and governors with v2.6.9 and the best I could do was about -50mV across the board before I started to encounter lags in screens opening or a big delay in Maps when, using satelite mode, I tried to zoom in and out.

Am back on v2.6.7 and everything is smooth and fast with no lags or problems with my u/v'ing. :)

UPDATE

Disregard the above. It was all my fault. See post #1139. Duh! :o
 
This new Siyah is a bit clunky with the patented ironass voltage control / lulzactive settings (hereby known as IVCL settings). I didn't actually try IVCL on 2.6.8 but they work very smooth on 2.6.7. I'm not usually one to revert back to a previous Siyah but if the greatly anticipated 2.7 fails to impress with IVCL, I might have to break my trend.
 
I have to say I'm impressed. 7 1/2 hours off charge overnight and 10 minutes browsing this morning and my batteries only just dropped to 99%.
 
Hmm, nothing in either should affect anything other than voltages. I'll admit that I haven't bothered to zero my own config out to check if the kernel defaults have altered, though. That's something for tomorrow if the weather remains cack.

OK... hands up all those who made an I.D. TEN T. error when installing Siyah 2.6.9! :mad:

(ironass sheepishly raises hand :o )

I was tossing and turning in bed last night when it hit me. I hadn't done a kernel wipe before installing v2.6.9 as I was out and about when it was launched and downloaded and installed it immediately. No excuse... I know.
A real noob error!

Have reinstalled it, "properly", this morning and all seems good. :)
 
Be aware the latest voltage control has the facility to save your settings as a service, so its init.d script will not be in effect.

2.6.9 is behaving itself very well for me. Extremely smooth. using noop/conservative. Quite aggressive undervolting, but mainly in the lower MHz range.
Had an unusual battery drain last night. I generally find NEAK better on battery, with Siyah to be slightly smoother, but last night on 2.6.9 my battery lost a grand total of 1% in 7.5 hours. I assume this might be incorrect! If it isnt, then I could have a winner here! More testing is in order tonight.

I would like to add however, when I was testing CheckROM 5, scrolling through the home screens and scrolling up+down the settings menu was smoother than I've ever seen it before, and this was using the bundled kernel (I assume it's a chainfire one). Shame chainfire doesnt support BLN.
 
1% drain is more than possible with the kernel, well for me at least, so I would take it as accurate. I lost 1% with the same amount of sleep time plus 10 minutes browsing.
 
I find after its been charging for quite some time (so its been on 100% for a while) it can take some time for it to make its first percentage drop. Perhaps there is an overcharge, or the reported 100% is not a true 100% but a calculated (and rounded up to nearest integer) percentage in which case when the battery indicator ticks over to 100%, there is still some charging left to get it to its true 100%.

For my case, I was on 36% when I went to bed, and 7.5 hours later I was on 35%. I've never seen such a slow drain before. 97% deep sleep, which is usually the norm, so I'm inclined to think its somewhat bogus. I'll take another test tonight.
 
I'm using 2.6.9 with Shotgun84's undervolt settings but using governor OnDemand instead of Lulzactive.

I hadn't realised that Voltage Control saves init.d scripts rather than using a service - that is great.

I had been using Thunderbolt! with 2.6.7 but subjectively felt the performance/battery were not as good as 2.5.2b. I wondered if Gokhan stopped including much of Thunderbolt! in the kernel because he didn't find any benefit.

Does anyone have any thoughts about Thunderbolt! and its effectiveness?

Is anyone using Thunderbolt! scripts?
 
I see your point. I'll give it a test as well when my battery isn't on 100% and see what happens.

In fact, going by the changelog, its a "feature" of 2.6.9! :confused:....

set topoff current in battery driver to 100mA (stock value is 200mA) to ensure that the battery is fully charged before the charger circuit stops charging. Your 100% level will be a bit higher than before.
 
In fact, going by the changelog, its a "feature" of 2.6.9! :confused:....

set topoff current in battery driver to 100mA (stock value is 200mA) to ensure that the battery is fully charged before the charger circuit stops charging. Your 100% level will be a bit higher than before.

Where exactly i can change topoff current ? is it in initd script?

Help pls :o
 
Where exactly i can change topoff current ? is it in initd script?

Help pls :o

I believe hawker is quoting the changelog from Siyah 2.6.9. Gokhan is saying that he set the topoff current to 100mA. So it's not really an instruction as much as it is an FYI.

I know you can set the Charging Current in the Voltage Control app, but I'm not sure how to play around with it (again I just following IVCL).
 
Back
Top Bottom