yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] mawardi:
I run some test. Here is the result:

No UV at all - works fine when screen off and on

Clock at 400MHz with No UV - fine on and off with Tasker On

Clock with UV - fine when on but freezed when off. Disabled Tasker and using PMC, fine when off.

Set 200 and under, fine when screen on but freezed when off.

I have no idea what's going on. TalonDev does not have this issue.
[Galaxy S I9000 Android Development] pikachu01:
It's obviously a UV problem.

Disable UV and run tasker at 400MHz. It runs fine doesn't it?
[Galaxy S I9000 Android Development] lucbl1:
Excellent Kernel ;)

Could you include the 10-point multitouch fix that is present on galaxian kernel?
[Galaxy S I9000 Android Development] stratosk:
Thanks for your feedback.

Excuse my ignorance, but what exactly does this fix?
[Galaxy S I9000 Android Development] bravoleader:
Will we ever get a fix for the BT issue? I'm trying any black magic stuff but nothing works atm :(

F
[Galaxy S I9000 Android Development] Rebel2k:
As long as the issue is not fixed in the initramfs it will not work correctly.
[Galaxy S I9000 Android Development] bravoleader:
I got the BT to work but as far as i rebooted the phone tons of times, cleaned cache and DCache over and over, applied lagfix. now it works. I don't know what i did but it was effective XD I hope that it will get fixed so you do not need to use any workaround ^^

Cheers

F
[Galaxy S I9000 Android Development] stratosk:
For the BM version, 720p video recording I guess never. Photo capture is just not included in BM. It could be changed, but I prefer (and many users also) it this way.

For the normal version of course you have everything. :)
[Galaxy S I9000 Android Development] ZaneZam:
Great! Thx a lot for the bm version and even more for the scbm version! I am testing right now! ;)

Maybe one thing to mention in addition in the 2.5.0(sc)bm cangelog is that frontcam pic capture does not work on bm versions, as discussed it leads to a frozen cam app! ;)
[Galaxy S I9000 Android Development] djb77:
I did have busybox installed...

Here's what I did:

- Uninstalled busybox

- Reflashed kernel

- SUCCESS!!

So I'm guessing it may be a busybox collision.
[Galaxy S I9000 Android Development] stratosk:
Semaphore comes with the recovery embedded 1.19.3 (cm7 edition).

You don't have to install additional version.

So, I think we are OK now. :)
[Galaxy S I9000 Android Development] stratosk:
Change log corrected.

scbm version attached in the OP.
[Galaxy S I9000 Android Development] SupremeXXL:
Sorry My bad :) I always usinh normal version. So eveything is OK;)

By the way I admire your work and support all the way thanks.

Loves and congratulations from Turkey !
[Galaxy S I9000 Android Development] djb77:
Yep we're good. I removed the busybox installer from my Custom ROM and it now installs perfectly.

Sorry for wasting your time hey.
[Galaxy S I9000 Android Development] kout:
hey thanks for this great kernel

I just can't convert my partitions to ext4 with Chainfire app anymore

is there another way to do it ? is this still useful or is RFS ok ?

(it seems to be)

I have stock JVU+this kernel
[Galaxy S I9000 Android Development] ~ Myzrael ~:
Why you can't? Anyway, rfs is good
[Galaxy S I9000 Android Development] knak2k1:
thx. but isnt voodoo and/or speedmod color better than stock?
[Galaxy S I9000 Android Development] burakgon:
I can't update su binary with superuser app. I'm on bigmem + sc
[Galaxy S I9000 Android Development] kout:
this app reboots my phone, then a few lines appear, and I barely see "aborted" and then it reboots but nothing happened

anyway it works well with RFS but idk ext4 might give it an extra boost
[Galaxy S I9000 Android Development] bokbacken:
Thanks for your excellent work!

Hi!

Please enjoy something good when you take a break next time, these are on me!

Confirmation number: 28K19051M9250402M

Hope more users show some gratitude to you, you really deserve it!
[Galaxy S I9000 Android Development] maopaopao:
BM version don't have front camera capature?
[Galaxy S I9000 Android Development] stratosk:
It depends on your eyes. :)

Any error messages?

Is should work. I tested many times and I'm on ext4.

How much free space do you have on SD card?

Thank you very very much. I really appreciate this my friend!

No, as you may read in change log.
[Galaxy S I9000 Android Development] sothebad:
Hi Stratosk,

thanks for this wonderful kernel! def the best 1.

I'm having problem with the latest version

I'm having these error in CWM, any idea what's wrong?

E:failed to open /etc/recovery.fstab ( no such file or directory)

E:unknown volume for path [/cache/recovery/command]

E:can't mount /cache/recovery/command

and some more line. it all said cant mount something... hmmm
[Galaxy S I9000 Android Development] knak2k1:
I flashed the kernel now. but how to enable bln?
[Galaxy S I9000 Android Development] burakgon:
Superuser update.

When I press update button:

Everything is okey and I accept the superuser request.

Eveything is okey and at last Checking installed version = fail!

I think that's something to do with permissions. Where is the location of this files to change permissions. I will add a chmod script to my gamerzrom to fix it.
[Galaxy S I9000 Android Development] stratosk:
Hi,

Any specific actions before you get this?

Any mod about file system?
[Galaxy S I9000 Android Development] omarbenjdida:
Thats work with onecosmic RC3??
[Galaxy S I9000 Android Development] stratosk:
Please use bln control application. You may find it on market.

It's on /system/xbin. But I doubt this is due to permissions.
[Galaxy S I9000 Android Development] burakgon:
Is it something to do with my rom or a kernel thing? I will try the vc bigmem one.
[Galaxy S I9000 Android Development] Millionas:
Why isn't the front cam working on 2.5.0bm and jvu? Will there come a fix? Need it in case someone steels my phone (cerberus app).

Does the front cam work on 2.4.0bm and jvu?

Love your work!
[Galaxy S I9000 Android Development] stratosk:
I really don't know but I've never had this issue.

No, only on stock gingerbread roms and custom based on stock.

No it does not work on bm version. It works only on normal.

Camera app changes on JVU. It needs more memory for this functionality (???) So, I kept this only on normal version.
[Galaxy S I9000 Android Development] burakgon:
I will build the rom from "0" with semaphore.
[Galaxy S I9000 Android Development] Millionas:
Ok I understand. Will stay on the normal one until you figure it out ;-)

Just a question: if I install camera app from jvt on jvu, will the front cam work on BM? Or does it lay deeper?
[Galaxy S I9000 Android Development] stratosk:
Can you check the permission of this file in your rom?
[Galaxy S I9000 Android Development] philipas:
Hi

Great kernel! I'm using this with SURFACE v9.01 Rom & TB scripts.

I've read that flashing Semaphore on SURFACE breaks the included TB scripts, so you need to re-flash the TB scripts. I've also read that there are some conflicts / overlaps between some of the Semaphore and TB init.d settings.

Can you advise which options in Semaphore are not relevant when using the TB scripts?

Thanks

Phil
[Galaxy S I9000 Android Development] Rebel2k:
I have the same error with superuser. Can't update it. It seems that the version number of sure can't be read. It is written "legacy" as version in the preferences of the superuser app and version can't be retrieved. I never had such an error in any semaphore version before...

Edit : I'm using the 2.5.0 stock colors version.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
Semaphore does not touch the init.d directory. By default all kernel's features/scripts are disabled.

Honestly, I never installed TB and I don't know what are the conflicts.

Please ask Pikachu. I think he knows better about this

I've just flashed sc version (god, I think I will break my phone after so many flashes :) ).

Everything is fine.

Just a shot. I believe you have an su binary from other kernel. Delete the cfroot directory in /system and reboot. Kernel will install the 3.0.3.2 version.
[Galaxy S I9000 Android Development] Rebel2k:
In fact I cleant Busybox with Semaphore Script Manager, restarted the phone and that's ok. It must have been another busybox instance which had been left there around... ;)

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] elhennig:
I had some old busybox from another kernel installation that prevented adb from working. After cleaning busybox with Semaphore app I can confirm adb working flawlessly...
[Galaxy S I9000 Android Development] burakgon:
Another busybody :D
[Galaxy S I9000 Android Development] kout:
well, what do you know, I uninstalled and reinstalled chainfire's app, and now it works, sorry for the bother
[Galaxy S I9000 Android Development] jna9000:
Can old backups be restored using the new CWM?

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] Rebel2k:
T9 word completion powaaaa! Lol... Busybox of course!

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
I think yes. But I recommend to make new ones just to be on the safe side because I didn't test it thoroughly. (good question I will update the first post)
[Galaxy S I9000 Android Development] EseLoKo:
Seems that everything is perfect with this "stable" version in stock JVS.

Thank you @stratosk.

I will post if I found any trouble.
[Galaxy S I9000 Android Development] hackeron:
Just flashed latest 2.5.0sc , and had usb connected to computer, while entering video mode and taking pictures with the new camera function. Just to try it out, and suddenly colors were totally weired, yellowish and green all over.

Then I rebooted the phone, everything was normal again.. Tried to recreate the bug. but It didnt happen again.. Can some1 try this?

Just posted my experience since Ive never seen anything like this before =)
[Galaxy S I9000 Android Development] ZaneZam:
As long as u don't touch the "Low Memory Killer" and the "SD-Card read ahead" settings in semaphore script manager you will be fine ;) assuming that you have not installed any of HM.Carbide's addon-packs (for example ScriptPack_AddOn_Tweak_v3.zip). If you use only the default bundled scripts from semaphore kernel then you can go ahead and just install thunderbolt and after that just don't touch the two mentioned settings above in semaphore script manager and dont install any tweak addon-packs. One note regarding touchscreen settings in script manager: if u install thunderbolt you will have the "s78enable_touchscreen_1" script in /system/etc/init.d directory, this is a 1:1 copy of "S78enable_touchscreen_1" from semaphore, so if u set touchscreen sensitivity to stock in semaphore script manager this script will be deleted, but you can set it again in semaphore script manager and it will be there again ( but now named "S78enable_touchscreen_1" ;) )
[Galaxy S I9000 Android Development] Jose_Paramore:
Why leds keep on if you touch them and then you touch the screen before the leds switch off?

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] stratosk:
Do you have Semaphore auto brightness enabled?

I'm sorry, I didn't understand your question.
[Galaxy S I9000 Android Development] Jose_Paramore:
Well... I was using Midnight kernel before this and with that kernel button "back" and "menu" lights where on only per a second... With your awesome kernel these lights keep on if you touch "menu" or "back" button and, before the button light switches off, you start using the screen.

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] ZaneZam:
during installation of one of stratosk's nice bootanimations i got a vision that it would be more handier to be able to set bootanimations in semaphore script manager as doing it manual :).As i was in scripting mood today i did an addon-pack for script manager which changes the bootanimation for us.

I share it HERE in hope that any of you guys will enjoy the use of it in such a way as i do! :)

It has all bootanimations from www.semaphore.gr included hence the fielsize of about 15 mb.

Download the pack for example to /sdcard/download on your phone and use Semaphore Script Manager's "Manage Packages" to install it!
[Galaxy S I9000 Android Development] Coolgreek:
Hi Strato,

Can the new cwm 5.x flash old cwm 3.x zip files without problem?

I read that yes but it happened to me not to be able to flash a theme through cwm 5.x (although the flash was reported as successful by cwm) but then i flashed 2.4.0 again, try it it through cwm 3.x and it worked...

Just reporting, i read another user had this problem (at some thread) and thought it would be wise to post this in case anyone else had a similar problem...
[Galaxy S I9000 Android Development] stratosk:
I didn't notice that before! But I've never touched the code for backlights (except the BLN patch of course).

Is this good or bad? :)

Excellent! I will try this!

Hi,

Yes it should. At least, it works for some zip files I tried.

Thanks for reporting this. Can you point me to this zip file?
[Galaxy S I9000 Android Development] Jose_Paramore:
It would be great if you modify this like in Midnight kernel. Those leds always on make me feel annoyed when playing games :)

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] Coolgreek:
It was this theme but allow me to test it once again before you do! I will reflash the undo zip file to get back to stock JVU and the try it again through cwm 5.x

Will report back as soon as i have results!

RESULTS: this time all were successful, i tried both the restore zip to get back to stock JVU (with success) rebooted the phone then reflashed the theme zip and all worked... I do not know what and why, but this as "weird". It could be that the phenomena happned with semaphore 2.5.0 beta although i doubt it (doubt that anything changed between semaphore 2.5 beta and 2.5 final regarding cwm).

Anyway if anyone else have a similar problem note this just in case.
[Galaxy S I9000 Android Development] hackeron:
nope. I got thunderbolt tweaks installed though, heres how my init.d looks.

Edit: Im trying to recreate the bug but I cant do it.. Tried like 2-3 times..
[Galaxy S I9000 Android Development] Millionas:
I edited my post and therefore I dont think you have seen it.

The question was:

Since the front camera dosent work on BM and jvu. Can i just use the camera.apk from JVT, push it to JVU on 2.5.0BM and the front cam will work? Or does it lay deeper in the kernel?

Maybe a silly question, but just wondering..
[Galaxy S I9000 Android Development] HM.Carbide:
Very Cool!

First "external" addon! And it works great.

Would you allow me to post it in my thread, of course with special thanks to you, creating it?
[Galaxy S I9000 Android Development] stratosk:
Noted for the next version.

I really don't know. I had this report with voodoo color (low gamma) and low brightness.

The kernel reserves more memory for JPEG driver in order the capture work correctly for JVU.

So, I assume that maybe the camera.apk from JVT will work. But, I don't know if something else changed except the kernel and the camera.apk between JVT and JVU.
[Galaxy S I9000 Android Development] bhu1:
Stratosk , I think the way the bln works in pawitp's cm9 stock kernel is best. Try if u can create the same.
[Galaxy S I9000 Android Development] ZaneZam:
As allready posted in your thread yes of course! I would be very pleased! :)
[Galaxy S I9000 Android Development] JuanRamiro:
Call recording

Hi again stratosk. This is the procedure I have done and found the call recording problem.

1. Flashed official JVU with odin, with re-partition

2. Installed "Record my call"" and make a call test. it records the call fine.

3. Flashed "semaphore 2.5" with odin. Reboot, wait 2 minutes, reboot again.

4. Made a call test: The other party cannot hear me after 3 seconds (just after the 3 sec. delay to start the recording)

I have also triad Galaxian kernels, TalonDev, Midnight... but exactly same thing happens. The call recording works with stock and Chainfire kernels.

If someone tells me how to get the log you asked me for, I will send it to you or post it.

Thank you stratosk.

Edit: When the recording "works" with stock an CF kernels, it records ONLY THROUGH MICROPHONE.
[Galaxy S I9000 Android Development] stratosk:
Thank you mate! your idea about external addons was terrific!

I've just tried this! Well done my friend! I really needed this!

Can you please describe what it does?

Hmm... I suspect that this also has to do with reserved memory. Anyway I will try to check it when I 'll find some time.
[Galaxy S I9000 Android Development] philipas:
Hi Zane

The only thing I've changed is UC (to 800) and Scheduling (to Simple IO).

So I should be OK, hopefully.

The other thing I'm not sure about is whether I need to set the remount script settings in Script Manager - it does not seem to be set by default in SURFACE ROM.

Phil
[Galaxy S I9000 Android Development] JuanRamiro:
I have also tried with bigmem versions and same thing.

I have just tried JetPack Rom (v9) after reflashing Stock JVU with Odin and re-partition. And same thing happens.

I have also tried AllCallRecorder... exactly same thing.

And same thing happened with some JW1 roms and kernels (tried a few)... only stock and corresponding CF kernel recorded the call correctly.

Good luck with it, and thank you again.
[Galaxy S I9000 Android Development] stratosk:
With the bigmem versions, kernel reserves less memory and you have less possibilities this to work (if it is caused by the reserved memory)
[Galaxy S I9000 Android Development] stratosk:
I 've just received a PM to implement in Semaphore a functionality of Galaxian kernel.

Few times in the past, I was asked to implement Galaxian colors. And I answered that I would check it.

I'm not happy to say this but yesterday, I downloaded galaxian tarball and I saw that the sources were 1 month old. I asked Lukiqq to update his sources and never answered to me.

Anyway, I don't know if this violates GPL. I don't care. I think that this community grown because of sharing knowledge, code, mods. Many parts of Semaphore kernel tweaks or code are made from other developers. I would be proud if someone could use my tweaks or code.

If someone don't want to share his work, I don't want to take it.

So, please don't ask me to implement Lukiqq's features in Semaphore kernel.
[Galaxy S I9000 Android Development] hackeron:
Hes known for not sharing sources (or being very slow at it), his thread have been locked 2 times cause of this.. When existz asked him for sources a while back the same thing happened.

Semaphore is awsome as it is btw =)
[Galaxy S I9000 Android Development] jeozme:
that is totally fine. I just thought in case it is about a setting only or something like that it could be easy to adjust. I didn't know that it would be a big thing to adjust that driver. Never mind. I understand the problem.

Btw. He answered just 6 min after somebody asked to update the tarball ;)
[Galaxy S I9000 Android Development] ZaneZam:
Hi Phil,

You gonna be ok with this settings, yes. You can switch around any settings you wish in semaphore script manager except the LMK and SD-Card tweaks or if installed the tweaks from tweak addon-pack. Yes the remount script step has to be done manual. If you want the optimized thunderbolt mount options for ext4 filesystem you have to set the remount script to execute as root and boot in script manager, then it will be executed on every boot.

hope you get it working without problems! :)
[Galaxy S I9000 Android Development] stratosk:
The problem is not how easy or difficult to adjust something. This is not my point.

And of course, it is totally acceptable to ask for new features that other developers already done.

Lets everybody think that we have custom kernels because it's Linux. And it's open source. We would not discuss these things if Linus and thousands other developers were hiding their findings.

And I want to serve the idea of Linux.

BTW: Check my post in Galaxian thread at "14th January 2012, 11:27 AM"

Tashuya79 copied my post at "Yesterday, 11:31 AM"

and Lukiqq answered 6 minutes after Tashuya79 post and 24hours and 10 minutes after mine ;)

And he should post sources without somebody asks him. ;)
[Galaxy S I9000 Android Development] ZaneZam:
Yeah i needed this too, glad that you like it! :)
[Galaxy S I9000 Android Development] sothebad:
No sir, I just flash from 2.4.0 and my filesystem is rfs for system and ext 4 for the rest.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] ZaneZam:
hmmm... these errors are looking exactly like those i got with the first 2.5.0 beta version you released stratosk.;)
[Galaxy S I9000 Android Development] stratosk:
And the fix was a removal of a symbolic link in /sbin from busybox to recovery.

Do you have any busybox installed? If yes please remove it. Did your file system corrupted? I mean are you able to boot normally?
[Galaxy S I9000 Android Development] elhennig:
Is the front camera supposed to work with the big mem kernel?
[Galaxy S I9000 Android Development] sothebad:
yes, i have removed it.

I can boot normally. just that i can't do anything in recovery. :(
[Galaxy S I9000 Android Development] ZaneZam:
The first post often contains needfull information! ;)

Front cam works on bm versions, but capturing pics from it doesn't on JVU roms.
[Galaxy S I9000 Android Development] stratosk:
OK, I think I found something. You said that your system is in rfs and the other partitions in ext4. I just thought that this can't be done with chainfire's conversion application. You converted with other kernel. I think that maybe different ext4 options prevent recovery to mount partitions correctly. Similar situation with AndiP problem.

As a workaround:

Backup your data. Convert to rfs. And then convert to ext4 again. Then recovery may be able to mount the partitions.

Please backup your data first.
[Galaxy S I9000 Android Development] djb77:
One weird thing I did notice once in my journeys is when I look at ext4 manager it will show both options for conversion (ext4 or rfs)

When this happens I usually just go straight to ext4, then back down to rfs if I need to capture a system image.
[Galaxy S I9000 Android Development] sothebad:
hmmm i converted with chainfire's ext4 app.

system was left with rfs is because it doens't have enough diskspace for conversion. I'm with your kernal all these while :) big fan of yous...

I tried converting to rfs also by using the app but when it rebooted it said cant mount as well.

I guess my last option will be to reflash from scratch.
[Galaxy S I9000 Android Development] stratosk:
Just a thought. :)

I can't thing anything else right now mate.

But, if you can live with this a little perhaps we can find the problem before flashing from scratch.
[Galaxy S I9000 Android Development] sothebad:
yes sure!

still trying to troubleshoot it :)

flashing back to 2.4.0 and trying to convert all back to rfs and i will try 2.5.0 again

thanks for your instant response sir!

hmmm, no luck. guess i will just live with this for awhile then :)
[Galaxy S I9000 Android Development] sirbrian:
I have just finished flashing to DarkyROM 10.4.2 and came back to Semaphore 2.4.0 Kernel from the default DarkCore 4.2.1 Kernel due to some widgets problem with GO Launcher EX.

May I know if just a normal reboot is good enough or must i do other steps (which I read in previous post that clearing dalvik and system cache?)?
[Galaxy S I9000 Android Development] DarkSorcerer:
Stratosk,

Nice to see that changelog! :) Still following this thread closely! Hope to see you succeeding in these changes! ;)

Regards,
[Galaxy S I9000 Android Development] go4saket:
Hello! I am on Simplicity 2.1 ROM with XXJVT 2.3.6.

Can I use the latest version of Semaphore with the above version or will it cause any issues with it?