yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pikachu01:
Only software decoding using a movie player can stress your CPU like never before. Hence, my Android Optimization Tips uses RMVB software decoding as an example to test OC/UV. Check my sig and CTRL-F for undervolting.

Yeah, I haven't edited it since the last time around. :P

After much testing, SIO is much better. It scrolls without lags while VR faces lags (even when backseek penalty is set to 1). The VR scheduler has too much overhead from processing, whereas SIO is much simpler.
[Galaxy S I9000 Android Development] ~ Myzrael ~:
I agree, best combo is sio+smartassv2
[Galaxy S I9000 Android Development] kubilayk:
Great kernel for all GB roms... Thanks man.
[Galaxy S I9000 Android Development] flolep:
Ok ok. I still think that it could be good to have the option but if stratosk and hm.carbide don't integrate it, I will stick with sio. Thanks pika.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pikachu01:
It's not a bad idea to integrate it, but I have very visible lags with VR. In fact, I just tested it again. Scrolling through Root Browser lags with VR (even with backseek penalty at 1) :(
[Galaxy S I9000 Android Development] pxrave:
do not include all crap into this kernel only space for the best we have a very good range for governors & schedulers

:)

i prefer smartassv2 & sio work very smooth
[Galaxy S I9000 Android Development] ponghk513:
i have tried 1000, still the same.

and what is "play with voltages" ? could you explain more , thanks
[Galaxy S I9000 Android Development] stratosk:
Maybe, I can try it in future. But as others said, I think we have the best schedulers for our phone available.

Can you please try to clean your dalvik cache?

@all

Anyone else tried the new auto brightness driver. Is it convenient now?
[Galaxy S I9000 Android Development] sryche:
stratosk thanks for big effort but autobright have some bug.

i'm on GalaxyDroid v5.0 and sometimes screen turns green for 1-2 sec.
[Galaxy S I9000 Android Development] stratosk:
Hmm... I suppose is the same side effect of voodoo color when the screen goes off?

Did you try to reset to default gamma values from voodoo control application?
[Galaxy S I9000 Android Development] sryche:
yep u re right, thanks again.
[Galaxy S I9000 Android Development] ponghk513:
thanks! actually my i9000 suddenly dead today

and i need to flash rom and wipe all data

after that the problem still occur
[Galaxy S I9000 Android Development] Fenvarien:
Autobrightness is working great. I had a complete green screen at my first test, tuning down the voodoo gamma values a bit solved the greenish experience ;-)

Excellent kernel release, Stratosk, very energy saving and innovative!

... using tapatalk
[Galaxy S I9000 Android Development] stratosk:
What exactly do you mean by 'dead'?

Do you have problems only with this game (or application - I don't know what is it)?

Did you have problems before you flash Semaphore?

Did you have problems before you flash your custom rom?
[Galaxy S I9000 Android Development] frydroid:
works great for me! dark preset is in use...i´m a creature of darkness! :D
[Galaxy S I9000 Android Development] krosscheck:
Very nice, my issue is gone :)

Thanks a lot!

-tapatraced-
[Galaxy S I9000 Android Development] Fenvarien:
Dark preset is in use here too, although it could still be a little bit darker ;-)

... using tapatalk
[Galaxy S I9000 Android Development] stratosk:
Now it's easy to do it without waiting a new version :)

You may edit the script in init.d directory and tweak it according to your needs (if you want help with the values please let me know).

You may also copy the script into SemaphoreScripts and edit here (more permanent solutions).
[Galaxy S I9000 Android Development] GreenSGS:
Have been to another kernel today just to see but now back to Home i.e. Semaphore. I can bet, nothing beats semaphore at the moment,you name it performance,stability,battery.

@Straosk, You are the number one with Semaphore kernel on SGS for me.great job.
[Galaxy S I9000 Android Development] stratosk:
Thank you for your nice words my friend.

But I have to be fair and say that the kernel you 've been before, is great and the dev behind it is just excellent! :)

BTW, I've just published the new code in case that anyone is interested in.
[Galaxy S I9000 Android Development] burakgon:
Thank you startosk. I play with my phone on 1440 mhz with stock 1275 mah. Battery life is x1.6 or more. Better brightness driver, smooth gaming, fast browsing, mutitasking. Low memory print + bigmem for high end games. Better colors, better touch, better market, better filesystem, better and faster, 25mb more ram.. Thank you again.
[Galaxy S I9000 Android Development] GreenSGS:
With due respect no doubt about that.

I am a newbie, I am just learning and sharing my experience.
[Galaxy S I9000 Android Development] stratosk:
Unfortunately I run out of 'Thanks' for today.

Thank you!
[Galaxy S I9000 Android Development] ZaneZam:
I just switched to JW1 installed new semaphore 2.4.0 version and it's working perfect here! ;)

So now i'm gonna check charging again. :):)
[Galaxy S I9000 Android Development] gsw5700:
totally agree, perfect as it is...

Sent using TCP/IP
[Galaxy S I9000 Android Development] Bubble-be:
Just a minor spelling mistake :

Semaphore Auto brigthness in the app menu and popup.
[Galaxy S I9000 Android Development] DarkSorcerer:
Thanks stratosk for another excellent release.

Will test the settings for autobrightness. ;)
[Galaxy S I9000 Android Development] stratosk:
Thanks! I will correct it for the bm version.
[Galaxy S I9000 Android Development] gsw5700:
Wicked update, very smooth, liking the brightness driver, just gets better and better

Sent using TCP/IP
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Thanks stratosk! I'll update as soon as the BM is available.

Thanks, thanks and happy holidays! :D
[Galaxy S I9000 Android Development] maopaopao:
waiting for the BM version
[Galaxy S I9000 Android Development] rugal28:
wait bm version
[Galaxy S I9000 Android Development] zecs:
what does BM stands for? and what are the diferences betwen BM and non-BM ?
[Galaxy S I9000 Android Development] abamann:
Bigmem = more memory= no hd video recording.
[Galaxy S I9000 Android Development] bralgei:
New kernel 2.4.0 is working fine. Same score as 2.1 (2422). I run on GalaxyDroid 5, with JW1. After testing about 10 ROM;s, this is the best combination of speed, stability an power consuption (I am a battery freack).

I will get back with power levels on this kernel in days!

Thanks Again!

Any idea where I can learn more about the modules in the kernel?
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Thanks for your feedback.

Have you tried also the XXJVT ROM? Do you find JW1 to be "better" to that one in some way? I ask because I'm in XXJVT wondering if I should update. :cool:
[Galaxy S I9000 Android Development] NEFart:
Happy New Year stratosk! I wish you and your family all the best in 2012! Thanks for your great job!
[Galaxy S I9000 Android Development] stratosk:
Bigmem version 2.4.0bm

- 353 MB available RAM (it breaks 720p video recording)

Happy and Healthy New Year, everybody!
[Galaxy S I9000 Android Development] andip71:
Edit: 352 mb ram. Ok. So just the version info missing.

Stratosk,

I just flashed it but it does not show bm anywhere. Is it really bm version?

Confused

Thanks

Andi

(sent via tapatalk)
[Galaxy S I9000 Android Development] stratosk:
Yes it is. But I forgot to change the version info. :p

I will update it right now.

Thanks

Edit: OK, I updated the file with correct version information.
[Galaxy S I9000 Android Development] mickeko:
If you have more RAM it is bm... There are no other differences in the kernels...
[Galaxy S I9000 Android Development] dongfangri:
Thanks for your great work, Stratosk.

Hope I897 version will also be available before the new year.

Happy New year to every one!
[Galaxy S I9000 Android Development] burakgon:
Ram is 353 for me. bigmem 2.4
[Galaxy S I9000 Android Development] stratosk:
You welcome. :)

New versions for I897 just uploaded.
[Galaxy S I9000 Android Development] Fenvarien:
Thanks Stratosk, just made a very dark version with min_brightness value of 7. This works perfectly well.

Happy and peaceful New Year 2012!

... using tapatalk
[Galaxy S I9000 Android Development] zadock:
Nice kernel stratosk! Only a little question...deep idle don't work in this kernel?

Happy New Year!!

Enviado desde mi Alcatel One Touch
[Galaxy S I9000 Android Development] stratosk:
Thanks.

Yes deep idle works. Did you face any problems?
[Galaxy S I9000 Android Development] pikachu01:
You mean Ezekeel's Didle? Enabling that would prevent the use of screenstate_scaling scripts :(
[Galaxy S I9000 Android Development] didicola:
hey strato my friend! happy new year in a while!

why dont you make an ics kernel for onecosmics version which rock stable and very good in many many aspects?

or are you already planning things?
[Galaxy S I9000 Android Development] stratosk:
Hey my friend! Happy new year!

In the near future I want to focus a little bit more in my real life and to work more on my real job (I love Semaphore but I need money as well :) )

But definitely I'll stay tuned here, update Semaphore and make new things ;).

I came here to stay...
[Galaxy S I9000 Android Development] bhu1:
Happy new year to stratosk and pikachu01. Keep it up guys. May 2012 bring more happiness in both of your lives.
[Galaxy S I9000 Android Development] HiKsFiles:
Charging problem since v2.2.0

Ever since v2.2.0, or maybe 2.3.0 I can't remember exactly, I noticed something strange with the phone when connecting it for charging.

Sometimes, even though the battery is not even near being 100% charged, the phone says it is fully charged.

The only way I can get it to actually recharge the phone is to reboot it and, once rebooted, reconnect it.

I've been running the same JVT with up to date semaphore kernels ever since v1.9.0 and it's been running rock solid.

Since some people here have reported that the GB charging bug has disappeared since version 2.2.0, I suspect my problem is somehow related.

Note that the problem occurs whether the phone is being charged via the computer, the car or from the wall.
[Galaxy S I9000 Android Development] stoske:
Same is happening to me, only when charging via USB.

Beamed from Dark Side
[Galaxy S I9000 Android Development] zadock:
Ok, now works deep idle. But 100 Mhz frequency works for a lot of time :confused:

Maybe some aplication is causing this.
[Galaxy S I9000 Android Development] bralgei:
Yes, I have tryed 3versions with xxjvt and manny with xxjvz, which have also jvt PDA. Second best stock and custom rom base is XXJVZ. But this... Is better. You should update.
[Galaxy S I9000 Android Development] stratosk:
I didn't change anything related in USB in these versions.

But, what do you mean "is not even near being 100%"? Do you mean below 90%?
[Galaxy S I9000 Android Development] ZaneZam:
Happy new year to everybody around here! :) The phone is behaving as it should imho! In fact it doesn't discharge anymore (at least it seems so) after battery full load by connected charger and thats a good thing! :) maybe the case is as stated from pikachu01:

Anyway i can confirm this behaving on semaphore 2.4.0 in combination with JW1 rom! :)
[Galaxy S I9000 Android Development] stratosk:
I don't think it's io_is_busy tunable because I used it since 2.2.0. And I turned it off (when screen off) in 2.3.0. Do you have this problem before 2.2.0?
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Hi stratosk,

In this new compiled version, it's still needed to turn auto brightness off in the phone settings and set the brightness to the lowest value from there too?

I've read somewhere that since you were introducing some tuning it wouldn't be needed anymore, I don't know if the BM is exactly the same as the not-BM (besides mem, of course), since I also read that you "were fixing <something> for the BM", hence they wouldn't be exactly the same.

Thanks!

---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------

Thanks for your reply!

In what exactly you find it "better"? Speed, battery, memory, etc

Thanks and happy new year!
[Galaxy S I9000 Android Development] stratosk:
Hi,

Yes BM is exactly the same except the memory. I only fixed a type in description of brightness scripts.

I forgot to mention this about auto brightness. You don't have to set the brightness to lowest value any more.

Also. you don't need to turn off auto brightness from settings since the function that adjusts the brightness is blocked since you enable the brightness from Semaphore.

Although, I suggest to turn it of (from settings) to minimize the overhead. If you have it 'on', framework will still try to adjust the brightness (without luck of course).
[Galaxy S I9000 Android Development] ZaneZam:
I wouldn't call it a problem as this seems to "fix" the "charging bug" we had. ;) i've seen this first on 2.2.0 with JVZ and now after a change to JW1 with 2.4.0 it's still behaving so.
[Galaxy S I9000 Android Development] stoske:
Happened to me just now at 86%.

I replugged the USB charger and it continues to charge up to few percent and then again... So I need to replugged few times.
[Galaxy S I9000 Android Development] stratosk:
Maybe your battery needs calibration. Leave your phone to complete 2-3 cycles of full charging/discharging without flashing anything between them.
[Galaxy S I9000 Android Development] HiKsFiles:
Yes, exactly!

Last night, before going to bed, it happened and the battery was in the low 60%.

EDIT: I'll do as you suggest stratosk and try to calibrate battery with 2 or 3 full charge/discharge cycle and report back. Might take a few day though...

Can't I just clear battery stats in Recovery mode instead ?
[Galaxy S I9000 Android Development] ZaneZam:
I would do it in addition, first wipe stats and then do the 2-3 cycles. You could also use batterycalibration app from market to wipe stats. ;-)
[Galaxy S I9000 Android Development] jugster:
Has happened to me once too. Long time ago though. Never reoccurred after that though so I didn't give it a second thought.
[Galaxy S I9000 Android Development] yani2000:
Just wanted to point out that the autobrightness script in /etc/init.d from previous kernel version is not needed anymore and can be deleted, because it uses the same insmod line as the new "Dark", "Normal", "Bright" scripts in the current version of the kernel.

I think it's also safe to leave it alone, but your phone will boot a few milliseconds longer. :)
[Galaxy S I9000 Android Development] Dan_Aykroyd:
Nice find! Is that a leftover from which kernel?
[Galaxy S I9000 Android Development] stratosk:
It's from Semaphore's previous version. It's useless now.
[Galaxy S I9000 Android Development] stoske:
I am on 2.2.0 version and my battery is properly calibrated.

It only happends when charching via USB.

Beamed from Dark Side
[Galaxy S I9000 Android Development] SomeYoungGuy:
Will this cause problems if I flash it on a JVZ rom?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] stratosk:
No, it will work just fine (I'm also on JVZ)
[Galaxy S I9000 Android Development] boris03:
update 2.4 for Simplicity jyz?

Hi Stratosk, can I just update the 2.4 on the simplicity jvz?

Just ask because you provided a special version for simplicity - what is different?

Thanks for your perfect Kernel
[Galaxy S I9000 Android Development] jocke_lulle:
Stratosk, very nice kernel release and the autobrightness works excellent!:)

Is there any chance that we can get the colors that are in the latest galaxian kernel? With them the screen looks really nice. It would be a nice tweak to add to your kernel aswell.

Thank you and happy new year:)
[Galaxy S I9000 Android Development] stratosk:
Hi,

Of course you can flash it. The special version has only the boot logo different.

As I said, I don't know if it work with voodoo color. I have to search for this.

But anyway, I think that I'm satisfied with voodoo color and speedmod color implemented in Semaphore.
[Galaxy S I9000 Android Development] DarkSorcerer:
I must say that was the thing I admired the most about Galaxian. Amazing stuff.
[Galaxy S I9000 Android Development] bhu1:
Anyone remembers the line in build.prop to enable hard to kill launcher. I want to try it on ics . Btw will it work on ics launcher.
[Galaxy S I9000 Android Development] pikachu01:
Try using Supercharger or ThunderBolt!'s LMK for that :)
[Galaxy S I9000 Android Development] zsandras:
Hi mate, how can I recognize the not needed, old autobrightness script files in /etc/init.d? Is anywhere a list of the old scripts file names?

Thx.

&rew
[Galaxy S I9000 Android Development] stratosk:
The old script name is S44enable_sema_autobr. You may delete it.

The new scripts names are:

S44enable_semaautobr_bright

S44enable_semaautobr_dark

S44enable_semaautobr_normal
[Galaxy S I9000 Android Development] HM.Carbide:
It is possible to reset to kernel default with semaphore app.

Misc - Profiles - Kernel default

This will remove all semaphore kernel scripts from init.d. Also older scripts from previous versions.

Other scripts will remain.

After that all features are disabled, so you have to enable features you want to have again.
[Galaxy S I9000 Android Development] zsandras:
You are grate Stratosk, I always admire your work.

Thanks and

HARPY NEW YEAR !
[Galaxy S I9000 Android Development] Heniuro:
I've never used Semaphore before, some simple questions:

1. I'm on Darky 10.2.2 (JVQ rom, currently with Darkcore 2.9.3)- Is Semaphore like "newest = best", or is there a specific version which works best with given firmware ?

2. Does Semaphore require specific lagfix setup (currently I have ext4 everywhere) ?
[Galaxy S I9000 Android Development] DarkSorcerer:
1 - No. You can flash the latest, as long its gingerbread.

2 - No.
[Galaxy S I9000 Android Development] dakost:
Great kernel.

Any chances that the lulzactive v2 governor will be added in the future?
[Galaxy S I9000 Android Development] djb77:
Quick question, when installing the Kernel etc does it set permissions for /system/xbin/su ??

Ran Titanium Backup and it said it needed to convert the su permissions from 04755 to 06755.

I can confirm its not my Custom ROM script causing the problem either, as its setting permissions to 06755.
[Galaxy S I9000 Android Development] rmean:
Same here..:)
[Galaxy S I9000 Android Development] Fenvarien:
Here too, additionally Mobile Odin throws an error about su package.

... using tapatalk
[Galaxy S I9000 Android Development] Rebel2k:
Same for me. I corrected that with Titanium automatically and everything seems to be ok.

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] djb77:
Same, just a heads up for the next version of the Kernel I suppose.
[Galaxy S I9000 Android Development] stratosk:
I have no problems here with titanium backup (4.6.7).

Su binary permissions didn't change in latest version.

It was always 4755. Why this should be 6755? I think we need only the setuid special permission since the file is owned by root.

I will update TB when I go home. Maybe something changed in latest version.
[Galaxy S I9000 Android Development] yani2000:
Ah, it's me again with another bad news. :(

With your kernel managed auto brightness (that overrides system settings) all flashlight apps (SwitchPro Widget, Color Flashlight, Torch,...) became obsolete because they can't set your brightness to max for max effectiveness.

But here is the catch:

I don't want to you to fix this because the Browser could then also set that brightness and I don't want that, because Browser's internal brightness setting is always too high even if I set it to lowest value possible (you know the darker the more battery friendlier). :)

You can put this info on first post so people could be warned.
[Galaxy S I9000 Android Development] Rebel2k:
Yeah, that's a change in the last 4.7.0 version of Titanium. That's clearly stated in the changelog. Actually, they just added a check when Titanium Backup starts, to check if SU has the right permissions. The message tells permissions are not correct and could cause issues and ask you to auto-fix it. That's why with your 4.6.7 version you can't see the message. You'll have it when you update for sure! :)

Indeed, that's a bit sad. Maybe you could add an option to say "block apps brightness control" in Semaphore Script Manager to enable/disable this behavior? We would have the best of both worlds, wouldn't we?
[Galaxy S I9000 Android Development] seeraj15:
Does the jvt version of this kernel support init.d? I need to know because I want to use the thunderbolt script.
[Galaxy S I9000 Android Development] Rebel2k:
Yes of course init.d is supported for a long time already!

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
I clearly say it in auto brightness driver description that the the driver will block brightness settings from framework.

Yes, I could implement an option to block or not the brightness from framework.

About su permissions:

Semaphore (and cfroot that Semaphore inherited this) always set su to 4755 and this is

-rwsr-xr-x

After many thousands downloads nobody had problems with this. The su binary has owner 'root' and group also 'root'. The file has set user id upon execution (the 's' in permissions). This means the any user that will run this, the binary itself will have root privileges. 'Set group uid upon execution' (6755) is meaningless. I checked also the permissions of su binary in my linux box (fedora 16):

-rwsr-xr-x. 1 root root 34904 Jul 15 17:05 /bin/su

Also the same in my job's linux servers.

I also checked the official gnucore utils. A part of the installation code:

[COLOR="Red"]setuid_root_mode = a=rx,u+s[/COLOR]

INSTALL_SU = \
p=su; \
echo " $(INSTALL_PROGRAM) $$p $(installed_su)"; \
$(INSTALL_PROGRAM) $$p $(installed_su); \
echo " chown root $(installed_su)"; \
chown root $(installed_su); \
echo " chmod $(setuid_root_mode) $(installed_su)"; \
chmod $(setuid_root_mode) $(installed_su)

I don't know why author of titanium backup did this. I will try to contact him.

Yes, Semaphore supports init.d
[Galaxy S I9000 Android Development] Fenvarien:
Thanks for investigating the su issue.

The new autobrightness works perfect for me, even with a darker preset (min_brightness 7).

... using tapatalk
[Galaxy S I9000 Android Development] stratosk:
No problem.

It would be very easy just to change a line in next version. But, I want to be sure that we are doing things in the 'right' way.
[Galaxy S I9000 Android Development] Rebel2k:
That's the best to do. As you said I never faced any problem with the sure rights we have until know, so let's wait for the explanation from Titanium...

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] stratosk:
i believe that the correct permissions are 4755. Although 6755 will not harm and will definitely work, I'm not sure if another application will check this in the future and say that it will be 4755.

Superuser application also changes permission to 6755. But I think it's 'wrong' (as I said it will be perfectly will work with both ways).

I have already sent an email to Titanium Backup support and I hope for a clarification.
[Galaxy S I9000 Android Development] yamatona:
Disable droidwall, that works for me.
[Galaxy S I9000 Android Development] ZaneZam:
Fine, and now we have to find the issue? I guess you want to play some kind of jeopardy here, hm? just kidding... :D
[Galaxy S I9000 Android Development] djb77:
Well I'd be led to believe if the Superuser app sets it as 6755 that's what it should be. Just strange how only now Titanium checks it.

Oh well, hopefully something will be sorted out and one of the programs will be adjusted to suit the other.

---------- Post added at 01:05 PM ---------- Previous post was at 12:08 PM ----------

@stratosk

While you're here, got an idea for you:

If possible can the kernel have an option for a custom start-up screen at all (the screen before the bootanimation)? Maybe have a file that can be read at the root of the device or /sdcard/ ?

Would be a nice feature but I have no clue if it would be hard to implement or not.