yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kathees:
Hi,

I just flashed latest (2.1.0) over my 2.0.6 version. Change-log says

- removed Semaphore Script Manager app

But after restart I can see the application still. Should I uninstall that first before install stratosk version from Google Play? Or is it same? Will I be able to control everything using this old application? (Guess I got from 2.0.6)

BTW I can't normally uninstall it since it's a system app! I can use TitaniumBackup? Is it correct procedure?

Edit:

Ok Problem - I cannot uninstall that. My titanium backup hangs! Any idea why?

Another thing to clear:

I remember in the init.d directory there is 2 files called 00Banner something and another one normally. (If I don't enable anything from Semaphore these are the only 2). Usually I clear cashe,dalvik, init.d directory and NS tools settings. Then flash CM10 and then Semaphore. So I guess those 2 files are from CM10.

Today since I flashed Semaphore only (Same steps as before except no CM10 flash.) I cannot see those 2 files. My phone works fine though. Any idea why those files are there and if there is any affect?

Thanks!
[Galaxy S I9000 Android Development] matesc:
Hey stratosk, my favorite developer!

I really want to say thank you, for your hard work on Semaphore kernel.

I appreciate, that you continue this work. It is a shame, that Google doesn't accept paid apps from Greece.

Anyway, I've just installed Sem 2.1.0.s on latest Slim Bean, everything is working perfectly, (I really like your new app :good: and I have also deleted the old Semaphore Script Manager app using TB).

Some questions-

a) What is the difference between the ondemand scheduler in Semaphore kernel and the stock CM10's one? Same sampling down factor, sampling rate, up threshold?

b) do you recommend to set io_is_busy to 1?

c) you set always the default SD card read ahead to 128Kb. CM10 stock is 1024Kb? What is better, or what would you recommend?

Thank you in advance and I'll keep my fingers crossed.

OT: in a week i will go for a holiday on one of the islands in Cyclades- i'm really looking forward to it!

There you go: 09T1340636815874U :D
[Galaxy S I9000 Android Development] Jens1969:
The old Script Manager App and the new Semaphore Manager can almost do the same right now. At least I couldn't spot any huge difference. (Please correct me, if that's not correct). I'd say, in the long run, the new app will get much more development time and therefore will be superior soon. :)

If the old app is installed, you have to a) reflash nightly or b) remove app manually. With TB I did it in two step: 1. convert the app to user app and 2. uninstall app.

Edit: see one post down: just uninstall the app. Don't now why I did it the other way, might be some leftover bad habbit... ;)
[Galaxy S I9000 Android Development] yaatzek:
Jens u don't have to convert it, tibu can uninstall system apps.
[Galaxy S I9000 Android Development] kathees:
Thanks for the information buddy. I cannot uninstall that old App still. I tried like you, convert to UserApp and it just get force close. When I direct uninstall it hangs!

Thanks but for some reason I cannot uninstall this. I have uninstalled several other system apps like Apollo etc...
[Galaxy S I9000 Android Development] matesc:
sorry for wrong information: With "i just unistalled the old app" I meant - I've just used TB to unistall it :)
[Galaxy S I9000 Android Development] pbecks1963:
is there an error in the changelog (jb-kernel)? Shouldn't Patched roms/sim bean have 2.1.0S ?

2.1.0

- 378MB - 390MB

For Slim Bean ROM or patched ROMs with hugemem configuration

2.1.0

- 391MB - 404MB
[Galaxy S I9000 Android Development] yaatzek:
Yep you're right, but we all know it even without "s" :D
[Galaxy S I9000 Android Development] pbecks1963:
I am on C-rom bean (1.7.0) and the stock kernel is semaphore 2.0.6 (no S in the description). Still it has a huge mem.

What semaphore should i flash 2.1.0 or 2.1.0S ?

ps: should i wipe nstools/semaphore settings before flashing latest kernel?
[Galaxy S I9000 Android Development] superkoal:
Why don't you guys use your file manager, go to system/app and delete the apk? ;)
[Galaxy S I9000 Android Development] keuda:
Great work as always stratosk!!! Thank you a ton!!!

Enviado desde mi GT-I9000 usando Tapatalk 2
[Galaxy S I9000 Android Development] Funnnny:
Clean init.d directory, reflash the kernel and reboot.

This should work
[Galaxy S I9000 Android Development] Bonta768:
Go back to the Devil... er... ;)

Semaphore 2.0.0* kernel will only work on pawitp's CM10 build.

Devil kernel will only work on DerTufel(spel) builds, and most of the others.

The official CM10 build tree (pawitp's) has changed the flash partitioning, and the other builds are (mostly?) choosing not to move to that yet.
[Galaxy S I9000 Android Development] slaphead20:
yay, nice one stratosk , got my recovery back testing slim with .tar, :thumbup::thumbup::thumbup::D
[Galaxy S I9000 Android Development] Neodymium:
Which roms does this supoort?
[Galaxy S I9000 Android Development] alcurtis93:
All jelly bean roms
[Galaxy S I9000 Android Development] malcho:
Only cm10 right now.It use same partition layout as pawitp kernel.
[Galaxy S I9000 Android Development] cink40:
Also aokp port by nasif
[Galaxy S I9000 Android Development] matt73300:
Hey stratosk, I compiled last kernel with last Linaro toolchain (2012-0720) and it solved a random reboot bug for me.

You should upgrade toolchain for next build :)

Have a nice vacation, me too I finish work Thuesday and then I go to the sea ! :D
[Galaxy S I9000 Android Development] Bonta768:
Nope. Try looking just 3 posts above yours.
[Galaxy S I9000 Android Development] habylab:
Sema on JB! Good work, as always.

Sent from my Galaxy S running Slim ICS 4.2 and Devil kernel from my XDA Premium app.
[Galaxy S I9000 Android Development] sigarocubano:
How may I obtain 398 MB of ram? Now I have 385 MB !
[Galaxy S I9000 Android Development] cspiby:
Has this got the linaro optimisations in?
[Galaxy S I9000 Android Development] stratosk:
You can't with this version. Changes to rom are also required. There will be a version in the future.

Yes, it's compiled with linaro with O3 optimizations.
[Galaxy S I9000 Android Development] groksteady:
Stratosk -- I hope you had a great vacation. Seems like you're working behind the scenes, though. Your name and Semaphore show up in the new Slim JB ...

I am in no way trying to rush you, but I'm looking forward to your next release. Slim JB 1 is pretty awesome, but as opposed to alpha 5, it breaks FM radio. I hope that module carries over... I tried creating a /res/scripts folder and installing HM.Carbide's manager app. It opened well st first but on reboot can't get it back.

Looking forward to the big power combo to return in JB....

Cheers

sent from a telephonic device
[Galaxy S I9000 Android Development] Maddmatt:
Searched through this thread and I see early versions don't work with Slim JB. Just checking if anything changed here, do the latest versions of Semaphore and Slim JB work together yet?

Appreciate all your work on this kernel :)

Edit:

Nevermind the stuff I just removed, wrong thread.
[Galaxy S I9000 Android Development] deedeeceleb:
2.0.0a2 is perfectly working with slim bean 1.0

Gesendet von meinem GT-I9000
[Galaxy S I9000 Android Development] beluthius:
I second that. Smooth, stable fast. No problems. Simply Semaphore ;)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] biccys:
I third it! As always, Sema kicks all ass in it's way!
[Galaxy S I9000 Android Development] manjee:
Same here, Semaphore is the only kernel that makes JB useable on our aging SGS :cowboy:

Greetz
[Galaxy S I9000 Android Development] florum:
why phone it's getting so hot? cause of kernel?

i can have car dock working on cm7,9,10 just with your magic kernel.

thanks!
[Galaxy S I9000 Android Development] alexovy:
thank you and congrats stratosk, for the new kernel.

- everything runs smooth and fast;

- the ANTUTU score is ~100 points better then 2.0.6s.
[Galaxy S I9000 Android Development] dilerus:
I've just flashed the latest nightly and new Semaphore 2.1.0, but I have no Semaphore app. What could be the problem? I've reflashed Semaphore and there is no change.
[Galaxy S I9000 Android Development] Mindfield21:
Read the changelog
[Galaxy S I9000 Android Development] dilerus:
So where can I change Semaphore settings?
[Galaxy S I9000 Android Development] jeozme:
Download app from market

Sent from my phone.
[Galaxy S I9000 Android Development] jv.batista:
Any change to the 'BLN module'?

I'm asking because in 2.0.6 it worked out of the box with the Elite JRO03U but with 2.1.0s it does not work...
[Galaxy S I9000 Android Development] grifovunque:
install bln from market and active it

;)
[Galaxy S I9000 Android Development] jv.batista:
that I already know...
[Galaxy S I9000 Android Development] grifovunque:
i have the same situation and it works after activate bln with apps from market
[Galaxy S I9000 Android Development] jv.batista:
sure, but I'll like to know if anything changed.

It's strange, to me, if it was working before and now not, assuming that there was no changes to it...
[Galaxy S I9000 Android Development] xtoudi:
I've just compiled fresh CM10 and after flashing it and flashing Semaphore 2.1.0 there is nothing but blank screen after big green andorid logo. Had to return to previous version of CM10 (compiled two days ago) ... in this version Semaphore 2.1.0 works perfectly.
[Galaxy S I9000 Android Development] DerTeufel1980:
There has been a change to hw composer. It needs a modified kernel. You could try to replace the hw composer in the new rom, with the old hw composer.
[Galaxy S I9000 Android Development] Rimmer1966:
The only custom Kernel you can use with the latest CM10 is MacKay 0.63. Some exynos3 libs changed in the latest nightly that require kernel changes that the latest Semaphore version doesn't include yet..
[Galaxy S I9000 Android Development] xtoudi:
thanks for info.
[Galaxy S I9000 Android Development] trailblazerz11:
Building still broken for me, output kernel gets stuck at boot splash, no recovery keys it seems. Thankfully JIG works.

Thanks for the update Strat :)

8VW18876TU726481Y
[Galaxy S I9000 Android Development] ulysse75:
edit
[Galaxy S I9000 Android Development] yaatzek:
It is and works very good. Just us app from GP.
[Galaxy S I9000 Android Development] stratosk:
Thanks so much! I really appreciate your help!

The reason is simple. I just found that they didn't work. Had no time to investigate since when. Maybe in the future.

Thanks for your comments and for you donation my friend!

a) I have implemented some tweaks in ondemand (sampling down momentum,smooth_ui, different values in tunables when screen off).

b) I think that io_is_busy causes a little bit more battery drain. io_is_busy causes ondemand to consider I/O operations as CPU demanding procedure and adds the I/O time to the total load time. I had it on in 2.0.6. But no major differences.

c) In most case I leave the default values untouched. Tweaks are optional. But I also use 1024 in my phone.

Thank you very much my friend! Really appreciate this.

Sorry about the issues. I wonder what's going on. Because I had 1-2 reports in 2.0.6 that the code didn't boot.
[Galaxy S I9000 Android Development] trailblazerz11:
No problem, support from dev for building is rare :)

I have been trying to isolate the issue but have gotten nowhere... and dunno how to debug at that early of boot stage.

I would assume something with ramdisk but i dunno..

Are you doing anything before running your new script? (seems very automated now)

I'll continue investigating.
[Galaxy S I9000 Android Development] matesc:
Slim bean + Sem 2.1.0.s = :good:

settings:

ondemand, cfq, read ahead 1024Kb, no smooth UI, no OC/ liveOC, no bigmem
[Galaxy S I9000 Android Development] stratosk:
If you want you may try this:

https://dl.dropbox.com/u/51987689/initramfs.tar.gz

It's a tar from my PC with jb_combo and jb_combo_v.

jb_combo_v does not include all the changes from 2.1.0 (though I don't think that this is problem).

Maybe it's file permissions issue. (git does not preserve the permissions).
[Galaxy S I9000 Android Development] trailblazerz11:
Yeah, I tried building for galaxy s too and same result :(

I'll check permissions tomorrow. Makes sense, I now doubt it's anything wrong with the remote code.

Thanks again :)
[Galaxy S I9000 Android Development] stratosk:
Try the tar file. Tar preserves permissions.
[Galaxy S I9000 Android Development] jv.batista:
there's my score

rom is on sig
[Galaxy S I9000 Android Development] s3icc0:
hey stratosk

i see the init.d folder is empty with 2.1.0 and app from market ... is that right? seems cm10 sees governor, sheduler and big mem .... but im not sure other functions works
[Galaxy S I9000 Android Development] stratosk:
Yes, this is normal. New semaphore app doesn't use init scripts.
[Galaxy S I9000 Android Development] Turtuga:
hello stratosk

new vsync updates has been implemented in your kernel??

thanks for your answer
[Galaxy S I9000 Android Development] Sw2rT1:
Hello Stratosk!

Please tell me why the CM settings and your program show different governor?

1 - CM settings - http://i.minus.com/icn1P5kdB3ae.png

2 - Your porgram - http://i.minus.com/i3I4kcZDiUbP4.png
[Galaxy S I9000 Android Development] stratosk:
No, not yet. But I will implement them.

Hello,

I think that you have to answer this question. :)

Most probably there is a race condition there. If you use the app don't use ROM's settings and the opposite.

Anyway this is your active governor:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Semaphore Manager app will apply the settings after the boot completes. If something else changes this after boot then app will still show your choice. You may select "Read System Settings" to get the current values.
[Galaxy S I9000 Android Development] stratosk:
Version 2.1.1

- Latest update for VSYNC from CM10

Please use it only if you know that your ROM supports this. Untested by me.
[Galaxy S I9000 Android Development] kraven001:
Latest version with VSYNC seems fine here ... using Mackay ROM 1.2.3.
[Galaxy S I9000 Android Development] adytum:
Hi, I'm sorry if this has been asked, but I couldn't find an answer in the thread.

Does the semaphore manager kill bluetooth somehow, for the phone to go top=off?

Sent from horseback.
[Galaxy S I9000 Android Development] stratosk:
No, I'm sorry for this. It will be implemented in next version.
[Galaxy S I9000 Android Development] xtoudi:
Works with latest CM10 with VSYNC.
[Galaxy S I9000 Android Development] Eleve11:
I updated to the latest CM10, let it boot up and so an. then I installed latest Semaphore (2.1.0) via CWM. Then when I restarted the phone the Semaphore logo shows as usual but then everything is black. Noting happens. Re-installed and tried again but with no success.

Thoughts??
[Galaxy S I9000 Android Development] stratosk:
Please read 5 posts above yours.
[Galaxy S I9000 Android Development] xtoudi:
Try Semaphore 2.1.1. It's all about this on this (and previous) page (and even previous post :)).
[Galaxy S I9000 Android Development] Eleve11:
Thanks! Was a bit stressed out. Will test!
[Galaxy S I9000 Android Development] alcurtis93:
Any chance of a 2.1.1s?
[Galaxy S I9000 Android Development] sgw99:
Boots fine with my own latest CM10-build. Thanks!
[Galaxy S I9000 Android Development] eejee:
Strange, I am convinced sensitivity increased with this setting. Now I'm on 2.1.0s and it feels different, more sluggish (but still fast enough) . Maybe differences between phone builds?

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] stratosk:
The sysfs path that the script writes to does not exist. You may try to run the scripts in terminal emulator and check the error.
[Galaxy S I9000 Android Development] sgw99:
I don't fully understand ( I don't get that "top ... off" description) ...

Does it mean that with Semaphore 2.1.x Bluetooth does not work?

Thanks, Stefan
[Galaxy S I9000 Android Development] alexovy:
Anybody knows if this is working with slim bean 2.4?
[Galaxy S I9000 Android Development] stratosk:
It means that bluetooth is not powered down (it's up and working). This is the reason that you don't have TOP=OFF in deep idle.
[Galaxy S I9000 Android Development] stratosk:
All 2.1.1 versions uploaded

Please make sure that your ROM includes VSYNC patch (CM10 - 20120917 or later)
[Galaxy S I9000 Android Development] eejee:
I can try (never done that before) Where can I find these scripts? They are not in your OP or on your site.

Verstuurd van mijn GT-P5100 met Tapatalk
[Galaxy S I9000 Android Development] Sw2rT1:
Today I installed CM from scratch.

I have never used performance settings in CM.

1) I installed CM10 from 14.09.12.

2) Installed Semaphore kernel v2.1.0

3) Set up the necessary parameters in Semaphore Manager v1.0.0

4) Reboot

5) And I found a discrepancy in governor in your app and CM10 performance-settings

Now, I followed your advice and once again hit the "Read System Settings" and found that the governor has changed from SmartassV2 to Ondemand. Why?

Again adjusted to SmartassV2, reboot, parabox...

1) Terminal Emulator - http://i.minus.com/iBmiYyQ55tivn.png

2) CM10 performance-settings - http://i.minus.com/ibaLO0A9dx3vfV.png

3) Your app - http://i.minus.com/ibzvT7tdDkYVwF.png
[Galaxy S I9000 Android Development] stratosk:
https://dl.dropbox.com/u/51987689/S78enable_touchscreen.tar
[Galaxy S I9000 Android Development] alexovy:
I don't see 2.1.1 on semaphore.gr. Where did you upload?

Al also, is there a version to work with slim bean 2.4?

Thank you!
[Galaxy S I9000 Android Development] stratosk:
Please check first post. I 'm uploading to semaphore.gr now.

As far as I know latest Slim build was before VSYNC patch. So, just remain on 2.1.0.
[Galaxy S I9000 Android Development] matesc:
He uploaded it to xda, see the first page!

No version for Slim, until vsync changes are implemented in Slim Bean, so you have to wait maybe for Slim 2.5 :) (as far as I understood it- correct me, if it is not true)
[Galaxy S I9000 Android Development] sgw99:
Thanks for the explanation. Will have a look tmrw when I use it w/ my car-audio ...
[Galaxy S I9000 Android Development] caper:
Do you have a slim bean ROM that includes VSYNC patch basead in CM10 - 20120917 or later ?

I think this version is not for SlimBean 2.4, maybe next versions. i´m i right ?

jmcdpereira
[Galaxy S I9000 Android Development] stratosk:
So, as I said CM settings are applied after Semaphore Manager settings. When you select "read system settings" the app reads the _current_ state for all options and overrides your settings. It's a good way to take all the system settings.

To check if it works, change governor to smartass from Semaphore manager and the run the command I mentioned.

You have to disable ROM's performance settings (I don't remember how you can do this on CM10)
[Galaxy S I9000 Android Development] eejee:
Thanks, another illusion down the drain ;)

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] caper:
This new version 2.1.1 dont have the Semapore Manager aplication ?

jmcdpereira
[Galaxy S I9000 Android Development] stratosk:
No problem. I also never noticed it (I never used them). But when I was testing Semaphore Manager I saw this issue. :)

2.1.1 also uploaded to www.semaphore.gr
[Galaxy S I9000 Android Development] stratosk:
Semaphore Manager will be deployed only through Google Play.
[Galaxy S I9000 Android Development] yahyoh:
https://play.google.com/store/apps/...?t=W251bGwsMSwxLDEsImNvbS5zZW1hcGhvcmUuc20iXQ..

:)
[Galaxy S I9000 Android Development] Sw2rT1:
After I changed the governor to smartassv2, i run the command that you mentioned. Terminal Emulator says current governor - smartassv2. Afret reboot, TE says, current governor - ondemand.. again...

I do not know how to do this too.

The question is, why in your application, there is an option to change the governor if it does not work after a reboot?
[Galaxy S I9000 Android Development] yahyoh:
did u waited until semaphore manager applied the setting ?? ( i mean did u saw semaphore manager get su permission ? )

and about performance setting on cm10 just don't tick apply after reboot :)
[Galaxy S I9000 Android Development] H-Body:
After a day of testing, i have to say that version 2.1.0 works great on 0914. Smooth as ever but with a better batterylife. I have 41% left after a full day of normal usage (almost 15 hours).

The only issue i got with your kernel is the non working auto brightness. I tried lots of methods, but non of them worked.

Nevertheless great work stratos! :)

P.S. I wrote a feature request in your app thread.
[Galaxy S I9000 Android Development] SnoopyDog:
I also had problems with Semaphore Auto Brightness+CM10 but after turning on auto brightness once in the normal phone settings under "Display", the Semaphore auto brightness was working again. Normally, these settings never affect each other but now there seems to be some kind of side effect due to ROM changes (?)
[Galaxy S I9000 Android Development] stratosk:
Let me try to explain this once more.

The only way to change governor in Linux/Android from user space is:

echo governor_name > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Whenever user or a program or a service run this command governor will change instantly.

Semaphore Manager uses a service which runs on boot complete event and applies your settings (and your selected governor). Other services (from ROM's settings) may do the same. The last service (or program) that will issue the above command will "win".

Obviously, ROM's settings run after Semaphore Manager's service and the ondemand selection remains.

Thanks for your comments. Yes, your request is interesting. Added in my TODO for next versions.

About Semaphore Auto Brightness:

auto brightness in ROM's settings MUST ALSO be enabled. Otherwise Semaphore auto brightness does not work.
[Galaxy S I9000 Android Development] beint:
Hi stratosk

Whenever I choose a governor, and then go into the governor tweak settings, all tweaks are set to zero. Sample factor. etc...

Waddya think?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] stratosk:
Hi,

Any steps to reproduce this? Logcat maybe?

Please try to reset to defaults and retry.

(Please use Semaphore Manager thread)
[Galaxy S I9000 Android Development] yahyoh:
delete it ;p
[Galaxy S I9000 Android Development] adrianmak:
I'm from kernel 2.1.0s. I just flashed 2.1.1s but my phone got a black screen after showing the semaphore logo
[Galaxy S I9000 Android Development] s3icc0:
mine too ... i wait 5 minutes .... then reflashed..... again black screen .... back to 2.1.0
[Galaxy S I9000 Android Development] yahyoh:
what rom?

2.1.1 only for 17/9 nightly and up if u are on nightly before 17/9 or any other rom it will not work
[Galaxy S I9000 Android Development] adrianmak:
Remics-JB 2.0 Rev1

http://xdaforums.com/showthread.php?t=1804032
[Galaxy S I9000 Android Development] yahyoh:
i think 2.1.1 will not work u have to stay on 2.1.0 until rom dev update the rom with latest cm10 changes ;)
[Galaxy S I9000 Android Development] caper:
as yahyoh said this 2.1.1 is ONLY for 17/9 nightly and up if u are on nightly before 17/9 or any other rom it will not work

Please READ the info !!!!

jmcdpereira
[Galaxy S I9000 Android Development] capriciousmike:
I flashed 2.1.1s and got the black screen mentioned above.

I am running Slim Bean 2.4.

Flashed back to Semaphore 2.1.0s and working fine again.
[Galaxy S I9000 Android Development] matesc:
Guess why? Because you didn't read the changelog. Otherwise you wouldn't even try it.
[Galaxy S I9000 Android Development] RestarTmen:
Until today I'm still trying to guess why people do things without even trying to READ first the instructions for whatever they are going to do.... :eek:

1st post clearly states to use 2.1.1 only with cm10 above or equal 17/09 nightly....

Just flashed both, 1st rom upgrade and then kernel upgrade and everything fine as usual! :highfive:

Regards!
[Galaxy S I9000 Android Development] trailblazerz11:
Works now with your initramfs :)

Thank you thank you