yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
The busybox version is 1.16.2androidminimal.

You can't remove it. Most accurately you may remove it but it will be installed with a new version.

The 'busybox' file in /sbin is actually a script:

#!/sbin/ext/busybox sh

if /sbin/ext/busybox [ "$0" = "sh" ]; then
/sbin/ext/busybox sh "$@";
elif /sbin/ext/busybox [ "$1" = "sh" ]; then
/sbin/ext/busybox "$@";
else
if /sbin/ext/busybox [ -x /system/bin/busybox ]; then
/system/bin/busybox $0 "$@";
elif /sbin/ext/busybox [ -x /system/xbin/busybox ]; then
/system/xbin/busybox $0 "$@";
else
/sbin/ext/busybox $0 "$@";
fi;
fi;

and the /sbix/ext/busybox is a symbolic to a 'recovery' binary (I don't have the source code of it). That's why removing or installing another busybox version in /sbin you will break something.

Embedded busybox version has the run-parts command.

According to chainfire (Semaphore's initramfs is based on cfroot's one) you may install busybox in /system/xbin. But you must test that the new version you install doesn't break anything.
[Galaxy S I9000 Android Development] corgar:
i'm just asking cuz i want to remove busybox from my rom and just left the one bundled with kernel. but dunno if after all script works.

Inviato dal mio Transformer TF101G
[Galaxy S I9000 Android Development] stratosk:
They will work. Semaphore kernel also uses many init.d scripts to enable/disable functionality.
[Galaxy S I9000 Android Development] DarknessWarrior:
1.9.1s?

the latest i see is the 1.9.1m, can anyone point me to the link/changelog for that version?

btw stratosk, if its not too much work, could you post the updated versions on the first post so we dont have to dig thru 500+ pages of posts? thx for the great kernel anyway!
[Galaxy S I9000 Android Development] johnsin5393:
is there anyone use cwm to flash semaphore kernel?

i use this way to flash it everytime but never face problem so far.

i just curious why have to use odin to flash it.

can i anyone explain to me?
[Galaxy S I9000 Android Development] stratosk:
1.9.1s is a special version I built for simplicity.it's the same as 1.9.1m with a simplicity rom boot logo. The latests versions are always attached to the first post.
[Galaxy S I9000 Android Development] pikachu01:
stratosk, could it be the compiler optimizations breaking some things in post 1.8.0?
[Galaxy S I9000 Android Development] stratosk:
I didn't notice anything wrong. Do you have something in mind?
[Galaxy S I9000 Android Development] pikachu01:
Using O2 instead of O3 and dropping these flags:

-funswitch-loops -fpredictive-commoning

-fgcse-after-reload -fipa-cp-clone

-finline-functions

-ftree-vectorize

I'm not sure if it will affect speed, but it'll increase the kernel's stability by a great degree.
[Galaxy S I9000 Android Development] darckengel:
But Semaphore don't have stabilities issues ...
[Galaxy S I9000 Android Development] stratosk:
Definitely reverting back to O2 will slightly decrease speed and smoothness, will also decrease kernel size and will add 1-2 MB in available RAM. All these are tested.

But I'm asking again: did you face any problems with these settings? Did you try Semaphore and get problems?
[Galaxy S I9000 Android Development] pikachu01:
Actually no, I'm not facing any problems with Semaphore. I'm not even using Semaphore (I'm building my own kernels :P from Semaphore and Talon sources).

I'm just offering perspectives where stability issues can occur :)

I actually read the oserx thread and felt that I should help out to resolve the problems as tenacious as you are in wanting to resolve the problems :)
[Galaxy S I9000 Android Development] stratosk:
Thanks for your help and your interest. I really appreciate this.

But I think stability issues that oserx faced are caused by the fact that he customize his rom for a specific Semaphore version (removing scripts during boot for directories of initrmafs). If someone upgrade kernel version there will be problem.

I didn't have any problems in stock JVT and in 1.9.1 I had no reports (except 1 maybe) about stability issues. And the latest version is counting over 15000 downloads.
[Galaxy S I9000 Android Development] pikachu01:
Ahh, yes 1 of the issues regarding reboot right?

Yup, I compiled O3 and felt it was a tad smoother (but increased in a few hundred KBs, which is OK).

Also, when reading this:

-finline-functions shouldn't be included in the optimization.

http://lkml.indiana.edu/hypermail/linux/kernel/0005.3/0111.html

You can manually specify all these options:

http://gcc.gnu.org/onlinedocs/gcc-4.6.2/gcc/Optimize-Options.html#Optimize-Options

-funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize and -fipa-cp-clone

but exclude -finline-functions.
[Galaxy S I9000 Android Development] stratosk:
Yes, someone report a reboot. The reboot issue was on 1.9.0, with 4-5 people whit overclocking. Same people reported that this resolved.

About the first link:

This was post on 2000! After 11 years I want to believe that something had changed. :)
[Galaxy S I9000 Android Development] pikachu01:
Yeah, I noticed it was posted in 2000. I do believe that finline functions should still be disabled (given the specific usage of it).

I compiled it and I don't see a noticeable difference between O3 and O2 with -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize and -fipa-cp-clone
[Galaxy S I9000 Android Development] stratosk:
Of course you will not see any major difference with just changing one flag.

I believe the only problem with inline functions is that they produce bigger code. But the definitely will produce faster (slightly of course) code because you will have less function calls.
[Galaxy S I9000 Android Development] pl4cid:
Hey, Im using 1.9.1 with Darkyrom JVT RE and it is brilliant! :) I came from CM7 and Glitch but video and the missing instant dialer sucked, so I decided to run Darky and this great kernel. Next week I will compare battery life but it seems it will be a bit better, even its oced to 1.3 with Smartass and Sio, but lets see.. It feels that JVT is a everyday release, no bugs so far.

But what Ive noticed: If I clean Busybox in Semaphore everything is messed up and I cant use CWM anymore. But now I did a nandroid and wont touch this checkbox again :) Everything works flawlessly now.

Nice work dev!
[Galaxy S I9000 Android Development] stratosk:
Thanks for your feedback.

Did you have additional busybox versions installed? Did you try to reboot your phone after this option?
[Galaxy S I9000 Android Development] pikachu01:
Hmm, based on what was discussed 11 years back then, inline functions should still not be used in kernel because of memory issues I think.
[Galaxy S I9000 Android Development] stratosk:
Yes, but that was 11 years ago. gcc upgraded many times since then. :)

Anyway, with Linaro gcc 4.6.2 11.11, I had no problems so far.

I will have it in my mind if something comes up.
[Galaxy S I9000 Android Development] s3icc0:
Great kernel ... no doubts ...

but I am still missing the ability to modify the autobrightness table ...

can you at least say if this is possible to implement?

thanks
[Galaxy S I9000 Android Development] stratosk:
Thanks.

Of course it is possible. Everything is possible.

But I didn't find a way to do it. But it is always on my mind as a possible feature.
[Galaxy S I9000 Android Development] tiwag:
there should be implemented a proportional-integral controller instead of a table in order to control display brightness with better and smooth adaption ...
[Galaxy S I9000 Android Development] HM.Carbide:
Thanks for the report, it is the second report with this problem.

The Busybox Clean removes the following files:

rm -f /system/xbin/busybox

rm -f /system/bin/busybox

It helped a lot of people, but maybe it is a problem, if a rom has scripts referencing explicitely:

/system/xbin/busybox xxxxx

or

/system/bin/busybox xxxxx

So it is better at now to only to use this option, if there is a busybox problem.

I will add a backup of these files, to enable a restore of them.

For that it would be good to know:

- Did the phone boot, so that it is possible to restore the 2 files in case of problems?

- Did the cwm in general not work, or did Reboot into CWM not work in extended Shut Down Menu?

- What exactly does "everything is messed up" mean, what did not work?
[Galaxy S I9000 Android Development] pl4cid:
I had another version of busybox, but I think its just for Titanium Backup. When I open the app it tells me use busybox 1.18.4 from app, so i dont think semaphore app deletes it..

What messed up means is that I cant enter recovery, nothing could be mounted, no cache, system, and so on.. I think its related to busybox because of su.. But i am no dev so its just an assumption..

Futhermore I cant open RootExplorer, screen stays black at the point where it grants su permissions. ES Explorer works but i cant write in system..

Where is the androidminimal busybox stored? also in system/(x)bin? when i toggled busybox cleander and tried to apply stericson's 1.19.3 his app told me there is any other busybox stored..

Its not a big deal for me but maybe its good to be updated, if i am right semaphore using 1.19.0 from git. can i somehow change it to 1.19.3?
[Galaxy S I9000 Android Development] stratosk:
About changing busybox, please see this post:

http://xdaforums.com/showpost.php?p=19981039&postcount=5338
[Galaxy S I9000 Android Development] s3icc0:
good to hear .. .thats one of the last things i am still missing :-)

---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------

I always thought the brightness level is based on reading from light sensor ... so the table with 7 (i think 7 is a nice number from statistical pov) levels should be fine for everyone ... unfortunatelly i have no idea how this is working:p
[Galaxy S I9000 Android Development] betoNL:
Sorry for the "shot in the dark" but I am no developer and been away from sgs forums ( I just check your thread and Lirik's from time to time, since you 2 improved my sgs experience a bunch, that I even decided to keep it a little longer and postpone the purchase on another expensive gadget ;)) but since you implemented some Hardcore's tweaks in the Semaphore app (script manager) like colors, could you not add Hardcore's brightness tweaks?

And , if it's not possible, (brightness tweaks on-demand) so leave it like this, cause this issue was a drag on speedmod's thread: some complain about minmum brightness beaing to dark , others complaining bout being to bright, no way to please "greeks and troyans" if you know what I mean

Anyhow very pleased with Semaphore1.9.1BM/GalaxyRom_v12 right now, no issues, smooth, energy-efficient, no need to OC/UV and still on RFS

And what about that Galaxy Note? 5.3 inch.....tough to resist .....and its getting ics

Cheers
[Galaxy S I9000 Android Development] martinomac:
Not sure if this issue is kernel, ROM or thunderbolt related but I've just lost all of my contacts that were imported to the phone.

I can't even restore the contacts from Tibu, strange. Can anyhow recommend how to sync or export my sim contacts into Google so I don't run into this problem again. Please and thanks!
[Galaxy S I9000 Android Development] Chrisuk80:
Hi I just flashed kernal 1.9.0 and i like it very much but since flashing it when i use Go SMS it bypasses my security lock but when i use darky 4.0 it asks for my security lock

but with semophores kernal handcent asks for the lock, just Go SMS doesnt

please help

many thanks
[Galaxy S I9000 Android Development] cooldoc007:
hi.. my second post here... i had reboot a total of 3 times on 1.9.1.. on darky jvt rom.. noticed them when i m pressing the power key when the screen is off.. the screen lights up and then everything is stuck for a while and it reboots itself...never had it in 1.8.2.. again i dont oc/uv..btw was on hm carbides recommended profile..will try the default profile..
[Galaxy S I9000 Android Development] sajidmkhan:
[Firmware][2.3.6] I9000XWJVX - I9000XWJVW

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

waiting for kernel from your side.

Thanks and Regards

p.s. pls do make it fast before $omator got unbanned
[Galaxy S I9000 Android Development] stratosk:
Due to Nexus S driver and Voodoo color, IF I'll manage to make something for brightness I think it have to be different from speedmod's.

So, don't worry about this.:)

It's not kernel related.

Anyway, for syncing with Google:

1) Contacts->Menu->Accounts->Add account

2) Menu->More->Settings->Save new contacts to and check Google.

3) Menu->Import from SIM card

done.
[Galaxy S I9000 Android Development] stratosk:
Thanks for the info.

But, what will happen if $omator got unbanned? :)
[Galaxy S I9000 Android Development] darckengel:
It's a GB rom, so current Semaphore will work...
[Galaxy S I9000 Android Development] ZaneZam:
And here is the third post about that, had to start from scratch and flash rom again as i had no chance to get root reinstalled after that mess. Tried everything. I did the same and used semaphore manager to remove busybox in /system/xbin. ;-)
[Galaxy S I9000 Android Development] stratosk:
That's true. Tiny changes between initramfs. But anyway:

JVX_2.0.0 (05/12/2011) (tested only on JVT)

- updated JVX initramfs

- 340MB available ram (fixes hardware video decoding in some formats)
[Galaxy S I9000 Android Development] HM.Carbide:
@stratosk please correct me, if i am wrong.

Root should be reinstalled, if cfroot folder in /system is deleted.

But rooting files are not deleted or touched. The phone should be still rooted.

Only problem could be, that busybox script in /sbin or the symlink is missing.

I want to find out, whats going wrong.

You installed darky rom and then semaphore kernel?

Did you install busybox after that?

Did you change busybox in /sbin?
[Galaxy S I9000 Android Development] betoNL:
Somator was banned..

Why he was banned?

and + 1, what happens if gets unbanned? :D
[Galaxy S I9000 Android Development] ZaneZam:
Sorry have to share some more info i guess, i am on JVT stock and semaphore 1.9.1bm. Dont know wich devil told me to install busybox 1.19.3 but i guess i just wanted to see what happens.Then I saw it :-) anyway what happend was that my wifi stopped working (a mentioned bug in busybox, strange but apparently true) so i removed additional busybox with semaphore manager. That led to the messed situation.I tried also to remove cf-root folder as i know the install scripts only will install stuff if its not present or the name of dir changes due updates. The strange thing is that this and reflashing the kernel did not fix it. Had the same problems as mentioned, cwm mounts and root explorer didnt work anymore.
[Galaxy S I9000 Android Development] ZaneZam:
Because he was not well-behaved, and i think what will happen is a new version of stock+ :) :)
[Galaxy S I9000 Android Development] Chrisuk80:
Please can someone on Semaphores kernel and with Go SMS test the following for me

in GO SMS you can use a security lock so each time you go into your messages it askes for it, can someone please see if this works for you

if one of you will be so kind then you need to go into GO SMS press the back button and go back in because the 1st time it may ask for the code but then it seems to stay active, hence not asking for it again

it doesnt work for me on this kernel but it does if i use darky 4.0 but i prefer this kernel MUCH MUCH more so i need to know if its the kernel or just my phone!!

handcent security lock works fine!!

many thanks!!
[Galaxy S I9000 Android Development] darckengel:
Just tested and It works
[Galaxy S I9000 Android Development] stam91:
I've copied enable_netfilter script from /res/scripts to /system/etc/init.d/ and set permissions rwxr-xr-x.

But the Droidwall 1.5.1 still can't be enabled -

Error applying iptables rules. Exit code: 1

iptables v1.4.10

iptables: No chain/target/match by that name.

Any suggestions, please?
[Galaxy S I9000 Android Development] nozerogravity:
Hi again stratosk,

Any chance on updating kernel 1.2.x for JVP with Voodoo sound v10 module?
[Galaxy S I9000 Android Development] stratosk:
No, it includes speedmod color fix.
[Galaxy S I9000 Android Development] stratosk:
Sorry, for asking this... but did you reboot your phone after copy?

If yes, what is your configuration on Droidwall?
[Galaxy S I9000 Android Development] stratosk:
Hi dj_deez,

I'm sorry but as I said in previous posts it's very difficult for me to maintain different versions.
[Galaxy S I9000 Android Development] nozerogravity:
Not a problem :) Thx again for best kernel and im looking forward for updates!
[Galaxy S I9000 Android Development] stam91:
That's ok) Yes, I rebooted many times, wiped etc.

I've enabled log in Droidwall and received this message: FIX IT! getprotobyname() bionic/libc/bionic/stubs.c:378

Then I've typed in terminal "iptables -t nat -L -n -v" and got this one:

iptables v1.4.7: can't initialize iptables table `nat': Table does not exist (d)

Perhaps iptables or your kernel needs to be upgraded.

Sadly, this problem exists only on your Semaphore 1.3.0, not any other kernel or your 1.2.2. But I don't want to use any other kernel because of the Semaphore's amazing speed and stability. Thanx for replying, Stratosk, and what should I do next? Wait for kernel update? ;)
[Galaxy S I9000 Android Development] :
i dont want to shout too loud, but could be "Connection tracking" in Kernel .config.

isnt there a mod called "iptables_nat"?
[Galaxy S I9000 Android Development] stam91:
Seems like you're on the right track) There were some words about implementing iptables NAT in kernels:

http://xdaforums.com/showthread.php?t=951981&page=12

Unfortunately, I didn't find any mods. Seems like it's a kernel gap needs to be solved. But I wonder why only I have such problem... or not only? (using Juwe's 5.1 JVQ ROM)
[Galaxy S I9000 Android Development] asicman:
I noticed that my accelerometer doesn't work with 1.2.2 for the game shakyTower. It works outside of the game however. Can anyone confirm? This worked ok with a different kernel.
[Galaxy S I9000 Android Development] pikachu01:
I'm having this issue with Talon kernel 0.3.1 too. Not sure what's the root cause for it.
[Galaxy S I9000 Android Development] ajazz:
hi

this is good kernel but i'm facing one problem

tethering is not working with your kernel it works with dark core.
[Galaxy S I9000 Android Development] Rebel2k:
What could I provide to you for us to try to understand why BT isn't enabling correctly?
[Galaxy S I9000 Android Development] pikachu01:
When you flashed this kernel, did you wipe the dalvik cache and cache before using it?
[Galaxy S I9000 Android Development] Rebel2k:
Yes I did, wiped both. Still the same issue. And if I stop BT and wifi and restart, then I can activate BT but only before wifi. Then BT and wifi seem to be working but after a few hours wifi isn't working because it is loosing DNS as I was saying in one of my previous post.
[Galaxy S I9000 Android Development] darckengel:
You have to copy the enable_netfilter script in the init.d like it's said in the first script.
[Galaxy S I9000 Android Development] yoshi57:
Hello,

I'm using semaphore with the GingerReal 7.1 base JVQ

I saw a lot the problem of working and non working BT so here is my experience:

On an fresh install of GR7.1 it was working ok. (time loading of about 1-2 sec)

(1day after)

Today i wanted to use BT again, but impossible to turn on. Stay semi-green (warmin up) for like a minute and goes back to off.

The only noticeable thing i've done between working and non working states is playing around with OC/UV.

As i've not set OC/UV at boot yet. I've rebooted my SGS. And voilà BT working !

So with Semaphore kernel BT is not compatible with OC/UV ?! :eek:

Hope it can help.
[Galaxy S I9000 Android Development] sahidmiah:
my friend i cant seem to save the setting .can you please give me some clear step by step instruction please i am using pimp my cpu.
[Galaxy S I9000 Android Development] sahidmiah:
mate it did not work for me on gingerreal 7.1 JVQ so i am using JVP and its working perfect.everything works .BT BLN tehering .because Jvq still at beta stage so i will wait when its properly stable .mind you there's not lots of diff between them..if you do use jvp then make sure you use 7.1 over a stock jvp rom
[Galaxy S I9000 Android Development] JB-007:
Call over BT issue

Hi all,

I'm on Juwe5.1 and Semaphore JVQ@1.2Ghz.

I have an issue with BT. I'm using BT in my car and noticed when I try to call someone over BT car, I get phone application FC and have to reboot my SGS. The workaround I found is to make a call directly from the phone.

Does somebody has the same issue?
[Galaxy S I9000 Android Development] HM.Carbide:
Thats really strange.

If you deleted cfroot folder, and flashed kernel, my idea of calling busybox installation script of semaphore kernel won't help.

Guess, if i want to make a working script, i have to install busybox :( , and try to corrupt my phone.

Thanks for the information. This is a starting point to investigate.
[Galaxy S I9000 Android Development] ZaneZam:
From busybox pro changelog 5.8:

Recent changes:

Found a major bug that was causing problems on many peoples installation and removal of BusyBox, this bug has been fixed

Maybe a pre 5.8 version is the problem not your removal script

and the failure starts with installation!? ;)

I think i had version 5.7 installed. Cant remember exactly, too many updates from Stericson. :I

Dont be angry with me, but i will NOT test this new version as i dont have time to recover my phone again atm. :) :)
[Galaxy S I9000 Android Development] ZaneZam:
So the little devil on my sholder told me to do it again and now it worked!! :-) I can confirm with newest version of busybox from stericson (at least with the pro version 5.9) after using semaphore manager to remove additional busybox 1.19.3 from /system/xbin i am back on fully functional busybox from semaphore!
[Galaxy S I9000 Android Development] EseLoKo:
Tested JVX version in Stock JVS.

Everything seems working perfect.
[Galaxy S I9000 Android Development] pikachu01:
You have to restore from Contacts Storage and reboot to see the changes. First wipe the data from Contacts Storage, then restore it. Then reboot.

Probably ThunderBolt! caused it. It's recoverable as long as you do your regular backups :)
[Galaxy S I9000 Android Development] martinomac:
Thanks for the tip. I decided to export to gmail to avoid future catastrophes.
[Galaxy S I9000 Android Development] Mr Majestyk:
I've returned to semaphore after a few months on GalaxianEE. Galaxian is a nice kernel overall, very stable and good battery, but I was getting lagging in some games. I'm using semaphore 1.9.1 and overall it's faster IMO, and no more lagging.

Great work to everyone involved
[Galaxy S I9000 Android Development] burakgon:
Wow thank you stratosk. Tested on JVX and no problem. That's great!
[Galaxy S I9000 Android Development] HM.Carbide:
Big thanks for testing this.
[Galaxy S I9000 Android Development] Mdrfkr:
Thans for sharing. The kernel works perfectly.
[Galaxy S I9000 Android Development] pitagorasz:
Hi!

Anyone tested this kernel on JVQ ?

Thank's for your work stratosk.
[Galaxy S I9000 Android Development] GreenSGS:
This kernel is comptible with all gingerbread ROMs, as read in this thread.
[Galaxy S I9000 Android Development] Proelio:
Is there really a significant improvement in Bigmem version with 13MB extra RAM? I don't know if it's worth breaking 720p recording for just 13MB RAM...
[Galaxy S I9000 Android Development] pitagorasz:
Thank you.
[Galaxy S I9000 Android Development] betoNL:
So, my friend, how did you solve your problems?

And by the way, smartphones are not a waste of time....but every addiction is ;).

Think bout that :cool:
[Galaxy S I9000 Android Development] voodoofox:
Really great kernel, if not the best kernel for galaxy s.

Phone is very responsive and does not lags after couple of days of usage.

Excellent work!

I have one question thou. And I have seen it was mentioned before.

Is there any way to disable any color modifications on this kernel?

I tried seeting it to manual and setting voodoo profile on stock but colors are not the same as on stock.

Thanks any way for your work!

CHeers