yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] darckengel:
Yes, you have to add it manually.

As you can download it from market, there is no need to include it by default.

---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------

All GB stock based roms are compatible.
[Galaxy S I9000 Android Development] haloimplant:
There's one exception that I know of: Bell Canada's KG3 stock rom. Something is weird with it, other kernels don't work just bootloop (with its bootloaders even the recovery mode button combo is different).
[Galaxy S I9000 Android Development] stevedb:
Battery fully charged alert + vibration

Since I flashed 2.3.5 JVT and added Semaphore 1.9.0, I no longer get an alert or vibration when the battery is fully charged - the 'notification' ringtone used to play and the phone vibrated when the battery reached 100% when I had Gingerbread 2.3.3.

Does anyone know if this function was taken out by Samsung in version 2.3.5, or has it been disabled in Semaphore 1.9.0?

Many thanks.
[Galaxy S I9000 Android Development] stratosk:
Semaphore only disable boot sound. I think it's JVT 'feature'.

Please correct me if I'm wrong.
[Galaxy S I9000 Android Development] paroulis:
Strato yparxei tropos na epanaferoyme ton boot sound?Me tin epilogi toy semaphore manager den ginete tipota.
[Galaxy S I9000 Android Development] stratosk:
Semaphore script manager restores boot sounds if it finds them in /data/local where previously backed up.

I just realized that the second time Semaphore kernel is installed the boot sounds in /data/local are removed. I will fix this in next version.
[Galaxy S I9000 Android Development] ryuzaki_eru:
Is 2.1.1 working with 2.3.5 ROM?
[Galaxy S I9000 Android Development] dherre65:
Yes. 10char
[Galaxy S I9000 Android Development] burner07:
after i do a lag fix my wi fi stops working... it just says obtaining ip address but dosen`t work

JVZ and 2.1.1 and the semaphore app stops working dosen`t detect the kernel
[Galaxy S I9000 Android Development] zsandras:
Hi guys, I flashed yesterday evening JVZ_2.1.1 (Settings: 1200 MHz with ondimand governor) over JVT_1.9.2 and today morning it has a very slow woke up. It was same slow up as it would be on 200-300GHz.

There was no other rom isue, because I went back to the 1.9.1 and it was again all ok.

As far as I know between the two kernels isn't basic function difference and all are OK on JVT roms, so I dont understand what happened. Had somebody same wake up problems on Darkys JVT RE BASE ROM?

Thx. &ew
[Galaxy S I9000 Android Development] paroulis:
Thanks Strato :)
[Galaxy S I9000 Android Development] stratosk:
Can you check with ext4 app if all of your file systems converted to ext4. I don't think it's related with the conversion.

Did you install Superuser application?

Otherwise I would suggest a fresh rom installation.

I'm sorry but I don't know what is the problem. Did the phone recover after this lag without reboot?
[Galaxy S I9000 Android Development] cooldoc007:
i had this problem with v1.9.1... having soft reboots with darky jvt re... never had with 1.8.2.. and not with darkcore...had applied ctr off/on animation in darkys after 1.9.1.. could dat be the reason(dats the only thing i changed between 1.8.2 and 1.9.1).. however darkcore worked fine even with dat effect:confused:...
[Galaxy S I9000 Android Development] Rosk1:
the 2.1.1bm is great but i must say something (i had the same problem in 1.9.0 too)-

when i lock the screen there is a green screen for a 0.5 second and then the screen is lock.
[Galaxy S I9000 Android Development] GreenSGS:
Agreed. its there.May be something with voodoo color, usual suspect.
[Galaxy S I9000 Android Development] Rebel2k:
For sure that's the culprit! ;) Raise your gamma level in the Voodoo Control App and that should work.

Envoyé depuis mon GT-I9000 utilisant Tapatalk
[Galaxy S I9000 Android Development] Tkbf:
Just flashed JVZ from JVS, re-partition was checked in Odin, JVZ installed successfully. CF-root and Ext4 tool were installed and converted to Ext4. Then I restore all data using CWM/Advance/Restore Data.

When I want to use CWM/Flash Kernel to flash Semaphore, after assigning the tar file of 2.1.1bm to CWM, it was FCed. Finally I flashed 2.1.1bm with Odin, everything seems beautiful.

But now in CWM, if I want to flash zip, flash kernel, or anything that CWM need to reboot into Recovery, SGS will enter Recovery but just STOP at the Main Menu instead of processing the job which is supposed to do automatically. Where is my problem, guys? Thanks in advance.
[Galaxy S I9000 Android Development] zsandras:
No mate, there was no problems with installation or so, it was perfect. All programs have run perfect too, benchmark tested ok, and than I put down the in the evening as usually I put down the phone.

In the morning I opened it and I saw that it was very, very slow. I mean it remained toward in deep sleep.

I made a reset but there was nothing changed.

Putting back the previous kernel all was again perfect.

That is my problem mate on Darkys JVT Base ROM with the Semaphore JVZ_2.1.1 and I wanted only to know is it mine mistake or there are same problems on another devices.
[Galaxy S I9000 Android Development] darckengel:
If your phone runs very slow, it must be because some app use all the ressources, chech with an app like antutu cpu master if your cpu is always at 100% and with android system info what app is running at 100%, it happens some times after you flash a kernel and you not wipe the dalvik cache
[Galaxy S I9000 Android Development] tendan:
-------- BLN on SMS --------

Hello @stratosk

My rom is jvz odex (stock).

Can I flash this one JVT_odex_STOCK+_blnfix.zip or I need a new one for jvz?

Thanks :)
[Galaxy S I9000 Android Development] stratosk:
For FCs before you flashed Semaphore I don't know. Did you try to clean dalvik? (You restored your data from 2.3.5 to 2.3.6).

Are you able to flash a zip file from recovery menu?

@tendan

This patch replaces the services.odex file. I don't know if it's compatible with JVZ.

I don't suggest you to try it unless you make a full backup.
[Galaxy S I9000 Android Development] darckengel:
You will need a new one.

The phone will bootloop if you try this.
[Galaxy S I9000 Android Development] dany__:
Hi,

I had the same problem and according to my knowledge, it's caused by the lockscreens ( Four tabs, Android AOSP and R2D2).

Since I use other lockscreen (SGS2 unlock for example), I never had that issue.

Try it, perhaps that it's the same issue for you too.
[Galaxy S I9000 Android Development] Tkbf:
I did clean dalvik right after I flashed to JVZ.

My procedures are: I flashed JVZ, clean catch & dalvik, do factory data reset , then flash CF-root, install ext4 Manager and convert to ext4, then flash Semaphore using CWM & Odin, then restore data from JVS.

I might do all these again and check it on every step to see what happen to me.

I can only flash a zip file from recovery menu now, and also CWM backup is the same, all setting in CWM Manager will lost and I must do it again using recovery menu.

But if I want to convert ext4 back to rfs using ext4 Manager, SGS will also stop at recovery menu rather than do its job, and recovery menu has no option to convert to rfs, so I can not convert back to rfs, that's my problem :)

Thanks a lot!
[Galaxy S I9000 Android Development] zsandras:
Thx mate, to much resources usage of the apps was not. I verified before/after flash with SystemPanel apk, and I didn't change anything before and after kernel flash.

Dalvik cache cleaning could be a idea, but as far as I know if it would be present immediately after flash
[Galaxy S I9000 Android Development] stratosk:
First of all, you don't need to flash cfroot to convert to ext4. You may do it from Semaphore kernel (using ext4 app). But you will not have CWM application.

Do you have any additional version of busybox versions installed? If yes, try to uninstall them and retry.
[Galaxy S I9000 Android Development] Tkbf:
OK I will follow your instructions, thanks.

The reason I flash CF-root is to has CWM Manager installed so that I can flash a kernel without the requirement to connect handset to PC.

I have installed busybox 1.19.3.
[Galaxy S I9000 Android Development] boldeagle:
Can anyone confirm if RFS is working fine on JVS?

I notice there is no longer an emphasis among developers to move to EXT4 with Gingerbread although I do notice a few diehard EXT4 fans.

I remember when moving to EXT4 with Speedmod on Froyo made such a dramatic improvement. I remember some folks saying RFS is no longer lagging under Gingerbread but I can't help but wonder if that is true.

When Gingerbread came out, I upgraded to stock Samsung ROM JV9 and stock kernel and I must say it was very smooth initially but became very sluggish over the last few months.

Now after flashing JVZ and Semaphore 2.1.1, my SGS is flying now. But I can't help wondering if it will get sluggish a few months later.

Maybe I will just convert to EXT4 and take away the uncertainty haha

Does the EXT4 app over at CF thread work with JVZ and Semaphore 2.1.1? Any other method to convert to EXT4?

cheers
[Galaxy S I9000 Android Development] sarbe:
I have problems also with CWM and making a backup, I tried to do it from phone, it just reboots and saves the backup with 0mb. Going into recovery and doing it from there was the only way.
[Galaxy S I9000 Android Development] sarbe:
My BLN works intermittently with JVZ stock and Semaphore 2.1.1
[Galaxy S I9000 Android Development] stratosk:
I always use ext4. You have to use chainfire's ext4 application for the conversion.
[Galaxy S I9000 Android Development] Rosk1:
I thought about it, i have change my lockscreen to the puzzle lockscreen (sgs2 lockscreen) and i still have this problem. really annoying thing. :\
[Galaxy S I9000 Android Development] stratosk:
Did you try to reset to default gamma and RGB values from voodoo control application?
[Galaxy S I9000 Android Development] Rosk1:
it helps, thanks!

i must say, the kernel is just great!!

very smooth, fast and stable, the Media scanning is speed like a cheeta :D

i am a proud user of this kernel since v1.8.0 :rolleyes:
[Galaxy S I9000 Android Development] JJustin:
I'm going to try sticking to rfs and odexed jvz for the next little while! It seems to be the same as ext4 so far. If things start to lag, then i'll convert with chainfire :D

Semaphore is running really well at 1.2ghz, 64mb lmk!
[Galaxy S I9000 Android Development] Tkbf:
Please excuse me that I didn't notice you have told us "The attachment tar files are for flashing with ODIN." at the 1st page.

So just ignore my question regarding to flash your kernel via CWM.

I have re-do every step and check CWM recovery function, and found that if I disable "Virtual /cache to 50MB", the problem disappear.

Thanks.
[Galaxy S I9000 Android Development] bhu1:
Startosk- i dont like to say this but i have been noticing great amount of lags on 1000mhz, 1200mhz from the past two versions, only 1300mhz is stable. music tends to break on 1000mhz, 1200mhz. V1.9.0 was very good, since 2.0.0 their are many problems. I hope u will fix these.
[Galaxy S I9000 Android Development] stratosk:
You can still flash kernel via CWM if you untar the file fist.
[Galaxy S I9000 Android Development] stratosk:
Hi BHuvan goyal,

I'm afraid that I can't fix it. The main reason is that I didn't touch a single line of code since 1.9.1.

The only changes is the new proprietary Samsung modules (for rfs, and fm radio) included in JVZ initramfs.

No offence, but It's sad to read statements like this from a power user like you: 'many problems', 'great amount of lags', 'music tends to break'

Maybe, you are right. Maybe latest versions are crap. But,

Can you post the exact steps to reproduce this issues?

Can you post which applications used and got these results?

Did you try the newest Semaphore versions in your old stable environment?

Did you check the possibility that maybe something goes wrong in your configuration or ROM you are using?

Few days ago, oserx said that 1.9.1 is laggy and 1.8.0 was OK. After many questions I found that he made some tweaks that worked only on 1.8.0 and under certain circumstances could cause conflicts.

Again, I don't say that maybe it's not kernel related. I 've never said that Semaphore is 'fast' or 'stable' or 'bug free'. I had hundreds of posts in this thread with problems and many of them was custom ROM related. But I didn't post in ROM's thread 'your rom is laggy, fix it'

Really, statements from developers like you make me want to drop Semaphore project.
[Galaxy S I9000 Android Development] bhu1:
Sorry, i dont tend to report problems until i myself face such problems and not my rom users. But music tends to break on 1000mhz on smartass v2 and tw 4.5 launcher using player pro or stock music player . Right now on 2.1.1 its stable, ill report if i face problems again.
[Galaxy S I9000 Android Development] danieldmm:
Me too using 2.1.1, everityng work great in my custom ROM, no issues...

Cheers
[Galaxy S I9000 Android Development] bhu1:
Include in doctorz rom v12 although i had some issues earlier but the king is king and will remain king.
[Galaxy S I9000 Android Development] stratosk:
I'm sorry if my post sounded offensive. I didn't mean this.

Semaphore is definitely not the king, and I didn't say that is a good product (but I want to be a good one).

I'm just trying hard to tweak and add some features (mostly made by other devs) on a linux kernel. And I'm trying to do this in a professional way because I'm a professional developer in real life and I like doing this. I built my first linux kernel for my PC, 15 year ago. I also spent all my free time since June for this project.

Maybe I failed, but I would really appreciate help from good developers like you to improve this product.
[Galaxy S I9000 Android Development] sbnaul:
Lol stratosk... i had the laughter of my life when u said 'Maybe i failed' even after making such a good kernel...
[Galaxy S I9000 Android Development] bhu1:
No it wasnt even a bit offensive, i can surely say that this kernel is king after trying other kernels last night. It doesnt have any competition. One thing- why have u removed the 'hard to kill launcher' feature. It was good. Keep up the good work. ;)
[Galaxy S I9000 Android Development] Fenvarien:
Stratosk,

your hard work and your kernel is really good and a great contribution to the android community. I recommend Semaphore as often as possible and the feedback has always been very positive.

Please think of your many silent fans, users which use Semaphore and are just happy with it. Not everybody goes for massive OC or tweaks to the max... but with Semaphore and Semaphore App optimizing the phone and stability come together :-) Thank you Stratosk!

Gesendet von meinem GT-I9000 mit Tapatalk (Stock JVZ with Semaphore 2.1.1)
[Galaxy S I9000 Android Development] cdmackay:
Yup, another vote for the silent, happy, majority :)

Thanks again, for this excellent kernel.
[Galaxy S I9000 Android Development] DocMarc73:
No issues on stock jvz here. Great work! will donate. We all should buy him some beers/coffees !-)
[Galaxy S I9000 Android Development] keuda:
Another semaphore and stratosk fan here!! Impressive all your work. 2.1.1 its working great, fast and,stable @ 1200.

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] darckengel:
It was just a script in semaphore app for LMK Settints.

If you want Hard to Kill Launcher, just add this line:

ro.HOME_APP_ADJ=1

in the build.prop file.
[Galaxy S I9000 Android Development] AGiovanni:
Hi Stratosk, perhaps this post is totally useless, but I must tell you: thanks for your job (your kernel works very well), but, above all, thanks for your style and your polite support to the users. Unfortunately my English is bad indeed, I hope to succeed in expressing my thankfulness.
[Galaxy S I9000 Android Development] bhu1:
hmmm......apparently i didnt knew about this. Thankxx
[Galaxy S I9000 Android Development] Psylosteriva:
Is it possible to compile kernel with bcm4329 module:

drivers/net/wireless/bcm4329/Makefile line 9

-DGET_CUSTOM_MAC_ENABLE

Disable above definition and make a new bcm4329.ko

to get mac spoof feature ?
[Galaxy S I9000 Android Development] mrweqa:
JVZ 2.1.1 tested and working on my rom (XXJVT), just thought I'd let you know so you can tell others :)

Also can you contact the creator of this feature and implement it to your kernel? (BackLightNotifications)
[Galaxy S I9000 Android Development] Steephig:
Read the 1st post of this thread first please.
[Galaxy S I9000 Android Development] burner07:
I found the problem with Wi-Fi not working after lagg fix ... the problem is that BUSYBOX is not correctly installed thats why it wont detect my phone and if i want to update busybox from market i dont have enough space then after restart every thing brakes... can you please fix this problem thx
[Galaxy S I9000 Android Development] stratosk:
Please uninstall any additional busybox versions. Semaphore comes with it's own bundled busybox.
[Galaxy S I9000 Android Development] Namiga:
Hi @stratosk.

Only a bit of your help :)

I run the latest JVZ version of Oserx Rom, and got a strange problem, but is only related to ext4.

Is a problem with Sygic GPS. With partitions in RFS the program runs great with JVZ and 2.1.1 kernel.

The problem is when I convert partitions to ext4, that Sygic gets frozed when showing the map, after calculating the route.

The rest of programs I use runs fine with ext4... So I wonder if could be a problem with the conversion to ext4 ...

With JVT and kernel 1.8.0, 1.8.2 and 1.9.1 Sygic works great in ext4.

Any idea about it??

Thanks in advance :) and thanks for a great Kernel .
[Galaxy S I9000 Android Development] stratosk:
Hi,

I doubt that problem is ext4. Applications don't 'understand' the filesystem is used.

Maybe it's space problem? Did you enable virtual cache option? Can you please try to clean the /cache partition?
[Galaxy S I9000 Android Development] ZaneZam:
No need to "bold" here, the problem comes from additional installed busybox in use with bb installer versions before 12/05/11, check changelog from stericson!
[Galaxy S I9000 Android Development] Namiga:
Hi stratosk.

I have space left, almost 2Gb :)...

I thought thatthe virtual cache was market related, but I will try :)

Also try to clena the /cache partition.

Thanks for the advices.

See you
[Galaxy S I9000 Android Development] stratosk:
I will check this and let you know.
[Galaxy S I9000 Android Development] bahaa89:
Where can I find ext4 manager application?
[Galaxy S I9000 Android Development] hhhans1:
this kernel, for JVQ, have bootanimation enabled? should i do steps to enable it?
[Galaxy S I9000 Android Development] stam91:
Here, pal:

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

Seems like placing your custom bootanimation.zip to system/media folder. Don't forget to mount write mode (rw) first. I suggest to use Root Explorer.
[Galaxy S I9000 Android Development] hhhans1:
Thank you..now is time to make my wife dancing when i boot my sgs:)

thanks again
[Galaxy S I9000 Android Development] stratosk:
Or in the data/local if the system is almost full of space
[Galaxy S I9000 Android Development] :
if u ask me its better to place it in data/local - i once had a corrupt bootanimation.zip and the phone was stuck in bootloop. i then tried to get into adb to delete the file - i thought i would. it did not work for me to delete the file, whenever i asked for root permissions i got a simple "permission denied" (or so) replied but no root.

wasn't able to delete the file. i rolled over a backup without this file and was good to go, but nomore time i place this in system when i can place it in data - which can easily be removed without root (on recovery -> adb) :)

that just as a sidenote. if u have lots of backups then you probably won't need to do that, just my thoughts on that ;)
[Galaxy S I9000 Android Development] ajazz:
thank you it works.
[Galaxy S I9000 Android Development] stam91:
Oh, hi, stratosk!

Reminding the iptables (droidwall) problem: http://xdaforums.com/showpost.php?p=15409455&postcount=527

What is that "getprotobyname()..." string, is this a fix and is there a way you can implement it in your Semaphore?
[Galaxy S I9000 Android Development] stratosk:
I didn't forget you :) Just give me some time to investigate it
[Galaxy S I9000 Android Development] stratosk:
Hi stam91,

I found that droidwall needs one more netfilter module to work properly: xt_owner.ko

I will included in the next version.

Until then, you may find attached the xt_owner.ko module. Copy it in the data/local and use the enable_netfilter script in the attachment (replace the old one, it runs better and also includes the new module).

About the "FIX ME!..." error just ignore it (It's just a message from iptables).

Please let me know if this helps
[Galaxy S I9000 Android Development] stratosk:
It will be very helpful if you can provide me step by step instructions to reproduce this problem on stock JVQ (with the 1.3.0 kernel).
[Galaxy S I9000 Android Development] hofinho:
am i blind or is there no jvh version available for download anymore? can anyone upload it for me please!? cheers
[Galaxy S I9000 Android Development] stratosk:
Sorry, my mistake.

In the first post, file: Semaphore_kernel_v1.0.1.tar
[Galaxy S I9000 Android Development] hofinho:
thanks, mate
[Galaxy S I9000 Android Development] maopaopao:
I can't enable BT from the pull down menu but can enable BT through setting/wireless, I am on criskelo V76 (Sema kernel 1.3.0). Other then that, the kernel works perfect!

upadte

after enable BT from setting/wireless for first time and BT can be enabled from pulldown menu now.
[Galaxy S I9000 Android Development] from.insider:
i am having "USB tethering error" after flashing JVQ kernel into Juwe rom v5.1. Now, i can only stick with Talon kernel which provided in Juwe kernel. In some occasion, Talon kernel is kind of lag even lag fix is activated.

Is there anyway i could use semaphore JVQ kernel into Juwe room?
[Galaxy S I9000 Android Development] JazonX:
I believe there are people already usin both.

Juwe's Smart 5.1

with Semaphore 1.3.0

No proper review yet though..
[Galaxy S I9000 Android Development] stratosk:
The answer is in the first post.

You have to copy the enable_netfilter script from res/scripts to system/etc/init.d to use tethering
[Galaxy S I9000 Android Development] stam91:
stratosk, the iptables problem is solved, your xt_owner.ko works perfectly, droidwall is active. You can implement it to your new release. Thank u and wheehaw!)
[Galaxy S I9000 Android Development] Hypergamma:
Hi.

I have a strange problem here. I can't find any init.d folder to copy the netfilter script in. The rom is a deodexed jvq stock rom from xda. So while i can't understand this I looked on my tab and there is also no init.d folder in system/etc. On the tab runs an unofficial stock gingerbread 2.3.3. with cfroot.

The only thing i found on both is in sbin. There's a folder named boot. Here are different .sh scripts from cfroot like the tweaks or ext4 script. So i tried to copy it inside here. Mounted read-write, renamed .txt extension, set permissions, mounted read-only back and rebooted the phone. But nothing is happend and if I look inside this folder the script I have copied was gone. I used the rootexplorer with settings on to show all files.

Maybe someone here can tell me what can I do to run the script at boottime. Thanks.
[Galaxy S I9000 Android Development] burner07:
Stratosk .... i reflasht jvz and kernel and i dont have busybox, when i want to install supercharger for example it says no busybox found .thx
[Galaxy S I9000 Android Development] Namiga:
Hi stratosk ...

I´d converted to ext4 and formated /cache partition

By now Sygic seems to be OK, and I got no problems now...

Tomorrow will test in in a short travel and let you know :)

Thanks again