yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ts1506:
The 100mhz step consumes more battery than 200mhz. Some i9000 devs discussed it, and it turned out that 200mhz consumes 0.7 some unit/hr, whereas 100 uses 1 unit/hr.
[Galaxy S I9000 Android Development] .:Crack:.:
Thanks for the insight (do you have a source?) but I don't see how this has anything to do with the ability to undervolt?
[Galaxy S I9000 Android Development] ts1506:
It was in some kernel thread, most probably during the early Jb times.

And no, it doesnt affect undervolting. Just raise the min clock to the next step and undervolt it, if the earlier step is unstable.
[Galaxy S I9000 Android Development] .:Crack:.:
Well the problem for me is that 100 and 200 are unstable if I uv as i normally do. But if you take a look at selective liveoc and hopefully include it erveything will be fine :)
[Galaxy S I9000 Android Development] senotrius:
a suggestion to the developer.please ads FAQ/links on

1.zram.how to edit and set this up is on page37.plus rwx rwx rwx permissions in init folder.I didn't know it was called 777permissions btw.

2.playing 720p videos.I had flashed and reflashed the cyancore kernel with and without big mem. no use until I flashed the big mem lib files uploaded by another member a few pages ago.for those who have issues playing 720p files despite the libs being already incorporated in the kernel.

the kernel is on the aggressive side.even killed real racing 3 while I was playing it.something to do with I/o or task manager values, oom etc?.(no I had played the same without issues on devil kernel but that's not the point)

thank u for the continued support.
[Galaxy S I9000 Android Development] ts1506:
About the permissions

r=4, w=2, x=1, therefore rwx rwx rwx rwx=(4+2+1) (4+2+1) (4+2+1) = 777

720p libs are flashed with kernel, but I will still check why it is not being flashed/used.

And the last point, foreground app isnt killed under any circumatances. And those settings are same as semaphore. Maybe you installed some script which is acting up.
[Galaxy S I9000 Android Development] solar666:
ts,

does this mean that we shouldn't use lock to min frequency 100MHz in the semaphore looking at your statement?
[Galaxy S I9000 Android Development] nereis:
Stratosk says that he uses lock min to 100mhz "just to be sure", not sure what that's about but I've always used that too.
[Galaxy S I9000 Android Development] ts1506:
The lock to 100mhz option locks the cpu only when the gpu is inactive, else cpu is locked to 200mhz with inactive gpu
[Galaxy S I9000 Android Development] senotrius:
@ts, these are the scripts I use plus zram.could they cause the issue I was talking about.opera mobile/mini kills off by itself too after a while.the launcher.etc.is it memory leak?

also ram is always full.like 6mb free even if nothing is running.I understand how android works utilising ram/memory(not a big fan of this).but what good is it if it can't free up memory when its needed? like when using the browser or playing games.
[Galaxy S I9000 Android Development] solar666:
Hi ts,

That's already clear enough but I was thinking about the power consumption in this context.

More power with 100 than compared to using 200MHz?
[Galaxy S I9000 Android Development] aToS88:
Except the case when OutOfMemoryError was thrown ;)
[Galaxy S I9000 Android Development] ts1506:
6mb free is too low. How are you measuring free ram.

That situation doesnt occur usually.
[Galaxy S I9000 Android Development] ts1506:
CyanCore 2.5.1 uploaded and attached to OP.

Changelog

1. ROW Scheduler tweaked (thanks for crack bringing this to my notice)
[Galaxy S I9000 Android Development] senotrius:
@ts, one method I use is that of slim bean ram bar on the recent apps list.of course I'm not sure this is correct always.but I also use system tuner and the inbuilt android task manager.the free ram situation isn't always like that but yes the phone gt laggy after a short while of using-browser, opera mobile,.meanwhile apps in background like network monitor mini, better battery stats, deep sleep battery saver, launcher gets killed-reopened all the time..not an issue if im playing game but while browsing?real racing 3, opera, browser,main app closes:results in message saying app has stopped.has not happened to poweramp for eg.but forget multitask.I think its I/o/memory related in my case.game performance varied with different schedulers.
[Galaxy S I9000 Android Development] ts1506:
For the correct RAM reading , select Applications only in RAM bar settings.
[Galaxy S I9000 Android Development] .:Crack:.:
Thanks but ROWQ_PRIO_LOW_SWRITE needs to be 2 instead of 12 :)
[Galaxy S I9000 Android Development] ts1506:
The commit was incorrect ?

EDIT: Both mako and tuna kernels seem to use 12 , and not 2 ..
[Galaxy S I9000 Android Development] senotrius:
this shows free as 268 to 312+ mb in slim ram bar.the exact opposite is seen in android system task manager.used is 268+.so still unsure about slim cause with that amount of free ram real racing3 should run just fine.instead it just closes or stops running. but the game ran with same specs in devil.so that's why I'm thinking its got something to do with the schedulers or memory managent.memory leaks or so forth.the setting used in devil was sio with on-demand. i could of course try factory format slim but not sure if its useful for kernel.
[Galaxy S I9000 Android Development] .:Crack:.:
2 is correct.
[Galaxy S I9000 Android Development] ts1506:
CyanCore 2.5.2 uploaded and attached to OP

Changelog

1. Small fix to ROW tweaks

2. UHID compiled as module
[Galaxy S I9000 Android Development] ts1506:
I looked at selective Live OC. Seems it is fairly straight forward to implement. Will look closely this weekend.
[Galaxy S I9000 Android Development] kernelfreak:
Hey,

There is a option to add smartassv2 pls?
[Galaxy S I9000 Android Development] ts1506:
Its there.

Download Semaphore Manager to load modules.
[Galaxy S I9000 Android Development] senotrius:
@ts, problem solved for rr3 game.does not shut down on itself.haven't tried playing for more than 10 minutes thou.2.5.2 kernel, row scheduler, on-demand, live oc of 114%.have not checked if background apps get killed.but happy that i was able to play the game like before.keep up the progress :)

enable 4x msaa.couod your kernel support this?right now it can't be enabled on our phones.
[Galaxy S I9000 Android Development] midnight911:
I don't think our phones will perform well with 4x MSAA. It makes more sonse on more powerful devices.
[Galaxy S I9000 Android Development] ts1506:
There is an option to enable 4x Msaa in developer options. I guess it works, cause graphically benchmarks fps lower quite a bit with it ticked.
[Galaxy S I9000 Android Development] ts1506:
For those who need the uhid driver, it was compiled as module to save 1mb ram.

You may load it via a simple insmod command, for reference, see the zram script's method of loading the module.
[Galaxy S I9000 Android Development] senotrius:
just wish the kernel would not try to kill just about anything that runs in background.getting almost stable live oc at114.had a reboot once with this setting.
[Galaxy S I9000 Android Development] ts1506:
The reboot is due to your phone not being able to handle it.

And I havent changed anything which could lead to apps being killed. They are the same as stock Semaphore.
[Galaxy S I9000 Android Development] ts1506:
My exams are approaching, wont have time to update this. I will put out an update with semaphore 2.9.23 changes today, but the next one will be after my exams end(about may 12-14)
[Galaxy S I9000 Android Development] 1Ishara:
Hi dev can i use this kernel with semaphore manager.. Or/ and should i need other app to change the settings:confused:

Sent from my GT-I9000
[Galaxy S I9000 Android Development] ts1506:
Yes, you can use Semaphore Manager
[Galaxy S I9000 Android Development] Yuna:
But i don't see there ability to load ROw scheduler module, or another cpu governor.

any ideas?
[Galaxy S I9000 Android Development] solar666:
C'mon use semaphore manager as stated just 1 post above by ts :banghead:
[Galaxy S I9000 Android Development] Yuna:
In it i can't see required modules.
[Galaxy S I9000 Android Development] solar666:
Look into the tweaks. There you can change the scheduler.
[Galaxy S I9000 Android Development] Yuna:
oh. Found it
[Galaxy S I9000 Android Development] ts1506:
CyanCore 2.5.5 is uploaded and attached to OP

Changelog

1. Update Base to Semaphore 2.9.23s

2. Update Linux Kernel to 3.0.75

3. Some stuff I had forgotten before

4. Tweaks to CFQ Scheduler
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel 2.6 uploaded and attached to OP

Changelog

1. Normal CPU OC Steps ( 1400,1300,1200 and 1100MHz )

There is a slight bug, CPU steps dont persist after reboot, they go back to 100 and 1000MHz.

There are two solutions

1. Use NSTools or equivalent software

2. Use my init.d script

#!/system/bin/sh
# Sets the min frequency
echo 400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# Sets the max frequency
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

The 1st one is the minimum frequency and the 2nd one is the maximum frequency.

Another thing , dont change voltages using Semaphore manager , and it doesnt support all the steps , use NSTools instead.
[Galaxy S I9000 Android Development] ficko_98:
[MENTION=4823985]ts1506[/MENTION] check the script :)
[Galaxy S I9000 Android Development] ts1506:
What ?

EDIT: Found and fixed. :P
[Galaxy S I9000 Android Development] ficko_98:
i think for max freq need to be scaling_max_freq
[Galaxy S I9000 Android Development] NDeaz:
Wow, good work, thx!

But do you think that stock voltages good? On 4.1 i use 1450mV/1400mV/1350mV for 1400mhz/1300mhz/1200mhz as on devilkernel.
[Galaxy S I9000 Android Development] ts1506:
Here are the voltages used

1400MHz

ARM - 1450

int - 1200

1300MHz

ARM - 1400

int - 1175

1200MHz

ARM - 1350

int - 1150

1100MHz

ARM - 1300

int - 1125
[Galaxy S I9000 Android Development] dashqa:
Hello ts1506 !! Could you tell us your ondemand settings? In signature it says you use tweaked ondemand:cyclops:
[Galaxy S I9000 Android Development] ts1506:
Now I am using

Smooth UI - On

Early Demand - On

IO is busy - On

Sampling down factor - 4

Sampling down momentum - 16

Sampling rate - 20000

Up threshold - 65

Gradient threshold - 40
[Galaxy S I9000 Android Development] ts1506:
It seems that CPU steps dont stick only if we overclock using Semaphore Manager.

If using NSTools to control Live OC , it works fine.
[Galaxy S I9000 Android Development] Alberto96:
No-Frills CPU Control app is working correctly for Normal OC. If you want an All-In-One app without NSTools and No-Frills, use Cpu Control by Juwe11: https://play.google.com/store/apps/details?id=com.smartprojects.CPUControl&feature=search_result

You can find also a lite/free version on play store.
[Galaxy S I9000 Android Development] ts1506:
Oh thanks , will remove it then.
[Galaxy S I9000 Android Development] tsatomas:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.1

Hello, it is nice to find your kernel (thanks to franzyroy), hope to add voodoo color.

I would like to ask you if there is s way to trigger ringer volume because my phone is rather quiet. The In call volume does not help.
[Galaxy S I9000 Android Development] fmc000:
Well, in my case I've ticked bigmem and have no FC at all, it works flawlessly. Also, I don't have options to choose, neither 480 nor 720. Please look at the screenshot.
[Galaxy S I9000 Android Development] empulse92:
they've beeen talking about video recording

would like that too :good:
[Galaxy S I9000 Android Development] pxrave:
new feature ;P

change the default govenor etc

to interactive and row

device is much more responsive after that ;)

good luck with this new kernel but remeber without stratosk this thing could never happen
[Galaxy S I9000 Android Development] ts1506:
True that , I personally see my kernel as an enhanced version of Semaphore , not as a full standalone kernel that I developed.

Next version I will tweak the default values for the ondemand tunables as I use them .
[Galaxy S I9000 Android Development] arjiegodz:
Re: [JB 4.2][KERNEL] CyanCore Kernel v1.1

can u make it work to sc02b?
[Galaxy S I9000 Android Development] ts1506:
Do you know what changes are needed for SC-02B ? Maybe some reference reading material ?
[Galaxy S I9000 Android Development] fmc000:
Me too of course.
[Galaxy S I9000 Android Development] rubervalrfl:
ts1506, good afternoon, I would ask your permission to port the kernel that you are compiling for our Brazilian model (GT-I9000B) as I already do the semaphore and you relied on it, your will not be so complicated, I have a permission?
[Galaxy S I9000 Android Development] ts1506:
Why not ? I have made very little change as it is.
[Galaxy S I9000 Android Development] rubervalrfl:
Ok, Thanks, I'll do the fork of the repository and start today, thank you so much, and a good job to you.
[Galaxy S I9000 Android Development] ts1506:
Please wait 5 mins , I forgot to upload some changes I did.
[Galaxy S I9000 Android Development] rubervalrfl:
Quiet, only make the night, yet here are 14:15 pm.

Thank you.
[Galaxy S I9000 Android Development] ts1506:
I have made the last change , now you can do whatever you want.

Also , I have attempted to add more CPU steps in the past , but failed. If you succeed in adding those , please send me a push request.

Same with ZRAM and KSM and SWAP, consider sending me a push request if you can enable that feature,

We should help each other eh.
[Galaxy S I9000 Android Development] rubervalrfl:
Quiet, actually, I inherited this compilation of cronot semaphore of a look at my github that you will see that there already have there.

https://github.com/rubervalflucas/samsung-kernel-aries
[Galaxy S I9000 Android Development] saschc:
AW: [JB 4.2][KERNEL] CyanCore Kernel v1.1

Can I use this kernel with FISHEARS 4.2.2?
[Galaxy S I9000 Android Development] ts1506:
I saw your github repo , but I cant find the commits for ZRAM , KSM and SWAP , except some changes in the semaphore_galaxysbmtd_config file.

But in the latest Semaphore code , the config files are far smaller , so I feared that those have been removed altogether than being disabled.

I would be very grateful if you can send me the commits to enable atleast ZRAM and KSM , SWAP is secondary.
[Galaxy S I9000 Android Development] rubervalrfl:
OK, OK, so I successfully get I send to you, ok.
[Galaxy S I9000 Android Development] Cu8eR:
Try adjusting voltages. Semaphore uses Live OC , so there is little point adjusting voltages if your phone cannot handle Live OC.

Here is a comparision of voltages of Devil and mackay

1400 MHz - 1450/1175 - 1350/1150
1200 MHz - 1350/1125 - 1275/1100

This is the answer... my phone is really unstable with liveOC and Semaphore kernel... Devil was OK, but I didnt know the values of voltages :)

Now I am happy again
[Galaxy S I9000 Android Development] ts1506:
I am attempting a modified Semaphore Manager to fix the issues.
[Galaxy S I9000 Android Development] NDeaz:
It is possible to add 1500mhz test step?

Remember, that this feature was on old 4.0 kernel.

For smartphones, which can work stable on 1400mhz or 125%+ liveoc.
[Galaxy S I9000 Android Development] ts1506:
No thanks.
[Galaxy S I9000 Android Development] Facebooook:
I am wating..
[Galaxy S I9000 Android Development] ts1506:
You must wait for quite long, as I will work on it after my exams
[Galaxy S I9000 Android Development] lonnieboy:
You've done more than enough. Every time I check there's either a new kernel or rom.

So much respect and appreciation for all the hard work.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Not sure if something is wrong but my phone is funny

So much stable at 1140 MHz 114% live oc

Then at 115% oc my phone randomly reboot into recovery and doesn't boot into os for even 5 minutes all of this changes only because of a extra 1% live oc wtf
[Galaxy S I9000 Android Development] alb3rtt:
i guess your phone can't handle that extra 1%. for me, 120% fully stable, 121% phone freezes instantly and the screen goes weird.
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Bro my phone can handle 1300 MHz normal oc
[Galaxy S I9000 Android Development] octolith:
It's been said 1000+ times, liveoc overclocks more things, not only cpu freq, but also bus freq, etc. And that's why 1300 MHz normal oc works for you, and 115% live oc doesn't. And that's why having higher normal oc steps is good: you could use 1200 Mhz normal oc + 114% live oc, so both cpu freq & bus freq can be maxed out. Correct me if I'm wrong.
[Galaxy S I9000 Android Development] .:Crack:.:
Might be the known issue.

Might be true but because of 114->115 I suggest a different problem.

If you read glitch 's liveoc tutorial you'll find the information that 115% is buggy. So either try 114 or 116+ and you must likely won't have problems.

Running at 124% with no problems...
[Galaxy S I9000 Android Development] .:Crack:.:
Does anybody have problems with 2.6?

It boot fine but after some seconds it reboots to recovery.

I suspected scripts or Semaphore Manager/NSTools/setCPU that change Voltages but still use 5 steps instead of 8. As far as I can see neither of them set anything -I deleted their data and cleaned init.d.
[Galaxy S I9000 Android Development] Facebooook:
No i have no problem with 2.6

I face only one time reboot to recovery problem when i install nstool and sema maneger both apk together.
[Galaxy S I9000 Android Development] ts1506:
Dont use multiple kernel control apps together.

Use NSTools , it shows all 9 steps for voltage control and does everything else just fine.
[Galaxy S I9000 Android Development] .:Crack:.:
Thats why I said i deleted all data. So they don't interfere.
[Galaxy S I9000 Android Development] ts1506:
Try uninstalling one of them and test.
[Galaxy S I9000 Android Development] alb3rtt:
Deleted
[Galaxy S I9000 Android Development] lookndbeat:
Fantastic kernel :)
[Galaxy S I9000 Android Development] .:Crack:.:
Uninstalled the apps but still didn't work. Wiped /data and worked after that...

Running stable at 1364MHz (Int 1150mV/Arm 1375mV) !

Just two things:

NSTools cannot change/see the governor (on devil kerne fixing permissions fixed that but not here...).

Min_freq in fact is 200MHz eventhough I set lock_min_freq....
[Galaxy S I9000 Android Development] alb3rtt:
To fix the governor issue, just download ROM manager and run fix permissions.
[Galaxy S I9000 Android Development] ts1506:
CyanCore Kernel 2.6.1 uploaded and attached to OP.

Changelog

1. Updated base to Semaphore 2.9.24s

2. Updated Linux Kernel to 3.0.76
[Galaxy S I9000 Android Development] alb3rtt:
When did you become a recognized developer? I just noticed that so Congratulations :)
[Galaxy S I9000 Android Development] ts1506:
Yesterday. Thanks.
[Galaxy S I9000 Android Development] Famzz:
Congrats man, you deserve it :)
[Galaxy S I9000 Android Development] Ahmad_Ashraf:
Let's make a party for you :)

Sent from my GT-I9000
[Galaxy S I9000 Android Development] akash6969:
Congratulations friend!:good:
[Galaxy S I9000 Android Development] senotrius:
how come zram does not get used much? in the past I could play power amp, play game easily at the same time without any small app in the background getting killed.I use 150mb for zram.how do I set other parameters like swappiness.I'd rather it get used than stay unused.
[Galaxy S I9000 Android Development] ts1506:
Modify the ZRAM script accordingly.

#!/system/bin/sh
insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/zram.ko
echo $((150 * 1024 * 1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0

Here is an example for ZRAM Disk size of 150MB.
[Galaxy S I9000 Android Development] senotrius:
I meant the other things.its there on page 37 how to change ZRam size.what about swappiness.
[Galaxy S I9000 Android Development] Yuna:
I completely disabled zram, and oc. as well as uninstalled semaphore/nstools.

now my phone don't lag :D
[Galaxy S I9000 Android Development] Rebel2k:
Don't know why, but every time I try this kernel on any ROM (tried Hellybean, Slimrom) it's lagging as hell. As soon as I reflash Semaphore, everything's fine again (but I definitely need Swap and/or Zram support). Do you have any idea of what could be the cause? Might my 1024 Mb SWAP partition be the cause?

For information, in the logcat, I can see thousands of "Connect" processes telling "Category not supported: 0"... I think that may be linked with what I notice...
[Galaxy S I9000 Android Development] METEMEDO:
Hi.

I had CyanAOSP v0.8.3 and Mackay Kernel v3.0.61.

Today i installed CyanCore, but the phone became completely unusable. Every app was ANRing and i couldn't even open the notification panel.

So i went back to Mackay Kernel but now my Wifi doesn't turn on! In system settings -> wifi, the on/off switch buttonis grayed out and it says "Turning on wifi" and it stays like that forever.

Please help.
[Galaxy S I9000 Android Development] alb3rtt:
UPDATE YOUR ROM!!!!1!!1 That would probably fix it, no need for flash cyancore after that because it is included with cyanaosp.
[Galaxy S I9000 Android Development] tsatomas:
Reflash Mackay kernel without wipe
[Galaxy S I9000 Android Development] aToS88:
I don't think you should use plain swap on this phone, it kills it completely. Unfortunately the I/O is very weak and has low performance so the phone is constantly trying to read and write from and to the card which makes everything slow.

I suggest you not to use swap, only in memory --> zram.
[Galaxy S I9000 Android Development] ts1506:
I think the old swap partition is acting up.
[Galaxy S I9000 Android Development] Rebel2k:
So you suggest I delete this old partition, right? With Devil Kernel it works like a charm though...

I'm going to try that but if that solves the problem, it may indicates the SWAP support isn't working as expected, am I right?

Thanks for your answers! :)

P.S.: Even if I don't use SWAP (I mean, I don't have any script running swapon -a for the SWAP partition, and I keep only Zram) the behaviour is the same...
[Galaxy S I9000 Android Development] ts1506:
SWAP and ZRAM cant co-exist at once. Its one or the other. SWAP works fine here ,but according to my tests (on both Devil and CyanCore) , swap actually causes more lags.
[Galaxy S I9000 Android Development] Rebel2k:
I can guarantee that if I use your Zram script and my swap script, both coexist. At least, the Swap section of the "free" command shows the amount of Swap + Zram...

Anyway, that's totally unusable... And can't find why. Even without any Zram or Swap, my phone is reacting 20 seconds after any touch command. Shouldn't it be the same as Semaphore if Zram and Swap are disabled? If no "swapon -a" command has been run, is the Swap partition used by the kernel?
[Galaxy S I9000 Android Development] ts1506:
Shouldnt be used. You must manually activate the swap partition. Have you try clearing cache.

And does all other kernels react normally ? I have tested the kernel on Hellybean , CyanAOSP , CM10.1 and SlimBean and they worked normally.
[Galaxy S I9000 Android Development] Rebel2k:
Yes all other kernels react normally during my tests. I tested semaphore, devil, stock cm. With or without swap it's the same.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] ts1506:
Strange, have you tried the kernel on other ROMs, maybe take a Nandroid and wipe and reflash the current ROM + CyanCore to test.
[Galaxy S I9000 Android Development] Rebel2k:
Yes that's what I told before. I tried CM10.1, Hellybean and Slimrom and that's slow every time. Really don't get it... Weird... And what makes me crazy is that I can't understand why...

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] ts1506:
What makes me crazy is that even I cant understand why.. I tested all those ROMs with every kernel release , and everytime it has been smooth.

Can you test CyanAOSP 2.5.2 (it comes with 2.6.1 kernel, and is running buttery in my phone).
[Galaxy S I9000 Android Development] aToS88:
I can confirm that Slim is running smooth and fine with this kernel with a little zram and no plain swap.