yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] huuub:
Hmmm, now I need a little help. I used to use VC for undervolting but I also want to make use of the AndreiLux’s settings.

Both are incompatible. So I guess my only option for the moment is to use scripts. Now my Noob question:

how to edit the folder /etc/init.d :p. (it seems write proteced when accessing my device on pc by SSH)

(and which undervolting script do I use best)
[Galaxy S II Original Android Development] spoiltz:
AnyOne here flashed SiyahKernel 2.6.11????

It comes with Red Pill Recovery, and not CWM???

So, can we still use the zip's made for cwm, or we have to wait for zip which are compatible with RedPill???

Also, will cwm app be still in use? Or it will become useless?

Also, the backups we made via cwm, still be applicable??
[Galaxy S II Original Android Development] huuub:
I can tell you that the backups are visible in it. Did not try to restore it :).
[Galaxy S II Original Android Development] Entropy512:
Changing the supply voltage of the LCD panel might completely alter the linearity curve of the OLEDs, altering color balance even if you don't touch the tables.

As has been answered in many places - when Samsung officially releases ICS. That is when Samsung will post source code for the kernel.

Have you noticed that there are NO custom kernels for I9100 ICS other than initramfs repacks? There won't be until source gets released.

Leaks are an oddball corner case of the GPL - Samsung is legally required to provide source to those they provide a binary to. But they technically never "provided" a binary to us - they provided it to someone else, and someone intercepted the transfer.

That's some interesting news, also, got a link to 89luca89's sources?

It's hard to tell - The fact that BTHID apparently DOES work with some kernels on newer bases is interesting. In the case of AT&T UCKK6 - there is no evidence they made source changes to the kernel. The stock UCKK6 kernel is broken with BTHID. However, if BTHID is working on some stock-derived I9100 kernels, that's evidence there ARE source changes. (Either that, or a defconfig change we haven't identified yet.)

As to "broke the whole bloody lot" - they sure did with UCKK6. Everything BCM4330 related in UCKK6 is a ****heap, and it's all (with the possible exception of BTHID) system image crap.

At least with some of the discussion here, I know where to look. Interesting observation - without changing kernels, if you run the following test:

arping -b <ip address of another machine on network>

from a machine on your LAN. (i.e. arping between two devices OTHER than the phone)

The CPU receives no wakeup interrupts on the AT&T UCKH7 base, battery life not affected

The CPU receives wakeup interrupts from the wifi chip on XXKI3 (Android OS skyrockets, drain goes way up, around 10%/hour or more)

Haven't tested UCKK6 yet

Oh, on another note: I've taken a look at Wheatley. It's interesting in design, but I'm not sure if it is applicable to Gingerbread Exynos. We have completely different available sleep states, so it is questionable whether any power savings are achieved without someone connecting a current sensor to the battery to determine exactly how much various sleep states can achieve. The concept of Wheatley is, however, why I don't include 100 MHz support in my kernels.
[Galaxy S II Original Android Development] remorema:
I made this installer(attached) and pushed it to system/etc/init.d and set cpu still shows siyah default cpu steps. what am I doing wrong ?
[Galaxy S II Original Android Development] Nono01:
I have one question. Sorry, but i am new to Android. As i understand, doomlord's .bat roots the phone, so why do i need to put siyah kernel?
[Galaxy S II Original Android Development] droidphile:
You mean this ?
[Galaxy S II Original Android Development] Mutalisk:
I'll glad the new recovery is now part of Siyah, thanks a lot!

Another question, not necessarily to gokhan:

As I've always considered this kernel to be a base for tweaking and customization (while already being excellent on default settings), I wondered if there are people interested in other governors from other kernels. (I know the governors implemented are good, but nevertheless ;))

Of course Gokhan could simply put them in, but that's not the point, the kernel should be as simple as possible.

As it's possible to insmod governor modules, is there interest in a thread where someone skilled creates and shares loadable governor modules one can separately put on sd-card and insmod it?

(I took a look at it, but I'm unfortunately a noob - no way I could do that :D))

So we could experiment with different governors with this great kernel without bothering Gokhan.

If it is technically impossible please forgive me,

I don't know much about how it really works in the end.

Was just thinking about further customization ;)

And Sorry for my English, i'm working on it ;)
[Galaxy S II Original Android Development] veyka:
Redpill is fully compatible with CWM5.x backups and zips, as its is based on it. Also the CWM manager app is fully compatible.
[Galaxy S II Original Android Development] SilverMist1:
does .11 have a screen off profile to limit cpu for ondemand?
[Galaxy S II Original Android Development] AndreiLux:
I don't know if you missed my post at the time but here it is again; undervolting surely would have some kind of effect (positive or negative) on the display:
[Galaxy S II Original Android Development] remorema:
can you please check whats wrong with "my" script ?
[Galaxy S II Original Android Development] Honusnap:
There are two overlaping zones with these settings .. IF 133 is 3.3x and 267Mhz 6.7x the performance of 40Mhz (suposition)

Than when being in overlaping parts .. we should choose the lower frequency ...

=> Meaning switching to lower frequencies where i put an O (when power needs go down it follow a lower frequency path)

040-#################

133-------#########O###################

267---------------------------#######O###################################

=> echo "90% 45% 90% 55%"

040-#################

133----------------O###################

267----------------------------------O###################################
[Galaxy S II Original Android Development] AndreiLux:
No that makes no sense. 40 is not half of 133. You did this with those values:

040: |#########+

133: |---------------###############++++

266: |-----------------------------####################################

You're also disregarding the up-threshold.. why?
[Galaxy S II Original Android Development] lpsi2000:
Exactly...:D
[Galaxy S II Original Android Development] droidphile:
Sure no other app (like VC) is setting something on boot which may override your script?

It's safer to change only first and last steps, 1696 instead of 1600 or 25 instead of 100 mhz and leave other steps as it is.

Add two more lines in your script, for a dirty trick to stick scaling max freq.

chmod 777 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "1400" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Galaxy S II Original Android Development] remorema:
I only use setcpu and the set on boot options are untagged

edit: made it look like this

#!/sbin/busybox sh

echo "1500 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo "100" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1500" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 777 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1500" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "100 160 267" > /sys/class/misc/gpu_clock_control/gpu_control

edit 2: no go. setcpu still shows 1600 as highest freq and wont allow to set 1500
[Galaxy S II Original Android Development] Honusnap:
In my UltraEdit graphic.. :) 133 is 3.3x greater than 133, you are right i messed me up with the proportional font... :)

Up-threshold is not a problem, it's just that when the frequency is going down, i suppose that the lowest frequency path is the best to choose. 90% seems ok for ramp up ... if the sample time is short enought... (which i don't how much is)

So i've corrected the graph with non proportional fonts..

040-###################

133------------------O--#####################################################

267---------------------------------------------------------------------O-------############################++++-

=> Your configuration is good now that my scale is non build with non proportional fonts .. :D, there is two small gaps..

Regarding 40Mhz Performance

040 is 1x

100 is 2.5x

133 is 3,3x

160 is 4x

267 is 6,7x

---------- Post added at 06:56 PM ---------- Previous post was at 06:47 PM ----------

Here is the scale for people that want to play .. :

040-0-1-2-3-4-5-6-7-8-9-X

100-0--.--1--.--2--.--3--.--4--.--5--.--6--.--7--.--8--.--9--.--X

133-0---.---1---.---2---.---3---.---4---.---5---.---6---.---7---.---8---.---9---.---X

160-0---------1---------2---------3---------4---------5---------6---------7---------8---------9---------X

267-0-------.--------1-------.--------2-------.--------3-------.--------4-------.--------5-------.--------6-------.--------7-------.--------8-------.--------9-------.--------X

Ps : I don't know why it is not correctly displayed on the forum.. scales are ok in my text editor
[Galaxy S II Original Android Development] AndreiLux:
You're almost there. The point is, when you are scaling down you want to end up in the "stable" area of the lower stepping, meaning in the #'s. That's why I have the +'s in my graphs depicting the area above the up-thresholds. If you scale down and have the load in that area, you'll scale up back again immediately... and in the end you'll end up with my values again. :)
[Galaxy S II Original Android Development] droidphile:
Check the content of the scaling_max_freq file using root explorer or any file explorer. If it doesn't say 1500, use the normal freq_table values (100 to 1600) and scale from 100 to 1400 or something.
[Galaxy S II Original Android Development] remorema:
Ill look into it. anyway I guess set cpu does everything I need regarding cpu. tks for your time
[Galaxy S II Original Android Development] legendasboy:
well going to stick on 2.6.9+ vc this script editing thing its way out of my league, and i'm satisfied with my phone at the moment, so if it works dont break it
[Galaxy S II Original Android Development] incubus_fr:
Sometimes you may set some values in your init script which will prevent your phone to boot (too much UV for example).

There are two main locations for these scripts:

/data/local/customboot.sh or /system/etc/init.d/bootscript, the latter generated by KcDaRookie excellent init.d Generator

I have made a CWM recovery flashable zip to disable these scripts. They actually will be renamed to /data/local/customboot.sh.disabled and /system/etc/init.d/bootscript.disabled.

After having saved this script on your sdcard (do this before it's too late!) and flashed it in recovery mode you will be able to reboot your phone with Siyah stock settings.
[Galaxy S II Original Android Development] Simba501:
Lol, that's a good attitude to take. Too many people try to dive into things they don't understand, and end up messing something up. Keep reading up on stuff; you'll eventually learn and understand those things.
[Galaxy S II Original Android Development] Honusnap:
Well i really messed up with these fonts.. :p Tooking an other approach with maths, it ends with :

"90% 25% 90% 45%"

40*90 = 3600

25*133 = 3325 => Good

90*133 = 11970

45*267 = 12015 => Not good cause > 11970

"90% 25% 90% 40%"

40*267 = 10680 => Good

Sorry for my mistake on my first post, i should have double checked before speaking .. :D
[Galaxy S II Original Android Development] :
heck i do not understand a thing on how to edit scripts...i tried but got bored half way through it and gave up:p

i have voltage control to do the work for me and if i do use a script it is only something like V6 supercharger(thanks Geko) or thunderbolt scripts(thanks Pikachu). Anything else i will pass unless it is cwm flashable or scriptmanager executable. To edit my own one blah forget it like the above poster said it is way out of my league. Would love to learn but i shall pass.

Still kernel is the bees bollocks and love tweaking around even if it is with apps i do it:D
[Galaxy S II Original Android Development] poochewer:
Actually sometimes its best to "if it works, break it and break it again!"

Cos thats how humanity learns things.;)
[Galaxy S II Original Android Development] AndreiLux:
Yea I know 45% is quite on the limit, but still acceptable, I used 90 25 90 40 when explaining it here, but Gokhan linked to my other post on the blog. I edited both to be the same.
[Galaxy S II Original Android Development] legendasboy:
dont mind to break it, if humanity pays me a new phone :)
[Galaxy S II Original Android Development] Sebsey:
[HELP] First kernel flash with starting problems!!

Hello together,

I just arrived a few days ago here at xda@galaxy s II, former I had a HTC HD2 with ICS. So I am kinda familiar with flashing, etc. :)

Today I flashed the newest kernel SiyahKernel v2.6.11 over my never flash-touched smartphone so far. I am now having the problem that whenever I receive a call and DO NOT answer it, the smartphone freezes totally! I have to take out the battery to restart the phone :(

My data (all stock / before flashing kernel):

Android: 2.3.4

Basisband: I9100XXKI1

Kernel: 2.6.35.7-I9100XWKI4-CL575468root@DELL143 #2

My data NOW (after flashing SiyahKernel)

Android: 2.3.4

Basisband: I9100XXKI1

Kernel: 2.6.35.14-Siyah-v2.6.11+gm@ubuntu #262

How did I flash?

I used Odin 1.8x and flashed the .tar file.

I really appreciate your work, nice job guys :) If anybody could help me out and pointing out the problem/mistake I made, I what me so thankful :)

Greetings, Seb
[Galaxy S II Original Android Development] Hannibal226:
Gr8 Kernel, no question!

But I can't find the right settings to play GTA III without crashes...

Any help?

Thanks in advance ;-)

Sent from my Galaxy S2 - I9100 with SlimRom!
[Galaxy S II Original Android Development] DeathMetalMods:
Is there allready a Stock SMS Fix around for 2.3.6 XWLA2?

(I found one in this thread for 2.3.5WWKI5 and was pretty thankfull for that...)
[Galaxy S II Original Android Development] karlesg:
Actually this is the only thing that troubles me the up threshold. Maybe 90 is a bit too high? Really I don't know.

If the sampling rate is short enough 90 is good. But if I had to choose between a short sampling rate combined with a higher threshold and and a longer sampling rate combined with a lower threshold I'd go with the second one. I'm not really a fan of very short sampling rates.

So playing safe here I ended up using

40 133 267

85% 20% 85% 40%

With these settings it seems that i don't get lags. But i'm not quite sure since i haven't thoroughly tested them yet, and maybe my whole thinking is wrong anyway...

What is your opinion AnderiLux?
[Galaxy S II Original Android Development] Honusnap:
OKkkk now i know that i understand it well .. good point.. :) and thanks for your patience.
[Galaxy S II Original Android Development] Kaffee4Eck:
After flashing the newest kernel i have hard battery drain very hard in 2 hrs without usw i lost 27-39%

I dont use setcpu or anything... No overclock
[Galaxy S II Original Android Development] Honusnap:
You can't have it all .. :)

- Fast response (ramping up / down) = Small sampling period = Higher battery consumption

Higher sampling period (lower sampling rate) means that you'll have to wait a longer time before making a decision :

- Slow response time

- More battery friendly cause it loose less power checking the sample and it will stay longer on the lower frequency (and lower voltage)

- It will absorb small peaks

It depends on how much the sampling is eating on the cpu side...

It it eat so much cpu than the sampling rate should be variable... depending on how much ramping up / down we haved in the last .. x minutes, increasing or lowering the sampling rate.
[Galaxy S II Original Android Development] karlesg:
Yes I know that's why I always choose the other path in my life. The more battery friendly one :) I care more about battery life than performance anyway. It's a philosophical issue... :p
[Galaxy S II Original Android Development] Honusnap:
Got a solution for you : Min frequency = Max frequency = 40Mhz .. :p;)
[Galaxy S II Original Android Development] gokhanmoral:
wait for the next version of voltage control app :)

it will both support GPU 3-step scaling and it will have a customizable tab to be filled dynamically by kernel developers (if they want to)

I also inspected that phoenix tweak app specs.

1-) it is not dynamic

2-) we already have all necessary modules loaded

3-) I will choose to support an open and universal implementation then supporting a paid app.

4-) some features are not kernel related and already available in custom roms

so, droidphile: thank you for giving the link to github for specs for phoenics (EDIT: oh, I think I found a new kernel name for knzo by making this typo: phoenICS) tweaks app but I don't think I will go that way. however, I think that the kernel sources should have been there instead of those specs.

anyway. I am back to work for the app :)
[Galaxy S II Original Android Development] karlesg:
lol!

why didin't i think of that??? :p

Anyway it's all about the battery/performance ratio... Some choose a liitle better performance, others a little better battery. How much this ratio will be, is strictly philosophical and personal :)
[Galaxy S II Original Android Development] zemariaabreusantos:
Lat time I came to this thread our kernel was on version 2.9 O.o Did you just rename it or went back in time of something of the sort? :P
[Galaxy S II Original Android Development] gokhanmoral:
I think it was 2.6.9 :)

I think we will soon reach 2.6.14 and we will have a perfect harmony with the linux base that we are using. when we reach that version the kernel will make your phone flash and talk about the meaning of life :p
[Galaxy S II Original Android Development] :
Check my sig and download the app from the thread to find out what causes your phone to stay awake. Find out more details from that thread mate
[Galaxy S II Original Android Development] AndreiLux:
The GPU sampling rate is a surprisingly large 1000ms.

/* Define how often to calculate and report GPU utilization, in milliseconds */
#define MALI_GPU_UTILIZATION_TIMEOUT 1000
[Galaxy S II Original Android Development] nikzDHD:
Gokhan, what do you think of the Wheatley governor?
[Galaxy S II Original Android Development] :
Haha nice one mate. You know were i am if you need a guinea pig. :D
[Galaxy S II Original Android Development] gokhanmoral:
I downloaded it but never tried or inspected the source. it's just on my disk and I think I will give priority to the universal app that all kernel developers will be able to use.
[Galaxy S II Original Android Development] bpivk:
I had a big battery drop when I flashed this kernel. Look at the picture.

Can it be just a battery charge reporting error or something?

You can see when I flashed the kernel. It's when the charge fell off the cliff. :D
[Galaxy S II Original Android Development] jrsoft:
Hi gokhan!

Do you know the problem with this xploit?: Linux Local Privilege Escalation via SUID /proc/pid/mem Write

http://blog.zx2c4.com/749

I do not know if AOSP has already solved the problem :confused:
[Galaxy S II Original Android Development] karlesg:
been there, done that...

see previous posts :p
[Galaxy S II Original Android Development] :
Gokhan...I would prefer savaged zen modules:p

Bloody hell never knew i would be so interested in kernels as of late more than roms:D
[Galaxy S II Original Android Development] nikzDHD:
Kernels are the new roms, a good kernel is more efficient than a new rom I think.

As shown by Pulser and VR.
[Galaxy S II Original Android Development] gokhanmoral:
that happens after flashing a kernel sometimes.

it is a problem with our fuel gauge chip and it behaves strange sometimes.

you may even experience that your phone charging without a charger after having that problem
[Galaxy S II Original Android Development] gokhanmoral:
I don't know about that but it is an interesting reading.

we can use it to root our phones without flashing any custom kernels maybe :)
[Galaxy S II Original Android Development] Mutalisk:
That's exactly what I ment 1 or two pages ago:

We should collect all avaiable governor modules somewhere (maybe other thread) so we can insmod them without always asking Gokhan to put them into his kernel.

Should be doable, I guess?! :)

Tweakening of this govs then can be done via scripts or maybe the coming siyah app :)
[Galaxy S II Original Android Development] :
Could not agree with you more mate. What you said is perfectly correct. For me as you said a good kernel is what makes the rom. Not the rom makes the kernel.:) Hence why i have taken such an interest in Siyah. :)
[Galaxy S II Original Android Development] Honusnap:
Every second is not a lot... i suppose this choice goes with the original configuration having only two frequencies... High or Low. The highest was only trigered for intensive graphical applications... perhaps rarely.
[Galaxy S II Original Android Development] poochewer:
I agree, i have seen this on quite a few occasions. This is why sometimes I have had to use a battery calibration app, even though I realise that SGS2s do not normally require batt calibration.
[Galaxy S II Original Android Development] :
would be good yes..but i can be patient and my configuration so far that i have been messing about with voltage control has not let me down so i can wait for the app and see what goodies that will bring..in the meantime i just follow the thread and anything i see and is worth learning i will read upon it and mess about with...and big kudos to droidphile for his sticky cause i always go back there to make my mind up regarding governors, modules and tweaks:)
[Galaxy S II Original Android Development] legendasboy:
ok been reading and know how to make the scrip changes but a strange thing happened, runned the script cleaner , and flashed the kernel but got into a bootloop, flashed the 2.6.9 again and everything worked again...any ideas?
[Galaxy S II Original Android Development] karlesg:
1000 ms is pretty slow... i like that :p

Which are the stock thresholds used by Samsung for 160 - 267 ?
[Galaxy S II Original Android Development] :
yes do not use script cleaners..if you want to remove voltage control scripts just go into the app and press menu and then select boot settings. if you have thunderbolt scripts just get the restore script from pikachus thread and use that. end of..:) i am not saying that cleaning scripts would not work but is best to delete yourself the scripts you want and if you do not know ask in the appropriate thread and use rootexplorer to do so. cause you might delete a script that is being used regarding the rom you are using and that might cause the bootloop
[Galaxy S II Original Android Development] Mutalisk:
That's right, his sticky is really great!

I think I'll at least try to start this "project", I am a noob and can't extract the

Cpufreq_governorname.ko modules out of the kernels, but I can kindly ask the kernel devs to send me them :D

Gokhan, would you be so kind and send me the "governor modules" you have? :)

If that whole thing is a stupid idea just tell me and I'll shut up :D