yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Pipperox:
Yeah we all may be living difficult times, but what i meant is: there is no need to donate 10$, if 25000 people download the kernel, then all it takes is that EVERYBODY donates 1-2€ (which is what, an ice cream?) and then the developer would have something to compensate his time, or at least to be able to buy a newer device to develop upon.

On the other hand i see forums which are distributing pirated Android games which cost 3-5€ in the market.. this is what i find disgusting.

Then people complain that on Android there are limited choices in terms of games or other apps compared to iPhone...

People were arguing that if video games didn't cost 50-60€ on consoles, and music CDs didn't cost 15€, then there would be no piracy.

Well, there you have it.

Anyway, enough with my ranting. :)
[Galaxy S I9000 Android Development] midikarma:
same thing happened to me, everytime... but no big deal...
[Galaxy S I9000 Android Development] stratosk:
Totally agree with you, my friend. But this is a big discussion... :)
[Galaxy S I9000 Android Development] stratosk:
Do you have virtual /cache checked in Semaphore application?
[Galaxy S I9000 Android Development] robogo1982:
So today I'm flashing away and I'm wondering:

What can happen if I flash 1.8.0 designed for JVT on an earlier ROM, say, JVQ?
[Galaxy S I9000 Android Development] Rebel2k:
That's working fine... ;) I'm on JVR right now.
[Galaxy S I9000 Android Development] stratosk:
Most probably everything will go fine. Remember that kernel sources we using are for JVQ. Initramfs is from JVT.
[Galaxy S I9000 Android Development] AceofSpades90:
how can i bring this kernel to captivate(SGH-I897)? i mean if i could reorient(somehow) and a little tweaking adding home key...(which i could do :P). anyways is it possible to reorient it?
[Galaxy S I9000 Android Development] stratosk:
I'm sorry, but I don't have this knowledge.:)
[Galaxy S I9000 Android Development] GreenSGS:
Thank you sir. I figured it out. One was bitdefender gone mad.40 % cpu use.

Could you plesde put some light on OC feature?Can I simply enable 1200 MHz from script manager or need to do something more. Is it stable there? Very noob question.

I notice highly increased number of Semaphore 1.8 users.Your kernel is become so popular.well deserved.
[Galaxy S I9000 Android Development] stratosk:
OC to 1200Mhz is pretty stable for most users and I think safe. You may choose it from test section of Semaphore app. This option will last until the next reboot of your device. If it is stable for you then you may choose it from overclocking options and this will be permanent (until you disable it).

I hope that this kernel is a good one and not just popular.:) Al least, this is my goal.
[Galaxy S I9000 Android Development] coldhandz:
Hi stratosk, just a quick question. Is it OK to flash v1.8 directly over v1.6? I have oc enabled uv settings, voodoo colour settings etc will my settings remain or will I have to reconfigure them?

Thank you for a fantastic kernel, great work.
[Galaxy S I9000 Android Development] stratosk:
Yes, you can flash it directly. I suggest you to disable OC before flashing and enable it again with the new scripts from semaphore script manager application. Voodoo color settings will remain the same.
[Galaxy S I9000 Android Development] AceofSpades90:
That's a heart breaker :o but I understand. After some research, i believe Hardcore or xcaliburinhand could help reorient this kernel. I used to have GT-I9000 and loved this kernel's color and fluent speed with Darky rom, now only if it could be available in captivate :) i believe it shouldn't be as much coding... here's a source from xcali site if you are still interested https://github.com/xcaliburinhand

Also, check my message in your inbox xD credit goes to exitz hands down :)
[Galaxy S I9000 Android Development] corgar:
got some problem with nandroid backup/restore.

factory reset -> full nandroid restore and got kernel partition corrupted. Had to reflash kernel via odin and after all was ok.
[Galaxy S I9000 Android Development] stratosk:
Let me check this when I have some free time. :)

Thanks for providing me information about this.

@corgar

I will check this tonight and let you know.
[Galaxy S I9000 Android Development] Kockowan:
Is IPV6 Privacy support included in Semaphore kernel?

Thx...
[Galaxy S I9000 Android Development] stratosk:
I checked kernel configuration and the option is there. :)

Did you face problems with it?
[Galaxy S I9000 Android Development] robogo1982:
Thank you for your explanation stratosk :) running 1.8.0bm for half a day now and my phone runs even faster and smoother. Tried OC test, works pretty well on 1200 MHz.
[Galaxy S I9000 Android Development] DanDroidian:
There is a lot of helpful info here about the different settings for Semaphore, BUT I still have many unanswered questions... I've searched but couldn't find much more info.

Surely there is a post/thread that explains ALL the tweaks in simple English and tells u the pros and cons..? Deadline scheduler, for example...? Please point me in the right direction if u can... Thx
[Galaxy S I9000 Android Development] Asterix040:
+1 for this. We could use some kind of "Semaphore for dummies"! :)
[Galaxy S I9000 Android Development] stratosk:
You may find information about your question here: http://www.semaphore.gr/how-to/use-modules-and-scripts
[Galaxy S I9000 Android Development] DanDroidian:
Thanks, but still doesn't really explain "what" they do... Scheduler?
[Galaxy S I9000 Android Development] pikachu01:
Information about scheduler can be obtained from my thread in my sig (Android Optimization Tips). CTRL-F for Scheduler.
[Galaxy S I9000 Android Development] =Dynamic=:
Can I flash Semaphore 1.8.0 JVT on JVS rom?
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Hi again stratosk,

I'm looking for a flashable mod that would change the governor and / or reduce max CPU freq on the screen_state change; i.e. when screen is off. So in order to save battery, it would change to the conservative governor and limit the CPU freq.

Now I've read on your OP that:

"- CPU frequency on stock music player when screen off to 400 MHz"

Does this means that the CPU lowers the freq when screen is off? Or only when playing music?

Also, would be possible to implement a "conservative" switch when the screen goes off? Maybe as a setting in the Semaphore app if you don't want to have that behavior as default.

Thanks in advance, looking forward to hear what you think!
[Galaxy S I9000 Android Development] Nergla:
I am running jvt_1.8.0bm on JVP and have experienced no problem
[Galaxy S I9000 Android Development] McDown:
stratosk thank you very much for your great work. I'm using 1.8 for over a week now and my phone stable as rock. The best kernel ever! :D

(my humble donation 3GV36073TH536711K)

I'm pretty sure you can.
[Galaxy S I9000 Android Development] =Dynamic=:
Well thanks !! ;)
[Galaxy S I9000 Android Development] Nergla:
Have one on me : 26X452471D132891M
[Galaxy S I9000 Android Development] stratosk:
Thank you very very much. It is not "humble". I really appreciate every cent that is donated.
[Galaxy S I9000 Android Development] stratosk:
I don't know what can I say! A thank you is just nothing!

Many many thanks my friend!
[Galaxy S I9000 Android Development] stratosk:
Hi,

There is a DVFS lock in the stock kernel which sets the minimum CPU freq when screen off in music player only to 800MHz. This was reduced to 400MHz.

Normally if music player is not running the minimum cpu freq is 100MHz.

I think (correct me if I am wrong) that the setcpu app does this kind of stuff.

But I really don't know if much battery will be saved if the governor changes to conservative during screen off. I mean normally the phone will go to deep idle. And will wake up only for short periods.
[Galaxy S I9000 Android Development] stratosk:
Hi again,

I just tried full nandroid backup and restore with no problem. I guess that something went wrong in your case but I don't know what. If you have time can you try it again? Did you notice any error during backup or restore?
[Galaxy S I9000 Android Development] stratosk:
OK, I understand what you mean. But it is a little bit difficult to analyze in depth every detail. And of course there are some things that I don't know in depth. :)

But, I will try to do it. Though, please be patient because there are many things to do and I have to find more free time.
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Thanks stratosk, always great to hear your opinions! :D

That's a good point; if the phone is in deep sleep, I don't know if it will improve much the switch to the conservative governor. Although that idea came from the good collection of scripts from Pikachu here:
[Galaxy S I9000 Android Development] stratosk:
The phone wakes up from time to time and do some stuff, but I'm not convinced about this.

Did you try this script? Did you have any noticeable difference in battery?
[Galaxy S I9000 Android Development] pikachu01:
I've tried this script :)

The screenstate_scaling is just as it is, it depends on the screenstate (not deepsleep). Doesn't matter if you're awake or asleep, as long as your screen is off, it'll use the SLEEP_GOVERNOR in which its default is conservative.

Go ahead and try it :) I've confirmed this through ADB (to check the governor), CPU Spy (to check the frequency scaling when asleep) and through battery stats monitoring.

It really does save battery.

Edit: SetCPU also does this (same implementation). The only problem is that the app is awake all the time, huge overhead. Script doesn't have a large overhead so battery savings are fairly noticeable :)
[Galaxy S I9000 Android Development] stratosk:
Do you have an estimated time of the phone being with screen off and not in deep idle? I'm mean in normal situation. With no apps running and preventing the phone go in deep idle.

I don't know but I'm just asking if you have ever tried to measure it.
[Galaxy S I9000 Android Development] HM.Carbide:
I've tried a lot of ondemand and conservative governor configurations, and tried to find out, battery drain/ all day performance behaviour.

The screenstate_scaling uses for awake:

ondemand, up_threshold=80.

Semaphore default:

ondemand, up_threshold=85.

Talon default is I think

ondemand, up_threshold=65.

Without describing the battery consumtion of conservative governor, i can say:

The talon setting with 65 needs a lot of battery.

Setting this to 80 as the screenstate_scaling does, saves a lot of battery for talon.

Not for Semaphore kernel, it will degrease the battery life, as 85 needs a bit less than 80.

In general I can give the following experience:

With semaphore ondemand 85, and the phone mainly not using I got battery time of 4days.

With any configuration (even my extrem battery save conservative) and using the phone I'll got a display time between 3,5h (min) and 5,5h (max). If I use it on block, the battery is empty -> 3,5h up to 5,5h battery time!
[Galaxy S I9000 Android Development] darckengel:
I would say, about less than 1% if you have sync off ...

I can have an entire night in deep sleep state.

And not much more with sync on

screenstate scaling is only usefull when you make a call, or listening musing without stock player. so when you make your phone working while screen off.
[Galaxy S I9000 Android Development] stratosk:
So, we have to find battery drain between conservative and ondemand during phone calls and generally during screen off with use of some apps.

It sounds no big difference to me. At least with the way I use the phone.
[Galaxy S I9000 Android Development] HM.Carbide:
I tested screenstate scaling for one battery cycle and had a bit lower battery time. But battery time is not a good measurement, so i can only say, that the script does at least not increase battery life significant.

But as i said, this is on semaphore kernel.

I think on kernels with aggressive ondemand configuration, you will see a difference in battery time, but this is mainly due to different awake configuration.
[Galaxy S I9000 Android Development] darckengel:
The scripts included his own governors configurations.

I found the conservative config very aggressive which can lead to worst battery life than with on demand (too low up thresold which lead to higher stable frequencies on some apps than with on demand).

In my opinion, the effect is almost placebo.
[Galaxy S I9000 Android Development] pikachu01:
I don't have an exact figure, but you can see Battery Usage and depending if you use sync/email sync, your battery will get high and screenstate_scaling helps bring this down.

Having a high display time will lead to higher battery usage. Display eats so much battery that even CPU battery usage pales in comparison. Having it 80 or 85 threshold doesn't really affect it much.

Not true. With it's current threshold setting at 70/35. It's a perfect balance that is less than ondemand's 80/85 threshold. I do admit though that it could go lower, but going lower would indirectly affect the delay when a call comes in and/or music playing stuttering(not on Samsung stock player).

70/35 is not really worse than ondemand's 80/85. At the very least 1GHz is used in lower ranges and most frequencies are at 400/800 and a dash of 200, with 400 being 3 or 4 times more than 200 and 800. (confirmed with CPU Spy).

This is in comparison with ondemand using 1GHz 7-8 (or even 20times depending on how much your screen was off) times more than 200/400/800. Now, which is more battery draining?
[Galaxy S I9000 Android Development] eng_saad:
Dear

I want to know how to active the lag-fix for this kernel?
[Galaxy S I9000 Android Development] Bushido76:
Hey eng_saad,

use the Ext4 app which is bundled to the kernel.

Bushido
[Galaxy S I9000 Android Development] jocke_lulle:
Download Chainfires ext4-app from CF-thread. Open app and Convert to ext4. You may have to try two times to get the convertion to start:)
[Galaxy S I9000 Android Development] eng_saad:
Thanks

I will install it
[Galaxy S I9000 Android Development] pikachu01:
Direct link:

http://xdaforums.com/attachment.php?attachmentid=591080&d=1304947623

From here:

http://xdaforums.com/showpost.php?p=12651371&postcount=7

Search is your friend :)
[Galaxy S I9000 Android Development] malcho:
Why to start two times to get conversion to start?!

Never had this problem with semaphore kernel.Only thing you need to do before convert is to free some space on system partition(delete unussed apps).Then ext4 app works without problem.
[Galaxy S I9000 Android Development] Bushido76:
It should appear in your app folder. ;-) Are you using Semaphore 1.8?

Bushido
[Galaxy S I9000 Android Development] Bushido76:
It's a known bug that the ext4 app "sometimes" needs a second try... ;-)

Bushido
[Galaxy S I9000 Android Development] ocelofil:
Hi all,

I don´t know where but somewhere had been written that can be problem with semaphore app and wifi! Coz I have this problem. When I permit this app in superuser after that wifi look like that is work (ikon is showed, in setting you can see normal connecting) but the contrary is the case! So now I´ve semaphore app denied and wifi is OK! Have someone better solving?
[Galaxy S I9000 Android Development] HM.Carbide:
Quite strange. The App does nothing on it's self.

The statements it runs on startup is:

su

ls /res/scripts

ls /res/scripts/addons

ls /res/scripts/tests

ls /mnt/sdcard/SemaphoreScripts

ls /mnt/sdcard/SemaphoreScripts/tests

and reading only files in those folders with

cat /res/scripts/enable_cifs

...

That's it.

The Only thing it does, only when you change any configuration, is copying a script and running the script. That is what the app is intended for.

So su (ask for right to read the above mentioned directories and files) and ls (list files in given path) and cat (get content of file) commands should not have any effect on wifi.

Could you please try to reproduce?

Maybe you have a bad signal, i have no clue what else could it be.

Please revoke SuperUser rights in SuperUser App from the Semaphore App and try to reproduce.

And maybe some additional questions:

Which kernel version are you running?

Which app version is shown?

Which rom are you running?

Are you running any additional script changing network configuration?
[Galaxy S I9000 Android Development] darckengel:
I notice many times on some games that with conservative like you use, the battery drain was worst than with on demand (with inotia3 for example, the CPU is 90% at 800 Mhz with conservative against 90% at 400Mhz with on demand).

Let's take an example:

Your app needs 300 000 CPU cycles/sec to work => it's 75% of 400Mhz and 37.5% of 800Mhz

So with conservative governor, it's more than 70% of 400Mhz, so it will scale to the next freq: 800Mhz

With On demand governor it's less than 85% of 800Mhz so it will try 400Mhz, as 200Mhz is more than 100% of load, it will scales at 400Mhz

But you use very aggressive settings for conservative, of course it permits to scale faster but you lose the benefits of conservative governor for battery saving
[Galaxy S I9000 Android Development] pikachu01:
Conservative is only used when screen is off, so you cannot use Inotia3 as an example.

Second, ondemand doesn't scale up like what you're saying. Ondemand scales up to the maximum when load reaches the CPU load threshold of 0.8 (for example). After that scaling down will take place depending on the load of the CPU, with each sampling rate being the point that it scales down. When sleeping, the ondemand governor will jump to the highest disregarding the lower frequencies causing battery drain.

Conservative on the other hand will jump to the next highest or highest frequency when it reaches 35 (example) but scale down quickly if the CPU load is below 70 (example).

Take note that when the phone is sleeping, load will rarely be > 80 more than a second or two (for sync). It will most likely jump to a high load (when the sync connects to the internet, and then waits for data to be sent over, it'll still be at the highest frequency, until sampling rate has done enough to reduce the frequency.

Ondemand is bad in this sense that it will jump to the highest and scale down slowly till there's no load. I.e. At 100MHz, it detects sync is on and load is more than 80, scale to 1GHz, load is now 50, scale to 800MHz, load is now 60, scale to 400MHz, load is now 80, scale to 1GHz, load is now 50, scale to 800MHz etc until it is over.

Ondemand:

CPU Load. ..Frequency

5->90...... 100MHz (Sleeping)

90->50......100MHz -> 1GHz (Awake -> Do Sync)

50->60......1GHz -> 800MHz

60->80......1GHz -> 400MHz

80->50......400MHz-> 1GHz

.

.

.

Until sync is over.

In the end, you'll get (in the span of those 2 seconds of sync):

50% at 1GHz

25% at 400MHz

25% at 800MHz

Conservative will however, scale up to 200MHz when load is 30, then to 400MHz when the load is still >30, and then 800MHz when load is still >30. At the next sampling rate, it determines if the load is above 70, it'll scale down, if not it'll scale up again to 1GHz until the load is below the down threshold until the sync is over.

Conservative:

CPU Load...Frequency

5->90.......100MHz (Sleeping)

90->85......100MHz -> 200MHz (Awake > Do sync)

85->80......200MHz -> 400MHz

80->60......400MHz -> 800MHz

60->80......800MHz -> 400MHz

80->60......400MHz -> 800MHz

.

.

.

Until sync is over.

For the conservative governor, take note that the freq_step is 5 (example), hence at every sampling rate, the upscale is 5% at every sampling rate (hence the above table is not accurate), this means it actually upscale from 100MHz to 105MHz, not 200MHz. How this is possible? It jumps alternately with 95% at 100MHz and 5% at 200MHz (or something like that, math is probably wrong :P)

In the end, you'll get (in the span of those 2 seconds of sync):

49% at 400MHz

49% at 800MHz

1% at 100MHz

1% at 200MHz

Tell me. :)

Which is more battery saving? :)
[Galaxy S I9000 Android Development] darckengel:
It was just to say that conservative governor is not always more battery friendly than on demand, as many people uses it also for normal use without the screenstate scaling scripts.

Personally i also use the screenstate scripts but with 90/50 thresold. And i'm not really sure that it improves my battery life or not.

And i think your misunderstood the freq_step, it's 5% of max freq :)

With 1Ghz max freq, it means that you will need 2 samples to reach 200Mhz and not about 15 samples (imagine how it would be laguy).

PS: i didn't understood your cpu tables :p

PS2: as the load depends of your frequency (CPU cycles used/Total Cpu cycles), that you need to know is not the "load", but the charge in operations/secs.
[Galaxy S I9000 Android Development] ocelofil:
Waw...hey dude, thx for you answer!

But it´s quite strange as you wrote. Coz I am using this app for few week and everything was good. I am used on JVS Doctorz rom, it was good, After I try Dynamic III on JVS stock and everything OK. But after I flashed JVT stock, so after that start this problem!

Now I am on Ametist JVT 5.2 ROM, Semaphore JVT1.8.0 kernel and Semaphore v 0.51 app and yes I am running on additional script (universal adrenalin shots)...but I used this all before and no problem but now yes?!

But big thx for your answer
[Galaxy S I9000 Android Development] pikachu01:
Oh, misread about the freq_step. 5% of 1GHz + 100MHz is still 150MHz. Not much different than the conclusion that I've obtained.

The configuration still saves battery with CPUSpy predicted to have this:

49% at 400MHz

49% at 800MHz

1% at 100MHz

1% at 200MHz

Rather than this:

50% at 1GHz

25% at 400MHz

25% at 800MHz

So now, with the conclusion I made (which is still valid even with freq_step misread that I made), does conservative save battery when screen is off? :)

Conservative is always more battery friendly than ondemand, if and only if your freq_step is a low number like 5, and your up_threshold and down threshold is not a small number (which is similar with how ondemand works)
[Galaxy S I9000 Android Development] darckengel:
Well, i'm not agree, mainly because i saw that in real, with the example i gave you before.

As soon as the CPU reachs the stable freq to work, the way you reach that (from 1Ghz scaling down to your freq or from 100Mhz scaling up) , and how much time you needed to reach it is almost negligeable. With aggressive up/down thresolds you can have worst result in battery savings than with on demand.

I think you still misunderstood the freq_step usage and cpu load...
[Galaxy S I9000 Android Development] pikachu01:
CPU load represents how much the CPU is loaded (waiting in queue) with a numerical percentage of based on how loaded the CPU is in caches and/or pipeline.

And as I said, your example is based on when you're playing a game. I'm talking in the sense when you're syncing or the phone is awake to perform a task.

And yes, if the conservative governor is tweaked aggressively, it'll be more battery draining than ondemand, but generally if freq_step is a low number and thresholds are moderately configured, it is really more battery saving.

FYI:

Conservative governor defaults are a little bit more aggressive than what's set in screenstate_scaling (at least in IBM's Linux):

IBM:

Up: 20 (Will scale up when it detects 20 load)

Down: 80 (Will scale down only if load is 80 or below)

Zach's:

Up: 30

Down: 70

I do wonder what you perceive as an aggressive setting.

Source: http://publib.boulder.ibm.com/infoc...ic=/liaai/cpufreq/TheConservativeGovernor.htm
[Galaxy S I9000 Android Development] darckengel:
You inverted the up and down factors :)

So your settings are more aggressive than default, you will scale up more easily.

I took the example of a game because it's a long task, as most time you use a phone, you will use long tasks, sync is a short task and don't occurs often (depends on how you set it, but about maybe 1-5 sec/hour, i don't think it could be relevent in term of battery saving compared to the other tasks).

30% load to go down means that if you reach 1 Ghz, you will need to go under 300 000 cycles/sec (aka 300Mhz) used to go to 800Mhz, it's the limit of conservative governor.