yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] roshan2989:
how to enable BLN light in Semaphore manager....i just install BLN Pro in my phone...the BLN light wont blink..im using cm10 30.9 with semaphore 2.0.2s with hugemem patch...
[Galaxy S I9000 Android Development] stratosk:
http://xdaforums.com/showpost.php?p=32258265&postcount=136
[Galaxy S I9000 Android Development] stratosk:
I'm not sure, I understand what's going on.

Since you are in recovery, please try to make a fresh install. Try to install cm10 for a second time after abort.

BLN control is enough. Just make sure that you have the notification light enabled in Settings->Display
[Galaxy S I9000 Android Development] mortallkombat:
ok, i already tried multiple times doing a fresh install of cm10 after abort but it still aborts again..............i even also re flashed d semaphore couple of times but still it couldn't pass d semaphore screen........guess am gonna end up flashing a stock rom n come bk 2 cm10........i really used ur semaphore on cm9 n had no problem but i flashed it with odin, here i flashed through cwm as a zip file, i wouldn't know if that in any way was d problem
[Galaxy S I9000 Android Development] alexovy:
@stratosk

Did you change anything in the kernel regarding the possibility to switch on the phone while charging? It looks like it is working now :)
[Galaxy S I9000 Android Development] stratosk:
Yes, fortunately the open source charger from cm10 with the tiny lpm.rc (the init script that is used during LPM mode) did the trick.

So, thanks and credits to cm10 team.:)
[Galaxy S I9000 Android Development] TheLach03:
Ohhh I understand now!

Mate you aren't crazy at all! I didnt realise he'd posted them round for other projects!

I completely agree with your decision; semaphore is it's own beast, in a league of it's own, and deserves to be its own project, not linked with other projects that don't even compare!

As i said before mate, keep up the amazing work! Everyone here is truly grateful for it, and youre helping prolong the life of our galaxy s phones so much longer than any of us thought possible!
[Galaxy S I9000 Android Development] mortallkombat:
problem seems to be getting worse .....tried flashing d value pack everything runs smooth from odin n i get a pass but get some error lines in red when d phone is about booting up.....it comes to the android recovery n i reboot n then it starts with d samsung boot screen n logo n continues looping on d samsung logo screen..............hv tried full wipe and cache wipe n reflash n its all d same............what do i do?
[Galaxy S I9000 Android Development] Silentbob999:
I took a look at your post history. I think something fail in the partitioning, but before I'm saying something stupid can you confirm that you are able to boot on cm10 last nighty stock without semaphore ?

Edit, probably not partitioning because you were working on 09/29. So too late I already said something stupid.

Stratosk will probably like if you can take last kmsg to see what those red errors line are.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] mortallkombat:
thanks for ur time but u seem not 2 get it i cant boot past d samsung/cyanogenmod logo......................so i tried flashing cm10 again n it aborts and i tried cm9 and it aborts ......they all return me to the recovery ......so i went for a GB rom(value pack) flashed thru odin a lot of times and still could not boot pass the samsung logo screen even tho i get a pass in odin ..........so i just figured even tho i cant boot, i should root and install cmw...........i did n got back 2 recovery, flashed cm10 again and it aborted n i tried cm9 n it flashed so i was happy n updated from cm9 to cm10 now............seems i am gonna stick with d stock kernel for somewhile ................its been the roughest night of my life ........i have virtually flashed everything available
[Galaxy S I9000 Android Development] prbassplayer:
Odin a kernel that has the has the correct partition set up. Cwm is probably not able to mount system. Or last resort Odin with repartitions back to a samsung firmware.
[Galaxy S I9000 Android Development] mortallkombat:
wow! what a night i cant actually believe i got thru this ......i just restored the backup i created b4 d semaphore on cm10 n it worked perfectly..................even tho i lost so much sleep time this night, i have really learnt a lot.........and thanks for trying to help me resolve my issue........i am grateful but will still hold on with installing semaphore for now as it gave me a terrible scare this night

---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------

thanks a lot, i already got thru the whole nightmare
[Galaxy S I9000 Android Development] tuncan:
After upgrade to AOKP JB build 4 (from ICS version of AOKP and Semaphore), I also installed Semaphore 2.2.0.

It looks ok (I can see Semaphore picture on boot time, it is listed in About Android ...), but I can't find any icon to go to settings. Like it was on ICS.

How can I change settings?
[Galaxy S I9000 Android Development] masterg0g0:
There is a app in the market for it, you can search right?
[Galaxy S I9000 Android Development] tuncan:
Thank you.

After coming from ICS (where this app was installed without go to Market), I thought something is wrong. Then I read OP and semaphore FAQ, but I didn't see anything (maybe I missed).

So, I asked - sorry :p
[Galaxy S I9000 Android Development] Jacktheskipper:
Just a quick ...

... question since I read there are clean up scripts for cm9: If I wanna test Semaphore on CM10 but would want to revert to stock kernel (or would flash the next nightly and it will be on stock if I wanted or not) would there be any leftovers from Semaphore that could/would prevent the system from running correctly or would it be gone without a trace and no trouble to expect?
[Galaxy S I9000 Android Development] Kees-Jan:
If you are on Semaphore Kernel and want to try something else, I'd recomment to boot CWM, under Advanced you'll find

"clear init.d directory", "clear NSTools settings" and "Clear Semaphore Manager settings"

after that you can use anything and go anywhere you want...
[Galaxy S I9000 Android Development] roshan2989:
i have problem with my gps wont detect my current location...?
[Galaxy S I9000 Android Development] Jacktheskipper:
Thanks a lot for the information!
[Galaxy S I9000 Android Development] jv.batista:
AFAIK the gps issues in cm10 0930 and 1001 are kernel related. just tried with devil 1.6.1, semaphore 2.2.0s and stock. On stock, gps works fine but on sema and devil it doesn't work at all...
[Galaxy S I9000 Android Development] Rahlp:
All video playback and all recording broken...

ROM: MIUI JB with new partition layout from here: http://forums.miui.us/showthread.php?21478-MIUI-us-JellyBean-I9000-Release

using the semaphore 2.2.0s kernel...
[Galaxy S I9000 Android Development] Kees-Jan:
Oh? I'm on Semaphore 2.2.0s and having no problems with GPS!
[Galaxy S I9000 Android Development] stratosk:
As far as I can see, there are no changes in CM github in the kernel for days.
[Galaxy S I9000 Android Development] jrongi1:
You will need to ether patch the video related files or use 2.20 not "s"

PA_Vibrant 360° Productions
[Galaxy S I9000 Android Development] Rahlp:
I have already patched it.. I also tried using Mackay kernel with the patched lib files for JB still not working...
[Galaxy S I9000 Android Development] jv.batista:
so, what can cause this?
[Galaxy S I9000 Android Development] stratosk:
I'm sorry, absolutely no idea. :)

Any error in logcat?
[Galaxy S I9000 Android Development] jv.batista:
will try get one as soon as I can...
[Galaxy S I9000 Android Development] Gvdn:
Damnit and i just wanted to ask you the next winning Lottery numbers. :p
[Galaxy S I9000 Android Development] Rahlp:
Flashed 2.2.0 and its working.

Got problem with gps here too... its detects the location almost correct just a few meters away but it doesnt move when I am moving.. like in a car...
[Galaxy S I9000 Android Development] toddmworth:
This post took me twenty minutes to write. Why? Because my fingertips are scarred and

2.1.0 (17/09/2012)

- Semaphore scripts: removed touch screen sensitivity options

I just upgraded.... Edit: to 2.2.0s

Can anyone help me adjust sensitivity? I am a little curious about why this was removed :)
[Galaxy S I9000 Android Development] RuffBuster:
I'm using this https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
[Galaxy S I9000 Android Development] kot7k:
Hi,

I searched this thread and found various references that people cant mount usb storage through recovery, this happens to me too, is it a known bug? or is there something wrong with our configuration? do this happen to all people?
[Galaxy S I9000 Android Development] Kees-Jan:
Just tried...

Its taking a while (about 90 secs) but then the drives (both) show up in Windows Explorer :victory:

:good:
[Galaxy S I9000 Android Development] TinyFeather:
Stratosk, not sure if this feature is already in your kernel, but please, add the "Fast Open" feature from linux 3.6 in your kernel :) Fast Open could result in speed improvements of between 4% and 41% in the page load times on popular web sites.

Just sayin'

I love your kernel :)
[Galaxy S I9000 Android Development] toddmworth:
Thanks man, that does the trick. Would be nice to have kernel support back though, so that we don't have to run a service :(

Any word on whether writing parameters to /sys still works, would be awesome :)
[Galaxy S I9000 Android Development] kot7k:
Well, they show up for me too (almost instantly) but when i click on them it gives you an error and you cant see the contents of your sd card
[Galaxy S I9000 Android Development] judhas:
Use Linux...all your problems will disappear immediately...good luck.
[Galaxy S I9000 Android Development] superkoal:
You can still use the old script manager or just use the touchscreen script as init.d ;)
[Galaxy S I9000 Android Development] stratosk:
Thanks, I will check it.

I'm on Fedora 17. Both internal and external are mounted instantly and work fine.

Unfortunately, this will not work.

Touch sensitivity init scrips were removed from the kernel because they simply didn't work. Semaphore Script manager reads the scripts that are included in the kernel. So, the app will not find them.
[Galaxy S I9000 Android Development] Sharken:
Been using 2.2.0 for a while now with 120% Live OC and its very stable for me. In fact i dont think there is much more to add, everything is working great.

Btw if you are considering a new splash screen, i would like to vote for the ones posted by TheLach03 at http://xdaforums.com/showpost.php?p=32188926&postcount=1842
[Galaxy S I9000 Android Development] Midomad:
+1 for splash screen and i think this what is missing for this awesome kernel :)
[Galaxy S I9000 Android Development] TinyFeather:
yeah, new splash screen would be great!! :D
[Galaxy S I9000 Android Development] TheeWolf:
Why? the current splash screen is much much better than the one suggested.
[Galaxy S I9000 Android Development] iyahman:
+1
[Galaxy S I9000 Android Development] jugster:
I couldn't care less about the splash screen, spend that time on something important like your family or the economic crisis. Yes in that order.

Kudos for a great kernel and a great developer!

Signature? Signature!
[Galaxy S I9000 Android Development] pl4cid:
Yes so I expressed wrong, what I ment was integration in sema manager, but this isnt important ;)

Tapatalked
[Galaxy S I9000 Android Development] TheLach03:
To everyone asking about the splash screen, please read what Strat said when I asked him!

Personally I'd love the new splash screen, but we all need to respect Start's decision, as it is certainly a fair call by him!

Besides, how much time do we actually spend looking at the splash screen? It's a couple seconds when the phone is turning on. The true brilliance of Semaphore is how perfectly it makes our SGS run! :)
[Galaxy S I9000 Android Development] TinyFeather:
I think the "Andy" is a concept that is used somewhere else too.. :P

However, a new splash-screen not very important to me.. I don't look at a booting phone, lol.
[Galaxy S I9000 Android Development] bitblaster:
Here it is, as promised:

80Y09345A6603424J

You deserve it, sorry it's not that much...

Thank you again for making my phone fly

Roberto
[Galaxy S I9000 Android Development] TheLach03:
Haha very true! But at least that is Strat's / whoevers own exclusive design for Semaphore, not something that was handed off to many developers, defeating the idea of originality!
[Galaxy S I9000 Android Development] stratosk:
Don't be sorry! Thanks so much or your help!

I really appreciate this!
[Galaxy S I9000 Android Development] DarkSorcerer:
Hi,

Just to say that stratosk is, by far, one of the people here that deserves donations and help.

You should be grateful to have him around. Really.

Regards,
[Galaxy S I9000 Android Development] goranbm:
I am quite sure I know the answer, but I just want to be sure - If I am on CM10 nightly from 3.10. i need to flash version 2.2.0 ??
[Galaxy S I9000 Android Development] malcho:
Yes

Powered by Codenameandroid
[Galaxy S I9000 Android Development] willthrom:
Logcat

Hi,

Maybe I am a little stupid but even after enabling the logger option in the Semaphore Manager and power off/on the phone, the command logcat return Unable to open log device '/dev/log/main': No such file or directory

Any clue?

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

Please try to execute logcat as root. Permissions for logcat changed on JB.
[Galaxy S I9000 Android Development] willthrom:
D:\tools\Adb>adb shell

root@android:/ # logcat

logcat

Unable to open log device '/dev/log/main': No such file or directory

1|root@android:/ # su

su

root@android:/ # logcat

logcat

Unable to open log device '/dev/log/main': No such file or directory

:(

Maybe my logcat binary is doing something wrong because there are three file in that folder, but not main.

I don't know how to read them :(

root@android:/dev/log # ls

ls

events

radio

system
[Galaxy S I9000 Android Development] stratosk:
The the logger module is not loaded. Please check the following:

1) execute 'lsmod' command in the shell. You must see the logger module.

2) execute 'ls /data/local'. Is the logger.ko file there?

3) if not, most probably you flash the 's' version and then the normal one. Please enable logger module in Semaphore app then delete the /system/lib/modules/ansi_cprng.ko and reboot your phone. This will reinstall the correct modules.
[Galaxy S I9000 Android Development] willthrom:
Thank you stratosk for your time :)

Still it is not working.....

root@android:/ # lsmod

lsmod

xpad 7628 0 - Live 0x00000000

joydev 8644 0 - Live 0x00000000

logger 1053260 18 [permanent], Live 0x00000000 (PC)

root@android:/ # ls /data/local

ls /data/local

first_boot

logger.ko

succ_boot

tmp

EDIT: I tried to remove the ansi module but nothing... still it is not working :(
[Galaxy S I9000 Android Development] stratosk:
Please post the output of following command in the /data/local directory:

grep Semaphore logger.ko
[Galaxy S I9000 Android Development] willthrom:
root@android:/data/local # grep Semaphore logger.ko

grep Semaphore logger.ko

vermagic=3.0.31-Semaphore_JB_2.2.0 preempt mod_unload ARMv7
[Galaxy S I9000 Android Development] caper:
Hi

Anyone have problems with FM module and kernel "normal" version ?

some people says that spiritFM works with the s version, but dont work with the normal version, both after activating the FM module in semalhore.

The ROM is CM10 Nightly 03/10

thanks

jmcdpereira
[Galaxy S I9000 Android Development] stratosk:
This is weird. This is the correct module for your version (normal one). The module is loaded.

This should work.

Which ROM do you use.

I'm on normal version. Module is loaded fine. Though I didn't test spiritFM.
[Galaxy S I9000 Android Development] willthrom:
EliteRom v13v3

I have tried with different binaries of logcat, but always I get the same issue....'/dev/log/main': No such file or directory :(

I do not know what else I could try.
[Galaxy S I9000 Android Development] beint:
I'm also on Elite, same version, and I didn't manage to get the logcat working a while ago as well.

Maybe it's something with that rom.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] tanivula:
I've had similar issues wish GPS, lock is fine while stationary but drops out when moving. Switching to devil kernel has improved this.
[Galaxy S I9000 Android Development] willthrom:
Yep in some EliteRom releae the logcat was broken because the binary was compiled with some stupid "color" dependencies but we fixed the problem changing the binary.

I will try to find another logcat binary from other roms a try again....
[Galaxy S I9000 Android Development] Giap:
deep idle?

Hi,

Just to understand. Could someone explain to me what deep idle does? Indeed, from betterbattery it seems to me that the time in which the phone stays in deep idle is similar either activating or not deep idle in sema manager. Thank you for reply
[Galaxy S I9000 Android Development] mikandlotta:
If you read earlier posts or search the thread you should see that enabling deep idle is not recommended as it can cause instability issues.

And, as you already noted, the phone, when 'inactive' uses very little battery anyway.

For me, enabling deep idle can be one of those things that 'tip it over the edge' and give you a negative experience with your phone.
[Galaxy S I9000 Android Development] Silentbob999:
Deep idle let's the phone in deepsleep while listening to music. Without it it would runn at 100-200. If you dont listen to music that doesnt change anything and it's just one more module loaded.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
You may read this:

http://xdaforums.com/showpost.php?p=23542743&postcount=1814
[Galaxy S I9000 Android Development] adytum:
I just want to say that I have used deep idle constantly ever since semaphore ics, and never at all had issues with it. However, with other kernels I've experienced a few issues because of it. I.e did an init d bluetooth kill script often cause severe wakelocks.

But no issues with Semaphore!

Sent from horseback.
[Galaxy S I9000 Android Development] sasukepl:
we see semaphore for new bulid cm 10 10.03

i9000
[Galaxy S I9000 Android Development] Neel.I:
Hey Stratosk !

Can't thank you enough for all your efforts .. You've made my awesome phone,even more better :)

Heres the thing,with deep idle,while using Wifi,if I keep a download in background,the phone doesn't wake,once the screen locks.

Faced a similar issue on ICS as well.

Its only when I lock my phone,with Wifi on,that I get this problem.Other than that,Deep Idle works fine for me.
[Galaxy S I9000 Android Development] Kees-Jan:
goto settings -> Wifi -> Advanced -> set sleep policy :good:
[Galaxy S I9000 Android Development] RlndVt:
I have the identical problem, on CM10.

Also, might have been explained but I missed it, why is the Huge Mem (403MB) not in the non s version? DerTeufel seems to have included it in his...

Your kernel is much better though Stratosk <3
[Galaxy S I9000 Android Development] stratosk:
I'm on CM10 (build 20120926). Logcat works just fine.

About the hugemem. I didn't understand. If you need hugemem patched kernel flash the 's' version.
[Galaxy S I9000 Android Development] Neel.I:
I see a "keep Wifi on during sleep" option,which is set to never

is that the one you are talking about ?
[Galaxy S I9000 Android Development] mnazim:
Devil kernel has combined both the normal and "s" versions by coupling the HugeMEM libs along with the kernel itself. Thats how all the memory versions are achieved from a single kernel zip. Semaphore does not bundle the lib files itself. ;)
[Galaxy S I9000 Android Development] willthrom:
I tried to use the logcat form the nighly CM10 for Galaxy S but that logcat is build with a dependency which is not in my system :(

root@android:/system/bin # logcat

logcat

reloc_library[1306]: 2647 cannot locate 'android_log_setColoredOutput'...

CANNOT LINK EXECUTABLE

I will try to find another logcat but stratosk, Could you confirm me that in your /dev/log there is a file called main?

Thank you.
[Galaxy S I9000 Android Development] Kees-Jan:
Yes, that's the one! set that to "Always". It's then configured as "Keep WiFi always on during sleep". :good:

If it is "Never", then it's configured as "Keep WiFi never on during sleep".

and sleep is as screen goes dark after an amount of time.

This is exactly the problem you describe ;)
[Galaxy S I9000 Android Development] RlndVt:
I thought the s-version was for not for CM10:

Thanks any way, will flash the s version :)

Also i'm on CM10 10-03.
[Galaxy S I9000 Android Development] SAINI99:
is this working with helly bean partition layout which version will i flash i m on latest helly bean 07/10
[Galaxy S I9000 Android Development] Neel.I:
Got it .. thanks

will give it a try
[Galaxy S I9000 Android Development] stratosk:
I guess you mean /dev/log/main. Yes, it's there once the logger module is loaded correctly.

By default, no. The 's' version is not for CM10. You have to patch the ROM with the hugemem patch.

As manzim mentioned Semaphore does not come with the libs bundled in the kernel. You have to manually patch the ROM.
[Galaxy S I9000 Android Development] willthrom:
Yet I meant /dev/log (I tried to edit it ontime but I had to wait 5min :P)

Still with the module loaded the file main is not there... very odd.

Is there any way to debug the module logger to check why it is not creating the file?

thank you
[Galaxy S I9000 Android Development] zxseven:
can use ClockworkMod Recovery to flash it?
[Galaxy S I9000 Android Development] T0rchlight:
Use CWM if .zip

Use Odin if .tar
[Galaxy S I9000 Android Development] SAINI99:
is this working with helly bean partition layout which version will i flash i m on latest helly bean 07/10

is my language diff from urs for understading

no answer .....
[Galaxy S I9000 Android Development] dark_knight35:
The latest version of this kernel.
[Galaxy S I9000 Android Development] RlndVt:
Odd, I flashed the s version before reading this post and i still had the S42enable_bigmem thingy in init.d loaded. After the reboot I had 403MB. I cannot remember ever manually patching anything. 720p recording/playing in gallery is broken though (as is to be expected right? or does this patch fix this?)

As a side note, I also noticed that using MX Player (w/ SW decoding) I could play 720p.

As far as logcat goes, after adding S30enable_logger to init.d it works properly.
[Galaxy S I9000 Android Development] willthrom:
Hi stratosk,

If I disable the logger (semaphore manager or deleting /data/local/logger.ko the folder /dev/log is not create. But If I load the module, the folder is created and 3 files (events, radio and system)... quite strange why the main file/descriptor is not there...
[Galaxy S I9000 Android Development] uhm:
Hello, I loaded slimbean 2.5 rom (that uses semaphore kernel) on my i897(Captivate). After installing it successfully, the screen becomes predominantly blue after the boot animation...almost as if all the screen colors are mixed with dark blue. It is like having a dark blue back light instead of white.

I read somewhere that this problem is related to using Nexus S Framebuffer. It was stated that for some devices, the color calibration data is invalid and that causes this blue color problem. I don't know how far it is true but I'm just stating it here thinking that it might be useful information.

Hope this issue will be fixed soon. Or if there is a work around, please let me know. It would be greatly appreciated.

Thanks a lot in advance!
[Galaxy S I9000 Android Development] prbassplayer:
Why you posting on i9000 thread? Use Slim 2.6
[Galaxy S I9000 Android Development] stratosk:
Yes, this is weird. I will investigate it when I will find some time.
[Galaxy S I9000 Android Development] stratosk:
New version 2.3.0

- updated base to the latest linux 3.0.45

- changed charging boot logo to match open source charger