yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
I'm not sure why NStools shows 100 as liveoc value. Please check this in terminal emulator:

cat /sys/devices/virtual/misc/liveoc

Also clear NStool settings from recovery and don't use them. It may cause instabilities with Semaphore.

I'm sorry, I guess I forgot to check this. Noted.

Please try to reduce liveoc to 1140. LiveOC is different from normal OC. LiveOC can't be stable to such high values.
[Galaxy S I9000 Android Development] willthrom:
Hi,

Stratosk, In EliteRom V13v3 in the /system/etc/inid.d/s01 file there is a "AWESOME" line:

rm /dev/log/main

After removing that abomination... everything works again. :)
[Galaxy S I9000 Android Development] stratosk:
Interesting way to stop logging. :confused:

I'm not sure if the actual logging mechanism also stops...

Anyway, nice finding. :)
[Galaxy S I9000 Android Development] duffymm:
@stratosk :

any interesting update from Crespo 4.1.2 AOSP tree for us ?

Thx a lot for the amazing 2.3.0 kernel !
[Galaxy S I9000 Android Development] stratosk:
Thanks.

I'm sorry, I didn't check. :)
[Galaxy S I9000 Android Development] Giap:
Thank you for your reply. I checked terminal emulator and the LiveOC was really 100 and not 114. Then I cleared NStool setings as you suggested. The phone rebooted 4 times (I spent 15 minutes without being able to use the phone). Finally, I could open Semaphore manager and the LiveOC value was 114: checked again terminal emulator and LiveOC is still 100. Thus it seems that Sema manager is not able to configure the overIocking. I did not touch anymore NStool, following your recommandation. What can I do? Also can you answer to my question about the optimal combination overclocking/scheduler. Thank you
[Galaxy S I9000 Android Development] stratosk:
Please try to clear data from Semaphore Manager (Manage Apps->All->Semaphore Manager->Clear data). Then open app and reapply your settings.

Also, make sure that Semaphore Manager has root access.
[Galaxy S I9000 Android Development] Giap:
Thank you Stratos, now I have got overlocking to 114. Maybe my question on overlocking/scheduler is stupid because you did not answer. Actually, I have read the tutorial on configuration of governor, scheduler etc, but I'm a little confused about the optimal combination for improving performance by overlocking and sparing battery with semaphore. I kept ondemand as governor, but I cannot choice the optimal scheduler. Sorry for taking your time
[Galaxy S I9000 Android Development] stratosk:
Sorry, I missed your question.

Optimal configuration is this that fit your needs.

I use oc 114, ondemand with smooth ui, SIO or CFQ.

Lately I also test interactive governor.

But, don't be afraid to experiment and find the best for you. :)
[Galaxy S I9000 Android Development] superkoal:
Thanks for sharing your settings with us.

I am currently using interactive governor and No-op scheduler (No OC) too, as Nova Launcher works quite a bit faster and overall scrolling is smoother than with ondemand, CFQ or SIO on 1050 MHz (my settings before).

Also Battery life is not really noticable shorter for my daily usage pattern.
[Galaxy S I9000 Android Development] zxseven:
how to make 720p video record work in Semaphore2.3 390MB RAM

any patch?
[Galaxy S I9000 Android Development] benbezalel:
720p break only if you using Bigmem (402mb)
[Galaxy S I9000 Android Development] zxseven:
but if now using 390mb, it break,, im using smephore 2.30 not 2.30s
[Galaxy S I9000 Android Development] erpurohit:
you can patch it with the one from kashper_h
[Galaxy S I9000 Android Development] jv.batista:
Will 2.3.0s work with the m2 build?
[Galaxy S I9000 Android Development] erpurohit:
it should..
[Galaxy S I9000 Android Development] Brignoud:
Please, what is M2?
[Galaxy S I9000 Android Development] jv.batista:
cm-10-20121011-EXPERIMENTAL-galaxysmtd-M2. Its the latest build. I asked because I misunderstood one thing on the change log...
[Galaxy S I9000 Android Development] GretaLewd:
People on Helly Bean thread have been reporting problems with HellyBean M2-based ROM. They think it is kernel related. Some have tried Semaphore kernel instead - but still not working (WiFi bust).

This may be Helly Bean issue...but may be kernel issue - so I thought I should point it out.
[Galaxy S I9000 Android Development] Slated:
2.3.0 works fine with X-Bean 2.0.

--

Sent from my X-Bean 2.0 SGS with Tapatalk 2
[Galaxy S I9000 Android Development] ulysse75:
please someone can point me to understand what's the function of the modules in the semaphore app?

Above all TUN and config.cz

It's usefull to put they on?

Thanks
[Galaxy S I9000 Android Development] HenriFred:
Have a look there : http://www.semaphore.gr/how-to/use-modules-and-scripts
[Galaxy S I9000 Android Development] podpowerbest:
stratos great job! you are the best!
[Galaxy S I9000 Android Development] Phandroid:
Coming from 2.1.2 I flashed 2.3.0 and my phone was stuck in a boot loop. I reflashed 2.1.2 with Odin (thanks for the tar files :p) and everything went back to normal. I thought the file might have been broken during download or what not, so I redownloaded 2.3.0, this time via PC. Just flashed the kernel and I'm stuck in a boot loop again. Will re-ODIN my old one and keep it for better or worse...

Just letting you know. Btw I'm on official AOKP Build 3.
[Galaxy S I9000 Android Development] superkoal:
Different partition layout...
[Galaxy S I9000 Android Development] Slated:
The tun (tunnel) module is for using OpenVPN tunnels, typically to connect securely to your employer's network, an anonymity/privacy service, or your home server acting as a proxy.

config.gz is a compressed text (virtual) file containing the configuration used to build the currently running kennel, which is useful for those who want to customise it.

--

Sent from my X-Bean 2.0 SGS with Tapatalk 2
[Galaxy S I9000 Android Development] duffymm:
@ stratosk

dunno if it can be usefull or not, but there are also new binaries for 4.1.2 - Crespo

https://developers.google.com/android/nexus/drivers

thx a lot for your amazing kernel ! 2.3 is uber !
[Galaxy S I9000 Android Development] ulysse75:
Thanks! so in normale use i can leave they off !?
[Galaxy S I9000 Android Development] Giap:
Huge instability and massive battery drain after overclocking to 114

After properly overclocking liveOC to 114 by semaphore manager, yesteraday nigly the phone rebooted and eventually went off since the battery emptied (from 100 to 7% in 6 h).

The phone continued rebooting since I wiped Semaphore manager setting from recovery. Then restarted correctly and I had to reapply my setting. Clearly I put OC 100. What could be happened?

My configuration was:

OC 114

Ondemand, io_is_busy, smooth UI, Deep Idle enabled

CFQ, Touchwake enabled,

Logger yes

Radio FM Yes

SGS I9000

Slimbean 2.6

Semaphore kernel 2.3.0s
[Galaxy S I9000 Android Development] Phandroid:
Again? Since when? How did I miss that?
[Galaxy S I9000 Android Development] Fenvarien:
Semaphore jb2.3.0 runs great with CM10-M2 build. Including bigmem option and OC to 114.
[Galaxy S I9000 Android Development] thETImo:
Between AOKP3 and AOKP4. :cowboy:

http://aokp.co/index.php/releases
[Galaxy S I9000 Android Development] Starsream88:
Maybe you can try to undervolt max cpu frequency by 25mV (use NSTOOL for that, semaphore manager dont support UV yet).

My settings are : 120%OC, SIO, Bigmem, Ondemand, 512K SD read ahead. And my phone is just fast, smooth and stable ! :good:
[Galaxy S I9000 Android Development] sucre213:
hey guys

there is an option in kernel manager that lock min freq to 100MHZ

i was wondering whether it will increase/decrease the battery life
[Galaxy S I9000 Android Development] jv.batista:
yes, there is...

@stratosk

http://xdaforums.com/showpost.php?p=32662692&postcount=9187

apparently the missing option is caused by the kernel...
[Galaxy S I9000 Android Development] sucre213:
I don't think you understand what i've said:o

btw how come you guys can oc to 1200MHZ?

everytime i try to change oc settings my phone will be dead soon or got a reboot

semaphore 2.3.0 here with latest cm m2:confused:
[Galaxy S I9000 Android Development] Midomad:
It will increase battery a little bit but give you some lags when u unlock the screen

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] Giap:
Thank you, but the problem seems bigger: after having resetting Semaphore with OC 100, I still had a huge battery drain (50% in 4 h with very little activity: it seems that system manager wakes up the phone). Before overclocking, yesterday I had 2-3 % battery decrease/hour in similar conditions. Therefore I'm considering to reflash the kernel. Maybe Stratos has an advice about the issue?
[Galaxy S I9000 Android Development] stratosk:
This is because CM team decided to implement vibration sysfs in different path than Mialwe did. Till now all kernel devs followed Mialwe's approach. At the present you may use Semaphore Manager to change vibration level.

120 liveoc is not stable in every phone.

Also try to clear NSTools settings from recovery.

I'm afraid this is not true. lock min frequency will only protect you for increasing min scaling frequency from other applications or from ROM's settings. It will not give you any lags.

I don't think that reflashing kernel will help. Please try to use Betterbatterystats application to find the reason of battery drain.
[Galaxy S I9000 Android Development] jv.batista:
thanks for the reply. I'm currently trying to build a cm9 rom 'cause the cm10 for me is having some trouble with the sms...
[Galaxy S I9000 Android Development] Ramanjit81:
Possible cause for instability at Live OC 120

I might have inadvertently come across a bug.

May be others here can confirm..

I have Hellybean rom 07102012 and semaphore kernel 2.3 on Galaxy S i91000.

I have not installed NS tools.

When I install the semaphore manager and open it first time and grant SU permissions it reads the system settings.

Once it has done that the deep idle is disable by default. I left it like that. I only changed the Live OC to 120, enables semphore auto brightness and fast charge support.

I installed the CPU spy app and left the phone. The screen imed out after 2 minutes. I left the phone in that state for a further 15 minutes.

Then I woke the phone up opened the CPU spy app and it showed the phone had been in deep sleep state- now I do not know if this is the same as deep idle or not, but the battery consumption dropped quite a bit over thiss period.

The source of instability

I opened Semaphore manager and enabled Deep idle and deep idle stats. I left the screen time out, aften 10 minutes the phone went into sleep of death.

I pulled the battery and the phone boot looped, regenerated the dalvik.

So, I think the cause for the instability is enabling deep idle with any value for Live Oc between 100 and 120.

I've disabled the deep idle on semaphore and the phone is still rock solid stable and fast with Live oc 120 , semaphore auto brightness driver, fast charge, ondemand, No-op, big mem, read ahead 512 and the kernels own voltages( I didn't change any voltages).

Thanks for the lovely kernel.

Please excuse me if I'm re-iterating something already pointed out.

Just by the by, I've had the same instability issue with devil 3.1.6 kernel when deep idle was enabled with or without Live oc.

So it may something in the ROM, but I'm happy with my currectn setup.
[Galaxy S I9000 Android Development] stratosk:
@Ramanjit81

I just want to say that deep idle usually cause instabilities. I don't recommend the use of it, unless you listen to many hours of music.

Deep idle is different from deep sleep.

Also, OC to high values > 114 also may cause instabilities on many phones.

So, I guess combining them (OC and deep idle) is more risky
[Galaxy S I9000 Android Development] Ramanjit81:
Does HD video work with hugemem + semaphore 2.3s
[Galaxy S I9000 Android Development] DerBobo:
I think hugemem will always berak 720p

send from my SGS with latest Slim Bean @ latest Semaphore Kernel
[Galaxy S I9000 Android Development] Ramanjit81:
Thanks a lot for the prompt response Stratosk.

While you'on could you kindly tell me if I were to enable live oc down to 110, then enable deep Idle with semaphore manager , will the kernel's default voltages work just as well, or will I have to install NS tools and then get into configuring voltages.

I've a spent the last one week testing the various configs, and just couldn't hack the deep idle enabled with user customised voltages on Devil kernel 3.1.6.

If I have to do the same with semaphore 2.3 I'll give it a pass.

Also, is the deep idle more likely to cause instability with hugemem enabled?

One other thing a bit off topic, what do you have to say about the following two patches. I've used them successfully on 2.2. I wonder if they'll help on JB with semaphore as well.

http://xdaforums.com/showpost.php?p=18703418&postcount=5023 - The V6 supercharger script by Zepplinrox

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

Thanks for your time and patience.
[Galaxy S I9000 Android Development] stratosk:
Bigmem option will break 720p.

720p will work on a hugemem patched ROM if you will not enable bigmem.

OC and deep idle are 2 different things.

Semaphore adjust voltages to L0 and L1 frequencies (stock 1000MHz and 800MHz), in different levels of oc value. So, when you apply LiveOC value voltages are automatically changed.

You have to find a way to adjust voltages AFTER applying LiveOC value (AFAIK there is no safe way to do this unless you use an init script to apply OC and voltages).

Deep idle is also totally independent with hugemem.

Finally, about the posts. I've never used these scripts, so I can't express any opinion. :)
[Galaxy S I9000 Android Development] nitramcek:
I'm on cm10 and with semaphore. I was always on stock until few days. So now if i wanna update cm10 I do it like before on stock, or I have to do something else before flash? Just read on cm10 forum that something should be deleted in CWM if upgrade with Semaphore kernel. True or not?
[Galaxy S I9000 Android Development] goranbm:
I had strange situation today... around 4 PM today i had around 85% battery. Then I had 4 minutes long call. After the call was finished i locsked my device and put it away. 30 min later I had Missed call but i didn't touch my phone. Around 6PM i tried to unlock my phone and i see it is turned off. I could not turn it on. So I put it on charging and i turn phone on and i see 1% of battery. How ? You can see screenshot

Is this because of the notification light ?? I am on nightly 10.10. with 2.3.0 kernel .

Sent from Jelly Bean galaxy s :)
[Galaxy S I9000 Android Development] Giap:
Hi Stratos,

I acknowledge that this morning I was rather scared in seeing that the battery emptied in spite of airplane mode, because I use my phone also for work. I could not check betterbatterystat, that I currently use, because the battery was empty and the phone continously rebooting. However, this evenins things are coming regular and I hope that it was only an accident. The explanation may come from the Ramanjit81's post and your reply: overclocking ans enabling deep idle may cause instability. I had both (OC=114 and deep idle) and my phone become mad. I will forward your opinion to Slimbean thread, it may be useful to many users.

I also would like tell you that I appreciate very much your attention and follow up of your correspondents, users and SGS friends.
[Galaxy S I9000 Android Development] purgalm:
Did anyone manage to mount anything in cifs manager running semaphore kernel? I've got some problems with my lan share and started wondering whether this is a matter of cifs.ko that comes with this kernel...?
[Galaxy S I9000 Android Development] tobiasth:
Did you enable the cifs modul in semaphore manager?

via SGS running SlimBean
[Galaxy S I9000 Android Development] ryuzaki_eru:
Can anyone tell me the meaning of all menu voice in Semaphore Manager (like smooth ui, downmax ecc)? Thank you.
[Galaxy S I9000 Android Development] purgalm:
Now I did... oh stupid me... Thanks a lot! :)
[Galaxy S I9000 Android Development] JohnstonF:
Can someone tell what the option io_is_busy is supposed to do? As in functions, pro's and cons.

Much appreciated
[Galaxy S I9000 Android Development] Kingo64:
Somebody really needs to write up some documentation on all of the options in the Semaphore kernel demonstration and also include this information in the Semaphore Manager.

How is a user supposed to know what Touch Wake, Deep Idle or WiFi PM FAST is without reading all 212 pages of this thread?
[Galaxy S I9000 Android Development] alb3rtt:
There is one, on the semaphore website. At least read the op before complaining man

Sent From My BEAST Galaxy S Running CM10 by Pawitp
[Galaxy S I9000 Android Development] Andii S.:
there is no netfilter switch in the sema app.

latest slim bean with sema 2.3.0s

Send from Pegasus Galaxy by a Semaphore powered Slim device
[Galaxy S I9000 Android Development] nitramcek:
Can someone help me with this?
[Galaxy S I9000 Android Development] Taomyn:
This is what I do:

Download new CM10 zip, but don't go into recovery just yet

Make sure you have a copy of zips for Semaphore and the latest GApps

Reboot into recovery

Do a backup

Install CM10 then before restarting, install Semaphore & GApps then clear the cache and dalvik cache

Restart phone

Hasn't failed me yet and I haven't lost anything.
[Galaxy S I9000 Android Development] ramas123:
Install cm10

Install Semaphore

Reboot

P.S. no need to reflash gaaps and to wipe cash and dalvik cash.
[Galaxy S I9000 Android Development] nitramcek:
Thanks to both of you. So there is no need to do this ...

But... Just before you flash, go to the Semaphore recovery and wipe NSTools and Kernel defaults (the last two options at the very bottom). Can't remember what they are called.

Then you flash CM10.

After reboot, go ahead and reboot into recovery again and flash Semaphore. Choose reboot recovery, then wipe those two options again as I mentioned above.

Reboot system. Done

I read that on CM10 thread and it worried me a little bit how to properly flash.
[Galaxy S I9000 Android Development] jugster:
+1

Has worked everytime, all well.

Signature? Signature!
[Galaxy S I9000 Android Development] Taomyn:
Yes you do. GApps are not included with CM10 (or any other ROM as it's against Google's conditions) so they need to be installed separately: http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps

Wiping the caches is good practice to make sure they're properly rebuilt with the new version.
[Galaxy S I9000 Android Development] stbenz:
No, you don't ;)

It's true that CM doesn't ship with GApps, but GApps installs a script, wich is run by the CM update zip. That script backs up all GApps before flashing CM and copies them back after installation finished.
[Galaxy S I9000 Android Development] nitramcek:
So the conclusion is, that flashing is the same no matter if stock or Semaphore kernel.

And yes, there is no need for flashing Gapps.
[Galaxy S I9000 Android Development] Taomyn:
It may be doing that but it never worked for me - I've always been left without the apps on my SGS, plus I wouldn't trust it to be able to copy everything anyway as there are a gazillion versions of GApps, mostly all newer and imho better than that linked by CyanogenMod. For the sake of an extra 10 seconds to install it's hardly worth not doing.
[Galaxy S I9000 Android Development] lmulli:
CM10 had always backed up my GAPPS and I never flash Gapps when I install each nightly and never had any problems thus far. Other roms, such as CNA, do require you do re-install Gapps each time that you update your rom, but CM10 doesn't because of the afore mentioned script.

Nor do I wipe and cache's - no reason to whatsoever.
[Galaxy S I9000 Android Development] Kees-Jan:
thought this was Semaphore Kernel tread?! :confused:
[Galaxy S I9000 Android Development] Ciprilik:
Hi all! I want to flash semaphore 2.3.0 (normal version because I am on Cm10 latest) but I have a couple of questions before I do this:

1. Can I go back to CM kernel if I flash cm10 from semaphore recovery without breaking the rom in any way?

2. Is 720p working on Cm10 with this kernel?

3. What is the safe OC for our phone? I mean to be stable and not overheat too much.

Thank you in advance!
[Galaxy S I9000 Android Development] ChmT:
Is there possibility to increase network speed over wifi? When I watch some video on phone from my desktop pc over wifi a got some lag sometimes with hd movies. Same video from sd card on mobile works fine.
[Galaxy S I9000 Android Development] pacc:
1. yes

2. yes

3. 1140
[Galaxy S I9000 Android Development] Kees-Jan:
1. Yes, just flash your CM ROM again

2. Yes, but don't use the 2.3.0s version nor BigMem

3. that's depending on chip, some CPU-chips can be OC'ed higher then other, settings for your chip can be different then for my chip; you should just try what setting is best fro your chip without overheating and freezing the system (yeah, yeah I know it's reading odd, but I mean "no heat" and "inresponsive":p)
[Galaxy S I9000 Android Development] Ciprilik:
Ty guys. Going to recovery :P
[Galaxy S I9000 Android Development] stratosk:
I don't know. What is your current download speed?

Please note that downloading from your PC and being in the same WiFi network, you split the bandwidth of your router in 2.
[Galaxy S I9000 Android Development] ChmT:
Im talking about transfer files from pc hard disk to phone over wifi. Not talking about internet.
[Galaxy S I9000 Android Development] giokspy:
No support tethering this kernel?
[Galaxy S I9000 Android Development] stratosk:
Yes, I understood that.

I meant that if your PC connects to network through WiFi, it uses half of Wifi channel to upload the file to the router/hub and your phone uses the other half to download it. Or maybe I'm wrong on this...

Yes, it does support.
[Galaxy S I9000 Android Development] ChmT:
No. My pc is connected with cable to router.
[Galaxy S I9000 Android Development] giokspy:
not working on me. Must be enable something on semaphore manager?
[Galaxy S I9000 Android Development] tobiasth:
hey stratosk!

i just want to ask you, if there is a "known" problem with the recovery and semaphore.

it happens from time to time, that, when i clear dalvik cache, the recovery is gone after rebooting and i have to reflash (another) kernel via odin to get it working again. i always flash devil over and afterwards semaphore again ... there is no other way to fix this (or i don't know how).

plz, could you investigate a look in this issue ... cause i know some other people with this problem too.

i think its a kernel issue ....

many many thanks!
[Galaxy S I9000 Android Development] stratosk:
There is not much that I can do. If you want try to measure your download speed from your phone to check if it's OK.

Works on me. Netfilter is compiled into the kernel, you don't have to enable anything (if you are in latests versions).

Do you mean that you can't access recovery and you are able to boot in normal mode?
[Galaxy S I9000 Android Development] saszseb:
Yes, he meant so. It happened this issue using Devil, too. Therefore I never clear dalvik and cache in recovery.
[Galaxy S I9000 Android Development] tobiasth:
No, i can't boot normaly when i lost my cwm, i get a bootloop too, only download mode is working.

after flashing devil, all runs normal again. when i flash semaphore over devil, all is booting normal again ...
[Galaxy S I9000 Android Development] jugster:
That does not negate the fact that the post I +1 was completely correct.

Signature? Signature!
[Galaxy S I9000 Android Development] stratosk:
Yes, this kind of bootloops were discussed in a thread that I was trying to find the issue, but I didn't manage to find a solution.
[Galaxy S I9000 Android Development] Kees-Jan:
you're right! :D

I only took the last post that was about the GApps discussion, which, I thought, was in no need to keep it in the Semaphore Kernel thread :angel:

but everything seems to be "en route" now :highfive:
[Galaxy S I9000 Android Development] shaarky:
Since it happened to me too, I'm flashing Semaphore always twice without reboot - so far no boot loop anymore.