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

Siyah Gingerbread kernel (v2.x)

Found a super lightweight battery manager called Battery Hero. It's only 42kb and all it does is turn off data when the screen locks. You can configure many settings such as how long to wait before turning off data and whether to turn on data when the screen is on or after the phone is unlocked. I'm trying it instead of JuiceDefender.

If you constantly lock and unlock your phone, then I guess this is not of much use as repeatedly turning on and off data would use more battery, although this could perhaps be minimised by setting the time to wait to turn off data to longer.

I am sticking with 2.5.2b for now.
 
fonegyro said:
Since flashing 2.6.1 and the batt zip v3 and then undervolting each clock step by 75mVs, my phone runs warmer than it ever has.
Click to expand...

The voltages are already reduced in the battery-friendly settings, and 75mV on top of that is a heck of a reduction over stock. Also, as noted previously by Gokhan himself, it's not a linear process; some frequencies can be undervolted further than others.

I've had problems with text editing in the browser (particularly here on the forum), the cursor can't always be placed at the end of the text being edited. I had the same problem weeks ago but thought it had been ironed out.
Click to expand...

Look at /sbin/siyah/tweaks.sh for an example of how to reset screen sensitivity back to stock, and see if that reduces or eliminates the problem.
 
Running cooler now, the heat was probably due to nothing more than fairly intensive usage.

caplja said:
Thank you. I've done it without problems. I'm only interested now in these battery.zip files, do I need that despite of using JD ultimate ?
Click to expand...

You could try running JD without flashing the battery zip for one full battery discharge, then recharge, temporarily uninstall JD, flash the battery zip and run the battery down again to see how they compare.

Some have commented that JD isn't all it's cracked up to be and is actually a bit of a resource hog... it gets a lot of good reviews on the market though.
 
hawker said:
I have to say i'm not getting on with 2.6.1 at all.
Lost 8% battery over night (10 hours) which is double my usual drain.
I'm back on void.echo for the time being, and perhaps switch to 2.5.2b if I get fed up of no boot animation.
Click to expand...

Merry xmas to all.

I have been updating to the latest kernel the last few weeks. And I have also found that 2.6.1 seems to go down quite fast compared to 2.5.2b -- considering reflashing to it for now.

I saw some people said that the screen was dimmer on 2.6.1 -- I also experienced this. Thanks for the battery.zip update.
 
Full list of 2.6.2 updates so far:

added lulzactiveV2 (thanks to tegrak). you can new lulzactive tuner app from the market to tweak lulzactive parameters.
disabled smooth scaling for interactive based governors (interactive, interactiveX and lulzactive).
changed the wifi drivers again.
LZO compression for the kernel image instead of gzip. it has less compression but faster decompression. (in this case, bigger is better )
New mali drivers from Galaxy Tab Plus (and “maybe” I will add one more level to gpu stepping, 160-266-300 just like in tab plus)
 
Slug said:
Oh what an exciting life I lead! :rolleyes:
Click to expand...

Living on the edge old boy... living on the edge! :D

Well, I've downloaded and installed the lulzactive app from the Market but am leaving it alone tonight.

Just running 2.6.2 with hawkers, "GoodScreen" battery script for Siyah. I'm sorry gokhanmoral but your battery script is just too dark for my poor, tired, old, eyes. Using stock voltage from the battery script... the new lulzactive v2 governor (called, "lulzactive") and the sio scheduler.

If you get really bored Slug, I'm open to suggestions on u/c'ing, u/v'ing and some ideas on the lulzactive app.

No rush old son... I'm going to bed now. :D
 
"fixed ondemandx governor" from 2.6.2 - does anyone know what was fixed and if it affected 2.5.2b?

Presumably I can change the script in siyah-battery.zip to use LulzactiveV2 with the following:
echo lulzactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Can the below LulzactiveV2 parameters be set by echoing?
int_cpu_load: 95%
pump_up_step: 4
pump_down_step: 1
screen_off: 200MHz
up_sample_time: 10,000us
down_sample_time: 40000us

eg. something like:
echo "95%" > /sys/devices/system/cpu/cpufreq/lulzactive/int_cpu_load
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
 
ironass said:
Living on the edge old boy... living on the edge! :D
Click to expand...

Living on the breadline, more like. That'll have blown most of my remaining VR payoff - 4.5hrs of drying it took! :eek:

I'm sorry gokhanmoral but your battery script is just too dark for my poor, tired, old, eyes.
Click to expand...
You'd hate my setup then, as it's even dimmer due to my liking of subdued lighting at home.

If you get really bored Slug, I'm open to suggestions on u/c'ing, u/v'ing and some ideas on the lulzactive app.
Click to expand...
I flashed v2.6.2, did some quick comparisons, and promptly binned it in favour of v2.6.1. I'll revisit it today now that one of my main complaints appears to have been addressed, namely....

mcarans said:
"fixed ondemandx governor" from 2.6.2 - does anyone know what was fixed and if it affected 2.5.2b?
Click to expand...

It didn't exist in v2.6.2! :)

Presumably I can change the script in siyah-battery.zip to use LulzactiveV2
Click to expand...

Yup, those are correct, Apart from screen_off, which I wasn't aware of as a parameter, I've done similar.
 
Thanks for the 2.6.2. I've flashed it few hours ago but my phone S2 managed to freez 4 times since then, 3 times in market and once when I was taking picture :/

I blame oxygen, because since I rooted it I have problems with kernel's. So mine question is can I now flash CheckROM from the CWM, restore apps from titanium and I'm finnaly done ?

this is what I have now :

 
Slug said:
Yup, those are correct, Apart from screen_off, which I wasn't aware of as a parameter, I've done similar.
Click to expand...

Would you mind posting your script as I'm unsure about formatting when echoing eg. "95%" or "95" or just plain 95?

How can I check that the parameters I've set in the script are actually those that are in use?
 
mcarans said:
Would you mind posting your script
Click to expand...

Here you go....

Code: 
#!/system/bin/sh
echo lulzactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "95" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
echo "1500 1350 1200 1000 800 500 350 200" > /sys/devices/system/cpu/cpufreq/lulzactive/freq_table
N.B. I'm using a custom frequency table with specific voltage values for my cpu so substitute your own frequency settings in that final line to avoid problems!

How can I check that the parameters I've set in the script are actually thsoe that are in use?
Click to expand...
Open the config files e.g. /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load and check that the parameter entered corresponds to the expected value. If it doesn't, and your script follows the above syntax, then your values are probably being overwritten by another script.

Custom ROMs often include init.d scripts containing performance tweaks, but I've found that many of these settings are duplicated in sbin/siyah/thunderbolt.sh and/or tweaks.sh. It's a bit of a headache trying to streamline things tbh. :(
 
Slug said:
Here you go....

Code: 
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
echo "1500 1350 1200 1000 800 500 350 200" > /sys/devices/system/cpu/cpufreq/lulzactive/freq_table
Click to expand...

I understand screen_off_min_step is for setting the frequency when the screen turns off - is that right? I am trying to decipher Tegrak's explanation. Does 5 set it to 500Mhz in your list of frequencies ie. do you count from the left of your list assuming 1500 is index 0?

So 5 would mean when the screen is off, the processor can only use clock frequencies from 200Mhz to 500Mhz - is that right?
 
mcarans said:
Does 5 set it to 500Mhz in your list of frequencies ie. do you count from the left of your list assuming 1500 is index 0?
Click to expand...

Yup, correct.

So 5 would mean when the screen is off, the processor can only use clock frequencies from 200Mhz to 500Mhz - is that right?
Click to expand...

You got it! It took an explanation from Gokhan before I understood how it worked. :o
 
Y'know, my phone is working pretty bloody well on S99 with the second battery mod (the one that Gokhan replaced first up) and with some mild undervolting. So far my phone has been on for 34h 55 mins, 17hr 18 min of that was in deep sleep and 14hr of that was at 100MHz (my phone never goes into deep sleep whilst charging). There have been so many updates recently, with conflicting reports on what is and isn't working, that I think I'm happy to stick with S99 for the time being - certainly until CheckRom v5 is released and/or a version of Siyah is posted that is markedly different / improved from teh current raft of offerings.
 
You must log in or register to reply here.
Back
Top Bottom