yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] burakgon:
Hi brother. You can't see a message after wipe battery stats. But its ok. Same on all kernels.
[Galaxy S I9000 Android Development] sathkartha:
can this be used on my 2.3.3 GB viz. DDJV9 without any negative impact arising out of non-compatibility with 2.3.5?

Great work and thanks in anticipation of a line in advice.
[Galaxy S I9000 Android Development] maopaopao:
waiting for the 1.9.0 bm version

---------- Post added at 06:44 AM ---------- Previous post was at 06:30 AM ----------

Is this kernel worked only for odexed rom? I am using a customer Deodexed rom Galaxy rom V11 by lirik0 and found my rom was laggy .
[Galaxy S I9000 Android Development] pikachu01:
It works for deodexed ROMs too. Have you tried ThunderBolt! to see if it can improve your phone's performance?
[Galaxy S I9000 Android Development] maopaopao:
thanks, do you have the link for thunderbolt and also how to set the scripts.
[Galaxy S I9000 Android Development] pikachu01:
Everything you need to know is in here:

http://xdaforums.com/showthread.php?t=1296927

:)

Let me know if you have specific parts you need help in. :)
[Galaxy S I9000 Android Development] pdppdp:
http://xdaforums.com/showthread.php?t=1296927

You'll find the instructions in op.
[Galaxy S I9000 Android Development] demonstone:
The only kernel with a real development and working like a charm for our sgs atm.

Thank you very much stratosk.

Escrito desde mi Galaxy S
[Galaxy S I9000 Android Development] maopaopao:
What is the different between thunderbolt and the semaphore kernel setting? Can I use both?
[Galaxy S I9000 Android Development] jna9000:
When upgrading from 1.82, cwm and superuser are kept. Is there any issue still ising them, or should I delete them?
[Galaxy S I9000 Android Development] pikachu01:
Nope, use either one. Netfilter, OC/UV, Voodoo Color can still be used though. Only things like Kernel scheduler/VM Dirtyness/LMK etc will clash with ThunderBolt!.

ThunderBolt! tweaks the same things (with different settings) and does more than Semaphore's tweaks.
[Galaxy S I9000 Android Development] stratosk:
No, you may continue use them.
[Galaxy S I9000 Android Development] stratosk:
You should not face any problem
[Galaxy S I9000 Android Development] darckengel:
Nice,

10 000 sampling rate makes it very responsive :)

I'm waiting too for the big mem version.

For the DVFS, yes the tests i made few months ago showed that the battery usage difference was few, but it was using different compilation option.

I'm almost sure that samsung introduce this DVFS to prevent music stuttering.

If i have some time i will make some tests on battery usage with or without dvfs set on.

Just to know what were the other altered DVFS?
[Galaxy S I9000 Android Development] stratosk:
Now, DVFS work as stock (except for the small change in music player).

The others are for USB, MFC (video driver) and there is one for bluetooth but I'm not sure if it's used in our platform.
[Galaxy S I9000 Android Development] burakgon:
I will wait to 1.9 bigmem for release my new rom.
[Galaxy S I9000 Android Development] Fenvarien:
The final 1.9.0 Semaphore is really impressive, smooth and super battery friendly! Thanks Stratosk for another great release :-)
[Galaxy S I9000 Android Development] silvergold:
Thank you for this great kernel!
[Galaxy S I9000 Android Development] keuda:
Thanks a ton, breathless job!!!
[Galaxy S I9000 Android Development] andip71:
+1 on big mem.

I would directly flash it as soon as it is available.

But 1.9.0 standard working brilliant on my side too since this morning, same as with the beta before.

No issues, no glitches, just rock solid. Great work, keep it up.

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

Hi,

many thanks again for the link to the tweaks.

I had a look at them and by taking over the mechanics I was finally able to reach exactly what I want :)

Basically I created a CWM flashable now that does:

- Remove journaling from system and cache

- Set all 4 partitions from ordered to writeback journaling mode (ok, useless for cache and system, but anyway)

- All partitions mounted with barrier=0

- Commit time for data and dbdata is set to 20 seconds

Now I am happy :-) :D:D:D

If anyone is interested in the tweak, I can upload it.

Cheers

Andi
[Galaxy S I9000 Android Development] manjee:
I am interested :)

With a few words to explain how to use it, it would be awesome !

Thank you.
[Galaxy S I9000 Android Development] DarkSorcerer:
stratosk,

Thank you very much. Really. What a hell of a kernel we have here. :)
[Galaxy S I9000 Android Development] mialwe:
Ouch......
[Galaxy S I9000 Android Development] andip71:
*** Download link removed as it led to some sporadic file system corruptions with Semaphore kernels 2.5 onwards ***

Hi,

here we go.

What it does:

* Remove journaling from /system and /cache

* Remount all partitions with barriers=0

* I had to remove the commit time as this was leading to unstability :-(

* For safety reasons I also removed the writeback journaling on /data and /dbdata

Installation is easy, it is the normal CWM route:

- Download the zip file from this link

- Put the file somewhere on your phone's sd card

- Boot into CWM (clockworkmod) recovery

- Flash the file from there

- Now the journaling is removed + the mount options for writeback are applied automatically + a remount script is placed into your init.d folder that does the commit thing

- Reboot and enjoy

Please note as always:

Flash on your own risk !!! I will not take any responsibility. As the script does quite "heavy" modifications to your file systems there is no guarantee you will not end up in a brick. For your own safety do a CWM backup before flashing so you can at least in worst case flash the firmware again and restore the backup.

For me it worked well many times during my trials.

BR

Andi
[Galaxy S I9000 Android Development] elhennig:
Your changes will improve the performance. data=writeback and noatime as mount options do pretty good.

However, users should be aware that data=writeback might cause loss of recent changes in metadata in case of a crash. There won't be filesystem corruption however, so it is rather save to use.

nobh option does not improve system performance to much. As well as barrier=0, which might cause filesystem corruption unless your using battery buffered write cache.

Your settings are well usable for /system (which is ro by default) /cache (which does not contain valuable data) but I wouldn't use them with /data and /dbdata.
[Galaxy S I9000 Android Development] andip71:
Hi Elhennig,

thanks for your comments, I fully agree. It is an agressive setting and people should know they take a certain risk. Trade off between performance and safety. Living a bit on the edge :)

People that periodically do CWM or Titanium backups (like I do) should however not be too afraid. As data and dbdata still use metadata journaling, data loss is possible under special circumstances but not too likely. Time will show.

Thanks

Andi
[Galaxy S I9000 Android Development] elhennig:
"Not too likely" is what they said in the nuclear power plants in Japan, didn't they? :eek:

It might happen and people - especially those who are not too deep into linux filesystems - should be informed. That was the intention of my post.
[Galaxy S I9000 Android Development] pikachu01:
Disabling barriers is still acceptable and within means of recovering through journaling. Data corruption could still happen in case of power loss.

Journaling on the other hand should be tuned just enough so that metadata can be replayed if power loss occurs in the middle of a transaction.

Hence, for /data and /dbdata, data=ordered is preferred as writeback data replayability is slightly at risk with stale data being replayed as well causing some form of logical corruption to your data.

Oh, and nobh mount option is deprecated in 2.6.35 if I'm not mistaken.
[Galaxy S I9000 Android Development] burakgon:
Bigmembigmembigmem when is bigmem brother. Thank you much. I wait your release for release my new rom.
[Galaxy S I9000 Android Development] stratosk:
I will try today my friend.

I took 3 days off from my job to work on a project. Guess what: I didn't write a line of code for this project. I spent all of my time on Semaphore. OK, I admit that I don't regret it, I like most Semaphore project. :)

Anyway, I will try tonight to do this. And, thanks for including Semaphore on your rom.
[Galaxy S I9000 Android Development] AGiovanni:
Hi friends, can I use kernel flasher to install this kernel?

@Stratosk: your kernel is really great! Thanks.
[Galaxy S I9000 Android Development] stratosk:
Yes, you can use it.
[Galaxy S I9000 Android Development] darckengel:
Cool down :D

He has a life outside xda too!
[Galaxy S I9000 Android Development] burakgon:
You're so great stratosk. A small or big donation can't take place of a small thank for you. And thank you for give us a chance to make best roms which include semaphore kernel!

Sorry for my english.
[Galaxy S I9000 Android Development] stratosk:
I'm not great at all.

Thanks goes to all of you, for your support and to all other kernel devs for their great work. I just hope that you like this kernel.
[Galaxy S I9000 Android Development] bhu1:
you and chainfire are some of the best kernel devs around at xda.

Thank you for awesomeness v1.9.0 ;)
[Galaxy S I9000 Android Development] elhennig:
Please don't forget supercurio and hardcore ;)

But of course currently Semaphore is the kernel of choice
[Galaxy S I9000 Android Development] bhu1:
I clearly said 'some of the best' . ;)
[Galaxy S I9000 Android Development] stratosk:
We should not forget:

Supercurio, Chainfire (what can I say about them!)

Existz (he helped me so much, every time I ask him something is there to help - pioneer)

Hardcore (just great, he is always helpful)

Mialwe (He is so good dev! He really works hard)

and many others...

But, I insist the real power is the community. All of you do the real work behind these devs by testing, pushing them for something new, encourage them.
[Galaxy S I9000 Android Development] bhu1:
will use this in doctor from v 10.
[Galaxy S I9000 Android Development] malcho:
Semaphore is really unleashed the real power.

Just want to say hi,i'm on little journey with cm7.Since i don't need to test new semaphore(it can't fail) i'm playing with cm7.

Many regards stratosk

P.S.See you on cyanogen 9!
[Galaxy S I9000 Android Development] stratosk:
Talking about community. What can I say about you my friend!

I would have stopped this project about 2 months ago. You made me change my mind and continue...
[Galaxy S I9000 Android Development] stratosk:
Bigmem version 1.9.0bm

- 353 MB available RAM (it breaks 720 video recording)
[Galaxy S I9000 Android Development] qtekker:
I want to install CWM, but it seems that there is no cwm apk to install. CWM app is normally included within cf-root and semaphore kernel. So what now???

I use CWM app to make backups and reboot into recovery of download.
[Galaxy S I9000 Android Development] sbnaul:
............
[Galaxy S I9000 Android Development] burakgon:
The rom is ready. And

The mysterious sacred stone.... Semaphore Kernel 1.9.0bm. Lighting the city.
[Galaxy S I9000 Android Development] betoNL:
Yum......:)
[Galaxy S I9000 Android Development] darckengel:
Install Semaphore 1.8.0

Go to /system/app

Copy CwmManager present to your SD card

You have now CWM app that you can restore to /system/app when you reflash a new rom.
[Galaxy S I9000 Android Development] qtekker:
Thanks darckengel, I'll try!

Edit: Back to 1.8.2, saved cwmmanager.apk, flashed 1.9.0 and then I found out that the apk was 0 bytes...

But now I knew the name of the apk, so google helped me to find and download it.

cwm app restored succesful!
[Galaxy S I9000 Android Development] betoNL:
Oops sorry didnt see your post....

I am not hanging around here as often as I would like...

If you update to another version , it could be that the older settings/scripts wont fit as good as they did on the prior version, for instance:

If you were using a BIGMEM version and agressive LMK settings, those settings could cause problems on a kernel with less ram.

I know that for a fact, since I was the one always begging for a public BIGMEM Gingerbread kernel for the i9000

I tried Tapatalk app and had no probs ( and un-installed it as soon as I could cause I dont like it)

Well, that was just an example....

Btw, this kernel and the Rom I using are so good right now, that I am not in a hurry anymore to purchase a GNote or a GNexus or any other abusevely priced phone :D:D

« »
[Galaxy S I9000 Android Development] GreenSGS:
Thanks for your reply betoNL, seems like I the only one troubling with OC 1.2. I have tried many options but had random reboot and freeze.Most annoying one was without OC and SIO,phone rebooting during an important call.

Now I start deleting some apps I suspect related to SIP. Lets see.

One request to people using OC or SIO, please share your kernel configuration.
[Galaxy S I9000 Android Development] haloimplant:
D'oh the bigmem comes out within an hour of me getting impatient and flashing the regular version. :rolleyes: Oh well thanks a bundle for everything!
[Galaxy S I9000 Android Development] borjaag:
Wifi Error for me... =(
[Galaxy S I9000 Android Development] Comporellon:
@stratosk: Thank you for the kernel and for your work. I'm on Darky but with semaphore. It's perfect!
[Galaxy S I9000 Android Development] qtekker:
Thanks for your effort!
[Galaxy S I9000 Android Development] a-id:
I have the same problem and I have tried many options too... Now I don't know what to do else...
[Galaxy S I9000 Android Development] Fenvarien:
Not every phone's hardware can handle OCing to 1.2. Also the hardware can degrade over the time if a lot OC/OV is done. Devices that once were able to go for high frequencies can become unstable after some time. That's the risk of OCing everybody should be aware of.
[Galaxy S I9000 Android Development] shanky77:
Just want to say a huge thanks for a great kernel!

Having updated my phone to 2.3.5 xxjvt via kies I was becoming increasingly frustrated with the lag/FC reboot issues so decided to do something about it!

As a relative noob to flashing etc etc I wanted something fairly straight forward and more importantly something that actually worked!

I did a bit of research and kept coming to semaphore kernel so went for it - converted to ext-4, applied phone FC fix and all has been great ever since. I did have one bootloop issue but that was me messing with overclocking and phone didn't like it, luckily I'd made a backup in CWM earlier in the day. (phew)

For any others following this thread as I did for a few days before having the courage to flash I'd say do it! You wont regret it!!

I do have a question though (probably a stupid one) - I'd like to update to the latest version 1.9.0, do I need to revert back to RFS or can I flash the update while on ext-4??

Thanks again Statosk please keep up the awesome work
[Galaxy S I9000 Android Development] stratosk:
You may flash it without converting back to RFS.
[Galaxy S I9000 Android Development] betoNL:
Some phones are tougher to overclock than others...mine for instance is one of those...

The only way I can overclock my phone is with a kernel with 6 frequencies.

Then I use Tegrak overclock ultimate to oc , undervolt and OVERvolt in order to keep it stable.

With the latest Semaphore kernel my phone is smooth and energy efficient enough so no need to OC/UV

But if you think you still need to fry your phone, just go back to the version that allows more frying ....

Or ask Stratosk for a version with 6 frequencies....than I will have a OC/UV/OV guide for a tough to overclock sgs , ready to use and tested....
[Galaxy S I9000 Android Development] shanky77:
Thanks for the fast reply!

Updating shortly :)
[Galaxy S I9000 Android Development] darckengel:
I tend to be agree with this,

Actually, you don't really need to OC the SGS, it works pretty well without OC for most of uses. I think you can even UC to 800Mhz it if you don't play heavy games, you loose a little of reactivity but it's still usable. Semaphore is very efficient and the phone is very responsive even at normal speed.
[Galaxy S I9000 Android Development] burakgon:
can someone post the latest semaphore app here? I deleted it wrongly. lol
[Galaxy S I9000 Android Development] O-T:
That should not be needed, because it's included in 1.9.0 kernel.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] darckengel:
Just reflash Semaphore.
[Galaxy S I9000 Android Development] andip71:
Hm, I think this is not enough. Think before flashing the folder /cfroot needs to be deleted to trigger a new copy process of the app to /system/app.

Right?

I can be wrong though...

Thanks

Andi
[Galaxy S I9000 Android Development] stratosk:
Yes, you are right. Flashing is not needed. Just delete the directory cfroot located in /system.

OR

Download the app from HM.Carbide's thread http://xdaforums.com/showthread.php?t=1277627
[Galaxy S I9000 Android Development] darckengel:
I'm not sure because when you flash semaphore it updates the app even if you had it before without having to do anything, so it should install it, but i didn't try.
[Galaxy S I9000 Android Development] elhennig:
I just ran Antutu Benchmark and scored the best result so far with my SGS: 2964

Settings used:

1000MhHz, Ondemand, No-op, CF Kernel Tweak, VM Dirtyness, LowMem 64MB SD-Card read-ahead 3072k
[Galaxy S I9000 Android Development] stratosk:
Kernel uses a flag file (in /system/cfroot directory) to check the first installation.

If the file exists then it skips the installation process.

So, deleting cfroot directory will trigger the installation process again.
[Galaxy S I9000 Android Development] SilverSonic:
Mobile AP Error

Hi just flashed Semaphore JVT_1.9.0 kernel together with the stock 2.3.5 JVT.

Now i recognized that the mobile AP function shows me "error" when i enable it. Connection via WLAN works but no internet access.

Is there someone with the same issue and has a fix for it?

Greetz Silversonic
[Galaxy S I9000 Android Development] senotrius:
@ stratosk ,please make a kernel based on xfjva kernel..I know we can use jvt kernel for jva rom..but the jvt sem kernel has issues regarding black colour(reverting back to cf kernel immediately fixes the problem).it is also much less brighter..speedmod fixes it to a limit. but please releasw one based on jva
[Galaxy S I9000 Android Development] danieldmm:
Enable netfilter option in semaphore apk.

Cheers

Escrito pelo meu querido S using tapatalk...
[Galaxy S I9000 Android Development] darckengel:
The samsung sources which semaphore is based on are the same for a while, only the initramfs is updated, i don't think your problem is related to the version.

You can't make a kernel really based on XFJVA cause we don't have the kernel sources code.

The fix is to read the first post correctly ...

Stratosk, maybe you should write in bold caracters that they have to set up netfilter option in semaphore app to enable tethering and firewall, people don't read the first post because they found it too long and always asks the same question ...
[Galaxy S I9000 Android Development] pikachu01:
I think your problem is related to Voodoo Color rather than JVT/JVA. They are almost similar with the only differences related to initramfs modules e.g. RFS.
[Galaxy S I9000 Android Development] SilverSonic:
Yor are my hero ;-) Thanks, works now!

Cheers
[Galaxy S I9000 Android Development] midikarma:
really nice update man! using it like awesome :D :D thx a lot!
[Galaxy S I9000 Android Development] burakgon:
- bootloop detection (clears init.d directory, if the phone does not complete 2 minutes of normal operation)

Hi brother this causes millions of issues for me. :(

When I reboot in 1 min it corrupts my init.d and I have to look my init.d after all reboot and now stucked on boot because of this trigger.
[Galaxy S I9000 Android Development] darckengel:
I doubt that you get stuck just because it empties your init.d folder.

Well, just try to wait a little before rebooting, wait for 2mns is not so long ...
[Galaxy S I9000 Android Development] MasterJam882:
I also don't like this feature that much, because u have to restart ur phone often in realtime usage.

In my case I made a battery reset and waited till phone went off. And as u can read in many guides in here I started my phone so often till it wasn't possible to start it up so battery was completely empty.

But this caused that init.d was emptied. Many users do that!

Or how often do we reset via CWM for resetting something that doesn't take more than 2 mins.

I think many ppl will face the problem that they either:

1. ...know why something isn't working anymore and will be angry to set up their scripts everytime

OR

2. ... will wonder why for example tethering is not working anymore, beacuse they don't consider that it could be due to a reset they made, don't know what to do and will ask in here very often for help

Just my 2 cents

greetz guys
[Galaxy S I9000 Android Development] darckengel:
Maybe with a shorter timer it would create less problems (30s or 1mn)
[Galaxy S I9000 Android Development] wassk:
don't know why,but it's very lagy for me.i flashed it over 1.8.2 with kernel flasher.would it be better to flash it with odin?
[Galaxy S I9000 Android Development] darckengel:
Little question about the sensitivy scripts.

Why to set sensitivity, there are many lines which update the same parameter?
[Galaxy S I9000 Android Development] Bonvaz:
if I open voltage control I have only ondemand and conservative for governor................it's normal?
[Galaxy S I9000 Android Development] darckengel:
Did you read the first post and used the semaphore app?
[Galaxy S I9000 Android Development] Bonvaz:
n order to load various modules of the kernel and enable or disable features use HM.Carbide's Semaphore Script Manager application. It automatically copies and runs the respective scripts from /res/scripts to /system/etc/init.d directory. The scripts:

.....here...but I don't really understand with I have to do:(
[Galaxy S I9000 Android Development] darckengel:
By default, only ondemand is available, if you want other governor, you have to load the proper module with the semaphore app.
[Galaxy S I9000 Android Development] jna9000:
I didn't felt this - in contrast, my battery file seems to have dropped. What are your settings, please so I can try these?
[Galaxy S I9000 Android Development] gsw5700:
Try smartassv2 and sio, don't use

Kernel or io tweaks, clear cache and dalvik cache, standard 1 ghz is great

Sent using TCP/IP
[Galaxy S I9000 Android Development] Bonvaz:
guys with smartassv2 what scheduler is better for best battery performance?and what is save battery governor?
[Galaxy S I9000 Android Development] gsw5700:
I find sio works best with smartass, responsive and great battery, guessing that battery save is conservative governor (way too slow for my liking

Sent using TCP/IP
[Galaxy S I9000 Android Development] burakgon:
Yes 30 s is enough really.
[Galaxy S I9000 Android Development] stratosk:
I will enable (or disable) it optionally in next version.

And maybe I can reduce the time. But I wanted to be sure that device will run long enough to detect a reboot due to improper scripts.
[Galaxy S I9000 Android Development] HM.Carbide:
You wanted also to ensure boot time, if dalvik cache is cleared.

If bootloop detection is shorter, and the phone needs long to boot due to cleared dalvik cache, i would have to wait for 2 reboots, but then the phone should be up in 30/40 seconds.

Btw.

Emtying the battery completely can damage it! li batteries should not be overloaded or underloaded too much. Battery statistik is mainly for protecting the battery.
[Galaxy S I9000 Android Development] stratosk:
Yes, I wanted that also.

Anyway I think i can easily enable/disable this feature through a script.
[Galaxy S I9000 Android Development] stratosk:
@GreenSGS, @all who reported problems with OC

This is a test version with latency back to 40000
[Galaxy S I9000 Android Development] jocke_lulle:
Thanks.

Downloaded and flashed:)